Re: testcases

--- Jeremias Maerki <[EMAIL PROTECTED]> wrote: > Thanks, Simon. > > And fop-devs, also note that you are allowed (and > encouraged) to correct, > modify, improve and add test cases yourself. :-) > Can we remove some too?!? ;) Glen

Re: testcases

Thanks, Simon. And fop-devs, also note that you are allowed (and encouraged) to correct, modify, improve and add test cases yourself. :-) On 12.02.2005 14:25:12 Simon Pepping wrote: > Jeremias, > > Note that you can use the ancestor axis: > xpath="//text[. = 'line1']/ancestor::pageViewport/@nr"

testcases

Jeremias, Note that you can use the ancestor axis: xpath="//text[. = 'line1']/ancestor::pageViewport/@nr" instead of xpath="//text[. = 'line1']/../../../../../../../../../@nr" Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

page breaks (was: Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking4.xml)

it's not > resetPosition() methods that don't behave as I claimed in my earlier CVS > message (although I found a few strange things with resetPosition() while > looking at table headers/footers). > > On 10.02.2005 13:52:35 jeremias wrote: > > jeremias2005/02/10 04:5

Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking4.xml

2/10 04:52:35 > > Modified: test/layoutengine/testcases normal-breaking4.xml > Log: > Adding an additional block at the end to see if a new block would behave > differently. Jeremias Maerki

Re: cvs commit: xml-fop/test/layoutengine/testcases table-cell5a.xml

Uhm, don't look too closely at my latest test cases. I've made some mistake in interpretation. Revisiting now... Jeremias Maerki

Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking2.xml

Thanks a lot, Luca. That was it. I was slowly tracking that thing down. I knew already that these start indices were wrong but hadn't figured out how to fix it. And thanks to Chris for the pointers earlier. In the meantime I got to know a lot about the inner workings of the line layout. :-) Good

Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking2.xml

On Feb 2, 2005, at 2:14 AM, Jeremias Maerki wrote: No, it don't think so. That bug happens in getNextBreakPoss() while mine happens in addAdreas(). I thought it was called addAndreas(to,,list-of-folks,to,send,big,thanks) ;-) Web Maestro Clay -- <[EMAIL PROTECTED]> -

Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking2.xml

Jeremias Maerki wrote: > If someone has an idea about the ArrayOutOfBoundsException, all the > better. I'm currently trying to debug that thing. It's because of this line in LineLM.addAreas(): iCurrParIndex = 0; If a block has properly handled preserved linefeeds, it will generate more than

Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking2.xml

No, it don't think so. That bug happens in getNextBreakPoss() while mine happens in addAdreas(). On 02.02.2005 10:36:41 Chris Bowditch wrote: > Jeremias Maerki wrote: > > Just to be clear. This ArrayOutOfBoundsException is not the same problem > > I've described in my earlier post. I just happened

Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking2.xml

Jeremias Maerki wrote: Just to be clear. This ArrayOutOfBoundsException is not the same problem I've described in my earlier post. I just happened to run into both problems at the same time. Running normal-breaking2.xml with the current code (without my patch) will result in a document with 1 page

Re: cvs commit: xml-fop/test/layoutengine/testcases normal-breaking2.xml

3:51:37 > > Modified:test/layoutengine disabled-testcases.txt > Added: test/layoutengine/testcases normal-breaking2.xml > Log: > Regression test for ArrayOutOfBoundsException in > LineLayoutManager.addAreas() (to be fixed). Jeremias Maerki

Re: cvs commit: xml-fop/test/layoutengine/testcases external-graphic1.xml external-graphic2.xml

Oops, sorry! And thanks for catching it. On 24.01.2005 23:03:56 pietsch wrote: > pietsch 2005/01/24 14:03:56 > > Modified:.build.xml >test/layoutengine/testcases external-graphic1.xml > external-graphic2.xml > Log: >

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 bl

Re: cvs commit: xml-fop/test/layoutengine/testcases block-container3.xml

n 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-c

Re: cvs commit: xml-fop/test/layoutengine/testcases block-nested1.xml

emias wrote: > jeremias2005/01/06 08:09:57 > > Added: test/layoutengine/testcases block-nested1.xml > Log: > Test for nested blocks with borders, margins and padding. Jeremias Maerki

Re: cvs commit: xml-fop/test/layoutengine/testcases padding2.xml

6 jeremias wrote: > jeremias2005/01/06 01:47:46 > > Added: test/layoutengine/testcases padding2.xml > Log: > Testing padding shorthands. Jeremias Maerki