Made a little more progress yesterday. I do not think it will be possible to
simply search for control characters in the table stream, it is going to be
necessary to interrogate the file information block for the offset to the
list of bookmarks. That is not as scary as it sounds because a lot of the
work has already been done in the FIBFieldHandler class. I think I am going
to hack this by adding an associative list that allows me to link the name
or ID number of the offset field to the number of bytes. Next, I need to
work out all of the entities that can appear in the table stream before the
bookmarks, get the offset for each along with the length, add all of this
together and hopefuly arrive at the offset for the bookmarks. Last night, I
had the chance to check that by simply accessing the field that relates to
the offset for the bookmarks was not enough; it gave me an offset of
something like 50 bytes whereas I know from mapping the table stream it
should be something like 2000.

Cannot promise to work on the problem today - I have commitments both during
the day and evening - but will post again if I make any progress.

Yours

Mark B.


Fernando Antonio Prado wrote:
> 
> 
> Hi there. I've just subscribed here so this is my first email. I searched
> the POI site but couldn't find the answer to may problem. I've just
> downloaded the most recent version of HWPF and I1d like to know if there's
> any way I can get the bookmarks of a word document. I'll be very pleased
> with your help.. Thx!!
> 
> _________________________________________________________________
> Com o Windows Live, vocĂȘ pode organizar, editar e compartilhar suas fotos.
> http://www.microsoft.com/brasil/windows/windowslive/products/photo-gallery-edit.aspx
> 

-- 
View this message in context: 
http://www.nabble.com/Bookmarks-on-word-documents-tp24573916p24600779.html
Sent from the POI - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to