Re: cvs commit: xml-fop/test/layoutengine/testcases block-container3.xml
I'm trying to figure out what the indent of the orange block under the block-container may be, or rather if our current implementation is really ok. It's clear that for the yellow block start-indent is 10pt. 5.3.2 says for FOs that don't generate a reference area (ex. fo:block) the following is true: start-indent = inherited_value_of(start-indent) + margin-corresponding + padding-corresponding + border-corresponding-width start-indent = 10pt = 10pt + 0pt + 0pt + 0pt For the block-container a different rule applies because it generates a reference area: start-indent = margin-corresponding + padding-corresponding + border-corresponding-width start-indent = 0pt = 0pt + 0pt + 0pt Then for the orange block the first formula is used again: start-indent= 0pt = 0pt + 0pt + 0pt + 0pt Now, it's interesting to note that XEP and AltSoft interpret this differently. XEP indents the orange block by 10pt while AltSoft indents it by 20pt. You could also note that start-indent is specified as Inherited: yes which somewhat contradicts the second formula above. XEP seems to use the inherited start-indent for the block-container. AltSoft seems to do the same and even does the same for the orange block although rendering then orients itself on the reference area established by the block-container, thus indenting the orange block by 20pt. AltSoft is certainly wrong. The question is if XEP is right. :-) I googled a bit and indeed, there seems be a certain amount of confusion how this should be handled. Any thoughts? On 13.01.2005 16:07:02 jeremias wrote: jeremias2005/01/13 07:07:02 Added: test/layoutengine/testcases block-container3.xml Log: Testcase for checking start-indent inheritance across block-containers. Revision ChangesPath 1.1 xml-fop/test/layoutengine/testcases/block-container3.xml Index: block-container3.xml === ?xml version=1.0 encoding=UTF-8? !-- Copyright 2005 The Apache Software Foundation Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- !-- $Id: block-container3.xml,v 1.1 2005/01/13 15:07:02 jeremias Exp $ -- testcase info p This test checks indents on block-containers. /p /info fo fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; xmlns:svg=http://www.w3.org/2000/svg; fo:layout-master-set fo:simple-page-master master-name=normal page-width=5in page-height=5in fo:region-body/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=normal white-space-collapse=true fo:flow flow-name=xsl-region-body fo:block start-indent=10pt fo:block background-color=yellowfo:block|fo:block/fo:block fo:block-container fo:block background-color=orangefo:block|fo:block-container|fo:block/fo:block /fo:block-container /fo:block /fo:flow /fo:page-sequence /fo:root /fo checks eval expected=35 xpath=/areaTree/pageSequence/pageViewport/page[1]/regionViewport/regionBody/mainReference/span/flow/block[1]/block[1]/@ipd/ eval expected=36 xpath=/areaTree/pageSequence/pageViewport/page[1]/regionViewport/regionBody/mainReference/span/flow/block[1]/block[1]/@ipda/ !-- TODO Complete checks after clarifying interpretation -- !--eval expected=35 xpath=/areaTree/pageSequence/pageViewport/page[1]/regionViewport/regionBody/mainReference/span/flow/block[1]/block[2]/block[1]/@ipd/ eval expected=35 xpath=/areaTree/pageSequence/pageViewport/page[1]/regionViewport/regionBody/mainReference/span/flow/block[1]/block[2]/block[1]/@ipda/-- /checks /testcase Jeremias Maerki
Re: start-indent inheritance (was: cvs commit: xml-fop/test/layoutengine/testcases block-container3.xml)
There seems to have been some discussion about this in the CR phase: http://www.w3.org/2001/08/28-XSL-PR-DOC.html (see comment 20) It would seem that in the case of reference-area generating FOs start-indent should simply be inherited (comment 20, item 3). In my example the start-indent of the block-container would be 10pt, which is then inherited by the orange block. This amounts to an effective 20pt indent for the orange block and oops, AltSoft is suddenly right. I'm confused. Jeremias Maerki
bring XSL 1.1 fo:flow-map into HEAD?
Team, The bookmarks are finished. In doing them, I found perhaps about 10 bugs in the 1.1 spec with them (mostly typos but a few functional ones as well), and I sent emails to the XSL-Editors list about those. Next, I'd like to start this weekend looking into bringing fo:flow-map [1] into our 1.0 release. Any objections? Thanks, Glen [1] http://www.w3.org/TR/xsl11/#fo_flow-map
Re: bring XSL 1.1 fo:flow-map into HEAD?
I'd prefer if you helped working on those things we really need for a 1.0 release. But as long as you don't break 1.0 compatibility I'm -0. So no real objection. On 13.01.2005 19:52:40 Glen Mazza wrote: Team, The bookmarks are finished. In doing them, I found perhaps about 10 bugs in the 1.1 spec with them (mostly typos but a few functional ones as well), and I sent emails to the XSL-Editors list about those. Next, I'd like to start this weekend looking into bringing fo:flow-map [1] into our 1.0 release. Any objections? Thanks, Glen [1] http://www.w3.org/TR/xsl11/#fo_flow-map Jeremias Maerki
Re: cvs commit: xml-fop build.xml
On Wed, Jan 12, 2005 at 09:02:37PM +0100, Jeremias Maerki wrote:
Uhm, the classpath was quite ok like it was. If you look into the
fop-transcoder-allinone.jar, it contains all classes (or at least should
contain all classes) that are needed to run the transcoder tests. That
JAR is for people who don't like all the little dependency JARs.
Why did you do the change in the first place? What was the problem?
Where else do I find the SAX2 driver class
org.apache.xerces.parsers.SAXParser?
[echo] Running basic functionality tests for fop-transcoder-allinone.jar
[junit] Testsuite: org.apache.fop.BasicTranscoderTestSuite
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.204 sec
[junit] - Standard Error -
[junit] java.io.IOException: SAX2 driver class
org.apache.xerces.parsers.SAXParser not found
[junit] at
org.apache.batik.dom.util.SAXDocumentFactory.createDocument(Unknown Source)
[junit] at
org.apache.batik.dom.util.SAXDocumentFactory.createDocument(Unknown Source)
[junit] at
org.apache.batik.dom.svg.SAXSVGDocumentFactory.createDocument(Unknown Source)
[junit] at
org.apache.batik.dom.svg.SAXSVGDocumentFactory.createDocument(Unknown Source)
[junit] at
org.apache.batik.transcoder.XMLAbstractTranscoder.transcode(Unknown Source)
[junit] at
org.apache.batik.transcoder.SVGAbstractTranscoder.transcode(Unknown Source)
[junit] at
org.apache.fop.AbstractBasicTranscoderTestCase.testGenericPDFTranscoder(AbstractBasicTranscoderTestCase.java:70)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:324)
[junit] at junit.framework.TestCase.runTest(TestCase.java:154)
[junit] at junit.framework.TestCase.runBare(TestCase.java:127)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:118)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:326)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:560)
[junit] - ---
[junit] Testcase:
testGenericPDFTranscoder(org.apache.fop.BasicPDFTranscoderTestCase):
Caused an ERROR
[junit] null
[junit] Enclosed Exception:
[junit] SAX2 driver class org.apache.xerces.parsers.SAXParser not found
[junit] org.apache.batik.transcoder.TranscoderException: null
[junit] Enclosed Exception:
[junit] SAX2 driver class org.apache.xerces.parsers.SAXParser not found
[junit] at
org.apache.batik.transcoder.XMLAbstractTranscoder.transcode(Unknown Source)
[junit] at
org.apache.batik.transcoder.SVGAbstractTranscoder.transcode(Unknown Source)
[junit] at
org.apache.fop.AbstractBasicTranscoderTestCase.testGenericPDFTranscoder(AbstractBasicTranscoderTestCase.java:70)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Simon
On 12.01.2005 20:50:37 spepping wrote:
spepping2005/01/12 11:50:36
Modified:.build.xml
Log:
Fixed an error in the classpath of one of the junit tests
Revision ChangesPath
1.113 +1 -0 xml-fop/build.xml
Index: build.xml
===
RCS file: /home/cvs/xml-fop/build.xml,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -r1.112 -r1.113
--- build.xml 6 Jan 2005 19:20:37 - 1.112
+++ build.xml 12 Jan 2005 19:50:36 - 1.113
@@ -696,6 +696,7 @@
formatter type=brief usefile=false/
classpath
pathelement location=${build.dir}/test-classes/
+path refid=libs-basic-run-classpath/
fileset dir=build
include name=fop-transcoder-allinone.jar/
/fileset
--
Simon Pepping
home page: http://www.leverkruid.nl
Re: cvs commit: xml-fop build.xml
I see. I've added JAXP and Xerces to the classpath. This approach still allows us to verify that the repackaging process is set up correctly. Sorry for the trouble. I rarely work with JDK 1.3 and I have Xerces and Xalan in the endorsed directory for all my JDK 1.4+ VMs. On 13.01.2005 21:14:25 Simon Pepping wrote: On Wed, Jan 12, 2005 at 09:02:37PM +0100, Jeremias Maerki wrote: Uhm, the classpath was quite ok like it was. If you look into the fop-transcoder-allinone.jar, it contains all classes (or at least should contain all classes) that are needed to run the transcoder tests. That JAR is for people who don't like all the little dependency JARs. Why did you do the change in the first place? What was the problem? Where else do I find the SAX2 driver class org.apache.xerces.parsers.SAXParser? [echo] Running basic functionality tests for fop-transcoder-allinone.jar [junit] Testsuite: org.apache.fop.BasicTranscoderTestSuite [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.204 sec [junit] - Standard Error - [junit] java.io.IOException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found [junit] at org.apache.batik.dom.util.SAXDocumentFactory.createDocument(Unknown Source) Jeremias Maerki
Re: cvs commit: xml-fop build.xml
Jeremias Maerki wrote: I see. I've added JAXP and Xerces to the classpath. Isn't it somewhat strange that org.apache.xerces.parsers.SAXParser is explicitely referenced? I'd think everyone uses JAXP meanwhile. Do you access Xerces specific functionality? J.Pietschmann
RE: Unsubscribe
Title: Message Please unsubscribe me from the list
Re: Unsubscribe
We can't do it for you. You have to do it yourself. Instructions are here: http://xml.apache.org/fop/dev/index.html#mail-fop-dev But all you need to do, is send an e-mail here *from the e-mail address with which you subscribed* (presumably [EMAIL PROTECTED]): [EMAIL PROTECTED] On Jan 13, 2005, at 3:02 PM, Peter King wrote: Please unsubscribe me from the list Cheers! Web Maestro Clay -- [EMAIL PROTECTED] - http://homepage.mac.com/webmaestro/ My religion is simple. My religion is kindness. - HH The 14th Dalai Lama of Tibet
text-decoration
Fop-devs, In spite of the huffing and puffing, my original implementation of text-decoration was wrong. Such hubris. Currently being corrected in Defoe. Peter
Re: Xerces-dependency in Batik (was: cvs commit: xml-fop build.xml)
(cc'ing batik-dev) If I interpret this correctly, Batik uses the following entry in XMLResourceDescriptor.properties to instantiate a parser in SAXDocumentFactory through the SAX XMLReaderFactory: org.xml.sax.driver = org.apache.xerces.parsers.SAXParser There's no Xerces-dependency in Java code, only SAX. Neither does the PDFTranscoder use Xerces-specific functionality. This should probably be improved in Batik. On 13.01.2005 23:22:14 J.Pietschmann wrote: Jeremias Maerki wrote: I see. I've added JAXP and Xerces to the classpath. Isn't it somewhat strange that org.apache.xerces.parsers.SAXParser is explicitely referenced? I'd think everyone uses JAXP meanwhile. Do you access Xerces specific functionality? J.Pietschmann Jeremias Maerki
