[WG: I18N & L10N] Mexican Spanish issue

[Matthew Jones]

Right, the java locale fallback would be to go

es_MX -> es -> en

So without an es the text is just appearing in English. I'd personally be
happy with either keeping es_ES in sync or just making your files from
es_ES the default as es and not having an es_ES variation. You could still
select es_ES from the translation menu in preferences but it would just
immediately fallback to es. That would eliminate having to do changes twice
at least. Whatever you decide though.

I think it would be good just in-case other Spanish countries like es_CO,
es_PR or es_AR, etc decide they also want to support a language with only
slight variations, for instance. :)


On Thu, May 29, 2014 at 11:38 AM, Diego del Blanco Orobitg <
diego.delblanco.sakai at gmail.com> wrote:

> Hi:
>
> As now Spanish (from Spain) is "es_ES" and not "es" (as some time ago),
> when there is not "es_MX" it uses the default (that is english) . I think
> before that "es_MX" searched for "es" when there is not "es_MX" file
> (please, if I'm wrong someone can correct me).
>
> So, maybe other solution can be duplicate all the "es_ES" files to "es"
> and have it as basis for all the spanish translations. better than mix
> es_ES with es_MX becuase if we do that, México people won't know what is
> missing or not to translate
>
> The problem can be to maintain "es" and "es_ES" because we will need to do
> changes twice... or always duplicate files when we change in "es_ES"...
>
>
> 2014-05-29 8:29 GMT-07:00 Neal Caidin <neal.caidin at apereo.org>:
>
> Hi i18n,
>>
>> I found a major regression in that Mexican Spanish in 10.0 mostly shows
>> English, except for a few places.
>>
>> https://jira.sakaiproject.org/browse/SAK-26268
>>
>> FYI - the team is working quickly to get out an 10.0-RC01 (like in the
>> next day or so) , and while i18n issues are not normally considered
>> blockers, it would be nice to get this one fixed ASAP.
>>
>> One option could be to hide the es_MX translations in 10.0 until it is
>> fixed.
>>
>> I guess another could be to copy es_ES (Spain) over to es_MX , except
>> for the few es_MX properties that exist.
>>
>> Thoughts?
>>
>> Thanks,
>> Neal
>>
>>
>> --
>> Neal Caidin
>> Sakai Community Coordinator
>> Apereo Foundation
>> neal.caidin at apereo.org
>> Skype me! (but let me know in advance for the first interaction) -
>> nealkdin
>>
>> _______________________________________________
>> i18n mailing list
>> i18n at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/i18n
>>
>> TO UNSUBSCRIBE: send email to i18n-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
>>
>
>
>
> --
> ***************************************
>  *Diego del Blanco Orobitg*
> Spain & LATAM Regional Manager (*ANI Sakai*)
> Apereo LATAM Representative (*Apereo Foundation*)
>
> P: (+34) 653 683 489
> E: ddelblanco at anisakai.com
> Sk: ddelblanco.ani
> ***************************************
>
> _______________________________________________
> i18n mailing list
> i18n at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/i18n
>
> TO UNSUBSCRIBE: send email to i18n-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/i18n/attachments/20140529/68991360/attachment.html