Return-Path: LOJBAN%CUVMB.BITNET@vms.dc.LSOFT.COM Received: from SEGATE.SUNET.SE (segate.sunet.se [192.36.125.6]) by xiron.pc.helsinki.fi (8.7.1/8.7.1) with ESMTP id QAA03072 for ; Tue, 13 Feb 1996 16:23:03 +0200 Message-Id: <199602131423.QAA03072@xiron.pc.helsinki.fi> Received: from listmail.sunet.se by SEGATE.SUNET.SE (LSMTP for OpenVMS v1.0a) with SMTP id 85B7E09D ; Tue, 13 Feb 1996 15:22:16 +0100 Date: Tue, 13 Feb 1996 05:13:06 -0500 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: Re: *old response on y and apostrophe X-To: ucleaar@UCL.AC.UK X-cc: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 1015 Lines: 20 >LOjbab: >> I have yet to hear an argument against apostrophe that doesn't reduce >> to (predominantly malglico or malropno) aesthetics, or the incompatibility >> of some software with using "punctuation marks" as letters of the >> alphabet - these software products apparently cannot handle standard >> English contractions as well, I presume. > >A further argument is redundancy; the <'> is usually nondistinctive >and can be omitted without confusion. Same for glottal stops, if >spaces are left between words. There has been very little complaint that LOjban is too redundant, and rather the reverse. JCB likes his conventions in part because they offer ADDED redundancy after the pattern of English - since capitals at the beginning of sentences are certainly NOT required except for redundancy. He doesn't need an apostrophe becasue he slurs all his glides anyway - his "eo" sounds like "eio", which is one reason we introduced the apostrophe: to make it clear that such slurring was NOT correct. lojbab