Created attachment 98015 [details] the font color was supposed to be cyan and not green I download the .docx file found at < http://download.microsoft.com/documents/customerevidence/Files/710000003670/Xiamen_Tungsten_Group_unifies_enterprise.docx > and opened it with kingsoft writer and then saved it as an DOC. When i opened the DOC in LibO, on page 1, the colored second line has turned into green rather than being blue. Tested in 3.6 - 4.3.
Created attachment 98016 [details] doc file produced by kingsoft writer
Confirmed in master.
Reproducible in LibreOffice 3.5.4 on Debian Wheezy. According to https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Version "We currently use the Version field to store the earliest LibreOffice version on which we can reproduce a bug". So I change the version field.
(In reply to comment #3) > Reproducible in LibreOffice 3.5.4 on Debian Wheezy. > > According to https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Version > "We currently use the Version field to store the earliest LibreOffice > version on which we can reproduce a bug". So I change the version field. Thanks for testing it on 3.5 and changing it.
Created attachment 101100 [details] comparative screenshot LibO (top) and Word Viewer (bottom) I confirm issue in OOo 3.3.0 and all LibO release up to 4.2.4.2 under Win7x64 so bug is inherited from OOo I attach a bigger comparative screenshot to better show the difference in color
** 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.1 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-07-18
bug persists in LibO 4.4.5.1 and 5.1.0.0.alpha1+ (x64) Build ID: 5a61d7f049a81d6e747d9d097f364ae45f58697b TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-07-16_01:06:26 Locale: en-US (it_IT)
** 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.5 or 5.2.1 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-20160920
I round-tripped the file from comment 1 in MSO2003. LibreOffice properly shows a cyan color on those round-tripped files. So, does this mean that Kingsoft used a non-palette color, and MSO automatically converts it to the nearest palette color?
(In reply to Justin L from comment #9) > I round-tripped the file from comment 1 in MSO2003. LibreOffice properly > shows a cyan color on those round-tripped files. Interesting. > So, does this mean that Kingsoft used a non-palette color, and MSO > automatically converts it to the nearest palette color? You can use non-palette colors in Word 2003 and the original docx file mentioned in comment 0 used the same cyan color. Maybe kingsoft is saving it in a way that LO isnt able to understand but is part of the spec. All i know is that Word 2003/2007/2010 and WPS Writer all show it as RGB(0,114,198) and LO is opening it as RGB(0,128,128).
Created attachment 136557 [details] kingsoft/wps doc with colors Here is a sample .doc from WPS with a variety of colors and LO only gets these ones right. Red rgb(255,0,0) Yellow rgb(255,255,0)
Reproducible with LibreOffice 5.2.7 and 6.0.0.0.alpha1 on Debian Jessie.
** 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
There is a "new" sprmCCv used by Read_TextForeColor which can be any RGB color - and that is what is processed after Word 2003 roundtrips the file. In this Kingsoft document, LO can only use the older sprmCIco, read by Read_TextColor, which references a 16 bit table defined by 2.9.119 Ico There are a lot of errors when reading this document: sprm longer[6] than remaining[4] bytes, doc or parser is wrong mso-dumper does indicate that CCv sprms exists in the document, but they are never seen/processed in LO. <prl type="Prl" offset="4541" index="0"> <sprm value="0x2a42" ispmd="0x42" fSpec="0x1" sgc="character" spra="1" name="sprmCIco" operandSize="1" operand="0x10"/> </prl> <prl type="Prl" offset="4544" index="1"> <sprm value="0x4a60" ispmd="0x60" fSpec="0x1" sgc="character" spra="2" name="sprmCIcoBi" operandSize="2" operand="0x10"/> </prl> <prl type="Prl" offset="4548" index="2"> <sprm value="0x6870" ispmd="0x70" fSpec="0x0" sgc="character" spra="3" name="sprmCCv" operandSize="4" operand="0xe7c6b4"/> ===================================================================== proposed fix at http://gerrit.libreoffice.org/c/core/+/98911
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/56b04e40ab72b6333ce278ba2980650f5272025f tdf#77962 ww8import: 0x4xxx sprms are always 2 byte It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Justin Luth committed a patch related to this issue. It has been pushed to "libreoffice-7-0": https://git.libreoffice.org/core/commit/52f004e27fbdef114a6fa1b467a7919ab1762dab tdf#77962 ww8import: 0x4xxx sprms are always 2 byte It will be available in 7.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Justin Luth committed a patch related to this issue. It has been pushed to "libreoffice-6-4": https://git.libreoffice.org/core/commit/8f37d303905c85dfa5027976d504b9b4904accce tdf#77962 ww8import: 0x4xxx sprms are always 2 byte It will be available in 6.4.6. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
*** Bug 77860 has been marked as a duplicate of this bug. ***