You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "J.Pietschmann" <j3...@yahoo.de> on 2002/07/24 04:11:34 UTC
Flow and region-body
Hi,
I'm about to remove some hackery from the maintenance
branch, as part of a general cleanup.
There is a comment in Flow.java (soon/now AbstractFlow.java)
// flow is *always* laid out into a BodyAreaContainer
I was not able to find support for this directly in the
spec, although I think this is reasonable.
Can anybody comment on this? I nail this down for now,
apparently this is how FOP currently works anyway.
Actually, routing static-content into a body region
causes FOP to loop, and if neither the flow nor static
content go into the body a "no flow found" is logged/thrown.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Table Sectioning
Posted by saravana kumar <sa...@yahoo.com>.
Hi Developers, I'm struck in formatting the table. pls
help me out. whts the equivalent xsl fo syntax for
<th colspan> and <th rowspan>.
i want my table in the following format.
|--------------------------------|
| | Status | Effect of |
|Total|--------------| Deduction |
| | Paid | UnPaid| |
|--------------------------------|
| |
| |
| |
| |
| |
|--------------------------------|
Thnx in Advance,
Saran.
__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: Flow and region-body
Posted by Victor Mote <vi...@outfitr.com>.
J.Pietschmann wrote:
> There is a comment in Flow.java (soon/now AbstractFlow.java)
> // flow is *always* laid out into a BodyAreaContainer
>
> I was not able to find support for this directly in the
> spec, although I think this is reasonable.
>
> Can anybody comment on this?
>
(Inferring from layout/Page.java in the maintenance branch that
BodyAreaContainer is used for the fo:region-body object, and that
AreaContainer is used for the other regions). The following sections of the
standard seem to at least imply a contrary conclusion:
6.4.13, 1st pointer: "Typically, for paged media, the areas returned by the
fo:flow formatting object in a fo:page-sequence are made to be descendants
of a sequence of region-reference-areas that correspond to the region-body.
These region-reference-areas are all area descendants of page-areas for
which the page-master included an fo:region-body. If the fo:flow flow is
assigned to some other region, then the areas returned by the fo:flow are
constrained to be descendants of region-reference-areas generated using the
assigned region-master."
7.25.5, para before last pointer: "The flow-name and region-name are used to
assign the flow's content (or static-content's content) to a specific region
or series of regions in the layout. In XSL this is done by specifying the
name of the target region as the flow-name. (For example, text placed in the
region-body would specify flow-name="xsl-region-body".)
>From these two sections, my understanding of the fo:static-content object is
that it is a sort of specialized fo:flow object, a subclass if you will (or
perhaps each is a subclass of some higher abstraction). They each have
exactly one property, "flow-name", and it appears that either should be able
to point to any region within the page-sequence-master object.
I would interpret the code comment to apply to the FOP implementation, not
the standard. I agree that this limitation is reasonable, but perhaps it
should be documented, and perhaps should include appropriate exceptions. Of
course, if it doesn't cost much, I suppose it would be better to comply with
the standard.
Victor Mote (mailto:vic@outfitr.com)
Enterprise Outfitters (www.outfitr.com)
2025 Eddington Way
Colorado Springs, Colorado 80916
Voice 719-622-0650, Fax 720-293-0044
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: Flow and region-body
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
> -----Original Message-----
> From: J.Pietschmann [mailto:j3322ptm@yahoo.de]
> Sent: July 23, 2002 11:12 PM
> To: fop dev
> Subject: Flow and region-body
>
>
> Hi,
> I'm about to remove some hackery from the maintenance
> branch, as part of a general cleanup.
>
> There is a comment in Flow.java (soon/now AbstractFlow.java)
> // flow is *always* laid out into a BodyAreaContainer
>
> I was not able to find support for this directly in the
> spec, although I think this is reasonable.
>
> Can anybody comment on this? I nail this down for now,
> apparently this is how FOP currently works anyway.
> Actually, routing static-content into a body region
> causes FOP to loop, and if neither the flow nor static
> content go into the body a "no flow found" is logged/thrown.
>
> J.Pietschmann
I believe I had something to do with this. :-) Basically, you're right -
there is no direct support in the spec for the assertion that fo:flow
content must go into fo:region-body child areas, and fo:static-contents go
into the 4 other regions' child areas.
I think it is clearly the intent of XSL 1.0, however, that fo:flow content
go into fo:region-body, and fo:static-content go into the other 4 regions.
After all, it is impossible to look at the specialisation of fo:region-body
and not realise that it occupies a special position in the region pantheon.
Down the road, with XSL 2.0, we may see some generalisation of flows of the
fo:flow type, and have more flexibility than just one single fo:region-body.
Regards,
Arved Sandstrom
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org