public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
* yasr related problem
@  Krishnakant Ramesh Mane
   ` Sergey Fleytin
   ` Lorenzo Prince
  0 siblings, 2 replies; 8+ messages in thread
From: Krishnakant Ramesh Mane @  UTC (permalink / raw)
  To: blinux-list

Hello Mr. Lorenzo,
yes, I got the flite and eflite packages and they are working 
fine.
I am trying to run yasr with the following command
yasr .
I don't know why but even after putting the following lines yasr 
doesn't give any output.
first I commented the line synthesizer = emacspeak server
and I added another line
synthesizer port =| the path to eflite.
I had the instructions in the help docs and I followed this 
installation.
what must be wrong?
does yasr require some parameters to be passed during startup?
Please let me know.


thanks.
Krishnakant.





^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: yasr related problem
   yasr related problem Krishnakant Ramesh Mane
@  ` Sergey Fleytin
   ` Lorenzo Prince
  1 sibling, 0 replies; 8+ messages in thread
From: Sergey Fleytin @  UTC (permalink / raw)
  To: blinux-list

Hi!

>>>>> "KRM" == Krishnakant Ramesh Mane <krmane@rediffmail.com> writes:

KRM> Hello Mr. Lorenzo, yes, I got the flite and eflite packages and
KRM> they are working fine.  I am trying to run yasr with the
KRM> following command yasr .  I don't know why but even after putting
KRM> the following lines yasr doesn't give any output.  first I
KRM> commented the line synthesizer = emacspeak server and I added
KRM> another line synthesizer port =| the path to eflite.  I had the

Don't forget to preceed the path to eflite in 'synthesizer port' line
with a '|' (pipe) sign.

Hope it helps.

-- 
Best regards,

Sergey.




^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: yasr related problem
   yasr related problem Krishnakant Ramesh Mane
   ` Sergey Fleytin
@  ` Lorenzo Prince
  1 sibling, 0 replies; 8+ messages in thread
From: Lorenzo Prince @  UTC (permalink / raw)
  To: blinux-list

Did you comment out the line that says synthesizer=speakout?
It should read something like this:

#synthesizer=speakout
#synthesizer=a few more lines like this
synthesizer=emacspeak server
synthesizer port=|path to eflite

This should give the desired result just by using the yasr command with no
parameters.  Also, be sure you have .yasr.conf in your home directory.

Lorenzo

panic("Foooooooood fight!");
	-- In the kernel source aha1542.c, after detecting a bad segment list




^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: yasr related problem
     ` Mike Gorse
@      ` Brent Harding
  0 siblings, 0 replies; 8+ messages in thread
From: Brent Harding @  UTC (permalink / raw)
  To: blinux-list

So, it needs the dreaded sighted assistance to install? What synth does it
use/support? Speakup rocks, but you lose access to use the num pad for
anything else.
At 04:26 PM 5/9/03 -0400, you wrote:
>John,
>
>Yasr currently only supports speech.  Aside from the user interface, it
>differs from Speak-up mainly in that it is not kernel-based.  It has a
>homepage at http://yasr.sf.net.
>
>-- Michael Gorse / AIM:linvortex / http://mgorse.home.dhs.org --
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: yasr related problem
   ` John J. Boyer
     ` Mike Gorse
@    ` jude dashiell
  1 sibling, 0 replies; 8+ messages in thread
From: jude dashiell @  UTC (permalink / raw)
  To: blinux-list

yasr is a screen reader with a review mode capable of talking to several
hardware speech synthesizers and some sound cards.  It has two advantages
over speakup.  First, it's not a kernel patch.  Second, it wasn't written
with any Linux dependencies.  Those two advantages make it possible to
build and use yasr on other flavors of Unix systems beyond Linux.




^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: yasr related problem
   ` John J. Boyer
@    ` Mike Gorse
       ` Brent Harding
     ` jude dashiell
  1 sibling, 1 reply; 8+ messages in thread
From: Mike Gorse @  UTC (permalink / raw)
  To: blinux-list

John,

Yasr currently only supports speech.  Aside from the user interface, it
differs from Speak-up mainly in that it is not kernel-based.  It has a
homepage at http://yasr.sf.net.

-- Michael Gorse / AIM:linvortex / http://mgorse.home.dhs.org --




^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: yasr related problem
   Krishnakant Ramesh Mane
@  ` John J. Boyer
     ` Mike Gorse
     ` jude dashiell
  0 siblings, 2 replies; 8+ messages in thread
From: John J. Boyer @  UTC (permalink / raw)
  To: blinux-list

Hello,

Please, someone, explain what yasr is and how it differs from speakup and 
brltty. What advantages does it have?

Thanks,
John


-- 
Computers to Help People, Inc.
http://www.chpi.org
825 East Johnson; Madison, WI 53703





^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: yasr related problem
@  Krishnakant Ramesh Mane
   ` John J. Boyer
  0 siblings, 1 reply; 8+ messages in thread
From: Krishnakant Ramesh Mane @  UTC (permalink / raw)
  To: blinux-list

Hello,
Well I think you got it right.  I think I forgot to put the conf 
file in the /home directory.
so you mean to say, the path to the yasr.conf file should be 
/home/yasr.conf is that you mean?  if yes then I will try it 
tomorrow in my lab.
well, can you do me a favour.  if you have a .conf file available 
with you that is working with eflite then please mail it to me.
thanks a lot.





^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 yasr related problem Krishnakant Ramesh Mane
 ` Sergey Fleytin
 ` Lorenzo Prince
 Krishnakant Ramesh Mane
 ` John J. Boyer
   ` Mike Gorse
     ` Brent Harding
   ` jude dashiell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).