Opened 9 years ago

Closed 8 years ago

#2549 closed enhancement (fixed)

new translations ready?

Reported by: arma Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version:
Severity: Keywords:
Cc: runa, erinn, chiiph, edmanm@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arma)

http://www.transifex.net/projects/p/torproject/resource/vidalia-vidalia-pot/ and http://www.transifex.net/projects/p/torproject/resource/vidalia-qt-pot/ look like there are some languages, like Greek, that are ready to enable in Vidalia.

In the past we had to explicitly enable a language in Vidalia, so it doesn't offer it in the drop-down box in the Settings Appearance window if only 7% of the strings are translated.

A) Runa, are the transifex translations up-to-date in the Vidalia repository?

B) Runa, is there anything else we should know about the Transifex side?

C) It looks like pkg/win32/CMakeLists.txt is where we choose what languages to use in the installer.

C') Erinn, It looks like Vidalia makes Chinese WXL files, whatever those are, but building of the Chinese NSIS files is commented out. Is that something we should fix?

D) Where in the code does it declare which languages are supported in the Vidalia interface? Is that also part of pkg/win32/, or am I just not finding the right place?

E) What about the translated help files? Is there some separate mechanism by which we declare which of those get offered to the users and which aren't ready yet, or is that decision made automatically when we decide which interface languages to offer?

Child Tickets

Change History (4)

comment:1 Changed 9 years ago by edmanm

Cc: edmanm@… added

C) Sort of. vidalia.nsi.in and vidalia-bundle.nsi.in are where the language files are actually included. The CMakeLists.txt file only determines which .po files get converted to .nsh files.

C') .wxl files are translations for WiX, which is what we use to generate a .msi installer. The Chinese translations were commented out due to charset limitations in NSIS. If NSIS supports UTF-8 now, that'd make life much easier.

D) See src/vidalia/LanguageSupport.cpp.

E) See src/vidalia/help/content/content.qrc. The language displayed in the help browser is determined at runtime on a page-by-page basis. If there exists a translated version of a requested help file in the user's current UI language, then it is displayed. Otherwise, the English version is displayed. To add a translated help file, add it to the content.qrc file.

comment:2 Changed 9 years ago by arma

Description: modified (diff)

comment:3 Changed 9 years ago by runa

A) Yes, I pulled new translations just now.

B) Not related to Vidalia. I'll write a document explaining how the translation process works.

comment:4 Changed 8 years ago by chiiph

Resolution: fixed
Status: newclosed

We can consider this done. Vidalia 0.2.17 applies the agreed policy to add/remove translations.

Note: See TracTickets for help on using tickets.