That's not a bug ;) You should avoid using non-ascii chars in msgid strings. This has nothing to do with Django, but with gettext (the "translation" engine behind the scene) itself. There's no point in using non-ascii chars anyways, since msgid strings are thought to be message identifiers, not actual human-understandable strings. Just placeholders. Though using the actual words to be translated eases the job a lot.
Also, keep an eye out for entries marked as "fuzzy" as they won't be used by gettext. 2007/8/2, Jonas <[EMAIL PROTECTED]>: > > There seems to have a bug with the internationalization. > When the (result) translated string has accents, that is the "msgstr" > in the .po file, there is no problem. > > But when the string TO BE translated has accents, that is the "msgid" > in the .po file, no substitution occurs in the translated page. > > Has anybody else experienced this? I think that's a real nuisance: why > should the original language be English? > > I have already mentionned, with more details, the problem in the > subject "Accents in translation strings", but there was no answer, so > I repeat it. > > Jonas > > > > > -- Best Regards, Chris Hoeppner - www.pixware.org // My weblog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
