-
-
Notifications
You must be signed in to change notification settings - Fork 756
Closed
Labels
good first issuegithub features these at https://github.com/nvaccess/nvda/contributegithub features these at https://github.com/nvaccess/nvda/contributetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Description
Steps to reproduce:
- Start NVDA.
- Switch NVDA's interface language from english to another one (preferably one that you are familiar with) and restart NVDA when prompted.
- Open a text editor like Notepad or a similar one, from which text formatting information can be retrieved by NVDA.
- Type some text in it.
- Move the system caret on one of the typed characters.
- Invoke the NVDA script for reporting formatting information (e.g. NVDA+F for the desktop keyboard layout).
- Press the same command twice, to display the information in a browse mode window.
- Observe how NVDA reports the information, specially the name of the font size unit.
Actual behavior:
NVDA reports the font size unit in english as "pt" (which means "points"), instead of in the language in which NVDA is set to.
Expected behavior:
NVDA should report the font size unit in the language in NVDA's interface language is set to.
System configuration
- Operating system: Windows 11 Pro version 21H2 (build 22000.556), 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- NVDA version: alpha-25159,c4466885, 2021.3.5 (both set to "Bulgarian").
- Processor: Intel Core i5-9400F at 2.90GHz.
- RAM Memory: 16.00GB.
- Graphics: MSI GeForce GTX-1050TI Gaming X 4G, 4096MB dedicated memory, desktop resolution set to 1920x1080.
- Sound Card: Realtek ALC892 at Intel Cannon Point PCH.
Other questions
Does the issue still occur after restarting your computer?
Yes, it does.
Have you tried any other versions of NVDA? If so, please report their behaviors.
Both the latest alpha build and 2021.3.5 behave the same.
If NVDA add-ons are disabled, is your problem still occurring?
Yes, it is.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
I haven't tried it, because the issues that the COM Registration Fixing Tool aims to fix are not related to the issue I'm describing here.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
good first issuegithub features these at https://github.com/nvaccess/nvda/contributegithub features these at https://github.com/nvaccess/nvda/contributetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.