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

            Bug ID: 157817
           Summary: PAC gives "Invalid use of a "P" structure element"
                    with title of multi page TOC
           Product: LibreOffice
           Version: 24.2.0.0 alpha0+ Master
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: bibisected, bisected, regression
          Severity: normal
          Priority: medium
         Component: Printing and PDF export
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: kelem...@ubuntu.com
            Blocks: 139007

Created attachment 190283
  --> https://bugs.documentfoundation.org/attachment.cgi?id=190283&action=edit
Example file from Writer

Attached example document has a simple TOC that spans two pages.

When exported as a PDF/UA document the PAC tool gives the Logical Structure -
Structure Tree - "P" structure elements - Invalid use of a "P" structure
element
error message. Not if all of the TOC is displayed on the same page.

1. Open attached file
2. Save as PDF, make sure to check the PDF/UA option
3. Open it in the PAC 2021 tool
-> error message

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e9374f74385d7dfe77d1902d3d82af20143bc775
CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: en-US (hu_HU); UI: en-US
Calc: threaded

Seems to have started with

https://git.libreoffice.org/core/+/033e37b49b5712df19dbfd2c307a102bce620de1

author  Michael Stahl <michael.st...@allotropia.de>     Thu Aug 31 19:50:55
2023 +0200
committer       Caolán McNamara <caolan.mcnam...@collabora.com> Tue Sep 26
21:13:18 2023 +0200
tree    1abc64b331189c3cadb29faa1c930f731a47d569
parent  8c94442fab9588dd0793a1792979f50a600c4c65 [diff]

sw: PDF/UA export: produce nested Sect SEs for nested sections


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=139007
[Bug 139007] [META] PDF accessibility
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to