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 E58673ED9D for ; Mon, 26 Nov 2001 16:13:10 -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 fAQLDAp28703 for ; Mon, 26 Nov 2001 16:13:10 -0500 Received: (from mail@localhost) by mail.redhat.com (8.11.0/8.8.7) id fAQLDAN01711 for blinux-list@listman.redhat.com; Mon, 26 Nov 2001 16:13:10 -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 fAQLDAw01707 for ; Mon, 26 Nov 2001 16:13:10 -0500 Received: from localhost (nico@localhost) by xanadu.home (8.11.6/8.11.6) with ESMTP id fAQLDBh18626 for ; Mon, 26 Nov 2001 16:13:11 -0500 X-Authentication-Warning: xanadu.home: nico owned process doing -bs Date: Mon, 26 Nov 2001 16:13:11 -0500 (EST) From: Nicolas Pitre X-X-Sender: To: Subject: Re: brltty and simultaneous grade 2 translation In-Reply-To: <012901c176b4$126b5760$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, > 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