Skip to content

Cannot escape "Parse From Developer Note Separator" #115

@yurim108

Description

@yurim108

Pipeline (|) is setup as a default separator.
How to deal with the situation when the pipeline must be included into translation (in the middle of a running project)?

Example:
ConfigFileFilterLbl: Label 'JSON files (.json)|.json|All files (.)|.', Comment = 'de-DE=JSON Dateien (.json)|.json|Alle Dateien (.)|.';

Changing default separator would mean that we need to check all other existing translations, whether they include the new separator.

Suggested solution: when the separator occures twice (||) then treat it as a single pipeline without separator functionality.
In this case one would have to escape the pipeline in the translated text like this:

ConfigFileFilterLbl: Label 'JSON files (.json)|.json|All files (.)|.', Comment = 'de-DE=JSON Dateien (.json)||.json||Alle Dateien (.)||.';

Another solution would be to define a line specific separator like this:
ConfigFileFilterLbl: Label 'JSON files (.json)|.json|All files (.)|.', Comment = 'Separator=##de-DE=JSON Dateien (.json)|.json|Alle Dateien (.)|.#fr-FR=.......';

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions