In the past we had multiple dialects of Spanish on Transifex with various degrees of translation progress. As I understand it they were nearly identical and it confused translators, because only one of them was shipped with Discourse. The main translators at that time requested all the clones to be deleted in May 2019.
We certainly can add one or more languages back on Crowdin. There’s a long list of Spanish languages available.
||Spanish, Costa Rica
||Spanish, Dominican Republic
||Spanish, El Salvador
||Spanish, Latin America
||Spanish, Puerto Rico
||Spanish, United States
Looking at that list, I think
es more or less would be
es-ES? So, maybe let’s add
I’m still not sure about the process for translating language dialects (and that’s not specific to Spanish):
- Start from scratch?
- Or initialize it with existing translations from
es and let them diverge afterwards?
- Or translate only strings which are different from
es and mark the rest as “Done” in the editor? There’s a filter option for “Done” and “ToDo” in Crowdin that might come in handy.
- Or use existing translations (from
es in this case) from Translation Memory and maybe add a new feature to our Crowdin integration that deletes those copies from
es-MX when strings in
es are changed?
Crowdin’s “Switch Source Language” workflow step is still unusable, so that’s not an option. cc @Andriy_Crowdin
We can always configure Discourse to use
es as fallback locale for
es-MX, so there’s no need to translate everything. But I don’t know anything about Spanish. How similar are