On 7/14/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > 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
Hi, I'm not the only contributor to the 'es' translation, but it is perfectly fine with me if we re-encode it to UTF-8. I'll re-encode 'es' and submit a patch. Regards --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
