Created attachment 106316 [details]
Test case (test.pptx)
The MS Office 2007/Windows produced file should look like:
B. That’s a test:
* In test 1
* Second line
However, with both LO 126.96.36.199/Windows and 188.8.131.52/CentOS6-x86-64-linux, a spurious mailbox symbol appears instead of a spacing between the bullet point and the item.
I think the test case requires MS Wingdings; the bullet point is probably character 110 and the half-open mailbox is character 46 (ASCII: '$').
Created attachment 106317 [details]
Screenshot: LO184.108.40.206 vs. PowerPoint 2007
I confirm this adding with import in LO 220.127.116.11 & Windows 7 Home Premium.
I set status to NEW.
From ppt/slides/slide1.xml (excerpt):
<a:buFont typeface="Wingdings" pitchFamily="2" charset="2"/><a:buChar char="§"/>
</a:pPr><a:r><a:rPr lang="en-US" dirty="0" smtClean="0"/><a:t>In test
According http://msdn.microsoft.com/en-us/library/documentformat.openxml.drawing.bulletfont%28v=office.14%29.aspx , one has:
pitchFamily "0x02 VARIABLE PITCH + UNKNOWN FONT FAMILY"
charset "0x02 Specifies the Symbol character set. This value specifies that the characters in the Unicode private use area (U+FF00 to U+FFFF) of the font should be used to display characters in the range U+0000 to U+00FF."
- The character "§" is Latin1's 0247, 167, A7 - which matches the small bullet point.
- Additionally shown is ASCII's "." (056, 46, 2E), which is the open-mailbox symbol.
As far as I know, Wingdings is an old-style TTF font with 256 characters and not an Unicode font. I wonder whether the charset="2" causes the trouble by trying to access 0x00A7 + 0xFF00 -> 0xFFA7 in a font which only has FF characters?
PriyankaGaikwad committed a patch related to this issue.
It has been pushed to "master":
tdf#83889:FILEOPEN:PPTX bullet point is followed by spurious symbol
It will be available in 4.5.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
Verified on LO Windows build ID :
Build ID: 5984cc83fe756f7483d1ac582b8adbef5042be8b
TinderBox: Win-x86@42, Branch:master, Time: 2015-05-07_05:11:59
Locale: en-US (en_US)
Issue has been fixed.