Hi, Andy-- On Mon, Dec 10, 2012 at 1:06 PM, Andy Bennett <[email protected]>wrote:
> > I've just realised that I have had the attached patch lurking around for > a couple of years! > It fixes up the pdf-font declarations and then ensures that they get > installed. > Thanks for doing that! However, your patch is out of date. It is for version 1.0 of the egg, while the current version is 1.0.2. The patch failed on the setup file, but the fix was simple. I'm attaching an updated version; you might like to check it to see if it looks right. Also, this raises a couple of questions for me. Oh, and for background, I'm the one who initially began porting this egg from PLT 3 or 4 years ago; I didn't do much, though, and Felix was interested, so I let him take it off my hands, and I guess he completed the Chickenizing process. Anyway: 1. I notice the setup file installs *.o files. Is that to enable static compilation? If so, I wonder if we really need that? 2. Part of the reason I abandoned the porting effort was that I need a PDF library that can embed arbitrary fonts. I was considering adding that functionality to the egg, but I looked through the PDF spec and never found an explanation of how to obtain the font data to embed (though, as you may be aware, it's a thick book, and it's quite possible I missed something). It has occured to me that possibly you just open the font file and write the bytes into a stream object ... but that can't be the whole answer, because there is also subsetting. Do you happen to know how that stuff works? -- Matt Gushee > > > > Regards, > @ndy > > -- > [email protected] > http://www.ashurst.eu.org/ > 0x7EBA75FF > > > _______________________________________________ > Chicken-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/chicken-users > >
pdf-font.patch
Description: Binary data
_______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
