My apologies. I had confused text-indent with start-indent.
I guess FOP has a bug here. The work around appears to be not having text
after a nested block.
Jay Bryant
Bryant Communication Services
(presently consulting at Synergistic Solution Technologies)
"Puppala, Kumar (LNG-DAY)" <[EMAIL PROTECTED]>
03/16/2005 12:49 PM
Please respond to
fop-users@xmlgraphics.apache.org
To
"'fop-users@xmlgraphics.apache.org'" <fop-users@xmlgraphics.apache.org>
cc
Subject
RE: text-indent issue
I totally agree that all the PCDATA is owned by the outer fo:block and
hence
when it applies the text-indent property, it should apply only to the
first
line in that block. The spec. for text-indent says:
"This property specifies the indentation of the first
line of text
in a block. More precisely, it specifies the indentation of
the first
box that flows into the block's first line box. The box is
indented with
respect to the left (or right, for right-to-left layout) edge of the line
box. User agents should render this indentation as blank space."
Any thoughts or comments?
Thanks,
Kumar Puppala
-----Original Message-----
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 16, 2005 1:46 PM
To: fop-users@xmlgraphics.apache.org
Subject: Re: text-indent issue
--- "Puppala, Kumar (LNG-DAY)"
<[EMAIL PROTECTED]> wrote:
> If I have text-indent specified on an fo:block and
> if I have a nested block
> within this, the text following this nested block is
> indented as well. For
> example:
>
>
>
> <fo:block text-indent="5">
>
> This is just for testing purpose and this line
> will be indented.
>
> <fo:block>this is the nested block </fo:block>
>
> The text following the nested block is indented
> as well...not sure if
> this is as per spec. since it does not happen in
> other renderers.
>
> </fo:block>
>
>
> In the above example, the text following the second
> block should not be
> indented since text-indent applies only to the first
> line of that block and
> not to any subsequent text in that block.
I really don't think so. All of the PCDATA in your
example is owned by that outer fo:block, and subject
to its properties.
> Is there a
> way to get around this
> issue by specifying some property on the first
> block? I appreciate your
> help.
>
De-nest your fo:blocks?
Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
