> > > Well, yes, but it actually hides the very problem, namely, that
> > > commands defined within a CJK environment must be defined as
> > > global.
> >
> > Thanks for clearing up that for me, that helps me a lot for the
> > future too. I could not get your example to work but will try
> > with the latest git repos files on my home machine later.
Don't worry about that; there's certainly a typo on my side :-)
A rule of thumb: If you define a macro which contains UTF-8 encoded
characters, it must be defined within an environment which is set up
for UTF-8 handling so that the leading bytes of UTF-8 sequences are
active characters:
\begin{document}
\usepackage{CJK}
\begin{CJK}{UTF8}{}
... define macros with \gdef ...
\end{CJK}{utf8}
\begin{document}
\begin{CJK}{UTF8}{...}
... use defined macros
\end{CJK}
\end{document}
> > Does that mean that, in generel, instead of the LaTeX \newcommand
> > (which I assume is local) we need to use the TeX method of \gdef
> > for macros when using the CJK package and possible CJK characters
> > will enter into either the argument or the body of the macro?
Yes.
Werner
_______________________________________________
Cjk maillist - [email protected]
https://lists.ffii.org/mailman/listinfo/cjk
