On 2012-12-17 19:04, Khaled Hosny wrote: > On Mon, Dec 17, 2012 at 06:47:19PM +0100, Pander wrote: >> Hi all, >> >> I am getting errors with XeLaTeX for Unicodes 01f01b up to 01f030. >> Attached is a test that fails and results in: >> >> ** ERROR ** Type2 Charstring Parser: Parsing charstring failed: >> (status=-2, stack=48) >> >> Output file removed. >> ) >> Error 256 (driver return code) generating output; >> file test.pdf may not be valid. >> >> Strange thing is that 01f01a is processed correctly and beyond 01f030 >> also. I have asked the maintainer of GNU FreeFonts to test this but he >> cannot reproduce this problem. Can any of you? >> >> I am using latest TeX Live and latest GNU FreeFonts. > > Runs fine here, but this sounds like a font-related xdvipdfmx error. > > Try running: > > xelatex --no-pdf test
xelatex --no-pdf test This is XeTeX, Version 3.1415926-2.4-0.9998 (TeX Live 2012) restricted \write18 enabled. entering extended mode (./test.tex LaTeX2e <2011/06/27> ... [1] (./test.aux) ) Output written on test.xdv (1 page, 660 bytes). Transcript written on test.log. > xdvipdfmx -v test xdvipdfmx -v test <FONTMAP:pdftex.map><FONTMAP:kanjix.map><FONTMAP:ckx.map> ** ERROR ** Could not open specified DVI (or XDV) file: test Output file removed. > and check which font file is causing the error. Eeeuh, I am trying to use FreeSerif. I only use OTF and TTF fonts. > Regards, > Khaled > > > -------------------------------------------------- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
