<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [TAGGEDPDF] Parse the Tagged-PDF document structure tree when present" href="https://bugs.freedesktop.org/show_bug.cgi?id=64815#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [TAGGEDPDF] Parse the Tagged-PDF document structure tree when present" href="https://bugs.freedesktop.org/show_bug.cgi?id=64815">bug 64815</a> from <a class="email" href="mailto:aperez@igalia.com" title="Adrian Perez de Castro <aperez@igalia.com>"> Adrian Perez de Castro</a> <pre>(In reply to <a href="show_bug.cgi?id=64815#c12">comment #12</a>) > Wow, [PATCH v3 2/7] Tagged-PDF: Interpret the document structure is huge :D > > I admit I haven't looked at the code in depth [...] I have uploaded an updated patch set with the outstanding issues already mentioned by Carlos Garcia Campos fixed. This updated patch set has the big patch split in four, I hope that eases the review process O:-) > [...] But I'll assume there's some tree structure parsing somewhere > because PDF are full of those trees, are we protecting against loop > in the tree somehow? I didn't see code in Poppler that would be particularly useful to parse the document structure tree. WRT loops in the structure tree, there is no protection and a malformed PDF file could potentially cause an infinite loop when parsing the tree. If I am understanding the PDF spec correctly, well-formed PDFs must not have loops in the tree. How critical would you say having protection against loops in the tree would be?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>