> > I'm unfortunately not familiar enough with i18n of Python software and > I have indeed no idea about how to regenerate to POT file from source > code. Could I have a hint about that? This would allow me to refresh > existing PO files and even send a call for translations to existing > translators, in addition to call for new translations. >
Just like with C, the xgettext tool is used to extract translation keys from Python source. There's a bash script in the Pytrainer source, utils/translator.sh, that is used to assist in localising. It generates a messages.pot file, merges the .pot file with the target locale .po file, deletes the .pot file and launches your graphical l10n tool to edit the translation. The current process for adding new translations is to add the new language code to translator.sh then run the script, providing the new language code as the target locale. If you remove the line in translator.sh that contains "rm ./messages.pot" (line 18) then run the script you will end up with the messages.pot file still intact. I think this is the template that you need for you call for translations. If distributing the .pot file is going to be the standard way of translating Pytrainer then we should make this easier. At least we can remove the "rm" statement from translator.sh and add messages.pot to svn ignore. As far as I am aware this translation process is not documented. I can add a wiki page for this. - Nathan ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
