-
-
Notifications
You must be signed in to change notification settings - Fork 658
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
Emojis not reported with eSpeak Portuguese (Portugal) #14434
Comments
Cyrylle, some notes: |
Hi Rui Thanks for these corrections and precisions. I have modified the initial description of this issue to take into account notes 2 and 3.
Actually this rather happens because eSpeak considers 'pt' as the code for Portuguese (Portugal), whereas NVDA uses 'pt_PT' for this language. |
Note: For pt_BR and pt_PT, I guess it's less obvious since Brasilians are more numerous than Portuguese people. But maybe Portuguese from Portugal (or like) is also spoken in other countries? |
We have several countries speaking portuguese: |
It seems that NVDA is not correctly creating aliases for language codes without locales. |
Note: issue found while developing #14433.
Steps to reproduce:
Actual behavior:
NVDA reports "smiling face" with Portuguese accent.
Expected behavior:
NVDA should report it in Portuguese, i.e. "cara a sorrir"
Technical
NVDA logs, crash dumps and other attachments:
N/A
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2022.4beta3
Windows version:
Windows 10 2004 (x64) build 19041.388
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Not tested but this is surely something old.
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested; unrelated.
The text was updated successfully, but these errors were encountered: