Closed Bug 1486500 Opened 4 years ago Closed 4 years ago

[Translate.Next] Make the UI localizable

Categories

(Webtools Graveyard :: Pontoon, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: adrian, Assigned: adrian)

References

Details

Attachments

(1 file)

We will use Fluent as our localization technology. 

Language choice
===============

The language that will be presented to the user will be, in order: 
 1. the user's defined language (in the settings) if the user is logged in and they have entered it
 2. the result of a typical language negotiation algorithm (either from django-ftl or fluent-langneg)

Translation storage
===================

We will likely do what many other Mozilla projects do and have a separate repo in the mozilla-l10n github organization. See https://github.com/mozilla-l10n/

Though at first, we can start with having the translations in the pontoon repo, to make it easier to test. We can switch to a separate repo once we are ready to expose the strings on Pontoon.
Priority: P2 → P1
Status: NEW → ASSIGNED
Blocks: 1504695
Blocks: 1504698
Blocks: 1504702
Commit pushed to master at https://github.com/mozilla/pontoon

https://github.com/mozilla/pontoon/commit/4289abfc90750b7cdadaa793fc87b035ae327513
Fix bug 1486500 - Make the Translate UI localizable.  (#1113)

This lays the foundations for translating Pontoon's UI. It installs Fluent and fluent-react, marks current content as localizable, provides basic language negotiation (useful for testing, use the `custom homepage` setting), adds a mediocre French translation, and adds documentation about localization for developers. From this commit onwards, all new exposed content should be made localizable.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.