|
From: | Hin-Tak Leung |
Subject: | [Devel] Re: ftdump, and oto question. |
Date: | Mon, 26 Jul 2004 09:18:45 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040608 |
Werner LEMBERG wrote:
Thanks. This is a strange font -- it starts with the byte sequence `0x00 0x02 0x00 0x00', while a normal TTF must start with `0x00 0x01 0x00 0x00'. If you change it, the font will be loaded.Yes, I took a look at the other 7 fonts which failed, and they all have this strange header, and indeed, correcting it does the work. Strange enough 3 from the same bundle (a total of 11) have the correct 0x00 0x01 0x00 0x00 header. I re-read the docs that came with it, apparently those Arphic fonts where intended for Microsoft Windows 3.1 Chinese version. (they all have a time stamp of Sept 94).I've made FreeType accept the 0x00020000 tag. Werner
Thanks. I wonder if it is either an off-spec anomaly in the early days of truetype, some kind of copy-protection scheme (font editors, etc probably wouldn't want to load it up?) or what. But yes, I made modified versions of them to 0x00010000 a few days ago and CJK/LaTeX+dvipdfmx+xpdf was happy both
displaying and printing, so the fonts seem to be otherwise well-formed. Hin-Tak
[Prev in Thread] | Current Thread | [Next in Thread] |