problems with newer Speakup

problems with newer Speakup

[Adam Myrow]

Hi.  Well, I finally got around to testing the changes in Speakup that 
were made last Monday.  To make a long story short, the results were 
disastrous!  I am using a Dectalk USB in RS-232 mode.  Thus, I use the 
speakup_dectlk module.  I discovered that it works fine with small amounts 
of text, but the computer locks hard once a large block of text has to be 
read.  For example, when I logged in and started alpine to read email, the 
system suddenly became unresponsive, and just kept reading the main menu. 
After that, I had to do a hard power-off.  In another attempt, I got as 
far as opening an email before it locked up.  In short, whatever this 
change involved, it made Speakup unusable for me.  I ended up reverting 
back to the previous version.  What I can't understand is why nobody else 
noticed this, especially since the change has been in place for almost a 
week.

Re: problems with newer Speakup

[Chris Brannon]

Adam Myrow wrote:
> Hi.  Well, I finally got around to testing the changes in Speakup that 
> were made last Monday.  To make a long story short, the results were 
> disastrous!  I am using a Dectalk USB in RS-232 mode.

Hello,
I failed to release a lock in the Dectalk driver, and that is why your
system froze.
This only affected the Dectalk Express driver.  I checked the others.

Would you mind testing this one more time, please?  I'd really appreciate it.

-- Chris

Re: problems with newer Speakup

[Adam Myrow]

On Sun, 26 Jul 2009, Chris Brannon wrote:

> Would you mind testing this one more time, please?  I'd really 
> appreciate it.

Yep, it is working properly now.  Thanks for the quick fix.  Now, do you 
have any idea why the Dectalk splits contractions?  For example, when 
Speakup sees the word "don't," the Dectalk pronounces it "don t."  It's as 
if the apostrophe were being treated as a space.  This is 
Speakup-specific, since this never happens if I echo a contraction to 
/sys/accessibility/speakup/synth_direct.  This has been a problem with the 
Dectalk drivers since day one.

Re: problems with newer Speakup

[William Hubbs]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Jul 27, 2009 at 07:17:41PM -0500, Adam Myrow wrote:
> Yep, it is working properly now.  Thanks for the quick fix.  Now, do you 
> have any idea why the Dectalk splits contractions?  For example, when 
> Speakup sees the word "don't," the Dectalk pronounces it "don t."  It's as 
> if the apostrophe were being treated as a space.  This is Speakup-specific, 
> since this never happens if I echo a contraction to 
> /sys/accessibility/speakup/synth_direct.  This has been a problem with the 
> Dectalk drivers since day one.

Adam, I believe I found this,  There was a flag that was set in the
driver that was having speakup insert a space when sending to the
synthesizer after a punctuation symbol.  I'm not sure why this was there
unless it had to do with older dectalks.  It has been removed.  It has
been removed.  Can you test again?

Thanks,

William

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkpuZRkACgkQblQW9DDEZThK3wCgjmiW4rRzzM+S5GaWlss5F608
0aYAoIjz9DCeSrqm33E0Aztr5E/hGLAc
=JplQ
-----END PGP SIGNATURE-----

Re: problems with newer Speakup

[Adam Myrow]

On Mon, 27 Jul 2009, William Hubbs wrote:

> Adam, I believe I found this,  There was a flag that was set in the
> driver that was having speakup insert a space when sending to the
> synthesizer after a punctuation symbol.

That seems to have done the trick, though I suspect I know why the space 
was being inserted originally.  Now, while contractions are spoken the way 
they should be, email addresses are spoken without the periods.  This only 
happens when reading with the plus key, or letting Speakup automatically 
read the screen.  When reading with the 4 and 6 keys, that is, word by 
word, the default reading punctuation level is apparently higher, as 
punctuation characters are all read.  As far as I am concerned, this is an 
acceptable trade off.  Those broken-up contractions were driving me crazy! 
However, if this really bugs somebody, it might be better to have spaces 
inserted only in certain situations.  That is, only if a period or at sign 
is between two letters.