> There're just too many READMEs littering around on a Linux box, you
> know.
Littering? I don't think so. It is good practice that in the
<TEXMF>/doc/<format>/<package> subdirectory you can find the package's
documentation. For CJK, this is <TEXMF>/doc/latex/CJK/. If your TeX
system has CJK.sty available but the docs are missing you should
complain to the package maintainer.
> >Looking into arialuni version 0.84 and cyberbit 1.1 (this is what I
> >have on my box) I can see that the latter has a real glyph for
> >uniFF0C, while the former uses the `comma' glyph as a subglyph.
> >Maybe this doesn't work properly with pdftex.
>
> How can I check it myself?
Use fontforge.
> In fact your updated Unicode.sfd that support the full Unicode range
> brought me to this mailing list in the first place. The subfonts
> script completed in 3 minutes instead of hours on my system. Is it
> normal?
Yes, if you use an older version of fontforge. Newer ones try much
harder to reduce the number of outline points.
> [...] I copied the PFB/ENC/TFM to the texmf tree and regenerating
> the PDF. U+FF0C seems to appear now, and the segfault disappeared
> (so I didn't bother to upgrade pdftex at this point anyway if it's
> still usable). That's marvellous. Will verify again on the other
> system I have at a later time.
The biggest advantage of using Type 1 fonts is that dvips works too.
Werner
_______________________________________________
Cjk maillist - [email protected]
http://lists.ffii.org/mailman/listinfo/cjk
