> -----Original Message----- > From: J.Pietschmann [mailto:[EMAIL PROTECTED]] > 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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
