Under Community Review

JSON parser - Conserving spaces as source

Currently, using the JSON parser in Passolo 2018, the localized target files' structure is not strictly identical to the source file.

Indeed, the number of spaces found before each string is divided by two. For instance, in the source en.json files, when the developers have added 4 spaces before the string ID, Passolo generate files with 2 spaces. There is no setting to change this behaviour in the parser.

This is correct JSON formatting, but from an engineering perspective we don't get the same structure and it would  be great to have target JSON files structured just like source JSON files.