From lojban@cuvmb.bitnet Wed Mar 13 23:32:28 1996 Received: from punt4.demon.co.uk by stryx.demon.co.uk with SMTP id AA10818 ; Wed, 13 Mar 96 23:32:27 GMT Received: from punt-4.mail.demon.net by mailstore for ia@stryx.demon.co.uk id 826693350:14125:0; Wed, 13 Mar 96 05:02:30 GMT Received: from cunyvm.cuny.edu ([128.228.1.2]) by punt-4.mail.demon.net id aa13946; 13 Mar 96 5:01 GMT Received: from CUVMB.CC.COLUMBIA.EDU by CUNYVM.CUNY.EDU (IBM VM SMTP V2R3) with BSMTP id 4585; Wed, 13 Mar 96 00:01:28 EST Received: from CUVMB.COLUMBIA.EDU by CUVMB.CC.COLUMBIA.EDU (Mailer R2.07) with BSMTP id 1795; Wed, 13 Mar 96 00:01:55 EDT Date: Tue, 12 Mar 1996 23:59:20 -0500 Reply-To: Logical Language Group Sender: Lojban list From: Logical Language Group Subject: *response to old posting on orthography To: lojban@cuvmb.cc.columbia.edu Message-ID: <826693310.13946.0@cunyvm.cuny.edu> Status: R Last month in the thread about orthography, Julian Pardoe said: >This is really only a serious problem with fixed-width founts. Looking >at some text on my screen, I suspect that my eye wants to bind a {.i} to >the preceding word unless I put two spaces before the {.}. So, my eyes >tend to resolve {mi'o .i} as {mi} {o.i}. As long as you do not lose the apostrophe: a text with "mi'o .i" is identical in meaning to the same text with "mi'o.i" lojbab