Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f1IG4lf15576 for ; Sun, 18 Feb 2001 17:04:47 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1IG4ld23652 . for ; Sun, 18 Feb 2001 17:04:47 +0100 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1IG4lQ09441 for ; Sun, 18 Feb 2001 17:04:47 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C099C4.83C8F980" Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id RAA14412 for ; Sun, 18 Feb 2001 17:04:46 +0100 (MET) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1IG4kQ09437 for ; Sun, 18 Feb 2001 17:04:46 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <13.56CD23C0@mail.listserv.gmd.de>; Sun, 18 Feb 2001 17:04:37 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 489508 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 18 Feb 2001 17:04:43 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id RAA04055 for ; Sun, 18 Feb 2001 17:04:39 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id RAA44698 for ; Sun, 18 Feb 2001 17:04:39 +0100 Received: from moutvdom00.kundenserver.de (moutvdom00.kundenserver.de [195.20.224.149]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1IG4cx28050 for ; Sun, 18 Feb 2001 17:04:38 +0100 (MET) Received: from [195.20.224.219] (helo=mrvdom03.kundenserver.de) by moutvdom00.kundenserver.de with esmtp (Exim 2.12 #2) id 14UWKE-0001kx-00 for LATEX-L@urz.uni-heidelberg.de; Sun, 18 Feb 2001 17:04:38 +0100 Received: from manz-3e3648b2.pool.mediaways.net ([62.54.72.178] helo=istrati.zdv.uni-mainz.de) by mrvdom03.kundenserver.de with esmtp (Exim 2.12 #2) id 14UWK2-0002mZ-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Sun, 18 Feb 2001 17:04:26 +0100 Received: (from latex3@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id QAA27278; Sun, 18 Feb 2001 16:06:37 +0100 In-Reply-To: <14991.47029.909613.454490@spqr2.oucs.ox.ac.uk> References: <200102131655.QAA05656@penguin.nag.co.uk> <14985.27933.205182.551235@gargle.gargle.HOWL> <14990.45178.192666.234476@istrati.zdv.uni-mainz.de> <14991.47029.909613.454490@spqr2.oucs.ox.ac.uk> Return-Path: X-Mailer: VM 6.75 under Emacs 20.4.1 X-Authentication-Warning: istrati.zdv.uni-mainz.de: latex3 set sender to frank@mittelbach-online.de using -f Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary Date: Sun, 18 Feb 2001 16:06:36 +0100 Message-ID: <14991.58620.873169.562430@istrati.zdv.uni-mainz.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3972 This is a multi-part message in MIME format. ------_=_NextPart_001_01C099C4.83C8F980 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sebastian Rahtz writes: > > > - How much of an advantage is pdftex compared to creating pdf = via DVI? > > > I have only done the latter without any problems, but of = course it > > > involves more file format conversions. > > > > the classic example is link breaking. if you have a long bit of text > to make into a link, pdftex can break it into multiple links, amd > linebreak nicely. dvi-based methods just crawl away in despair and = make > a long unbroken link. People do claim they could break links at the = dvi > level, but I don't think anyone has actually done it is that technically very different from providing, say, color support at = dvi level? i mean if i say \textcolor{red}{this text is in red} and my text = gets broken across the line by TeX all that TeX does is providing some = \special at the begin and end of this text (ie they fall onto two different lines). Nevertheless dvips can color my text red. so why can't i let TeX split the link and nevertheless communicate via \specials to, say dvips what the unbroken link would be? do i miss something? frank ------_=_NextPart_001_01C099C4.83C8F980 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary

Sebastian Rahtz writes:
 >  >  > - How much of an = advantage is pdftex compared to creating pdf via DVI?
 >  >  >   I have = only done the latter without any problems, but of course it
 >  >  >   involves = more file format conversions.
 >  >
 >
 > the classic example is link breaking. if = you have a long bit of text
 > to make into a link, pdftex can break it = into multiple links, amd
 > linebreak nicely. dvi-based methods just = crawl away in despair and make
 > a long unbroken link. People do claim they = could break links at the dvi
 > level, but I don't think anyone has = actually done it

is that technically very different from providing, = say, color support at dvi
level? i mean if i say \textcolor{red}{this text is = in red} and my text gets
broken across the line by TeX all that TeX does is = providing some \special at
the begin and end of this text (ie they fall onto two = different
lines). Nevertheless dvips can color my text = red.

so why can't i let TeX split the link and nevertheless = communicate via
\specials to, say dvips what the unbroken link would = be?

do i miss something?

frank

------_=_NextPart_001_01C099C4.83C8F980--