Re: Retrieve-marker problem. Can anyone help with wrapper workaround?

2004-10-22 Thread Louis . Masters

John:

Here is my marker code (FOP 0.20.3):

!--parse out the markers--
fo:inline font-size=7pt color=black font-weight=normal
white-space-collapse=true
  xsl:for-each select=@*[starts-with(name(.),'marker__')]
fo:inlinefo:marker
marker-class-name={name(.)}xsl:value-of
select=.//fo:marker/fo:inline
  /xsl:for-each
/fo:inline
!--parse out the markers--

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

fo:block use-attribute-set=chapter-heading !-- sets 20 point, bold
font --
fo:wrapper use-attribute-set=headers-footers !-- sets 8 point light
--
fo:marker marker-class-name=chapterIntroduction/fo:marker
/fo:wrapper

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]



RE: Retrieve-marker problem. Can anyone help with wrapper workaround?

2004-10-22 Thread Andreas L. Delmelle
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]


 Here is my marker code (FOP 0.20.3):

 !--parse out the markers--
 fo:inline font-size=7pt color=black font-weight=normal
 white-space-collapse=true
   xsl:for-each select=@*[starts-with(name(.),'marker__')]
 fo:inlinefo:marker
 marker-class-name={name(.)}xsl:value-of
 select=.//fo:marker/fo:inline
   /xsl:for-each
 /fo:inline
 !--parse out the markers--

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?

2004-10-22 Thread John Burgess
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:

 fo:block
 fo:wrapper use-attribute-set=headers-footers !-- sets 8 point
 ight  --
 fo:marker marker-class-name=chapterIntroduction/fo:marker
 /fo:wrapper
 /fo:block

 fo:block use-attribute-set=chapter-heading
 Introduction
 /fo:block

 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]