Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: [Digital BW] QTR Linux and qtcups impressions

2003-11-12 by Mike Finley

Thanks, Roger. I had made sure that the image was the resolution I
wanted to use when I saved it as a TIFF from photoshop (and converted
it from RGB .PSD to 8 bit monochrome uncompressed TIFF). I've double
checked with identify using the script you emailed me, and that has
confirmed the resolution and aspect ratio are as I expected. 

I'd forgotten qpr, so I'll have a look at that and see how that works
- at least there I should be able to see the lpr command it makes, and
see what's going on (and maybe write derivative scripts for specific
purposes). Getting away from an unpredictable 'helpful' GUI interface
might help!

thanks,
mike

On Tue, 11 Nov 2003 15:50:09 -0700, Roger wrote:

>Hi Mike,
>
>I haven't had this problem but qtcups is fussy about the resolution setting
>and will produce odd results if the image resolution and the resolution set
>in qtcups are not the same (whole numbers). There is a Linux program that
>may help to check the resolution. In an open terminal try entering
>
>    identify -format "%w %h %x %q"  name of image (e.g. foo.tif) The first
>two figures are the height and width in pixels, the third is the image
>resolution and the last is the bit depth. If you would like I can script it
>for you and send you a url you can download from.
>
>There are other programs you can print from. A more direct approach than
>qtcups is to use David Wroblewski's qpr script which is available in the
>files. If you are using a different printer from a 2200 then you would need
>to edit the printer setting (line 11) in it with gedit or the like.
>
>No question using QTR-Linux is not like printing directly from PostScript
>but I have found the results to be worth the grief. Chacon a son gout
>
>Roger

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.