Bug 107793 - FILESAVE: docx file; multiple highlighted text colours have been saved in one colour.
Summary: FILESAVE: docx file; multiple highlighted text colours have been saved in one...
Status: RESOLVED DUPLICATE of bug 125268
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.0 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:docx, regression
: 108091 (view as bug list)
Depends on:
Blocks: DOCX Highlight-Color
  Show dependency treegraph
 
Reported: 2017-05-12 11:13 UTC by Alex
Modified: 2020-03-23 09:40 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (12.10 KB, application/odt)
2017-05-12 15:00 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2017-05-12 11:13:15 UTC
Description:
Creating and saving .docx files in LibreOffice, so others can review and edit them in their own software (Pages, Office and Google docs). 

I background-highlighted various texts in my files (using the highlight button and sub-palette viewer), in different colours so that editorial reviews could be made. However on saving the files, all highlighted texts were converted to one colour, diminishing all my editorial key/legend for others to refer too. I.E "Yellow highlighted text is for inputting, orange highlighted text is for editorial review by the Director", on opening the file, the orange sections had been converted to yellow.

Steps to Reproduce:
1.Copy and paste text on to a new page, from various copy-and-pasted files that have been compiled from templates old and brand new.
2. Highlight texts in multiple colours
3. Save as a .docx 

Actual Results:  
Re opened and found multiple colour highlights converted to one colour.

Expected Results:
Colours should have saved correctly.


Reproducible: Always

User Profile Reset: No

Additional Info:
Thinking about it, the using old templates may be creating a few buggy issues, perhaps I could copy and paste into an .rtf file, convert to paling text then copy/paste to libra, its a whole extra process though. If editing in MS Office saves everything accurately, so there must be a way around for Libre :) 

Also theres no way of opening .pages files in Libre other than resaving through MS Office as .docx and losing all the previous formatting. 

Good luck and thanks for the great work, if bugs like this get fixed then we can look at converting the whole of our office set up to Libre, until then, I'm the office gineapig trying this out first. 


[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Mac OS X (All)
OS is 64bit: no
Builds ID: LibreOffice 5.2.6.2


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.1 Safari/603.1.30
Comment 1 Telesto 2017-05-12 15:00:20 UTC
Created attachment 133267 [details]
Example file

Steps to reproduce:
1. Open attached file
2. Save to DOCX
3. Open the DOCX and the ODT
4. Compare both

The highlighted colors differ.

Found in
Version: 5.4.0.0.alpha1+
Build ID: 970b431f1a7b6b96c4c9536657ce4fe9d8f5b585
CPU threads: 4; OS: Windows 6.2; UI render: default; 
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-11_23:07:53
Locale: en-US (nl_NL); Calc: single

and in
Version: 5.2.5.0.0+
Build ID: a4d4fbeb623013f6377b30711ceedb38ea4b49f8
CPU Threads: 4; OS Version: Windows 6.2; UI Render: GL; 
TinderBox: Win-x86@62-merge-TDF, Branch:libreoffice-5-2, Time: 2016-12-24_14:43:55
Locale: nl-NL (nl_NL); Calc: CL

but not in 
Versie: 4.4.6.3 
Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d
Locale: nl_NL
Comment 2 Xisco Faulí 2017-05-13 19:17:35 UTC
Regression introduced by:

author	Zolnai Tamás <zolnaitamas2000@gmail.com>	2015-03-18 09:31:11 (GMT)
committer	Zolnai Tamás <zolnaitamas2000@gmail.com>	2015-03-21 15:19:09 (GMT)
commit 8519d51b3a06a84d0d6418651e66e9bb534f1788 (patch)
tree bba32ae5e640194ee0e2fd86e0c0a7ef16f42dbd /sw/source/filter/ww8/ww8atr.cxx
parent 89399a6ba7c1817dfdc7676603f3fa1106d398c5 (diff)
Char highlight: export character background to MSO formats based on settings

The problem seem to be in AttributeOutputBase::CharBackgroundBase

Bisected with bibisect-50max

Adding Cc: to Zolnai Tamás
Comment 3 Xisco Faulí 2017-05-30 22:19:18 UTC
*** Bug 108091 has been marked as a duplicate of this bug. ***
Comment 4 Tamás Zolnai 2017-05-31 08:34:22 UTC
Hi guys,

It's not a bug. LO behavior was changed for better comapatibility with MSO formats:
https://wiki.documentfoundation.org/ReleaseNotes/5.0#Word-compatible_text_highlighting

In MSO there are two kind of character background called highlighting and shading. By default LO highlighting is saved as MSO highlighting, but MSO highlighting has only a 16 color palette, so colors are converted to this 16 colors using the best matching color, that's why colors are different and also may happen that two colors are converted to the same MSO highlighting color.
At the Tools -> Options -> Load/Save -> Microsoft Office you can change the default behavior to save LO highlighting as MSO shading and so you get the old behavior having all colors the same, but be aware of that when opening this document with MSO, backgroud colors will be shading, so the highlighter tool won't work on them. There is a different settings for shading.
Comment 5 Xisco Faulí 2017-05-31 08:37:57 UTC
*** Bug 99023 has been marked as a duplicate of this bug. ***
Comment 6 Nicolas Mailhot 2017-05-31 11:14:20 UTC
Can't mark as notabug a change that results in white-on-white text when saving as .doc (bug #99023)

It's not just a presentation regression it's functionnaly a data loss as text disappears
Comment 7 Tamás Zolnai 2017-05-31 11:19:04 UTC
(In reply to Nicolas Mailhot from comment #6)
> Can't mark as notabug a change that results in white-on-white text when
> saving as .doc (bug #99023)
> 
> It's not just a presentation regression it's functionnaly a data loss as
> text disappears

The two bugs are not the same. I reopend tdf#99023 for this reason.
Comment 8 Dieter 2020-03-23 09:39:49 UTC
There are a lot of bugs reporting that problem. I think it is better to mark them as duplicates. Tamás feel free to change it back, if you disagree.

*** This bug has been marked as a duplicate of bug 125268 ***