<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Wrong text highlight color when export document to doc/docx" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125268#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Wrong text highlight color when export document to doc/docx" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125268">bug 125268</a> from <a class="email" href="mailto:kelemeng@ubuntu.com" title="Gabor Kelemen <kelemeng@ubuntu.com>"> Gabor Kelemen</a> <pre>(In reply to Tamás Zolnai from <a href="show_bug.cgi?id=125268#c9">comment #9</a>) > > > There is quite the 'surprise factor'. You save A and get B on reload. I > > > would even consider it calling DataLoss.. > > > About the surprise factor, when the user is surprised that they get a > different color, it may worth to point out that MSO supports only 16 colors > for text highlighting. After the user gets to know what they are trying to > use, I guess they can choose whether to use these 16 colors or switch to > using shading. Using shading still has the disadvantage that another user > might not able to remove the colored background because he / she expects it > is highlighting. How about introducing a 15-color character-highlight-compatibility palette and an Options - Writer - Compatibility config option to enable that and only that palette in the Character - Highlight tab; Color button? Surely a lot of work, but one less "surprise" for users. (see also my talk at this years FOSDEM :) )</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>