Received: from relay2.UU.NET by MINERVA.CIS.YALE.EDU via SMTP; Thu, 24 Sep 1992 02:56:23 -0400 Received: from grebyn.com by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA15699; Thu, 24 Sep 92 02:56:08 -0400 Received: by grebyn.com (5.57/SMI-4.1/kan.8.19.92) id AA17737; Thu, 24 Sep 92 02:55:55 -0400 Received: by daily.grebyn.com (5.57/UUCP-Project/02.16.86-kan-10.20.91) id AA08742; Thu, 24 Sep 92 02:55:44 -0400 Date: Thu, 24 Sep 92 02:55:44 -0400 From: lojbab@grebyn.com (Logical Language Group) Message-Id: <9209240655.AA08742@daily.grebyn.com> To: erikr@MINERVA.CIS.YALE.EDU Subject: Re: Tex version of Ckafybarja Papers Cc: lojban@cuvmb.cc.columbia.edu Status: RO X-Status: X-From-Space-Date: Thu Sep 24 02:56:24 1992 X-From-Space-Address: lojbab@grebyn.com The reason we use non-proportional fonts for Lojban text has nothing to do with making things computer like, and everything to do with making Lojban and English interlinear text able to be lined up. I'm sure there exists software that can do this with proportional fonts, but I don;t have it (unless I want to put a tab in for every word of text). Almost everything we publish has at least some interlinear text in, it, so we tend to stick with the non-proportional fonts in any document where that is needed. The dictionary will use some kind of proportional font for Lojban except if I have a small chunk that needs interlinear text. (Another problem with proportional fonts, by the way, is that in some cases it is a pain to convert such a file to an electronic format with 80 character lines. My word processor supports this to a limited extent, but I still have to do some amount of hand massaging, which is why the files posted to the Planned ALanguages Server are mostly in a less usable form with more than 80 characters per line, and hence not readable for many computer people.) lojbab