Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T18:15:33Zhttps://gitlab.torproject.org/legacy/trac/-/issues/33497Translation on metrics.torproject.org2020-06-13T18:15:33ZTracTranslation on metrics.torproject.orgI think it is necessary to have different translations of metrics.torproject.org.
There is an old closed ticket https://trac.torproject.org/projects/tor/ticket/20867 but there are still no translations except from https://exonerator.torp...I think it is necessary to have different translations of metrics.torproject.org.
There is an old closed ticket https://trac.torproject.org/projects/tor/ticket/20867 but there are still no translations except from https://exonerator.torproject.org/.
If we could take the content to the 'Tor Project Web' on transifex there would be volunteers for many languages which would translate it.
It's also not that much so i think one could translate the whole content in one day.
**Trac**:
**Username**: kucehttps://gitlab.torproject.org/legacy/trac/-/issues/33482Update about:tor donate string2020-06-16T01:11:26ZAntonelaantonela@torproject.orgUpdate about:tor donate stringSarah suggested:
"On about:Tor instead of “Keep Tor Strong” how about something like, “Tor is free to use because of donations from people like you. Donate Now.”?" [i like it! -steph]
I attached a mockup.Sarah suggested:
"On about:Tor instead of “Keep Tor Strong” how about something like, “Tor is free to use because of donations from people like you. Donate Now.”?" [i like it! -steph]
I attached a mockup.Mark SmithMark Smithhttps://gitlab.torproject.org/legacy/trac/-/issues/33306Consider mapping snowflake locales as we map the tor button and others2020-06-13T17:33:43ZemmapeelConsider mapping snowflake locales as we map the tor button and othersThe Tor Browser is based on Firefox ESR, and so it must use the locale mapping of firefox. But transifex mapping differs a bit. So we map this changes from transifex:
bn = bn-BD
en_GB = en-GB
en = en-US
es_AR = es-AR
es_CL = es-CL
es_CO...The Tor Browser is based on Firefox ESR, and so it must use the locale mapping of firefox. But transifex mapping differs a bit. So we map this changes from transifex:
bn = bn-BD
en_GB = en-GB
en = en-US
es_AR = es-AR
es_CL = es-CL
es_CO = es-CO
es = es-ES
es_MX = es-MX
fy = fy-NL
ga = ga-IE
gu = gu-IN
hi = hi-IN
hr_HR = hr-HR
hy = hy-AM
ms_MY = ms
nb = nb-NO
nn = nn-NO
nl_BE = nl-BE
pa = pa-IN
pt_BR = pt-BR
pt_PT = pt-PT
si_LK = si
sv = sv-SE
zh_CN = zh-CN
zh_HK = zh-HK
zh_TW = zh-TW
maybe Snowflake should be mapped with the same locales?Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/legacy/trac/-/issues/33146translations branches are not translating.2020-06-13T17:00:48Zemmapeeltranslations branches are not translating.The new translations builds jenkins is doing when there are changes in the translation files (#32746) do not show translations, see for example:
https://lektor-staging.torproject.org/community/translations/fr/
It seems the translation ...The new translations builds jenkins is doing when there are changes in the translation files (#32746) do not show translations, see for example:
https://lektor-staging.torproject.org/community/translations/fr/
It seems the translation files are not in place when the build starts, so the lektor install generates new files.
You can see lektor does not find the files, because it creates them instead of editing:
https://jenkins.torproject.org/job/lektor-website-support-translation-translation/15/consoleText
search for 'Created contents+ar.po.' (it should update instead of creating)HiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/32996trigger lektor/translations build when translation.git/[website] updates2020-06-13T17:00:24Zemmapeeltrigger lektor/translations build when translation.git/[website] updatesFor the work of translators, we have a staging site so they can review their work before publishing it (see parent ticket).
When there are updates in transifex, we get them in the repository
https://gitweb.torproject.org/translation.gi...For the work of translators, we have a staging site so they can review their work before publishing it (see parent ticket).
When there are updates in transifex, we get them in the repository
https://gitweb.torproject.org/translation.git/ [website]
where website can be support-portal, community, etc.
We need that jenkins builds then the branch /translations/ of the website repo, so the translatos can see their work and correct any errors.
So, any changes to https://gitweb.torproject.org/translation.git/commit/?h=support-portal should trigger the build of https://gitweb.torproject.org/project/web/support.git/log/?h=translations
any changes to https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot should trigger the build of https://gitweb.torproject.org/project/web/manual.git/log/?h=translations
any changes to https://gitweb.torproject.org/translation.git/commit/?h=communitytpo-contentspot should trigger the build of https://gitweb.torproject.org/project/web/community.git/log/?h=translations
https://gitweb.torproject.org/translation.git/commit/?h=tpo-web should trigger the build of https://gitweb.torproject.org/project/web/tpo.git/log/?h=translationsweasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/32762major networking issues on moly, affects: majus, fallax, web-cymru-01, build-...2020-06-13T16:59:57Zemmapeelmajor networking issues on moly, affects: majus, fallax, web-cymru-01, build-x86-05, build-x86-06hello:
something happened in https://db.torproject.org/machines.cgi?host=majus the translation server.
last night the last update happened, around 2019-12-15 23:55:01
and since then the translations are not getting updated.
i have ...hello:
something happened in https://db.torproject.org/machines.cgi?host=majus the translation server.
last night the last update happened, around 2019-12-15 23:55:01
and since then the translations are not getting updated.
i have entered on the server and i can ping to google.com, but i could not git clone https://github.com/transifex/transifex-client.git repository-git
and when i run the script at /srv/translation.torproject.org/tools/update_translations it just stays there waiting and cannot connect.
is it possible that some network functions cannot be performed?
the scripts and such are run under the translations user
please have a look as this is a pretty important repo for updates in translations and for the translators to review their work as well.anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/32746translations repo and jenkins: reduce builds2020-06-13T16:59:56Zemmapeeltranslations repo and jenkins: reduce buildsi have been thinking on how to use our resources more wisely regarding the translations and the websites.
THE PROBLEM
* At this moment we are building our websites many branches anew each time we push changes to our translations reposi...i have been thinking on how to use our resources more wisely regarding the translations and the websites.
THE PROBLEM
* At this moment we are building our websites many branches anew each time we push changes to our translations repository, even with languages still not enabled on production.
This results on a situation when, if there is people translating the support portal for example to Malayalam, which is still not published, and therefore making changes to the translation repository, the website is rebuild several times when there have been no actual changes to it (the pages for the actual website show still no Malayalam translations)
On the other hand, the quick updates are very useful for translators, and they use the staging version of the site a lot, learning to test their translations and thus fixing problems by themselves.
* The translations configuration gets on the way with the development process
It makes work on staging hard, because there are a lot of changes in the configuration files (databags/alternatives.ini, $website.lektorproject, .htaccess, configs/i18n.ini) that should not get in the production website.
The local and jenkins builds get longer, as people using staging will have to compile all this languages too.
* The content of the staging site gets outdated, and translators are translating newer content that is not updated on staging
As it is so hard to merge master changes to staging, the staging website gets outdated on other code and is not useful anymore as a quick preview site.
SOLUTION
So I propose to:
* new branches for translators, called translations, that get updated when the dedicated branch at https://gitweb.torproject.org/translation.git/ is updated, and follow master closely, differing from it only in changes to the configuration files (databags/alternatives.ini, $website.lektorproject, .htaccess, configs/i18n.ini).
* the following scheduling in lektor-jenkins-translation branches:
* master/staging/develop: when there is a change on this branches, we pull the new translations from the translation repo, and update all together
* translations: we rebuild when there are changes on the website repo, AND changes on the translation repo branch as well
If we want to update the translations in branches master/staging/develop, we should be able to do it simply by triggering a build from the web interface.
This way we can reduce the builds and make development less cumbersome, while also providing a quick preview of their changes to active translators.
We can also prevent accidentally publishing incomplete languages, or removing languages from the 'preview' website.
So, for this to be implemented we need to:
* Make sure that the 'translations' branches are updated when their corresponding branch at https://gitweb.torproject.org/translation.git/ gets updated.
* Stop building the master/develop/staging builds each time there is a commit in their corresponding https://gitweb.torproject.org/translation.git/ branch, and only build when a commit is pushed to lektor itself.
* Remove extra languages in staging and develop, and leave them only in translations.
Please let me know what you thinkemmapeelemmapeelhttps://gitlab.torproject.org/legacy/trac/-/issues/32602Consider what to do about locales used by very few people2020-06-13T17:33:40ZemmapeelConsider what to do about locales used by very few peopleWe give users an option to hide their locale and say they are using en-US as to decrease their fingerprint, but once in a while we can see some information may be leaked (ref: https://trac.torproject.org/projects/tor/query?status=!closed...We give users an option to hide their locale and say they are using en-US as to decrease their fingerprint, but once in a while we can see some information may be leaked (ref: https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~tbb-fingerprinting-locale).
I wonder if we should let users know about this?
Looking at the stats, specially the smaller numbers in Update pings at
https://metrics.torproject.org/webstats-tb-locale.csv
I wonder if maybe we should make users aware somehow about this? For example when in the download page:
warning: you are using a locale used by very few people and there are a couple of ways in which your locale may be leaked.
maybe we should also add a note about 'how do we know about this', maybe linking to the metrics page:
https://metrics.torproject.org/webstats-tb-locale.html
it sounds awful for a new translation to be published and get that, though :Semmapeelemmapeelhttps://gitlab.torproject.org/legacy/trac/-/issues/31861remove SSL observatory l10n resource2020-06-13T17:33:37Zemmapeelremove SSL observatory l10n resourceSSL Observatory has been removed from HTTPS Everywhere codebase, ref
https://github.com/EFForg/https-everywhere/pull/18408
so i should
- remove it from transifex
- move it from the translations repo to the attic.SSL Observatory has been removed from HTTPS Everywhere codebase, ref
https://github.com/EFForg/https-everywhere/pull/18408
so i should
- remove it from transifex
- move it from the translations repo to the attic.emmapeelemmapeelhttps://gitlab.torproject.org/legacy/trac/-/issues/31784move majus off of moly2020-06-13T16:59:02Zanarcatmove majus off of molyas part of an effort to reduce our dependence on an old server (moly), we should move majus (a non-redundant server) to a different host, probably the FSN* cluster.as part of an effort to reduce our dependence on an old server (moly), we should move majus (a non-redundant server) to a different host, probably the FSN* cluster.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/31384localize snowflake website2020-06-13T18:20:50Zemmapeellocalize snowflake websitehttps://snowflake.torproject.org/ should appear at least on our priority 12 languages.https://snowflake.torproject.org/ should appear at least on our priority 12 languages.Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/legacy/trac/-/issues/31368find new URLs for the Tor Browser translation components2020-06-16T01:06:11Zemmapeelfind new URLs for the Tor Browser translation componentswith the last changes on the Tor Browser code, some translation files have moved. I need to get their new addresses.
ref: https://gitweb.torproject.org/torbutton.git/commit/?id=8c5a555b50274aabf0498a2da39696e4cde77cf7with the last changes on the Tor Browser code, some translation files have moved. I need to get their new addresses.
ref: https://gitweb.torproject.org/torbutton.git/commit/?id=8c5a555b50274aabf0498a2da39696e4cde77cf7emmapeelemmapeelhttps://gitlab.torproject.org/legacy/trac/-/issues/31351localization orfoxRIP2020-06-16T01:06:09Zemmapeellocalization orfoxRIPthe sunsetting app needs to be localized. the file to localize seems to be
https://github.com/guardianproject/Orfox/blob/final-migrate-app/app/src/main/res/values/strings.xml
translations are available at https://gitweb.torproject.org...the sunsetting app needs to be localized. the file to localize seems to be
https://github.com/guardianproject/Orfox/blob/final-migrate-app/app/src/main/res/values/strings.xml
translations are available at https://gitweb.torproject.org/translation.git/tree/?h=orfox-stringsxml_completedemmapeelemmapeelhttps://gitlab.torproject.org/legacy/trac/-/issues/30678remove hardcoded capitalization from tpo css and templates2020-06-13T17:28:11Zemmapeelremove hardcoded capitalization from tpo css and templatesthis does not work well in many languages. capitalization should be on the string itself.
here some examples submitted by ecron (thanks!):
![Captura0.cleaned.PNG](uploads/Captura0.cleaned.PNG)
![Captura1.cleaned.PNG](uploads/Captur...this does not work well in many languages. capitalization should be on the string itself.
here some examples submitted by ecron (thanks!):
![Captura0.cleaned.PNG](uploads/Captura0.cleaned.PNG)
![Captura1.cleaned.PNG](uploads/Captura1.cleaned.PNG)
![Captura2.cleaned.PNG](uploads/Captura2.cleaned.PNG)
![Captura3.cleaned.PNG](uploads/Captura3.cleaned.PNG)HiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/30528please create a l10n mailing list2020-06-13T16:57:41Zemmapeelplease create a l10n mailing listit would be nice to have a mailing list for l10n issues.
can be called tor-l10n so it is in line with the irc channel.
i want to administer it and invite people to join the mailing list to know more about translations and also we could...it would be nice to have a mailing list for l10n issues.
can be called tor-l10n so it is in line with the irc channel.
i want to administer it and invite people to join the mailing list to know more about translations and also we could use the address for 'reporting errors on translations' or other things people wants to know.
It will be a public list.
Pili also thinks it is a good idea.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/legacy/trac/-/issues/30505Migrate Tor Browser locales to Fluent2020-06-16T01:03:49ZAlex CatarineuMigrate Tor Browser locales to FluentWe should probably try to migrate Tor-specific locales in Tor Browser (torbutton, tor-launcher, ...) to Fluent, the new Firefox localization system (https://firefox-source-docs.mozilla.org/intl/l10n/l10n/index.html)We should probably try to migrate Tor-specific locales in Tor Browser (torbutton, tor-launcher, ...) to Fluent, the new Firefox localization system (https://firefox-source-docs.mozilla.org/intl/l10n/l10n/index.html)https://gitlab.torproject.org/legacy/trac/-/issues/30447TBA strings are coming from a different branch each release, which makes it d...2020-06-16T01:03:35ZemmapeelTBA strings are coming from a different branch each release, which makes it difficult to track in transifexMost of the resources we have in Transifex are linked to source files we have on our own repositories, so when we make changes on our repositories, those changes appear automatically in Transifex.
This happens with all Torbutton strings,...Most of the resources we have in Transifex are linked to source files we have on our own repositories, so when we make changes on our repositories, those changes appear automatically in Transifex.
This happens with all Torbutton strings, coming mostly from the torbutton.git repository.
But the strings for Tor Browser for Android come from the Tor Browser repository, and the branch name is not 'master' but it is the release name, as in current branch is 'tor-browser-60.6.1esr-8.5-1'
This makes it impossible to track permanently the branch, somebody needs to login to transifex with enough privileges to change the autoupdate to the new URL, or do updates as part of the release cycle with the push feature of the tx client ( https://docs.transifex.com/client/push )https://gitlab.torproject.org/legacy/trac/-/issues/30310Snowflake localization2020-06-13T18:19:55ZCecylia BocovichSnowflake localizationWe should start localizing the user-facing parts of snowflake. Right now that is just the browser-based proxy, but eventually it will include the WebExtension version.We should start localizing the user-facing parts of snowflake. Right now that is just the browser-based proxy, but eventually it will include the WebExtension version.Arlo BreaultArlo Breaulthttps://gitlab.torproject.org/legacy/trac/-/issues/30074Clarify what is the plan with bn, bn-BD, bn-IN, that are now different versio...2020-06-13T17:33:35ZemmapeelClarify what is the plan with bn, bn-BD, bn-IN, that are now different versions in Mozilla l10nThere used to be a time when there was no bn in Mozilla. There was only bn-BD.
Now, there is bn, bn-BD, bn-IN.
* We only have bn in Transifex and most translators say 'it is almost the same'.
* We haven't got an alpha now because of #...There used to be a time when there was no bn in Mozilla. There was only bn-BD.
Now, there is bn, bn-BD, bn-IN.
* We only have bn in Transifex and most translators say 'it is almost the same'.
* We haven't got an alpha now because of #29257 but it will be called bn-BD
* The translators are quite active and our documentation is already translated, they are translating only one language as bn in Transifex.
This ticket is here to take a decision about that.emmapeelemmapeelhttps://gitlab.torproject.org/legacy/trac/-/issues/29940merges in transifex2020-06-13T17:33:32Zemmapeelmerges in transifexwe still need to merge some more language codes:
* hr and hr_HR: some mmiscommunication, translators need to agree on the merge and if they choose hr_HR we need to remap.
* es and es_ES: es_ES is dead, the real translation is at es in T...we still need to merge some more language codes:
* hr and hr_HR: some mmiscommunication, translators need to agree on the merge and if they choose hr_HR we need to remap.
* es and es_ES: es_ES is dead, the real translation is at es in Transifex, but we map it to es-ES in Torbutton branches
* pt and pt_PT should be merged?
Other cases still to define, maybe in other ticket:
* nl-BE has no locale in Mozilla, so we should not make translators translate TorBrowser to it.
* There is Mozilla locale for Swahili now!emmapeelemmapeel