There is some language files for Opera on its site: http://opera.com/download/languagefiles/ If there IS language files, why does not Opera's ebuild provide them? No matter what your LINGUAS is - only english language file will be installed. Opera's ebuild should download language files based on the LINGUAS variable just like OOo, Firefox etc. do. No, I don't know how to do this - I'm just a whining bastard.
I like the idea and I have played around with an adapted ebuild that uses LINGUAS to download selected .lng files from [1] and install them in /opt/opera/share/opera/locale, which is quite trivial to achieve, yet that is about all the ebuild can properly do. Opera does not automatically select a UI language for $USER, and neither does the ebuild - it would be improper for the ebuild to edit $HOME/.opera/opera6.ini for every $USER. I do however think axxo might still want to comment on your enhancement proposal. [1] http://www.opera.com/download/languagefiles/
I was about to submit a bug requesting this, so, instead of submitting a duplicate, I will ask here: please add this feature. :) The ebuild should download and install the language files (like Firefox ebuild does). The user is responsible to change the language file (like in Firefox). The ebuild can, however, print an EINFO explaining where the language files were stored. Nothing more than that.
Created attachment 97984 [details] opera-lng-9.01.ebuild An ebuild for a new package (I suggest www-client/opera-lng) that installs .lng files for LINGUAS. Please feel free to test, improve, and comment.
I am closing this bug because of the complete lack of interest this bug has attracted in the last few months (since I posted the attached ebuild).
Too bad... Firefox already has LINGUAS support on its "main" ebuild (no extra ebuild necessary). Too bad no developer wanted to take a look at this. Maybe all of them use Firefox... :-P
(In reply to comment #5) > Too bad... Firefox already has LINGUAS support on its "main" ebuild (no extra > ebuild necessary). Too bad no developer wanted to take a look at this. Maybe > all of them use Firefox... :-P Er, you don't understand. I happen to be a developer and I did take a look at the problem, I proposed a solution and worked out an ebuild, then nobody responded for months on end. Recap: maintaining opera-lng will be a bit more of a hassle than maintaining LINGUAS for firefox is, because Opera is slacking in updating lng files with every new Opera release, so you may end up with, say, Opera 9.02 and with a 9.01 lng file, which usually works well enough but does pose an ebuild maintainance problem, as the Gentoo maintainer would have to monitor [1] frequently (weekly or just when yet another bug is filed?) for changes of available languages against Opera versions and update the opera-lng ebuilds accordingly. If only Opera would enforce lng file updates with new Opera versions, this[2] wouldn't be such a chore. [1] http://www.opera.com/download/languagefiles/?platform=linux [2] I.e. editing several opera-lng ebuilds to update the LANGS variable in each.
*** Bug 171762 has been marked as a duplicate of this bug. ***
I'm looking at an opera 9.50 beta2 build 1971 snapshot which includes lng files in SRC_URI, so this is looking very promising now.
I filed Opera bug #331638 to get the zh-* languages in line with the rest of them (i.e. to follow the pattern of ll-CC so that the ebuild doesn't need to perform odd tolower/toupper (or as it is going to be now, to use find -iname <foo> for that purpose).
Comment on attachment 97984 [details] opera-lng-9.01.ebuild This will no longer be needed.
www-client/opera-9.50_beta2_p1971-r1 implements the new scheme: [ebuild R ] www-client/opera-9.50_beta2_p1971 USE="qt-static spell -gnome" LINGUAS="en en_GB nl -be -bg -cs -da -de -el -es_ES -es_LA -fi -fr -fr_CA -fy -hi -hr -hu -it -ja -ka -ko -lt -mk -nb -nn -pl -pt -pt_BR -ru -sv -tr -zh_CN -zh_TW" 0 kB It will be available soon in a Portage tree near you.
