🚀 go-pugleaf

In article <1991Apr29.195913.5520@ico.isc.com> rcd@ico.isc.com (Dick Dunn) writes:
}jlr1801@aim1.tamu.edu (Jeff Rife) writes:
}> >    - "What's that silly binary code doing on the PFB files at [archive]?"
}> 
}> That's part of the encoding of an Adobe Type 1 font.  It's documented.
}
}It is documented, but it's not part of the Adobe Type 1 font.  The .pfb
}files are divided into chunks of data with a little header-descriptor on
}each chunk.  This header is for the use of a PC-based downloader; it should
}not be sent to the printer.
}
}You can tell it's *NOT* PostScript because the first byte has value 80 hex,
}which is not valid for Level 1 PostScript.  In Level 2, 0x80 it would be an
}indicator of a "binary object sequence"--which is NOT what the .pfb is.
}

I'm sorry, I must have been on drugs or something. ;->  I missed the point
of the question entirely.  I assumed the first enquiry was concerning the
hex bytes within the "currentfile eexec.....cleartomark{restore}if" section.
I never even noticed the binary on at the beginning of the file.  I guess I
just assumed the fonts were OK because I never had any trouble, and I hadn't
done anything special, but I assume my application is taking care of it.

}
}The header consists of:
}	- 0x80: flag byte
}	- type byte:  1=text, 2=binary data, 3=EOF
}	- length: 4-byte little-endian integer counting the number of data
}	  bytes which follow

Thanks for the info on this header.  I will file it, and stand corrected.
It is so much fun to make a fool of yourself in front of millions of people.
:-)

--
Jeff Rife   P.O. Box 3836   |   "Because he was human; because he had goodness;
College Station, TX 77844   |    because he was moral they called him insane.
(409) 823-2710              |    Delusions of grandeur; visons of splendor;
jlr1801@aim1.tamu.edu       |    A manic-depressive, he walks in the rain."