Several locales for torbutton in Transifex are fully or almost fully translated, but we aren't including these in our ./import_translations.sh script in torbutton.
And we would probably like to release some of these as Tor Browsers as well.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
Trac: Description: Several locales for torbutton in Transifex are fully or almost fully translated, but we aren't including these in our ./import_translations.sh script in torbutton.
to
Several locales for torbutton in Transifex are fully or almost fully translated, but we aren't including these in our ./import_translations.sh script in torbutton.
And we would probably like to release some of these as Tor Browsers as well.
During today's localization AMA, Roger suggested that we ship a nightly Tor Browser build that includes all available translations. Doing so would provide a way for translators to check their work before a Tor Browser that includes a new language is available.
During today's localization AMA, Roger suggested that we ship a nightly Tor Browser build that includes all available translations. Doing so would provide a way for translators to check their work before a Tor Browser that includes a new language is available.
Several locales for torbutton in Transifex are fully or almost fully translated, but we aren't including these in our ./import_translations.sh script in torbutton.
And we would probably like to release some of these as Tor Browsers as well.
Arthur (or Colin): which locales are fully or almost fully translated, yet we don't have Tor Browser versions of them?
Even if we have to do a "popular languages are on the main download page" and "less popular language are tucked away over here" division for good user experience, we should make the builds for the people who want those languages.
Adding the ux-team keyword so Linda et al can say "wait, you have other languages available, and the only thing left is to do the builds? yes, we should do that."
Or she can say something different if she prefers. :)
The following languages have enough completion (Tor Button and Launcher) for a Tor Browser, and have support in Firefox-ESR:
Albanian, Shqip Basque, Euskara Bulgarian, Български Catalan, Català Czech, Čeština Danish, Dansk English (British) Estonian, Eesti keel Finnish, suomi Greek, Ελληνικά Hungarian, magyar Icelandic, íslenska Indonesian, Bahasa Indonesia Latvian, LatviešuLithuanian, lietuvių kalba Norwegian (Bokmål), Norsk bokmål Romanian, Română Slovak, slovenčina Swedish, SvenskaUkrainian, Українська
The following are languages that have partial support for our components, and full Firefox-ESR support:
Azerbaijani, AzərbaycancaCroatian, HrvatskiHebrew, עברית Malay, Melayu Norwegian (Nynorsk), Norsk nynorsk Serbian, Српски Slovenian, Slovenščina Thai, ไทย Welsh, Cymraeg
Several locales for torbutton in Transifex are fully or almost fully translated, but we aren't including these in our ./import_translations.sh script in torbutton.
And we would probably like to release some of these as Tor Browsers as well.
Arthur (or Colin): which locales are fully or almost fully translated, yet we don't have Tor Browser versions of them?
Even if we have to do a "popular languages are on the main download page" and "less popular language are tucked away over here" division for good user experience, we should make the builds for the people who want those languages.
Just adding a note to ensure that our Irish translation (ISO 639 "ga") doesn't fall through the tracks, since we're not included in the list of potential locales above. We're translated/reviewed to 100% in Transifex in all Tor projects, and have support in Firefox-ESR (all versions back to FF1.0). Anything I can do to help move this forward? Even short of a full release, a nightly build so we can test the localisation would be a big help.
"Macedonian, Македонски" should be added to the "completed" list. Latest release of Moxilla Firefox ESR is confirmed available and Tor Project resources associated with Tor Browser have been translated.
Is there any progress on making all of the above languages available? If new languages cannot be realistically added to Tor Browser, we may want to consider halting all contributions to languages not currently supported.
I created an auto-updating page that lets us see what extra locales are available for Tor Browser:
https://torpat.ch/locales
Right now, the list of possible new locales with 100% coverage (in tor-launcher and torbutton) are:
bg, bn-BD, ca, da, en-GB, fr-CA, ga, he, id, lv, mk, nb, pt, ro, sv, zh-TW
I'd like to propose adding these, with the exception of en-GB, fr-CA, and pt which are probably well-enough covered by en-US, fr, and pt-BR respectively. So the list would be:
bg, bn-BD, ca, da, ga, he, id, lv, mk, nb, ro, sv, zh-TW
What do you mean with "adding these"? I think, again, #17400 (moved) is important here. To get some locales of your list added to the current list of bundles we ship I think doing the following in that order is not unreasonable:
Find out how many disk space we have available for additional locales (don't forget our mirrors)
Find out how many additional bytes Fastly is willing to serve to our users
[For 1) and 2) keep in mind that Win64 bundles are supposed to be stable later this year and that Android apks are planned as well]
Order the list you have using some metric so that the N locales we add are most helpful (in case N would be smaller than the amount of items we currently have)
The first two patches look good. I merged them to master (in Torbutton's case commit 46c71b6a528e70386fb8165f7d1507615d1a2a47 and in Tor Launcher's case commit f34580ab7e70487e5c97c67969326111ac00d074)
I think the other two need revision because there is no sv lang pack Mozilla ships, rather sv-SE. The bundle name should match that I think.
Trac: Status: needs_review to needs_revision Keywords: TorBrowserTeam201806R deleted, TorBrowserTeam201806 added
20628+1 looks good to me. I merged it to master (in our tor-browser-build repo) with commit b39dad476f870b60d7008c1e22e477dc80875c38 and we'll pick up the webml change once we update the website.
Trac: Resolution: N/Ato fixed Status: needs_revision to closed