[duxuser] Re: Translated Braille file problem with lateest JAWS update

  • From: Caryn Navy <caryn@xxxxxxxxxx>
  • To: duxuser@xxxxxxxxxxxxx, jean.e.menzies@xxxxxxxxx
  • Date: Fri, 29 Jan 2021 15:42:53 -0500

Hello again Jean.


I may be misunderstanding you, but I want to make sure that I was clear about the settings. The two settings that I listed are the ones that cause the problem, not the settings I recommend. If you have both of the settings that I listed, then make a change. For example, in Global -> Internationalization, switch from Prefer Unicode braille patterns to Prefer local/national encoding.


If you already had JAWS 2021 on your system and just updated to a newer release, there would be no reason for DBT to prompt you to install the JAWS script files, as they would already have been installed. To make sure you are using the JAWS script files for DBT, press Insert+Q in DBT. If JAWS says, "dbtw settings are loaded," that means the JAWS script files for DBT are running.


I hope this helps.


Best regards,

Caryn


On 1/29/2021 1:45 PM, jean.e.menzies@xxxxxxxxx wrote:

Hello Caryn,

I doublechecked, and those are the settings I have. So this is not the fix. Ug.

After installing this Jaws update, I didn’t get a prompt from DBT to install the latest Jaws scripts, etc. Can you remind me where to check to see if the Jaws scripts are even being loaded? I have forgotten how to manually install scripts.

Jean

*From:* duxuser-bounce@xxxxxxxxxxxxx <duxuser-bounce@xxxxxxxxxxxxx> *On Behalf Of *Caryn Navy
*Sent:* January 28, 2021 10:51 PM
*To:* duxuser@xxxxxxxxxxxxx; jean.e.menzies@xxxxxxxxx
*Subject:* [duxuser] Re: Translated Braille file problem with lateest JAWS update

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 <mailto: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
    ______________________________________________________________________


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

Other related posts: