Localization notes for coders
Instruction for translators can be found here.
Localization related bugs are here.
- If possible, it shouldn't include spaces or other non-printing characters before or after the sentence/expression.
- TBD Comments to the localizers - maybe the POEditor system does not support it
- TBD Concatenate strings with + (which is easier to read) or with join() (which is faster)?
- TBD Which string formatting to use? It should be easily understood by the localizers.
Adding a new language to CogStat
- Create the new language code directory in locale directory
- Extend the language list for Preferences dialog in cogstat_dialogs.py
- Extend the changelog with the language and the translator
- Add the language and the translator to https://github.com/cogstat/cogstat/wiki/Translation#translators
- Add the new language to the Windows installer
Note for POEditor administrators
- POEditor can import comments for the string from pot file, only if the string is new.
- After importing terms from a .pot file linked from the GitHub page, POEditor will not delete unused terms. Still, this can be done
- with Webhooks (GitHub integration page > Generate Webhook > Operation: Synv terms and translations > access the link)
- or with manual import terms (after the import obsolete terms can be selected and deleted).
Note for transifex administrator
Problem. When uploading already translated .po files, transifex checks if %something is the same both in the source and target languages. However, this is unnecessary, e.g., in '95% confidence interval'. '95%%' would print 95%%, so using it is not a solution.
Solution. To overcome the problem,
disable the translation check as described here,
and remove the "#, python-format" lines (automatically generated by xgettext) from the appropriate strings in the .po files.