Interface Detect language Behavior

inesicio

I assume the "Detect language" feature setting under Settings > General > Interface Language works with GeoIP. I make this assumption because I have set macOS and Firefox to English, my IP is from Austria, and I get German as detected language instead of English.

For my setup I would expect English. If the feature relies on GeoIP keep in mind: Countries != languages. Especially awkward and tricky for multilingual countires like Switzerland and others.

Maybe change detection to "Accept-Language" header sent by the browser?

laiz

inesicio I assume the "Detect language" feature setting under Settings > General > Interface Language works with GeoIP.

That doesn't seem to be the case, at least for me. Changing the language setting of my browser (Orion) was reflected in the Detect Language section changing accordingly.

inesicio I have set macOS and Firefox to English, my IP is from Austria, and I get German as detected language instead of English.

I tested English, Swedish, French, and Finnish on my instance of Firefox. Setting the browser language was correctly detected by Detect Language.

Curiously, setting my Firefox to Polish was not detected by Kagi settings but setting Orion to Polish was.

inesicio

laiz You are right! I can not reproduce the issue with Chrome, but can still reproduct it with Firefox. So I guess its a browser related issue.

jacobwinters

"Detect language" is powered by Accept-Language. Firefox has two different language selectors in its settings; one sets the language used in the browser UI and one sets the contents of Accept-Language. Do you have any German options set in the dialog for "Choose your preferred language for displaying pages"?

(Also, our Accept-Language parser is a little weird. I'll take a look at it.)

inesicio

I have indeed set an addtional langauge. This is my setting

and this is how it looks in the header

Anyway, as EN is first this defaults the weight to 1 and german is 0.5. So also in this setup/constellation I would assume that English is beeing suggested.

But you probably have found the issue already, so thanks 🙂

jacobwinters

Yep, our Accept-Language parser had a bug and that configuration would hit it. Bug has been fixed.