The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2024-03-26T20:59:30Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42214Fluent migration: security level2024-03-26T20:59:30ZhenryFluent migration: security levelMigrate "securityLevel.properties" to Fluent.Migrate "securityLevel.properties" to Fluent.henryhenryhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42305(Semi-)Automatically merge translation resources across tor browser releases ...2024-03-26T20:31:08Zhenry(Semi-)Automatically merge translation resources across tor browser releases (desktop)/cc @emmapeel @pierov
When I had my time offline the week before last I wrote a script to which takes a `tor-browser` or `firefox-android` translation file (`.dtd`, `.properties`, `.ftl`, or android `.xml`), and a new and an old branch.../cc @emmapeel @pierov
When I had my time offline the week before last I wrote a script to which takes a `tor-browser` or `firefox-android` translation file (`.dtd`, `.properties`, `.ftl`, or android `.xml`), and a new and an old branch name, and merges the versions found in both branches together with a comment added for strings that will be dropped at the next release. Here is the initial draft of the script if you want a quick look: [combine-translation-versions.py](/uploads/83cf1424566cf3b3222e6a60682bcc56/combine-translation-versions.py)
We could use the output as the `en-US` source files for weblate, combining both the strings needed for the next release as well as for the current stable release. The idea being that in tor-browser we can stop trying to maintain all the old strings in the current development branch that are still needed for the current stable release. And we can avoid having to manual clean ups of old strings, like in https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42221.
E.g., if we have `tor-browser.ftl` in tor-browser-xxx-13.5 with the content
```
string1 = String 1
new-string = New String
string2 = String 2
```
and in tor-browser-xxx-13.0 with the content
```
old-string = Old String
string1 = String 1
string2 = String 2
```
the script would output
```
string1 = String 1
new-string = New String
string2 = String 2
## Will be unused in Tor Browser 13.5!
old-string = Old String
```
The reason I add the comment is to provide a little notification to weblate translators in the "Source string description" to let them know that a string has a short lifetime. Weblate doesn't support descriptions for `.dtd` though so it won't work for that format.
@emmapeel and @pierov what do you think? And where would we want to run this script?
I guess we basically want to merge the translations files from both the branch used for current nightly and current stable. I'm not sure if this can be automatically pulled from `tor-browser-build` in a convenient way, or whether we would need some manual input.henryhenryhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42209Fluent migration: tor circuit2024-03-26T13:41:53ZhenryFluent migration: tor circuitMigrate tor circuit strings found in "torbutton.dtd" and "torbutton.properties" to Fluent.Migrate tor circuit strings found in "torbutton.dtd" and "torbutton.properties" to Fluent.henryhenryhttps://gitlab.torproject.org/tpo/ux/research/-/issues/22Share new material with community members to collect feedback about localized...2024-03-26T00:03:06ZGabagaba@torproject.orgShare new material with community members to collect feedback about localized versions- [x] Share the material worked during Sponsor 9, with members of the community.
- training materials
- outreach: Tor for Anti-censorship, Tor for Feminists, Tor for Human Rights, Tor for Privacy
- [x] Collect feedback about localiz...- [x] Share the material worked during Sponsor 9, with members of the community.
- training materials
- outreach: Tor for Anti-censorship, Tor for Feminists, Tor for Human Rights, Tor for Privacy
- [x] Collect feedback about localized versions.Sponsor 9 - Phase 5 - Usability and Community Intervention on Support for Democracy and Human RightsNahNahhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42203Fluent migration: about dialog2024-03-21T13:33:26ZhenryFluent migration: about dialogMigrate "aboutDialog.dtd" to Fluent.Migrate "aboutDialog.dtd" to Fluent.henryhenryhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42211Fluent migration: new identity2024-03-21T09:57:00ZhenryFluent migration: new identityMigrate "newIdentity.properties" to Fluent.Migrate "newIdentity.properties" to Fluent.henryhenryhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42335Do not localize the order of locales for app lang2024-03-20T09:00:09ZThorinDo not localize the order of locales for app langit currently goes
- `<localized name>` `lt`
- `<localized name>` `my`
- `<localized name>` `mk`
- `<localized name>` `ms`
- `<localized name>` `nb-NO`
it should be mk, ms, _then_ my
cc: @pierovit currently goes
- `<localized name>` `lt`
- `<localized name>` `my`
- `<localized name>` `mk`
- `<localized name>` `ms`
- `<localized name>` `nb-NO`
it should be mk, ms, _then_ my
cc: @pierovPier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42442Remove unused setting strings2024-03-13T16:45:02ZhenryRemove unused setting stringsNow that we have the CI from https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42305 in place, we can just remove the old settings strings unused since https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues...Now that we have the CI from https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42305 in place, we can just remove the old settings strings unused since https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42036 from our daily branch, and they should be kept around as long as they are needed in the stable build.henryhenryhttps://gitlab.torproject.org/tpo/web/community/-/issues/338User stories category names need to be made translatable2024-03-12T18:00:42ZemmapeelUser stories category names need to be made translatableIt seems the category names for the User Stories are not reaching the translation files. We should allow for translation.It seems the category names for the User Stories are not reaching the translation files. We should allow for translation.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/manual/-/issues/156New translations available for the manual: tk, ja2024-03-07T16:56:04ZemmapeelNew translations available for the manual: tk, jaThe manual can be released to Turkmen and Japanese, they are 100% translated.The manual can be released to Turkmen and Japanese, they are 100% translated.emmapeelemmapeelhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42221Remove legacy strings (13.0)2024-03-05T17:11:58ZhenryRemove legacy strings (13.0)We have a few old strings hanging around that are unused in any of our current releases (13.0 stable, or 13.5 alpha).We have a few old strings hanging around that are unused in any of our current releases (13.0 stable, or 13.5 alpha).henryhenryhttps://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/52Translate GetTor messages2024-02-27T18:20:31ZtraumschuleTranslate GetTor messagesThis is the parent ticket to translate GetTor into more languages, especially for censored areas.This is the parent ticket to translate GetTor into more languages, especially for censored areas.Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibetmeskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42423Move temporary Lox Fluent strings to new file2024-02-22T12:53:35ZhenryMove temporary Lox Fluent strings to new fileThe Lox invite dialog is due to be re-designed in https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42385
We should move the temporary strings to a new Fluent file so they don't end up on weblate.The Lox invite dialog is due to be re-designed in https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42385
We should move the temporary strings to a new Fluent file so they don't end up on weblate.henryhenryhttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40130Fix OnionShare weblate-git setup2024-02-15T16:17:15ZemmapeelFix OnionShare weblate-git setupWeblate has improved their merge requests since we setup the onionshare repository, and we can use github merge requests now.
We can fix the setup because it runs into conflicts pretty often.
https://hosted.weblate.org/settings/onionsh...Weblate has improved their merge requests since we setup the onionshare repository, and we can use github merge requests now.
We can fix the setup because it runs into conflicts pretty often.
https://hosted.weblate.org/settings/onionshare/translations/emmapeelemmapeelhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42402Remove Android YEC strings2024-02-08T09:18:22ZPier Angelo VendrameRemove Android YEC stringsIn firefox-android!58 I missed the strings. We should remove them.
Desktop strings have already been removed.In firefox-android!58 I missed the strings. We should remove them.
Desktop strings have already been removed.Pier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40129Move default Tor Browser component in Weblate2024-01-31T14:37:10ZemmapeelMove default Tor Browser component in WeblateTor Browser devs are removing the old properties and dtd files and adding more strings to the Fluent files.
In Weblate, when several files to translate are on the same branch, you can use one component as an internal weblate repo, as th...Tor Browser devs are removing the old properties and dtd files and adding more strings to the Fluent files.
In Weblate, when several files to translate are on the same branch, you can use one component as an internal weblate repo, as this saves resources and space.
For the Tor Browser, many components are tied to the \`aboutDialog.dtd\` component, but this file will dissapper eventually, so I need to choose another default file (tor-browser.ftl) and tie the rest of the components to it.Sponsor 9 - Phase 7 - Usability and Community Intervention on Support for Democracy and Human Rightsemmapeelemmapeelhttps://gitlab.torproject.org/tpo/web/community/-/issues/333More translations are ready2024-01-31T14:36:49ZemmapeelMore translations are readyWe can release some more translations for the community portal:
* Persian ![weblate status](https://hosted.weblate.org/widget/tor/community-portal/fa/svg-badge.svg)
* Swahili ![weblate status](https://hosted.weblate.org/widget/tor/commu...We can release some more translations for the community portal:
* Persian ![weblate status](https://hosted.weblate.org/widget/tor/community-portal/fa/svg-badge.svg)
* Swahili ![weblate status](https://hosted.weblate.org/widget/tor/community-portal/sw/svg-badge.svg)
* German ![weblate status](https://hosted.weblate.org/widget/tor/community-portal/de/svg-badge.svg)
* French ![weblate status](https://hosted.weblate.org/widget/tor/community-portal/fr/svg-badge.svg)
* Romanian ![Romanian](https://hosted.weblate.org/widget/tor/community-portal/ro/svg-badge.svg)
This translations are not complete, but they have active translators and will be completed soon (especially if we release the translation)
We have talked with @gus about allowing the community portal, as is so big and has very different sections, to be published even when translations are not complete. Hopefully this availability will make the community contribute to the translation, but in the case of the community portal, volunteer translators get discouraged cause is so big, and some sections are quite technical.emmapeelemmapeelhttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40031More automatic stats2024-01-24T15:33:58ZemmapeelMore automatic statsI spend lots of time reviewing the status of translation for several languages.
I should automate this process better. One way can be through the [stats Arthur Edelstein](https://torpat.ch) kindly provides to us, other with my dirty pyt...I spend lots of time reviewing the status of translation for several languages.
I should automate this process better. One way can be through the [stats Arthur Edelstein](https://torpat.ch) kindly provides to us, other with my dirty python scripts.
We should have automatically updated and easily available stats of:
* [x] Situation for one language across projects, with priorities. Useful for when somebody asks: I speak $language, where should I start?
* [ ] Completed or almost completed (from 90% in big websites) translations in need of review. Grouped by languages, but all in one page. Useful for reviewers to decide where to work on.
* [x] Published translations that have untranslated updates (i.e. changes on the Tor Browser Manual that need to be translated on the published languages.
If this stats get automatically updated it provide more autonomy to the language groups and coordinators to direct their efforts, will help developers and stakeholders to see the work that needs to be done for a language to be 'complete', and will leave me time for nicer/more productive endeavors.
They are generated by gitlab pagesemmapeelemmapeelhttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40116Correct name for Arabic language for menus, from عربية to العربية2024-01-24T12:47:08ZemmapeelCorrect name for Arabic language for menus, from عربية to العربيةWe are not writing the Arabic language word well on our menus. We need to change it in Lektor and our docs at least.
The Tor Browser uses Mozilla l10n name and it is correct.We are not writing the Arabic language word well on our menus. We need to change it in Lektor and our docs at least.
The Tor Browser uses Mozilla l10n name and it is correct.emmapeelemmapeelhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41300[gitlab] Mirror the mullvad-browser branch from community/crowdin/ to transla...2024-01-18T17:01:39Zemmapeel[gitlab] Mirror the mullvad-browser branch from community/crowdin/ to translation/The translations for the Mullvad Browser are done in Crowdin.
I have linked the crowdin bot with the repository:
https://gitlab.torproject.org/tpo/community/crowdin/
The bot is accessing with an Access Token and pushes to the branch ...The translations for the Mullvad Browser are done in Crowdin.
I have linked the crowdin bot with the repository:
https://gitlab.torproject.org/tpo/community/crowdin/
The bot is accessing with an Access Token and pushes to the branch l10n_mullvad-browser, and makes a merge request to mullvad-browser.
I gave this bot its own repository because to be setup Crowdin wanted total access to the repository, and I didnt wanted it to have such access on the translation repository.
I tried to setup mirroring on the mullvad-browser branch, but I was unable.
I need help to make the mullvad-browser branch at https://gitlab.torproject.org/tpo/community/crowdin/ push to the same branch in https://gitlab.torproject.org/tpo/translation/
I wish it could be done with a pull request from https://gitlab.torproject.org/tpo/translation/ (an option I was unable to select), so the mantainers of the crowdin repo (like the bot) do not have merge/push rights in the tpo/translation repo.anarcatanarcat