Arora does not use translations

[David Planella]

Binary package hint: arora

I'm using the ca_ES.UTF-8 (Catalan language) on Kubuntu Karmic. Although there is a Catalan translation at:

/usr/share/arora/locale/ca.qm

The user interface doesn ot seem to pick it up and appears untranslated. I'm told that similar problems happen when using a different locale than the ones explicitly created there (i.e. when using German in Austria, de_AT, the fallback will not be de_DE and the UI will also be in English).

[Bruno (bruno666-666)]

Hi,
I'm using arora 0.8.0 from karmic repo. and I don't have this problem. My locale is fr_FR.UTF-_ and Arora is in French. If I choose to change application language to ca_ES it also works.

[Harald Sitter (apachelogger)]

fr_FR will work just fine, as will manually setting of a language (since the list will only offer available ones anyway).

Auto detection of de_AT as de_DE or fr_CA as fr_FR will fail though. Since Arora does not know about those locales, but only goes by language, so German is de_DE and nothing else. The operating system itself however differs between locales since de_AT might not always be the same as de_DE (this even more applies to French due to the former colonies). So the OS says "The user wants to use de_AT" and Arora goes like "Wha? Never heared of that, I'll give him en_US" while instead it should be "Too bad, I don't have translations for that locale, but I got de_DE, so we'll just use them for the time being".

So either there should be symlinks or a proper fallback algorithm needs to be implemented to make Arora fallback to super locales when no direct match is available.

[David Planella (dpm)]

After having tried it again, it works for me when I explicitly set up the language in the application.

I simply did not realise that I had to do the extra step,

Actually, I think this might be better split in two separate bugs:

* Arora does not use global settings for automatically setting the language
* Arora does not fall back to the same language code's locale when the country codes differ.

[Harald Sitter (apachelogger)]

Yep, splitting is a good idea, however looking at the locale folder, Arora seems to use the actual locale names, so ca.qm is just not the right name, it should be ca_ES I suppose. So generally Arora follows the global setting, but in case of ca the file name is just wrong.

[icefox (ben-meyerhome)]

I have tried to make some improvements to Arora based upon the comments in this thread. The improvements can be found in the Arora Git repository. Please let me know if there are other particular ways that I can improve the locale support in Arora. Unfortunately Qt does not provide an out of the box solution so we had to create a class to do this.

[Adi Roiban (adiroiban)]

I have this problem durring Karmic development stage, but now I can see that Arora is using the Spanish translations.

Is this still a problem in Karmic?

[David Planella (dpm)]

Lowering importance. Arora is not the default browser, and although in main, there are alternatives which are localised and use the standard gettext format.

I'd need to try on Lucid if this is still a problem, though.

[David Planella (dpm)]

If someone can confirm that Aurora is localized and translations are used in Lucid or in Maverick, I guess we can mark it as solved.