Am 26.10.2010 um 16:22 schrieb Pander:
Is it possible to have more information printed to command line and
log
file for where this error originates?
Invoke xdvipdfmx with -v or -vv or -vvv or ... or invoke xelatex as
"xelatex -output-driver='xdvipdfmx -vv'" etc.
You could also invest a bit of time looking at the font in FontForge,
particularly checking the glyph #2448.
--
Greetings
Pete
To be is to do.
– I. Kant
To do is to be.
– A. Sartre
Yabba-Dabba-Doo!
– F. Flintstone
--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
