the direction of speakup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Years ago I used yasr quite regularly. I used it when I was traveling
and needed my computer in situations where it just wasn't possibly to
wire up a serial synth. Obviously, this was before Speakup supported
software speech.

It worked well enough. But, I can tell you that I was alway very, very
happy to get back to a more situation where I could wire in my synth and
fire up Speakup.

PS: The guy who wrote yasr while he was still in school is now the
maintainer of AT-SPI/ATK, the APIs that help drive Orca for us.

Janina

Kyle writes:
> According to Jason White:
> # It runs its own shell and captures input/output, somewhat like screen(1).
> 
> This actually makes YASR the most portable text console screen reader I
> am aware of, since it can run on just about any Unix-like operating
> system. It runs entirely in userspace and depends on shell output rather
> than relying on any kernel level code or output. It also has the benefit
> of being able to work with a wide range of hardware synthesizers via
> Emacspeak servers and possibly other local drivers as well, and also has
> software speech available through various interfaces, including EFlite
> and speech-dispatcher. The trade-off is that you will get no speech
> prior to login, although with the correct login script, you can have
> YASR come up automatically once you've logged into the console you want
> to use. There once was a separate program included in the YASR source
> tree that could read the console prior to login, but I don't currently
> know if it still works. I remember getting it to work at one point, but
> that was some time ago. I did most things with a single text console
> that ran YASR automatically at login and did all my work in Screen,
> which allowed me to have a nearly unlimited number of "windows" open on
> a single console, all under a single YASR instance.
> 
> Just a quick note: because of the way YASR works in a subshell, it
> should be capable of working in a desktop terminal application like
> Xterm, giving you familiar functionality when you have that text-based
> application that Orca doesn't like in gnome-terminal. Keybindings
> shouldn't be a problem either, even if you use gnome-terminal and
> silence Orca, since as far as I know, there aren't any conflicts between
> Orca and YASR keyboard commands.
> ~Kyle
> http://kyle.tk/
> -- 
> "Kyle? ... She calls her cake, Kyle?"
> Out of This World, season 2 episode 21 - "The Amazing Evie"
> _______________________________________________
> Speakup mailing list
> Speakup at linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina at asterisk.rednote.net
		Email:	janina at rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/



[Index of Archives]     [Linux for the Blind]     [Fedora Discussioin]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]
  Powered by Linux