From: Nicolas Pitre <nico@cam.org>
To: <blinux-list@redhat.com>
Subject: Re: brltty and simultaneous grade 2 translation
Date: Mon, 26 Nov 2001 16:13:11 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.33.0111261608300.15932-100000@xanadu.home> (raw)
In-Reply-To: <012901c176b4$126b5760$e08caad8@tds.net>
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
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
` Dave Mielke
` John J. Boyer
` Dave Mielke
` Nicolas Pitre [this message]
` 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.33.0111261608300.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).