Re: question
On 26.09.2005 19:09:59 Sergey Simonchik wrote: Hi, Letters A and B have same indent from the left edge of page in this example: ... fo:block border-style=solid border-width=20pt border-color=redA fo:block border-style=solid border-width=20pt border-color=blackB /fo:block /fo:block ... Here behaviors of block-progression and inline-progression are different. Is it correct? Yes, that's right. In your example the start-indent and end-indent trait is the same for both blocks. This has to do with the rules established in 5.3.2 in XSL 1.0. Jeremias Maerki
Re: question
On 27.09.2005 09:25:15 Jeremias Maerki wrote: On 26.09.2005 19:09:59 Sergey Simonchik wrote: Hi, Letters A and B have same indent from the left edge of page in this example: ... fo:block border-style=solid border-width=20pt border-color=redA fo:block border-style=solid border-width=20pt border-color=blackB /fo:block /fo:block ... Here behaviors of block-progression and inline-progression are different. Is it correct? Yes, that's right. In your example the start-indent and end-indent trait is the same for both blocks. This has to do with the rules established in 5.3.2 in XSL 1.0. I may need to add something to that. You can modify the behaviour to that which I assume you expect: Just add margin=0pt to your example. fo:block margin=0pt border-style=solid border-width=20pt border-color=redA fo:block margin=0pt border-style=solid border-width=20pt border-color=blackB /fo:block /fo:block Extensive documentation about indents can be found here: http://wiki.apache.org/xmlgraphics-fop/IndentInheritance Jeremias Maerki
[EMAIL PROTECTED]: Project xml-fop-maintenance (in module xml-fop-maintenance) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop-maintenance has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 40 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - xml-fop-maintenance : XSL-FO (Formatting Objects) processor (Maintenance branch) Full details are available at: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes] -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/gump_work/build_xml-fop-maintenance_xml-fop-maintenance.html Work Name: build_xml-fop-maintenance_xml-fop-maintenance (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only gump [Working Directory: /usr/local/gump/public/workspace/xml-fop-maintenance] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-script.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-gvt.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-27092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-27092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-27092005.jar - Buildfile: build.xml init-avail: init-filters-jdk14: [echo] JDK 1.4 present. [copy] Copying 1 file to /x1/gump/public/workspace/xml-fop-maintenance/build/src/codegen init-filters-jdk13: init: [echo] --- Fop 0.20.5 [1999-2003] prepare: [echo] Preparing the build directories [mkdir] Created dir: /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir:
[EMAIL PROTECTED]: Project xml-fop-maintenance (in module xml-fop-maintenance) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop-maintenance has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 40 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - xml-fop-maintenance : XSL-FO (Formatting Objects) processor (Maintenance branch) Full details are available at: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes] -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/gump_work/build_xml-fop-maintenance_xml-fop-maintenance.html Work Name: build_xml-fop-maintenance_xml-fop-maintenance (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only gump [Working Directory: /usr/local/gump/public/workspace/xml-fop-maintenance] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-script.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-gvt.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-27092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-27092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-27092005.jar - Buildfile: build.xml init-avail: init-filters-jdk14: [echo] JDK 1.4 present. [copy] Copying 1 file to /x1/gump/public/workspace/xml-fop-maintenance/build/src/codegen init-filters-jdk13: init: [echo] --- Fop 0.20.5 [1999-2003] prepare: [echo] Preparing the build directories [mkdir] Created dir: /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir:
[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-fop has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 63 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole output [fop.jar] identifier set to project name
-INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/classes]
-INFO- Failed with reason build failed
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop/gump_work/build_xml-fop_xml-fop.html
Work Name: build_xml-fop_xml-fop (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar
org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only package
[Working Directory: /usr/local/gump/public/workspace/xml-fop]
CLASSPATH:
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-script.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-gvt.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-27092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-27092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-27092005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-27092005.jar:/usr/local/gump/public/workspace/jakarta-commons/io/dist/jakarta-commons-io-27092005.jar:/usr/local/gump/public/workspace/jakarta-servletapi/dist/lib/servlet.jar
-
Buildfile: build.xml
BUILD FAILED
/x1/gump/public/workspace/xml-fop/build.xml:191: Cannot find
${env.FORREST_HOME}/main/forrest.build.xml imported from
/x1/gump/public/workspace/xml-fop/build.xml
Total time: 1 second
-
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/rss.xml
- Atom: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/atom.xml
== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2127092005,
[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-fop has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 63 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
Full details are available at:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole output [fop.jar] identifier set to project name
-INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/classes]
-INFO- Failed with reason build failed
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/xml-fop/xml-fop/gump_work/build_xml-fop_xml-fop.html
Work Name: build_xml-fop_xml-fop (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar
org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only package
[Working Directory: /usr/local/gump/public/workspace/xml-fop]
CLASSPATH:
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-script.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-27092005/lib/batik-gvt.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-27092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-27092005.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-27092005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-27092005.jar:/usr/local/gump/public/workspace/jakarta-commons/io/dist/jakarta-commons-io-27092005.jar:/usr/local/gump/public/workspace/jakarta-servletapi/dist/lib/servlet.jar
-
Buildfile: build.xml
BUILD FAILED
/x1/gump/public/workspace/xml-fop/build.xml:191: Cannot find
${env.FORREST_HOME}/main/forrest.build.xml imported from
/x1/gump/public/workspace/xml-fop/build.xml
Total time: 1 second
-
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/rss.xml
- Atom: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/atom.xml
== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2127092005,
Re: svn commit: r291860 - /xmlgraphics/fop/trunk/build.xml
Luca Furini schrieb: Added docs building with forrest (needs Ant 1.6 and you need to run forrest once manually as there's a bug with the plugin download) Modified: xmlgraphics/fop/trunk/build.xml Shouldn't the documentation target be an optional one, so as to let the user decide whether or not to install forrest? Uhm sorry, of course it should work without forrest. At the moment, users without forrest are not able to compile fop. I'll have a look at it later today -- Christian
alignment-baseline property
Finn, (and others of course) what to you make out of the following? In 7.13.2 alignment-baseline is defined as having the values: auto | baseline | before-edge | text-before-edge | middle | central | after-edge | text-after-edge | ideographic | alphabetic | hanging | mathematical | inherit But further below in the text where it says Values have the following meanings: we have at the end explanations for the values: top, bottom, text-top, and text-bottom, which according to the definition above are not valid values for this property. Manuel
DO NOT REPLY [Bug 36826] New: - nullpointerexc at org.apache.fop.fo.FOTreeBuilder.endElement, XSL and XML are valid
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36826. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36826 Summary: nullpointerexc at org.apache.fop.fo.FOTreeBuilder.endElement, XSL and XML are valid Product: Fop Version: 0.20.5 Platform: All OS/Version: All Status: NEW Severity: critical Priority: P1 Component: pdf renderer AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] XML and XSL are valid, XSL seems to be OK. I got the following exception: Caused by: javax.xml.transform.TransformerException: java.lang.NullPointerException at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java(Compiled Code)) at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java(Compiled Code)) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java(Compiled Code)) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:738) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1251) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1229) at hu.cib.soa.print.docgenerator.DocGenerator.generatePdfDoc(DocGenerator.java:94) ... 24 more Caused by: java.lang.NullPointerException at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java(Compiled Code)) at org.apache.xml.serializer.ToXMLSAXHandler.endElement(ToXMLSAXHandler.java(Compiled Code)) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java(Compiled Code)) ... 31 more -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36826] - nullpointerexc at org.apache.fop.fo.FOTreeBuilder.endElement, XSL and XML are valid
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36826. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36826 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |NEEDINFO --- Additional Comments From [EMAIL PROTECTED] 2005-09-27 15:27 --- TransformerException is a wrapped exception. Please provide the full stack trace including the wrapped exception. Otherwise, there's no chance we can help. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: Another page-related question: page-position=last
Jeremias Maerki wrote: It's an interesting idea. However, I suspect this will probably not be necessary. We should be able to make the breaker clever enough to handle this particular case. When the page bpd depends on the page-masters, things becomes very strange. Not only it's difficult to implement the page-master choice, but even to understand what should be the expected result! :-) For example: let's suppose the breaker is working, and it has to place the last 25 lines of a page-sequence. The page-master for the last page has a bpd allowing no more than 20 lines, while the other page-masters can contain up to 30 lines. What happens? If the breaker starts building a last page it soon realizes that it would not contain all the remaining content, so it would be no more a last page. But if it starts building a non-last page, it reaches the end of the content, and has to turn it into a last page, which is impossible. What is the expected output? The only way I see to satisfy the property is to create two more pages: one non-last page, partially empty, with less than 25 lines (24 or fewer, if there are keeps, widows or orphans) and a last page with the remaining lines. This sort of problems happens only if the last page is smaller than the previous ones: otherwise, the breaker can always try to build a non-last page, eventually moving all its content into a last page. Now I think of this ... an idea, that could work at least when the non-last pages have the same bpd and the last page a smaller one, could be to modify a little the elements appended at the end of the sequence, so that they have a width equal to the difference (nonLastBPD - lastBPD). This way, the last page created by the breaker will have an apparent width of nonLastBPD, but the content placed inside it will have an overall bpd equal to nonLastBPD - (nonLastBPD - lastBPD) = lastBPD What do you think? Regards Luca
RE: question
Thank you. -Исходное сообщение- От: Jeremias Maerki [mailto:[EMAIL PROTECTED] Отправлено: Вт 27.09.2005 12:12 Кому: fop-dev@xmlgraphics.apache.org Копия: Тема: Re: question On 27.09.2005 09:25:15 Jeremias Maerki wrote: On 26.09.2005 19:09:59 Sergey Simonchik wrote: Hi, Letters A and B have same indent from the left edge of page in this example: ... fo:block border-style=solid border-width=20pt border-color=redA fo:block border-style=solid border-width=20pt border-color=blackB /fo:block /fo:block ... Here behaviors of block-progression and inline-progression are different. Is it correct? Yes, that's right. In your example the start-indent and end-indent trait is the same for both blocks. This has to do with the rules established in 5.3.2 in XSL 1.0. I may need to add something to that. You can modify the behaviour to that which I assume you expect: Just add margin=0pt to your example. fo:block margin=0pt border-style=solid border-width=20pt border-color=redA fo:block margin=0pt border-style=solid border-width=20pt border-color=blackB /fo:block /fo:block Extensive documentation about indents can be found here: http://wiki.apache.org/xmlgraphics-fop/IndentInheritance Jeremias Maerki winmail.dat
Re: Another page-related question: page-position=last
On 27.09.2005 16:38:23 Luca Furini wrote: Jeremias Maerki wrote: It's an interesting idea. However, I suspect this will probably not be necessary. We should be able to make the breaker clever enough to handle this particular case. When the page bpd depends on the page-masters, things becomes very strange. Not only it's difficult to implement the page-master choice, but even to understand what should be the expected result! :-) For example: let's suppose the breaker is working, and it has to place the last 25 lines of a page-sequence. The page-master for the last page has a bpd allowing no more than 20 lines, while the other page-masters can contain up to 30 lines. What happens? If the breaker starts building a last page it soon realizes that it would not contain all the remaining content, so it would be no more a last page. But if it starts building a non-last page, it reaches the end of the content, and has to turn it into a last page, which is impossible. What is the expected output? In this case it has to generate a blank page IMO. Note that this is a scenario that is important for Switzerland where we have Einzahlungsscheine (a preprinted form used for payments). These are often expected to be on the last page of the document. So far I always had to persuade my clients that putting the Einzahlungsschein on the first page is not so bad. :-) The problem is with the page x of y hack that won't work like this if the last empty block ends up on the second-to-last page. The only way I see to satisfy the property is to create two more pages: one non-last page, partially empty, with less than 25 lines (24 or fewer, if there are keeps, widows or orphans) and a last page with the remaining lines. That sounds suboptimal. The less breaks, the better. Better have a blank page. This sort of problems happens only if the last page is smaller than the previous ones: otherwise, the breaker can always try to build a non-last page, eventually moving all its content into a last page. Now I think of this ... an idea, that could work at least when the non-last pages have the same bpd and the last page a smaller one, could be to modify a little the elements appended at the end of the sequence, so that they have a width equal to the difference (nonLastBPD - lastBPD). This way, the last page created by the breaker will have an apparent width of nonLastBPD, but the content placed inside it will have an overall bpd equal to nonLastBPD - (nonLastBPD - lastBPD) = lastBPD What do you think? I don't get it, yet. What about the following approach? Run the breaker without special last-page handling, then inspect the allocated BPD for the last part. If it fits into the last page, just exchange the page-master (*) and paint it there. If it doesn't fit, paint it using the non-last page-master and add a blank page with the last page-master. If there's a box w=0 at the end of the element list, force a new part and paint that on the last page to handle the page x of y case. (*) Doesn't work if the available IPD is different. A restart will be necessary in this case which could result in an overflow of the last page which means that the content can still be reset to the old page-master and a blank last page has to be generated. Jeremias Maerki
Re: alignment-baseline property
On Sep 27, 2005, at 14:34, Manuel Mall wrote: Hi Manuel, what to you make out of the following? In 7.13.2 alignment-baseline is defined as having the values: auto | baseline | before-edge | text-before-edge | middle | central | after-edge | text-after-edge | ideographic | alphabetic | hanging | mathematical | inherit But further below in the text where it says Values have the following meanings: we have at the end explanations for the values: top, bottom, text-top, and text-bottom, which according to the definition above are not valid values for this property. IIC, the definition-list should be expanded to include these latter four. Well, it could easily be. Their meaning seems to be related to 'before-edge', 'after-edge', 'text-before-edge' and 'text-after-edge', only that the ones currently not included in the list are only valid for horizontal writing modes (lr-tb and rl-tb). In vertical writing-mode they fall back to the dominant-baseline, as there, 'before' is 'right' and 'after' is 'left' --and 'top' and 'bottom' are 'end' and 'start'. If you catch the drift... ;-) Not 100% sure, but this seems to be the most plausible... BTW: XSL 1.1 also misses these in the definition --Feel like submitting the question to the XSL-FO WG? :-) Cheers, Andreas
Re: alignment-baseline property
On Sep 27, 2005, at 19:58, Andreas L Delmelle wrote: On Sep 27, 2005, at 14:34, Manuel Mall wrote: what to you make out of the following? In 7.13.2 alignment-baseline is defined as having the values: auto | baseline | before-edge | text-before-edge | middle | central | after-edge | text-after-edge | ideographic | alphabetic | hanging | mathematical | inherit Just thought I'd add: 7.13.1 alignment-adjust --same thing there Cheers, Andreas
Re: alignment-baseline property
On Wed, 28 Sep 2005 02:03 am, Andreas L Delmelle wrote: On Sep 27, 2005, at 19:58, Andreas L Delmelle wrote: On Sep 27, 2005, at 14:34, Manuel Mall wrote: what to you make out of the following? In 7.13.2 alignment-baseline is defined as having the values: auto | baseline | before-edge | text-before-edge | middle | central | after-edge | text-after-edge | ideographic | alphabetic | hanging | mathematical | inherit Just thought I'd add: 7.13.1 alignment-adjust --same thing there Yes, you are correct. So may be it was done deliberately - but I still don't understand. As you said its not corrected in the 1.1 draft nor is it in the 1.0 errata. And surely other implementers would have picked up on that long before me and alerted the XSL-FO WG? What am I not getting here? Cheers, Andreas Cheers Manuel
alignment-adjust property
This is another of those spec interpretation questions. Sorry to populate this list with so many of these questions but this is a source of real irritation for me in the moment. I just want to get sub/superscripts working and do it properly and I am hitting all these murky (as Peter put it) things in the spec. Here we go again. In 7.13 the spec defines the various baselines. In that section it says: There are, in addition, two computed baselines that are only defined for line areas. and then goes on about those two baselines being before-edge and after-edge. We then come to 7.13.1 alignment-adjust and before-edge and after-edge are valid values. However, the alignment-adjust property applies only to inline fo's. And inline fo's don't generate line areas. As the alignment-adjust property applies to the area generated by the fo (not like the alignment-baseline property which applies to the parent area) none of the areas generated by the fo's in question will have those baselines defined. The text also implies that i-f-o and and e-g have the after-edge as their dominant baseline. For the auto setting we are allowed to use heuristics to determine where the baseline is but that option is not open to the other values. So, what's the point of having before-edge, after-edge as allowed values if those baselines are guaranteed not to be defined (and even use them as default for e-g and i-f-o)? Manuel
