https://issues.apache.org/bugzilla/show_bug.cgi?id=51993

Glenn Adams <gad...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #9 from Glenn Adams <gad...@apache.org> 2012-04-10 16:34:04 UTC ---
(In reply to comment #8)
> I see. But I didn't specify the line-height or the font-size of the block
> element. FOP assumed a "normal" value and this value took precedence over the
> natural line-height of a 7pt text, which I indeed specified in the inline
> element. I just think it might be confusing for the end-user to have an
> implicit value outweighing a value which was explicitly set.
> 
> In fact, browsers seem to calculate line-height for each line individually
> based on the maximum font-size of the line, which sounds reasonable. FOP seems
> to do the same in most cases. However, assuming a default line-height for the
> block seems to be causing inconsistent results.

Keep in mind the semantics of the line-stacking-strategy property, which
defaults to max-height and not line-height. The CSS semantics default to
line-height, not max-height, so this is a difference between XSL-FO and CSS.
Further, at this time, FOP does not support the line-height value. That is, FOP
at present supports only max-height and font-height strategies. In the former
case, the maximum line rectangle applies (i.e., the maximum needed to contain
the line's inline areas) in the latter case, the text-altitude/depth properties
(or font metrics) apply, where the font/font-size that applies to the parent
block is what determines the font metric flavors of altitude/default.

See XSL-FO Section 4.5 Line Areas [1] for more detail.

Also, in case of max-height and font-height strategy, the space-{before,after}
of the generated line areas is set to the half leading trait value [2].

My conclusion is that the current behavior is not a bug.

[1] http://www.w3.org/TR/2006/REC-xsl11-20061205/#area-line
[2] http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_block

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to