Re: [ft] Type 1 PFM read problem.

[mpsuzuki]

Hi Rajeev,

On Thu, 30 Mar 2006 20:00:23 -0800
"Rajeev Pahuja" <address@hidden> wrote:
>You can download this font for testing from :
>http://metatag-report.com/files/fonts/TYPE1/A

$ od -x ATLAINLN.PFM
0000000 0200 0af3 0000 0000 0000 0000 0000 0000
0000020 0000 0000 0000 0000 0000 0000 0000 0000
*
0000100 0000 0081 000a 012c 012c 02e1 0000 0000
0000120 0000 9000 0001 0000 0000 2221 b803 0005

According to Adobe's specification the header
should be recognized as:

data in font    specification
0x0200          (x) dfVersion Two bytes 256
0x00000af3      (o) dfSize Four bytes The exact size of the PFM file, in bytes
0x00...         (?) dfCopyright 60 byte string, null padded Copyright string
0x0081          (o) dfType Two bytes 129
0x000a          (o) dfPoint Two bytes 10
0x012c          (o) dfVertRes Two bytes 300
0x012c          (o) dfHorizRes Two bytes 300

Although I've not checked following structure is
not broken, I guess Microsoft implementation ignores
dfVersion. I'm not sure if FreeType had better
be more permissive as Microsoft implementation.

Oops, I found other broken PFM, AACHENB.PFM

$ od -x AACHENB.PFM
0000000 0100 0778 0000 6f43 7970 6972 6867 2074
0000020 6942 7374 7274 6165 206d 6e49 2e63 3120
0000040 3839 2d36 3931 3239 202e 6c41 206c 6972
0000060 6867 7374 7220 7365 7265 6576 2e64 1500
0000100 180a 0081 00f0 012c 012c 03e1 00eb 0000

0x0100          (o) dfVersion Two bytes 256
0x00000778      (o) dfSize Four bytes The exact size of the PFM file, in bytes
0x6f43 ...      (?) dfCopyright 60 byte string, null padded Copyright string
0x0081          (o) dfType Two bytes 129
0x00f0          (x) dfPoint Two bytes 10
0x012c          (o) dfVertRes Two bytes 300
0x012c          (o) dfHorizRes Two bytes 300

Regards,
mpsuzuki