I think there is some pseudo-standard in the FO world to specify CMYK colors: http://www.xslfo.info/examples/colors_1.htm shows that. The "pseudo" part is that I think "#CMYK" is a convention, not an actual ICC Color Profile. I'm not sure, though.
So it would be better to properly implement the rgb-icc() function and to extend FOP's color support which BTW can't be extended using an extension function. FOP is completely focused on sRGB at the moment. Every now and then CMYK comes up as a topic. I'd wish someone would finally sit down and do the necessary changes. It can't be that difficult if you know a little bit about color management. The infrastructure is there, it just needs to be extended to accomodate non-sRGB colors. But it's not a one-hour job. The changes will go through the whole codebase. If the latter is not an option, there are several tools on the net that allow conversion of PDFs from RGB to CMYK. On 11.01.2006 22:47:46 Andreas L Delmelle wrote: > On Jan 11, 2006, at 14:38, Pierre-Yves Landuré wrote: > > > Ok, thanx for your reply. > > > > Now, given that i know : > > > > wanted CMYK. > > used RGB. > > > > and that color is only use by text elements. > > > > Is there a way to "manualy" convert pdf colorspace ? By manualy, i > > mean writing a script that find elements having for color a given > > RGB value, and that translate them to CMYK. > > Not that I know of immediately... but it might be a nice idea, if > possible and anyone is willing to invest time in it, to add an > extension function, fox:cmyk() > Come to think of it, I don't really know how easy extension functions > would be to implement...? Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
