Pavel Sanda wrote:
hi,
i have basic working skeleton for bug 3527; now there is only minimal set of
supported features, but i'll add others, when you won't opose the general
construction of this code. i would like to ask :
1) is it possible to add hyperref support to 1.6 series (Jose?)
2) can somebody review this code and comment what should be done
otherwise and mainly what i forgot to do.
3) what features you would like to have from hyperref ?
from my point of view these things need to be resolved:
1) afaiu strings entered into gui are in utf8; now they are pasted to output
.tex via from_utf8,
but i'm not sure how it works with current encodings. whats the best
solution for this ?
2) i know from my previous experience with hyperref, that there are options,
which are just fine for
pdflatex, but when i try to render it through ps2pdf, the whole compilation
fails.
When LyX creates latex code, you know if it is creating for
pdflatex or plain latex. So you can generate different latex code for
these two cases. Assume that "latex" code may hit ps2pdf, while
"pdflatex" code will not.
Of course, if the "ps2pdf" kind of code is fine for pdflatex too, then
use that.
howto treat these cases ? is it possible to generate different code for a
different targets ?
3) is there something needed for lyx2lyx support ?
4) adding others things like keywords, checkboxes for working bookmarks and
references.
Hyperref has some known incompatibilites, for example
the "language in section heading" problem I describe in bug 3527.
Using the \textorpdfstring construct as described shouldn't be that hard.
This is how I use hyperref currently:
\usepackage[breaklinks=true,colorlinks=true,bookmarks=true,
bookmarksopen=true,bookmarksnumbered=true]{hyperref}
So obviously I'll find it nice if these options are supported,
possibly in the form of checkboxes. Ability to set the link colors
would be nice also.
Options like pdftitle, pdfauthor and pdflang can probably be set
automatic from title, author and the document language.
Helge Hafting
