Getting image to printer & pdf at more than 72 dpi
Posted: Thu Jun 07, 2012 5:01 pm
I've run into a roadblock here, which could kill my project completely.
Images, even 300dpi png, are getting truncated to 72dpi (screen density) before being sent to the printer or pdf.
Is there *any* way to do this within livecode?
I suppose this could be done by exporting without them, and then using a shell script to use ghostscript to print print the images and the livecode output onto yet another pdf, but given that my output is generally 60-90 pages, this would be a nightmare.
For pages that are pure scans, I could also use apple scripting, I suppose, to use preview to stick scanned pages between the pages I generate--but again, this would be a nightmare to maintain.
Also, both of this hacks would be really out of place in a commercial project (along with the issues of either distributing the gpl version of gs, forcing someone to install it, or licensing the commercial version just to work around a bizarrely missing feature of livecode . . .)
We asked tech support almost a month ago, and still don't have a response.
EDIT:
Since first posting, I've found that if I make the size of the stack equal to the size of the png, but specify the output rectangle, this puts all the pixels into the output pdf. This will let me include scanned pages, but doesn't solve the case where I need to add information to the scanned image.
Perhaps selecting all the objects on the regular page of my output, and somehow pasting them scaled? (I really only have fields to deal with).
Or select them in a loop, copy, paste, multiply field & font size by 200/72 (the numerator being the png density), then set the topleft of the pasted object to that same ratio times the original topleft?
All of these are ugly; it makes no sense that the screen density of a scaled object is used . . .
help!
hawk
Images, even 300dpi png, are getting truncated to 72dpi (screen density) before being sent to the printer or pdf.
Is there *any* way to do this within livecode?
I suppose this could be done by exporting without them, and then using a shell script to use ghostscript to print print the images and the livecode output onto yet another pdf, but given that my output is generally 60-90 pages, this would be a nightmare.
For pages that are pure scans, I could also use apple scripting, I suppose, to use preview to stick scanned pages between the pages I generate--but again, this would be a nightmare to maintain.
Also, both of this hacks would be really out of place in a commercial project (along with the issues of either distributing the gpl version of gs, forcing someone to install it, or licensing the commercial version just to work around a bizarrely missing feature of livecode . . .)
We asked tech support almost a month ago, and still don't have a response.
EDIT:
Since first posting, I've found that if I make the size of the stack equal to the size of the png, but specify the output rectangle, this puts all the pixels into the output pdf. This will let me include scanned pages, but doesn't solve the case where I need to add information to the scanned image.
Perhaps selecting all the objects on the regular page of my output, and somehow pasting them scaled? (I really only have fields to deal with).
Or select them in a loop, copy, paste, multiply field & font size by 200/72 (the numerator being the png density), then set the topleft of the pasted object to that same ratio times the original topleft?
All of these are ugly; it makes no sense that the screen density of a scaled object is used . . .
help!
hawk