The default language of this website is English [en], content in this language shall always be the primary source of truth.
After creating a fork of this git repository, translating a page or section is very similar to updating a page, the only difference is that you have to create a file of the same name as in the english version in the sub-folder of your target language. All translateable content can be found inside the _i18n/ folder.
So if you would like to translate section1 of the how-to-vote page (_i18n/en/how-to-vote/section1.md) into chinese, you would create the file _i18n/zh-hans/how-to-vote/section1.md and fill it with the translated content. That’s it!
Some general translations, such as site title, header menu or footer content, are done in a YAML file, located at _i18n/LANGUAGE.yml, please refer to _i18n/en.yml for all translateable keys.
Translation of blog posts inside _i18n/en/_posts/ is very similar to the translation of pages. Each blog posts is contained in a separate file, e.g. 2019-02-11-eosdac-dactivation-day-is-here-feb-11th-2019.md.
_i18n/LANGUAGE/_posts/title field.external_link field to point to the translated version, otherwise keep the link to the english version.We are providing a scripts, which help to identify content in need of a (updated) translation.
show_files_to_be_translated.sh inside the _i18n/ folder
./show_files_to_be_translated.sh from within the _i18n foldercheck_all.sh inside the scripts/translation-status/ folder
scripts/translation-status/check_all.sh from within the root folder of this website’s git repository.translation_status/ display website documents which are still TODO, need an UPDATE or are a DUPLICATE of the english version (and thus should be deleted from the translation)The check_all.sh script should be run from time to time and the results inside translation_status/ should be commited to the git repository, so everybody can see the current translation status, without needing to run the script himself.