[WG: I18N & L10N] Mexican Spanish issue

Neal Caidin neal.caidin at apereo.org
Thu May 29 09:47:12 PDT 2014


It's already too late for Sakai 10.0

The team is working diligently to get out Sakai 10.0 in time for the 
conference (or at least a release candidate, which is "code frozen".)

I think we will need to go with the option to copy the es_ES to es.

2 cents.

-- Neal


> Rafael Morales Gamboa <mailto:rmorales at suv.udg.mx>
> May 29, 2014 at 12:19 PM
> Hello,
>
> Sorry about this. I was translating to es_MX but a got "too busy". So 
> please let me know a date and I will try to have the translation complete.
>
> On the other hand, I agree with having a default Spanish translation. 
> It should be the most complete one, and if there is more than one we 
> can toss a coin.
>
> Regards,
> Rafael
>
>
> On 29/05/2014 10:37 a. m., Matthew Jones wrote:
>
> _______________________________________________
> 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"
> Matthew Jones <mailto:matthew at longsight.com>
> May 29, 2014 at 11:37 AM
> 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.
>
>
>
> Neal Caidin <mailto:neal.caidin at apereo.org>
> May 29, 2014 at 11:29 AM
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/i18n/attachments/20140529/59b8ba5b/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1185 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/i18n/attachments/20140529/59b8ba5b/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/i18n/attachments/20140529/59b8ba5b/attachment-0001.jpg 


More information about the i18n mailing list