To paraphrase from Vchapter 7 of Xlib programming (page 193) it says
Whe XAllocNamedColor, XlookupColor, XparseColor and XStoreNamedColor (or their
device indepent analogues) and pased a colour string thyey attempt the
following thins (and take the first that works)
1. Attempt to parse is as a new-style declaration in one of the suppoered
colour spaces (RGB, RGBi, CIEXYZ, CIEuvY, CIELab, CIELuv and TekHVC)
2. Look for the colour in the client side deivce independetn colour database
(Xcms.txt)
3. Attempt to parse it as an old style colour (#hhhhhh or the servers's
rgb.txt)
If h is a hex digit and Lars writes
#hhhhhh then 1 and 2 fail, and 3 suceeds.
Examples of the nwe X11R5 and greater format are
RGB:00/00/ff
RGBi:1.0/0.6/0.3
CIEXYZ:0.06711/0.0337/0.3130
CIELab:0.0/0.0/0.0
CIELuv: 50.0/0.0/0.0
TekHVC:0.0/100.0/0.0
So Lars is right when he guess's it is an X11 feature, but he was probably not
aware of the range of formats supported. Actually not supporting any of the
formats would require special effort. (The colour space names are case
insensitive). CIE* and TekHVC are supposedly device independent (modulo the
display's device gamut).
--
Duncan (-:
"software industry, the: unique industry where selling substandard goods is
legal and you can charge extra for fixing the problems."
