From: Till Kamppeter <till.kamppeter@gmail.com>
To: Kai-Uwe Behrmann <ku.b@gmx.de>
Cc: gs-devel <gs-devel@ghostscript.com>,
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>,
Hin-Tak Leung <hintak_leung@yahoo.co.uk>
Subject: Re: [Printing-architecture] [gs-devel] Re: poppler vs. GhostScript & color management
Date: Wed, 03 Sep 2008 08:18:35 +0200 [thread overview]
Message-ID: <48BE2C3B.4070407@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0809021917440.5106@sirius.rasena>
Can everyone here with enough knowledge about color management and PDF
standards file bugs against both Poppler and Ghostscript for everything
which is wrong? Please attach sample PDFs to your bug reports and
perhaps also image files (JPG, PNG, ...) which show how the output
should look like.
Till
Kai-Uwe Behrmann wrote:
> Hello,
>
> first thanks to considering the colour management argument. ...
>
> Am 02.09.08, 18:43 +0200 schrieb Till Kamppeter:
>> 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.
>
>> 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).
>
> In regards of a comparision I would say Xpdf has no ICC support as of
> v3.02.
> On a PDF with lots of different ICC colour spaces, Xpdf does get
> only sRGB right.
> Ghostscript renders correct all those ICC profile taged images from the
> same test PDF.
>
> Colour people where really excited to see all the capbilities in
> Ghostscript since v8.15 and especially 8.5x. It is good for support and
> the over all appearance of a system to say to clients and custumers, there
> is a CM wise working printing solution already installed on your system.
> In the past we had often to suggest for difficult replacements or thierd
> party products.
>
>> Hin-Tak wrote:
>>> I think we have a few project ideas here for next year's GSoC :-), for both
>>> poppler and ghostscript...
>
> ... and support of transparent images, which is missed in both.
>
> kind regards
> Kai-Uwe Behrmann
next prev parent reply other threads:[~2008-09-03 6:18 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
[not found] ` <Pine.LNX.4.64.0809021917440.5106@sirius.rasena>
2008-09-03 6:18 ` Till Kamppeter [this message]
[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 ` [Printing-architecture] [gs-devel] " 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=48BE2C3B.4070407@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=gs-devel@ghostscript.com \
--cc=hintak_leung@yahoo.co.uk \
--cc=hvengel@astound.net \
--cc=ku.b@gmx.de \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=printing-japan@lists.linux-foundation.org \
--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.