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

            Bug ID: 140461
           Summary: Libreoffice 7.1.0.3 cannot handle "<w:fldSimple
                    w:instr="TOC \o "1-3" \h" w:dirty="true"/>" to create
                    Table of Contents automatically anymore
           Product: LibreOffice
           Version: 7.1.0.3 release
          Hardware: All
                OS: Mac OS X (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: [email protected]
          Reporter: [email protected]

Description:
We create an .docx document with apache poi and convert it to PDF with
jodconverter (wich requires LibreOffice). The TOC (table of contents) was
updated in previous versions by adding "<w:fldSimple w:instr="TOC \o "1-3" \h"
w:dirty="true"/>" when you opened the generated .docx file. MS-Word and
Google-Docs are still able to recognize it, but LibreOffice does not detect the
instruction to create the TOC automatically. Also the "Update Index/Indices"
does not appear on right-click.

When I add a TOC by hand in the opened .docx in LibreOffice, everything works
fine.

It was tested with MacOS-bigSur(11.2) and MS-Windows-10.

Unfortunately i cannot attach the example files here.

Actual Results:
The "<w:fldSimple w:instr="TOC \o "1-3" \h" w:dirty="true"/>" is not recognized
by  LibreOffice and sometimes leads to lacking UI.

Expected Results:
The TOC is automatically created and recognized in LibreOffice. The "Update
Index/Indices" can be executed on right-click or triggered programmatically.


Reproducible: Always


User Profile Reset: No



Additional Info:
Works with MS-Word and Google-Docs, just "Update Indexes" is required. The TOC
instruction is recognized and applied.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to