On Thu, Feb 20, 2003 at 10:30:20AM +0000, Michael Nordstr�m wrote: > You have to understand my view on this; if there is a bug somewhere in > the viewer I want to be able to fix it. However, if we start to include > stuff that can only be handled by using non-free tools (probably also > only running on Windows) then I can't do that...
I understand. In that case what I'll do is write a perl script or something to handle job. Specifically what I'm trying to do is convert a standard 'NFNT' font resource into an 'nfnt' extended font resource. Once that's done then the font would then be defined as 'double density' and show up properly on OS5 devices as a tiny/small/etc font. I just need codewarrior to find out exactly how an 'nfnt' resource is structured compared to an 'NFNT'. It's that compiled resource that I wanted to commit into plucker's repository as binary data. Incase a perl script is not feasable people can still build the viewer and take advantage of the small font. No matter :) I'll get a script going so we don't have any non-free bits floating around. -- Adam McDaniel Array.org Calgary, AB, Canada _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
