Comment 13 for bug 291416

Paolo, I think that's a different issue than what's being discussed here.

There problem here is that when a PDF is imported, the XML structure is severely nested. The tree structure goes something like 1,200 or 2,000 elements deep. This bumps up against an arbitrary limit inside the XML parser, that only allows structures 1,024 elements deep.

If you examine the resulting XML after a PDF import, there is no need for the structure to be so deep. I'm guessing there's probably a simple fix in the PDF import logic. Like there's a loop that's adding subelements instead of sibling elements.