I suspected that it might be that the JAWS script files were not
installed onto one computer.
The Liblouis braille translator that JAWS 17 and later uses does not
correctly translate dots 4-5-6. I believe that this issue was
addressed in a recent version of DBT, but would not be available in
11.3.
On 7/15/18, Caryn Navy <caryn@xxxxxxxxxx> wrote:
Hello Kuenga and all.* * *
Roger, I think you are right that JAWS says bullet when it recognizes
these two cells as the bullet and says underline when it does not. I
just did an experiment and found that when reading by line in a braille
document, JAWS says bullet when the UEB translator is in use but says
underline when the English (American Pre-UEB) translator is in use. I
got this result in DBT 11.3 and also in more recent versions of DBT. It
seems that the English (American Pre-UEB) braille-to-print translator
does not recognize dots 456, 256 as a bullet.
Kuenga, this seems connected to your other question about the choice of
template. Perhaps one computer has had an English UEB template as the
default one, but the other computer has had an English American Pre-UEB
template as the default one.
Just a guess in Massachusetts.
All the best,
Caryn
On 7/14/2018 7:13 PM, Roger Newell wrote:
I think I know what the issue is. Please provide the exact steps you
do to perform this, and then I can help fix the issue.
The issue is that on one computer, JAWS recognises the dots as the
symbol for a bullet point, while on the other computer, it is saying
the computer braille equivalents of these dot combinations.
On 7/14/18, Kuenga Chhoegyel<kuengachhoegyel@xxxxxxxxx> wrote:
Dear List,
I have two machines. Both have been installed JAWS 17 and DBT 11.3. Both
the
machines have windows 7 32 bit professional and office 2010.
When I type dot 4 5 6 and dot 2 5 6 one machine JAWS announces bulet and
another machine jaws announces underline.
Why do you think they announce differently and which is the correct?
Looking forward to hearing soon.
Kuenga Chhoegyel,
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
