search

open-contracting / standard-development-handbook

A guide for authors of the Open Contracting Data Standard
http://ocds-standard-development-handbook.readthedocs.io/en/latest/
Other
6 stars 3 forks source link

Describe what not to translate #289

Closed duncandewhurst closed 6 months ago

duncandewhurst commented 6 months ago

I forgot to add this in #288

Regarding my question in https://github.com/open-contracting/infrastructure/issues/467#issuecomment-1969942902:

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?

I realised that the anchor slugs created by the MyST parser are not translated, e.g. https://standard.open-contracting.org/infrastructure/latest/es/guidance/identifiers/#project-identifiers-in-ocds

jpmckinney commented 6 months ago

Actually, this is covered at https://ocds-standard-development-handbook.readthedocs.io/en/latest/standard/translation/quality.html#translation-style-guide along with other reminders.

duncandewhurst commented 6 months ago

Ah, how did I miss that!