Closed
Bug 1734220
Opened 3 years ago
Closed 2 years ago
[meta] Migrate strings from browser/chrome/browser/translation.dtd to Fluent
Categories
(Firefox :: Translations, task, P4)
Firefox
Translations
Tracking
()
RESOLVED
FIXED
106 Branch
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: nordzilla, Assigned: eemeli)
References
(Blocks 2 open bugs)
Details
(Keywords: meta)
Attachments
(1 file)
As part of the M3 milestone, we should migrate strings from browser/chrome/browser/translation.dtd
to Fluent
At the time of creating this bug, this file contains 18 strings that should be migrated to Fluent.
These strings don't block the startup path or anything else critical, but should be moved eventually.
This will serve as a meta bug for the migration.
Updated•3 years ago
|
Component: General → Translation
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → earo
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•2 years ago
|
||
The strings from the translation.dtd and translation.properties files are all
merged into a single translationNotification.ftl file.
The string concatenation used in the original is maintained here, as DOM
Localization does not allow for using a <menulist> as a localized element.
Updated•2 years ago
|
Attachment #9290700 -
Attachment description: WIP: Bug 1734220 - Migrate translation-notification.js to Fluent → Bug 1734220 - Migrate translation-notification.js to Fluent. r=jaws!
Pushed by earo@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3477776b80ac Migrate translation-notification.js to Fluent. r=jaws,fluent-reviewers,flod
Comment 3•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox106:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•