> > [...] if you want to access, say, U+2018, it is first checked
> > whether LaTeX itself provides a definition for this character
> > (defined with \DeclareUnicodeCharacter in a DFU file -- this is
> > output in the log file, BTW), and then CJKutf8.sty looks up the
> > CJK definition. With other words: Your definitions in the FDX
> > file are never seen by LaTeX!
>
> Aha! My first time to hear of .dfu files.
:-)
> I am supposing that removing the definition from the utf8enc.dfu
> file is not an acceptable solution.
Yep.
> Is it possible to force latex to read the definition in the fdx file
> and overwrite whatever it had previously read from a .dfu file? I'm
> afraid I still know far too little about latex and tex programming
> to see exactly what issues are at stake here.
Well, \DeclareUnicodeCharacter acts globally (and is allowed in the
preamble only). However, we need to override it locally.
> Is the setting or "fetching" of the glyph for horizontal CJK also
> not under control of the CJK package but rather done by normal latex
> in this case?
CJKutf8.sty redefines some underlying macros of \CJKchar, regardless
of the writing direction ([EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL
PROTECTED], [EMAIL PROTECTED]). I
could imagine to add a macro which switches to and from the original
definitions of those four macros. Another possibility is to activate
and deactivate the particular macros defined with
\DeclareUnicodeCharacter for those 6 characters.
Of course, a much simpler solution is to not use CJKutf8.sty...
Werner
_______________________________________________
Cjk maillist - [email protected]
https://lists.ffii.org/mailman/listinfo/cjk
