1. core/workdir/CustomTarget/writerfilter/source/ooxml/OOXMLFactory_shared-math.cxx:461]: (style) Expression is always false because 'else if' condition matches previous condition at line 460. Source code is if (rValue == "left") { rOutValue = NS_ooxml::LN_Value_math_ST_Jc_start; } else if (rValue == "left") { rOutValue = NS_ooxml::LN_Value_math_ST_Jc_left; } 2. Similar thing a few lines further down if (rValue == "right") { rOutValue = NS_ooxml::LN_Value_math_ST_Jc_end; } else if (rValue == "right") { rOutValue = NS_ooxml::LN_Value_math_ST_Jc_right; }
thank you for your report OOXMLFactory_shared-math.cxx is generated from writerfilter/source/ooxml/model.xml the lines 8218 and 8219 are responsible for the findings. introduced by commit b17f4ecea142fd6f311dcb457e8896cd12e60fc0 in LO 4.4 branch and all following hmm, start means align to leading edge and end means align to tailing edge I don't see the difference to left and right aligned. so maybe it's correct and was just forgotten in the commit message?
as Micheal Stahl noted it was actually introduced in commit 794c8cf13bd0c8512bf77c57934abd9b9a0fe998 [Docx] n#513479: import start/end values for ST_Jc
So we should just replace this: <value tokenid="ooxml:Value_math_ST_Jc_start">left</value> by this: <value tokenid="ooxml:Value_math_ST_Jc_start">start</value> (see http://opengrok.libreoffice.org/xref/core/writerfilter/source/ooxml/model.xml#8218) Miklos: does it seem ok or would it break something?
'needsConfirmationAdvise' is only used for unconfirmed bugs. Removing it from this bug. [NinjaEdit]
** 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.4.1 or 5.3.6 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-20170929
Dear dcb314, 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 dcb314, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Julien, is this one still actual?
(In reply to Roman Kuznetsov from comment #8) > Julien, is this one still actual? There have been several commits on writerfilter/source/ooxml/model.xml, at least what dcb314 described doesn't appear anymore in workdir/CustomTarget/writerfilter/source/ooxml/OOXMLFactory_shared-math.cxx Here's what we see now: 257 case NN_shared_math|DEFINE_ST_XAlign: 258 if (aValue.empty()) 259 return false; 260 switch (aValue[0]) 261 { 262 case 'c': 263 if (aValue == "center") { rOutValue = NS_ooxml::LN_Value_math_ST_XAlign_center; } 264 else { return false; } 265 return true; 266 case 'l': 267 if (aValue == "left") { rOutValue = NS_ooxml::LN_Value_math_ST_XAlign_left; } 268 else { return false; } 269 return true; 270 case 'r': 271 if (aValue == "right") { rOutValue = NS_ooxml::LN_Value_math_ST_XAlign_right; } 272 else { return false; } 273 return true; 274 } 275 return false; So let's put this one to WFM then. dcb314: don't hesitate to reopen if I missed something. Roman: thank you for the ping! :-)