PO(T) Export, for message extraction #45
Merged
Conversation
This file contains 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
|
@TropicalPenguin Thanks for your contribution. Please note that there are some conflicts after I merged a previous PR I had pending. |
|
Yeah, no problem; got a few more improvements to make anyway. |
Allows stable round-tripping of PO(T) data across multiple message extraction passes. Avoids canonicalisation of header keys, while preserving other semantics.
TropicalPenguin
force-pushed
the
master-potexport
branch
from
0208991
to
01a5eea
Compare
|
I think that should do it 😄 |
|
Thank you @TropicalPenguin ! |
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.
Permits the writing of message extractors, using gotext. With round-tripping support to update existing translations (while preserving contextual details like copyright notices & source references).