#~ msgid "Some text"
#~ msgstr "Some text"
Is there a way in Crowdin to preserve commented-out strings in PO files? Currently, they’re being treated as deleted.
Hi there,
Comments are supported in markdown file format, kindly see the file’s documentation and examples:
Hi Tetiana, the file format I’m working with is the PO format, not Markdown
Sorry, I’ve provided you wrong documentation
Comments from the Editor are not included in the exported file. If you filtered out strings with comments in the Editor, it is possible to export filtered in XLIFF format:
In case, this is not what you’re looking for - please provide more details regarding your case and expected results?
@Tetiana No thats not it either. What I’m asking about is specific to the PO file format.
#~ msgid "String one"
#~ msgstr "String one"
msgid "String two"
msgstr "String two"
In the code above, “String one” is commented out because it’s no longer referenced in the code base, but it is still kept in the PO file. But I would like for Crowdin to not delete “String one” when I upload this source file.
Hi @trevorweng
During the import only strings that are ready for localization and exist in the file are imported. If it’s just a comment that refers to no real string, we wouldn’t be able to parse it.
Did you configure the file to use the source node as msgstr?
How about making a small adjustment to the import-export process? If the string exists you can make it hidden during the import so translators wouldn’t be able to access it, but it still would be presented in your file. During the export, you can, theoretically, change it, from the source string to the comment: