Re: continuous reading feature

Re: continuous reading feature

[MICHAEL MCDONALD]

I'm not sure about the keymap issue.  I don't know if that is done
automatically when you rebuild speakup or if some procedure needs to be
done to rebuild it.  Maybe Kirk can give a better answer on this one.

I have the read all command working, but only for a few of the synths. 
When I finished read all, I asked if there was anyone to help with the
development of the other synths, but I never got much of a response.  I
can give you the status as I know it.  Dectalk, doubletalk, and litetalk
should work as far as I know.  I have all 3 synths, so I can test these
easily.  Speakout has been implemented, but there are some issues and it
seems to behave differently with different kernels, but I don't have one
to try and fix the issues..  Speech Dispatcher should work with
Festival.  It should be fairly easy to implement other synths, but since
I don't have access to them, I haven't been able to implement them.

Mike

Re: continuous reading feature

[Charles Hallenbeck]

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


Mike,

The keymap tutorial seems pretty clear if a change needs to be made. I 
guess the speakup+r key needs to be bound to something. What should it 
be bound to?

Thanks,
Chuck

On Mon, Jun 19, 2006 at 06:46:42AM -0400, MICHAEL MCDONALD wrote:
> I'm not sure about the keymap issue.  I don't know if that is done
> automatically when you rebuild speakup or if some procedure needs to be
> done to rebuild it.  Maybe Kirk can give a better answer on this one.
> 
> I have the read all command working, but only for a few of the synths. 
> When I finished read all, I asked if there was anyone to help with the
> development of the other synths, but I never got much of a response.  I
> can give you the status as I know it.  Dectalk, doubletalk, and litetalk
> should work as far as I know.  I have all 3 synths, so I can test these
> easily.  Speakout has been implemented, but there are some issues and it
> seems to behave differently with different kernels, but I don't have one
> to try and fix the issues..  Speech Dispatcher should work with
> Festival.  It should be fairly easy to implement other synths, but since
> I don't have access to them, I haven't been able to implement them.
> 
> Mike
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
The Moon is Waning Crescent (40% of Full)
Get downloads from http://www.mhcable.com/~chuckh
  and remember, INFORMATION WANTS TO BE FREE!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEloy6XnuiIOyDVQURAlu0AJ0coxk1VkXPN8Bzk0N8b1M1UkLyPgCcD4fh
6oiNOGwhve/Lt5HggRMfX7w=
=OLW0
-----END PGP SIGNATURE-----

Re: continuous reading feature

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

The most recent versions of keymap.map in the speakup directory has
speakup-R listed at the bottom of the list.

I don't think this gets generated automatically though I saw some stuff
in the Makefile for it.  In fact, I recently had to manually compile the
genmap.c program in order to regen my keymap.  I have a keymap that I
modified the laptop keys to be more clearly mapped and I included the
read-all key in there as well.  The keymap tutorial explains all how to
build the keymap and I then explicitly copied the generated map into my
/proc/keymap and backup directories so I don't lose them.

On Mon, Jun 19, 2006 at 07:38:34AM -0400, Charles Hallenbeck wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> Mike,
> 
> The keymap tutorial seems pretty clear if a change needs to be made. I 
> guess the speakup+r key needs to be bound to something. What should it 
> be bound to?
> 
> Thanks,
> Chuck
> 
> On Mon, Jun 19, 2006 at 06:46:42AM -0400, MICHAEL MCDONALD wrote:
> > I'm not sure about the keymap issue.  I don't know if that is done
> > automatically when you rebuild speakup or if some procedure needs to be
> > done to rebuild it.  Maybe Kirk can give a better answer on this one.
> > 
> > I have the read all command working, but only for a few of the synths. 
> > When I finished read all, I asked if there was anyone to help with the
> > development of the other synths, but I never got much of a response.  I
> > can give you the status as I know it.  Dectalk, doubletalk, and litetalk
> > should work as far as I know.  I have all 3 synths, so I can test these
> > easily.  Speakout has been implemented, but there are some issues and it
> > seems to behave differently with different kernels, but I don't have one
> > to try and fix the issues..  Speech Dispatcher should work with
> > Festival.  It should be fairly easy to implement other synths, but since
> > I don't have access to them, I haven't been able to implement them.
> > 
> > Mike
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> - -- 
> The Moon is Waning Crescent (40% of Full)
> Get downloads from http://www.mhcable.com/~chuckh
>   and remember, INFORMATION WANTS TO BE FREE!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> 
> iD8DBQFEloy6XnuiIOyDVQURAlu0AJ0coxk1VkXPN8Bzk0N8b1M1UkLyPgCcD4fh
> 6oiNOGwhve/Lt5HggRMfX7w=
> =OLW0
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://holmesgrown.ld.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFElrRQWSjv55S0LfERA5OmAKCaHdkw6ZgyS6rbwfU8/j3Dimva1QCeJp/q
QLYop9bSxQYnMoe1xqtgho0=
=l7UR
-----END PGP SIGNATURE-----

Re: continuous reading feature

[Charles Hallenbeck]

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


Steve,

Interesting. Seems like the tutorial is no longer current and describes 
things that have changed substantially since it was written. However I 
found the keymap file, now called speakup.map in my source tree, and in 
fact the last line binds the speakup+r key combination to read-all-doc 
instead of just read-all. Also, I find I have a console-tools package 
instead of kbd, which seems to be newer and replaces it. So I am really 
confused now, and will have to defer to others to figure this one out.



On Mon, Jun 19, 2006 at 07:27:30AM -0700, Steve Holmes wrote:
> The most recent versions of keymap.map in the speakup directory has
> speakup-R listed at the bottom of the list.
> 
> I don't think this gets generated automatically though I saw some stuff
> in the Makefile for it.  In fact, I recently had to manually compile the
> genmap.c program in order to regen my keymap.  I have a keymap that I
> modified the laptop keys to be more clearly mapped and I included the
> read-all key in there as well.  The keymap tutorial explains all how to
> build the keymap and I then explicitly copied the generated map into my
> /proc/keymap and backup directories so I don't lose them.
> 
> On Mon, Jun 19, 2006 at 07:38:34AM -0400, Charles Hallenbeck wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > 
> > Mike,
> > 
> > The keymap tutorial seems pretty clear if a change needs to be made. I 
> > guess the speakup+r key needs to be bound to something. What should it 
> > be bound to?
> > 
> > Thanks,
> > Chuck
> > 
> > On Mon, Jun 19, 2006 at 06:46:42AM -0400, MICHAEL MCDONALD wrote:
> > > I'm not sure about the keymap issue.  I don't know if that is done
> > > automatically when you rebuild speakup or if some procedure needs to be
> > > done to rebuild it.  Maybe Kirk can give a better answer on this one.
> > > 
> > > I have the read all command working, but only for a few of the synths. 
> > > When I finished read all, I asked if there was anyone to help with the
> > > development of the other synths, but I never got much of a response.  I
> > > can give you the status as I know it.  Dectalk, doubletalk, and litetalk
> > > should work as far as I know.  I have all 3 synths, so I can test these
> > > easily.  Speakout has been implemented, but there are some issues and it
> > > seems to behave differently with different kernels, but I don't have one
> > > to try and fix the issues..  Speech Dispatcher should work with
> > > Festival.  It should be fairly easy to implement other synths, but since
> > > I don't have access to them, I haven't been able to implement them.
> > > 
> > > Mike
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > - -- 
> > The Moon is Waning Crescent (40% of Full)
> > Get downloads from http://www.mhcable.com/~chuckh
> >   and remember, INFORMATION WANTS TO BE FREE!
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.3 (GNU/Linux)
> > 
> > iD8DBQFEloy6XnuiIOyDVQURAlu0AJ0coxk1VkXPN8Bzk0N8b1M1UkLyPgCcD4fh
> > 6oiNOGwhve/Lt5HggRMfX7w=
> > =OLW0
> > -----END PGP SIGNATURE-----
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > 
> 
> -- 
> HolmesGrown Solutions
> The best solutions for the best price!
> http://holmesgrown.ld.net/
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
The Moon is Waning Crescent (38% of Full)
Get downloads from http://www.mhcable.com/~chuckh
  and remember, INFORMATION WANTS TO BE FREE!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFElsK0XnuiIOyDVQURAnODAJ9ZAfP9bDoBgu8J5uJcoR9TtYDy8gCfUJL0
F/V9/diluybHAiD81NGFHIY=
=/S2T
-----END PGP SIGNATURE-----

Re: continuous reading feature

[Gregory Nowak]

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

As Chuck has pointed out, the keymap tutorial is out of date, and
keymap.map has in fact been replaced by speakupmap.map. Also, the
speakup+r key is in fact listed at the very bottom.

The last time when I asked about this, and said I got no instructions,
I did in fact try compiling genmap.c, but ran into problems doing so,
which I don't remember anymore, but I'm sure I described them in that
long ago post, which is probably still in the archives somewhere. Anyway,
I've tried it again, and have gotten speakup+r working this time
around. So, here's what I did; it's very simple really.

1. cd to /usr/src/linux/drivers/char/speakup

2. If you have a recent version of speakup, speakupmap.map should
already have speakup+r defined as the last line, so you shouldn't need
to do anything.

3. Compile genmap.c by running:

gcc -o genmap genmap.c

4. Generate the keymap, placing the output in a file called keymap in
the current directory by running:

./genmap speakupmap.map >keymap

5. Finally, copy your new keymap to /proc/speakup/keymap by typing:

cat keymap >/proc/speakup/keymap

That's it, you should have speakup+r working now.

There are a couple of questions that I have, that maybe someone can
answer.

1. How do you stop speakup+r from reading? I thought it was done with
the escape key, but both that, and speakup+r itself don't stop it. I
had to finally use ctrl+c once I got to the end of the document in
emacs, and I'm pretty sure that this isn't how it should be done,
since that would have the probably unwanted side-effect of terminating
the currently foreground application.

2. How do I preserve my keymap changes across reboots? Do I need a
line in my boot scripts to copy it to /proc/speakup/keymap every time,
or is there a more permanent way of doing this, such as including it
in the kernel?

Greg


On Mon, Jun 19, 2006 at 07:27:30AM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> The most recent versions of keymap.map in the speakup directory has
> speakup-R listed at the bottom of the list.
> 
> I don't think this gets generated automatically though I saw some stuff
> in the Makefile for it.  In fact, I recently had to manually compile the
> genmap.c program in order to regen my keymap.  I have a keymap that I
> modified the laptop keys to be more clearly mapped and I included the
> read-all key in there as well.  The keymap tutorial explains all how to
> build the keymap and I then explicitly copied the generated map into my
> /proc/keymap and backup directories so I don't lose them.
> 

- -- 
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.3 (GNU/Linux)

iD8DBQFEluPg7s9z/XlyUyARAhfYAJ91W0UehlLFenmp6NXHvk8JS1WijQCdEqYg
0JWQHTPivkhl/DBbJAdnOrw=
=k0zE
-----END PGP SIGNATURE-----

Re: continuous reading feature

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I would be willing to update the keymap tutorial in a few days.
Actually, when I read it, it didn't seem to far off to me.  I'll have to
check file names and the like.  Greg, the steps you outlined are
basically what I did last week when I dealt with all this.  The only
hitch I seemed to have was the keymap proc variable didn't seem to take
effect right away.  I'm not quite sure what was happening but I would
replace the proc variable and the old map seemed to persist.  Once I
rebooted the box and had the new map in my holding areas for my backed
up proc variables, then all was fine.

I really wonder why genmap.c doesn't get compiled with the Speakup
Makefile.  I saw the target in there.  I'll have to look further and see
why.

On Mon, Jun 19, 2006 at 10:50:24AM -0700, Gregory Nowak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> As Chuck has pointed out, the keymap tutorial is out of date, and
> keymap.map has in fact been replaced by speakupmap.map. Also, the
> speakup+r key is in fact listed at the very bottom.
> 
> The last time when I asked about this, and said I got no instructions,
> I did in fact try compiling genmap.c, but ran into problems doing so,
> which I don't remember anymore, but I'm sure I described them in that
> long ago post, which is probably still in the archives somewhere. Anyway,
> I've tried it again, and have gotten speakup+r working this time
> around. So, here's what I did; it's very simple really.
> 
> 1. cd to /usr/src/linux/drivers/char/speakup
> 
> 2. If you have a recent version of speakup, speakupmap.map should
> already have speakup+r defined as the last line, so you shouldn't need
> to do anything.
> 
> 3. Compile genmap.c by running:
> 
> gcc -o genmap genmap.c
> 
> 4. Generate the keymap, placing the output in a file called keymap in
> the current directory by running:
> 
> ./genmap speakupmap.map >keymap
> 
> 5. Finally, copy your new keymap to /proc/speakup/keymap by typing:
> 
> cat keymap >/proc/speakup/keymap
> 
> That's it, you should have speakup+r working now.
> 
> There are a couple of questions that I have, that maybe someone can
> answer.
> 
> 1. How do you stop speakup+r from reading? I thought it was done with
> the escape key, but both that, and speakup+r itself don't stop it. I
> had to finally use ctrl+c once I got to the end of the document in
> emacs, and I'm pretty sure that this isn't how it should be done,
> since that would have the probably unwanted side-effect of terminating
> the currently foreground application.
> 
> 2. How do I preserve my keymap changes across reboots? Do I need a
> line in my boot scripts to copy it to /proc/speakup/keymap every time,
> or is there a more permanent way of doing this, such as including it
> in the kernel?
> 
> Greg
> 
> 
> On Mon, Jun 19, 2006 at 07:27:30AM -0700, Steve Holmes wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: RIPEMD160
> > 
> > The most recent versions of keymap.map in the speakup directory has
> > speakup-R listed at the bottom of the list.
> > 
> > I don't think this gets generated automatically though I saw some stuff
> > in the Makefile for it.  In fact, I recently had to manually compile the
> > genmap.c program in order to regen my keymap.  I have a keymap that I
> > modified the laptop keys to be more clearly mapped and I included the
> > read-all key in there as well.  The keymap tutorial explains all how to
> > build the keymap and I then explicitly copied the generated map into my
> > /proc/keymap and backup directories so I don't lose them.
> > 
> 
> - -- 
> 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.3 (GNU/Linux)
> 
> iD8DBQFEluPg7s9z/XlyUyARAhfYAJ91W0UehlLFenmp6NXHvk8JS1WijQCdEqYg
> 0JWQHTPivkhl/DBbJAdnOrw=
> =k0zE
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://holmesgrown.ld.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFElyv5WSjv55S0LfERAy6mAKCqeZqmlaDWgOsIfAiOVRde5EM4jwCgjY9i
90KwU8N1wRo8ERrGfg03qsM=
=1zKI
-----END PGP SIGNATURE-----

Re: continuous reading feature

[Ameer Armaly]

As for preserving your keymap changes, as far as I know it all works like 
this:  genmap produces speakupmap.h, which is later included by the code as 
the default keymap; so at least in theory any changes you make to 
speakupmap.map should take effect when you recompile.
----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, June 19, 2006 1:50 PM
Subject: Re: continuous reading feature


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> As Chuck has pointed out, the keymap tutorial is out of date, and
> keymap.map has in fact been replaced by speakupmap.map. Also, the
> speakup+r key is in fact listed at the very bottom.
>
> The last time when I asked about this, and said I got no instructions,
> I did in fact try compiling genmap.c, but ran into problems doing so,
> which I don't remember anymore, but I'm sure I described them in that
> long ago post, which is probably still in the archives somewhere. Anyway,
> I've tried it again, and have gotten speakup+r working this time
> around. So, here's what I did; it's very simple really.
>
> 1. cd to /usr/src/linux/drivers/char/speakup
>
> 2. If you have a recent version of speakup, speakupmap.map should
> already have speakup+r defined as the last line, so you shouldn't need
> to do anything.
>
> 3. Compile genmap.c by running:
>
> gcc -o genmap genmap.c
>
> 4. Generate the keymap, placing the output in a file called keymap in
> the current directory by running:
>
> ./genmap speakupmap.map >keymap
>
> 5. Finally, copy your new keymap to /proc/speakup/keymap by typing:
>
> cat keymap >/proc/speakup/keymap
>
> That's it, you should have speakup+r working now.
>
> There are a couple of questions that I have, that maybe someone can
> answer.
>
> 1. How do you stop speakup+r from reading? I thought it was done with
> the escape key, but both that, and speakup+r itself don't stop it. I
> had to finally use ctrl+c once I got to the end of the document in
> emacs, and I'm pretty sure that this isn't how it should be done,
> since that would have the probably unwanted side-effect of terminating
> the currently foreground application.
>
> 2. How do I preserve my keymap changes across reboots? Do I need a
> line in my boot scripts to copy it to /proc/speakup/keymap every time,
> or is there a more permanent way of doing this, such as including it
> in the kernel?
>
> Greg
>
>
> On Mon, Jun 19, 2006 at 07:27:30AM -0700, Steve Holmes wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: RIPEMD160
>>
>> The most recent versions of keymap.map in the speakup directory has
>> speakup-R listed at the bottom of the list.
>>
>> I don't think this gets generated automatically though I saw some stuff
>> in the Makefile for it.  In fact, I recently had to manually compile the
>> genmap.c program in order to regen my keymap.  I have a keymap that I
>> modified the laptop keys to be more clearly mapped and I included the
>> read-all key in there as well.  The keymap tutorial explains all how to
>> build the keymap and I then explicitly copied the generated map into my
>> /proc/keymap and backup directories so I don't lose them.
>>
>
> - -- 
> 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.3 (GNU/Linux)
>
> iD8DBQFEluPg7s9z/XlyUyARAhfYAJ91W0UehlLFenmp6NXHvk8JS1WijQCdEqYg
> 0JWQHTPivkhl/DBbJAdnOrw=
> =k0zE
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: continuous reading feature

[Charles Hallenbeck]

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

Greg,
Terrific. Thanks for this. I will give that a shot, and hopefully your 
new questions will get an answer. 

I seem to recall that just pressing either control or alt would stop the 
reading, or maybe it was just space, but it was many moons ago that the 
feature got any discussion.

Chuck


On Mon, Jun 19, 2006 at 10:50:24AM -0700, Gregory Nowak wrote:
> As Chuck has pointed out, the keymap tutorial is out of date, and
> keymap.map has in fact been replaced by speakupmap.map. Also, the
> speakup+r key is in fact listed at the very bottom.
> 
> The last time when I asked about this, and said I got no instructions,
> I did in fact try compiling genmap.c, but ran into problems doing so,
> which I don't remember anymore, but I'm sure I described them in that
> long ago post, which is probably still in the archives somewhere. Anyway,
> I've tried it again, and have gotten speakup+r working this time
> around. So, here's what I did; it's very simple really.
> 
> 1. cd to /usr/src/linux/drivers/char/speakup
> 
> 2. If you have a recent version of speakup, speakupmap.map should
> already have speakup+r defined as the last line, so you shouldn't need
> to do anything.
> 
> 3. Compile genmap.c by running:
> 
> gcc -o genmap genmap.c
> 
> 4. Generate the keymap, placing the output in a file called keymap in
> the current directory by running:
> 
> ./genmap speakupmap.map >keymap
> 
> 5. Finally, copy your new keymap to /proc/speakup/keymap by typing:
> 
> cat keymap >/proc/speakup/keymap
> 
> That's it, you should have speakup+r working now.
> 
> There are a couple of questions that I have, that maybe someone can
> answer.
> 
> 1. How do you stop speakup+r from reading? I thought it was done with
> the escape key, but both that, and speakup+r itself don't stop it. I
> had to finally use ctrl+c once I got to the end of the document in
> emacs, and I'm pretty sure that this isn't how it should be done,
> since that would have the probably unwanted side-effect of terminating
> the currently foreground application.
> 
> 2. How do I preserve my keymap changes across reboots? Do I need a
> line in my boot scripts to copy it to /proc/speakup/keymap every time,
> or is there a more permanent way of doing this, such as including it
> in the kernel?
> 
> Greg
> 
> 
> On Mon, Jun 19, 2006 at 07:27:30AM -0700, Steve Holmes wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: RIPEMD160
> > 
> > The most recent versions of keymap.map in the speakup directory has
> > speakup-R listed at the bottom of the list.
> > 
> > I don't think this gets generated automatically though I saw some stuff
> > in the Makefile for it.  In fact, I recently had to manually compile the
> > genmap.c program in order to regen my keymap.  I have a keymap that I
> > modified the laptop keys to be more clearly mapped and I included the
> > read-all key in there as well.  The keymap tutorial explains all how to
> > build the keymap and I then explicitly copied the generated map into my
> > /proc/keymap and backup directories so I don't lose them.
> > 
> 
> -- 
> 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
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
The Moon is Waning Crescent (34% of Full)
Get downloads from http://www.mhcable.com/~chuckh
  and remember, INFORMATION WANTS TO BE FREE!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFElzRFXnuiIOyDVQURAhY7AJ9GQr7hWWtU54gI9QRdWUvsc477DwCfd+RL
ZEM/PnXTMs09DGVDO2l0Xqg=
=pXTm
-----END PGP SIGNATURE-----

Re: continuous reading feature

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I don't remember the exact role of speakupmap.h or genmap.h or whatever
it is, but one thing I know so far is typing gcc -o genmap genmap.c
compiles and leaves you with an executable module called genmap.  I put
that in my /usr/local/bin so I could execute at will.  I then do a
genmap speakupmap.map >keymap and that keymap file can be placed into
/proc/speakup and your holding places for speakupconf to load the next
time you boot and away we go.

If anyone else wants to clarify some of this for sure, I can try and
update the keymap tutorial and we can get it included in the next
updates to speakup.

On Mon, Jun 19, 2006 at 07:10:25PM -0400, Ameer Armaly wrote:
> As for preserving your keymap changes, as far as I know it all works like 
> this:  genmap produces speakupmap.h, which is later included by the code as 
> the default keymap; so at least in theory any changes you make to 
> speakupmap.map should take effect when you recompile.

- -- 
HolmesGrown Solutions
The best solutions for the best price!
http://holmesgrown.ld.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFEl13FWSjv55S0LfERAyZuAJ9sFSTGmpc2qDWvZReVSKO6njH6JgCg6x3n
5Rbal1hACxzPc6npYeSa3DI=
=CFMB
-----END PGP SIGNATURE-----

Re: continuous reading feature

[MICHAEL MCDONALD]

>1. How do you stop speakup+r from reading? I thought it was done with
>the escape key, but both that, and speakup+r itself don't stop it. I
>had to finally use ctrl+c once I got to the end of the document in
>emacs, and I'm pretty sure that this isn't how it should be done,
>since that would have the probably unwanted side-effect of
terminating
>the currently foreground application.

To stop the read all command just hit the ctrl key.  Actually I think
most single key presses should stop it, but I believe I have it set up
to act based on the ctrl key.


>2. How do I preserve my keymap changes across reboots? Do I need a
>line in my boot scripts to copy it to /proc/speakup/keymap every
time,
>or is there a more permanent way of doing this, such as including it
>in the kernel?

There is a way to compile speakup into the kernel so that the keymap
comes up everytime.  Basically you replace the existing keymap and
recompile the kernel.  I don't remember the exact sequence to make it
work though.

Re: continuous reading feature

[Gregory Nowak]

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

- From what I recall, the continuous reading feature should work with the
doubletalk pc. However, I also get just an r, when pressing
speakup+r. When I mentioned this when the feature was first made
available, Mike said that I needed to regenerate my keymap. However,
when I asked how to do this, I didn't get any instructions, and
searching the web didn't produce anything either. I thought that
building speakup into the kernel automatically generated a keymap, but
maybe I'm wrong there.

Greg



On Sat, Jun 17, 2006 at 05:09:10AM -0400, Charles Hallenbeck wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> > > but it seems not to be activated "out of the box".
> > 
> > Speakup key + R.
> > -- 
> 
> All I get is the letter 'r' when I do that. Does speakup+r work for 
> others? Why not for me? 
> 
> 
> - -- 
> The Moon is Waning Gibbous (64% of Full)
> Get downloads from http://www.mhcable.com/~chuckh
>   and remember, INFORMATION WANTS TO BE FREE!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> 
> iD8DBQFEk8a2XnuiIOyDVQURArD4AJ9ndUpMSwrlykgFzrlIdfwYYbAq4wCdFnRl
> Z2wGRZYKdOJwuoi4U/GX+u4=
> =ZVfm
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
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.3 (GNU/Linux)

iD8DBQFElFmz7s9z/XlyUyARAjXnAJ4hQK9G13NDFRnb+vCEyC61KMfoxwCeIk05
12aCBTIjsZYz5pdDgLqiW8A=
=tTCc
-----END PGP SIGNATURE-----

Re: continuous reading feature

[Charles Hallenbeck]

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

On Sat, Jun 17, 2006 at 12:24:18PM +1000, Luke Yelavich wrote:
> On Sat, Jun 17, 2006 at 11:17:32AM EST, Charles Hallenbeck wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > I am using a 2.6.16 kernel patched with speakup from a few weeks ago. 
> > Can someone please tell me how to activate the continuous read feature 
> > that Mike McDonald contributed? Is there somewhere I can read about it? 
> > It occurred to me that this feature would be a nice match to edbrowse, 

> > but it seems not to be activated "out of the box".
> 
> Speakup key + R.
> -- 

All I get is the letter 'r' when I do that. Does speakup+r work for 
others? Why not for me? 


- -- 
The Moon is Waning Gibbous (64% of Full)
Get downloads from http://www.mhcable.com/~chuckh
  and remember, INFORMATION WANTS TO BE FREE!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEk8a2XnuiIOyDVQURArD4AJ9ndUpMSwrlykgFzrlIdfwYYbAq4wCdFnRl
Z2wGRZYKdOJwuoi4U/GX+u4=
=ZVfm
-----END PGP SIGNATURE-----

Re: continuous reading feature

[Luke Yelavich]

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

On Sat, Jun 17, 2006 at 11:17:32AM EST, Charles Hallenbeck wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I am using a 2.6.16 kernel patched with speakup from a few weeks ago. 
> Can someone please tell me how to activate the continuous read feature 
> that Mike McDonald contributed? Is there somewhere I can read about it? 
> It occurred to me that this feature would be a nice match to edbrowse, 
> but it seems not to be activated "out of the box".

Speakup key + R.
- -- 
Luke Yelavich
GPG key: 0xD06320CE 
	 (http://www.themuso.com/themuso-gpg-key.txt)
Email & MSN: themuso@themuso.com
ICQ: 18444344
Jabber: themuso@jabber.org.au
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEk2fSjVefwtBjIM4RAmLWAJ9TTu+cyWXns4ICRDStC4NVw1rB+ACeMHlI
iwSB8pBpoxUr8sjphD/GbH4=
=A8T8
-----END PGP SIGNATURE-----

continuous reading feature

[Charles Hallenbeck]

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

I am using a 2.6.16 kernel patched with speakup from a few weeks ago. 
Can someone please tell me how to activate the continuous read feature 
that Mike McDonald contributed? Is there somewhere I can read about it? 
It occurred to me that this feature would be a nice match to edbrowse, 
but it seems not to be activated "out of the box".

Thanks,
Chuck

- -- 
The Moon is Waning Gibbous (68% of Full)
Get downloads from http://www.mhcable.com/~chuckh
  and remember, INFORMATION WANTS TO BE FREE!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEk1gsXnuiIOyDVQURAhbkAJ9UbuOpKRfab77t4TR46LXLXJseLgCfQyrk
CND5Gd7PeoYj8VQgdhsRnhM=
=Irxf
-----END PGP SIGNATURE-----