![]() □Integrating new translations from Weblate Repeat the last four steps for the other themes, themes/hugo-darktable-docs-epub-theme and themes/hugo-darktable-docs-pdf-theme.Check the translated PO file into git, push it to github, and open a pull request to have your changes accepted.Translate the content of the new yaml file.Copy content of the file en.yaml and name the new file.Go to themes/hugo-darktable-docs-themes/i18n.You’ll need to translate the strings for both. There are two themes for the darktable documentation: one for the HTML website and one for the PDF. □Translating website, epub, and PDF strings generate-translations.sh -rm-translations. Remove the translated files, as we never check them into git:Ĭd tools/ &.The URL is in the output of the hugo server command. ![]() Open a web browser and check the changes.Check the translation by starting hugo’s internal server:.generate-translations.sh -no-translationsĭo the following steps to generate the website files from a translation.Ĭd tools/ &. Run the script to populate the PO file:Ĭd tools/ &.Create an empty PO file for your language in the po folder with the file name content.po.For example, the English looks like this: en-us:ĭo the following steps if you want to update the POT and PO files from the markdown source. In the files config.yaml and config-pdf.yaml, locate the languages: line.Īdd the language you wish to translate. Make a new branch to work on it in git.We will not accept pull requests directly on github to update PO files. Please do all translation work through Weblate. You can either use Weblate’s web UI to translate the documentation or download the translation from Weblate to your computer, edit it, and then upload the changes. Translation of the darktable documentation is done via our Weblate instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |