CompuServe Messages

Chris Well, the line beginning with % is simply a comment so should cause no problems at all (lines beginning with %% are part of the document structuring convention, and should have a specified syntax following the %%, but they're still to be ignored by the interpreter) The setting of the Encoding entry should also be perfectly okay since it's a quick way of setting up an AdobeStandardEncoding without having to specify it yourself. In other words … the /Encoding StandardEncoding def does all the work that defining the array and then setting each entry one at a time. I've looked at the source code for POST and it handles StandardEncoding just fine. The /FontInfo 13 thing is also fine … it's just the PostScript equivalent of a DIM FontInfo() array definition (in effect) and all 3.5 is doing is making a little more space. However, I've examined the encrypted section of the Lilith font and I have discovered that there is some unusual code in there. In _theory_ it should still work, but it assumes the state of the stack and adds a comment. The black-book specification for Type-1 fonts doesn't disallow this sort of thing, but it does look very odd and it's possible that this is where POST is falling over. I'll continue investigating. Unfortunately, Aylward has stated he will no longer support POST so I don't know if we'd get anywhere with him … however, I may drop him a line. Mike (from the UK)