Bug 125268 - Wrong text highlight color when export document to doc/docx
Summary: Wrong text highlight color when export document to doc/docx
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
: 126264 (view as bug list)
Depends on:
Blocks: DOCX
  Show dependency treegraph
 
Reported: 2019-05-13 17:06 UTC by Clemens Eisserer
Modified: 2019-07-07 14:01 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Attachments
sample document (source) (16.65 KB, application/vnd.oasis.opendocument.text)
2019-05-13 17:06 UTC, Clemens Eisserer
Details
document saved as Word97 file (11.50 KB, application/msword)
2019-05-13 17:06 UTC, Clemens Eisserer
Details
the document saved to docx format (5.62 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-05-13 17:09 UTC, Clemens Eisserer
Details
screenshot comparing the ODT (top) source to the resulting docx file (bottom) (89.35 KB, image/png)
2019-05-13 17:10 UTC, Clemens Eisserer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Clemens Eisserer 2019-05-13 17:06:04 UTC
Created attachment 151370 [details]
sample document (source)

When saving the attached document containing colored text to Doc (word97-2003) or docx (Word2007+)-format, the colored text is broken.

When loading the resulting file, LibreOffice as well as Word2016 show constent results.
Comment 1 Clemens Eisserer 2019-05-13 17:06:35 UTC
Created attachment 151371 [details]
document saved as Word97 file
Comment 2 Clemens Eisserer 2019-05-13 17:09:48 UTC
Created attachment 151372 [details]
the document saved to docx format
Comment 3 Clemens Eisserer 2019-05-13 17:10:37 UTC
Created attachment 151373 [details]
screenshot comparing the ODT (top) source to the resulting docx file (bottom)
Comment 4 Roman Kuznetsov 2019-05-14 05:55:40 UTC
confirm in

Version: 6.3.0.0.alpha0+
Build ID: 773ac3abbf8ab1343367e51b1774d2ee1f8c4f49
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded
Comment 5 Telesto 2019-05-14 09:45:32 UTC
Looks like bug 97865 see also bug 107793 (and related bug 116458 bug 115291 bug 113872)

@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.
https://wiki.documentfoundation.org/ReleaseNotes/5.0
Comment 6 Buovjaga 2019-05-14 09:56:33 UTC
(In reply to Telesto from comment #5)
> Looks like bug 97865 see also bug 107793 (and related bug 116458 bug 115291
> bug 113872)
> 
> @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.
> https://wiki.documentfoundation.org/ReleaseNotes/5.0

I don't think I am the right person to ask, so pinging Tamás.
Comment 7 Tamás Zolnai 2019-05-14 10:24:22 UTC
(In reply to Telesto from comment #5)
> Looks like bug 97865 see also bug 107793 (and related bug 116458 bug 115291
> bug 113872)
> 
> @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.
> https://wiki.documentfoundation.org/ReleaseNotes/5.0

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.
Comment 8 Buovjaga 2019-05-14 10:33:55 UTC

*** This bug has been marked as a duplicate of bug 97865 ***
Comment 9 Tamás Zolnai 2019-05-14 10:35:48 UTC
> > 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.
Comment 10 Tamás Zolnai 2019-05-14 10:40:17 UTC
> 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 [...]


15 colors actually.
Comment 11 Gabor Kelemen 2019-05-30 09:31:48 UTC
(In reply to Tamás Zolnai from comment #9)
> > > 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 :) )
Comment 12 Tamás Zolnai 2019-05-30 09:56:27 UTC
> 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?

It's a great idea.
Comment 13 Telesto 2019-07-07 13:50:10 UTC
*** Bug 126264 has been marked as a duplicate of this bug. ***