xmlgraphics-fop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Xmlgraphics-fop Wiki] Update of "Troubleshooting/CommonLogMessages" by JeremiasMaerki
Date Sun, 13 Jul 2008 09:48:57 GMT
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 JeremiasMaerki:
http://wiki.apache.org/xmlgraphics-fop/Troubleshooting/CommonLogMessages

The comment on the change is:
Explaining two more messages.

------------------------------------------------------------------------------
  
  This happens if you use the column-number property when defining table columns and you just
specify the columns for columns 1 and 3 but not 2.
  
+ === Message ===
+ 
+ {{{
+ Ascender and descender together are larger than the em box. This could lead to a wrong baseline
placement in Apache FOP.
+ }}}
+ 
+ ==== 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.
+ 
+ Normally, this error can be ignored as it mostly happens on special fonts which are discovered
by auto-detection which are seldomly used.
+ 
+ === Message ===
+ 
+ {{{
+ Adjusting end-indent based on overconstrained geometry rules for fo:table.
+ }}}
+ 
+ ==== 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:
+ 
+ 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".
+ 
+ 2cm + 9cm = 11cm (which is larger than the available 10cm)
+ 
+ Result: end-indent is adjusted to "-1cm", so "2cm - 1cm + 9cm = 10cm". The table extends
beyond the right edge of the available area.
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org


Mime
View raw message