> I only learned of this mailing list a few days ago so I think I may
> have a try here.
This surprises me, since I've mentioned it in the README file of the
CJK package, already in the second paragraph.
> I'm trying to pdflatex the following document: [...]
>
> pdflatex segfaults toward the end.
I think this is a bug in pdfeTeX. IIRC, this or a similar problem has
been mentioned on the pdftex mailing list.
Please check the pdftex mailing list archive and try to download the
latest version from Sarovar -- probably compiling with the `-g -O0'
compiler flags to activate debugging, and to disable optimization. In
case this doesn't fix the issue, submit a bug report to the pdftex
maintainers.
> In the past, probably before change to pdfeTeX, an empty space was
> substituted for the comma in the PDF without segfault. I don't quite
> understand why the font contained the glyph for full-width comma (U+FF0C)
> but it (in fact all U+FFxx glyphs) refuse to render in the final PDF for
> this particular font.
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.
> The latest CJK package and Unicode.sfd didn't help with the issue.
> Any ideas on why it is failing? It seems so strange that I cannot
> explain in any sensible way.
As a workaround I suggest that you use the subfonts.pe script from CJK
4.6.0 (or the latest snapshot) to split arialuni.ttf in a set of Type 1
subfonts. Be warned that it takes hours even on a fast computer until
the conversion has finished! The proper SFD file is Unicode.sfd; Some
time ago I've posted an updated version to this list; you might find
it also in the `freetype1-contrib' CVS repository (available from
savannah.gnu.org/projects/freetype).
Werner
_______________________________________________
Cjk maillist - [email protected]
http://lists.ffii.org/mailman/listinfo/cjk
