Added 'bogus' function definition to illustrate handling of short
authorTony Graham
Tue, 29 Jul 2014 00:33:22 +0100
changeset 55 873cf39a5e9c
parent 54 3fe35c97a8a8
child 56 b184e200b875
Added 'bogus' function definition to illustrate handling of short
labels. Minor text changes.
--- a/FOPRunXSLTExt/examples/balisage2014.xml	Tue Jul 29 00:32:37 2014 +0100
+++ b/FOPRunXSLTExt/examples/balisage2014.xml	Tue Jul 29 00:33:22 2014 +0100
@@ -4,11 +4,11 @@
 <box id="box001" width="2240pt" height="540pt">
 <paragraph id="para001">The XSLT extension functions from the Print and Page Layout Community Group @ W3C (see <url></url>) allow you to run your XSL-FO formatter within your XSLT transform, and do it as often as you like, to get an area tree and make decisions based on formatted areas to do things like:</paragraph>
 <list id="list009">
-  <item label="*">Adjust the start-indent of a fo:list-block based on the length of the longest fo:list-item-label; or</item>
+  <item label="*">Adjust the start-indent of a <code>fo:list-block</code> based on the length of the longest <code>fo:list-item-label</code>; or</item>
   <item label="*">Size this text to be <font-size/> so it fits this box.</item>
-<box id="box002" width="2240pt" height="560pt" columns="2" border="none">
+<box id="box002" width="2240pt" height="630pt" columns="2" border="none">
 <title>XSLT and XSL-FO Processors</title>
 <paragraph id="para002">The extension is available for Java and DotNet and uses either the Apache FOP XSL formatter or Antenna House AHF formatter to produce the area trees.</paragraph>
 <paragraph>The single Java jar file covers four combinations of XSLT processor and XSL-FO formatter:</paragraph>
@@ -63,6 +63,10 @@
     <function>ppl:sum-lengths-to-pt($lengths as xs:string*) as xs:double</function>
     <def>Returns the length, in points (1/72 of an inch), of the sum of a sequence of lengths represented as strings, e.g., &#x201C;<code>6pt</code>&#x201D;, etc.</def>
+  <item>
+    <function>bogus</function>
+    <def>Not a function, just an illustration of how, by using the extension functions to find the formatted size of the function definition, the <code>fo:list-item-body</code> moves down only for long function definitions.</def>
+  </item>