public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Dave Mielke <dave@mielke.cc>
To: <blinux-list@redhat.com>
Subject: Re: brltty and simultaneous grade 2 translation
Date: Mon, 26 Nov 2001 15:16:04 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0111261511010.985-100000@dave.private.mielke.cc> (raw)
In-Reply-To: <010501c176ae$3aad2f60$e08caad8@tds.net>

[quoted lines by John J. Boyer on November 26, 2001, at 14:12]

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

I think tabs will also need to be supported since some editors insert them in
spite of what their users might happen to prefer. :-)

Any number (one or more) of tabs and spaces should be permitted between each
part. Blank lines should be skipped. Comments should be supported, and, to be
as familiar as possible to Unix users, the # character should initiate a
comment.

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

This part I'll have to defer to the experts in the field.

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

Agreed. Unix people have a love/hate relationship with the backslash, so it
might as well be used.

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




  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 [this message]
                     ` 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=Pine.LNX.4.30.0111261511010.985-100000@dave.private.mielke.cc \
    --to=dave@mielke.cc \
    --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).