You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Versions of the cdevents.dev narrative content in other languages can be added at any time by adding a new, language-specific content root under the content folder in this repo and providing translated duplicates of the files found in content/en.
UI strings are maintained in the i18n folder. You may need to update these if the desired language is not already supported.
In development, run hugo server --printI18nWarnings when doing translation work, as it will give you warnings on what strings are missing.
Translations of the specification documentation will require language-specific forks of the spec repo. The docs subfolder of the content/<new language>/ folder should be linked as a git submodule to the appropriate fork. Note the need to manually maintain and synchronise the releases of translated versions of the spec.
The text was updated successfully, but these errors were encountered:
How common is it nowadays that these kinds of websites have support for multiple languages? And what languages would then be the most common ones? I believe some such existing multi-language websites have a different initial language than English and then English translation is added to reach a wider audience, which is not the case for CDEvents.
I currently don't see that we should spend time on translating this info to any other language. It might be interesting if we sometime foresee an increase in CDEvents adopters in some region where English is not commonly understood.
I see a risk that this issue will not be resolved anytime soon. Should we instead document the description from this issue in e.g. a CONTRIBUTING.md document in this repo and then close this issue for now?
If the intent is to establish an international standard, diversity is particularly important, in order to identify localisation challenges that may sit outside the experience of contributors from some regions. Similarly, adoption of a standard can be rapid in highly active tech regions like India and China, if there is localised documentation available to simplify the process.
Versions of the cdevents.dev narrative content in other languages can be added at any time by adding a new, language-specific content root under the
content
folder in this repo and providing translated duplicates of the files found incontent/en
.The
[languages]
section ofconfig.toml
should be updated as documented in https://www.docsy.dev/docs/language/UI strings are maintained in the
i18n
folder. You may need to update these if the desired language is not already supported.In development, run
hugo server --printI18nWarnings
when doing translation work, as it will give you warnings on what strings are missing.Translations of the specification documentation will require language-specific forks of the spec repo. The
docs
subfolder of thecontent/<new language>/
folder should be linked as a git submodule to the appropriate fork. Note the need to manually maintain and synchronise the releases of translated versions of the spec.The text was updated successfully, but these errors were encountered: