- From: Christoph Päper via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Dec 2016 19:42:04 +0000
- To: public-css-archive@w3.org
For
[RAL](http://www.ral-farben.de/content/application-help/all-ral-colours-names.html),
this would suggest `color(RAL /* … */)`.
The *RAL Design* sub-system is an alternative (HCL) notation of [LCH
colors](https://drafts.csswg.org/css-color/#specifying-lab-lch), as it
seems. So it probably makes no sense to introduce a separate syntax
for this, although it would be possible.
RAL <hhh> <ll> <cc> → lch(<ll> <cc> <hhh>deg)
color(RAL "000 15 00") … color(RAL "360 92 05")
color(RAL 0deg 15 00) … color(RAL 360deg 92 05)
The original *RAL Classic* sub-system would work with 4-digit
`<<number>>`, but it also has localized names:
color(RAL 1000) … color(RAL 9023)
color(RAL "1000") … color(RAL "9023")
color(RAL "green beige") … color(RAL "pearl dark grey")
color(RAL "Grünbeige") … color(RAL "Perldunkelgrau")
The *RAL Effect* sub-system is based on a 3-digit number and another
character (a digit or the letter `M`) , conventionally concatenated
with a hyphen `-`. There are several ways this could be mapped to
`color()`.
color(RAL "110-1") … color(RAL "870-M")
color(RAL 110 "1") … color(RAL 870 "M")
color(RAL 110 1) … color(RAL 870 M)
color(RAL-1 110) … color(RAL-M 870)
Similarly, *RAL Plastics*, is just Classic or Design with an added
`-P`. This may constitute a reason for not using `lch()` for Design.
color(RAL "1000-P") … color(RAL "9016-P")
color(RAL-P 1000) … color(RAL-P 9016)
color(RAL "000 15 00-P") … color(RAL "360 70 15-P")
color(RAL-P 0deg 15 00) … color(RAL-P 360deg 70 15)
--
GitHub Notification of comment by Crissov
Please view or discuss this issue at
https://github.com/w3c/csswg-drafts/issues/817#issuecomment-269373162
using your GitHub account
Received on Tuesday, 27 December 2016 19:42:10 UTC