On 7/14/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> Short version: anybody unhappy if we *require* PO files to be encoded as
> UTF-8? For almost everybody, this means no change at all. For "es" and
> "es_AR", I will have to re-encode the current files (they are
> ISO-8859-1) to UTF-8 and, in future, you will need to edit them as
> UTF-8. I would like to make sure I'm not going to make things impossible
> for anybody by asking for this.
>
> Longer version (with explanation):
> [...]
I was going to post to the list asking about that same topic last week[1].
I'm the es_AR translator and I think there is no problem with what
you propose.
Now that two huge merges to trunk have happened and now you' ve
commited the [5695] fix I can post to Trac an updated translation
with the regular updates plus some fixes. I can post it already encoded
in UTF-8 if you want.
Regards,
--
Ramiro Morales
1. I decided to wait for the then current discussion about the
project-id-version header field value. By the way, we haven't given you much
feedback on that topic; I'm ok with using "Django" "Django JavaScript".
Will also point language-team to this list and will keep filling
my email address
on last-translator
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
