[Petter Reinholdtsen] >> Regarding Plinth, translation has started on Github >> https://github.com/freedombox/Plinth/tree/bcb26cc52c9048501e3cfa1098de98df4a4b75af/locale > > Very good that it is using PO files.
Btw, I had a closer look (and started on an nb translation), and noticed two typos (missing quotes) in the fr file. I've commited a fix, but you should check if I got it right. But most translation files are empty at the moment: % for f in locale/*/LC_MESSAGES/django.po ; do printf "%s " $f; msgfmt --output=/dev/null --statistics $f; done locale/de/LC_MESSAGES/django.po 0 translated messages, 240 untranslated messages. locale/es/LC_MESSAGES/django.po 0 translated messages, 240 untranslated messages. locale/fr/LC_MESSAGES/django.po 240 translated messages. locale/it/LC_MESSAGES/django.po 0 translated messages, 240 untranslated messages. locale/nb/LC_MESSAGES/django.po 28 translated messages, 212 untranslated messages. locale/pt/LC_MESSAGES/django.po 0 translated messages, 240 untranslated messages. % What is the logic beind the current language selections? Do we have volunteer translators for the listed languages? Btw, why is the file structure locale/<lang>/LC_MESSAGES/django.po? A more common structure is to use locale/<lang>.po or similar (I've seen po/ as the directory too), and this make it easier to loop over all the translation files, as the language code is included in the file name. -- Happy hacking Petter Reinholdtsen _______________________________________________ Freedombox-discuss mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
