<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Wrong text highlight color when export document to doc/docx" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125268#c31">Comment # 31</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - 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:glogow@fbihome.de" title="Jan-Marek Glogowski <glogow@fbihome.de>"> Jan-Marek Glogowski</a> <pre>As mentioned on IRC, I don't have a solution. I'll just use the log as an infodump. [14:51] <jmux> buovjaga: the change is just in 7.0, so plenty of time to agree on some "final" solution. Probably start with a revert, so LO won't accidently release the current state. [14:52] <buovjaga> sure [14:52] <jmux> And I agree with buovjaga that this is a primary a usability, not a coding problem. [14:56] <jmux> What I seem to understand is: character background handling is different between ODF and DOCX. I don't know, why DOCX has shading and highlight. [14:57] <lo-dsgn-tg> <Kompilainenn> History [14:58] <jmux> I don't think it's a good idea to open a DOCX and allow the user to make changes, which aren't representable in the format. [14:59] <jmux> As we already see, this results in frustration. Since the user doesn't know about this limits, no blame on him. [15:01] <jmux> So I guess the idea about the MS color palette is not the worst to start with. [15:03] <jmux> It obviously breaks, if the import document now actually uses shading colors, as LO at this point can't know, if the color was highlight or shading to begin with. [15:05] <jmux> IMHO the UX team should provide a suggestion to handle these constraints in their preferred way given the restrictions. [15:05] <jmux> And then we can discuss, if an implementation is feasible. [15:08] <jmux> And from my current POV, it doesn't look that there will be any perfect solution. Also when the term highlight is already used different in DOCX and ODF. [15:11] <jmux> Maybe for DOCX documents there should be explicitly two ways to set the background: highlight and shading, so the user can be aware of the difference? [15:16] <jmux> Or have a color picker with two areas, one depicting the 15 highlight colors and one for the shading? [15:17] <jmux> BTW: what happens, if the user sets highlight and shading? Is that possible? [15:36] <lo-dsgn-tg> <Kompilainenn> We already have two variants for saving highlights/shading for docx documnets [15:36] <lo-dsgn-tg> <Kompilainenn> You'll find option in Tools-Options dialog [15:42] <jmux> Kompilainenn: I'm aware of the compatibility settings. But I don't think this is the most agreeable solution from the UX POV. [15:43] <lo-dsgn-tg> <Kompilainenn> Why not? It worked many years [15:44] <lo-dsgn-tg> <Kompilainenn> If UX-team will suggest a better solution it would be good... [15:46] <lo-dsgn-tg> <Kompilainenn> But I don't think it's an UX problem [15:46] <lo-dsgn-tg> <Kompilainenn> In general [15:48] <jmux> Maybe. I don't know if this is a common problem or not. I read the bug as that it is, but really don't have a way to evaluate the claims. [15:50] <jmux> If "we" decide the compatibility flags is still good, fair enough. Less work to be done.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>