gimp-print-devel

Re: [Gimp-print-devel] canon-unprint

[<sh...@al...>]

> * Added parse_canon() with calls to page_update()
> * Added rle_decode() since canon rather knows the compressed buffer size than
> the uncompressed
> * Added switching from parse_escp2() to parse_canon() via environment variabl
> e

I spent about 30 seconds scanning your code.  What I saw looked pretty good.

> UNPRINT:
>    "UNPRINT=canon ./unprint" will use parse_canon()

Ok, although I'd like to remove this feature eventually.

Unfortunately, there's no really simple way to do that.  What we want is
for each routine to be given a file pointer and be able to read that file
from the beginning, yet we need to read some of the file to determine what
the file type is.  There are only two ways to do this that I can think of.
One is to create a pipe internally, fork the process, read the data in
one process, determine the file type, and write the data to the pipe which
then gets read and parsed by the appropriate child process.

The other way is to read to a buffer, and then only read from the file
if the buffer is empty.

I think the second method would require less in the way of computer resources,
although I think the first is stylistically cleaner.

I haven't decided which is the better way to go.

> The output produced from canon-printfiles looks extremely poor - there are
> some weird artefacts. Eric, could you please have a look at it? Maybe I've go
> t
> something terribly wrong?

I just compiled it.  I'll have a look.

Eric

Re: [Gimp-print-devel] canon-unprint

[<sh...@al...>]

> The output produced from canon-printfiles looks extremely poor - there are
> some weird artefacts. Eric, could you please have a look at it? Maybe I've go
> t
> something terribly wrong?

Hmm, I wasn't able to get it to unprint at all.  Are there particular
settings I should use when printing the image to a file?  I choose Canon
BJC 3000, photo ink, 720 DPI.  When unprint is given the file when
UNPRINT is set to canon, I get the following:

    Warning: Unknown command ESC [ 0x61 at 0x0000000A.
    canon: res is 720 x 720 dpi

    K:129->223Y:170->223M:146->223C:145->223Error: unsupported color type 0x00.

BTW, on my 1024x768 LCD, the driver selection box already scrolls off the
bottom of the screen.  Is there anything after Canon BJC 3000?  I can't tell,
I'm out of pixels.  We should probably change the driver selector to be
two pull down menus.  The first menu would be manufacturer, the second would
be a list of models.  That should make the lists a little more manageable.

Eric

Re: [Gimp-print-devel] canon-unprint

[Andy T. <th...@ph...>]

sh...@al... wrote:

> Hmm, I wasn't able to get it to unprint at all.  Are there particular
> settings I should use when printing the image to a file?  I choose Canon
> BJC 3000, photo ink, 720 DPI.  When unprint is given the file when
> UNPRINT is set to canon, I get the following:
>
>     Warning: Unknown command ESC [ 0x61 at 0x0000000A.
>     canon: res is 720 x 720 dpi
>
>     K:129->223Y:170->223M:146->223C:145->223Error: unsupported color type 0x00.

Hmm - could be an older version than mine - when did you update?

Andy.

Re: [Gimp-print-devel] canon-unprint

[Andy T. <th...@ph...>]

sh...@al... wrote:

> > strange... anyway, I've just commit a bugfixed version of print-canon.c that
> > actually produces valid output and a slightly modified unprint.c
>
> I'm on the repository mailing list, so, I see what you commit as soon as
> you commit it.  Assuming I'm reading my mail that is...

Ah, how gan I get there? :-)

> > I've printed to a file using the bjc6000 driver @ 360x360 dpi, postcard, plai
> > n
> > paper, small scaling and was able to deprint it with canon-unprint.cpp which
> > showed me the printer driver works allright now. however, unprint still
> > produces noise only...
>
> Ok, if you can't figure it out shortly, I'll have a look at it tomorrow.
> It's past my bed time for today, though.

So have a good night then.

Andy.

Re: [Gimp-print-devel] canon-unprint

[Robert L K. <rl...@al...>]

   Date: Wed, 23 Feb 2000 19:01:43 +0100
   From: Andy Thaller <th...@ph...>

   sh...@al... wrote:

   > > strange... anyway, I've just commit a bugfixed version of print-canon.c that
   > > actually produces valid output and a slightly modified unprint.c
   >
   > I'm on the repository mailing list, so, I see what you commit as soon as
   > you commit it.  Assuming I'm reading my mail that is...

   Ah, how gan I get there? :-)

Is there anyone on here who would *not* like to be on the commit list?
You can add yourself by checking out the CVSROOT module, editing
loginfo, and checking it back in.

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton