Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #17400

Closed (moved)
(moved)
Open
Created Oct 21, 2015 by Georg Koppen@gk

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

Now that #12967 (moved) 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: http://meetbot.debian.net/tor-dev/2015/tor-dev.2015-08-10-18.01.log.txt). I think I like that idea. Is that still something we want?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking