Open Bug 1454248 Opened 6 years ago Updated 4 years ago

Support the web extension json localization format as first-class citizen in our l10n toolchain

Categories

(Localization Infrastructure and Tools :: General, enhancement, P5)

Product:
Localization Infrastructure and Tools
Component:
General
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: Pike, Unassigned)

References

(
URL
)

Details

User Story

Work needs to happen on both pontoon and compare-locales.

compare-locales is needed for basic stats of translation completion, but also for linting localized files for builds.

pontoon is needed to edit the localized files, integrate the error checks from c-l, and create good localizer experience for the advanced features in messages.json.

Basic support:

TODO

Features to triage:

TODO
For web-extension projects, it'd be nice to support the browser.i18n l10n json format directly.

We'll need more phases here to actually do something, starting a user story to track that. I'll spend some actual work time on filling that out, not doing that on a Sunday. Filing a template bug to have something to link to.
Flags: needinfo?(l10n)
Flags: needinfo?(l10n)
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.