AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Darktable user manual12/27/2023 ![]() generate-translations.sh -no-translations & cd. Update the POT and PO files: cd tools/ &.Commit the PO files: git commit -m "Updated with the PO files from weblate.".Squash all the Weblate commits, since there are so many: git reset $(git merge-base master $(git rev-parse -abbrev-ref HEAD)).Merge the Weblate changes into your locally created branch: git merge weblate/master.Update the Weblate remote: git remote update weblate. ![]() In your local dtdocs git repo, create a new branch: git checkout -b po-updates.Lock the Weblate project to prevent further changes: wlc lock darktable/dtdocs.Commit any changes in Weblate: wlc commit darktable/dtdocs.The following assumes that you’re git working directory is clean, that you have API access to the Weblate instance, that you’ve configured the Weblate git repo as a remote in your local dtdocs git repo, and that wlc, the Weblate command line client, is configured. □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.
0 Comments
Read More
Leave a Reply. |