tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

commit b45cdc3df666457d4a031079e916b58ee0b67291
parent 210f169e9f2669590c9b0cd6f0c090f3112a4e9d
Author: Eemeli Aro <eemeli@gmail.com>
Date:   Tue, 25 Nov 2025 11:54:13 +0000

Bug 1996930 - Update Android localization docs r=android-reviewers,android-l10n-reviewers,flod,sfamisa

Differential Revision: https://phabricator.services.mozilla.com/D273782

Diffstat:
Mmobile/android/fenix/docs/Working-with-Strings.md | 9++++++---
1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/mobile/android/fenix/docs/Working-with-Strings.md b/mobile/android/fenix/docs/Working-with-Strings.md @@ -1,8 +1,12 @@ # Working with Strings +For additional documentation, +see the [android-l10n docs](https://mozilla-l10n.github.io/documentation/products/android-l10n/index.html) +and [Firefox Mobile L10N FAQs](https://mozilla-l10n.github.io/documentation/products/mobile/mobile_l10n_faqs.html). + ## Marking an unused string to be removed -Removing strings manually could cause crashes in **Beta** and **Release** versions 💥 , as the removed strings could be [uplifted to release branches](https://github.com/mozilla-mobile/fenix/pull/20364) by mistake, where strings are still needed. For this reason, we need a special process to remove them. +Removing strings manually could cause crashes in **Beta** and **Release** versions 💥 , as the removed strings could be uplifted to release branches by mistake, where strings are still needed. For this reason, we need a special process to remove them. Any landed string that is not removed while in development in Nightly will persist through 3 Firefox releases (Nightly, Beta, Release) before we can remove them from our code base. For example, if you want to remove a string that has already shipped prior to **Firefox Nightly 93**, the same string will still be in-use in **Firefox Beta 92** and **Firefox Release 91**. This means the string will be marked as unused and removed in 93 while still riding the train, and it can be removed safely when **Firefox Release 93** no longer ships, for instance, **Firefox Release 94** and beyond. @@ -14,7 +18,6 @@ To keep us safe when you want to remove strings from nightly: ```xml <string name="onboarding_close" moz:removedIn="93" tools:ignore="UnusedResources">Close</string> ``` -Example PR https://github.com/mozilla-mobile/fenix/pull/20980. ## When to remove an unused string and how @@ -22,7 +25,7 @@ Strings that have been tagged with `moz:removedIn` attributes are safe to be rem Consult the [Firefox release calendar](https://wiki.mozilla.org/Release_Management/Calendar). Let's say the Beta cut just happened and we are at Firefox Nightly 109, Firefox Beta 108 and Firefox Release 107. Everything marked with `moz:removedIn` <= 106 can now be removed. -You only need to remove the en-US strings within [values/strings.xml](https://searchfox.org/mozilla-mobile/source/fenix/app/src/main/res/values/strings.xml), and this change will propagate to the other locales. +You only need to remove the en-US strings within [values/strings.xml](https://searchfox.org/firefox-main/source/mobile/android/fenix/app/src/main/res/values/strings.xml), and this change will propagate to the other locales. ## Future