From: Bill Gaughan <wgaughan@snet.net>
To: blinux-list@redhat.com
Subject: Re: looking for...
Date: Mon, 26 Nov 2001 11:46:02 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.40.0111261139250.1971-100000@beethoven.wgaughan.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0111261058510.985-100000@dave.private.mielke.cc>
--
Bill Gaughan
wgaughan@snet.net
On Mon, 26 Nov 2001, Dave Mielke wrote:
> [quoted lines by Bill Gaughan on November 26, 2001, at 10:05]
>
> >The grade 2 translator for ScreenPower Braille (which employs a version of
> >Duxbury) translates the whole screen at once. What I think it does is
> >translates the information in the VersaBraille's buffer. I think what you
> >want to do is translate everything in the brltty buffer at once, so, when
> >the reader hits the advance buttons, the next display would be in grade
> >two until the feature was turned off.
>
> What about formatting? Does it fill each line by picking up the beginning of
> the next line to fill out the end of the previous, now shorter, previous line,
> or does it leave each line as an atomic element? What about left margin
> indentation?
>
It leaves the rest of the lines blank, but, since most lines would be over
40 characters anyway, (the standard braille line length on paper), you
wouldn't have to reformat the buffer by starting a new print line on the
same braille line of the previous print line just because there was room
left on the new braille line. That would get too messy and I think, it
would be too hard to program. The only reformatting you would want to do,
and this is not a requirement really, might be to use two spaces instead
of five spaces for a new paragraph. And you could delete blank lines from
the display buffer when translating. Maybe brltty could have two buffers,
a computer braille buffer and a grade two buffer. Also, I think you would
want this feature to be a plug-in compatible option like the synthesizer
drivers or make it library code. Maybe you could borrow code from nfbtrans
package or turbo-braille code that was ported to linux.
just some thoughts. I am not a C++ programmer. I was a COBOL programmer
until three years ago, though.
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
lobap
` Jacek Zadrozny
` Bill Gaughan
` Dave Mielke
` Grade 2 and Brltty (was " John J. Boyer
` Bill Gaughan [this message]
` Grade 2 for " John J. Boyer
` Bill Gaughan
` Dave Mielke
` John J. Boyer
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.LNX.4.40.0111261139250.1971-100000@beethoven.wgaughan.net \
--to=wgaughan@snet.net \
--cc=blinux-list@redhat.com \
/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).