Simplify translation workflow by using high-level po4a #581
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Since this is blocking the docs components in WebLate, I am going to merge this right away. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In the first iteration of AsciiDoc to gettext to enable translation of docs, 4 scripts did a lot of pre- and post-processing. Pushes to WebLate and merges back from WebLate were a fightening moment, and updating the gettext files generated a metric fuckton of gargabe in commits due to updated timestamps in headers.
This PR gets rid of most of that by using the high-level
po4atool instead of the low-levelpo4a-gettextize,po4a-updatepo,po4a-translateand others. Now one .pot/.po file is directly generated per documentation guide, and po4a takes care of generating translated AsciiDoc files form those big .po files.No translations have been lost: I used
msgmergeto bring the translated strings from the old .po files to the new .po files with the new .pot as base catalog.Review advise: ignore most of it. The only interesting thing here is the high-level
po4atool uses configuration files, which are the files inl10n-weblate/*.cfg. List of files is currently maintained manually but in the near future it will be autogenerated from the navigators in the guides (same we do for the PDF), or automagically captured from the directories (see mquinson/po4a#272).Target branches
Which product version does this PR apply to?
Links
Fixes #<insert issue or PR link, if any>