Created attachment 116426 [details] word file create by our webapp We create docx in our webapp, our filter creates a "shd" entry. MS-word can read this value without problem and in libre office "4.1.6.2" it was still working, too! HalloStrik.docx -> unzip -> /word/stlyes.xml <w:style w:type="paragraph" w:styleId="Geilo" w:default="false"> <w:rPr> <w:shd w:val="clear" w:fill="auto" /> If you take out this line, it looks correct in current version of libre.
<w:shd w:val="clear" w:fill="auto"/> appears twice. Once under <w:pPr> which is fine and also under <w:rPr> which if removed allows Writer to display it correctly. I could find the part in the ooxml specification for "shd" which is a property of paragraph styles but I could not find it as a property of text. I have seen it in document.xml as character background colour which in Writer is direct formatting. Is it possible to create a document from Word or Writer that has the text property in paragraph styles or point to where in the specification that has it? Question to any and all: Even if it is not valid, should it not just be ignored? Maybe it is to do with the order they are read. When it gets to the second one, the strikethrough would have been read after it but it does not get there. Does that mean that there are other properties that do not get read in this example? Windows Vista 64 Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
yes, that bug is on "needinfo", but nobody wanted infos from me. I just reported a bug which i would like to see it fixed. needinfo was from one programmer to another. so i set the bug as "new" and hope somebody cares...
Indeed, as stated in the specification the shd can be part of the pPr and also rPr. Within the pPr the whole paragraph gets a background shading, if defined within the rPr then the text run gets a background shading. If both are defined, then first the paragraph background shading is applied thereafter the text run shading. The documentation to the rPr shading can be found in the ECMA-376 Fourth Edition Fundamentals And Markup Language Reference.pdf on page 303 (17.3.2.32 shd Run Shading) Be it as it is, both shadings are having the "clear" value which means that no pattern is used -> no background is to be painted. The question is, why does this background pattern affect underline and or strike through attributing ? Best regards, Sven
** 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.2.5 or 5.3.0 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-20170306
This bug was incorrectly moved from NEEDINFO to NEED. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180102
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180129