<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Ross Moore wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:04C36082-8326-427D-8B4A-8DF13BDD99A0@mq.edu.au">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<blockquote type="cite">No, the fourth couplet is TT, where T is
"Transparency". Unfortunately , it is a misnomer, since 00 =
completely transparent and FE is almost opaque, which is why I
spoke of "opacity" rather than transparency. Unfortunately FF
is
<i class="">not</i> opaque when preceded by FFFFFF, because the
driver treats FFFFFF [FF] specially.</blockquote>
<br class="">
<div>
<div>As I said, it didn’t make sense to me. :-)</div>
<div>Thanks for the clarification, and sorry for my added noise.</div>
</div>
</blockquote>
<br>
Not your fault, Ross : the problem originated, I believe, with the
choice of "transparency" to refer to the fourth couplet rather than
"opacity".<br>
<br>
<blockquote type="cite"
cite="mid:04C36082-8326-427D-8B4A-8DF13BDD99A0@mq.edu.au">
<div>
<div>It looks as if Akira has done what you wanted, so the
exercise was a success. :-)<br>
</div>
</div>
</blockquote>
<br>
Indeed. I personally regard this as a great step forward, so many
thanks to Akira-san. Now what I would <i>really</i> like is the
ability to specify font colours in CMYK, so that whereas at the
moment one can write only :<br>
<ul>
<li>\font \thisfont = "Calibri:color=RRGGBB[TT]"</li>
</ul>
<p>one would be able, in an ideal world, to write in addition :<br>
</p>
<ul>
<li>\font \thisfont = "Calibri:color=rgb (RRGGBB)"</li>
<li>\font \thisfont = "Calibri:color=rgbo (RRGGBBOO)"</li>
<li>\font \thisfont = "Calibri:color=cmyk (CCMMYYKK)"</li>
</ul>
<p>or their decimal equivalents :<br>
</p>
<ul>
<li>\font \thisfont = "Calibri:color=rgb01 (r.r, g.g, b.b)"</li>
<li>\font \thisfont = "Calibri:color=rgbo01 (r.r, g.g, b.b, o.o)"</li>
<li>\font \thisfont = "Calibri:color=cmyk01 (c.c, m.m, y.y, k.k)"</li>
</ul>
<p>or the 0–255 version :<br>
</p>
<ul>
<li>\font \thisfont = "Calibri:color=rgb255 (r, g, b)"</li>
<li>\font \thisfont = "Calibri:color=rgbo255 (r, g, b, o)"</li>
<li>\font \thisfont = "Calibri:color=cmyk255 (c, m, y, k)"</li>
</ul>
<p>There could even be shorthands :<br>
</p>
<ul>
<li>\font \thisfont = "Calibri:color=#RRGGBB" <br>
</li>
<li>\font \thisfont = "Calibri:color=#RRGGBBOO" <br>
</li>
<li>\font \thisfont = "Calibri:color=$CCMMYYKK" <br>
</li>
</ul>
<p>But that would require changes not only to [x]dvipdfm[x] but (and
more importantly) to XeTeX itself, and I do not know whether XeTeX
is still being developed.<br>
</p>
<p>** Phil.</p>
</body>
</html>