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: Tue, 09 Sep 2008 17:58:48 +0200 [thread overview]
Message-ID: <48C69D38.4020607@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0809091644001.5208@sirius.rasena>
Kai-Uwe Behrmann wrote:
> I've sent the below information to the respective bug trackers.
> The web has many good resources about PDF colour management. The OpenICC
> list is one good place to talk with people about this toppic or obtain
> specific hints.
Can you post links to the bug reports/feature requests you have made?
Till
next prev parent reply other threads:[~2008-09-09 15:58 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 ` [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 [this message]
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=48C69D38.4020607@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.