Open Bug 1726586 Opened 5 years ago Updated 2 months ago

Switch from ja-JP-mac to ja-JP-macos to make it a valid BCP-47 Language Tag

Categories

(Localization Infrastructure and Tools :: Administration / Setup, defect)

defect

Tracking

(Not tracked)

People

(Reporter: zbraniecki, Unassigned)

References

Details

At the moment we use invalid BCP-47 Language Tag for the macos variant of ja-JP locale.

It causes minor papercuts when interacting with a valid BCP-47 system, and we keep Firefox Platform as such.

It would be nice to clean this wrinkle.

See Also: → 1726535

We have a lot of in-tree places to fix: https://searchfox.org/mozilla-central/search?q=ja-JP-mac&path=

We have references in braindump, shipit, gecko-strings, gecko-strings-quarantine, balrog. This may not be an exhaustive list.

We will likely need to somehow provide updates for existing ja-JP-mac installs to update to ja-JP-macos; this will likely be a balrog watershed.

A number of these services are for all branches, while an in-tree patch will only land on Central; we'll either need to uplift to all release branches quickly and then update the services, or we'll have to figure out a way to support both ja-JP-mac and ja-JP-macos concurrently until all release trains have updated. We'll still need to support ja-JP-mac in Balrog for existing installs of older Firefoxes.

Not a trivial request by any means, but doable. We can weigh benefits vs costs.

See Also: → 2053908
You need to log in before you can comment on or make changes to this bug.