Closed
Bug 1615209
Opened 5 years ago
Closed 5 years ago
Fluent migrations should only apply localized entities from bilingual files
Categories
(Localization Infrastructure and Tools :: Fluent Migration, defect, P1)
Localization Infrastructure and Tools
Fluent Migration
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: Pike)
References
Details
Attachments
(1 file)
When migrating off of .lang files (but also PO), the locale files have entities which are not localized.
Right now, we add them to our legacy translations, which creates all-English Fluent files for non-translated content.
Hit us with mission.ftl on bedrock.
| Assignee | ||
Comment 1•5 years ago
|
||
For bilingual files, entities exist regardless if they're
localized or not. That's what .localized on Entity represents.
Make sure we use that when reading legacy files, so that we
only migrate content that's actually translated.
And yes, message keys in our gettext implementation are weird,
I haven't yet figured out a better way to support contexts.
| Assignee | ||
Comment 2•5 years ago
|
||
Landed as https://hg.mozilla.org/l10n/fluent-migration/rev/7da7b5442526e0c1de372799f5433dec0ee0fd1d.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•