Hello Jean and all.
This problem sounds like what happens with JAWS when you have two
particular settings in DBT's Global Menu. Here are the Global settings
in DBT which when combined throw JAWS off course:
1. In Global -> Internationalization choose Prefer Unicode braille
patterns, and
2. in Global -> Default views set Default font for braille documents to
Braille or SimBraille.
With those two settings combined, JAWS chooses the wrong characters to
speak and show on the braille display. It's interesting that this same
combination of DBT settings works fine with other screen readers.
All the best,
Caryn
If you switch in Global -> Internationalization from Prefer Unicode
braille patterns to Prefer Local/national encoding, the problem is
eliminated. Alternatively, if you switch the default font for braille
documents in Global -> Default Views from Braille or SimBraille to
Print, the problem is eliminated as well.
All the best,
Caryn
On 1/28/2021 9:12 PM, jean.e.menzies@xxxxxxxxx wrote:
Further information. Six-key entry in a Braille file is also really messed up. For example, pressing “l” for dot 6, I hear “sh sign”. “k” for dot 5 says “ed sign”. Etc.
To explain the results in a translated file, if I type the word “test” and translate, I get “dots 3-6 space space dots 1-3-4”. The second hyphen does not appear on the display, but Jaws speaks it.
Tomorrow I will reinstall an older version of Jaws and see if it fixes this.
Jean
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
