Update Spanish translations

[jpmckinney]

About 50% translated in 0.9.4.

[duncandewhurst]

The new pages in 0.9.4 were missing from the list of resources in Transifex so I followed the steps in the handbook to extract, map and push strings to Transifex.

After doing so, the translation is more like ~30% complete.

[duncandewhurst]

@EvelynDinora, regarding the sustainability modules documentation, please confirm which parts you want to be translated to Spanish:

[duncandewhurst]

I've taken the OCDS Development Handbook instructions for translators and I'm adapting them for OC4IDS in a Google Doc.

If the mappings need to be translated, I think we'll need to add some extra instructions on which parts to leave untranslated, e.g. don't translate words in backticks or single quotes. Likewise, we should explain what to do with relative URLs, e.g. if a heading in the schema reference Markdown page is translated, should the translator update the references to that heading, or is that something that we do afterwards as part of a tidy-up?

[jpmckinney]

Is there a reason there is a copy for OC4IDS, rather than making changes to the original? (e.g. moving OCDS-specific content to admonitions). From the doc's change history, it looks like it's mostly changing the examples to be about OC4IDS.

[duncandewhurst]

Mostly that all the links pointed to the OCDS docs and OCDS Transifex project and I think it'll be easier for the translator to follow the instructions if the links point to the project that the translator is working on. Happy to discuss how best to integrate the docs for both projects, this was just a quick route to having something the OC4IDS translator can work with.

[jpmckinney]

Cool, we can just provide both links.

[duncandewhurst]

Like this? (Just checking before I add them all)

1. Go to the list of resources (OCDS, OC4IDS)

[jpmckinney]

Yup, that works.

[EvelynDinora]

@EvelynDinora, regarding the sustainability modules documentation, please confirm which parts you want to be translated to Spanish:

Hi @duncandewhurst I am happy to translate the updates in the same way and to the same extend we did for the original OC4IDS, please. Many thanks.

[duncandewhurst]

@EvelynDinora in the original mapping of the core CoST IDS elements, only the OC4IDS mapping column is translated (see below). Do you want to take the same approach for the sustainability modules, i.e. translate only the OC4IDS mapping and not the CoST IDS element titles and disclosure formats?

I think it'll be most useful to readers if everything is translated, but I'm not sure if you have already arranged the translation of the CoST IDS elements elsewhere. If so, we can reuse those translations to avoid duplicating work.

[EvelynDinora]

@EvelynDinora in the original mapping of the core CoST IDS elements, only the OC4IDS mapping column is translated (see below). Do you want to take the same approach for the sustainability modules, i.e. translate only the OC4IDS mapping and not the CoST IDS element titles and disclosure formats?

I think it'll be most useful to readers if everything is translated, but I'm not sure if you have already arranged the translation of the CoST IDS elements elsewhere. If so, we can reuse those translations to avoid duplicating work.

@duncandewhurst yes, we can translate everything to facilitate what is most useful for the readers, even the original CoST elements that were not translated at the beginning. Many thanks.

[duncandewhurst]

@EvelynDinora. Great. I've pushed the missing strings to Transifex. Everything is now ready for the translator.