Hi, The current implementation of PdfPagesTree::GetPageNode() has a questionable branch for nested kids arrays:
// We have to traverse the tree
while( it != rKidsArray.end() )
{
if( (*it).IsArray() )
{ // Fixes PDFs broken by having trees with arrays nested once
...
}
Does anyone know what the relevance of nested kids arrays is??? Where do such
broken PDFs occur and why should they be handled by PoDoFo? This is not in
accordance with the PDF spec. And I have not found a single PDF tool (including
Adobe products) which handles such broken PDFs, yet.
I think this case is meant to handle PDFs containing /Pages nodes of this form:
3 0 obj<</Type/Pages/Count 3/Kids[[ 8 0 R 10 0 R 12 0 R]]>>
endobj
However, if there is no really good reason for it, this branch should be
completely removed from GetPageNode() to open the way for further improvements
of the current code.
Best regards,
Amin
signature.asc
Description: Message signed with OpenPGP
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
