איזו ניב של ספרדית צפוי להיות נתרם?

In the past, we had multiple dialects of Spanish on Transifex with varying degrees of translation progress. As I understand it, they were nearly identical and confused translators, as only one of them was shipped with Discourse. The main translators at that time requested that all clones be deleted in May 2019.

We can certainly add one or more languages back on Crowdin. There’s a long list of Spanish languages available.

Language Code Name
es Spanish
es-EM Spanish (Modern)
es-AR Spanish, Argentina
es-BO Spanish, Bolivia
es-CL Spanish, Chile
es-CO Spanish, Colombia
es-CR Spanish, Costa Rica
es-DO Spanish, Dominican Republic
es-EC Spanish, Ecuador
es-SV Spanish, El Salvador
es-GT Spanish, Guatemala
es-HN Spanish, Honduras
es-419 Spanish, Latin America
es-MX Spanish, Mexico
es-NI Spanish, Nicaragua
es-PA Spanish, Panama
es-PY Spanish, Paraguay
es-PE Spanish, Peru
es-PR Spanish, Puerto Rico
es-US Spanish, United States
es-UY Spanish, Uruguay
es-VE Spanish, Venezuela

Looking at that list, I think es more or less would be es-ES? So, maybe let’s add es-MX?

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 that 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 a fallback locale for es-MX, so there’s no need to translate everything. But I don’t know anything about Spanish. How similar are es-ES and es-MX?

5 לייקים