tauri-apps / wry

Cross-platform WebView library in Rust for Tauri.
Apache License 2.0
3.72k stars 279 forks source link

better l18n support in webview (navigator.language) #442

Closed tauri-apps[bot] closed 2 years ago

tauri-apps[bot] commented 3 years ago

This issue has been upstreamed from https://github.com/tauri-apps/tauri/issues/2735

Is your feature request related to a problem? Please describe. I want to rely on navigator.language or navigator.languages in the webview to determine which language a user prefers and to then translate the app.

On WSL 2 / Ubuntu 20 the language is just "c", on Windows 10 with WebView2 it does not respect language settings on the system or browser (Edge) level, on native Ubuntu 20 it had a language that was actually more accurate then the system setting, but did not respect the system setting as well. I don't have access to a macos device.

Describe the solution you'd like Ideally navigator.language or navigator.languages contain languages that match the system level user preferences.

Describe alternatives you've considered One could call system level APIs (different for every platform, i guess) from Rust to determine the preferences and expose those to Rust and finally the webview. Without changing navigator.language or navigator.languages this approach is not ideal, because some libraries rely on those fields. Maybe an approach where those preferences are exposed on the navigator and additionally have exposed to Rust and Webview via functions.

keiya01 commented 2 years ago

I switched the MacOS system language setting from "English" to "Japanese" and it seems to be working as intended.

lucasfernog commented 2 years ago

navigator.language returns en-US in my Arch Linux; maybe the OP didn't set up the system language properly?

edit: ahh it's WSL2, maybe that's the problem.

lucasfernog commented 2 years ago

I can't find a way to change it in Windows though :(

lucasfernog commented 2 years ago

Looks like this is the way to read and set the language in webview2: https://docs.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.core.corewebview2environmentoptions.language?view=webview2-dotnet-1.0.902.49

See https://github.com/MicrosoftEdge/WebView2Feedback/issues/833

keiya01 commented 2 years ago

It looks good. I will try to implement it.

lucasfernog commented 2 years ago

I manage to overwrite navigator.language with this snippet:

let options: ICoreWebView2EnvironmentOptions = CoreWebView2EnvironmentOptions::default().into();
let mut language = String::from("pt-BR\0").encode_utf16().collect::<Vec<u16>>();
let lang = PWSTR(text.as_mut_ptr());
options.SetLanguage(lang);
lucasfernog commented 2 years ago

And an ugly code to read it:

let mut buffer = Vec::<u16>::with_capacity(6);
let mut lang = PWSTR(buffer.as_mut_ptr());
options.Language(&mut lang);
let buffer = unsafe { std::slice::from_raw_parts(lang.0, 5) };
let lang = String::from_utf16_lossy(buffer);

oh boy it's hard to learn the windows api :|

keiya01 commented 2 years ago

I found this issue. And I tried to set system language to webview but this code is not working.

lzdyes commented 2 years ago

invalid in Windows

keiya01 commented 2 years ago

Hey there. If you have a time, could you run this branch and tell me whether this works or not on windows. I think this should work but this is not working correctly in my ARM Windows11(language is not set in webview2). And if you know the reason why this is not working, please tell me about it :pray: Thank you.

amrbashir commented 2 years ago

@keiya01 it works perfectly on my x86 Windows machine. Don't worry about ARM now. we can fix it later if someone else reports it.

keiya01 commented 2 years ago

Wooo! Thank you @amrbashir !! I will open PR!

amrbashir commented 2 years ago

on a second test, navigator.langagues still returns ["en-US", "en"] although every setting in my Windows is changed to Arabic. There is nothing we can do about this apparently since the issue exists in Edge chromium and probably all chromium-based browsers.

I'll still merge the PR since it does have the desired effect on some other i18n components like new Date().toLocaleString()

John0x commented 1 year ago

Are there any news about this issue? @amrbashir I've run navigator.languages in the edge devtools and in my tauri app and they return entirely different results. OS: Mac

amrbashir commented 1 year ago

@John0x please file a new issue with the results an full tauri info output