Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loading NVDA with specific languages shows "Locale not supported by OS" warning message box #8064

Closed
florianionascu7 opened this issue Mar 8, 2018 · 16 comments · Fixed by #8612
Closed
Labels
Milestone

Comments

@florianionascu7
Copy link

@florianionascu7 florianionascu7 commented Mar 8, 2018

Hello folks! When changing the language to Kirgyz, NVDA works Properly till the restart. After that, the following error message occurs:


Nvda Warning

Locale 'Kirghiz' not supported by OS.

OK

Steps to reproduce:

  1. Open the NVDA menu.
  2. Go to Preferences, General Settings.
  3. Choose and select Kirgyz language from the languages list. After the restart, the error I'm talking about occurs.

NVDA version: 2018.1
Operating system: Windows 10 Fall Creators Update 64-bit.
Hope this helps.

@leonardder leonardder changed the title A bug regarding Kirgyz language Loading NVDA with specific languages shows "Locale not supported by OS" warning message box Mar 13, 2018
@leonardder
Copy link
Collaborator

@leonardder leonardder commented Mar 13, 2018

cc @josephsl

This also applies to Mongolian at least.

@ivnc
Copy link

@ivnc ivnc commented Mar 13, 2018

Also for Galician.
Looks like that's something related with dependencies, as TWBlue shows the same message with Galician.
This issue was pressent in many versions, it didn't appeared with 2018.1. Tested in various computers (Windows10 High Creators, Windows10 Creators, windows XP...).

@florianionascu7
Copy link
Author

@florianionascu7 florianionascu7 commented Mar 16, 2018

Now I'm confirming what Iván said. Unfortunately, it seems that this is a regression bug.

@leonardder
Copy link
Collaborator

@leonardder leonardder commented Mar 16, 2018

@ivnc commented on 13 Mar 2018, 21:33 CET:

This issue was pressent in many versions, it didn't appeared with 2018.1.

Are you saying that this problem also occurred in 2017.4 and even earlier?

@ivnc
Copy link

@ivnc ivnc commented Mar 16, 2018

@angaragmn
Copy link

@angaragmn angaragmn commented Apr 3, 2018

Yes, when using Mongolian local test, it gives exactly that error. I'm wondering when it is going to be fixed. Still 18.1.1 didn't fix it yet. :)

@Qchristensen
Copy link
Member

@Qchristensen Qchristensen commented Aug 8, 2018

As noted in linked issue #8080, Macedonian also encounters this error.

I noticed when looking at: https://github.com/nvaccess/nvda/wiki/Translating

That a number of the languages affected (Mongolian, Kyrgyz, Macedonian at least), aren't listed on that page, could that be related, or is it just that the translation list on that page is out of date?

Has anyone found a workaround?

@michaelDCurran
Copy link
Member

@michaelDCurran michaelDCurran commented Aug 9, 2018

If I understand correctly from quick testing, a part from that warning, NvDA continues to function normally?
I'm guessing that the error is because wx does not have a translation database (wxstd.mo) for these languages.
This means that some standard UI elements won't have translations. E.g. Ok and cancel buttons etc.
Question is though whether we can/should suppress that warning.

@ivnc
Copy link

@ivnc ivnc commented Aug 9, 2018

I think it isn't related, because as I've said happens also with other Python applications. For example Galician, one of the affected languages, is listed in that page and is a NVDA translation since several years ago (cc @quetzatl).
It could be more related with the size of the language's community. For instance, Galician isn't present in most of big/proprietary-code applications (p.e. JAWS, without going any further). If the app in question is opensource the probability of being translated into less diffused languages normally increments, but there still are few translated open-source apps compared to other languages. What I want to say is that probably there is one NVDA dependency that supports less languages than NVDA itself. I suppose that something similar may happen, more or less, with the other languages affected by this.

I say this from my elemental NVDA internals knowledge, but this is the option I've in mind that makes more sense for me.

BTW, could the reason why these languages don't appear in the wiki be that it was updated with 2017.3 release? Mongolian was added in 2018.2, Kyrgyz in 2018.1 and Macedonian in 2017.4, according with the changelog.

Regards.
Update: After seing the @michaelDCurran's comment (I hadn't seen it before the original comment), it seems that our hypothesis are similar. Yes, NVDA continues to work normally after closing the warning and even if the dialog remains opened.

@josephsl
Copy link
Collaborator

@josephsl josephsl commented Aug 9, 2018

Hi,

This is a wxPython error. When wx.Locale().Init is called and when the locale isn't present, the dialog noted will be shown.

Thanks.

@michaelDCurran
Copy link
Member

@michaelDCurran michaelDCurran commented Aug 9, 2018

@angaragmn
Copy link

@angaragmn angaragmn commented Sep 12, 2018

Guys, in 2018.3 rc1, the famed warning message is still there, showing its ugly head upon us. lol all joking aside, has anyone tested it with the 2018.3 rc1? I have checked all 3 languages that were effected by this, and all 3 are giving same warning messages. "NVDA warning, locale x is not supported by OS." I thought we have fixed this issue. So is it only me? or you guys are getting same errors as well. The 3 languages are, Mongolian, Kirgiz and Galician.

@ivnc
Copy link

@ivnc ivnc commented Sep 12, 2018

@zstanecic
Copy link
Contributor

@zstanecic zstanecic commented Sep 12, 2018

@angaragmn
Copy link

@angaragmn angaragmn commented Sep 12, 2018

Oo I just saw that Michael had added it to the milestone 2018.4 my bad. Thanks guys, Yeah just tested the Alpha snap and it works fine. Once again, thank you guys for responding quickly. :)b

@florianionascu7
Copy link
Author

@florianionascu7 florianionascu7 commented Sep 13, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants