Thread:Extension talk:UniversalLanguageSelector/How Does this tool interact with accpet-language and what the user chooses with the tool

I upgraded to 1.20.2 and installed the latest "Language Extension Bundle"

I set the Accept-Header in my browser to "fr" (verified with firebug).

By default I see the english version of my page (and built-in MW text in english too).

If I use the ULS (universal language selector) and set to french I also by default see the english version of my page (but I do see the built-in mediawiki text in french).

I removed the uls-previous-languages cookie and refreshed my page. My authentication is done with a custom extension and it does not set any cookie or setting related to language (and my LocalSettings.php does not set wgDefaultLanguage.

I would like this to happen: 1) accept-language is used for mediwiki text (Im talking about the text rendered by mediawiki not by my content). If not set it defaults to $wgDefaultLanguage 2) accept-language is used to decide which translate page to render.

I dont see how it would make sense to do it any other way - and I assumed that the language bundle would just do things this way. Basically, if a french browser comes to my site, they see the french version of the page - they should not have to select the french link and wait for ye another page refresh.

Regarding point #2:

It seems the "language specific" page is the one with the / appended in the URL. And this allows a french browser to see the english page. Etc. this is all fine.

but by default, the rendering of the page with no / appended tot he URL should be based on the accept-language header. But its not.

I even use the "universal language extension" and select "french" and it STILL displays the default page never the french page.

If I fiddle with $wgLanguageCode and $wgDefaultLanguage I can get strange things to happen. I should not have to touch these, the extensions should be doing all this right?

Mike Papper