Bug 78143 - FILEOPEN: WPS DOC - Incorrect font color and missing bold and underline applied to text
Summary: FILEOPEN: WPS DOC - Incorrect font color and missing bold and underline appli...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.6 release
Hardware: Other All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc
Depends on:
Blocks: DOC-Character
  Show dependency treegraph
 
Reported: 2014-05-01 03:26 UTC by Yousuf Philips (jay) (retired)
Modified: 2018-09-30 02:49 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
showing the difference in libO and word 2010, highlighting the missing bold and underlined texts (97.14 KB, image/jpeg)
2014-05-01 03:26 UTC, Yousuf Philips (jay) (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2014-05-01 03:26:31 UTC
Created attachment 98275 [details]
showing the difference in libO and word 2010, highlighting the missing bold and underlined texts

As a continuation of bug 78142, another instance of font styles not being retained in opening the .doc file include the font text which is set to 'gray 6' rather than the user defined color of #505050, bold text disappearing from the beginning of the bullet points, and underlines disappearing from below text.
Comment 1 Yousuf Philips (jay) (retired) 2014-05-01 03:31:38 UTC
This was tested in 3.6 to 4.3. Additional occurrence of bold not being retained in this file include 2 words in the second paragraph of page 1, all hyperlinks, and table text in on page 6.
Comment 2 tommy27 2014-05-01 07:09:53 UTC
confirmed under Win7x64 using LibO 4.2.3.3
Comment 3 Jean-Baptiste Faure 2014-05-01 09:46:00 UTC
For me we can't conclude that there is a bug in Libo here:
1/ It is not clear which version of the file you opened with MS-Word 2010 : the original docx by MS or the doc file by Kingsoft ?
2/ the font Segoe UI Light is not installed by default on Ubuntu systems.

To be more sure that there is a problem in LibO, you should export the docx in doc format using MS-Word 2010 and open this doc file with LibO.

Best regards. JBF
Comment 4 Yousuf Philips (jay) (retired) 2014-05-01 10:05:32 UTC
Hey Jean-Baptiste Faure,

1. I opened the .doc in LibO and word 2010 and attached the results in the jpg.
2. It is not installed by default but i've installed it. :)

Just so that you know, i'm doing extensive testing of .docx files and opening them in LibO, Kingsoft Office and MS Office and then saving them in different formats, and opening those formats in each of the software suits to compare their results. Of course if LibO doesnt render whichever .doc, .docx, or rtf similar to ms word, then these are the only bug reports i'm sending in.

About exporting the docx into doc in word 2010, i've done that and have sent in bug reports for that as well.

Jay
Comment 5 tommy27 2014-05-02 12:50:29 UTC
(In reply to comment #4)
> Hey Jean-Baptiste Faure,
> 
> 1. I opened the .doc in LibO and word 2010 and attached the results in the
> jpg.
> 2. It is not installed by default but i've installed it. :)

set status again to NEW, since I've confirmed it in comment 2.

> Just so that you know, i'm doing extensive testing of .docx files and
> opening them in LibO, Kingsoft Office and MS Office and then saving them in
> different formats, and opening those formats in each of the software suits
> to compare their results. Of course if LibO doesnt render whichever .doc,
> .docx, or rtf similar to ms word, then these are the only bug reports i'm
> sending in.

your test are helpful, but please try to create reports that have all the needed informations, otherwise there will be misunderstanding:

1- O/S where you tested it.
it must be indicated anytime, I know from other reports that you use Linux Mint, but other users who see only this report won't know it

2- replicate exact description of the issue.
you did it in the other report, please replicate it even in followup reports.
just a matter of copy & paste

3- give link to test file. 
here you posted just the screenshot but there's no direct link to the file which is in another report (I suppose it's attachment 98274 [details] from bug 78142) 

bottomline is that you probably know well the bug you are reporting but if you don't give complete and clear description to people who see those bugs for the first time, there're chances your reports will be not completely understood.
Comment 6 tommy27 2014-05-02 12:57:24 UTC
4- better summary notes.
should have important informations, in this case is that the DOC you are talking about come from Kingsoft Writer.

5- use the "See Also" field.
add links of your related bug reports to the "See also" field on the left.

if you follow these tips your reports will be easier to understand.


in the meantime I've made the necessary changes.
Comment 7 QA Administrators 2015-06-08 14:42:08 UTC Comment hidden (obsolete)
Comment 8 Buovjaga 2015-06-21 18:57:09 UTC
Confirmed.

Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+
Build ID: 3ecef8cedb215e49237a11607197edc91639bfcd
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-19_23:16:58
Locale: fi-FI (fi_FI)
Comment 9 A (Andy) 2015-12-27 20:49:49 UTC
Reproducible with LO 5.1.0.1, Win 8.1
Comment 10 QA Administrators 2017-01-03 19:55:28 UTC Comment hidden (obsolete)
Comment 11 tommy27 2017-01-09 06:00:44 UTC
still present in LibO 5.4.0.0.alpha0+
Build ID: 215cbfb460326010737433c2020638e9388a88a4
CPU Threads: 4; OS Version: Windows 6.29; UI Render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-01-02_23:58:32
Locale: it-IT (it_IT); Calc: group
Comment 12 Yousuf Philips (jay) (retired) 2017-09-29 17:35:26 UTC
So the text color in MSO is #505050 which is rgb(80,80,80) and LO is loading it as #808080.
Comment 13 QA Administrators 2018-09-30 02:49:37 UTC Comment hidden (spam)