public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: <blinux-list@redhat.com>
Subject: Re: brltty and simultaneous grade 2 translation
Date: Mon, 26 Nov 2001 18:09:34 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0111261749210.15932-100000@xanadu.home> (raw)
In-Reply-To: <014b01c176c0$43719480$e08caad8@tds.net>

On Mon, 26 Nov 2001, John J. Boyer wrote:

> 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?

Don't know.  I learned compressed French braille a couple years ago.  
Although I still can read it more or less with surrounding context, I fear I
wouldn't be able to write it anymore.  There are the pretty generic rules
which are sensible, but you must also account for the hundreds of ad hoc
rules.

> 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. 

Well... not necessarily.  At least not in French, especially when it comes 
to computer braille.  French braille is quite well defined for 
paper literature, but computer braille is a much random matter, especially 
for non alphabetical characters.  A simple dot "." may translate to 
different dot pattern depending on your taste.  I even got my own braille 
table to use with BRLTTY as I couldn't stand the other available tables 
which seemed not natural to me.

Therefore it would be much simpler, at least for the French braille 
compression, to just tell BRLTTY: replace each "ation" sufix in a word by 
dots 3-4, "ent" sufixes by dot 1-2-6, and so on, since that's actually how 
it is defined for paper document and not fiddle with the current braille 
table for the non translated case.  Still I may wish to read compressed 
English text without having to change my own braille table for something I 
couldn't understand just because the braille compressor was defined with a 
particular braille table in mind.


Nicolas




  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
                           ` Nicolas Pitre [this message]
                             ` 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=Pine.LNX.4.33.0111261749210.15932-100000@xanadu.home \
    --to=nico@cam.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).