[
https://issues.apache.org/jira/browse/TIKA-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18115687#comment-18115687
]
ASF GitHub Bot commented on TIKA-4891:
--------------------------------------
Copilot commented on code in PR #3177:
URL: https://github.com/apache/tika/pull/3177#discussion_r4018292371
##########
docs/modules/ROOT/pages/configuration/parsers/pdf-parser.adoc:
##########
@@ -113,9 +113,12 @@ text. `NONE` ignores the tree and writes what the stripper
writes, the output of
The `AUTO` gate, per page. A page uses its tags only when the tree claims at
least `minCoverage`
of the page's text (artifact content counts, since a producer that marks the
body as artifact
has not described the page), at most `maxDanglingRatio` of the tree's leaves
for the page
-point at content the page never draws, and the tree puts at least some of the
page's text in
+point at content the page never draws, the tree puts at least some of the
page's text in
an element that holds text (a paragraph, heading, cell or item: a tree of bare
spans or
-divisions has no paragraphs to offer). Both start loose (0.5 and 0.2) until a
corpus says
+divisions has no paragraphs to offer), and the tree does not cut the page's
words into
+pieces (some form generators put every glyph in its own paragraph, which would
write each
+word as a column of letters; a page where more than a third of its words span
three blocks
Review Comment:
`MAX_SHREDDED_RATIO` is `0.3f`, so AUTO falls back when more than 30% of the
counted words are shredded, not when more than one third are. A page with
31/100 shredded words therefore follows the stripper despite this
documentation; please document the actual 30% threshold (or change the constant
if one third is intended).
> Improve handling of PDF/UA structural tags/marked content
> ---------------------------------------------------------
>
> Key: TIKA-4891
> URL: https://issues.apache.org/jira/browse/TIKA-4891
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
> Attachments: 1008690.pdf, TIKA-4891-1008690.html,
> image-2026-09-13-10-54-59-251.png, screenshot-1.png, screenshot-2.png
>
>
> PDF/UA includes structural markup. We hacked out a standalone handler for
> this back in 1.x but haven't touched it in years.
>
> We should modernize our handling of structural tags and eventually consider
> turning that on by default. That decision will be based on evaluation on
> 1000s of PDFs. This is not a default switch to be taken lightly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
