Both the standard schema, and accompanying text and documentation, may be provided in multiple languages.
For launch some minimal translation may have taken place.
In further, more detailed translation may take place.
At a basic implementation, the collaborator should be able to:
Use content negotiation and manual switching to display documentation in a different language if appropriate markdown files are available (e.g. going to /home_es or to /home with language-accept:es should provide the text of home_es.md)
Display the relevant language labels and text from within the schema
The multi-language issue does raise some wider problems of consistency between language versions of the standard. Options to deal with this include:
On master displaying a clear note (in each appropriate language) to state that translations are only updated with each new release, and only the English language version of master should be used.
Whenever edits to the schema are made that update the English descriptive text, the related translated texts should be (manually) marked as TRANSLATION_NEEDED (or similar), so that (a) the interface can display a warning to note that the translation may be behind the English version, and (b) so that translators can be assigned to remove all such flags before the next release (or if a release has to be made before translation is done, the absence of translation is clearly noted).
Some governance decisions about translation of each release of the standard remain to be made.
Both the standard schema, and accompanying text and documentation, may be provided in multiple languages.
For launch some minimal translation may have taken place.
In further, more detailed translation may take place.
At a basic implementation, the collaborator should be able to:
The multi-language issue does raise some wider problems of consistency between language versions of the standard. Options to deal with this include:
Some governance decisions about translation of each release of the standard remain to be made.