<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#c7">Comment # 7</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:zolnaitamas2000@gmail.com" title="Tamás Zolnai <zolnaitamas2000@gmail.com>"> Tamás Zolnai</a> <pre>(In reply to Telesto from <a href="show_bug.cgi?id=125268#c5">comment #5</a>) > Looks like <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - FILESAVE Text highlighting changes from Yellow 10 to Yellow 2 after saving to DOC" href="show_bug.cgi?id=97865">bug 97865</a> see also <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - FILESAVE: docx file; multiple highlighted text colours have been saved in one colour." href="show_bug.cgi?id=107793">bug 107793</a> (and related <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Highlight Color Not Staying The Color I Choose." href="show_bug.cgi?id=116458">bug 116458</a> <a class="bz_bug_link bz_status_NEW " title="NEW - List incompatible features when saving to alien formats in detail (see c5)" href="show_bug.cgi?id=115291">bug 115291</a> > <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Highlight colors change" href="show_bug.cgi?id=113872">bug 113872</a>) > > @Buovjaga > Any advise on handling this re-occurring type of bug report. Keeps coming up > once in a while (and gets confirmed too) Ends in NOTABUG, WONTFIX, DUPLICATE > of something.. Feels a bit like suppressing the issue > > There is quite the 'surprise factor'. You save A and get B on reload. I > would even consider it calling DataLoss.. > > Current situation is quite terrible; IMHO. However no solution has come up > in the mean time (except better documentation). But I call that more a > 'excuse' type of argument. > > I personally prefer the 'old way' prior to LibO 5.0 by default (so using > text background). But technical/ terminological 'wrong' I guess. And the > number of complains are rather limited (or people stopped used LibreOffice > for this reason) > > --------------- > > Before the 5.0 version sometimes we saved Writer text background as shading > (doc, docx), sometimes as highlighting (rtf). From that version an option is > added, so the user can select the preferred behavior. Highlighting became > the default, because on LO UI text background is called highlighting. This > option can be set also via user profile. > <a href="https://wiki.documentfoundation.org/ReleaseNotes/5.0">https://wiki.documentfoundation.org/ReleaseNotes/5.0</a> Before the change, the complaint was that the user could not change the highlighting color in Word because it was not highlighting, but shading and it is actually more intuitive that this color is highlighting since LO calls it also that way. Before this change, user can't do anything with that, by now the user can change the settings and export text background as shading if he needs it to work on that way. About the data loss. That is true, but it's always a risk to save to an alien format that something is not exported as is. Even Word warns you when you save something in the older DOC format that you may lose something. It's the same in LO. Changing default value there and back also a bad idea, because after that those user will come to complain who are happy with the current default and then what will you do? So I would stick to this default behavior and when there is a complaint always mention the corresponding option. If there is a better solution to handle these two types of character background (e.g. shading and highlighting) patches are always welcome, but changing the default behavior does not actually improve the situation.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>