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 f1JG08104243 for ; Mon, 19 Feb 2001 17:00:16 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1JG04d27909 . for ; Mon, 19 Feb 2001 17:00:08 +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 f1JG04Q21670 for ; Mon, 19 Feb 2001 17:00:04 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09A8D.0CAB6800" 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 RAA18516 for ; Mon, 19 Feb 2001 17:00:03 +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 f1JG03Q21666 for ; Mon, 19 Feb 2001 17:00:03 +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 <5.D86A0333@mail.listserv.gmd.de>; Mon, 19 Feb 2001 16:59:54 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 490512 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 19 Feb 2001 17:00:00 +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 QAA26861 for ; Mon, 19 Feb 2001 16:59:59 +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 QAA54930 for ; Mon, 19 Feb 2001 16:59:59 +0100 Received: from server-6.tower-4.starlabs.net (mail.london-1.starlabs.net [212.125.75.12]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f1JFxwx02735 for ; Mon, 19 Feb 2001 16:59:58 +0100 (MET) Received: (qmail 5177 invoked from network); 19 Feb 2001 15:55:48 -0000 Received: from nagmx1e.nag.co.uk (HELO nag.co.uk) (62.232.54.130) by server-6.tower-4.starlabs.net with SMTP; 19 Feb 2001 15:55:48 -0000 Received: from penguin.nag.co.uk (IDENT:root@penguin.nag.co.uk [192.156.217.14]) by nag.co.uk (8.9.3/8.9.3) with ESMTP id PAA13741 for ; Mon, 19 Feb 2001 15:59:52 GMT Received: by penguin.nag.co.uk (8.9.3) id PAA03657; Mon, 19 Feb 2001 15:56:00 GMT In-Reply-To: <14991.58620.873169.562430@istrati.zdv.uni-mainz.de> (message from Frank Mittelbach on Sun, 18 Feb 2001 16:06:36 +0100) 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> <14991.58620.873169.562430@istrati.zdv.uni-mainz.de> Return-Path: X-VirusChecked: Checked Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary Date: Mon, 19 Feb 2001 16:56:00 +0100 Message-ID: <200102191556.PAA03657@penguin.nag.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Carlisle" 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: 3982 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09A8D.0CAB6800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank (Or Chris pretending to be Frank) wrote: > 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? colour changes in pdf work the same was as they do in dvi, namely an instruction to change the state at some point and revert it at the end. But for links it's a lot more interesting. The dvi (and HTML) links work the same way: a special corresponding to at one place and another special corresonding to somewhere else, maybe three or four lines down, or on the next page, or somewhere. PDF links work by specifying an active rectangular region. So your dvi->pdf converter has to figure out what this rectangular region (or regions) is (or are) just based on the information in the dvi file on where text has been positioned, and two distinguished points for the start and end of the link. It's probably possible to do a reasonable job of this (I haven't checked recently what dvipdfm does) but it's a lot harder than getting colours right. (And getting colours right over page boundaries isn't always easy either) David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet = delivered through the MessageLabs Virus Control Centre. For further information = visit http://www.star.net.uk/stats.asp ------_=_NextPart_001_01C09A8D.0CAB6800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary

Frank (Or Chris pretending to be Frank) wrote:

> 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?

colour changes in pdf work the same was as they do in = dvi, namely an
instruction to change the state at some point and = revert it at the end.

But for links it's a lot more interesting.

The dvi (and HTML) links work the same way: a special = corresponding to
<a href=3D"..."> at one place and = another special corresonding to </a>
somewhere else, maybe three or four lines down, or on = the next page, or
somewhere.

PDF links work by specifying an active rectangular = region.
So your dvi->pdf converter has to figure out what = this
rectangular region (or regions) is (or are) just = based on the
information in the dvi file on where text has been = positioned, and two
distinguished points for the start and end of the = link.
It's probably possible to do a reasonable job of this = (I haven't checked
recently what dvipdfm does) but it's a lot harder = than getting colours
right. (And getting colours right over page = boundaries isn't always easy
either)

David

________________________________________________________________= _____
This message has been checked for all known viruses = by Star Internet delivered
through the MessageLabs Virus Control Centre. For = further information visit
http://www.star.net.uk/stats.as= p

------_=_NextPart_001_01C09A8D.0CAB6800--