We've discussed this before... There are only 16 color names defined in the HTML spec (see http://www.w3.org/TR/html4/types.html#h-6.5) and the Plucker distiller supports all of those. Here's the text from the HTML spec:
"A color value may either be a hexadecimal number (prefixed by a hash mark) or one of the following sixteen color names." If it's not one of those 16 names, it's an HTML error. There are other sets of color names floating around the web, many based on the X Window System's old "rgb.txt" file, and they may or may not work properly in a viewer. No HTML renderer is obliged to support any of them, and their use in HTML should be discouraged. The right thing to do in the distiller is to raise an error if one of them is encountered, but I could see perhaps simply ignoring it. OK, having gotten the principled view out there... I could add an option to the distiller that would load a user-provided set of colornames. Something along the lines of an option in your .pluckerrc (or the site-wide one) that would give a filename, which in turn would contain a number of colorname/colorspec pairs. Bill
