> Also, you should be using a recent SVN checkout for this to work.
It does work with he latest development version. Thank you!
Jonas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post t
On 8/2/07, Jonas <[EMAIL PROTECTED]> wrote:
>
> 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 th
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 a
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
4 matches
Mail list logo
