Gesendet: Montag, 27. Oktober 2014 um 01:37 Uhr Von: "Alexandre Prokoudine" <alexandre.prokoudine@...400...> An: Kein Empfänger Cc: "Inkscape Devel List" inkscape-devel@lists.sourceforge.net Betreff: Re: [Inkscape-devel] Inkscape in print workflows: Feedback from a conference in Switzerland
27 окт. 2014 г. 0:47 "the Adib" <theadib@...400...> :
this was the LGM 2012 :-O At this years LGM 2014 in Leipzig Chris Murphy a CMS expert was present. At the end of the event he was asking if anyone is interested in joining a workgroup to implement cms into the destop. So that any application can use it.
Excuse me, what does this mean? For the past few years any application has been able to use colord or simply read > _ICC_ATOM from X.org to color-correct display output (even Wayland has basic color management by now, to the best > of my knowledge). There's even that Oyranos thing. Is this about CMS in widgets? Or full-screen color management? > I'm puzzled. As for Cairo, it is my understanding from conversations with various developers that it's architecturally > > unsuitable for CMYK and spot colors capable output. Alex
This seems to be a misunderstanding. Inkscape already does CM, and, like GIMP, Krita or Scribus, does so very well, thanks to lcms. Thus, display CM is not an issue, but CM-based colour conversion for print files is. As I already wrote, at the conference in Switzerland, there was a Mac with GIMP, Photoshop, Scribus and InDesign available, and the monitor was one of the insanely expensive EIZO models used in many print workflows. There was *no* discernible or measurable difference in quality between Adobe's products and lcms-powered Open-Source programmes. The EIZO sales engineer -- who was very comptetent and friendly -- even scratched his head and wondered how this could be possible with a Free library. So this is not the issue. Moreover, the use of lcms helps with cross-platform compatibility.
I'm currently preparing a paper (PDF, c. 20 pages) based on feedback from several sources who are working in print workflows. It'll list and describe what users need to replace Illy *for print*. I will also suggest some potential short term and long term solutions. It may take a few weeks, as some testers need some time and will be able to provide feedback in November at the earliest. Some may also want to wait for the release of 0.91.
Please be patient :)
Kind regards,
Christoph