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 732CB3EA0D for ; Mon, 26 Nov 2001 15:17:38 -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 fAQKHcp16550 for ; Mon, 26 Nov 2001 15:17:38 -0500 Received: (from mail@localhost) by mail.redhat.com (8.11.0/8.8.7) id fAQKHcV26295 for blinux-list@listman.redhat.com; Mon, 26 Nov 2001 15:17:38 -0500 Received: from mielke.cc (root@wsp233033wss.cpe.net.cable.rogers.com [24.157.76.7]) by mail.redhat.com (8.11.0/8.8.7) with ESMTP id fAQKHbw26288 for ; Mon, 26 Nov 2001 15:17:37 -0500 Received: from dave.private.mielke.cc (root@dave.private.mielke.cc [192.168.0.2]) by mielke.cc (8.11.6/8.11.6) with ESMTP id fAQKHa011315 for ; Mon, 26 Nov 2001 15:17:36 -0500 Received: from localhost (dave@localhost) by dave.private.mielke.cc (8.9.3/8.9.3) with ESMTP id PAA04490 for ; Mon, 26 Nov 2001 15:16:05 -0500 X-Authentication-Warning: dave.private.mielke.cc: dave owned process doing -bs Date: Mon, 26 Nov 2001 15:16:04 -0500 (EST) From: Dave Mielke 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: [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.