https://issues.apache.org/bugzilla/show_bug.cgi?id=51639
Vincent Hennebert <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Line height of <inline> |Height of <inline> element |element is not applied |is not correctly computed |correctly if the text |if the text contains white |contains spaces only. |space only OS/Version| |All --- Comment #1 from Vincent Hennebert <[email protected]> 2011-09-12 14:08:22 UTC --- Thanks for your bug report. I believe the attached FO file is rendered in accordance with the XSL-FO Recommendation. The line-height property specified on an fo:inline element has an effect only if the line-stacking-strategy on the parent fo:block has been set to 'line-height', which is not the case here. FOP does not support that strategy, but even if it did, the result would probably not be what you expect as the second fo:inline would not generate any area. Indeed, it is ending a line and since its white-space-treatment property has been left to the default value, the white space it contains will be discarded. To achieve the desired effect you probably want to play with the font-size property on the fo:inline elements, but a quick test shows that the size of the second inline will be taken into account only if it contains non-white space glyphs. Even a non-breakable space doesn't work. I think this is a bug, so I'm leaving this issue open and re-phrased accordingly. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
