speakup 3.0.4 is out

speakup 3.0.4 is out

[William Hubbs]

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

All,

I would like to announce the release of speakup 3.0.4.

This includes Chris Brannon's fixes for the sys file parameters, so
speakupconf should work correctly now.  Thanks, Chris, for this fix.

Also it includes a fix for the long-standing issue of slow
responsiveness to the reading commands such as read full screen.  I am
thinking this fix will also take care of the issue of some hardware
synthesizers randomly timing out.  The issue was that we were not
commanding the synthesizer to speak text being sent to it as often as we
should have.

If you are using the speakup git repository, this release is available
now.  Just use git pull to retrieve it and do the installation from
there.  Otherwise, it will be available on your distribution as soon as
the maintainers can package it.

If you have any questions, issues, or patches, please report them here,
and we will fix them as soon as we can.

Thanks,

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

iEYEARECAAYFAkoipFQACgkQblQW9DDEZTgLgACggWyHhwuGmTs4H0ODcdNdogxb
d5oAn2LkAfOeJ7+TvbhCYqtz7nhDPtI6
=Cf1B
-----END PGP SIGNATURE-----

Re: speakup 3.0.4 is out

[Hermann]

On 31.05.2009 17:37, William Hubbs wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> All,
>
> I would like to announce the release of speakup 3.0.4.
>
> This includes Chris Brannon's fixes for the sys file parameters, so
> speakupconf should work correctly now.  Thanks, Chris, for this fix.
>
> Also it includes a fix for the long-standing issue of slow
> responsiveness to the reading commands such as read full screen.  I am
> thinking this fix will also take care of the issue of some hardware
> synthesizers randomly timing out.  The issue was that we were not
> commanding the synthesizer to speak text being sent to it as often as we
> should have.
>
> If you are using the speakup git repository, this release is available
> now.  Just use git pull to retrieve it and do the installation from
> there.  Otherwise, it will be available on your distribution as soon as
> the maintainers can package it.
>
Could you please give the link to the Git repository?
Is it on the same site as Espeakup?
Hermann

Re: speakup 3.0.4 is out

[Tyler Littlefield]

William:
Is there any way I can help out with speakup? I'd like to start contributing 
somehow.


Thanks,
Tyler Littlefield
Web: tysdomain.com
email: tyler@tysdomain.com
My programs don't have bugs, they're called randomly added features.

----- Original Message ----- 
From: "William Hubbs" <w.d.hubbs@gmail.com>
To: "speakup mailing list" <speakup@braille.uwo.ca>
Sent: Sunday, May 31, 2009 9:37 AM
Subject: speakup 3.0.4 is out


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> All,
>
> I would like to announce the release of speakup 3.0.4.
>
> This includes Chris Brannon's fixes for the sys file parameters, so
> speakupconf should work correctly now.  Thanks, Chris, for this fix.
>
> Also it includes a fix for the long-standing issue of slow
> responsiveness to the reading commands such as read full screen.  I am
> thinking this fix will also take care of the issue of some hardware
> synthesizers randomly timing out.  The issue was that we were not
> commanding the synthesizer to speak text being sent to it as often as we
> should have.
>
> If you are using the speakup git repository, this release is available
> now.  Just use git pull to retrieve it and do the installation from
> there.  Otherwise, it will be available on your distribution as soon as
> the maintainers can package it.
>
> If you have any questions, issues, or patches, please report them here,
> and we will fix them as soon as we can.
>
> Thanks,
>
> William
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.11 (GNU/Linux)
>
> iEYEARECAAYFAkoipFQACgkQblQW9DDEZTgLgACggWyHhwuGmTs4H0ODcdNdogxb
> d5oAn2LkAfOeJ7+TvbhCYqtz7nhDPtI6
> =Cf1B
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 

Re: speakup 3.0.4 is out

[William Hubbs]

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

On Sun, May 31, 2009 at 05:53:34PM +0200, Hermann wrote:
> On 31.05.2009 17:37, William Hubbs wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> All,
>>
>> I would like to announce the release of speakup 3.0.4.
>>
>> This includes Chris Brannon's fixes for the sys file parameters, so
>> speakupconf should work correctly now.  Thanks, Chris, for this fix.
>>
>> Also it includes a fix for the long-standing issue of slow
>> responsiveness to the reading commands such as read full screen.  I am
>> thinking this fix will also take care of the issue of some hardware
>> synthesizers randomly timing out.  The issue was that we were not
>> commanding the synthesizer to speak text being sent to it as often as we
>> should have.
>>
>> If you are using the speakup git repository, this release is available
>> now.  Just use git pull to retrieve it and do the installation from
>> there.  Otherwise, it will be available on your distribution as soon as
>> the maintainers can package it.
>>
> Could you please give the link to the Git repository?
> Is it on the same site as Espeakup?

To get the speakup repository, issue the following command:

git clone http://linux-speakup.org/speakup.git

There is also currently a mirror which is updated every 3 hours at:

git clone git://hubbs.homedns.org/speakup.git

And Chris has a mirror which I do not recall right now.

William

> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEARECAAYFAkoirqYACgkQblQW9DDEZTjeJwCgge3qeuq+EcvDaAdxfirFouLl
VeAAoIoO37TUixq53LO+kaBQpdCyRRFA
=zO1z
-----END PGP SIGNATURE-----

Re: speakup 3.0.4 is out

[Hermann]

am So 31. Mai 2009 um 21:20:56 schrieb William Hubbs <w.d.hubbs@gmail.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sun, May 31, 2009 at 05:53:34PM +0200, Hermann wrote:
> > On 31.05.2009 17:37, William Hubbs wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> All,
> >>
> >> I would like to announce the release of speakup 3.0.4.
> >>
> >> This includes Chris Brannon's fixes for the sys file parameters, so
> >> speakupconf should work correctly now.  Thanks, Chris, for this fix.
> >>
> >> Also it includes a fix for the long-standing issue of slow
> >> responsiveness to the reading commands such as read full screen.  I am
> >> thinking this fix will also take care of the issue of some hardware
> >> synthesizers randomly timing out.  The issue was that we were not
> >> commanding the synthesizer to speak text being sent to it as often as we
> >> should have.
> >>
> >> If you are using the speakup git repository, this release is available
> >> now.  Just use git pull to retrieve it and do the installation from
> >> there.  Otherwise, it will be available on your distribution as soon as
> >> the maintainers can package it.
> >>
> > Could you please give the link to the Git repository?
> > Is it on the same site as Espeakup?
> 
> To get the speakup repository, issue the following command:
> 
> git clone http://linux-speakup.org/speakup.git
> 
Was pretty slow.

> There is also currently a mirror which is updated every 3 hours at:
> 
> git clone git://hubbs.homedns.org/speakup.git
> 
That worked well.

> And Chris has a mirror which I do not recall right now.
> 
The installation went well, and now it is possible to create that direct 
file in /sys/module/speakup/parameters.
But one issue remains: When doing so, and start Espeakup with the -V option 
using "de" for German, not all punctuation characters were echoed when 
typing. In fact almost non are spoken. For English this works fine.
And one final thing: When I reboot my machine the direct file has changed 
its value from 1 to 0; is this normal? Do I have to create a startup script 
containing the change of this value together with Espeak's start options?
Hermann

Re: speakup 3.0.4 is out

[Adam Myrow]

I found a nasty bug right off with speakupconf.  It still doesn't work 
quite right, at least with the Dectalk USB in RS232 mode.  All you have to 
do to see it in action is do "speakupconf save" followed by "speakupconf 
load."  After that, no uppercase characters will be echoed.  That is, you 
will get silence when typing any uppercase character, or going over it in 
review mode.  Also, the bug involving slowness with the Dectalk still 
exists.  To reproduce it, simply echo something to the serial port that 
the Dectalk is on.  You will get an I/O error, and the shell will hang 
until you hit control-c.  Also, the Dectalk will now respond very slowly, 
taking about 5 seconds to speak after any keystroke.  I originally noticed 
this because of the HAL daemon, (hald.)  Apparently, it opens serial ports 
during its initial startup.  I had to disable it in order to avoid this 
bug.  So, for me, this new Speakup didn't fix anything.

Re: speakup 3.0.4 is out

[Chris Brannon]

Adam Myrow wrote:
> I found a nasty bug right off with speakupconf.  It still doesn't work 
> quite right, at least with the Dectalk USB in RS232 mode.  All you have to 
> do to see it in action is do "speakupconf save" followed by "speakupconf 

Hi Adam,
I don't have a DecTalk USB, so I can't reproduce your bug.  I want to know
what your caps_start and caps_stop parameters look like, before and
after speakupconf load.
Please copy /sys/module/speakup/parameters/caps_start and
/sys/module/speakup/parameters/caps_stop to temporary files, before and after
speakupconf load.
Send them on list or off, so I can have a look.

Regards,
-- Chris

Re: speakup 3.0.4 is out

[Adam Myrow]

On Sun, 31 May 2009, Chris Brannon wrote:

> I don't have a DecTalk USB, so I can't reproduce your bug.  I want to know
> what your caps_start and caps_stop parameters look like, before and
> after speakupconf load.

They look the same to me.

The contents of caps_start before "speakupconf load."
"[:dv ap 200]"

The contents of caps_stop before "speakupconf load."
"[:dv ap 100]"

After "speakupconf load," the caps_start contents are still the same.
"[:dv ap 200"

The same goes for caps_stop.
"[:dv ap 100"

One other thing I noticed is that after doing "speakupconf load," the 
volume goes up slightly.  I'm really wondering about those quotes.  That 
just doesn't look right to me.

Re: speakup 3.0.4 is out

[Chris Brannon]

Adam Myrow wrote:
> They look the same to me.
> 
> The contents of caps_start before "speakupconf load."
> "[:dv ap 200]"
> 
> The contents of caps_stop before "speakupconf load."
> "[:dv ap 100]"
> 
> After "speakupconf load," the caps_start contents are still the same.
> "[:dv ap 200"
> 
> The same goes for caps_stop.
> "[:dv ap 100"

The second contents are missing a right bracket before the closing quote
in both  cases.
So they aren't the same, unless perhaps, you typed them and forgot the
closing brackets.
Still, I can't see where the closing brackets would have gone.

Regards,
-- Chris

Re: speakup 3.0.4 is out

[Samuel Thibault]

Hello,

Hermann, le Sun 31 May 2009 22:07:37 +0200, a écrit :
> When I reboot my machine the direct file has changed its value from 1
> to 0; is this normal?

Yes.  You can change modules' parameters by adding a file to
/etc/modprobe.d or whichever way it's done in your distro, see its
documentation.

That said, maybe we could make espeakup systematically set direct to 1
itself?

Samuel

Re: speakup 3.0.4 is out

[Samuel Thibault]

Adam Myrow, le Sun 31 May 2009 19:08:39 -0500, a écrit :
> To reproduce it, simply echo something to the serial port that 
> the Dectalk is on.

Then don't do it :)  That is a basic flaw in the way speakup is
currently done: it doesn't interfere correctly with using the serial
port with other applications.

> I originally noticed this because of the HAL daemon, (hald.)          
> Apparently, it opens serial ports during its initial startup.

Augh.  I wonder the reason why they do such things, it can not but
interfere with a lot of things.

Samuel

Re: speakup 3.0.4 is out

[William F. Acker WB2FLW +1 303 722 7209]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 673 bytes --]

On Mon, 1 Jun 2009, Samuel Thibault wrote:

> Adam Myrow, le Sun 31 May 2009 19:08:39 -0500, a écrit :
>> To reproduce it, simply echo something to the serial port that
>> the Dectalk is on.
>
> Then don't do it :)  That is a basic flaw in the way speakup is
> currently done: it doesn't interfere correctly with using the serial
> port with other applications.
>
>> I originally noticed this because of the HAL daemon, (hald.)
>> Apparently, it opens serial ports during its initial startup.
>
> Augh.  I wonder the reason why they do such things, it can not but
> interfere with a lot of things.
I wonder why this only bothers the Dectalk.

-- 
           Bill in Denver

Re: speakup 3.0.4 is out

[Samuel Thibault]

Hello,

William Hubbs, le Sun 31 May 2009 10:37:57 -0500, a écrit :
> If you are using the speakup git repository, this release is available
> now.  Just use git pull to retrieve it and do the installation from
> there.  Otherwise, it will be available on your distribution as soon as
> the maintainers can package it.

That's done in Debian.

Samuel

Re: speakup 3.0.4 is out

[Gregory Nowak]

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

On Mon, Jun 01, 2009 at 05:51:52PM +0200, Samuel Thibault wrote:
> That said, maybe we could make espeakup systematically set direct to 1
> itself?

Then that would mean that those of us who like the behavior of direct
as it now is, would have to set it to 0 every time. Since you can't
please everyone whichever way you go, why not simply leave things as
they are now? Besides, I seem to recall William saying that direct is
experimental at this stage. If that's still the case, then that's
another reason for not activating it by default.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkokR9wACgkQ7s9z/XlyUyCGZwCfbX8sTW94fByOvetlvfEL1eS8
ApAAn2FJXRUxB0fjiSR8Qq5/U+MD5J3k
=FC+E
-----END PGP SIGNATURE-----

Re: speakup 3.0.4 is out

[Samuel Thibault]

Gregory Nowak, le Mon 01 Jun 2009 14:27:56 -0700, a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Mon, Jun 01, 2009 at 05:51:52PM +0200, Samuel Thibault wrote:
> > That said, maybe we could make espeakup systematically set direct to 1
> > itself?
> 
> Then that would mean that those of us who like the behavior of direct
> as it now is, would have to set it to 0 every time. Since you can't
> please everyone whichever way you go, why not simply leave things as
> they are now?

Because we can also find an intermediate.  For any language other than
english, letting direct to 0 give very bad result.

Samuel

Re: speakup 3.0.4 is out

[William F. Acker WB2FLW +1 303 722 7209]

On Sun, 31 May 2009, Chris Brannon wrote:

> Adam Myrow wrote:
>> They look the same to me.
>>
>> The contents of caps_start before "speakupconf load."
>> "[:dv ap 200]"
>>
>> The contents of caps_stop before "speakupconf load."
>> "[:dv ap 100]"
>>
>> After "speakupconf load," the caps_start contents are still the same.
>> "[:dv ap 200"
>>
>> The same goes for caps_stop.
>> "[:dv ap 100"
>
> The second contents are missing a right bracket before the closing quote
> in both  cases.
> So they aren't the same, unless perhaps, you typed them and forgot the
> closing brackets.
> Still, I can't see where the closing brackets would have gone.
>
Same with soft.  In that case, the trailing letter p is missing.

           HTH.

-- 
           Bill in Denver

Re: speakup 3.0.4 is out

[Adam Myrow]

On Sun, 31 May 2009, Chris Brannon wrote:

> The second contents are missing a right bracket before the closing quote 
> in both cases.

You're right.  A few experiments show that it appears to be cutting off 
the last character that gets sent to it.  In other words, if you echo a 
string to caps_start or caps_stop, the last character gets chopped off. 
The only way I've found to restore Speakup to proper behavior after this 
is to echo "soft" to /sys/module/speakup/parameters/synth, then echo 
"dectlk" to the same file.  In other words, by switching synthesizers, it 
resets everything to default values.

Re: speakup 3.0.4 is out

[Chris Brannon]

William F. Acker wrote:
> Same with soft.  In that case, the trailing letter p is missing.
> 
>            HTH.

Yes, it helped very much.  Not sure why I wasn't seeing the same problem,
but I did after a rebuild and reinstall.
There was an off-by-one error in the patch that I posted Thursday morning.

Regards,
-- Chris

bug fixed was Re: speakup 3.0.4 is out

[Chris Brannon]

Adam Myrow wrote:
> You're right.  A few experiments show that it appears to be cutting off 
> the last character that gets sent to it.  In other words, if you echo a 
> string to caps_start or caps_stop, the last character gets chopped off. 

This is fixed in git, as of about 5 minutes ago.
Thanks to you and William Acker for tracking it down.

Regards,
-- Chris

Re: speakup 3.0.4 is out

[Willem van der Walt]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1501 bytes --]

Maybe, William Hubs can add a --direct flag to espeakup?
As one need to give the -V flag already to set the espeak language, adding 
another would be easier than the echo for most.
Regards, Willem

On Mon, 1 Jun 2009, Samuel Thibault wrote:

> Gregory Nowak, le Mon 01 Jun 2009 14:27:56 -0700, a écrit :
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > On Mon, Jun 01, 2009 at 05:51:52PM +0200, Samuel Thibault wrote:
> > > That said, maybe we could make espeakup systematically set direct to 1
> > > itself?
> > 
> > Then that would mean that those of us who like the behavior of direct
> > as it now is, would have to set it to 0 every time. Since you can't
> > please everyone whichever way you go, why not simply leave things as
> > they are now?
> 
> Because we can also find an intermediate.  For any language other than
> english, letting direct to 0 give very bad result.
> 
> Samuel
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.