> > + // since LyX uses unicode, also set the PDF strings to unicode strings
>> with the
>> + // hyperref option "unicode"
>> + opt += "unicode=true,\n ";
>
> What happens when the output is _not_ unicode?
How that?
> What does this option do exactly?
Option pdfencoding
The PDF format allows two encodings for bookmarks and entries
in the information dictionary: PDFDocEncoding and Unicode
as UTF-16BE. Option "pdfencoding" selects between these encodings:
* "pdfdoc" uses PDFDocEncoding. It uses just one byte per character,
but the supported characters are limited (244 in PDF-1.7).
* "unicode" sets Unicode. It is encoded as UTF-16BE. Two bytes
are used for most characters, surrogates need four bytes.
* "auto" PDFDocEncoding if the string does not contain characters
outside the encoding and Unicode otherwise.
iT IS SAVE TO USE UNICODE IN ALL CASES. I tested this carefully I think. And nevertheless, whenever
the user uses not latin1 as encoding, unicode must be set to get proper PDF-bookmarks.
>> + // try to extract author and title from document when none is
>> + // explicitely given
>> + if (title.empty() && author.empty())
>> + opt += "pdfusetitle,\n ";
> Why do this even if the author did not ask for it? Shouldn't it be an
> additional option? In general, adding options behind the user's back looks
bad to me.
Before people start to add their "+1", please read my statement in
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg129100.html
regards Uwe
