![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#21
| |||
| |||
|
|
unfortunately then i would loose all the benefits of sending to the printer texts and graphic shapes which are resolution independent. I was considering this approach earlier but i don't think this is the right path for me. The printer i'm targeting uses native 600dpi resolution - to generate best quality curves my preprinted bitmaps would need to have that. When printing pages of sizes up to twice the A4 (A4 is similar to US Letter size) i would quickly end up with about 120MB postscript files per page, regardless the actual use of images on pages. that would certainly kill the rip server when printing documents that has up to 80 pages. not mentioning the humongous amount of storage i would need for that in extreme cases i would need almost 10GB for one postscriptfile! This is certainly the case when it is worth to invest processor time and memory in the right preprinting process - especially if i have available a spare dual core intel server for that ![]() |
#22
| |||
| |||
|
|
Bob Powell [MVP] wrote: I think that the problem here is that the interpolation mode will force the image to use a background colour around the image. This can give an unwanted halo effect. yes that is correct. When resizing the image you may need to create several different images, for example, one for light backgrounds and one for dark. what if background is another image? you now image on top of image on top of other image and so on - each edge may have totally different background. You may also wish to ignore interpolation for the printer image and go for a rougher looking but more true-to-the-original image. this sound promising. could you be more specific? |
#23
| |||
| |||
|
|
In such a case one cannot win... |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |