Re: XeTeX encoding problem

[Masamichi HOSODA]

Thank you for your advice.

> By the way, I don't understand ChangeLog entries like this:
> 
>     2016-03-23  Masamichi Hosoda  <address@hidden>
>             * doc/texinfo.tex (\pdfgettoks, \pdfaddtokens, \adn, \poptoks, 
>             \maketoks, \makelink, \pdflink, \done): New Macro.
>             Add XeTeX PDF table of contents page number link support.
> 
> \pdfgettoks and the rest aren't "new macros" here.  Are they?  I don't
> see new definitions being added.

I'll change them like the following:

  Copy from the definition for pdfTeX and modify for XeTeX
  or
  Copy from the definition for pdfTeX

> I also happened to notice:
>       % In the case of XeTeX, xdvipdfmx converts strings to UTF-16.
>       % Therefore \txiescapepdf is not necessary.
> 
> A string like "\node" (where we don't want \n to be interpreted as a
> newline) or unbalanced parentheses won't cause problems?  -k

I did not notice the case of "\n" and unbalanced parentheses.
In my experiment, they cause problems.
I'll add \txiescapepdf to XeTeX supports.

However, XeTeX does not have \pdfescapestring.
So even if \txiescapepdf is add, the problems are not solved.