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 f1ICfOf13738 for ; Sun, 18 Feb 2001 13:41:24 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1ICfOd23077 . for ; Sun, 18 Feb 2001 13:41:24 +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 f1ICfNQ03113 for ; Sun, 18 Feb 2001 13:41:24 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C099A8.1A3AF200" 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 NAA19810 for ; Sun, 18 Feb 2001 13:41:23 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 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 f1ICfMQ03109 for ; Sun, 18 Feb 2001 13:41:22 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.ECA13DF2@mail.listserv.gmd.de>; Sun, 18 Feb 2001 13:41:13 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 489408 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 18 Feb 2001 13:41:19 +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 NAA01839 for ; Sun, 18 Feb 2001 13:41:17 +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 NAA48276 for ; Sun, 18 Feb 2001 13:41:18 +0100 Received: from oxmail.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1ICfHx00208 for ; Sun, 18 Feb 2001 13:41:17 +0100 (MET) Received: from heraldgate2.oucs.ox.ac.uk ([163.1.2.50] helo=frontend2.herald.ox.ac.uk ident=exim) by oxmail.ox.ac.uk with esmtp (Exim 3.12 #1) id 14UT9R-0005j0-00 for LATEX-L@urz.uni-heidelberg.de; Sun, 18 Feb 2001 12:41:17 +0000 Received: from max24.public.ox.ac.uk ([192.76.27.24] helo=spqr2.oucs.ox.ac.uk ident=rahtz) by frontend2.herald.ox.ac.uk with esmtp (Exim 2.02 #1) id 14UT9P-0008M9-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Sun, 18 Feb 2001 12:41:15 +0000 In-Reply-To: <14990.45178.192666.234476@istrati.zdv.uni-mainz.de> References: <200102131655.QAA05656@penguin.nag.co.uk> <14985.27933.205182.551235@gargle.gargle.HOWL> <14990.45178.192666.234476@istrati.zdv.uni-mainz.de> Return-Path: X-Mailer: emacs 20.6.1 (via feedmail 8 Q); VM 6.86 under Emacs 20.6.1 Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary Date: Sun, 18 Feb 2001 12:53:25 +0100 Message-ID: <14991.47029.909613.454490@spqr2.oucs.ox.ac.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Sebastian Rahtz" 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: 3967 This is a multi-part message in MIME format. ------_=_NextPart_001_01C099A8.1A3AF200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank Mittelbach 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. > > not only that, but "rich" as produced via pdftex with hyperef might = be more > difficult to provide (I might get corrected here), eg can you easily = produce > references etc via the dvi -> ps -> pdf route right now? that might = become a > non issue but I guess there is an advantage when you can control what = is > produced for the target format directly. 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 sebastian ------_=_NextPart_001_01C099A8.1A3AF200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary

Frank Mittelbach 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.
 >
 > not only that, but "rich" as = produced via pdftex with hyperef might be  more
 > difficult to provide (I might get = corrected here), eg can you easily produce
 > references etc via the dvi -> ps -> = pdf route right now? that might become a
 > non issue but I guess there is an = advantage when you can control what is
 > produced for the target format = directly.

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

sebastian

------_=_NextPart_001_01C099A8.1A3AF200--