On Wed, 2008-11-05 at 19:20 +0100, Marc Fargas wrote: > Hi all, > I was updating the .po file and there's a msgid that reads "Flag" in > contrib/comments/templates/comments/flag.html:12, as far as I > understand Django's i18n, if I translate Flag to anything in django.po > this translation would be used *always* no matter on where the string > appears... > > The problem is that, in context, Flag means "Marcar" (from Flag as > ....) but the word alone means "Bandera", so, at least in Spanish and > Catalan (and I guess lots of other languages) Flag cannot be > translated right now without either: > > a) Showing "Bandera" were we would like to show "Marcar" > b) Showing "Marcar" were we would like to show "Bandera" > > Am I wrong, or would Django really handle this that way? > > Then a solution could be to change flag.html:12 "Flag" to "FLAGAS" or > something like that, but that would mean that conf/locale/en should be > updated at least to include this msgid !
Normally that would be the solution. However, Django also has to work with USE_I18N=False, so all our msgids have to be useful as raw strings. Unfortunate sometimes, but that's the way it goes. In this particular case, perhaps there's an alternative phrase or less common word that could be used. It's an imperfect world here; we have to work on a case-by-case basis, since messing up the English version or requiring the i18n overhead in those cases just to support non-English languages is as bad as ignoring support for non-English languages. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N?hl=en -~----------~----~----~----~------~----~------~--~---
