Closed
Bug 1498533
Opened 7 years ago
Closed 7 years ago
Add serialization to compare-locales, based on cross-channel merge
Categories
(Localization Infrastructure and Tools :: compare-locales, enhancement)
Localization Infrastructure and Tools
compare-locales
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: Pike)
References
Details
Attachments
(1 file)
Cross-channel merge code is useful for serialization of cross-channel, fluent.migrate, fluent.migrate --force, pontoon, and l10n-merge. We’ll need a dead or placeholder entity for the ones that we don’t want to change. That assists the ordering algorithm, but will need to be stripped in prune() to collapse adjacent white-space.
For --force, l10n-merge, and pontoon, we’ll need to reverse the order in which we’re keeping duplicate entries.
For pontoon and l10n-merge we’ll also need an optional filter that strips “bad” messages.
^^^ from Berlin April 2018 notes from Stas & Axel
Assignee | ||
Comment 1•7 years ago
|
||
This adds an option to merge_channels to keep the oldest
instead of the newest variant, and uses that to serialize a file.
The file structure is taken from the en-US template.
This only supports Fluent, Android's string.xml and .properties.
Other file formats supported by compare-locales might work,
but will be added later (and get tests added).
This comes as two changesets, the first of which is just
technical and doesn't really require review.
It's requiring a follow-up change in cross-channel, so I
don't want to just land that.
Assignee | ||
Comment 2•7 years ago
|
||
Landed as https://hg.mozilla.org/l10n/compare-locales/rev/17b6b3bc231c18006f052c081889a06bc1c875a6.
It'd be nice if we could dogfood the code from pontoon a bit before I release 5.0.3 ;-)
Assignee: nobody → l10n
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•