FOP fans,

I could also use cmyk support in fop. My options are to buy some xsl fo
implementation that supports it or trye to contribute to fop (assuming the
community lets me)

Could someone give me a very rough estimate on how much work it would
require, including getting acquainted with the fop architecture.



Jeremias Maerki-2 wrote:
> On 31.03.2006 21:48:43 Max Berger wrote:
>> I know I have no vote in this, but I do disagree.
> Every opinion is always welcome.
>> 1) I still believe that PDF is a print medium and should therefore
>> default to CMYK colorspace. If supported correctly by software, the
>> colors should show up right on the screen.
> One use case of PDF is as a print medium, but it's not the only one. If
> we're talking about producing documents for offset printing, then yes, I
> agree with you. Fact is that most PDF-producing software packages I know
> produce RGB (either uncalibrated DeviceRGB or sRGB). This applies to
> OpenOffice, Acrobat Distiller with its default settings, GhostScript.
> The list probably goes on.
> Supporting CMYK in FOP means some additional work which I don't have
> time for (and don't really have a need myself). The client that has
> asked me to implement PDF/A-1 is happy with sRGB since it's only about
> patent documents. If someone (you?) implements an option to generate a
> full CMYK PDF, then I'm all for adding that since it has been requested
> a number of times. But doing that per default would be a change in
> long-standing standard FOP behaviour which I don't support.
>> 2) If you want to embedd the sRGB profile, I would recommend using the
>> profiles found at the International Color Consortium:
>> especially
>> unfortunately I was unable to find the exact licensing terms.
> That's exactly why I didn't use them. Licensing terms are not clear. On
> the other side, Adobe & Co. are distributing the sRGB profile from
>, not from It's also unclear to me which of the two
> variants (withBPC/noBPC) would have to be used.
>> just my 2 cts.
>> Max
>> Jeremias Maerki wrote:
>> > I'm near the end of my work for basic PDF/A-1b support. PDF/A-1b
>> > mandates the use of an OutputIntent if uncalibrated color spaces (like
>> > DeviceRGB) are used. That means that in each PDF which has PDF/A-1b
>> > enabled an ICC color profile will be embedded and used in the
>> > OutputIntent object. Since we don't support ICC-based colors, yet, I've
>> > hard-coded sRGB into PDF/A-1b support (XSL-FO supports sRGB and
>> > ICC colors, XSL 1.0, 5.9.9). But that means I need to embed the sRGB
>> > IEC61966-2.1 color profile. The JRE provides such a color profile but
>> > does this is a weird way: the profile alone is about 140KB. That's why
>> > I'd like to use the standard sRGB profile from HP. Info on that file:
>> > 
>> > Obtained from:
>> > 
>> > The file "sRGB Color Space Profile.icm" is:
>> > Copyright (c) 1998 Hewlett-Packard Company
>> > 
>> > To anyone who acknowledges that the file "sRGB Color Space Profile.icm" 
>> > permission to use, copy and distribute this file for any purpose is
>> hereby 
>> > granted without fee, provided that the file is not changed including
>> the HP 
>> > copyright notice tag, and that the name of Hewlett-Packard Company not
>> be 
>> > used in advertising or publicity pertaining to distribution of the
>> software 
>> > without specific, written prior permission.  Hewlett-Packard Company
>> makes 
>> > no representations about the suitability of this software for any
>> purpose.
>> > 
>> > I need to get the license approved by the VP legal affairs but I don't
>> > expect any problems.
>> > 
>> > Anyone against me including this color profile (3144 bytes,
>> uncompressed)
>> > in the org.apache.fop.pdf package?
>> > 
>> > Jeremias Maerki
> Jeremias Maerki

View this message in context:
Sent from the FOP - Dev mailing list archive at

Reply via email to