moderated Re: Why are basic symbols not being spoken?

Sieghard Weitzel <sieghard@...>

I don't experience this, for me Jaws correctly read the section symbol when I read your message and even now when composing a message where I have inserted the same symbol below Jaws speaks it correctly. Unfortunately I have no idea why it won't speak it for you, I use Eloquence by the way, not sure if it could be specific to the synthesizer you use if you use a different one.




From: <> On Behalf Of Leo
Sent: September 9, 2021 7:44 AM
Subject: Re: Why are basic symbols not being spoken?


Hi Richard, I believe I heard something about this issue on a different mailing list, but I didn’t pay much of attention; however, if I recall well, it was something related to spelling alphanumeric data or spelling phonetically. You may check them out. In my case, this is not happening at all, and I have both of those options turned off. I’m sorry for the vagueness  of my feedback, but that’s all I got, may be someone familiarized with this issue will give you spot-on instructions.



     Leo Bado.


"It seems to me that I will always be happy in the place where I am not." Paul Auster. "City of Glass"


From: <> On Behalf Of Richard B. McDonald
Sent: Thursday, September 9, 2021 6:51 AM
Subject: Why are basic symbols not being spoken?




I am using Windows 10 and JAWS 2020.  Various basic symbols are not being spoken presently, when in the past they were.  For example, below is the “section symbol”:




Instead of JAWS speaking “section” it says “character 167.”  This symbol was inserted above using the JAWSKey+4 command.  So, it is not some rare, strange symbol.  In the past, JAWS use to properly speak it.


What has changed?  Is it, perhaps, some setting in my speech scheme or some other setting?




Join to automatically receive all group messages.