Localize theme variant names
Categories
(Firefox :: Theme, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox94 | --- | fixed |
People
(Reporter: bugzilla, Assigned: bugzilla)
References
Details
(Whiteboard: [fidefe-theme])
Attachments
(1 file)
We want to partially localize monochromatic theme names. They have two parts: the color name and the variant name. For example, one color is "Abstract" and one variant is "Balanced". We want to localize just the variant name, so the theme appears in about:addons with a name like (using French as an example): Abstract – Balancé
.
Currently, we localize some theme names using a .properties file. Zibi thinks this is currently the only way to localize theme names, although work may be underway to support Fluent. Mardak points out that we could maybe add custom localization in bug 1729535, but I am concerned about maintainability in that case.
Review thread, for context: https://phabricator.services.mozilla.com/D125755#inline-692933
Assignee | ||
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Just mentioning for completeness, in case it helps:
WebExtensions (including themes) can have localized strings by bundling the translations in a _locales/
directory, as documented at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Internationalization
There are two downsides:
- The format doesn't use Fluent, so all supported translations would be bundled with one XPI file, and be checked in as part of m-c (search for
_locales/*/messages.json
for some existing examples in m-c). - All locales are loaded when the extension/theme starts for the first time, which results in slightly more overhead in the initialization/installation of the extension at the first run. The result is cached, but the cache is cleared when the Firefox version changes.
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
Updated•3 years ago
|
Comment 5•3 years ago
|
||
bugherder |
Description
•