Dear Arved, 
>-----Message d'origine-----
>De: Arved Sandstrom [mailto:[EMAIL PROTECTED]]
>Date: 26 July 2001 12:54
>Objet: Re: Marker issue
>At 12:31 PM 7/26/01 +0200, GALLO Jean-Claude wrote:
>>Does Marker and Retrieve-Marker work or not. 
>>Reading the source code, I suppose I am able to define markers, but I get
>>Null exception when Retrieve-Marker try to get markers. 
>>It seems to me that the Page object don't return the true Vector struct
>>to store markers. The one returned is always empty.
>>Is this work in progress or ami using markers in a bad manner ?
>Hi, Jean-Claude,
>Very definitely work in progress. :-) Not all of the data structures that 
>you see associated with markers are going to survive in their present form,

>Assuming that you are using the very latest CVS, would it be too much to
>if you could post an FO example that does not work for you? At the very 
>least I could explain why, and how I intend to fix it (and when).

For my actual starting point I need to report element numerotation in a
before or after area. 
I suppose this can be handle by a hastable like solution. Every time an
element is encountered, 
the value may change and is reported anywhere outside the body of the page
model (I know to do that in the body area). 

So my need is very close to the XSL spec.

<extract from W3C Candidate Recommendation 21 November 2000,
(slice6.html#fo_marker html link)>
>>6.11.3 fo:marker
>>Common Usage: 
>>The fo:marker is used in conjunction with fo:retrieve-marker to produce
running headers or footers. Typical 
>>examples include:
>>dictionary headers showing the first and last word defined on the page.
>>headers showing the page's chapter and section titles.
>>The fo:marker has to be an initial child of its parent formatting object.

Another need for me is to compute an embedded index containing, for choosen
ancestor elements, small data (eg: a title)
for each page of the PDF document the element is present. I hope Markers can
help me to do that. That's like a Table of Content, but the table shows all
the pages of the document and the elements which are painted on each page
(generally the first one which appear on top of the page body). The table
contains as many rows as the document has pages. 

After doing that, I need to compute what I call a String page number
(different from physic page number, the one displayed by Acroread) which
behave like a chapter or subchapter numerotation (page : III.1.a, 
or page : Also I hope Markers behaviour will help us to support
such numerotation. So I will be able to build table (of content or indexes)
containing the logical numerotation of the pages instead of the physical one
(actual one). Is this last need seems to be outside XSL specification ?

>Arved Sandstrom
>Fairly Senior Software Type
>e-plicity (
>Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, email: [EMAIL PROTECTED]

Thanks to your answer.

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

Reply via email to