RE: AW: Latest FOP schema
Comments intermingled. > -Original Message- > From: J.U. Anderegg [mailto:[EMAIL PROTECTED]] > Sent: May 13, 2002 5:15 AM > To: [EMAIL PROTECTED] > Subject: AW: AW: Latest FOP schema > > J. Pietschmann wrote: > > are > > > Rectangular areas, perhaps indented and with border, padding > > and other individual traits, nested into a rectangular area. > > I understand setting traits, properties. How about page layout, setting > inline and baseline postitions? Does it imply a unconditional CRLF? It's not that there is a "CRLF", or anything like it, after a block, but rather that if it is succeeded by block-level siblings that they will be stacked in the block-progression-direction, so the effect will be the same. Can you be more specific with respect to the other questions? > What does the input below look look like on the page? > > > level_0_text fills to position A > > level_1_text positioned at A fills to position B > > more level_0_text positioned at B > I think the predominant opinion is (assume all of this fits on one page) - a normal block area (generated by the outer block) that contains: one or more line areas for "level_0_text fills to position A"; then a block area with one or more line areas for "level_1_text positioned at A fills to position B"; finally more line areas for "more level_0_text positioned at B". Note that if your example had been level_0_text fills to position A level_1_text positioned at A fills to position B more level_0_text positioned at B then it would still be the same. Regards, AHS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AW: Latest FOP schema
J.U. Anderegg wrote: >>From the external view means a rectangle containing formatted text, > something like a paragraph. > > o What do as children of : mean for the end user? Rectangular areas, perhaps indented and with border, padding and other individual traits, nested into a rectangular area. A user might be tempted to see them as higher level structures, like HTML DIV elements, or (nested) sections or whatever. That's not too bad but can be very misleading at times (for example, a headline probably has to be *mapped* to a fo:block too). Nested fo:blocks can be used by the transformation designer for pure technical reasons, for example to define certain properties for a longer stretch of text, without any corespondence to the structure of the original document. From this point of view, it has bee a very good idea to name a fo:block a block and not a paragraph. In the same sense, fo:table should probably have been named grid. BTW: the list related FOs are redundant, aren't they? Or am I missing something that can't be easily mapped to a table (grid)? > o What's teheffect of 's in combination with tag element TEXT like > , , , , ? There are some hassles with whitespaces. There is some similarity in handling fo:leaders to handling whitespaces. > o When is a required? If you want to put text where a block level FO is expected. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
