Opened 3 years ago

Last modified 10 months ago

#17400 new task

Decide how to use the multi-lingual Tor Browser in the alpha/release series

Reported by: gk Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: ux-team, tbb-usability-stoppoint-wizard, TorBrowserTeam201608
Cc: mcs, brade, mikeperry, whonix-devel@…, ilv, isabela, linda, arthuredelstein Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Now that #12967 is fixed, we should decide on how we want to make use of a multi-lingual Tor Browser. For the hardened series we just ship one build with all locales. We could do that for the alpha and the release series as well but maybe there is a smarter way to strike the balance between usability (downloading just the localized bundle I want) and resource scarcity (hosting all the localized bundles on our infrastructure).

Mike had the idea a while ago to ship the most important bundles localized while putting all the other locales in a generic bundle (see: I think I like that idea. Is that still something we want?

Child Tickets

Change History (21)

comment:1 Changed 3 years ago by gk

Keywords: tbb-usability-stoppoint-wizard added; tbb-usability removed

comment:2 Changed 3 years ago by mcs

I assume the advantage of shipping packages for each locale is the smaller download size. But the impact of including many locales is not too high. Here is some data from some alpha builds I made yesterday:

locale-specific package:
63M tor-browser-linux64-5.5a3_ar.tar.xz
76M tor-browser-linux64-5.5a3_ar.mar

"ALL" package with 15 language packs:
67M tor-browser-linux64-5.5a3_ALL.tar.xz
82M tor-browser-linux64-5.5a3_ALL.mar

The size increase over a locale-specific package is about 4MB for the .tar.gz files and about 6MB for the complete MAR files. That does not seem bad at all. Should we just switch to the "ALL" package? Or are we planning to increase the number of Firefox language packs we ship?

We can greatly reduce the footprint on the web server and mirrors by producing multi-locale packages.

comment:3 Changed 3 years ago by gk

Keywords: TorBrowserTeam201511 added

comment:4 Changed 3 years ago by mcs

From #17616 (resolved as a duplicate of this ticket):

However, for better consistency and not breaking TBB downloaders in future, please consider producing also stable TBB bundles with language "ALL".

comment:5 Changed 3 years ago by proper

Cc: whonix-devel@… added

If you go for "ALL" bundles only, could you please consider adding web redirects from language specific links to to "ALL"? At least from "en-US" to "ALL"? This would help not breaking TBB downloaders.

comment:6 Changed 3 years ago by mikeperry

Keywords: TorBrowserTeam201512 added; TorBrowserTeam201511 removed

comment:7 Changed 2 years ago by gk

Keywords: TorBrowserTeam201601 added; TorBrowserTeam201512 removed

Tickets for Jan 2016.

comment:8 Changed 2 years ago by bugzilla

Great task! Solve all Localization problems in one ticket!
It is still being solved by IT industry for now ;)
But due to the security nature of the project there are some key moments that make a solution more definite:

  1. Tor Browser emulates some "common" browser to the web, and it's better for it to handle all locale-specific features of the web (not only language), because it is being built potentially for everyone (or not?).
  2. Fingerprinting problem leads project to bundle in future (?) Unicode fonts with it to be OS-independent (a lot of megabytes each).
  3. Best UI is MUI that can switch on the fly and has "same as system" option.
  4. Localized versions (Mozilla style) are needed anyways if you want people that know only one language to use it. Localized site, localized installer, localized app - no "select language" dialogs (in English!). MUI installer with OS language detection might be used.
  5. To reduce size TBB can download LPKs (xpi) from your site when user switches language in UI (and can restart automatically to apply), but users in restricted locations cannot switch this way.

Hope that differences in UI will not be exposed to the web - it's the main concern.

Last edited 23 months ago by bugzilla (previous) (diff)

comment:9 Changed 2 years ago by gk

Keywords: TorBrowserTeam201602 added; TorBrowserTeam201601 removed

Putting stuff on the radar for February.

comment:10 Changed 2 years ago by ilv

Cc: ilv@… added

comment:11 Changed 2 years ago by gk

Keywords: TorBrowserTeam201603 added; TorBrowserTeam201602 removed

comment:12 Changed 2 years ago by gk

Keywords: TorBrowserTeam201604 added; TorBrowserTeam201603 removed

comment:13 Changed 2 years ago by gk

Keywords: TorBrowserTeam201605 added; TorBrowserTeam201604 removed

Moving tickets

comment:14 Changed 2 years ago by gk

Keywords: TorBrowserTeam201606 added; TorBrowserTeam201605 removed

comment:15 Changed 2 years ago by gk

Keywords: TorBrowserTeam201607 added; TorBrowserTeam201606 removed

comment:16 Changed 2 years ago by isabela

Cc: ilv isabela added; ilv@… removed

comment:17 Changed 23 months ago by gk

Keywords: TorBrowserTeam201608 added; TorBrowserTeam201607 removed

Moving items to August 2016.

comment:18 Changed 15 months ago by gk

Cc: lnl added

comment:19 Changed 13 months ago by linda

Cc: linda added; lnl removed

comment:20 Changed 13 months ago by linda

Keywords: ux-team added

comment:21 Changed 10 months ago by arthuredelstein

Cc: arthuredelstein added
Note: See TracTickets for help on using tickets.