Download it now!
Bug 33787 - FORMATTING, FILEOPEN: Bullet point numbers don't increment (.lwp import)
Summary: FORMATTING, FILEOPEN: Bullet point numbers don't increment (.lwp import)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: TableofContents-Indexes LWP
  Show dependency treegraph
Reported: 2011-01-31 15:10 UTC by Jaxson Lee
Modified: 2019-12-03 13:55 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

lwp '97 file containing different styles of bullet points (21.24 KB, application/vnd.lotus-wordpro)
2011-01-31 15:10 UTC, Jaxson Lee
PDF showing LWP '97 and LibO Writer 3.3.0 handling of bullets.lwp (182.59 KB, application/pdf)
2011-01-31 15:11 UTC, Jaxson Lee

Note You need to log in before you can comment on or make changes to this bug.
Description Jaxson Lee 2011-01-31 15:10:08 UTC
Created attachment 42782 [details]
lwp '97 file containing different styles of bullet points

The attached .lwp document uses all of the default styles built into Lotus Word Pro '97 for bullet points.

When opened in Writer, the numbered bullet points don't increment correctly. i.e. it shows as 1. 1. 1. rather than 1. 2. 3. and i. i. i. rather than i. ii. iii. 

There is one exception however - the uppercase roman numeral style of bullet does increment correctly (i.e. I. II. III.) and behave as expected. It'll even handle skipped bullet points correctly. It should therefore be a fairly easy fix to get the other number displays to work in the same way. 

I've also attached a .pdf with expected output and Writer output.
Comment 1 Jaxson Lee 2011-01-31 15:11:17 UTC
Created attachment 42783 [details]
PDF showing LWP '97 and LibO Writer 3.3.0 handling of bullets.lwp
Comment 2 Björn Michaelsen 2011-12-23 11:43:04 UTC Comment hidden (obsolete)
Comment 3 sasha.libreoffice 2012-02-23 04:28:11 UTC
reproduced in 3.6.0 master on Fedora 64 bit
And on console appears this:
warn:legacy.osl:6959:1:/usr/src/libre-master/core/sw/source/filter/ww8/ww8par.cxx:3170: WW8: Please report this document, it may have a missing graphic
warn:legacy.osl:6959:1:/usr/src/libre-master/core/xmloff/source/core/xmlerror.cxx:195: An error or a warning has occurred during XML import/export!
Error-Id: 0x10020002
    Flags: 1 WARNING
    Class: 2 FORMAT
    Number: 2
    0: style:font-name-asian
Comment 4 bfoman (inactive) 2013-07-26 12:57:27 UTC
Confirmed with:
Build ID: 2013-06-24 own debug build 
Windows 7 Professional SP1 64 bit

Same results as in reporter's PDF.
Comment 5 QA Administrators 2015-04-19 03:19:55 UTC Comment hidden (obsolete)
Comment 6 Buovjaga 2015-06-15 07:37:14 UTC

Win 7 Pro 64-bit Version:
Build ID: 01a189abcd9a4ca472a74b3b2c000c9338fc2c91
TinderBox: Win-x86@39, Branch:master, Time: 2015-06-14_07:46:28
Locale: fi-FI (fi_FI)
Comment 7 QA Administrators 2016-09-20 10:00:29 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2019-12-03 13:55:26 UTC
Dear Jaxson Lee,

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

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

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:

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team