FreeLists / open-beos-printing / [open-beos-printing] Re: Next PDF Writer Release

[Michael Pfeiffer <michael.pfeiffer@xxxxxxxxx>]

>> Any idea how to handle internal hyperlinks or how to detect 
>bookmarks. 
>
>Internal hyperlinks willl be very hard to detect, I guess.

And also to decide what is an anchor and what a link.
(ie. figure description or reference to figure)

>As they can jumb forward or backward in pages, it'll need to do a first 
>pass 
>over all pages, just to build a sort of index (title, page, position in 
>page=3F) in memory, 

Ok, the extra pass would be no problem, if pattern support is enabled
one pass is already made, before the actual PDF generation starts.

BTW patterns in PDFs do not crash Acrobat Reader any more!
So it will be enabled by default.

[implementation detail:
PDF allows two kind of patterns, one that take the current
active stroke and fill colors and one that define them inside
of the pattern definition.

As the pattern used by PDF Writer consists only of a bitmap,
I thought I could use the first kind, because the pattern
does not stroke or fill anything. Don't know why but this
crashes Acrobat Reader.
]

>Yes, that's a pragmatic way to do it. 
>No better one come to my mind, but I'm not a natural text parsing 
>expert.
>Maybe you could find on Net some clever solution, I'll bet some open 
>source 
>projects here and there have implemented a text auto-indexer or auto-
>summary maker.
>
>BTW, if you add this first pass thing, you could count the total 
>BPicture(s) operand for all pages too, 
>which could make the progress status window even more accurate... most 
>accurate, in fact.

Thanks for your feedback, this will help a lot!

- Michael