<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Remove color palettes Breeze, Tango and LibreOffice" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113858#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Remove color palettes Breeze, Tango and LibreOffice" href="https://bugs.documentfoundation.org/show_bug.cgi?id=113858">bug 113858</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>Only concerns I have would be impact on existing templates and existing documents anywhere the colors are named and it makes it into the ODF. I've not checked but in generating templates and area fill gradients do we pick colors by palette name, or are they always by HEX sRGB value? Also, we had to be careful with handling localization of html palette because both HTML/CSS and SVG use the X11 color names as keywords. Looking at standard.sog we refer to Tango in the gradient names, but colors receive a specific HEX value. And, the unit test for ODF export make use of the gradient names containing Tango. So dropping the "branding" palettes (Tango, Breeze, and LibreOffice) is probably fine, but we do need to check other corners of the UI. =-ref-= <a href="https://opengrok.libreoffice.org/xref/core/extras/source/palettes/standard.sog">https://opengrok.libreoffice.org/xref/core/extras/source/palettes/standard.sog</a> <a href="https://opengrok.libreoffice.org/xref/core/sw/qa/extras/odfexport/odfexport.cxx">https://opengrok.libreoffice.org/xref/core/sw/qa/extras/odfexport/odfexport.cxx</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>