Created attachment 119255 [details] PTTX with ==> character Some of ==> made by PowerPoint 2007 will not show correctly in LibO. I use LibO 5.0.2.2 under Win7 SP1 x64.
Created attachment 119256 [details] Compare Impress and PowerPoint
Created attachment 119257 [details] Compare Impress and PowerPoint Same issue for LibreOffice Impress 4.4.2.2 under lubuntu 15.04.
Created attachment 119258 [details] PPTX with correct one and incorrect one I think that the issue might come from Chinese character or Chinese font. For this file one is correct and the other is incorrect under Win7 x64 SP1. But both arrow turn in to square character under lubuntu 15.04.
hi, I adjusted version field to 4.4.2.2 since it's the earlier release you saw the bug. I opened the test file under Win8.1x64 using LibO 4.4.5.1 and the arrow character of that PPTX is correctly shown as in MS Office probably there's a font issue on your computers
I suspect this is caused because that arrow is from some non-standardly encoded font (not following Unicode) such as Wingdings, which will be obviously replaced when not available.
(In reply to Adolfo Jayme from comment #5) > I suspect this is caused because that arrow is from some non-standardly > encoded font (not following Unicode) such as Wingdings, which will be > obviously replaced when not available. Yep, it is Wingdings. Should this be closed as notourbug, or was there some bug report / enhancement for better automatic font replacement? Works ok here. Win 7 Pro 64-bit, Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: fi-FI (fi_FI)
maybe a related issue is Bug 94776 which is still in NEEDINFO state because of lack of important informations from reporter
Since the pptx contain the arrow as a character with Wingdings font, and the font is not present in Linux (and the other font in Windows/Linux), nothing can be done. Unfortunately symbols can't be substituted well, since their glyphs are special and unique. The current behavior is therefore not a bug, or if it's considered a bug from the user's perspective, it can't be fixed in LibreOffice.