From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.44.254]) by listman.redhat.com (Postfix) with ESMTP id D32F13EE06 for ; Mon, 26 Nov 2001 17:16:03 -0500 (EST) Received: from mail.redhat.com (mail.redhat.com [199.183.24.239]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id fAQMG3p01070 for ; Mon, 26 Nov 2001 17:16:03 -0500 Received: (from mail@localhost) by mail.redhat.com (8.11.0/8.8.7) id fAQMG3K12495 for blinux-list@listman.redhat.com; Mon, 26 Nov 2001 17:16:03 -0500 Received: from lowblow.svc.tds.net (lowblow.svc.tds.net [204.246.1.39]) by mail.redhat.com (8.11.0/8.8.7) with ESMTP id fAQMG3w12491 for ; Mon, 26 Nov 2001 17:16:03 -0500 Received: from jumbo ([216.170.140.224]) by lowblow.svc.tds.net with SMTP id <20011126221602.UVRI1072.lowblow@jumbo> for ; Mon, 26 Nov 2001 16:16:02 -0600 Message-ID: <014b01c176c0$43719480$e08caad8@tds.net> From: "John J. Boyer" To: References: Subject: Re: brltty and simultaneous grade 2 translation Date: Mon, 26 Nov 2001 16:21:04 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: blinux-list@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: 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" To: 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 >