<div>Ann, </div><div><br></div><div> I would really, really, like the color settings problem to be addressed by the ICC, with procedure guidelines as to what an inkjet printer should support, as to how it can be ensured that the print system can be used for profiling, how it can be ensured that the profile matches with the printer queue/ media employed. </div> <div><br></div><div>But the total mess that is inkjet printing on the platforms supported by the ICC shows no sign of abating, I see a minor member of the ICC (Xrite) having its clients unable to profile, when they buy the tool in order to, another minor member (Adobe) plagued by printing bugs from version to version of its least selling product, another hardware vendor (Epson) distributing free mini-RIPS in the hope that users will be able to print by bypassing the print system of the base OS. </div> <div><br></div><div> All we seem to be discussing here is the minor issue of the format for settings; well let me turn this round: If XML, Json or whatever is employed, I am sure we can embed the whole mess in a profile, or embed the profile in the settings or whatever, and make the system work regardless of syntax. </div> <div><br></div><div> It would help if you chose to sit down *here* and made helpful suggestions to us chickens about how to design a system that works, as all the talking over there sure ain't produced results.</div><div> <br></div><div>Edmund</div><div><br><div class="gmail_quote">On Fri, Jan 21, 2011 at 6:37 PM, Ann L McCarthy <span dir="ltr"><<a href="mailto:almccart@lexmark.com">almccart@lexmark.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <br><font size="2" face="sans-serif">Please be aware that SampleICC already includes an XML <=> ICC format capability.</font> <br><font size="2" face="sans-serif">Any tags in an ICC profile can be edited in an XML editor using that capability for pre- and post- conversion.</font> <br><font size="2" face="sans-serif">This obtains the XML text editing experience and at the same time retains the efficient storage format of the ICC profile.</font> <br> <br><font size="2" face="sans-serif">Best regards,<br> Ann McCarthy<br> Imaging Systems R&D<br> Lexmark International, Inc.<br> <br> <br> </font> <br> <br> <br> <p></p><table width="100%"> <tbody><tr valign="top"> <td width="40%"><div class="im"><font size="1" face="sans-serif"><b>"Alastair M. Robinson" <<a href="mailto:blackfive@fakenhamweb.co.uk" target="_blank">blackfive@fakenhamweb.co.uk</a>></b> </font> <br></div><font size="1" face="sans-serif">Sent by: openicc-bounces+almccart=<a href="http://lexmark.com" target="_blank">lexmark.com</a>@<a href="http://lists.freedesktop.org" target="_blank">lists.freedesktop.org</a></font> <p><font size="1" face="sans-serif">01/20/2011 09:24 PM</font> </p></td><td width="59%"> <table width="100%"> <tbody><tr valign="top"> <td> <div align="right"><font size="1" face="sans-serif">To</font></div> </td><td><font size="1" face="sans-serif">edmund ronald <<a href="mailto:edmundronald@gmail.com" target="_blank">edmundronald@gmail.com</a>></font> </td></tr><tr valign="top"> <td> <div align="right"><font size="1" face="sans-serif">cc</font></div> </td><td><font size="1" face="sans-serif">OpenICC Liste <<a href="mailto:openicc@lists.freedesktop.org" target="_blank">openicc@lists.freedesktop.org</a>></font> </td></tr><tr valign="top"> <td> <div align="right"><font size="1" face="sans-serif">Subject</font></div> </td><td><font size="1" face="sans-serif">Re: [Openicc] meta data in test chart</font></td></tr></tbody></table> <br> <table> <tbody><tr valign="top"> <td> </td><td></td></tr></tbody></table> <br></td></tr></tbody></table> <br> <br> <br><tt><font size="2"><div><div></div><div class="h5">Hi,<br> <br> On 21/01/11 01:07, edmund ronald wrote:<br> <br> > I think we need to choose between XML and JSON. Robert will have final<br> > say, I guess, but we might as well have it out there.<br> <br> I'm with Graeme in thinking XML is a horrible format to edit by hand <br> (because the tags and the <> delimiters all have the same visual <br> "weight" as the data within, so to my eyes it all just congeals into a <br> mass on screen.) However, despite my dislike of it, I think XML might <br> be the better fit in this case.<br> <br> What needs to be able to parse the serialised options, and what can just <br> treat it as a "blob"?<br> <br> * Gutenprint: Obviously needs to be able to both parse and write.<br> <br> * Oyranos, colord, etc.: Do they need to parse, or is a test for <br> "equality" (for some yet-to-be-determined definition of "equality") <br> sufficient?<br> <br> * ArgyllCMS: I would think profiling tools in general would need no <br> awareness of the contents and would treat the data as a blob to be <br> embedded in the final profile?<br> <br> > One argument in favor of JSON is that we can expect to write GUI's to<br> > manipulate settings for the user so JSON is a good fit.<br> <br> From my experience using the Gutenprint options system from within <br> PhotoPrint I'd say the options' limits and their interactions with each <br> other are *way* too complicated to be encoded within a serialised <br> options file, so a GUI tool to edit such a set of options would probably <br> need to be linked with libgutenprint. Such a tool (at least a <br> Gutenprint-specific tool) would be far better off deserialising an <br> options file into a live stp_vars_t, editing that, then serialising it <br> again than attempting to parse a file itself and implementing its own <br> internal model with option constraints. Gutenprint already has an XML <br> library, so I don't see much sense in making Gutenprint use a different <br> parsing library just for option serialisation.<br> <br> All the best<br> --<br> Alastair M. Robinson<br></div></div><div class="im"> _______________________________________________<br> openicc mailing list<br> <a href="mailto:openicc@lists.freedesktop.org" target="_blank">openicc@lists.freedesktop.org</a><br> </div></font></tt><div><div></div><div class="h5"><a href="http://lists.freedesktop.org/mailman/listinfo/openicc" target="_blank"><tt><font size="2">http://lists.freedesktop.org/mailman/listinfo/openicc<br> </font></tt></a> <br></div></div></blockquote></div><br></div>