Hi,
I’m importing files from github. It’s format is below: KEY_NAME=SOURCE_STRINGS
But when source string has semicolon(;), imported source string divided source and context. KEY_NAME=SOURCE_STRING1;SOURCE_STRING2
In this case SOURCE_STRING2 becomes context.
To prevent the semicolon in your source strings from being interpreted as a context separator, you can adjust the import settings by using a custom segmentation rule. Please refer to the following page for guidance on setting up custom segmentation in Crowdin:
Hello @DianaO ,
I read your suggested page. In my case source file recognized as key-value structure.
So I can’t see Parser Configuration Tab. Is it my mistake to operation?
The thing is that the ; sign is considered to be a comment, so in order to import everything properly, you will need to enclose strings in quotation marks. For example,
Hello @Olena ,
Thank you for your answer.
I have a question. Are there any other rules about importing key-value structure?
I’d like to know what I need to concern.
When importing a key-value structure, it’s important to ensure that your file format is supported and correctly formatted. Make sure to follow the syntax specific to your file type to avoid any import errors.
Hello @NataliaS ,
I read documents you suggest. I see it is specification.
To import ini file within semicolon its value, I need to edit source file contents.
OK. Thank you crowdin team. Please close this topic.