-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let mdbook-xgettext
generate a file in the same format as msgmerge
#32
Labels
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
Comments
mgeisler
added a commit
that referenced
this issue
Oct 2, 2023
This will reduce churn between the output of `mdbook-xgettext` and `msgmerge`. See google/comprehensive-rust#1245 for an example PR which would shrink with this feature. Part of #32, but we still have differences in the way the messages themselves are wrapped.
The changes for this should ideally be made in polib: BrettDong/polib#8. |
This was referenced Oct 2, 2023
mgeisler
added a commit
that referenced
this issue
Nov 10, 2023
Noticed by @henrif75 in google/comprehensive-rust#317. Part of #32 and a followup to #93.
mgeisler
added a commit
that referenced
this issue
Nov 10, 2023
Noticed by @henrif75 in google/comprehensive-rust#317. Part of #32 and a followup to #93.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
Today,
mdbook-xgettext
outputs a PO file which looks different from whatmsgmerge
outputs. The result is that translators get a huge diff the first time they runmsgmerge
. This is confusing, e.g., see the question in google/comprehensive-rust#743 (comment). It is also annoying since it prevents people from reviewing the changes.The text was updated successfully, but these errors were encountered: