Date: prev next · Thread: first prev next last
December 2017 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=104048

V Stuart Foote <vstuart.foote@utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gautier.sophie@gmail.com,
                   |                            |vstuart.foote@utsa.edu

--- Comment #7 from V Stuart Foote <vstuart.foote@utsa.edu> ---

Gabor had prepared https://gerrit.libreoffice.org/42516 to support Pootle
translation of the HTML/CSS and SVG colors, I think that should be abandoned.

Our html palette should not be translated.


=-ref-=

Regards translating the HTML/CSS and SVG color name keywords, taken from the
dupe bug 112079 asking about the CamelCase naming:

Gabor:
...
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.

Stuart:
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.

https://www.w3.org/TR/SVG/types.html#ColorKeywords
https://www.w3.org/TR/css3-color/#svg-color

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.