From: David Poehlman <poehlman@clark.net>
To: Hans Zoebelein <zocki@goldfish.cube.net>
Cc: blinux-list@goldfish.cube.net
Subject: Re: Survey results: Linux braille documentation
Date: Wed, 16 Oct 1996 09:16:57 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.3.95.961016091210.6183C-100000@explorer2> (raw)
In-Reply-To: <Pine.LNX.3.94.961015032253.3933H-100000@goldfish.cube.net>
Speaking to the last point, the braille would be handled in a couple of
ways none of which would seriously impair the timeliness of their
production. For hard copy since the documentation will already be on
diskette, it would be no problem to produce it quickly. here are the ways
again. it would be archived in ready to braille format for anyone with an
embosser who chooses to braill thyself, it would be sent to a professional
house gathered for this purpose to braille and disceminate upon request.
It would be brailled on request by individuals who are known to be
available for this process. in other words. the documentation would be
announced and then requested. Don't forget that if it is on the web in
braille, it would also be readable electronically by people with the
equipment to take advantage of it. concievably, this port too could be
printed directly from the web to an embosser.
I anticipate little to no lagtime in any of these processes.
Thank you!
On Wed, 16 Oct 1996, Hans Zoebelein wrote:
> Dear Blinux subscriber,
>
> thanks to you all who contributed to the braille documentation for Linux
> survery.
>
> So here come the results. Subject was: "Move your a.." posted at
> blinux-list on 10.Sep.1996. Since sometimes more than one option
> was used, the sum of percentages may be more than 100%.
>
> We had a total of 38 contributions.
>
> 24 contributions (63%) from registerd blinux-list subscribers.
> 14 contributions (37%) from blind-l subscribers where this survey was
> posted also. (BLIND-L@UAFSYSB.UARK.EDU is a busy list which deals about
> support for the computer user who is blind)
>
> 24 posters (63%) announced interest for Linux braille documentation.
> 5 posters (13%) had no interest in Linux braille docu "forget it..."
> 3 posters (8%) remarked that they were not blind.
> 5 posters (13%) didn't know/had no interest in Linux (all from blind-l).
> 8 posters (21%) said, that they would prefer some sort of software or
> hardware filter which would be able to transfer normal Linux man pages
> into braille or spoken words.
>
> Some people brought up the thought, that braille documentation would be
> always late since the develeopment speed of Linux is really fast, so that
> the normal man pages are often outdated, not to speak about braille
> documentation. This seems to be a vaild point.
>
>
>
>
> --
> Hans Zoebelein You are interested in Linux blind support?
> zocki@goldfish.cube.net Join the blinux mailing list and mail to:
> *I'm a poker player, blinux-list-request@goldfish.cube.net
> *I don't believe in gambling. with subject line: subscribe
>
>
>
>
>
>
> ---
> Send your message for blinux-list to blinux-list@goldfish.cube.net
> Blinux software archive at ftp://leb.net/pub/blinux
> To unsubscribe send mail to blinux-list-request@goldfish.cube.net
> with subject line: unsubscribe
>
>
Hands-On-Technolog(eye)s
touching the internet
voice: 1-(301) 949-7599
E-mail: poehlman@clark.net
ftp: ftp.clark.net/pub/poehlman
url: http://www.clark.net/pub/poehlman
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Hans Zoebelein
` David Poehlman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.3.95.961016091210.6183C-100000@explorer2 \
--to=poehlman@clark.net \
--cc=blinux-list@goldfish.cube.net \
--cc=zocki@goldfish.cube.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).