Langpacks and repacks should include information about which strings/messages they're missing (if any)
Categories
(Release Engineering :: Release Automation, task)
Tracking
(Not tracked)
People
(Reporter: eemeli, Unassigned)
Details
The settings redesign currently includes a string like "Canadian English (en-CA) is 97% complete" as a part of the UI for fallback language selection. To produce that string, we'll need a count of the strings missing from each localization, along with a total count of localizable strings in Firefox. Later on, this information may also prove quite useful in simplifying how and when fallback actually happens.
This per-locale information is not currently available in our localization systems, as it depends on the exact commit from which the build happens, and the localization data includes strings from all active branches. We do track the strings included in the source locale, from which the total count can be derived (currently, 14023 strings).
The string in question is only displayed after the preferred UI language is selected, and so the locale-specific data could be included only in the langpack or repack, rather than being immediately available for all locales. We currently fetch the list of available localizations from AMO each time, but in practice it ~never changes after a version's initial build.
To compile the localizations, we call either moz.l10n.bin.build or moz.l10n.bin.build_file, which commands can be expanded to provide the data as a text file, but I'm not sure if further changes are required to ensure that it's available at runtime.
Description
•