Sign up ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

I use the harvmac macros to write papers with plain TeX, and harvmac loads the hyperbasics file to enable hyperlinks.

However I can't figure out why the hyperlinks have a different appearance in the dvi and the PDF files and I can't find where the defaults are defined so that I can change them. Furthermore, I get different styles for the hyperlinks in the pdf depending on how I compile to get the PDF.

With the MWE below, the dvi file from tex MWE.tex has a blue hyperlink with no surrounding box (see image below), whereas the outcome of dvips -z MWE.dvi; ps2pdf14 has a black hyperlink inside a blue box. The outcome of xetex MWE.tex has invisible hyperlinks (black equation number, no surrounding box).

I'd like to understand where these style definitions come from, since I prefer the DVI style and I'd like the PDF to be the same (blue equation number, no surrounding box). The macros from hyperbasics.tex do not seem to define any default, so out of luck I like the DVI style, but not the PDF style.

So, how can I get the blue equation number with no box in the PDF file?


\input harvmac

\newsec{Some title}

One equation:
\eqn\ps{ A = 0}
Reference: See equation \ps.


In the DVI file:

DVI style as seen with xdvi

In the PDF file:

enter image description here

share|improve this question
At least the dvi mystery is now solved. There is a -linkstyle option for xdvi (the program I use for dvi preview). But I couldn't find a similar option for evince to explain the PDF appearance. That would also not explain why the pdf generated with xetex and through dvips+ps2pdf14 have different styles since I use evince for both. – Mafra Dec 2 '12 at 11:30

3 Answers 3

up vote 6 down vote accepted

You get the same result with the hypertex driver of the LaTeX package hyperref. The hyperTeX specials define some very basic HTML markup, e.g.:

s:[1/1]:: html:<a name="page.1">
s:[1/1]:: html:</a>
s:[1/1]:: html:<a name="Doc-Start">
s:[1/1]:: html:</a>
s:[1/1]:: html:<a name="section*.1">
s:[1/1]:: html:</a>
s:[1/1]:: html:<a href="#section.1">
s:[1/1]:: html:</a>
s:[1/1]:: html:<a name="section.1">
s:[1/1]:: html:</a>
s:[1/1]:: html:<a href="#section.1">
s:[1/1]:: html:</a>
s:[1/1]:: html:<a href="">
s:[1/1]:: html:</a>

This is the output of dvii, the TeX source file:

\section{Hello World}
See section \ref{sec:hello}.

The hyperTeX specials do not provide configuration options and do not know about PDF. Thus the link outcome is in control of the DVI program:

  • xdvi underlines in blue.
  • dvips -z uses blue boxes.

Configuration of xdvi

There are three options to configure the link outcome, from the manual page of `xdvi`:
      (.linkColor)  Color  used  for unvisited hyperlinks
      (`Blue2' by default). Hyperlinks are unvisited  be­
      fore  you  click on them, or after the DVI file has
      been reloaded.  The value should be either a  valid
      X color name (such as DarkGoldenrod4) or a hexadec­
      imal color string (such as #8b6508).Seealso -visit­
      edlinkcolor and -linkstyle.

      (.LinkStyle)  Determines  the style in which hyper­
      links are  displayed.  Possible  values  and  their
      meanings are:

       0       No highlighting of links
       1       Underline links with link color
       2       No underlining, color text with link color
       3       Underline and display text colored with
               link color

      The  values for link color are specified by the op­
      tions/resources  -linkcolor  and  -visitedlinkcolor
      (which see).

      (.visitedLinkColor) Color used for  visited  hyper­
      links  (`Purple4'  by  default).  Hyperlinks become
      visited once you click on them. As  for  linkColor,
      the  value should be either a valid X color name or
      a hexadecimal color string.

Configuration of dvips

The border and color are hardcoded, from hps.c:

p->color[0] = 0;
p->color[1] = 0; /* Blue links */
p->color[2] = 1;
p->border[0] = 1; /* horizontal corner radius */
p->border[1] = 1; /* vertical corner radius */
p->border[2] = 1; /* box line width */
p->border[3] = 3; /* dash on size */
p->border[4] = 3;  /* dash off size */

As result dvips -z writes the links of the example above as:

(#section.1) [[134 682 210 694] [1 1 1 [3 3]] [0 0 1]] pdfm 
(#section.1) [[185 628 190 640] [1 1 1 [3 3]] [0 0 1]] pdfm
[[197 628 318 640] [1 1 1 [3 3]] [0 0 1]] ( pdfm 

To get different colors, either the definition of pdfm needs to be changed in or the redefinition can be done at later time by manipulating the arguments for pdfm and replacing the arrays for the border and the color.

Or in short, dvips -z cannot be configured without hacking internals.

share|improve this answer

This is my solution to the problems of (1) using pdfmark in plain TeX to produce the hyperlinks in PDF outputs, and (2) converting the blue rectangles to underlines.

It's too long to summarize here. But roughly speaking, the answer to (1) was to write some TeX macros to do the job. The answer to (2) was to edit the file "" in the current working directory to use the underlines.

PS. Here's my answer to part (1).
How to use PDF hyperlinks in plain TeX.

When I say "plain TeX", I mean completely plain TeX with no 3rd party macro libraries or external scripts or anything like that, except for what I write myself. The basic references for my plain TeX macros are (the section marked "How it is all done internally") and (the section marked "introduction").

First I had to get the HTML special commands into the DVI file by writing them into my own \chapter, \section and various subsection macros. These are far too tedious and irrelevant to write out in full. But the following code snippet gives the basic idea.

% This \PreHatch macro to prefix a text string with a hatch character.
{\catcode`\^=6 \catcode`\#=12 \gdef\PreHatch^1{#^1}}

% Anchor points for cross-reference hyperlinks.
 \special{html:<a name="#1">}#2\special{html:</a>}}
\def\LinkNamePRE#1{\special{html:<a name="#1">}}

% Cross-reference hyperlinks to defined anchor points.
 \special{html:<a href="\PreHatch{#1}">}#2\special{html:</a>}}

% Pre-text and post-text macros.
\def\LinkHrefPRE#1{\special{html:<a href="\PreHatch{#1}">}}

% External hyperlinks.
 \special{html:<a href="#1">}#2\special{html:</a>}}

That's the actual code which I use for my documents. These macros may be invoked as in this example.


That inserts the text parameter (an integer number of a section) into an A/HREF span. If I need to first output the A/HREF link info, then some text, and then after that add the </a>, then I invoke the LinkHrefPRE and LinkHrefPOST macros.

The above description is the relatively easy part, just getting completely plain TeX to create PDF hyperlinks. The only tricky thing is altering the \catcode to allow the hash character to be inserted in the a/href parameter.

I'll write up part (2) about how to get the blue link-boxes replaced by underlines in the next answer.

share|improve this answer
The link does indeed show the relevant information, but links can become dead. I think you should us at least a small example on bookmarks in Plain TeX – Christian Hupfer Aug 4 at 7:08
@Christian Hupfer Yes, you're right. I think about 50% of links die within 2 years. So I'll work up a summary here, but it will take me a while to write it up. – Alan U. Kennington Aug 4 at 7:52

Part (2).
How to change pdfmark blue rectangle hyperlinks to underlines.

By running the strace command for the linux dvips -z command, I discovered that dvips -z used a global file /usr/lib/texmf/dvips/base/ by default to prepend to the output Postscript file to make the hyperlinks get used by ps2pdf. However, dvips -z also looked in the current working directory for a file first. So all I had to do was copy the global file to the local working directory and hack it to change the blue box for hyperlinks to a blue underline.

First I added a new Postscript dictionary /bsdict just below where the original file creates a dictionary called /actiondict.

/actiondict 2 dict dup/Subtype/URI put def
/bsdict 4 dict dup /S /U put dup /W 1 put def

The first line above was in the file already. The second line is what I added.

Second, I added the text /BS bsdict in the places where indicated in the following text.

/Color exch /BS bsdict oldstyle{/LNK}{/Subtype/Link/ANN}ifelse gsave initmat
aload pop/Rect 4 1 roll/Border 3 1 roll/Color exch/BS bsdict/LNK gsave initmat

The added text must be exactly where indicated (unless you know exactly how to program Postscript so that you know how to put it somewhere else). The above commands have the effect of adding the desired parameters for creating blue underlines. I think that BS means box style, /S means "style", /U means underline, and very importantly, '/W' means "width" of line. If this is not set, then the default is zero, which is invisible.

PS. Just for the record, here is the modified version of the file which I have been using successfully for the last year. I'm fairly sure there are no copyright issues with this.

/HPSdict 20 dict dup begin/braindeaddistill 50 def/rfch{dup length 1 sub
1 exch getinterval}bind def/splituri{dup(#)search{exch pop}{()exch}
ifelse dup(file:)anchorsearch{pop exch pop 3 -1 roll pop false}{pop 3 -1
roll exch pop true}ifelse}bind def/lookuptarget{exch rfch dup
/TargetAnchors where{pop TargetAnchors dup 3 -1 roll known{exch get true
}{pop(target unknown:)print == false}ifelse}{pop pop
(target dictionary unknown\012)print false}ifelse}bind def/savecount 0
def/stackstopped{count counttomark sub/savecount exch store stopped
count savecount sub 1 sub dup 0 gt{{exch pop}repeat}{pop}ifelse}bind def
/tempstring 128 string def/targetvalidate{1 index dup length 127 gt exch
tempstring cvs dup(/)search{pop pop pop exch pop true exch}{pop}ifelse
token{pop length 0 ne}{true}ifelse or not}bind def/targetdump-hook where
{pop}{/targetdump-hook{dup mark exch gsave initmat setmatrix{{mark/Dest
4 2 roll targetvalidate{aload pop exch pop/Page 3 1 roll/View exch[exch
/FitH exch]/DEST pdfmark}{cleartomark}ifelse}forall}stackstopped pop
grestore}bind def}ifelse/baseurl{mark exch 1 dict dup 3 -1 roll/Base
exch put/URI exch/DOCVIEW{pdfmark}stackstopped pop}bind def
/externalhack systemdict/PDF known def/oldstyle true def/initmat matrix
currentmatrix def
/actiondict 2 dict dup/Subtype/URI put def
/bsdict 4 dict dup /S /U put dup /W 1 put def
/weblinkhandler{dup 3 1 roll mark 4 1 roll/Title 4 1 roll splituri 3 -1
roll dup length 0 gt{cvn/Dest exch 4 2 roll}{pop}ifelse{externalhack{
/HTTPFile exch}{actiondict dup 3 -1 roll/URI exch put/Action exch}
ifelse}{externalhack{/HTTPFile exch}{/File exch/Action/GoToR}ifelse}
ifelse counttomark 2 sub -1 roll aload pop/Rect 4 1 roll/Border 3 1 roll
/Color exch /BS bsdict oldstyle{/LNK}{/Subtype/Link/ANN}ifelse gsave initmat
setmatrix{pdfmark}stackstopped grestore}bind def/externalhandler where{
pop}{/externalhandler{2 copy{weblinkhandler}exec{/externalhack
externalhack not store 2 copy{weblinkhandler}exec{/externalhack
externalhack not store/oldstyle false store 2 copy{weblinkhandler}exec{
(WARNING: external refs disabled\012)print/externalhandler{pop pop}bind
store externalhandler}{pop pop}ifelse}{pop pop/externalhack externalhack
not store}ifelse}{pop pop/externalhandler{weblinkhandler pop}bind store}
ifelse}bind def}ifelse/pdfmnew{dup type/stringtype eq{externalhandler}{
exch dup rfch exch 3 -1 roll lookuptarget{mark 4 1 roll/Title 4 1 roll
aload pop exch pop/Page 3 1 roll/View exch[exch/FitH exch]5 -1 roll
aload pop/Rect 4 1 roll/Border 3 1 roll/Color exch/BS bsdict/LNK gsave initmat
setmatrix pdfmark grestore}{pop pop}ifelse}ifelse}bind def/pdfmold{dup
type/stringtype eq{externalhandler}{exch dup rfch exch 3 -1 roll
lookuptarget{mark 4 1 roll/Title 4 1 roll aload pop exch pop/Page 3 1
roll/View exch[exch/FitH exch]5 -1 roll aload pop pop 0 3 getinterval
/Rect 3 1 roll/Border exch/LNK gsave initmat setmatrix pdfmark grestore}
{pop pop}ifelse}ifelse}bind def/pdfm where{pop}{/pdfm
/currentdistillerparams where{pop currentdistillerparams dup
/CoreDistVersion known{/CoreDistVersion get}{0}ifelse dup
braindeaddistill le{(WARNING: switching to old pdfm because version =)
print ==/pdfmold}{pop/pdfmnew}ifelse load}{/pdfmark where{pop{dup type
/stringtype eq{externalhandler}{2 copy mark 3 1 roll{pdfmnew}
stackstopped{2 copy mark 3 1 roll{pdfmold}stackstopped{
(WARNING: pdfm disabled\012)print/pdfm{pop pop}store}{
(WARNING: new pdfm failed, switching to old pdfm\012)print/pdfm/pdfmold
load store}ifelse}{/pdfm/pdfmnew load store}ifelse pop pop}ifelse}}{{
pop pop}}ifelse}ifelse bind def}ifelse end def

If this file is put in the local directory when dvips -z is run, then it will be used instead of the global file. It works on dvips version 5.98 anyway.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.