<br><font size=2 face="sans-serif">One purpose of the ICC metadataTag is
to enable automated profile selection, so perhaps </font>
<br><font size=2 face="sans-serif">the metadataTag can help in this case.</font>
<br>
<br><font size=2 face="sans-serif">Perhaps </font><tt><font size=2>the
ArgyllCMS command-line utilities will be updated to use </font></tt>
<br><tt><font size=2>the new metadataTag?</font></tt>
<br>
<br><font size=2 face="sans-serif">Best regards,<br>
Ann McCarthy<br>
Imaging Systems R&D<br>
Lexmark Imaging Solutions Division<br>
Lexmark International, Inc.<br>
<br>
<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Alastair M. Robinson"
<blackfive@fakenhamweb.co.uk></b> </font>
<br><font size=1 face="sans-serif">Sent by: openicc-bounces@lists.freedesktop.org</font>
<p><font size=1 face="sans-serif">04/05/2010 12:09 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">OpenICC Liste <openicc@lists.freedesktop.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [Openicc] Devicelink profiles and
accompanying metadata</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Hi :)<br>
<br>
Kai-Uwe Behrmann wrote:<br>
<br>
> They would become visible in the general ICC profile path.<br>
> How does you think software can select these profiles? What shall
the UI<br>
> show to the user or how can the selection happen automatic?<br>
<br>
Well these issues are the reason for my question - I wanted to know<br>
whether anyone else had given it any thought, and whether there was any<br>
consensus on the right way to handle devicelinks, before putting too<br>
much time into it myself.<br>
<br>
I can only speak for my own software, but currently I display a<br>
Descriptive name for a profile if possible, and the filename if not.<br>
The ProfileSelector widget used in PhotoPrint, CMYKTool, etc., has a<br>
flag which the application can use to choose whether or not devicelinks<br>
will be included in the list of profiles.<br>
<br>
I don't know how good or otherwise the support for Devicelinks is in<br>
other software, or how much havoc their appearance in standard search<br>
paths would cause - would it be better to create a new directory for<br>
these (say, XDG_DATA_HOME/color/devicelink or<br>
XDG_DATA_HOME/color/icc_devicelink) or just cache them privately?<br>
<br>
> Consider the 'psid' tag?<br>
<br>
The profiles I intend to create will be created using the ArgyllCMS<br>
command-line utilities - so I guess I'd need to write some kind of<br>
"injector" utility to add such a tag after the profile's created
(unless<br>
there's some utility already out there that I don't know about yet?).<br>
Other than that, it sounds like an ideal solution.<br>
<br>
Thanks for the response :)<br>
<br>
All the best<br>
--<br>
Alastair M. Robinson<br>
_______________________________________________<br>
openicc mailing list<br>
openicc@lists.freedesktop.org<br>
</font></tt><a href=http://lists.freedesktop.org/mailman/listinfo/openicc><tt><font size=2>http://lists.freedesktop.org/mailman/listinfo/openicc<br>
</font></tt></a>
<br>