From ucleaar@UCL.AC.UK Ukn Jul 29 13:24:47 1993 Received: from YALEVM.YCC.YALE.EDU by MINERVA.CIS.YALE.EDU via SMTP; Thu, 29 Jul 1993 13:24:44 -0400 Received: from YALEVM.CIS.YALE.EDU by YaleVM.YCC.Yale.Edu (IBM VM SMTP V2R2) with BSMTP id 8563; Thu, 29 Jul 93 13:23:26 EDT Received: from YALEVM.CIS.YALE.EDU (NJE origin LISTSERV@YALEVM) by YALEVM.CIS.YALE.EDU (LMail V1.1d/1.7f) with BSMTP id 3743; Thu, 29 Jul 1993 13:20:43 -0400 Date: Thu, 29 Jul 1993 18:20:12 +0100 Reply-To: ucleaar@UCL.AC.UK Sender: Lojban list From: Mr Andrew Rosta Subject: Re: logban ' X-To: lojban@cuvma.BITNET, conlang@diku.dk To: Erik Rauch In-Reply-To: (Your message of Wed, 28 Jul 93 23:29:36 O.) <9307282114.AA27408@pyrps5.eng.pyramid.com> Status: RO X-Status: Message-ID: Frank says: > Using ' as an alphabetic character is incredibly stupid. My command > line interpreter uses ' as meaning quoted material follows. I have > commands which do lookup for lojban words and I use "h" to replace ' > when I use lojban words as arguments to commands. ' is about the > worst possible character to use. I wind up seeing "h" and ' as synonyms > which is annoying. This is one of the most irritating of the lojban > design flaws. The lojban designers deserve a lot more heat for this > than they got. This is one bug that should be fixed. > -- > Frank Schulz ( fschulz@pyramid.com ) I think h should be mandated as at least an allograph of '. I have tried using h instead of ', but got complaints. In general Lojban is very resistant to change, & unless you can prove beyond all doubt that something really doesn't work, the only way to effect a change is to adopt it yourself & hope that others follow. In this particular case there is a chance it might catch on. ---- And