Incorrect locale code from Google Chrome on Mac - macos

On Mac, the operating system language is the chrome browser language. I change the language to English (Canada) but the chrome extension I created was picking up en_US as the locale code. Tried it with multiple mac devices and the behaviors were all similar.
Used this method to get the language:
chrome.i18n.getMessage('##ui_locale')
also tried using
chrome.i18n.getUILanguage()
and they both had similar results which is en_US and en-US respectively.

Related

SwiftUI application localized the wrong way on Xcode?

I have a localized (in English and in French) iPhone app on the App Store and there's something I'm wondering for a while without being able to get a response.
As you can see on the image below (from Xcode), English is set as the Development Language but not as the Base one so I'm wondering what happens for a user in Spain (with a phone in Spanish) or in Germany (in German), etc? What language did he sees on the App Store?
Maybe I'm freaking out for nothing! But English as the Base and not the Development Language would be more logic? Unfortunately, I can't try it myself, making my phone in Spain/Spanish because I still get the French App Store.
Thanks!
The localization setting has nothing to do with the AppStore. It's related to the end user's device (or app-specific) region. You can add your localized files for any localization you need (by selecting the file and adding to the desired localization from the right pannel), but the default localization will always be English.
So don't worry

p5.speech set default voice is not working

Hello I am working with p5.speech and I have set in my code a default voice to an english voice like so:
var speech = new p5.Speech('Kate');
My computer default language is Italian, and everything works as it should. I hear the english voice. I tested it on a friend computer and he gets his Spanish default speaking voice. How is this possible? Do I need some more settings?
Voices available to different browsers, operating systems, individual computers are vastly different. Your friend's computer probably does not have a voice named Kate.
These are voices available to Chrome on my Win10 machine.
These are voices available to Edge on my Win10 machine.
These are voices available to Chrome on my MacBook Pro.
It's less likely that people will have a specific English voice named Kate; it's more likely that people will have at least one en-US voice. The following code can choose an English (United States) voice for you.
var speech = new p5.Speech();
speech.setLang("en-US");
Demo:
https://glitch.com/~p5-speech-setlang-setvoice
A demo for you to try different combinations of setLang() and setVoice()
My observations:
Voices available depend on the browser you use. For example, I have 21 voices in Chrome and 6 in Edge.
There are two related functions: setVoice() and setLang(). They digest different arguments.
setLang() will try to choose a voice in the language you want if you have never called setVoice(). If you have called setVoice() once, setLang() won't be able to change voice for you anymore.
setLang()
For example:
setLang("it-IT")
setLang("en-US")
setLang("en-GB")
setLang("es-ES")
setVoice()
For example:
setVoice("Microsoft David Desktop - English (United States)")
setVoice("Microsoft Zira Desktop - English (United States)")
setVoice("Google US English")
setVoice("Google UK English Female")
References: BCP-47 code for languages | p5.speech reference

Office Add-in Not Detecting 'en-gb' Locale in Outlook Desktop

I've been having an issue with locale overriding in my Outlook Add-in. I recently added some simple override logic to the manifest to point the user to our UK sign in process if they are in a UK locale. For example:
<SourceLocation DefaultValue="https://our-url.com/assets/outlook.html">
<Override Locale="en-gb" Value="https://our-url.co.uk/assets/outlook.html" />
</SourceLocation>
This works correctly in outlook web, so the overrides appear to be implemented correctly. All the urls are the UK versions when I change my language to English(United Kingdom). However it does not work in Outlook desktop. It's picking up the locale as en-us regardless of any settings I change in Outlook or on my PC. We've also had an internal user located in the UK attempt to use the add-in and they still see the US version in Outlook desktop.
Edit: I'm on Windows 7 with Outlook 2016 (Also tested on Windows 10 with Outlook 2016). I've tried setting the editing language under Outlook's options menu to English (United Kingdom) as well as changing the date format, location, key board language, and system locale under the Windows control panel to English (United Kingdom) and changing the Outlook display language settings to match Microsoft Windows. There doesn't seem to be any variants of the english display language pack for Outlook. Just one general english pack.
What setting specifically is checked by Outlook desktop to determine locale?

iterm2 stopped showing cyrillic in Mojave (Terminal.app works fine)

iTerm2 stopped showed cyrillic letters (it shows ? instead of them). Terminal.app worked fine. System localization was setup to Russian.
Everything were working in High Sierra
Clarification: iTerm2 is usually used not as 'ssh' client but as regular terminal app on client macOS machine instead.
I would like to not that changing LC_ALL to russian is not good option here since it will change entire locale variable which will change the behaviour of other applications, I don't want to have russian in terminal output on the servers for example. So I would suggest to change it to en_US.UTF-8 instead.
Solution is simple - just add export LC_ALL=ru_RU.UTF-8 to ~/.bashrc

Google Play Experiment is available in wrong region

I've started Store listing experiment for en-IN English (India) language but I can see this experiment on Google Play although my device uses en-GB English (United Kingdom) locale.
Default Store listing language for my app is en-US English (United States) and en-GB is not listed.
Shouldn't be experiment available only for users with en-IN language and other English languages should fall back to default (en-US)? Can be this Store listing experiments distribution bug?
I've got response from Google Play Developer Support. It is Store listing bug and they are working on fix.

Resources