public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
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 16:21:04 -0500	[thread overview]
Message-ID: <014b01c176c0$43719480$e08caad8@tds.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0111261608300.15932-100000@xanadu.home>

Nicolas,
I'll take a look at nfbtrans and also at the Duxbury table format. I kind of
dooubt that nfbtrans would be very good at supporting languages other than
English.
I like Dave's suggestion of putting the number first in the rules. This
number actually indicates a pattern-matching method. So the algorithm would
be more than a simple pattern replacement. I know French. Where could I find
their Braille code, preferably on the Web?
I think that a direct dot pattern representation would not be as clear as
using the ASCII characters that are used to represent Braille dot patterns
in the particular language. Don't the text-translation tables already take
care of translating to whatever characters a particular display needs to
represent a particular dot pattern. Of course, we might need to have an
escapt sequence for representing non-printing characters, such as \xnn
John


Computers to Help People, Inc.
http://www.chpi.org
825 East Johnson; Madison, WI 53703


----- Original Message -----
From: "Nicolas Pitre" <nico@cam.org>
To: <blinux-list@redhat.com>
Sent: Monday, November 26, 2001 16:13
Subject: Re: brltty and simultaneous grade 2 translation


> On Mon, 26 Nov 2001, John J. Boyer wrote:
>
> > Dave,
> > Comments are a good idea. However, any character used as a comment
indicator
> > will present problems, since it could be used in some language. Perhaps
the
> > # could indicate a comment only if it is the very first character in a
line
> > or of it follows the number, separated from it by a space or tab. If a
> > source string has # as its first character it can be indented a space or
> > two. That would mean that leading spaces on a line would be ignored.
>
> I'd suggest supporting a dot pattern representation directly instead of
> relying on ascii correspondance which may well be different from one
braille
> table to another, especially for symbols outside of the standard alphabet.
>
>
> Nicolas
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>





  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
                   ` Dave Mielke
                     ` John J. Boyer
                       ` Dave Mielke
                       ` Nicolas Pitre
                         ` John J. Boyer [this message]
                           ` 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='014b01c176c0$43719480$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).