mozilla-l10n/android-l10n

Add Lockbox to Shared Android L10n System

Closed this issue · 3 comments

devinreams commented

Please add a new Android project to the cross-product Android localization repository (this repository).

Product in shared l10n system

We've read the documentation on the mana and would like to use

Separate files

Our strings.xml file gets its own copy in this repository.

We'll ask to unify that file across versions from master and release branches, allowing for dot releases to be shipped from these localizations, including l10n updates.

https://github.com/mozilla-lockbox/lockbox-android/blob/master/app/src/main/res/values/strings.xml

First steps taken

https://github.com/mozilla-l10n/android-l10n/projects/6

  • Our technical string review was tracked in mozilla-lockwise/lockwise-android#204. That's where we make sure strings have comments to explain parameters to localizers and ambiguous strings are clarified.
  • There was then a copy-review completed tracked in mozilla-lockwise/lockwise-android#248
  • We've maintained strings with translator comments since then
  • Our initial target market and locale list is matches Firefox's priority locales including:
    • French
    • German
    • Spanish
    • Italian
  • The l10n infrastructure integration tracking is here: mozilla-lockwise/lockwise-android#519
devinreams commented

Current usage metrics from Play Store:

image

To help prioritize the languages for translation (added Italian to initial requirements in addition to French, German, Spanish).

Any additions or considerations at this time @sandysage?

Delphine commented

Thanks so much for filing this :)
While we wait for the final fixes to strings to get into #579 (needed in order to expose strings on Pontoon), could you let us know what your release cadence and timeline currently look like? thanks!

devinreams commented

We are planning releases every 2 weeks (or so) to match our sprint cadence (end sprint, QA, then release).

Based on our current backlog, we are not expecting to implement a language picker and be “ready” for translations for at least 1 month (2 sprints).