On 30-04-2010 11:42, Peter Dyballa wrote:
When the \tableofcontents command is found, the line
\XeTeXinputencoding "cp1252"
was not read yet.
Which is your proof?
The command \XeTeXinputencoding resets the default UTF-8 or UTF-16 input
encoding to something else, restricted, awkward, whatever. It allows
XeTeX to translate the limited characters to sensible Unicode (BTW, MS
Windows has knowledge of Unicode since more the ten years, no need to
present oneself as a guy from last millennium). This internal
representation is used by the TeX core. If you want to keep a
non-Unicode representation of particular characters, then use the LICR
(LaTeX internal character representation) form directly: \´e or {\´e}.
This also works in \hypersetup...
I have participated in discussions both on newsgroups and on mailing
lists for ten years and I don't remember having ever been so attacked as
now. And all because I wanted to use a certain encoding instead of
another one! Besides, this has nothing to do with what I wish or do not
wish to do, since I am trying to compile a multi-chapter document in
which each of the 15 chapters was written by a different person; it is
not as if I am writing something myself from scratch.
Best regards,
Jose Carlos Santos
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
