Hello,
> It is simply the localization of literals to the variant of the spanish > language > as spoken in Argentina, not more and not less. When I started it I want(ed) to > have the freedom to decide about it without having to worry about the need of > tradeoffs that could lead to a minimum denominator, lower quality translation. > I know it is not perfect, but I'm happy and proud of it. > > This is why I don't think merging these two translations would be a good idea. > > Of course all the other es* translators, current and future, are free > to reuse the > strings from the 'es_AR' translation as they see fit in the same way I > [1]reused > the efforts the 'es' translators had done when I started it four years ago. > When I said merge this wouldn't imply to make es_AR dissapear. In fact my idea was to use es_AR as the base for es and mantain both translations. What I'm trying to say is that at least es translation should be as completed as es_AR. Now in spanish :) Ramiro, no estoy pidiendo que es_AR desaparezca, mi idea era que dado que es_AR está más avanzada que la localización es se tome es_AR como base. Cuando digo que 'es' es la localización neutra me estoy refiriendo a que en caso de duda un hispanohablante pondrá la localización es, por tanto conviene que esté lo más completa posible. Si la localización que está más completa es es_AR pues tomemos esa como base. Para mi lo que no tiene sentido es que es_AR esté al 100% y es no. No sé si me estoy explicando ... -- Antoni Aloy López Blog: http://trespams.com Site: http://apsl.net -- You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to django-i...@googlegroups.com. To unsubscribe from this group, send email to django-i18n+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-i18n?hl=en.
