- From: MURAKAMI Shinyu <murakami@nadita.com>
- Date: Fri, 26 May 2000 13:48:19 +0900
- To: xsl-editors@w3.org
Dear xsl-editors, The XSL WD 2000-03-27 says: 7.13.4 "line-height" ... <space> The difference between the inline-area's actual height and the line-height's space-specifier's three lengths are each divided by 2.0 and the result is used to set three half-leading values (optimum, minimum, and maximum). ... The line-height.precedence setting can be used to control the merging of the half-leading with other spaces. The space-before and space-after space-specifiers are set to the value of the half-leading. A definition of space-specifiers, and the interaction between space-specifiers occurring in sequence are given in [4.3 Spaces and Conditionality]. If line-height is specified using <length>, <percentage>, or <number>, the formatter shall convert the single value to a space-specifier with the subfields interpreted as follows: * ... * line-height.precedence: force. * ... My question is about the default line-height.precedence: force. If a line-area have the space-before and space-after (= half-leading values) with .precedence="force", and the containing or adjacent block-area's space-before/after.precedence is not "force", then the non-forcing spaces (maybe inter-paragraph spaces) are suppressed!! Because: 4.3.1 Space-resolution Rules ... 2. If any of the remaining space-specifiers is forcing, all non-forcing space-specifiers are suppressed, and the value of each of the forcing space-specifiers is taken as its resolved value. ... Is this a spec's bug? or my misunderstanding? Thanks, MURAKAMI Shinyu
Received on Friday, 26 May 2000 00:47:17 UTC