Sorry, "have issues" is not a very precise description. You have to
include the exact testcase reproducible with the "xw" driver that
displays a window with a picture of a braille device on a remote X
display. I.e., I will run qemu, and boot with the following arguments
(the 10.0.2.2:1 display doesn't require authentication):
Sorry, what you say is way over my head. Most of us still work on the command
line. I'm using "brltty -b b"m once the disk is loaded as whatever, I do, I
cannot get it running from the boot prompt. It's not because I'm missing it,
it's because the misunderstanding of what the correct command line should be.
I'm sure I got it working once with the string "Linux brltty,bm,usb:" but I
can't get to go again until I get to the login.
These are the messages that rapidly scroll off the screen.
brltty:
brltty[2790]: Ignored Byte: 09
brltty[2790]: Ignored Byte: 60
brltty[2790]: Ignored Byte: EF
brltty[2790]: Ignored Byte: 03
brltty[2790]: Ignored Byte: 94
brltty[2790]: Ignored Byte: 10
brltty[2790]: Ignored Byte: 00
brltty[2790]: Ignored Byte: 00
brltty[2790]: GPM open error: Inappropriate ioctl for device
brltty[2790]: GPM open error: Inappropriate ioctl for device
brltty[2790]: GPM open error: Inappropriate ioctl for device
lfslivecd:root | Sat Sep 1 19:00:09 2007 | ~
# brltty[2790]: GPM open error: Inappropriate ioctl for device
brltty[2790]: GPM open error: Inappropriate ioctl for device
brltty[2790]: GPM open error: Inappropriate ioctl for device
brltty[2790]: GPM open error: Inappropriate ioctl for device
brltty[2790]: GPM open error: Inappropriate ioctl for device
brltty[2790]: GPM open error: Inappropriate ioctl for device
brltty[2790]: GPM open error: Inappropriate ioctl for device
brltty[2790]: GPM open error: Inappropriate ioctl for device
linux DISPLAY=10.0.2.2:1 brltty=xw,10.0.2.2:1
> Also on the issue of brltty, what were the install options used? I see the
> binary in /usr/bin whereas, by default, they are in /bin. So I assume that
> the typical ./configure --prefix=/usr was used? What version is it installed?
>
version 3.8, compiled with ./configure --prefix=/usr --sysconfdir=/etc
--disable-speech-support --disable-api (as recommended by another blind
user)
> I've got speakup working with hardware synths. Which leaves
> speech-dispatcher and espeak which also works. However, I have a problem
> alsa activity is being printed out to STDOUT. How do I redirect the messages
> generated by alsa from being directed to STDOUT on a livecd?
>
Please be more specific, e.g. include a sample message of ALSA activity.
Sat Sep 1 19:09:18 2007 [8510] ALSA: Start of playback on ALSA
Sat Sep 1 19:09:18 2007 [8541] ALSA: Allocating new hw_params structure
Sat Sep 1 19:09:18 2007 [8855] ALSA: PCM state before setting audio
parameters: SETUP
Sat Sep 1 19:09:18 2007 [8881] ALSA: Setting access type to INTERLEAVED
Sat Sep 1 19:09:18 2007 [9019] ALSA: Setting sample format to S16_LE
Sat Sep 1 19:09:18 2007 [9108] ALSA: Setting sample rate to 22050
Sat Sep 1 19:09:18 2007 [9259] ALSA: Setting channel count to 1
Sat Sep 1 19:09:18 2007 [9327] ALSA: Setting hardware parameters on
the ALSA device
Sat Sep 1
What appears to be happening here is that they only appear on one console so
that's not too bad, unlike the brltty.
> The opening dialogs concerning language and time zone etc are very difficult
> to use via brltty or speakup. I'm not sure what to do about this. It would
> be a shame to disable them and restrict the user to a predefined char set and
> time zone etc. But the tab order does not seem to include the listing i.e.
> by pressing tab, it alternates to OK and Cancel. How would I disable these
> dialogs and how would I set predefined defaults?
>
Boot as "linux LANG=fr_FR.UTF-8 TZ=Europe/Paris UTC=1". This is
documented on the boot loader help screens. Unfortunately, they cannot
be made accessible to blind users, so here is the URL where you can read
them:
OK, I'll read about them. But this is not practical at all. The chances of an
error is far too great. Speakup is bad enough with 18 chars. When you are
used to speech or braille support, typing blindly like that is very nerve
racking.
http://wiki.linuxfromscratch.org/livecd/browser/trunk/isolinux
What should I do in order to make this documentation "visible" enough
for blind users? E.g., suggest a wording about this for the release
announcement, web page, etc.
In the linux world we are frequently told rtfm. One of the major problems is
that the user has to go looking for it, why not have it at source. i.e. On
the route of the CD alternatively, a folder called doc on the disk containing a
README.Accessibility. Of course people will want to read the notes before they
download an iso image.
As for inaccessible dialogs, can this be fixed by adding something to
/etc/dialogrc? Currently, if a user requests brltty, the
"visit_items=ON" line is added. You may want to add this line if the
user requests speakup, too. Alternatively, it may be better to skip the
dialogs at all if the user requested brltty, and point to documentation
about the boot arguments.
Thanks for the info about the switch, this needs to be made the default. It
could be why speakup can't manage the dialogs very well.
And BTW, I cannot reproduce the dialog accessibility issue using brltty.
When I press Tab, it changes the virtual braille display between
"Europe/Paris", "OK" and "Cancel", contrary to what you say. The
"visit_items=ON" option is there.
Also, please share your feedback on the accessibility of mutt, lynx and
tin on the CD with brltty.
I'll help whereever possible, I've only just been given a braille display, so
have plenty to learn. With speakup, mutt works very well. As does lynx when a
particular curser setting is made, which I can't remember at this point in time.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
__________ NOD32 2497 (20070901) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
--
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
