From: Till Kamppeter <till.kamppeter@gmail.com>
To: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
Cc: gs-devel <gs-devel@ghostscript.com>, OTANI Koji <sho@bbr.jp>,
Tobias Hoffmann <th55@gmx.de>,
"Hal V. Engel" <hvengel@astound.net>,
Printing-japan <printing-japan@lists.linux-foundation.org>,
"printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] poppler vs. GhostScript & color management
Date: Tue, 02 Sep 2008 18:43:46 +0200 [thread overview]
Message-ID: <48BD6D42.7000209@gmail.com> (raw)
In-Reply-To: <48BD5F88.5040109@yahoo.co.uk>
We switched now from a PostScript workflow without color management to a
PDF workflow without color management. Next step would be to have color
management being a standard part of the printing infrastructure.
All drivers except CUPS raster drivers (IJS, Ghostscript built-in, ...)
still use Ghostscript in the first implementation of the CUPS PDF
workflow in Ubuntu Intrepid. Foomatic 4.0 makes it possible that PDF
gets fed into Ghostscript and using nearly the same Ghostscript command
lines as before.
Color management is not yet completely implemented in both renderers. It
is really a good idea for next GSoC to do projects on making color
management work in both Ghostscript (if GS upstream developers do not
complete it in 8.64, due in Feb 2009) and Poppler (and also the CUPS
imagetoraster filter).
Till
Hin-Tak Leung wrote:
> Till Kamppeter wrote:
>> Hal, thank you very much for your posting. This is a very important
>> point.
>>
>> I think under these circumstances we should switch all PDF
>> rasterization to Ghostscript. Otani-san, can you change the
>> pdftoraster (and if needed also the pdftopdf filter) to be based on
>> the Ghostscript library libgs? Lars, Alex, can you make the preview of
>> the printing dialog be libgs-based? Tobias, Hin-Tak, can you do the
>> appropriate changes on pdftoijs?
>
> I don't know enough of the other issues, but libgs and poppler being
> substantially different in so many levels, switching from one to another is
> not trivial; also, on pdftoijs going libgs - it won't be much different
> from the existing postscript-based workflow, other than some efficiency
> advantage of a customized/dedicated libgs client vs a general ghostscript
> command-line shell-script.
>
>> We do not need to rush this into Intrepid or into the GSoC, but at
>> some point we should be standards-conforming as far as possible and we
>> should also support color management.
>>
>> Ghostscript developers, what are the plans for support for handling
>> all "CIE based" objects using CIE compliant techniques and ICC
>> profiles in Ghostscript 8.64?
>
> I think we have a few project ideas here for next year's GSoC :-), for both
> poppler and ghostscript...
>
> Hin-Tak
>
>
>
>
next prev parent reply other threads:[~2008-09-02 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200808281229.31215.hvengel@astound.net>
2008-09-02 14:39 ` [Printing-architecture] poppler vs. GhostScript & color management Till Kamppeter
[not found] ` <48BD5F88.5040109@yahoo.co.uk>
2008-09-02 16:43 ` Till Kamppeter [this message]
[not found] ` <Pine.LNX.4.64.0809021917440.5106@sirius.rasena>
2008-09-03 6:18 ` [Printing-architecture] [gs-devel] " Till Kamppeter
[not found] ` <Pine.LNX.4.64.0809082211350.5851@sirius.rasena>
[not found] ` <Pine.LNX.4.64.0809091644001.5208@sirius.rasena>
2008-09-09 15:58 ` Till Kamppeter
2008-09-03 3:27 ` [Printing-architecture] " Alex Wauck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48BD6D42.7000209@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=gs-devel@ghostscript.com \
--cc=hintak_leung@yahoo.co.uk \
--cc=hvengel@astound.net \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=printing-japan@lists.linux-foundation.org \
--cc=sho@bbr.jp \
--cc=th55@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.