On Feb 22, 2007, at 13:17, Luca Furini wrote: Hi Luca,
Concerning the following:
- there are a few space-before and space-after defined using just the .optimum component; I was wondering if this is correct (isn't the default value for .maximum and .optimum 0 points?)
You are correct about the initial values for the other components, but it is also correct to use only the .optimum component. The answer is in the Rec's definition of the compound <space> datatype (XSL 1.1 - 5.11)
"A compound datatype, with components: minimum, optimum, maximum, precedence, and conditionality. ... If 'minimum' is greater than optimum, it will be treated as if it had been set to 'optimum'. If 'maximum' is less than optimum, it will be treated as if it had been set to 'optimum'."
Specifying only .optimum should lead to a resolved min=opt=max.
- there is always an empty block at the end of the foontote-body; at the moment it does not have any effect on the output, so they could maybe be avoided
In this case, I'd say "Definitely to be avoided", and as mentioned recently in another thread, using empty blocks for no other reason than to force a line-break should be avoided whenever possible, due to the overhead of creating a corresponding Block and BlockLayoutManager. Using linefeed-treatment="preserve" is much more efficient. Too bad it has such weird effects in combination with hyphenate="true" :(
Cheers, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
