Re: [Podofo-users] podofo vs. libpoppler: What should a pdf-parsing application use?

[Craig R. <cr...@po...>]

Martin Schröder wrote:
> 2007/2/2, Craig Ringer <cr...@po...>:
>>   I'm really not sure what their best option is. I can tell them that no
>> matter which library they choose they'll probably want to use
>> PoDoFoBrowser when debugging their PDF ;-)
> 
> We already are. :-)

I'd be rather interested in your thoughts on the in-progress enhanced 
qt4 version in svn trunk, then.

I'm already planing on including the old view-by-indirect-object-no as 
well as the current catalog-rooted tree, and want to include some search 
functionality. There are a couple of known bugs - mainly that the tree 
editing still isn't right, and stream import/export isn't done yet.

Any other suggestions would be very welcome. Since you're using the app, 
  I'm sure there are other things you'd like to see improved, fixed, or 
changed, and I'm lucky enough to have a bit more time to work on it.

>> On the other hand, I don't think it has anywhere near as much developer
>> manpower behind it as libpoppler and is less widely deployed and tested.
> 
> Which is a problem. Our xpdf code just works. :-)

Speaking of your XPdf code ... it sounds like you support including a 
PDF as an image resource in another PDF. The only other app I know of 
off the top of my head that does this (well) is QuarkXPress 7.

I was wondering if there's any chance of a quick overview of how you do 
that in PdfTeX. It's something I'm *extremely* interested in supporting 
in PoDoFo once we have a content stream parser, and the more ideas I get 
and the more approaches to the issue I hear about the better.

Whatever you can tell me would be really helpful - it doesn't have to be 
a long and detailed discussion of every aspect of the process.

--
Craig Ringer