Bug 161084 - FILESAVE PDF PAC tool reports "Link annotation is not nested inside a Link structure element" error with page headers
Summary: FILESAVE PDF PAC tool reports "Link annotation is not nested inside a Link st...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
7.6.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-15 08:58 UTC by Domenico Tironi
Modified: 2024-05-22 15:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Domenico Tironi 2024-05-15 08:58:04 UTC 
Description:
This bug is very similar to bug id https://bugs.documentfoundation.org/show_bug.cgi?id=157919.
The page headers are also affected and not fixed yet (7.6.7.2).
An odt. file with a hyperlink in a page header exported to pdf with pdf/ua settings checked will be verified with an error (link annotation is not nested inside a link structure element).

Steps to Reproduce:
1.new odt file; page header with hyperlink in it (www.test.de)
2. export it as pdf with pdf/ua settings checked
3.verify the pdf document with pdf accessibility checker 2021, version 21.0.0.0

Actual Results:
accessibility check fails; error "link annotation is not nested inside a link structure element"

Expected Results:
should pass the verification


Reproducible: Always


User Profile Reset: No

Additional Info:
should pass the verification
Comment 1 breadsathwik 2024-05-16 22:14:18 UTC 
Could not reproduce in:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e939685f9c6918830bd3097062790bfccbce937e
CPU threads: 8; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 2 Domenico Tironi 2024-05-21 08:07:16 UTC 
Where can I get the version "24.8.0.0.alpha0+ (X86_64) / LibreOffice Community"?
I tried "24.8.0.0.alpha1", which is available in the libreoffice archive downloads. In that version, the bug is reproducible.
Comment 3 Domenico Tironi 2024-05-21 08:07:52 UTC Comment hidden (obsolete)
Comment 4 breadsathwik 2024-05-21 20:08:28 UTC 
(In reply to Domenico Tironi from comment #3)
> Where can I get the version "24.8.0.0.alpha0+ (X86_64) / LibreOffice
> Community"?
> I tried "24.8.0.0.alpha1", which is available in the libreoffice archive
> downloads. In that version, the bug is reproducible.

You should be able to access the development versions from the pre-releases page here:

https://www.libreoffice.org/download/pre-releases/

But it's not recommended for production use, although it is available for testing. The most recent version should be "24.8.0.0.alpha1+".
Comment 5 Domenico Tironi 2024-05-22 11:40:48 UTC 
Thank you. I tested some preview versions which all have the bug, but

I confirm that the bug does not occur in the following version:

Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 101b08fe1ec77ffe8c1a9b2b8f9f20884269a1ed
CPU threads: 8; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: CL threaded