On Wed, Jul 2, 2014 at 1:47 PM, Mark Rogers <mark.rog...@powermapper.com>
wrote:
> Hi
>
>
>
> I finally had a chance to look at this – looks like there’s a
> long-standing bug in PdfParser::ReadXRefStreamContents
>
>
>
> Once called, the method assumes that all cross reference information found
> by following the “Prev” keys is stored as cross ref streams (XRefStm). The
> IRS test documents uses a mix of old style cross-ref tables (xref) and
> cross ref streams (XRefStm) in the Prev chain. I’m guessing they’ve been
> through a couple of different PDF editors.
>
>
>
> PdfTokenizer::GetNextNumber() is throwing an error because the next token
> is “xref” instead of number when it reads an xref table it assumes is an
> XRefStm
>
>
>
> Given that fixing this might uncover more problems, and it’s very close to
> release day, I’d suggest keeping r1648 for the moment and I’ll submit a
> patch after the release.
>
>
>
> Does that sound ok?
>
>
>
> Cheers
>
> Mark
>
>
>
>
+1 That sounds like a very sensible plan to me!
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users
