Bug 96016 - highlighting and .doc / .docx : the color is changing when re-opened
Summary: highlighting and .doc / .docx : the color is changing when re-opened
Status: RESOLVED DUPLICATE of bug 97865
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2015-11-23 17:35 UTC by leonce35
Modified: 2016-05-20 08:04 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Color chart example (odt) (16.80 KB, application/vnd.oasis.opendocument.text)
2016-05-13 12:55 UTC, Randolph
Color chart example (docx) (5.53 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2016-05-13 12:56 UTC, Randolph
Color chart example (doc) (30.50 KB, application/msword)
2016-05-13 12:56 UTC, Randolph

Note You need to log in before you can comment on or make changes to this bug.
Description leonce35 2015-11-23 17:35:38 UTC
Sometimes I have to highlight my text in a particular color, such as "Yellow 10 ". But after saving my file and reopen it, "yellow 10 " is systematically transformed in "yellow 1". This happens when I record .doc , but not odt .

Best regards
Comment 1 A (Andy) 2015-11-23 20:15:48 UTC
Reproducible with LO, Win 8.1.

Highlight color changes from "Yellow 10" to "Yellow 2".
Comment 2 UR 2015-12-16 19:05:31 UTC
Repoduced with, Linux x86_64

Highlight color changes from "Orange 1" to "Yellow 1"
Comment 3 Randolph 2016-05-13 12:54:41 UTC
Still a problem in, and applies to .docx and .doc files. This a serious incompatibility!

Sample files uploaded (the odt file being the orignal)
Comment 4 Randolph 2016-05-13 12:55:31 UTC
Created attachment 125033 [details]
Color chart example (odt)
Comment 5 Randolph 2016-05-13 12:56:07 UTC
Created attachment 125034 [details]
Color chart example (docx)
Comment 6 Randolph 2016-05-13 12:56:37 UTC
Created attachment 125035 [details]
Color chart example (doc)
Comment 7 Tamás Zolnai 2016-05-20 08:04:42 UTC

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