On Sat, 2007-07-14 at 12:53 -0500, Jorge Gajon wrote: > 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.
Cool. Thanks for the rapid feedback (Ramiro, too). The only other person who might be affected is Mario Gonzalez (who contributes to the 'es' translation). However, I think he might be outvoted in any case. Not that I don't love the rest of the translators like my own family, but all the other files are already in UTF-8, so it's a bit of a non-issue there. I'll leave it up to translators to do the re-encoding, because I suspect that if I commit a huge change like that you might get a bunch of subversion conflicts on the next update. Regards, Malcolm -- Honk if you love peace and quiet. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
