There are two widely used conventions for representing the end of a line and the start of the next in files. Unix-like systems have traditionally used one character, \n (ASCII 10, "line feed"), while Microsoft DOS and Windows used a sequence \r\n (ASCII 13, "carriage return", \n).
While working on translations, you may run into issues related to line-ending conventions, especially if you work on development projects with multiple developers using different operating systems. Transifex offers a way to avoid these issues during your localization process.
When you upload a source file, transifex takes the line-ending convention of the source file and applies it to the translation files; so, depending on the line-ending convention of your source file, you could face one of the following situations:
If you upload a CRLF source file to Transifex, the translation files will also be CRLF, even if they were uploaded as LF files in your repository.
If you upload an LF source file to Transifex, the translation files generated by Transifex will also be LF, even if they were uploaded as CRLF files in your repository.
Even if you upload your translation files to transifex using a different line-ending convention than the line-ending convention of the source file, they will be changed to match the line-ending convention of the source file.
Looking for more help? Get support from our Transifex Community Forum!
Find answers or post to get help from Transifex Support and our Community.