LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
From:
Sebastian Rahtz <[log in to unmask]>
Date:
Tue, 15 Dec 1998 11:39:06 +0000
In-Reply-To:
<v03110700b29bee43f597@[130.237.37.57]>
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments:
text/plain (19 lines)
Hans Aberg writes:
 > Depends: In DVI, such links are shipped out using \special, when converted
 > to PS, it must be put into a similar box, which later is converted
 > correctly to PDF. If people sit down and work it out correctly, it may
 > work, but it is a fragile procedure, as it hangs on a chain of extensions
I have maintained a LaTeX package since 1995 which manages this
process, supporting half a dozen different backends. Believe me, its not
fragile (ok, its not unbreakable!). The bits of it that relate
to TeX->DVI->PS->PDF are reliable, well-understood, and supported.

 > On the other hand, if the format from the beginning understands links (like
 > PDF), there is no doubt that it will work if the format converted to also
 > understands links.
the PostScript which is fed to Distiller or ps2pdf understands
links. so there you go. read up on the pdfmark operator, if you are
interested

Sebastian

ATOM RSS1 RSS2