Bug 112079 - Palettes: CamelCase color names in the html palette
Summary: Palettes: CamelCase color names in the html palette
Status: RESOLVED DUPLICATE of bug 104048
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
6.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Color-Palettes
  Show dependency treegraph
 
Reported: 2017-08-29 07:43 UTC by Gabor Kelemen (allotropia)
Modified: 2017-08-29 13:16 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gabor Kelemen (allotropia) 2017-08-29 07:43:53 UTC
The html palette contains CamelCased color names, like MintCream, AliceBlue or GhostWhite: 
https://cgit.freedesktop.org/libreoffice/core/tree/extras/source/palettes/html.soc 

As far as I see, these names are not saved to html/ODF/OOXML files as strings, only the hex codes of the color are used. So these names seem to serve only as an identifier to the user.

I'd like to ask to change these to proper English: Mint Cream, Alice Blue or Ghost White seem easier to read to me.
Comment 1 Regina Henschel 2017-08-29 07:52:03 UTC
I do not support this request. The names in the HTML-palette are designed to meet the official HTML color names. https://www.w3schools.com/colors/colors_names.asp
Comment 2 Heiko Tietze 2017-08-29 08:20:27 UTC
HTML is defined as this, see also bug 104048

*** This bug has been marked as a duplicate of bug 104048 ***
Comment 3 Gabor Kelemen (allotropia) 2017-08-29 12:30:17 UTC
(In reply to Regina Henschel from comment #1)
> I do not support this request. The names in the HTML-palette are designed to
> meet the official HTML color names.
> https://www.w3schools.com/colors/colors_names.asp

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.
Comment 4 Regina Henschel 2017-08-29 12:53:22 UTC
I personally would not translate them, but it is a decision of the local team.
Comment 5 V Stuart Foote 2017-08-29 13:16:09 UTC
(In reply to Gabor Kelemen from comment #3)
> (In reply to Regina Henschel from comment #1)
> > I do not support this request. The names in the HTML-palette are designed to
> > meet the official HTML color names.
> > https://www.w3schools.com/colors/colors_names.asp
> 
> 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.

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-=
https://www.w3.org/TR/SVG/types.html#ColorKeywords
https://www.w3.org/TR/css3-color/#svg-color