X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["942" "Sat" "19" "December" "1998" "21:54:42" "+0100" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "18" "Re: portable LaTeX" "^Date:" nil nil "12" nil "portable LaTeX" nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id VAA08092; Sat, 19 Dec 1998 21:54:59 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <2.AF8CAB44@listserv.gmd.de>; Sat, 19 Dec 1998 21:54:59 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 413520 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sat, 19 Dec 1998 21:54:56 +0100 Received: from mail0.nada.kth.se (mail0.nada.kth.se [130.237.222.70]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id VAA07935 for ; Sat, 19 Dec 1998 21:54:21 +0100 (MET) Received: from [130.237.37.77] (sl57.modempool.kth.se [130.237.37.77]) by mail0.nada.kth.se (8.8.7/8.8.7) with ESMTP id VAA01716 for ; Sat, 19 Dec 1998 21:54:19 +0100 (MET) X-Sender: su95-hab@mail.nada.kth.se References: Your message of "Sat, 19 Dec 1998 16:30:31 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Date: Sat, 19 Dec 1998 21:54:42 +0100 From: Hans Aberg Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: portable LaTeX Status: R X-Status: X-Keywords: X-UID: 3216 At 15:38 +0000 1998/12/19, Robin Fairbairns wrote: >it is of course absolutely nothing whatever to do with object >orientation in tex or the lack of it. it's to do with what bits of a >paragraph tex makes available to the user after it's been split into >lines (not, as it happens, a lot). how those bits would be made >accessible, if that was going to happen) is a matter that could differ >according to whether the underlying engine was trying to exhibit >object orientation or not, but waving a magic o-o wand over tex won't >alter the way it works in the smallest particular. Well, that's the OO of the output language; and in order to get that OO in the output language, you will need an engine able to process OO. Hans Aberg * Email: Hans Aberg * Home Page: * AMS member listing: