Adding for reference: Date: Mon, 11 Apr 2005 15:59:34 -0700 (PDT) From: "Derek B. Noonburg" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
>> >> Hey! I did pdftops; gv on it and: > gv 3.6.1-9 works fine on http://www.noise.com.tw/standard/AW.PDF > but as you see > $ gv zx.pdf > looks terrible. So OK, not a pdf2ps problem. > If you know what gv problem it is, please report it. That file (AW.PDF) has vectorized all of the fonts, which is why it looks fine. My guess is that ghostscript is running into the same issue as FreeType. Apple apparently has a patent which covers (some part of) the bytecode interpreter used by TrueType font engines. I'm not familiar with gs's TrueType implementation, but FreeType ships with the interpreter disabled by default, and that causes major problems with some CJK fonts that use the interpreter to move sections (not sure if that's the right word) of the characters around. The interpreter was initially intended (by the TrueType format architects) to be used for hinting, but was later co-opted into use for other things (or at least that's the story I've heard). So FreeType without the interpreter works ok for *most* fonts, but fails badly on a few. As far as I know, Apple hasn't sued anyone over the patent(s). But FreeType is being (justifiably) paranoid, and shipping with the interpreter off by default. I haven't looked at ghostscript that closely, but they may be doing something similar. In any case, if this is in fact the relevant problem, I'm sure the ghoscript folks are well aware of it. - Derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
