Dear Wiki user, You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" for change notification.
The following page has been changed by VincentHennebert: http://wiki.apache.org/xmlgraphics-fop/Troubleshooting/CommonLogMessages The comment on the change is: Fixed typos ------------------------------------------------------------------------------ ==== Explanation ==== - The "em box" is the "normal" bounding box in which all glyphs of a font fit. That doesn't mean that parts of a glyph cannot extend beyond that box in extreme cases, especially if accents gets stacked. The "ascender" is the "normal" value by which a font ascends beyond the baseline, and the "descender" is the "normal" value by which a font descends under the baseline. Those two values added together normally make up the height of a line of text for a particular font at the design size of the font. The em box's height is normally equal to the this line height. Now, not all !TrueType/!OpenType fonts provide the same metrics information (or the same quality of information). During development it was noticed that there could be placement errors if the em box, the ascender and descender don't match. + The "em box" is the "normal" bounding box in which all glyphs of a font fit. That doesn't mean that parts of a glyph cannot extend beyond that box in extreme cases, especially if accents gets stacked. The "ascender" is the "normal" value by which a font ascends beyond the baseline, and the "descender" is the "normal" value by which a font descends under the baseline. Those two values added together normally make up the height of a line of text for a particular font at the design size of the font. The em box's height is normally equal to this line height. Now, not all !TrueType/!OpenType fonts provide the same metrics information (or the same quality of information). During development it was noticed that there could be placement errors if the em box, the ascender and descender don't match. - Normally, this error can be ignored as it mostly happens on special fonts which are discovered by auto-detection which are seldomly used. + Normally, this error can be ignored as it mostly happens on special fonts which are discovered by auto-detection and are rarely used. === Message === @@ -266, +266 @@ ==== Explanation ==== - This is triggered when the when the rule in [http://www.w3.org/TR/xsl11/#overcons_geom XSL 1.1, 5.3.4 Overconstrained Geometry] is triggered. This can happen on a fo:table when the table width is larger than the available space in inline-progression-direction. An example: + This is triggered when the rule in [http://www.w3.org/TR/xsl11/#overcons_geom XSL 1.1, 5.3.4 Overconstrained Geometry] is triggered. This can happen on a fo:table when the table width is larger than the available space in inline-progression-direction. An example: Assume the region-body has a width of 10cm. start-indent has been set to "2cm" and a table was added with a width of "9cm". --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
