J.U. Anderegg wrote:
>>From the external view <block> means a rectangle containing formatted text,
> something like a paragraph.
> o What do <fo:blocks> as children of <fo:blocks>: 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 <block>'s in combination with tag element TEXT like
> <leader>, <marker>, <inline>, <wrapper>, <basic-link>?

There are some hassles with whitespaces. There is some similarity
in handling fo:leaders to handling whitespaces.

> o When is a <block> required?

If you want to put text where a block level FO is expected.


To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to