From: "John J. Boyer" <director@chpi.org>
To: <blinux-list@redhat.com>
Subject: Re: brltty and simultaneous grade 2 translation
Date: Mon, 26 Nov 2001 14:12:01 -0500 [thread overview]
Message-ID: <010501c176ae$3aad2f60$e08caad8@tds.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0111261414010.985-100000@dave.private.mielke.cc>
Dave,
This all sounds fine to me. Now about the format of the translation table.
Since we want to accomodate many languages, I think it would be best to put
each rule on a line by itself and to use a simple space between the parts of
the rule. As I see it, each rule would consist of a source string, a space,
the destination string, space, and a number that specifies whether the
source string is a whole word, should be translated only if it is in the
middle of a word, etc. If either the source or destination string includes a
space, we can arrange for an escape sequence. This would be necessary no
matter what separation character we used.
John
Computers to Help People, Inc.
http://www.chpi.org
825 East Johnson; Madison, WI 53703
----- Original Message -----
From: "Dave Mielke" <dave@mielke.cc>
To: <blinux-list@redhat.com>
Sent: Monday, November 26, 2001 14:19
Subject: Re: brltty and simultaneous grade 2 translation
> [quoted lines by John J. Boyer on November 26, 2001, at 13:10]
>
> >I prefer a pointer and a length also. I think it would be a good idea to
> >have a global variable containing the length of the Braille display, so
it
> >wouldn't have to be passed.
>
> I prefer passing it via a parameter so that, should the imagination kick
in, we
> can get more inventive regarding what gets translated when.
>
> >I can pass back an aray of the position in the
> >input buffer of each character in the output buffer, but I feel a bit
> >uncomfortable about doing cut and paste in Grade 2 because Grade 2 isn't
1
> >for 1. I would probably turn off Grade 2 before doing cut and paste.
>
> As long as the array identifies non-first characters of sequences, BRLTTY
could
> easily enforce that only the first character of a sequence can be used
when
> cutting. Better yet, the first character should be used for the start of
the
> selected text, but the last character should be used for the end of the
> selected text. The array, however, need only mark the first character of
each
> sequence, as BRLTTY could easily figure out the rest.
>
> --
> Dave Mielke | 2213 Fox Crescent | I believe that the Bible is
the
> Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me
> EMail: dave@mielke.cc | Canada K2A 1H7 | if you're concerned about
Hell.
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
linux, and audio cbowman
` philwh
` cbowman
` A. R. Vener
` cbowman
` L. C. Robinson
` Bill Gaughan
` Dave Hunt
` A. R. Vener
` Bill Gaughan
` Bill Gaughan
` Luke Davis
` L. C. Robinson
` Brent Harding
` brltty and simultaneous grade 2 translation Bill Gaughan
` Dave Mielke
` John J. Boyer
` Dave Mielke
` John J. Boyer
` Dave Mielke
` John J. Boyer
` Dave Mielke
` John J. Boyer [this message]
` Dave Mielke
` John J. Boyer
` Dave Mielke
` Nicolas Pitre
` John J. Boyer
` Nicolas Pitre
` John J. Boyer
` Nicolas Pitre
` Bill Gaughan
` John J. Boyer
` Bill Gaughan
` John J. Boyer
` Nicolas Pitre
` John J. Boyer
` Dave Mielke
` Nicolas Pitre
Ian Blackburn
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='010501c176ae$3aad2f60$e08caad8@tds.net' \
--to=director@chpi.org \
--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).