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 f1K2eo106605 for ; Tue, 20 Feb 2001 03:40:50 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1K2eod30182 . for ; Tue, 20 Feb 2001 03:40:50 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09AE6.891E6500" 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 f1K2eoH13658 for ; Tue, 20 Feb 2001 03:40:50 +0100 (MET) 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 DAA25927 for ; Tue, 20 Feb 2001 03:40:49 +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 f1K2enQ26453 for ; Tue, 20 Feb 2001 03:40:49 +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 <3.5BCDDC45@mail.listserv.gmd.de>; Tue, 20 Feb 2001 3:40:40 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 490219 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 20 Feb 2001 03:40:45 +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 DAA08914 for ; Tue, 20 Feb 2001 03:40:44 +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 DAA23648 for ; Tue, 20 Feb 2001 03:40:45 +0100 Received: from matups.math.u-psud.fr (mathups.math.u-psud.fr [129.175.52.4]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f1K2ekx17487 for ; Tue, 20 Feb 2001 03:40:46 +0100 (MET) Received: from stats.math.u-psud.fr (beryl.math.u-psud.fr [129.175.54.194]) by matups.math.u-psud.fr (8.11.0/jtpda-5.3.3) with ESMTP id f1K2e2G01274 ; Tue, 20 Feb 2001 03:40:02 +0100 (MET) Received: (from sieben@localhost) by stats.math.u-psud.fr (8.9.1b+Sun/8.9.1) id DAA25424; Tue, 20 Feb 2001 03:41:53 GMT Return-Path: Content-class: urn:content-classes:message Subject: Re: Multilingual Encodings Summary Date: Tue, 20 Feb 2001 04:41:53 +0100 Message-ID: <200102200341.DAA25424@stats.math.u-psud.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Laurent Siebenmann" 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: 3992 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09AE6.891E6500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Here are two past weather reports on the hypertext link breaking = problem: --------------- > From: "Sebastian Rahtz" = > Date: Sun, 3 Oct 1999 23:54:27 +0100 (BST) > To: thierry.bouche@ujf-grenoble.fr > Cc: skirsch@t-online.de, pdftex@tug.org > Subject: Re: Article about pdfTeX in c't > > Thierry Bouche writes: > > Sebastian Rahtz a =E9crit: > > > With the latest dvipdfm, it is actually hard to see much = difference > > > for normal people. > > > > How is the ``links across line or page breaks'' problem handled? > > Not sure _how_, but Mark says he has done it, in the current release. >... --------------- > Date: Mon, 19 Feb 2001 00:36:54 +0000 > From: Sebastian Rahtz > > > so why can't i let TeX split the link and nevertheless communicate = via > > \specials to, say dvips what the unbroken link would be? > > yes, you can, in theory. no problem. but over the last 4 or 5 years = no-one has > actually come up with the code to do so. so either > > a) it *is* hard > or > b) no-one cares enough --------------- My comment: One point that seems not to have been mentioned is that extended TeX implementations like eTeX and PDFTeX could (or do?) offer facilities for setting signposts at the end of lines. These alleviate = the worst headaches in constrcting the mouse-sensitive link regions. On the other hand the first duty of "dvipdfm" (or LaTeX) has been to serve ordinary TeX. Cheers Larry Siebenmann ------_=_NextPart_001_01C09AE6.891E6500 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Multilingual Encodings Summary

Here are two past weather reports on the hypertext = link breaking problem:

 ---------------

 > From: "Sebastian Rahtz" = <sebastian.rahtz@computing-services.oxford.ac.uk>
 > Date: Sun, 3 Oct 1999 23:54:27 +0100 = (BST)
 > To: thierry.bouche@ujf-grenoble.fr
 > Cc: skirsch@t-online.de, = pdftex@tug.org
 > Subject: Re: Article about pdfTeX in = c't
 >
 > Thierry Bouche writes:
 >  > Sebastian Rahtz a = =E9crit:
 >  > > With the latest dvipdfm, = it is actually hard to see much difference
 >  > > for normal people.
 >  >
 >  > How is the ``links across line = or page breaks'' problem handled?
 >
 > Not sure _how_, but Mark says he has done = it, in the current release.
 >...

 ---------------

 > = Date:         Mon, 19 Feb 2001 = 00:36:54 +0000
 > From: Sebastian Rahtz
 >
 > > so why can't i let TeX split the link = and nevertheless communicate via
 > > \specials to, say dvips what the = unbroken link would be?
 >
 > yes, you can, in theory. no problem. but = over the last 4 or 5 years no-one has
 > actually come up with the code to do so. = so either
 >
 >  a) it *is* hard
 > or
 >  b) no-one cares enough

 ---------------

My comment: One point that seems not to have been = mentioned is that
extended TeX implementations like eTeX and PDFTeX = could (or do?) offer
facilities for setting signposts at the end of lines. = These alleviate the
worst headaches in constrcting the mouse-sensitive = link regions. On the
other hand the first duty of "dvipdfm" (or = LaTeX)  has been to serve
ordinary TeX.

Cheers

Larry Siebenmann

------_=_NextPart_001_01C09AE6.891E6500--