Bug 166233 - FILESAVE: Tagged PDF export makes Calc size grow 15-30x
Summary: FILESAVE: Tagged PDF export makes Calc size grow 15-30x
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
24.8.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: PDF-Export PDF-Accessibility
  Show dependency treegraph
 
Reported: 2025-04-17 17:05 UTC by Timur
Modified: 2025-04-17 18:22 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2025-04-17 17:05:57 UTC
Since tdf#123870 where tagged content is ostensibly fixed, if Tagged is checked in PDF export, PDF grows a lot.
And that is worsened by tdf#39667 where tagged PDF export options are checked by default, wihtout due consideration of reality with larger documents. 

For example, using attachment 171182 [details] from tdf#141508, export size grows from 0,7 MB to 21 MB. 
There is already tdf#157028 with this, but sample there andin duplicates is text document, so I opened this separately to check.
Comment 1 V Stuart Foote 2025-04-17 17:57:56 UTC
This was expected when done for bug 39667

By their nature--fully tagged PDF, a superset of 'accessible' PDF (PDF/UA ISO 14289-1) are *much* larger than legacy untagged (and non-accessible) PDF generated for published formatting only.

LibreOffice intentionally implemented tagged PDF by default (bug 39667 - https://gerrit.libreoffice.org/c/core/+/148303 ) simply toggling the PDF export to enabled.  Tagging since expanded with PDF/UA and PDF/A3 support to comply with those formatting requirements.

Users can easily disable/uncheck creation of Tagged PDF to restore concise PDF, but those PDF will not meet accessibility or archival format standards.

As LibreOffice as an Assistive Technology, and the majority of institutional/corporate users are required to prepare/publish accessible documents--so preparing tagged and accessible PDF are reasonable defaults.

IMHO => INVALID and => WF users can choose in UI to not prepare tagged or fully accessible PDF.
Comment 2 Timur 2025-04-17 18:05:13 UTC
That is not expected by huge majority of users. 
Those who need accessible PDF have the checkbox.
Question is: who in the world will use enormous number of tags, without PDF/UA option?
It all makes no sense. 

"Users can easily disable/uncheck creation of Tagged PDF" yes, but majority will not pay attention and will unnecessarily have huge PDFs.
Rather should smaller number of those who need them check Tagged PDF, wrongfully defaulted in bug 39667 .  

Contrary to the paroles, we should take into account the example of 3.000% file increase.
Comment 3 V Stuart Foote 2025-04-17 18:22:09 UTC
(In reply to Timur from comment #2)
> That is not expected by huge majority of users. 
> Those who need accessible PDF have the checkbox.
> Question is: who in the world will use enormous number of tags, without
> PDF/UA option?
> It all makes no sense. 
> 
> "Users can easily disable/uncheck creation of Tagged PDF" yes, but majority
> will not pay attention and will unnecessarily have huge PDFs.
> Rather should smaller number of those who need them check Tagged PDF,
> wrongfully defaulted in bug 39667 .  
> 
> Contrary to the paroles, we should take into account the example of 3.000%
> file increase.

Nonsense. Folks using PDF to publish/exchange their documents *are* more often than not required to prepare accessible PDF--that means tagged, structured, and bookmarked with alternate text provided for meaningful graphics and charts. I.e. larger PDFs.

Folks can *choose* to generate more concise PDF if that meets their needs--that capability has not been taken away, it is just not the default.

Otherwise LibreOffice as a PDF/UA or WCAG 2.0 compliant document authoring tool, is mandated to implement accessible content--EN 301 549, US Section 508 of the Rehabilitation Act, Canadian Accessible Canada Act, Australian  Disability Discrimination Act 1992 (DDA), and Etc.

Point is ESC and TDF opted to enable by default, users can uncheck it if that meets their needs but the project can't.