[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#145339: debiandoc-sgml: Stylistic error in generated PDF and PostScript cross-references



On 16.07.03 Ardo van Rangelrooij (ardo@debian.org) wrote:
> Hilmar Preusse (hille42@web.de) wrote:

Hi,

> > At least this minimal example doesn't show up that bug in woody:
<snip>
> > So I guess, this is not the fault of varioref...
> 
> Hmm, it's the only package that generates the references unless
> there's something going on behind the scenes I'm not aware of.  At
> least it's a problem in one of the LaTeX modules.
> 
Perhaps I should read the documentation more carefully... Sorry!

The following example shows the behaviour.

\documentclass{article}
\usepackage{varioref}
\begin{document}
test\label{test}\newpage test1\vref{test}
\newpage
test2\label{test1}\newpage test3\vref{test1}
\newpage
test4\label{test2}\newpage test5\vref{test2}
\newpage
test6\label{test3}\newpage test7\vref{test3}
\newpage
test8\label{test4}\newpage test9\vref{test4}
\end{document}

I think Frank has implemented it, to allow a bit random variation in
the generated strings. I don't know, if we can convince him to undo
that change. One solution could be to put a
\renewcommand{\reftextbefore}{on the preceding page}%
after that call of varioref, however that will break, as soon as one
use another language than english. Experimenting with something like

\documentclass[english]{article}
\usepackage{babel}
\usepackage{varioref}
\selectlanguage{english}
\iflanguage{english}{\renewcommand{\reftextbefore}{on the preceding page}}{}
<snip>

gained no result. Any ideas, what to do? Again sorry, for my fault.

H.
-- 
sigmentation fault



Reply to: