Bug 115291 - Text highlight color changes when .odt document saved as a .doc(x) document.
Summary: Text highlight color changes when .odt document saved as a .doc(x) document.
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.4.3.2 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 116458 (view as bug list)
Depends on:
Blocks: DOCX-Character DOC-Character
  Show dependency treegraph
 
Reported: 2018-01-29 06:08 UTC by Mark
Modified: 2018-04-11 08:44 UTC (History)
8 users (show)

See Also:
Crash report or crash signature:


Attachments
Example of .odt text highlight color change when saved as .doc file (25.50 KB, application/msword)
2018-01-29 06:08 UTC, Mark
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark 2018-01-29 06:08:00 UTC
Created attachment 139421 [details]
Example of .odt text highlight color change when saved as .doc file

Text segments, not necessarily a full paragraph, but it could be, open with a totally different background color after the original document (in .odt format) was saved as a Word 97-2003 (.doc) document. In my case, I used color "Blue gray" for the initial highlight color. When I opened the new document, the background color came up as "Blue 3". To do the formatting, I used the "Highlight Color" toolbar button to set the background color of the first segment, then the "Clone Formatting" button to "paint" additional text with the selected color. I saved the document to the Word 97 format. When opened, the new Word 97 document had a different color (Blue 3) for all highlighted segments.


Version: 5.4.3.2 (x64)
Build ID: 92a7159f7e4af62137622921e809f8546db437e5
CPU threads: 4; OS: Windows 6.19; UI render: default; 
Locale: en-US (en_US); Calc: group


Windows 10 Pro
Version 1709
OS Build 16299.192
Comment 1 Dieter Praas 2018-01-29 08:40:46 UTC
I confirm it with

Version: 6.1.0.0.alpha0+ (x64)
Build ID: 77a535285f0fd5f2464430abdc67cf99be024868
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-01-23_23:04:23
Locale: de-DE (de_DE); Calc: CL

1. I used highlight color Light Blue 4 (from standard palette)
2. Saved as .doc
3. Reopened document. Highlight color was blue (#0000FF)
Comment 2 Telesto 2018-01-29 19:10:47 UTC
Quote from: https://bugs.documentfoundation.org/show_bug.cgi?id=97865#c9

This thing happens because MS highlighting has only 15 highlighting color and when you save Writer text background \ highlighting to an MS format it is converted to this color palette.
It's the default behavior, but you can change this at Tools -> Option -> Load/Save -> Microsoft Office, to save Writer text background as MS Shading and so colors won't change. Nut in this case when you open that *.doc file in MS Word you could not change the text background with highlighting tool, but with the shading tool:
https://blogs.technet.microsoft.com/hub/2011/04/05/how-to-select-more-highlight-colors-in-word/

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

So, probably not a bug..
Comment 3 Telesto 2018-01-30 08:49:56 UTC
Has UX any opinion on this? The type of issue has been reported multiple times...  all of them where closed with the explanation given in comment 2. (see bug 96016, bug 97865, bug 113872) However it doesn't feel right...

It's might be better to switch the setting the other way around -> saving the highlighting as MS Shading. 

Pro
* It would prevent unexpected dataloss (in the sense of losing highlighting)
* it's compatible with MS Word (viewing)
* People aware of the risk of switching to MS highlighting mode (mouse over text?)

Contra
*It will break the experience of MS Word users wanting to edit a file..
Comment 4 Heiko Tietze 2018-01-30 09:22:32 UTC
Switching to the save mode makes sense. Guess most users don't know the difference.

Alternatively, we could ask the user when exporting a document may result in corrupt properties.
Comment 5 Yousuf Philips (jay) (retired) 2018-01-31 00:59:28 UTC
Microsoft only allows 15 colors to be used as highlight colors in both .doc and .docx, so this is a format limitation bug that isnt ours.

(In reply to Telesto from comment #3)
> Contra
> *It will break the experience of MS Word users wanting to edit a file..

Users being able to modify the highlighting is the most important thing, so i'd stick with this by default.

(In reply to Heiko Tietze from comment #4)
> Alternatively, we could ask the user when exporting a document may result in
> corrupt properties.

We already give users the 'Confirm File Format' dialog when not saving to ODF, which does state 'This document may contain formatting or content that cannot be saved in the currently selected file format'. We could go beyond this, if devs are interested in implementing it, and create a dialog similar to the MS compatibility checker.

http://technastic.com/wp-content/uploads/2016/02/Microsoft-Word-Compatibility-checker.jpg
Comment 6 Thomas Lendo 2018-02-20 21:18:23 UTC
(In reply to Yousuf Philips (jay) (retired) from comment #5)
> (In reply to Heiko Tietze from comment #4)
> > Alternatively, we could ask the user when exporting a document may result in
> > corrupt properties.
> We already give users the 'Confirm File Format' dialog when not saving to
> ODF, which does state 'This document may contain formatting or content that
> cannot be saved in the currently selected file format'. We could go beyond
> this, if devs are interested in implementing it, and create a dialog similar
> to the MS compatibility checker.
> 
> http://technastic.com/wp-content/uploads/2016/02/Microsoft-Word-
> Compatibility-checker.jpg
This would be really genius to have a list of things that change instead of a vague statement that something could happen--or not.

In such a dialog also the possibilities in the options dialog can be referenced because nobody finds the option to change highlighting saving today.
Comment 7 Buovjaga 2018-03-18 13:29:11 UTC
*** Bug 116458 has been marked as a duplicate of this bug. ***
Comment 8 Heiko Tietze 2018-04-11 08:44:13 UTC Comment hidden (no-value)