<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Palettes: CamelCase color names in the html palette"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=112079#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Palettes: CamelCase color names in the html palette"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=112079">bug 112079</a>
from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
<pre>(In reply to Gabor Kelemen from <a href="show_bug.cgi?id=112079#c3">comment #3</a>)
<span class="quote">> (In reply to Regina Henschel from <a href="show_bug.cgi?id=112079#c1">comment #1</a>)
> > I do not support this request. The names in the HTML-palette are designed to
> > meet the official HTML color names.
> > <a href="https://www.w3schools.com/colors/colors_names.asp">https://www.w3schools.com/colors/colors_names.asp</a>
>
> Well, this is a choice too.
> But does this also mean that we should not translate them either? That would
> cause quite a bit of divergence from that list as well in case of a
> translated UI.</span >
Both SVG and CSS use these as 'keywords', capitalization does not matter--so
camelCase is fine. But the names as 'keywords' should probably be left intact
and _not_ translated to be standards compliant with our filter handling to
assure the correct sRGB hex gets assigned when keyword is parsed.
=-ref-=
<a href="https://www.w3.org/TR/SVG/types.html#ColorKeywords">https://www.w3.org/TR/SVG/types.html#ColorKeywords</a>
<a href="https://www.w3.org/TR/css3-color/#svg-color">https://www.w3.org/TR/css3-color/#svg-color</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>