Open Bug 2087290 Opened 17 days ago Updated 16 days ago

Upstream the enterprise localization files

Categories

(Enterprise Products :: General, task)

Tracking

(Not tracked)

People

(Reporter: jmendez, Assigned: jmendez, NeedInfo)

References

(Blocks 1 open bug)

Details

Attachments

(1 external file)

Firefox Enterprise strings currently live in enterprise-specific Fluent files in enterprise-firefox and are translated in a separate enterprise-l10n Pontoon project, with syncing of the translations into mozilla-l10n/firefox-l10n at the same paths these files would have in mozilla-central. Enterprise l10n repacks then pick them up through browser/locales/enterprise-l10n-changesets.json.

This bug captures upstreaming all of the enterprise en-US localization files to mozilla-central together (without the code that uses them). Because of migration/mapping work that is necessary as strings move upstream, the l10n team has requested that the strings be moved in one batch rather than bit by bit with their features. The files include:

  • browser/locales/en-US/chrome/overrides/enterprise.properties
  • browser/locales/en-US/browser/enterprise/enterprise-policies-descriptions.ftl
  • dom/locales/en-US/chrome/enterprise.properties
  • toolkit/locales/en-US/toolkit/enterprise/enterprise.ftl
  • toolkit/locales/en-US/toolkit/enterprise/felt.ftl
  • toolkit/locales/en-US/crashreporter/crashreporter-enterprise.ftl
  • browser/branding/enterprise/locales/ (brand.ftl, brand.properties, jar.mn, moz.build), plus its entry in browser/locales/l10n.toml

The files should land complete and keep their current paths and message IDs, so the translations already in firefox-l10n match them.

This has to be coordinated with the l10n team, who will, at landing time:

  • move ownership of these files from the enterprise-l10n project to the Firefox project in Pontoon, reusing the existing translations;
  • turn off the enterprise-l10n to firefox-l10n sync, and later retire the enterprise-l10n repository;

Things to settle before landing:

  • These strings are currently translated for only a few locales. Once in mozilla-central they are exposed to every Firefox locale, so confirm with the l10n team that this is acceptable or how they can be isolated or prioritized.

After landing, mozilla-central owns all enterprise strings. New or changed enterprise strings must land in mozilla-central first (or at the same time) and be synced to enterprise-firefox, and the fork's copies of these files must stay identical to mozilla-central. Upstream Fluent rules apply from then on: a changed meaning needs a new ID, and moves or renames need a Fluent migration.

Note that this bug does not cover setting up upstream enterprise builds to consume the localized strings (e.g. the enterprise l10n repack configuration). That will be handled separately.

Firefox Enterprise strings are moved upstream in one batch, without the code
that uses them, keeping the paths and IDs already used by firefox-l10n so the
existing translations carry over.

Things to settle before landing:

  • These strings are currently translated for only a few locales. Once in mozilla-central they are exposed to every Firefox locale, so confirm with the l10n team that this is acceptable or how they can be isolated or prioritized.

[:bolsson] You had brought up this issue in our slack discussion. Is the exposure to all locales a concern/problem for the l10n team or were you pointing it out just for our own awareness? If we do care and want to keep the strings isolated to the few current locales, is there any means to do so with the strings upstreamed?

[:mkaply] If enterprise strings do get translated to other locales, is that a problem/concern for us as a product? I would guess the main reason we limited the exposure was to not waste people's time for locales we weren't marketing, but are there other reasons we actively would want to prevent this?

Flags: needinfo?(mozilla)
Flags: needinfo?(bolsson)
Flags: needinfo?(bolsson)

It was mostly pointing it our for your awareness. It's not a concern/problem for the l10n team, and not avoidable if enterprise is entering the main tree.

Depends on: 2087613
Assignee: nobody → jmendez
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: