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.
The [languages] section of config.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 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.
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
contentfolder in this repo and providing translated duplicates of the files found incontent/en.The
[languages]section ofconfig.tomlshould be updated as documented in https://www.docsy.dev/docs/language/UI strings are maintained in the
i18nfolder. You may need to update these if the desired language is not already supported.In development, run
hugo server --printI18nWarningswhen 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
docssubfolder 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.