Skip to content

Pull Request to create/update 'rebased/structure-tree-fix' branch#315

Closed
iText-CI wants to merge 2 commits intodevelopfrom
structure-tree-fix
Closed

Pull Request to create/update 'rebased/structure-tree-fix' branch#315
iText-CI wants to merge 2 commits intodevelopfrom
structure-tree-fix

Conversation

@iText-CI
Copy link
Contributor

@iText-CI iText-CI commented Jan 6, 2026

Programmatically created Pull Request to automatically keep merge branch to develop up-to-date

@iText-CI iText-CI assigned Eswcvlad and iText-CI and unassigned iText-CI Jan 6, 2026
`/Type /StructElem` is optional for structure element nodes, but if it
wasn't present, we weren't checking the /S key for better node titles.
Now it will assume /StructElem type, if type is missing.

Also, there was some weird thing with the caption having NUL characters,
as toUnicodeString was returning them. Not sure, whether they are
present in the PDF itself or is it just some other random issue. For
now just added stripping for some of the ASCII control chars.
@Eswcvlad Eswcvlad force-pushed the structure-tree-fix branch from 240af17 to 909b085 Compare January 8, 2026 18:40
I've managed to find such files in the wild. There is a proper page in
the page tree. But the structure elements reference some entirely
different page, which is not referenced in /Pages...

Now in such cases we will assume, that no marked content was found.
@Eswcvlad Eswcvlad force-pushed the structure-tree-fix branch from 909b085 to 4d4130a Compare January 9, 2026 08:59
@iText-CI iText-CI closed this Jan 9, 2026
@iText-CI iText-CI deleted the structure-tree-fix branch January 9, 2026 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants