[WG: I18N & L10N] Mexican Spanish issue

[Matthew Jones]

The better overall option would be to copy the es_ES down to es so that all
Spanish variations get some kind of fallback. Trying to figure out the
missing pieces between es_ES and es_MX would require writing some kind of
script and would get out of date, much faster to just either copy or move
all of the es_ES to es.


On Thu, May 29, 2014 at 11:29 AM, Neal Caidin <neal.caidin at apereo.org>
wrote:

> 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"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/i18n/attachments/20140529/792d4cb7/attachment.html