You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Bart Locanthi <ba...@sabl.com> on 2002/02/27 00:25:51 UTC

markers

does fop support markers? i'm having trouble getting them to work.

my input looks like
...
<fo:flow>
  <fo:block>
    <fo:block>
      <fo:marker marker-class-name="chap">chapter one</fo:marker>
      ...
    </fo:block>
  </fo:block>
  <fo:block>
    <fo:block>
      <fo:marker marker-class-name="chap">chapter two</fo:marker>
...

note that the markers share a common great-grandparent.

the error message i get from any fop-0.20.[23] is:

[ERROR]: fo:marker must be an initial child,and 'marker-class-name' must 
be unique for same parent.

i'm following all the rules, i think, but no joy.

sounds like a simple misconception on my part but i'm stumped.


RE: markers

Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
Interesting...I didn't realise that that much was still functional. :-) I
will have to revisit and see what the scope of potential fixes is.

AHS

-----Original Message-----
From: Chuck Paussa [mailto:Chuck.Paussa@systems.dhl.com]
Sent: February 27, 2002 12:48 PM
To: fop-user@xml.apache.org
Subject: Re: markers


Hi Bart,

I've done some playing with markers also and gotten them to work pretty
well. One of the things I've noticed is that FOP complains mightily
about both "fo:marker must be an initial child"" and "marker-class-name'
must be unique for same parent."but, they are recoverable errors and can
be ignored.

Here's an XML and XSL to demonstrate the capabilities. Notice that I
place a marker at the beginning and end of each marked block (That's
strictly illegal! But it works) I also have placed an "x" in the illegal
marker contents so you can see the illegal retrieval. I do that so that
the functions first-including-carryover and last-ending-within-page will
work. Arved did a great job of implementing markers, you just have to
break the rules for now (and be prepared to unbreak the rules  when FOP
has a correct implementation)

fop -xsl dictionary.xsl -xml dictionary.xml -pdf dictionary.pdf

Chuck


Re: markers

Posted by Chuck Paussa <Ch...@systems.dhl.com>.
Hi Bart,

I've done some playing with markers also and gotten them to work pretty 
well. One of the things I've noticed is that FOP complains mightily 
about both "fo:marker must be an initial child"" and "marker-class-name' 
must be unique for same parent."but, they are recoverable errors and can 
be ignored.

Here's an XML and XSL to demonstrate the capabilities. Notice that I 
place a marker at the beginning and end of each marked block (That's 
strictly illegal! But it works) I also have placed an "x" in the illegal 
marker contents so you can see the illegal retrieval. I do that so that 
the functions first-including-carryover and last-ending-within-page will 
work. Arved did a great job of implementing markers, you just have to 
break the rules for now (and be prepared to unbreak the rules  when FOP 
has a correct implementation)

fop -xsl dictionary.xsl -xml dictionary.xml -pdf dictionary.pdf

Chuck

Bart Locanthi wrote:

> does fop support markers? i'm having trouble getting them to work.
>
> my input looks like
> ...
> <fo:flow>
>  <fo:block>
>    <fo:block>
>      <fo:marker marker-class-name="chap">chapter one</fo:marker>
>      ...
>    </fo:block>
>  </fo:block>
>  <fo:block>
>    <fo:block>
>      <fo:marker marker-class-name="chap">chapter two</fo:marker>
> ...
>
> note that the markers share a common great-grandparent.
>
> the error message i get from any fop-0.20.[23] is:
>
> [ERROR]: fo:marker must be an initial child,and 'marker-class-name' 
> must be unique for same parent.
>
> i'm following all the rules, i think, but no joy.
>
> sounds like a simple misconception on my part but i'm stumped.
>



Re: markers

Posted by Etwin van Krimpen <ev...@ambrac.nl>.
Arved,

I would appreciate that. One of the reasons to turn to (at this moment
evaluation-version of) XEP is that XEP works fine with marker-retrieve
marker.

Regards, Etwin

----- Original Message -----
From: "Arved Sandstrom" <Ar...@chebucto.ns.ca>
To: <fo...@xml.apache.org>
Sent: Wednesday, February 27, 2002 12:41 AM
Subject: RE: markers


> Hi, Bart
>
> I took markers up to a certain point last summer. I didn't have the
property
> re-parenting happening yet, but in terms of retrieving the right marker
> probably about half the retrieve-position/retrieve-boundary combos were
> already functional. The example file glossary.xml stems from that period.
>
> We had an injection of code just about that time that was generally held
to
> be higher priority, including by me, and this broke the partial marker
> support. I don't think anything has happened since, and so you are
probably
> seeing the effects of this, not doing anything wrong in your FO.
>
> I am loathe to invest any effort in marker support in the maintenance
> branch, unless Karen and/or Keiron were to indicate that they do not
expect
> functional markers in the rewrite for at least another 3 months (by which
I
> mean I'd be happy to actually write that code if they indicate that I
could
> reasonably expect to be doing so within 3 months). If it looks like there
> won't be any markers in the rewrite for quite a while then I'd be happy to
> look at getting them back into the maintenance branch because it wouldn't
be
> wasted effort.
>
> Regards,
> Arved Sandstrom
>
> -----Original Message-----
> From: Bart Locanthi [mailto:bart@sabl.com]
> Sent: February 26, 2002 7:26 PM
> To: fop-user@xml.apache.org
> Subject: markers
>
>
> does fop support markers? i'm having trouble getting them to work.
>
> my input looks like
> ...
> <fo:flow>
>   <fo:block>
>     <fo:block>
>       <fo:marker marker-class-name="chap">chapter one</fo:marker>
>       ...
>     </fo:block>
>   </fo:block>
>   <fo:block>
>     <fo:block>
>       <fo:marker marker-class-name="chap">chapter two</fo:marker>
> ...
>
> note that the markers share a common great-grandparent.
>
> the error message i get from any fop-0.20.[23] is:
>
> [ERROR]: fo:marker must be an initial child,and 'marker-class-name' must
> be unique for same parent.
>
> i'm following all the rules, i think, but no joy.
>
> sounds like a simple misconception on my part but i'm stumped.
>


RE: markers

Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
Hi, Bart

I took markers up to a certain point last summer. I didn't have the property
re-parenting happening yet, but in terms of retrieving the right marker
probably about half the retrieve-position/retrieve-boundary combos were
already functional. The example file glossary.xml stems from that period.

We had an injection of code just about that time that was generally held to
be higher priority, including by me, and this broke the partial marker
support. I don't think anything has happened since, and so you are probably
seeing the effects of this, not doing anything wrong in your FO.

I am loathe to invest any effort in marker support in the maintenance
branch, unless Karen and/or Keiron were to indicate that they do not expect
functional markers in the rewrite for at least another 3 months (by which I
mean I'd be happy to actually write that code if they indicate that I could
reasonably expect to be doing so within 3 months). If it looks like there
won't be any markers in the rewrite for quite a while then I'd be happy to
look at getting them back into the maintenance branch because it wouldn't be
wasted effort.

Regards,
Arved Sandstrom

-----Original Message-----
From: Bart Locanthi [mailto:bart@sabl.com]
Sent: February 26, 2002 7:26 PM
To: fop-user@xml.apache.org
Subject: markers


does fop support markers? i'm having trouble getting them to work.

my input looks like
...
<fo:flow>
  <fo:block>
    <fo:block>
      <fo:marker marker-class-name="chap">chapter one</fo:marker>
      ...
    </fo:block>
  </fo:block>
  <fo:block>
    <fo:block>
      <fo:marker marker-class-name="chap">chapter two</fo:marker>
...

note that the markers share a common great-grandparent.

the error message i get from any fop-0.20.[23] is:

[ERROR]: fo:marker must be an initial child,and 'marker-class-name' must
be unique for same parent.

i'm following all the rules, i think, but no joy.

sounds like a simple misconception on my part but i'm stumped.