|
Ok, I fixed some stupid errors that were preventing multi-page PDFs from working. Thanks go to Scott for one of those (buffer overflow - it wasn't the variable gdb was reporting that was having a problem. variable 'text' was being written to way beyond it's bounds and that was wrecking the other variables. Dumb, dumb, dumb). Also the problem with job logs being print all squished should be fixed, too. Thanks to Scott again for pointing me to the AHPP command. Time to test, test, test! If anyone wants to try printing directly to PDF files, give this a shot. Some things are not ready yet, but it would be good to know what is broken that shouldn't be. Here is what is left to do in order of importance: 1. Page size. This works sometimes and sometimes it doesn't. I truly am stumped on this one. 2. Absolute vertical position to. I see this happen once in a while, but it hasn't bothered me yet. But I bet there are some reports out there that look stupid when run through scs2pdf as it is right now because of vertical positioning issues. 3. Fonts. There are probably a million things we *could* do with fonts, but we probably shouldn't. But we do need things like bold, larger size, or whatever an *SCS printer can do. That's all I can think of. The diff and the entire C source file can be found at: http://www.eaerich.com/scs2pdf.c.diff http://www.eaerich.com/scs2pdf.c Scott, can you commit these changes? This should make scs2pdf actually work for people, much better than what is already there. Note for developers: I placed #ifdef DEBUG ... #endif around fprintf statements that dealt with SCS codes that I think we handle correctly. If you want to see all that stuff (and a little more) you need to #define DEBUG. James Rich james@eaerich.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.