Created attachment 144115 [details] Colored Fontwork to test export Enter a Fontwork in Impress or Calc with filled characters with outline. Save the file in the corresponding MS Office format. Reopen the exported file or open it in MS Office. The outline of the character becomes a shape border line, the fill color of the characters are lost and the characters are black. If you open the original files in MS Office and export it there to pptx or xlsx respectively, MS Office converts it so, that the characters look the same. We should do the same, to get a good user experience. [BTW, using the Fontwork in Writer results in the correct character fill and outline. But the size of the shape is wrong.]
Created attachment 144116 [details] Export result by LibreOffice
Created attachment 144117 [details] How PowerPoint converts from odp to pptx
Reproducible Version: 6.2.0.0.alpha0+ (x64) Build ID: 82b12d836582c2dccc5f438363c9d128e85ac656 CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-08-12_03:30:11 Locale: es-ES (es_ES); Calc: CL
Also reproduced in Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 4.10; Render: default; Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Dear Regina Henschel, 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
Export is correct in Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community Build ID: e718f0e703c0fb33a0b1b5efe7b13b02c25f3335 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL
Issue fixed in https://cgit.freedesktop.org/libreoffice/core/commit/?id=005f5db47b8e1bbd7ebddee92009be072e835fd5 author Regina Henschel <rb.henschel@t-online.de> 2020-07-04 15:11:03 +0200 committer Thorsten Behrens <Thorsten.Behrens@CIB.de> 2020-07-10 00:57:22 +0200 commit 005f5db47b8e1bbd7ebddee92009be072e835fd5 (patch) tree dd91d9f59e17b1ae916c34db7373cd3d4f5a3ab6 parent b8ff69726959ee4d148c12866d64601d86635bcc (diff) tdf#100348 add fill to fontwork in export to pptx Closing as dupe of bug 100348 *** This bug has been marked as a duplicate of bug 100348 ***