Created attachment 68530 [details] Circular arrow created in LibO * Create a Circular Arrow in LibO - attached file "arrow_created_LibO.odp" * Export as ppt (or pptx). - attached file "arrow_created_LibO.ppt" * Open in LibO "arrow_created_LibO.ppt" - The head of the arrow is incorrectly displayed. * Create the same Circular Arrow in PowerPoint (3003) - attached file "arrow_created_PPT2003.ppt" * Open it in LibO - The arrow is correctly displayed * Save it as ppt - attached file "arrow_created_PPT2003_saved_LibO.ppt" * Open in LibO the newly created file - It is displayed correctly! In summary, - when working with a MS PPT generated "Circular arrow", LibO is able to open/save the ppt file. - when working with a LibO generated "Circular arrow", LibO can only save it as .odp but not as .ppt (or pptx).
Created attachment 68532 [details] Circular arrow created in LibO saved as ppt
Created attachment 68533 [details] Circular arrow created in MS PPT2003
Created attachment 68534 [details] Circular arrow created in MS PPT2003 saved as ppt in LibO
Confirmed this bug with 3.5.4.2 and 3.7.0.0-master of last week (2012-10-14) on Ubuntu 12.04 x86_64
Confirm reproducible on LO 4.0.4.1 (Win7 32bit)
*** Bug 69785 has been marked as a duplicate of this bug. ***
** 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-04-18
Still a problem in V4.4.2 - unchanged behaviour OS Fedora 21
This issue is still reproducible in Version: 5.2.0.0.alpha1+ Build ID: e7f55f15ccd97bc92e1400bc5862171a621da3e2 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-04-27_00:29:05 Locale: es-ES (es_ES)
*** Bug 86295 has been marked as a duplicate of this bug. ***
** 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
The bug is still present in the last libreoffice version. Of note, export in pptx is a bit better but the arrow is still not identical to the original Tested in Version: 5.4.4.2 Build ID: 2524958677847fb3bb44820e40380acbe820f960 CPU threads: 4; OS: Mac OS X 10.11.6; UI render: GL; Locale: fr-FR (fr.UTF-8); Calc: group Version: 6.0.0.3 Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 4; OS: Mac OS X 10.11.6; UI render: GL; Locale: fr-FR (fr.UTF-8); Calc: group
Still reproducible in Version: 6.2.0.0.alpha0+ Build ID: b264c9276888bb952deeec31abe3a77e05dac164 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: threaded
Dear Pierre Martineau, 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
The bug is still present in the last libreoffice version It both affect ppt and pptx, but with differences - ppt: the arrowhead is not correct - pptx: the originally round arrow is oval after export Tested in Version: 6.3.0.4 Build ID: 057fc023c990d676a43019934386b85b21a9ee99 Threads CPU : 4; OS : Mac OS X 10.11.6; UI Render : par défaut; VCL: osx; Locale : en-US (fr.UTF-8); Langue IHM : fr-FR
Created attachment 168822 [details] The original document and its pptx version in PP Original document is attachment #86605 [details] from duplicate bug #69785 Still a problem in: Version: 7.2.0.0.alpha0+ (x64) Build ID: 8e691505d4675b878b30bd00cd2e4fb4f794f0ef CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL
My take would be to put all mso-shapes into a Gallery theme and fill the UI-lists with ooxml-preset shapes. That way users would automatically use pptx compatible shapes. User who need compatibility with binary ppt can still get the shapes from the Gallery theme.
The reason is, that the w and h attributes of the path element are set to the bound rectangle of the path, but they need to be set to the shape size in Hmm. The 'circular arrow' shape has no compatible ooxml preset shape, so the error cannot be fixed with the new introduced DMLPresetShapeExporter. The ooxml preset shape 'circularArrow' is not compatible, because its arrow head has a different direction in its base. For a full fix including handles, it would be necessary to generate an individual custGeom element. That is not trivial, because our circular Arrow uses the enhanced path commands B and W, whereas PowerPoint needs the command G (arcTo). PowerPoint 365 reads our circular arrow from an .odp document and converts it to a suitable shape including handles for pptx. That is very likely done by a general algorithm, because the resulting shape has 247 equations (gd elements). Astonishing, opening a .ppt document with this shape in PowerPoint looses the handles. But even exporting our shape to such ooxml custGeom, would not really help here, because we would not be able to detect that it is our circular arrow on import. Thus we will convert it to a general path and that has the same problem, that w and h is wrongly set. Other shapes with the same error are 'up-right-down-arrow' and 'up-right-arrow-callout' and Bezier-curves.
Created attachment 173208 [details] Other effected shapes The document has the shapes in Blue and behind each one a screen shot in Red.
Created attachment 173209 [details] w and h attributes manually set Here the w and h attributes were manually set to the shape size (cx, cy) in Hmm. You can see, that the size is correct now. But such will not be the complete fix, because position has to be corrected too.
Dear Pierre Martineau, 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