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 C28393F0AD for ; Mon, 26 Nov 2001 15:59:26 -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 fAQKxQp24115 for ; Mon, 26 Nov 2001 15:59:26 -0500 Received: (from mail@localhost) by mail.redhat.com (8.11.0/8.8.7) id fAQKxQf32544 for blinux-list@listman.redhat.com; Mon, 26 Nov 2001 15:59:26 -0500 Received: from xanadu.home (modemcable084.137-200-24.mtl.mc.videotron.ca [24.200.137.84]) by mail.redhat.com (8.11.0/8.8.7) with ESMTP id fAQKxQw32538 for ; Mon, 26 Nov 2001 15:59:26 -0500 Received: from localhost (nico@localhost) by xanadu.home (8.11.6/8.11.6) with ESMTP id fAQKxQh18591 for ; Mon, 26 Nov 2001 15:59:26 -0500 X-Authentication-Warning: xanadu.home: nico owned process doing -bs Date: Mon, 26 Nov 2001 15:59:26 -0500 (EST) From: Nicolas Pitre X-X-Sender: To: Subject: Re: brltty and simultaneous grade 2 translation In-Reply-To: <010501c176ae$3aad2f60$e08caad8@tds.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: On Mon, 26 Nov 2001, John J. Boyer wrote: > Dave, > This all sounds fine to me. Now about the format of the translation table. > 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. 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. 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. First, let me tell you that English braille has a _much_ simpler ruleset when it comes to abreviate it than say French. In French the rules are much more convoluted and complex than a simple pattern replacement. Therefore I suggest having a look at already existing braille conversion packages and see if those can be used instead of duplicating work. For one I think nfbtrans might do the job and could be GPL already. Nicolas