On Sun, 2017-12-17 at 17:29 +0100, Michal Sudolsky wrote:
> I changed only this one line:
>
> - m_pNext = new PdfOutlineItem( pObj, NULL, this );
> + m_pNext = new PdfOutlineItem( pObj, m_pParentOutline, this
> );
>
Hi,
this is not a patch, but okay. I took a file without outlines and one
with outlines and used podofomerge to merge them. The resulting PDF
file had those outlines, recognized by an acrobat reader and by evince,
and both were able to work with them. I didn't do your suggested
change, because I wanted to test it first. If you've any test .pdf
files where it doesn't work, then feel free to share them (mine were
generated by PoDoFo itself).
> Seems this is already fixed in newest source at svn, I have 0.9.5
Right, the development version contains some fixes. I made the above
test with the svn checkout at revision 1863.
I suggest you to use the svn checkout, which will save your time, and
it also makes it super-simple to provide usable patches, like when you:
$ cd podofo-trunk-checkout/
$ svn diff >../podofo.patch
The default `svn diff` didn't use the -p parameter of the diff command,
which is also useful when applying older patches, but I do not know the
current state, maybe they begun to use it. It's not a big deal, just a
nice to have part of the patch. They do provide unified (-u) patches,
which contain some context of the change.
Bye,
zyx
------------------------------------------------------------------------------
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
