Uh, this conversion has lost its focus. We were discussing the native viability of the OS X Terminal for TTS based screen reader use. My mention of Speakup on a laptop was intended as illustrative, not an expression of concern.
As it happens, I had no problem running Speakup in a VMware Linux vm and using my Mac's CapsLock plus the Fn key (in the lower left corner of my Airbook) to get the Speakup popup. in fact, if memory serves, I offered that it was so much superior to native Terminal in my experience, that I would ssh from my Linux vm to perform native OS X tasks. Janina Linux for blind general discussion writes: > Ahh. But you can change they Speakup key to be something other than the > CapsLock key. > I modified my keymap to use the Alt key instead of Caps Lock. > > Here's how I modified mine. > su - root > cat /speakup/keymap > keymap.new > vi keymap.new > > Within vi I changed > 58, 128, 128, 0, 0, 0, 0, > to > 56, 128, 128, 0, 0, 0, 0, > > Where 58 is the keycode for the CapsLock key, and 56 is the > Keycode for the Alt key. > > then I did: > cat keymap.new > /speakup/keymap > > And viola, the Alt key worked as my Speakup key. > > Be warned. Tampering with your keymap can be dangerous. > Never make a new keymap part of your boot process until you have > tested it very, very thoroughly. > > Good luck. > > On Wed, Mar 07, 2018 at 10:08:26AM -0500, Linux for blind general discussion > wrote: > > Ah, precisely my point. There's no numpad on an Airbook. This isn't a > > problem for Speakup in Linux where you simply use CapsLock as a > > modifier. But that's a doing anything robust with CapsLock is a long > > standing issue with Macintosh. > > > > Linux for blind general discussion writes: > > > > > > In voiceovr configuration there are key and numpad commander settings. > > > Speech functions can be attached to them. The key commanders can be > > > used with any keyboarrd, numpad commanders are best suited where there is > > > a numpad. > > > > > > On Mon, 5 Mar 2018, Linux for blind general discussion wrote: > > > > > > > Linux for blind general discussion writes: > > > > > > > > > > Voiceover can be made to act exactly like speakup using the numpad > > > > > keys. > > > > > > > > > On an Airbook? How? > > > > > > > > > On Thu, 1 Mar 2018, Linux for blind general discussion wrote: > > > > > > > > > > > Oh, yes, one can do this with Voice Over, but it's so very, very > > > > > > cumbersome compared to using Speakup's numeric keypad screen review. > > > > > > > > > > > > I just don't have all day to fuss with VO. Just my experience. > > > > > > > > > > > > Janina > > > > > > > > > > > > Linux for blind general discussion writes: > > > > > > > -eric, > > > > > > > > > > > > > > I honestly do not have any special software or configerations to > > > > > > > interact with the Unix console. I have noticed that each person > > > > > > > who is having issues with the Mac terminal have in common. > > > > > > > Remember Voiceover requires that you use the VoiceOver keys to > > > > > > > navigate the VoiceOver cursor. It is similar to the flat review > > > > > > > in Linux but uses different keys. You have to hold down the CTRL > > > > > > > + CMD keys to move the cursor. In addition to these keys you have > > > > > > > to make sure you are interacting with the terminal window. > > > > > > > VoiceOver requires that you are "interacting" with windows for > > > > > > > VoiceOver to read the contents of that window. To do this you > > > > > > > press the Shift key + CTRL + CMD + the down arrow. In terms of > > > > > > > the terminal window you would listen for "Shell" and perform the > > > > > > > interaction command. From this point you would use the VoiceOver > > > > > > > navigation commands to move around the stdout including the man > > > > > > > pages. > > > > > > > > > > > > > > To interact with the man pages simply execute the man page you > > > > > > > are interested in then use the above commands to read it. Once > > > > > > > you have read the currently displayed page you would press the > > > > > > > space bar to bring up the next section of the man page. You can > > > > > > > tell if there is additional pages not being displayed because at > > > > > > > the bottom there will be a : displayed letting you know there are > > > > > > > more pages to show. To exit the man pages you would simply type > > > > > > > the letter q. I typically will execute this command to have more > > > > > > > control of the man docs and can review them later. > > > > > > > $ man grep >> grep.txt > > > > > > > > > > > > > > I am sure you understand what that is doing but in case someone > > > > > > > does not it is basically redirecting the stdout from the man > > > > > > > command to a file named grep.txt. I then will use vim or cat to > > > > > > > read the documentation. Hope this helps > > > > > > > Bryan Duarte | software engineer > > > > > > > > > > > > > > ASU Computer Science Ph.D Student > > > > > > > IGERT Fellow > > > > > > > Alliance for Person-centered Accessible Technology (APAcT) > > > > > > > Center for Cognitive Ubiquitous Computing (CUbiC Lab) > > > > > > > National Federation of the Blind of Arizona | Affiliate Board > > > > > > > Member > > > > > > > National Association of Blind Students | Board Member > > > > > > > Arizona Association of Blind Students | President > > > > > > > Phone: 480-652-3045 > > > > > > > > > > > > > > > On Feb 28, 2018, at 5:03 PM, Linux for blind general discussion > > > > > > > > <blinux-list@redhat.com> wrote: > > > > > > > > > > > > > > > > -eric > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Blinux-list mailing list > > > > > > > Blinux-list@redhat.com > > > > > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > > > > > > > > > > > > > -- > > > > > XB > > > > > > > > > > _______________________________________________ > > > > > Blinux-list mailing list > > > > > Blinux-list@redhat.com > > > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > > > > > -- > > > XB > > > > > > _______________________________________________ > > > Blinux-list mailing list > > > Blinux-list@redhat.com > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > -- > > > > Janina Sajka > > > > Linux Foundation Fellow > > Executive Chair, Accessibility Workgroup: http://a11y.org > > > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) > > Chair, Accessible Platform Architectures http://www.w3.org/wai/apa > > > > _______________________________________________ > > Blinux-list mailing list > > Blinux-list@redhat.com > > https://www.redhat.com/mailman/listinfo/blinux-list > > -- > Rudy Vener > Website: http://www.rudyvener.com > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list -- Janina Sajka Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectures http://www.w3.org/wai/apa _______________________________________________ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
