X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1120" "Sat" "19" "December" "1998" "15:38:56" "+0000" "Robin Fairbairns" "Robin.Fairbairns@CL.CAM.AC.UK" nil "26" "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 QAA25478; Sat, 19 Dec 1998 16:40:35 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <6.8DD02458@listserv.gmd.de>; Sat, 19 Dec 1998 16:39:04 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 413389 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sat, 19 Dec 1998 16:39:00 +0100 Received: from heaton.cl.cam.ac.uk (exim@heaton.cl.cam.ac.uk [128.232.32.11]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with SMTP id QAA28507 for ; Sat, 19 Dec 1998 16:38:59 +0100 (MET) Received: from dorceus.cl.cam.ac.uk (cl.cam.ac.uk) [128.232.1.34] (rf) by heaton.cl.cam.ac.uk with esmtp (Exim 1.82 #1) id 0zrOT4-0007lG-00; Sat, 19 Dec 1998 15:38:59 +0000 Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Your message of "Sat, 19 Dec 1998 16:30:31 +0100." Date: Sat, 19 Dec 1998 15:38:56 +0000 From: Robin Fairbairns 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: 3213 > At 08:51 -0500 1998/12/19, Y&Y Inc. wrote: > >>But can PDF break links across pages ? -- > .. > >...You have to split the link into two parts before > >you turn it into PDF code. Which is a non-trivial exercise in TeX! > > This is probably due to the lack of OO (Object Orientation) in TeX: A new > DVI must be fully object oriented, so that it is possible for other > processing tools to easily extract the information needed. 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. and it is of course completely irrelevant to the discussion of latex and/or its portability. [sorry, everyone else. i know i shouldn't have responded...] robin