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.
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.
confirmed under Win7x64 using LibO 4.2.3.3
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
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
(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.
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.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.3 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results; 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-06-08
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)
Reproducible with LO 5.1.0.1, Win 8.1
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
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
So the text color in MSO is #505050 which is rgb(80,80,80) and LO is loading it as #808080.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Everything in attachment 98274 [details] works now, bold, underline, the grey is #505050 like in MSO. Let's close. Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: 97bc09c1fef52c45cf299868045d250838d8e89b CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 28 September 2020