Hello all, As you probably know, since some time we've separated django-localflavor into a separate project on GitHub. Translations, like the rest of Django, are handled through Transifex. However, due to the nature of localflavor not all translation strings are equally important. Translating an error message in the br localflavor to Brazillian is essential, but not so important to translate to Dutch. And we don't even have Dutch names for Hungarian province names.
To get some better statistics, I wrote a little script that tries to connect localflavor and language names, and rate how many messages from a flavor are translated into that flavor's language. It's not flawless yet, but I posted the report that I have now on: https://gist.github.com/erikr/86375a042988b8a781fc You can find the script in my branch: https://github.com/erikr/django-localflavor/blob/translation-rating/translation-rate.py We have quite a few geographical names where the original message in the code is already in the local language, so a translation would be identical, but they are being reported as untranslated. I haven't thought of a reliable way to filter that yet. Interesting already is that for the at, ch, cl, co, cz, dk, ee, gr, hk, ie, il, jp, kw, mt, no, nz, pe, pk, se, sg, si and za local flavors, we have no translations at all. Some of these may be due to mismatching of the language, or because users in New Zealand simply always use AU or US English. Perhaps people from these countries could comment. In any case, I hope this can help local translation teams to prioritise which strings should be translated :) Erik -- You received this message because you are subscribed to the Google Groups "Django internationalization and localization" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-i18n. For more options, visit https://groups.google.com/d/optout.
