> here it is from the manual > There are scripts in the "po" directory for converting the text files > to PO format (and back) for easy translation to different languages. > Therefore you should never add or change translations in the .txt > files directly.
Do you know the reason why they use text files instead of MO files? In my opinion, it would be easier to just put the English source message in text files and then let the application get translated messages from MO files with the standard gettext API. When you want to update messages for a given language (which we'll have to do), currently you need to have the PO files for every language, or to write a script that will replace/add in the text files the translations for the language to be updated. Sounds more complicated than just replacing the MO file of the language! > from the readme.txt > In this directory you'll find scripts for converting > the stamp description files to and from gettext PO files, > for use by translators. > > Run the following two scripts (in this order) everytime > a stamp description is added or changed, or a translation > (PO file) is updated: > > createpo.sh > createtxt.sh Ok, I looked at the scripts but finally decided to write my own ones. Indeed these scripts don't do exactly what I need because I don't want to put the text files onto our SVN, only the PO files (avoid duplicate data), and I saw that they didn't use the gettext Python package, which causes their code to be bigger than needed and more difficult to read. Cheers, JM. _______________________________________________ Doudoulinux-lang mailing list [email protected] https://mail.gna.org/listinfo/doudoulinux-lang
