[j-say list] Re: improvement for the next version of J-say Pro
- From: "Chris Jenkins" <saveup@xxxxxxxxxxxxxx>
- To: <j-say@xxxxxxxxxxxxx>
- Date: Sun, 22 Oct 2006 04:08:58 -0400
Hello Brian.
Another problem that I have is when I bring a phrase into the correction
dialog box I cannot remember the word number of the word I need to correct.
This may just be something I need to learn and I probably will. But I hope
to see a say previous word and say next word command while in the
correction dialog box in a future version. I know that this command exists
already the only problem is it does not have the word selected so you can
type over it.
Once again I still say I am enjoying this new version of J-say Pro. It is
just my opinion to make problems known very early so they will stand a
better chance of being included in the next version.
Thank you for reading.
Chris.
-----Original Message-----
From: j-say-bounce@xxxxxxxxxxxxx [mailto:j-say-bounce@xxxxxxxxxxxxx] On
Behalf Of Brian Hartgen
Sent: Sunday, October 22, 2006 3:31 AM
To: j-say@xxxxxxxxxxxxx
Subject: [j-say list] Re: improvement for the next version of J-say Pro
Hi Sue
I hope as from this version however you will be saying "cancel that" rather
than "click cancel" (smile). I am sure you will.
We think it is quite important to teach people to use the J-Say phrasing as
opposed to the Dragon phrasing and I am sure we will be extending this kind
of terminology in the coming versions. As Terry eloquently said in his part
of the Main Menu presentation, we hope that people will think that they are
using J-Say, as opposed to JAWS and Dragon. To follow this example a
little, the term "click cancel" means nothing to a blind person because they
do not click anything. However "cancel that" is more effective.
I think that now we have the special command interface in place, and
additional tools such as J-Say contacts, this is the start of working
towards a very dedicated interface for non-visual voice input/output users.
But to return to the original point Chris made, we will certainly look at
this. We have put in a lot of extra code because there were many situations
(in this varied depending upon the Office version being used) where if you
were dictating in the body field, on exiting the correction box Dragon would
move to an alternative field. We have tried to put some checks in to
rectify this situation should it happen and I am sure access to the
correction box will be an ongoing issue we will work on in every upcoming
version in some form or another.
Brian Hartgen
MSN: brian@xxxxxxxxxxx
SKYPE: brianhartgen
SKYPE IN UK: 0208-133-7186
SKYPE IN US: 213-985-3581
----- Original Message -----
From: "Sue Martin" <smartin27@xxxxxxxxxx>
To: <j-say@xxxxxxxxxxxxx>
Sent: Sunday, October 22, 2006 7:49 AM
Subject: [j-say list] Re: improvement for the next version of J-say Pro
> Chris,
>
> I've experienced the same thing. In fact it happened during a
> presentation
> in Los Angeles last March. What I did then and what I still do is simply
> say, "click cancel," and then try again. No idea why it happens but there
> you are.
>
> -----Original Message-----
> From: j-say-bounce@xxxxxxxxxxxxx [mailto:j-say-bounce@xxxxxxxxxxxxx]On
> Behalf Of Chris Jenkins
> Sent: Sunday, October 22, 2006 1:18 AM
> To: j-say@xxxxxxxxxxxxx
> Subject: [j-say list] improvement for the next version of J-say Pro
>
>
> Sometimes when I'm in the body of an e-mail message and I have to go into
> the correction dialog box I still get excessive chatter while in the
> correction dialog box. What I mean by excessive chatter is a lot more
> than
> box open and box closed. If it matters to my knowledge I have everything
> set up correctly within Microsoft Outlook 2003. This behavior only
> happens
> when it wants to. I have not taken the time yet to track down when it
> happens and when it does not. I know it happened when I was replying to a
> e-mail message while ago. But it did not happen while writing this e-mail
> message.
>
> Thank you for reading.
>
> Chris.
>
>
>
>
>
__________ NOD32 1.1822 (20061021) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
Other related posts:
