- From: James Aylett <sja20@hermes.cam.ac.uk>
- Date: Tue, 12 Nov 1996 13:27:27 +0000 (GMT)
- To: S.N.Brodie@ecs.soton.ac.uk
- cc: www-html@w3.org
On Tue, 12 Nov 1996 S.N.Brodie@ecs.soton.ac.uk wrote: > James Aylett wrote: > > > > RffGffBff - RGB values in hex > > R100%G100%B100% - RGB values in percentages (just to please the few ...) > > I think rather than R100%G100%B100% it would be better to have: > > RGB:50%,0%,50% > CYMK:0%,100%,0%,50% That's true; I was making the point that different colour models should be supported rather than advocating a particular syntax. > Alternatively, how about introducing a <colour> tag for defining local > colour names. [model snipped] > This gets around the problem of the browser not knowing the meaning of a > new colour format, since it can be embedded in the document itself. It > also means that document authors can define a colour setting once and then > refer to it by name throughout the document, although it would probably be > less useful in the presence of stylesheets. What exactly would you mean the COLOUR (a/or COLOR) element to do? Define a name which can then be used by BGCOLOR etc.? > Colour handling is something which I think should be controllable outside > the browser application if necessary. For example, people with monochrome > displays might have special files which change the mappings of the textual > names to different RGB values for a better display on their system. This is also true; with distinct colour models however this would (although possible) become tricky to do intuitively for most people. Probably the best possible would be to convert from the model to RGB and then filter that through the user's preferences. James -- /-----------------------------------------------------------------------------\ James Aylett - Crystal Services (crystal.clare.cam.ac.uk): BBS, Ftp and Web Clare College, Cambridge, CB2 1TL -- sja20@cam.ac.uk -- (0976) 212023
Received on Tuesday, 12 November 1996 08:27:40 UTC