On 2015-10-27, Georg Baum wrote:
> Guenter Milde wrote:
>> A proper fix would be to use lib/unicodesymbols for the content of the
>> hypersetup.
> It has been discussed in the past to use lib/unicodesymbols replacements for
> the preamble, but there was some important reason not to do it (which I
> forgot unfortunately). Searching the list archives or trac should for
> unicodesymbols and preamble should hopefully find the discussion.
OK. For XeTeX, this is not required, as the PDF-Info does not use TeX-fonts
and hence utf8 works fine.
For "latexencoding"="ascii", we need one of the tree options:
a) \usepackage[ascii]{inputenc}
(and \inputencoding{utf8} for the PDF-info).
+1 simple
-1 breaks documents that clash with inputenc
b) use lib/unicodesymbols
+1 no loading of "inputenc" package, as currently
+1 support for more characters than \inputenc{utf8} with hyperref
(e.g. polytonic Greek).
-1 pdf strings expect a different input,
many lib/unicodesymbols replacements do not work!
c) tell the user to use LICR in the preamble, e.g.
PDF title: Gru\ss aus Dresden
+1 consistent with the idea: preamble is "raw" (kind of)
+1 simple (for us)
-1 fails for \" (Gr\"u\ss e)
(different bug: any ASCII-" terminates the string!!!!!)
Günter
