On Sun, 31 Mar 2013 08:50:20 +0200 (CEST) "Christoph Sch?fer" <christoph-schaefer at gmx.de> wrote:
> Hi all, > > I have brought on board another commercial colour vendor, this time > one from North America. At the moment, we are feverishly working on > all sorts of issues, including documentation, colour correctness, > logo exchange, licensing etc. > > You could help to speed up the process by writing a shell or Python > script. > > I receive all palettes as EPS files, which are easy to convert to > Scribus's own XML palette format. However, since the colours aren't > stored as spot colours, they end up being imported as something like > "FromPDF#00000040", which is completely useless when referring to a > printed colour swatch that is based on CMYK ink mixtures. > > In a Scribus XML palette file, the converted colour entry looks like > this: > > <COLOR NAME="FromPDF#00404040" CMYK="#00404040"/> > > What is needed is a script that strips the string FromPDF and > converts the hex value in a specific way (adding ink channel > abbreviations and slashes), so that the end result looks like this: > > <COLOR NAME="C25/M25/Y25/K25" CMYK="#40404040"/> > > Anyone willing to step in? Hi, A bit like Frank, I am not sure how you went from #00404040 to #40404040 Did you intend to include the eps file in the source? or just the xml? -- Owen
