On 5-11-2005, at 15:58, Pedro Furtado wrote:
Just for
illustration, I use non-english caracters in model's verbose name.
IIRC, (x)gettext will have problems if message id's have non ASCII
characters. Better use english only characters in all messages to
avoid potential problems.
---
Neb
>I'm having some headaches with this and don't know how to fix it. For
>now I've changed all the files to ASCII and it works fine, but when I
>save it in UTF-8 the site has some encoding problems. Just for
>illustration, I use non-english caracters in model's verbose name.
Django is by default co
Django handles the encoding too?
I'm having some headaches with this and don't know how to fix it. For
now I've changed all the files to ASCII and it works fine, but when I
save it in UTF-8 the site has some encoding problems. Just for
illustration, I use non-english caracters in model's verbose
>I also think that utf-8 should be the standard file
>encoding for every language translation file.
Don't worry. Just stick to what you are comfortable with, gettext will
take care of it. No need to change anything.
bye, Georg
Hi,
I already started the french translation and I used the given file sample
(iso-8859 encoding). I also think that utf-8 should be the standard file
encoding for every language translation file.
What do you think about it Georg ??
Le Samedi 5 Novembre 2005 00:14, Steven Armstrong a écrit :
>For example the german translations are encoded as iso-8859-1.
>I'm not sure, but guess that this may cause some headaches when serving
>content as utf-8. Or does the gettext library handle this some way?
gettext indeed handles that transparently. So there is no need to use
only one encoding for
On 11/04/05 06:13, Jacob Kaplan-Moss wrote:
Howdy --
I've merged the i18n branch into the trunk; major thanks are due to
hugo! I'm running it live on all the LJW sites and it works fine,
but there could be some lurking issues, so caveat programmer. Adrian
will have a blog post on the ma
Arrgh, I think I had a caching problem. I take it back. Everything
seems to work fine now.
Sorry,
Morten
Hi,
Updating my django source seems to have broken the django admin app. I
get this error: http://django.pastebin.com/417624, saying "i18n is not
a valid tag library.
Any clues as to how to get things working again?
Thanks,
Morten
Howdy --
I've merged the i18n branch into the trunk; major thanks are due to
hugo! I'm running it live on all the LJW sites and it works fine,
but there could be some lurking issues, so caveat programmer. Adrian
will have a blog post on the matter some time in the next day or two
(he's
10 matches
Mail list logo
