> > Short answer: Don't do that. If you want to produce bookmarks,
> > use UTF-8 encoding and nothing else. If you prefer to work with a
> > GBK editor, call iconv later, for example
>
> I also learned that this issue can be worked around by the following
> command immediately after the hyperref package's invoking like this:
> [...]
But only dvipdfmx understands this.
> % For the gb1212 encoded tex file:
> \AtBeginDvi{\special{pdf:tounicode GBpc-EUC-UCS2}}
> % For the gbk encoded tex file:
> \AtBeginDvi{\special{pdf:tounicode GBK-EUC-UCS2}}
> % For the utf-8 encoded tex file:
> \AtBeginDvi{\special{pdf:tounicode UTF8-UCS2}}
Using CJKutf8.sty, this isn't necessary, since it already creates
proper ToUnicode cmap files.
> For a more detailed version of the above method, please find the
> attachment. But, with this method, I will meet the errors like
> this:
>
> --------------------------
> ! Improper alphabetic constant.
> <to be read again>
> [EMAIL PROTECTED]
> l.38 \section{简介}
>
> ?
> --------------------------
>
> Any hints on this issue?
Sorry, I don't have time to look into this more closely. Given that
Unicode is the de-facto standard of today (and both XeTeX and luaTeX
use this encoding exclusively), I don't see much sense in creating new
documents with a legacy encoding like GB, let alone GBK.
However, you might analyze this by yourself, adding
\tracingall
\tracingonline0
at an appropriate place in your document. Then check the log file and
find out where the problem starts.
Werner
_______________________________________________
Cjk maillist - [email protected]
https://lists.ffii.org/mailman/listinfo/cjk
