https://bugs.documentfoundation.org/show_bug.cgi?id=173721

            Bug ID: 173721
           Summary: FILEOPEN ODP: a text:list without continue-numbering
                    after a plain paragraph continues the previous
                    numbering
           Product: LibreOffice
           Version: 26.8.0.3 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: filter:odf
          Severity: normal
          Priority: medium
         Component: Impress
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 208744
  --> https://bugs.documentfoundation.org/attachment.cgi?id=208744&action=edit
Impress: two lists separated by a plain paragraph, no continue-numbering

In Impress, a numbered <text:list> that follows a plain paragraph continues the
numbering of the list before it, although the file does not ask for that.
Writer restarts it, as ODF requires, and so does PowerPoint.

ODF 1.3 part 3: every list of level 1 "defines a list and the counter domain
for its list items" (5.3.1). Continuing the numbering of the preceding list is
something a file has to ask for, with text:continue-numbering="true" or
text:continue-list (19.785, 19.786). 19.786 gives no default value, so an
absent attribute leaves the list as its own counter domain.

Steps: open the attached two-lists.fodp. It has a list of two items, a plain
paragraph, and a second list of two items, with no continue-numbering.
Actual: 1. 2. / plain paragraph / 3. 4.
Expected: 1. 2. / plain paragraph / 1. 2. The attached two-lists.fodt, which
has the same markup, gives this result in Writer.

When saving, Impress writes text:continue-numbering="true" on the second list,
so its own files round-trip correctly. Only lists without that attribute are
affected. Workarounds for generated files: text:continue-numbering="false" on
the list, or text:start-value="1" on its first item.

Reproduced on 26.8.0.3 and master, macOS.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to