From: Hrafnkell E. <he...@kv...> - 2000-04-23 20:02:05
|
Hi On Sun, Apr 23, 2000 at 01:34:18PM -0400, Karl Heinz Kremer wrote: > > Could I find something out by taking the output from the windows > > or printpro driver and try to parse that into escp2 commands? > > You can use the unprint command to "dis-assemble" the ESC/P2 code. hmm.. It just coredumped :) Also on the ghostscript output. I went through the output from the windows driver when letting in print in 360dpi and the output looked very much like what the print-escp2.c driver should generate (some differences though). Do we have access anywhere to documentation on the commands used in REMOTE mode? Then I looked at the output from ghostscript when using the gimp-print driver and it looked funny. I then installed gimp-1.1.20 and compiled the gimp-print plugin to use with it. I was able to use the Epson 640 driver to print in both 360 dpi and 720 microweave. The other modes just ejected paper. I used hybrid floyd steinberg dithering and in both cases the image looked veeerrry grainy and way to bright. I was printing a photograph of me and around my head I could see strange artifacts, like a outline drawed around it. I have dark hair and the background is white. It looks like the quantization error is being diffused in a very regular manner to those pixels (it is a mix between floyd steinberg and ordered dithering?). Hmm I just checked.. this effect is even worse when using ordinary floyd steinberg with 720dpi microweave. Now it looks like an edge-detect filter is used on the image first, then the edges are shifted from their correct place and added to the image and then it is printed. The printout is also very bright (brightness setting 100 in adjust color). I think I'm about to get chockolate-poisoning now :) -- //-----------------------//------------------------------------------------- // Hrafnkell Eiriksson // // he...@kv... // // TF3HR // "Blessed are they who go around in circles, // // for they shall be known as Wheels" |