Skip to content

NVDA incorrectely associated symbols with wrong replace text #11963

@ghost

Description

Steps to reproduce:

  1. Create portable copy of NVDA 2020.4 beta 1 and set Windows One Core Voice to Microsoft Tracy (Hong Kong Cantonese)

  2. typing specific symbols or reading specific symbols will incorrectly spoken with wrong replace text
    For example:
    english comma are now spoken as 逗號 not comma
    symboles like ; @!.&^%*[]\ etc are all spoken as ↑↑↑

  3. I try pressing the reset configurations to default setting, and the issue described above disappeared

  4. Then I try changing the Windows OneCore voice from Microsoft HanHan (Taiwan Mandarin)to Microsoft Tracy (Hong Kong Cantonese), the problem come back again

Actual behavior:

When I take a look at the Punctuation/symbol pronunciation window,
I noticed the following issues

searching with , I found that the text replacement for , is now written as 逗號 (chinese name for comma) not comma

searching for symbols like @, I found that the replacement for @ is ↑↑↑

searching for symbols like ; there will have two results matching this search, where one symbol has a replacement of semi, where the other has a text replacement of ↑↑↑

Expected behavior:

symboles should be spoken with correct replace text, say , should say comma; ; should say semi; @ should say at etc.

System configuration

NVDA installed/portable/running from source:

portable

NVDA version:

2020.4 beta 1

Windows version:

win 10 20h1

Other information about your system:

My nvda language is set to Hong Kong Traditional Chinese
I have try switching nvda language to Taiwan Traditional Chinese, the problem still exist
My Windows language is Hong Kong Traditional Chinese

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.

The above issue I have not experience in any other nvda versions that I have used before. i.e. 2020.2, 2020.3 etc.

If addons are disabled, is your problem still occuring?

This issue identified when the portable copy is newly created, thus without addons

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions