On 5/16/06, hugo <[EMAIL PROTECTED]> wrote:
> the "el" translation is broken - it listed utf-8 as charset, but the
> content wasn't utf-8. I don't know what charset it is in, I just set it
> to iso-8859-1 to prevent aborts on it in the make-messages -a stage.
> Someone who can read that language: p
Hi,
>Please use either ISO8859-7 or UTF-8. At the moment it is in
>ISO8859-7. I put an UTF-8 encoded one up at
>http://www.in-nomine.org/~asmodai/django.po
Thx, now it compiles fine.
bye, Georg
--~--~-~--~~~---~--~~
You received this message because you are sub
Please see http://code.djangoproject.com/ticket/2010 for an updated
Dutch django.po.
--
Jeroen Ruigrok van der Werven
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to this group, send
On 5/26/06, hugo <[EMAIL PROTECTED]> wrote:
> Thx, now it compiles fine.
Per
http://code.djangoproject.com/browser/django/trunk/django/conf/locale/el/LC_MESSAGES/django.po
shouldn't the "Content-Type: text/plain; charset=iso-8859-1\n" line be
changed to reflect the UTF-8 encoding?
--
Jeroen Rui
