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 f1J8cc101201 for ; Mon, 19 Feb 2001 09:38:38 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1J8Bmd26389 . for ; Mon, 19 Feb 2001 09:11:48 +0100 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1J8BkH29926 for ; Mon, 19 Feb 2001 09:11:47 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09A4F.5AA17B00" 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 JAA28064 for ; Mon, 19 Feb 2001 09:11:41 +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 f1J8BfQ11415 for ; Mon, 19 Feb 2001 09:11:41 +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 <4.6A16033A@mail.listserv.gmd.de>; Mon, 19 Feb 2001 9:11:32 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 489453 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 19 Feb 2001 09:11:38 +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 JAA15211 for ; Mon, 19 Feb 2001 09:11:36 +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 JAA54750 for ; Mon, 19 Feb 2001 09:11:34 +0100 Received: from mailgateway1.uni-freiburg.de (mailgateway1.uni-freiburg.de [132.230.1.6]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f1J8BWx21127 for ; Mon, 19 Feb 2001 09:11:32 +0100 (MET) Received: from remote142-137.home.uni-freiburg.de [132.230.142.137] by mailgateway1.uni-freiburg.de with smtp (Exim 1.82 #3) id 14UlPu-0003KB-00; Mon, 19 Feb 2001 09:11:30 +0100 In-Reply-To: <14991.58620.873169.562430@istrati.zdv.uni-mainz.de> References: <14991.47029.909613.454490@spqr2.oucs.ox.ac.uk> <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: Windows Eudora Light Version 3.0.1 (16) X-Sender: oberdiek@localhost Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary Date: Mon, 19 Feb 2001 08:45:36 +0100 Message-ID: <3.0.1.16.20010219084536.441786f0@localhost> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Heiko Oberdiek" 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: 3981 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09A4F.5AA17B00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 16:06 18.02.2001 +0100, Frank Mittelbach wrote: >Sebastian Rahtz writes: > > 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). For color support, \specials at the begin and the end are enough. Here a graphics attribute is set at the begin and the previous color is set at the end of the group. However, a link region has to be a rectangle (the normal annotations in PDF 1.2) and the coordinates have to be known or calculated. This is easy, if the link is put in a \hbox. At TeX level \special markers at the lower left and upper right corners can be put in the dvi. At PostScript level the dimensions and absolute position of the rectangle are calculated by the help of the PostScript command currentpoint (I do not know a similar command in TeX). This technique is used by pdfmark (dvips) driver of hyperref. The problem arises, if the link does not fit the current line, but is broken across lines. Then in most cases the link area is not a rectangle like this paragraph as an example. PdfTeX does know, that there are line breaks and it knows about all boxes that are part of the link. So it generates _multiple_ links, one for each line, that is part of the link. But how to collect the informations in the TeX/dvips case? I do know about \vadjust to put a special between the first and second lines of a multiple line link, but how to get the heights of the next lines? And, especially, how to get the informations about the x coordinates of the lines? Regards Heiko PS: The next big problem is a page break that can occur in a link, that is broken across lines. In the pdfTeX case, the headline of the next page will become part of the link. ------_=_NextPart_001_01C09A4F.5AA17B00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary

At 16:06 18.02.2001 +0100, Frank Mittelbach = wrote:
>Sebastian Rahtz writes:

> > 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).

For color support, \specials at the begin and the = end
are enough. Here a graphics attribute is set at the = begin
and the previous color is set at the end of the = group.

However, a link region has to be a rectangle (the = normal
annotations in PDF 1.2) and the coordinates have to = be
known or calculated.
  This is easy, if the link is put in a \hbox. = At TeX
level \special markers at the lower left and upper = right
corners can be put in the dvi. At PostScript level = the
dimensions and absolute position of the rectangle = are
calculated by the help of the PostScript = command
currentpoint (I do not know a similar command in = TeX).
This technique is used by pdfmark (dvips) driver = of
hyperref.
  The problem arises, if the link does not fit = the
current line, but is broken across lines. Then in = most
cases the link area is not a rectangle like = this
paragraph as an example.
  PdfTeX does know, that there are line breaks = and it
knows about all boxes that are part of the link. So = it
generates _multiple_ links, one for each line, that = is
part of the link.
  But how to collect the informations in the = TeX/dvips
case? I do know about \vadjust to put a special = between
the first and second lines of a multiple line = link,
but how to get the heights of the next lines?
And, especially, how to get the informations = about
the x coordinates of the lines?

Regards
  Heiko = <oberdiek@ruf.uni-freiburg.de>

PS: The next big problem is a page break that = can
    occur in a link, that is broken = across lines.
    In the pdfTeX case, the headline = of the
    next page will become part of the = link.

------_=_NextPart_001_01C09A4F.5AA17B00--