[Bf-translations-dev] Spring clean up in branches

Gabriel Gazzán gabcorreo at gmail.com
Wed Mar 21 05:49:51 CET 2012


I'd remove *es_MX* for now and ask *es_ES* translators if they will go on
with their effort (or perhaps it'd be less work for them to just start
fresh from the current *es* and adapt it from there?).
FYI currently, *es* does have some american terms, but otherwise it aims to
be as neutral as possible.

Greetings,
Gabriel


2012/3/20 Bastien Montagne <montagne29 at wanadoo.fr>

> Hi translators,
>
> I’d like to make some clean-up in the following languages’ branches:
> * Spanish: Remove at least the es_MX (and probably also es_ES) branches.
> We just do not have enough people working here to keep these, both did
> not had any commit since the move to bf server (2011, early October). So
> even I do know “european” spanish is not exactly the same as “american”
> one, I really think we should just keep es for now (wich is mainly
> South/Center American currently, iirc?) .
> * Portuguese: I’d like to rename pt_BR to simply pt (as we did some
> times ago with spanish), because the later ISO code is more universal
> (i.e. users with locales of all portuguese variants will be able to use
> it).
>
> So, if you have any comments/suggestions/disagreements about this,
> please talk – I intend to make the changes next week-end! :)
>
> Best regards,
> Bastien
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-translations-dev/attachments/20120321/dea9af00/attachment.htm 


More information about the Bf-translations-dev mailing list