Re: Retrieve-marker problem. Can anyone help with wrapper workaround?
Andreas Thanks very much! Putting the marker in a wrapper in an otherwise empty block stopped it appearing, and had it correctly formatted in the footer. I've looked again at what was happening before and you're quite right - the Chapter didn't appear. I'm afraid I had misunderstood fo:marker and assumed it took a copy of the text inside that would also be shown in the flow and that was what I saw, rather than what was actually in front of my eyes. My apologies, and once again thanks very much indeed! John - Original Message - From: "Andreas L. Delmelle" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 22, 2004 4:41 PM Subject: RE: Retrieve-marker problem. Can anyone help with wrapper workaround? > > -Original Message- > > From: John Burgess [mailto:[EMAIL PROTECTED] > > > Hi John, > > I know it sounds like a bit of a pain, but try to use this: > > > > Introduction > > > > > Introduction > > > Notice that the actual title appears in two places (under the > fo:marker/fo:wrapper, and once again in a block *after* the wrapper) > > I don't really see how your problem could arise though... IIC, then the text > placed under fo:marker shouldn't be visible anywhere except when there is a > corresponding fo:retrieve-marker that retrieves it --at least that's the way > it currently works for me, and how it's defined in the spec: > > "The fo:marker does not directly produce any area. Its children may be > retrieved and formatted from within an fo:static-content, using an > fo:retrieve-marker..." > > Currently, FOP maintenance version only has a problem with the '...and > formatted...' part. The rest seems to be handled quite OK. > > Greetz, > > Andreas > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.776 / Virus Database: 523 - Release Date: 16/10/04 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Retrieve-marker problem. Can anyone help with wrapper workaround?
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>
> Here is my marker code (FOP 0.20.3):
>
>
> white-space-collapse="true">
>
> marker-class-name="{name(.)}"> select="."/>
>
>
>
This solution will also do the trick, but...
Be careful with fo:inline's. As I recall, in FOP 0.20.X fo:wrapper's still
treated the same way as fo:inline, but according to the spec fo:inline
generates areas of itself --thus an fo:wrapper seems to be more appropriate
here (well actually... 'nothing' seems to be even more appropriate, but you
can't win 'em all ;-) )
Greetz,
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Retrieve-marker problem. Can anyone help with wrapper workaround?
> -Original Message- > From: John Burgess [mailto:[EMAIL PROTECTED] Hi John, I know it sounds like a bit of a pain, but try to use this: Introduction Introduction Notice that the actual title appears in two places (under the fo:marker/fo:wrapper, and once again in a block *after* the wrapper) I don't really see how your problem could arise though... IIC, then the text placed under fo:marker shouldn't be visible anywhere except when there is a corresponding fo:retrieve-marker that retrieves it --at least that's the way it currently works for me, and how it's defined in the spec: "The fo:marker does not directly produce any area. Its children may be retrieved and formatted from within an fo:static-content, using an fo:retrieve-marker..." Currently, FOP maintenance version only has a problem with the '...and formatted...' part. The rest seems to be handled quite OK. Greetz, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Retrieve-marker problem. Can anyone help with wrapper workaround?
John: Here is my marker code (FOP 0.20.3): The inner inline was to "fix" the "fo:marker must be an initial child,and 'marker-class-name' must be unique for same parent" messages. The "for" loop is because I have multiple dynamically generated markers in a given area. Hope this helps. -Lou |-+> | | "John Burgess" | | | <[EMAIL PROTECTED]| | | isions.com> | | || | | 10/22/2004 05:13 | | | Please respond to| | | fop-user | | || |-+> >---| | | |To: <[EMAIL PROTECTED]> | |cc: | |Subject: Retrieve-marker problem. Can anyone help with wrapper workaround?| >---| I am trying to use maker and retrieve-marker to put the title of the current chapter into the header of my documents. I have this working BUT the formatting of the chapter title in the header is the same as where the marker is i.e. Large and Bold, appropriately for the title of a chapter bit not for a running header. I know this is a known problem with fop (I am using 0.20.5 by the way). However, in the mailing list archive I saw amongst the messages dealing with this problem one from Andreas L. Delmelle saying: Oh, another detail: there's a nasty bug with markers that renders them with the same properties as the region/block where they are defined, so to make it work correctly, you have to add an fo:wrapper around the marker to set the font-size/-weight etc. to the same values they have in the static content... For more info: check the examples for markers that came with FOP (FOP_HOME/examples/fo/markers) --- I think I have probably misunderstood what Andreas means. What I did was to have Introduction But while that meant the header was in the correct font etc., the chapter title was then very small. Is there a workaround for this situation? Best Wishes John Burgess Risk Decisions Limited T: 01865 718666 F: 01865 718600 [EMAIL PROTECTED] http://www.riskdecisions.com/ --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.776 / Virus Database: 523 - Release Date: 16/10/04 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Retrieve-marker problem. Can anyone help with wrapper workaround?
I am trying to use maker and retrieve-marker to put the title of the current chapter into the header of my documents. I have this working BUT the formatting of the chapter title in the header is the same as where the marker is i.e. Large and Bold, appropriately for the title of a chapter bit not for a running header. I know this is a known problem with fop (I am using 0.20.5 by the way). However, in the mailing list archive I saw amongst the messages dealing with this problem one from Andreas L. Delmelle saying: Oh, another detail: there's a nasty bug with markers that renders them withthe same properties as the region/block where they are defined, so to makeit work correctly, you have to add an fo:wrapper around the marker to setthe font-size/-weight etc. to the same values they have in the staticcontent...For more info: check the examples for markers that came with FOP(FOP_HOME/examples/fo/markers)--- I think I have probably misunderstood what Andreas means. What I did was to have Introduction But while that meant the header was in the correct font etc., the chapter title was then very small. Is there a workaround for this situation? Best WishesJohn BurgessRisk Decisions LimitedT: 01865 718666F: 01865 718600[EMAIL PROTECTED]http://www.riskdecisions.com/ ---Outgoing mail is certified Virus Free.Checked by AVG anti-virus system (http://www.grisoft.com).Version: 6.0.776 / Virus Database: 523 - Release Date: 16/10/04
Re: Marker problem
Thanks for your response. The size of the content was the first thing I thought of. I increased it to a ridiculously high size and I got the same results except my body was halfway down the page. Anyway, it fit on the first two pages. I only get the problem when my table is larger than one page. Right now I have 2 tables. The first one fits on one page. the second table starts one page two and flows into page three. It fails on page three. Keiron Liddle wrote: Hi, The messages about the marker not being added could be due to some minor error like the marker is not the first child of the block or there is whitespace before the marker (markers haven't been fully implemented yet). The message "Some static content could not fit in the area." indicates that something could not fit into the static area on page three. This may be the real reason that you do not see the marker. You need to increase the size of the static area or reduce the size of the contents. Fop does not currently handle this properly, it should (by default) put all the contents there and clip so you only see the specified area. On 2001.12.05 17:06 Steven Ford wrote: I am using a marker to change the header each time there is a new 'Center' in the data. I get the following error: marker cannot be added to '[EMAIL PROTECTED]'marker cannot be added to '[EMAIL PROTECTED]' [1] [2] [3Warning: Some static content could not fit in the area.] I retrieve the marker in the xsl-region-before. It shows up fine in the first and second pages but fails in the third. Where it fails is when a table spans over into a new page. I am displaying data grouped by "Center". each center is in a table which is in it's own block. At the top of the block I have: Center: 201445 - Clinical Chemistry I get 3 pages. the first page is fine, the center has a few rows and fits on one page. The next center starts on a new page (I use ). page 2 is fine but page 3 is a continuation of the block & table that started on page 2 and I get the above error. Does anyone have an idea what is causing this? PS - If you can't tell by my question I am new to XSL-FO
Re: Marker problem
Hi, The messages about the marker not being added could be due to some minor error like the marker is not the first child of the block or there is whitespace before the marker (markers haven't been fully implemented yet). The message "Some static content could not fit in the area." indicates that something could not fit into the static area on page three. This may be the real reason that you do not see the marker. You need to increase the size of the static area or reduce the size of the contents. Fop does not currently handle this properly, it should (by default) put all the contents there and clip so you only see the specified area. On 2001.12.05 17:06 Steven Ford wrote: I am using a marker to change the header each time there is a new 'Center' in the data. I get the following error: marker cannot be added to '[EMAIL PROTECTED]'marker cannot be added to '[EMAIL PROTECTED]' [1] [2] [3Warning: Some static content could not fit in the area.] I retrieve the marker in the xsl-region-before. It shows up fine in the first and second pages but fails in the third. Where it fails is when a table spans over into a new page. I am displaying data grouped by "Center". each center is in a table which is in it's own block. At the top of the block I have: Center: 201445 - Clinical Chemistry I get 3 pages. the first page is fine, the center has a few rows and fits on one page. The next center starts on a new page (I use ). page 2 is fine but page 3 is a continuation of the block & table that started on page 2 and I get the above error. Does anyone have an idea what is causing this? PS - If you can't tell by my question I am new to XSL-FO
Marker problem
I am using a marker to change the header each time there is a new 'Center' in the data. I get the following error: marker cannot be added to '[EMAIL PROTECTED]'marker cannot be added to '[EMAIL PROTECTED]' [1] [2] [3Warning: Some static content could not fit in the area.] I retrieve the marker in the xsl-region-before. It shows up fine in the first and second pages but fails in the third. Where it fails is when a table spans over into a new page. I am displaying data grouped by "Center". each center is in a table which is in it's own block. At the top of the block I have: Center: 201445 - Clinical Chemistry I get 3 pages. the first page is fine, the center has a few rows and fits on one page. The next center starts on a new page (I use ). page 2 is fine but page 3 is a continuation of the block & table that started on page 2 and I get the above error. Does anyone have an idea what is causing this? PS - If you can't tell by my question I am new to XSL-FO
