- Develop a glossary first
- Separate translation and review
- Translation feedback
- Normative documentation
- Translation policy
Develop a glossary first¶
Terms may be translated inconsistently, or technical translators may not select the right term of art.
Develop a glossary first, to include the key technical terms and terms-of-art used in the standard.
Write a concise description of each of these terms in the context of the standard. This can ensure terms are used consistently in the main language, and that translators have information to base their translations on.
Separate translation and review¶
Mistakes in translation, or translations that make wrong assumptions about the audience, can cause a lot of confusion.
Separate translation and review. Have the same reviewer for a language to ensure consistency.
Users may have questions or suggestions to improve a translation.
Provide tools to allow them to comment on the translated text.
Tools like hypothes.is can support non-technical users (who wouldn't use GitHub) to annotate a schema.
Documentation may need to be improved. Improvements can be delayed if waiting for a new version
Clearly separate normative and non-normative documentation so that updates can be made more easily.