Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tor-launcher
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • tor-launcher
  • Issues
  • #32636
Closed
Open
Issue created Nov 28, 2019 by Georg Koppen@gkDeveloper

Clean up locales shipped with Tor Launcher

Now that legacy/trac#29941 (moved) is basically fixed on the server-side we are getting all the new goodness with the next translations fetch. We should clean-up the locales we ship while doing so (removing the ones we don't support anymore etc.). Additionally, we should adapt all the scripts around translation update imports if that's needed. And, after checking everything is still working we need to backport the changes to a stable branch (as the locale updates that landed in 9.5a3 will ride the train).

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