Opened 12 months ago

Last modified 8 months ago

#32394 new defect

Update Progress Bar doesn't use translations

Reported by: Zarko_Gjurov Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-update, TorBrowserTeam202006
Cc: emmapeel, gk, ggus Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

While Tor Browser v9.0 (MK locale) is updating to v9.0.1 the Update Progress Bar doesn't use MK translation string(s).

https://i.ibb.co/Xxhx0Kd/Update-Progress-Bar-not-use-MK-translations.png

Child Tickets

Change History (12)

comment:1 Changed 12 months ago by gk

Component: Community/TranslationsApplications/Tor Browser
Owner: changed from emmapeel to tbb-team

comment:2 Changed 12 months ago by mcs

Summary: Update Progress Bar doesn't use MK translationsUpdate Progress Bar doesn't use translations

This is not specific to any one locale. The updater reads its UI strings from a file named updater.ini but that file does not contain translated strings in our Tor Browser builds. Unless I am mistaken, this bug has existed in Tor Browser for a long time: the method we use to create language-specific packages relies on including the correct Firefox ESR language pack, but the updater does not read strings from a language pack.

I am not sure how to obtain the correct updater.ini files; we will need to look at how those are generated during Firefox's localized builds.

Last edited 12 months ago by mcs (previous) (diff)

comment:3 Changed 12 months ago by gk

Keywords: tbb-update added

comment:4 Changed 12 months ago by mcs

It looks like updater.ini is translated directly in Mozilla's Pontoon system. See: https://pontoon.mozilla.org/mk/firefox/browser/updater/updater.ini/?string=79133

Doe anyone know how resources "flow" from Pontoon into Firefox? Maybe there is some intermediate place between Pontoon and the final packages where we could obtain the correct updater.ini files.

comment:5 Changed 12 months ago by sysrqb

Keywords: TorBrowserTeam201912 added

comment:6 Changed 11 months ago by Zarko_Gjurov

Probably should be taken over and directly integrated to Tor Project and to be put on Transifex for translating same as was with the case of "onboarding.properties".

comment:7 in reply to:  6 Changed 11 months ago by mcs

Replying to Zarko_Gjurov:

Probably should be taken over and directly integrated to Tor Project and to be put on Transifex for translating same as was with the case of "onboarding.properties".

I disagree. The reason we "took over" the onboarding properties is because Firefox no longer uses them. We would prefer to let Mozilla own the translation process for strings that are still used by Firefox.

comment:8 Changed 11 months ago by Zarko_Gjurov

I have said that because Mozilla from unknown reasons didn't include it in, even the string is translated more than 3 years ago. That was the strange thing.

comment:9 Changed 10 months ago by sysrqb

Keywords: TorBrowserTeam202001 added; TorBrowserTeam201912 removed

comment:10 Changed 8 months ago by pili

Keywords: TorBrowserTeam202002 added; TorBrowserTeam202001 removed

Moving tickets to February

comment:11 Changed 8 months ago by sysrqb

Deferring some more tickets from February 2020 to June 2020. Too many tickets, not enough time.

comment:12 Changed 8 months ago by sysrqb

Keywords: TorBrowserTeam202006 added; TorBrowserTeam202002 removed

Second attempt at deferring tickets until June.

Note: See TracTickets for help on using tickets.