Setting up MY preferred language is impossible with Camino



14 years ago
14 years ago


(Reporter: xn--mlform-iua, Assigned: mikepinkerton)





14 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: 2005033112 (v0.8.3) Camino/0.8.3

In connection with this new version of Camino, version 0.8.3 (build 2005033112)
it was reported that as a great new thing that Camino now prefers web pages in
same language as the user interface language of Mac OS X.

While this is a very good as a _DEFAULT_ language value, it was very bad to, at
the same time remove --or not added-- options to select ones own preferred
language, like it is possible in Firefox and Mozilla Suite. 

Why? Simply because the OSX interface does not support all the languages in the

Reproducible: Always

Steps to Reproduce:

Actual Results:  
The new language preference implementation is supposed to make a better
impression on Mac users. And indeed, this is actually how Safari works also. But
if Camino is only going to be a replica of Safari, then I think we must say
that: we allready have Safari! And in fact, on reason why I do not like Safari
is that it does not let me specify my own languge. The Mac OS X only has very
few Interface languages. But what we are supposed to specify with the languge
preferences in the web browser is the _content_ language.

Expected Results:  
I expect to be able to select freely whichever language I want as my preferred
language. Plus I expect to be able to select freely alternative languages. Just
like Mozilla and Firefox let us do.

I will say that here a major web feature and thrusted Mozilla feature is broken!

Comment 1

14 years ago
This can be done with camino.accept_languages in user.js. Document on website

Comment 2

14 years ago
yep wontfix. you can still do it with the user,js changes always has been like that.
Last Resolved: 14 years ago
Resolution: --- → WONTFIX

Comment 3

14 years ago
But there need to be an interface for this. Even for Safari we may (I think)
fiddle with hidden preferences.

Comment 4

14 years ago
This bug reported asked for a interface.
Resolution: WONTFIX → ---
How about an entry on the website that addresses the possibility and how to
change it? I doubt it's work adding the interface as it seems a bit much. Maybe
as an addon/drop-in pref, but not by default.


Comment 6

14 years ago
I can't say how unbelievably unserious I find your suggestions about WONTFIX.

Why should this be so difficult? Firefox have this feature:

If this request gets a wontfix, then at least I am throughing Camino out of my
window, that's for sure. And I going to tell my share of the public, even they
arent't many, to do the same.

Comment 7

14 years ago
Saying you will use another browser is not effective and not appropriate for

You can do this with user.js and someone could very simply make a preference
pane that adds in to have an interface. Maybe it could even be a pane bundled
with the international version if enough people would actually want it.

Comment 8

14 years ago
Norway is a country with two languages, which both goes under the name
Norwegian. Norwegian has always been one of the supported languages of Apple.
There are 3 language codes for Norwegian: NO (for both languages), NN (for
Norwegian Nynorsk), NB (for Norwegian Bokmål). There are some other language
domains that are under the same situation.

There are two Norwegian versions of Google, one fore each language. But as you
can understand: Norwegian users want such a feature.

But I will give support you partly: it is on OS X system level this should have
been fixed. 

Perhaps one should/could wait till Mac OS X 10.4 is out to see if there are
improvements there ... 

And in the mean time I could encourage you all to open up Safari and use the
Report Bug to Apple for and tell them about the problem. 
This is an Apple error. You can set the value with user.js.

Last Resolved: 14 years ago14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.