W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2020

[csswg-drafts] [css-color] Non-ICC color specifications (#5737)

From: Christoph Päper via GitHub <sysbot+gh@w3.org>
Date: Thu, 19 Nov 2020 19:26:20 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-746859767-1605813979-sysbot+gh@w3.org>
Crissov has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-color] Non-ICC color specifications ==
~~~~ ebnf
color() = color( [ 
    [<ident> | <dashed-ident>]? 
    [ <number-percentage>+ | <string> ] 
    [ / <alpha-value> ]? 
  ]# , <color>? )
~~~~

The  [`color()` function][color] as currently specified expects either a single color name or a sequence of numeric component values. This may well cover everything that is possible with [ICC profiles][color-profile], but it does not support systems which support multiple keywords to specify a single color, e.g. [CNS](https://en.wikipedia.org/wiki/Color_Naming_System) `very dark reddish orange`, or combine letters/words and numeric amounts, e.g. [NCS](https://en.wikipedia.org/wiki/Natural_Color_System) `S 2030-Y90R` ~ `20% 30% 10% yellow 90% red`. 

Should the syntax be relaxed a bit to support such systems in the future?

[color]: <https://drafts.csswg.org/css-color-4/#color-function> "Specifying profiled colors: the color() function" 
[color-profile]: <https://drafts.csswg.org/css-color-4/#at-profile> "Specifying a color profile: the @color-profile at-rule"

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5737 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 November 2020 19:26:22 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:22 UTC