Yeah It's horrible under the winblows console. Sometimes it doesn't read the whole screen, and deffinately not the whole command prompt. I get "w>" instead of "c:\windows>". ----- Original Message ----- From: "Janina Sajka" <janina@xxxxxxx> To: <speakup at braille.uwo.ca> Sent: Tuesday, May 21, 2002 10:03 AM Subject: Re: interesting experiment. > A better solution would be to get ASAP instead of JAWS for DOS. > But that would cost you more than a Doubletalk internal card > which would allow you to use Linux and Speakup natively. Your > real problem is that lame excuse of a DOS screen reader called > JAWS. > > On Mon, 20 May 2002, Octavian Rasnita wrote: > > > Yes I am connecting to the Linux machine but not with the default Telnet > > included in Windows. I use SecureCRT and I use SSH2 protocol to work under > > Linux. > > The program is pretty accessible, but of course it is not very friendly to > > use because I have to read the screen with the mouse cursor (the Jaws > > cursor). > > > > I know a better solution would be to install NCSA Telnet for DOS. > > That program works fine under DOS and I heard that it is easier to use than > > a windows program. > > > > I've downloaded it, but I need to configure it and I need to find a good DOS > > screen reader. > > This won't be such a big problem, but the main idea is that I would like to > > use only the Linux machine, not 2 computers in the same time. > > > > I am willing to try more screen readers and sinthesizers, and as a matter of > > fact, I would like to try the mbrola sinthesizer because I heard that it has > > support for my native language, but I am afraid that I could broke > > something, and then I won't be able to have the emacspeak back. > > > > I've seen some help files telling me that I should "compile" something ... > > Well, here I am lost. How to compile? > > I heard that there is another screen reader named Jupiter that works with > > the mbrola sinthesizer, but I am not sure here, and I heard that it is a > > real screen reader, not like emacspeak. > > > > I am hoping 2 things: > > 1. The GUI will be accessible for the blind and it won't be necessary a > > hardware sinthesizer. > > 2. The software sinthesizer will work with a newly created screen reader > > for the GUI. > > > > If this won't happend very soon, I hope I could use Jupiter with mbrola and > > I hope it sounds well. > > > > I think I need to clear a little why I need so much a good voice easy to > > understand. > > I am not a native english speaker and I don't speak english at all. I only > > type in english and I listen the screen reader. > > Well, there is no support for my native language and I listen to romanian > > texts with the english sinthesizer. I think you imagine how well it sounds. > > Now I am used to listen to romanians texts in english with a pretty high > > speed, and IBM Via voice sounds almost like the eloquence sinthesizer and > > that's why I like it. > > If I need to read romanian texts in eenglish with the Dec Talk sinthesizer, > > I can't understand almost anything. > > > > In fact, it is hard to understand english texts also. The old Dec Talk > > doesn't sound as well as the new ones. > > > > > > > > Teddy, > > orasnita at home.ro > > > > ----- Original Message ----- > > From: "Janina Sajka" <janina at afb.net> > > To: <speakup at braille.uwo.ca> > > Sent: Monday, May 20, 2002 7:38 AM > > Subject: Re: interesting experiment. > > > > > > Greg: > > > > I'm pretty sure he isn't using Speakup. He doesn't have a > > supported synth. He telnets from his Windows machine, as I > > recall, and he's tried using ViaVoice directly with emacspeak. Of > > course, the latter is a very steep learning curve. > > > > Still, he's got the DEC Talk internal, and emacs with or without > > emacspeak is worth learning. Without emacspeak, he can run it > > over telnet--but I doubt JFW is all that great as a telnet > > client's screen review program. Also, the default Microsoft > > telnet is pretty lame. I would think this setup is fraught with > > frustration. > > > > So, emacspeak with that DEC Talk is probably his smartest option > > right now, with the telnet as a back up to avoid rebooting. > > > > I have also suggest yasr and eflite, but he's insisting on > > nothing less than Eloquence for free, so the DEC Talk is probably > > the best compromise. > > > > Another option would be a better screen reader for telnet and a > > better telnet client. That would mean a good DOS screen reader > > like asap or Vocal-Eyes, assuming he can actually run DOS on that > > Windows machine. Neither of those is very cheap, though, and > > spending that much money would be dumb, because he could get a > > good Doubletalk for less than the cost of that software. > > > > On Sun, 19 May 2002, Gregory Nowak wrote: > > > > > We're all assuming he's using speakup since he's here. But from all of > > Tedy's comments in other posts, I am beginning to get the impression that > > he's not, since he seems to be asking for screen readers which support > > software tts. > > > Greg > > > > > > > > > On Sun, May 19, 2002 at 10:58:09PM -0400, Deedra Waters wrote: > > > > Try man < emacs|less then use the speakup keys to read line by line, or > > > > word by word if you wish. you can bring up the next page by hitting the > > > > space bar. > > > > > > > > > > > > On Mon, 20 May 2002, Octavian Rasnita wrote: > > > > > > > > > Please enlighten me. > > > > > I never used the Jaws cursor in the new HTML help format under > > Windows. > > > > > Select an item in the tree view, press enter, then press F6 and it > > will > > > > > automaticly start reading that help item. It is a simple HTML file > > there, > > > > > and it works exactly as simple as Internet Explorer. > > > > > You don't need the Jaws cursor at all. > > > > > > > > > > You needed the Jaws cursor only for some bad designed help files in > > the old > > > > > .hlp format. > > > > > Now in the new .chm format, you don't have any problems. > > > > > > > > > > But this doesn't matter too much. Please tell me how to navigate the > > man > > > > > pages. > > > > > I type man mv, for example. > > > > > It starts to print all the help file, but maybe I want to move with a > > page > > > > > up then down, etc. > > > > > > > > > > I know this is possible. Thanks. > > > > > Teddy, > > > > > orasnita at home.ro > > > > > > > > > > ----- Original Message ----- > > > > > From: "Shaun Oliver" <shaun_oliver at optusnet.com.au> > > > > > To: <speakup at braille.uwo.ca> > > > > > Sent: Sunday, May 19, 2002 8:05 AM > > > > > Subject: Re: interesting experiment. > > > > > > > > > > > > > > > SNIP > > > > > > > You open a window, and it explains you what you should do there. > > > > > > > You have to press the space bar to check some checkboxes, to press > > some > > > > > > > buttons, etc, and if you don't know something, press shift+f10 (or > > the > > > > > right > > > > > > > mouse button and choose "what's this?" or press F1 to view the > > help file > > > > > > > wich is much much more easier to navigate than the man pages under > > > > > Linux. > > > > > SNIP > > > > > > > > > > A fake. > > > > > man pages under GNU/Linux are a lot easier to navigate than windows > > help > > > > > pages. > > > > > you need to route the jaws cursor to the pc and then fart around > > trying to > > > > > find what you were looking for. > > > > > even with the new features in jfw I seriously doubt you could navigate > > a > > > > > help file easier than a man page.. > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Speakup mailing list > > > > > Speakup at braille.uwo.ca > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Speakup mailing list > > > > > Speakup at braille.uwo.ca > > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup at braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup at braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > -- > > > > Janina Sajka, Director > > Technology Research and Development > > Governmental Relations Group > > American Foundation for the Blind (AFB) > > > > Email: janina at afb.net Phone: (202) 408-8175 > > > > Chair, Accessibility SIG > > Open Electronic Book Forum (OEBF) > > http://www.openebook.org > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > -- > > Janina Sajka, Director > Technology Research and Development > Governmental Relations Group > American Foundation for the Blind (AFB) > > Email: janina at afb.net Phone: (202) 408-8175 > > Chair, Accessibility SIG > Open Electronic Book Forum (OEBF) > http://www.openebook.org > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >
