Using Windows 7 64 bit with WE 8, I have no problem with any of those words
with any of the voices I've tried. So far the vast majority of such
peculiarities I've encountered are either just minor quirks I can get used
to or have been solved more or less easily by using the exceptions
dictionary. I have noticed though that most of the quirks that can't be
fixed take place while reading the words in a sentence. Many words that
sound wrong, leading me to check out whether or not I have misspelled them
pronounce correctly when I navigate word by word. I even encountered one
while typing this paragraph, the word peculiarities was pronounced oddly,
but when I navigated to it to check the spelling, Samanthat pronounced it
correctly and she also did so when reading this sentence while continuing to
say it oddly in the previous sentence. This sort of quirkiness doesn't seem
to me to be any more odd than various quirks I've encountered with pretty
much every synth. They all have their quirks, the question for each
individual user becomes which quirks of each synthesizer one finds one can
get used to and ignore and which ones are just too annoying.
What hasn't been so easy for me to put up with is the full stop issue and
related problems. I've read some saying that they don't consider it a big
issue and that one should just be careful to type things out correctly, but
the problem doesn't come from my own documents but rather from the vagaries
of web page and document rendering. In addition to pages randomly having a
period end up hanging by itself on a line, if the author of a page presents
an ellipsis and puts spaces between the periods used, one gets a triple full
stop. Since I have punctuation turned off, WE shouldn't even be reading
these periods. The Vocalizer voices also seem to be ignoring some other
settings as well, the best example I can give is abbreviations like 1st are
getting read as one street, though I've had a couple of occasions of st
being read as Saint as well. I didn't alter my settings after installing the
Vocalizer voices and Eloquence voices still read things correctly. So, what
seems to be happening is that the Vocalizer voices are selectively ignoring
verbosity settings. I am really liking the voices in every other way, it
would be great if this issue could be fixed.
Regards,
Chris
-----Original Message-----
From: manny
Sent: Friday, January 11, 2013 8:24 AM
To: gwmicro list
Subject: vocalizer voices not pronouncing words correctly
Hi,
The following :
dawn
d a w n
sounds like john
8gb
8 g b
sounds
like hgb
dog
d o g
sounds like cog
c o g
however
if I put d o g after dog then dog dog is pronounce correctly.
The same is true for the other examples.
Is this happening to everyone or is this a computer specific problem.
I am using tom premiem hi and tom premiem.
Many thanks,
Manny
--
Good luck, Manny checkout my stand-up comedy performance
http://www.youtube.com/watch?v=75fbevlz10g computer specifications:
Window Eyes 8 Dell xps420 with 8 gb memory c p u: Intel q6600 quad core
dual boot between Windows 7 64-bit and windows 8 64 bit all software and
drivers are up to date
If you reply to this message it will be delivered to the original sender
only. If your reply would benefit others on the list and your message is
related to GW Micro, then please consider sending your message to
[email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can
manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
