Add Spanish (Cuba) and Spanish (Spain) to l.d.o

I think it makes more sense to have "Spanish-Spain" and "Spanish-International" (#568454-6: Create localized versions of Spanish)
for a more neutral Spanish, which might serve well to many Latin American countries

Yes, let's 'proceed with this in a sensible manner'.

At some point, the question is only what the best moment is, we should start creating new regional versions of Spanish. At the moment we still lack the tools to have versions that default translations to other languages so this will require some manual work by admins for each language version to periodically update missing strings from other versions of Spanish.

I.e. I'd like to be the admin for Spanish-International (that should be current 'es') and Spanish-Spain (es_es). Then I'd periodically update missing 'es' translations with 'es_xx' translations available from any other version of Spanish and I'd update 'es_es' translation from the 'International' version. There's no reason for the International version to have any preference for 'Spanish/Spain' over other regional versions so this should be done in a kind of random manner, that's why I'd update 'International' version with *any* other of them, possibly starting by the one that gets more translations, then other strings would stand as suggestions.

Or maybe we should try to minimize the amount of duplication and ask people to download es_es on top of es translation though this is not very practical from the end user pov, and also with the current client side tools (l10n_client, l10n_update) we have. I really don't know.

This will need to be done manually for now, and this will create lots of new strings on the server (many of them the same but for different language versions). When we go through this a number of times we are likely to multiply the amount of work for everybody, having thousands of suggestions for every Spanish version coming from other Spanish versions.

This is why I was not really in a hurry to start with new versions. Though I agree we may start needing some 'local versions' of Spanish.

So Gabor, if you think we are good from the server side to have maybe 20+ new teams and many thousands of new strings, I'm willing to give it a try to 'Spanish-Spain' (and of course any other country that requests it too, as long as someone takes care of each as I'd only administer and take care of periodically cross-updating 'International' and 'Spain').

Well, it is just my guess they will :-)

I may be wrong though. So we can create Spanish-Spain, I'll post the news to the 'Spanish' group (that will become 'Spanish-International') and deal with it when/if it comes.

But better let me know what you think could be a sensible guideline por requesting a new Spanish version (so I can post it to the group too). I.e. (1) post an issue on Infrastructure, then (2) post a follow-up each person willing to work on that one and (3) agree on a first maintainer/s that would hand over permissions to other people. ?

I think we should start creating "Spanish-Spain" and "Spanish-International" and then allow people from other countries to create "Spanish/[Country]" for their own regional version.

Although in principle "Spanish-International" may serve well for several Latin American countries, I think there will be interest from people from other regions to maintain their own regional distribution.

This is a great idea.

I had to customize some translations in the past to use a "colloquial-Spanish" ("tú" instead of "usted") and I wonder: Wouldn´t it be great to have both Formal and Unformal language variants too? Or would that be too many groups?

If possible add South American Spanish

If possible add Spanish Internatinal or Spanish South America

No progress

Well, I think it is a bout time to pick this up.
There are multiple versions of Spanish and it seems that they need to be kept in sync manually because we do not have language inheritance in here. Well, I think that is not really necessary. Any variation of the Spanish (es-es, es-ar, es-bo, etc) can be created now as a copy of the current es, and maintained independently. They will diverge naturally as the languages and the maintainers are different for each one.

Considering that I am ready to clone the current es into es-es and start making some changes to it. But what is the process to follow? How is a language created in localize.drupal.org?