feature request

feature request

[Doug Smith]

, folks.   I have just a little request to make here.  Is it possible
that the next version of speakup can be done such that it will work in
a kernel with the preempt on, so that I won't have to compile a new
kernel in order to get it to work without spelling the words.  It
jumps in and out of a crazy spelling mode because of the preempt
feature of the kernel being on.  I am not going to re-compile a kernel
that works on a system where nothing else is wrong.  

If there is a way to fix this without building a new kernel, please
tell me how to do it.  



Thanks. 




-- 
Doug Smith: C.S.F.C.
Computer Scientist For CHRIST

Re: feature request

[Samuel Thibault]

Doug Smith, le Thu 06 Sep 2007 12:32:51 -0400, a écrit :
> , folks.   I have just a little request to make here.  Is it possible
> that the next version of speakup can be done such that it will work in
> a kernel with the preempt on, so that I won't have to compile a new
> kernel in order to get it to work without spelling the words.

This is already the case in the git repository.

Samuel

Re: feature request

[Adam Myrow]

Actually, I've never had any problems with a hardware synthesizer.  In my 
case, a Dectalk USB in serial mode emulating a Dectalk Express.  It has 
its quirks, but spelling words is not one of them.  So, I suspect the 
problem was more with software speech than hardware speech.  I think 
software speech is more sensitive to timing, whereas with the Dectalk, all 
that is needed is to dump text at a serial port and let the synthesizer 
decide what to do with it.

Re: Feature Request

[Sean McMahon]

Agreed!  And while we're on the subject of features, can you make speakup tell
you you're on a space char?  That is with current char command.Seems when I go
back and forth between words I can't always tell where my cursor is landing.
----- Original Message ----- 
From: "Janina Sajka" <janina@rednote.net>
To: <speakup@braille.uwo.ca>
Sent: Saturday, April 02, 2005 8:25 AM
Subject: Feature Request


> I'm finding I would appreciate a slightly different behavior from the
> "read current word" key in Speakup.
>
> In the instance when current word is a single char, I would like it to
> acknowledge upper and lower case differences. In other words, I think 5
> should behave exactly as 2 does, when the current-word is actually a
> single-char in upper case.
>
> Thoughts?
>
>
> -- 
>
> Janina Sajka Phone: +1.202.494.7040
> Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
>
> Chair, Accessibility Workgroup Free Standards Group (FSG)
> janina@freestandards.org http://a11y.org
>
> If Linux can't solve your computing problem, you need a different problem.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

RE: Feature Request

[jim grimsby]

Agreed 

-----Original Message-----
From: speakup-bounces@braille.uwo.ca
[mailto:speakup-bounces@braille.uwo.ca] On Behalf Of Janina Sajka
Sent: Saturday, April 02, 2005 7:26 AM
To: speakup@braille.uwo.ca
Subject: Feature Request


I'm finding I would appreciate a slightly different behavior from the
"read current word" key in Speakup.

In the instance when current word is a single char, I would like it to
acknowledge upper and lower case differences. In other words, I think 5
should behave exactly as 2 does, when the current-word is actually a
single-char in upper case.

Thoughts?


-- 

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC
http://www.CapitalAccessibility.Com

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

If Linux can't solve your computing problem, you need a different
problem.


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup

Feature Request

[Janina Sajka]

I'm finding I would appreciate a slightly different behavior from the
"read current word" key in Speakup.

In the instance when current word is a single char, I would like it to
acknowledge upper and lower case differences. In other words, I think 5
should behave exactly as 2 does, when the current-word is actually a
single-char in upper case.

Thoughts?


-- 

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

If Linux can't solve your computing problem, you need a different problem.

Re: Feature Request

[Chuck Hallenbeck]

It makes more sense to me to know where the non-blank data begin instead
of how many spaces precede it.


On Fri, 8 Oct 2004, Tyler Spivey wrote:

> Just wanted to point out something: double keypad 8 has a small problem,
> in my opinion.
> take the following lines:
> def fact(n):
> 	return [f for f in xrange(1,n+1) if n%f == 0]
> using double keypad 8 on the first line yields 1.
> the second line yeilds 9.
> I feel that knowing how much whitespace is on the line, and not where the first character is and having to subtract 1,
> is more useful.
> all that needs to be done in the speakup code is subtract 1 from the value before sending it.
> Thanks,
> Tyler
> On Fri, Oct 08, 2004 at 11:54:17AM -0400, Janina Sajka wrote:
>> Thanks, David. Double keypad 8 is going to be very helpful! I wasn't
>> aware of it before.
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
The Moon is Waning Crescent (23% of Full)
Home page at http://www.mhcable.com/~chuckh
Speakfreely address 24.105.197.112:2074

Re: Feature Request

[Chuck Hallenbeck]

Janina,

Have you noticed that pressing "say_line" twice in rapid succession will
do what you ask? or nearly so?

Chuck


On Fri, 8 Oct 2004, Janina Sajka wrote:

> Speaking as one who has recently (and with trepidation) cracked a Python
> book or two:
>
> Might Speakup be more helpful regarding white space at the beginning of
> a line? Those who know about such things will immediately recognize that
> this kind of information is critical in languages like Python.
>
> I would suggest two ways to get useful data like this. Either or both
> would do the trick, I'm sure.
>
> 1.)	A configurable toggle to announce, in a different pitched voice,
> the number of white space elements at the beginning of a line. So, for
> two tab chars it would say "two," and for 4 spaces (ASCII 32) it would
> say "four." I believe asap for DOS did something like this.
>
> 2.)	A togglable configuration feature that beeps the speaker. So, 2
> tabs would yield two beeps. This would probably be less valuable in
> circumstances where there are many white space chars -- 8 beeps for 8
> spaces might be less helpful, in other words.
>
> What'ch'ya think, Kirk?
>
> Yes, yes, I know. I should be able to just send you a patch. But, I'm
> just beginning to crack the books! <grin>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
The Moon is Waning Crescent (23% of Full)
Home page at http://www.mhcable.com/~chuckh
Speakfreely address 24.105.197.112:2074

Re: Feature Request

[Janina Sajka]

So, with the double 8 already available, it seems it would be even
easier than I originally thought to make this kind of data automatic.

It's nice to be able to do double 8. It would be even nicer to toggle
the feature on and hear this data, preferably at with some pitch offset,
as one moves around in one's code.

				Janina

Re: Feature Request

[Tyler Spivey]

Just wanted to point out something: double keypad 8 has a small problem,
in my opinion.
take the following lines:
def fact(n):
	return [f for f in xrange(1,n+1) if n%f == 0]
using double keypad 8 on the first line yields 1.
the second line yeilds 9.
I feel that knowing how much whitespace is on the line, and not where the first character is and having to subtract 1,
is more useful.
all that needs to be done in the speakup code is subtract 1 from the value before sending it.
Thanks,
Tyler
On Fri, Oct 08, 2004 at 11:54:17AM -0400, Janina Sajka wrote:
> Thanks, David. Double keypad 8 is going to be very helpful! I wasn't
> aware of it before.

Re: Feature Request

[Janina Sajka]

Thanks, David. Double keypad 8 is going to be very helpful! I wasn't
aware of it before.

David Csercsics writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> >Speaking as one who has recently (and with trepidation) cracked a Python
> >book or two:
> >
> >Might Speakup be more helpful regarding white space at the beginning of
> >a line? Those who know about such things will immediately recognize that
> >this kind of information is critical in languages like Python.
> >
> 
> I like python a lot. Double keypad 8 is very useful for this sort of
> thing. Setting your editor correctly to indent things for you is good too.
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
> 
> iEYEARECAAYFAkFmtScACgkQ7V+Ye7TD5BwuUwCg3ZQ+s9XpeBocUyetve2Fm7nH
> EaMAoJl39yWw36q2MsWyptP0Fj2Akmb+
> =tNWr
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
	
				Janina Sajka, Chair
				Accessibility Workgroup
				Free Standards Group (FSG)

janina@freestandards.org	Phone: +1 202.494.7040

Re: Feature Request

[David Csercsics]

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

>Speaking as one who has recently (and with trepidation) cracked a Python
>book or two:
>
>Might Speakup be more helpful regarding white space at the beginning of
>a line? Those who know about such things will immediately recognize that
>this kind of information is critical in languages like Python.
>

I like python a lot. Double keypad 8 is very useful for this sort of
thing. Setting your editor correctly to indent things for you is good too.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iEYEARECAAYFAkFmtScACgkQ7V+Ye7TD5BwuUwCg3ZQ+s9XpeBocUyetve2Fm7nH
EaMAoJl39yWw36q2MsWyptP0Fj2Akmb+
=tNWr
-----END PGP SIGNATURE-----

Feature Request

[Janina Sajka]

Speaking as one who has recently (and with trepidation) cracked a Python
book or two:

Might Speakup be more helpful regarding white space at the beginning of
a line? Those who know about such things will immediately recognize that
this kind of information is critical in languages like Python.

I would suggest two ways to get useful data like this. Either or both
would do the trick, I'm sure.

1.)	A configurable toggle to announce, in a different pitched voice,
the number of white space elements at the beginning of a line. So, for
two tab chars it would say "two," and for 4 spaces (ASCII 32) it would
say "four." I believe asap for DOS did something like this.

2.)	A togglable configuration feature that beeps the speaker. So, 2
tabs would yield two beeps. This would probably be less valuable in
circumstances where there are many white space chars -- 8 beeps for 8
spaces might be less helpful, in other words.

What'ch'ya think, Kirk?

Yes, yes, I know. I should be able to just send you a patch. But, I'm
just beginning to crack the books! <grin>