locale: Update es-419 translations from in-progress Google Docs sheets

[pwithnall]

The translations are not yet fully complete, but this gets us a lot closer.

This commit is the result of:

1. Downloading the Docs sheets as CSVs (see below for links).
2. Renaming ‘Spanish Translation’ to ‘Translation’ as a column in each of them, as kolibri-tools uses the column names to find translations.
3. Putting the CSV files in kolibri_explore_plugin/locale/es_419/LC_MESSAGES. Naming doesn’t matter, as long as they have a .csv extension.
4. Running yarn run i18n-download-translations and selecting only the es-419 changes to be committed.

Google Docs spreadsheets are:

• https://docs.google.com/spreadsheets/d/1fNnvbH1erD-Ll6kOgab870F-Jqpvj-LCuoZEVEjoy74/edit#gid=644360418
• https://docs.google.com/spreadsheets/d/1HiCGm0XIXi5dOQMEIiwVitbdG4RKFgEy-6yKI9RksG8/edit#gid=1637832512
• https://docs.google.com/spreadsheets/d/1qtkHtDQOMzfK_8_IQnL59WGK-ub2BjIpsccjac7iYf0/edit#gid=1161103477
• https://docs.google.com/spreadsheets/d/1J4OyG-KCARsC0hSc0zC0LOguUdpmVw_YJxYG2HA5rBc/edit#gid=1177927074

Signed-off-by: Philip Withnall pwithnall@endlessos.org

Helps: #765

[pwithnall]

The obvious steps to improve this process would be:

1. Rename the columns in the source Google Docs so they’re the right name and don’t need post-processing.
2. Fix kolibri-tools to actually error if it can’t find the expected column in the CSV, rather than just happily writing out a blank file.

I chose not to make those changes in this PR so we can get it merged asap.

[manuq]

I think you should also remove es-es from kolibri_explore_plugin/locale/language_info.json, right?

It is a bit awkward, but can we keep both es-es and es-419 as duplicate files? Ideally we would have es directly but it doesn't seem to be how kolibri/formatjs wants it?

[pwithnall]

I thought we weren’t targeting es-ES at all?

[manuq]

I thought we weren’t targeting es-ES at all?

I don't know which locale will be used for QA'ing this. Kolibri has both es-419 and es-ES. I wonder if a simple symlink would work in all of our platforms.