Open Bug 1922245 Opened 1 month ago

Use moz.l10n build for l10n-merge

Categories

(Localization Infrastructure and Tools :: General, task)

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

Tracking

(Not tracked)

Status:
ASSIGNED

People

(Reporter: eemeli, Assigned: eemeli)

References

(Blocks 1 open bug)

Details

Currently, the l10n-merge build action ensures that the non-Fluent localizable content of the browser is complete for repacks and langpacks by copying the localized contents from firefox-l10n, and then filling out the .properties and .ini files with en-US values where they're missing from the localization. This mostly works, but has some issues that have been identified:

  • As the localizations are a combination of all the current Firefox branches (nightly, beta, release, ESRs), this means that messages not meant for the current build are also included.
  • If a localization is completely missing a Fluent file, no such file is included in the merged result. This leads to issues such as bug 1899255.
  • All comments are retained in the merged data.

All of the above will be resolved by using the moz.l10n build command instead of compare-locales.

You need to log in before you can comment on or make changes to this bug.