DO NOT REPLY [Bug 46160] Automatic breaking of long landscape elements (tables) across multiple pages
https://issues.apache.org/bugzilla/show_bug.cgi?id=46160 --- Comment #8 from Paul 2009-03-09 17:19:28 PST --- Created an attachment (id=23363) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23363) Landscape table example Sorry for the delay in getting an example out to you. Attached is an archive containing, DocBook XML source, fo and Apache FOP PDF output for a landscape table example. LandscapeTableExampleWanted.xml.pdf is an example of the type of output I would like to be able to generate. Paul -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46823] LayoutException when rendering ./examples/fo/basic/blockcontainer.fo
https://issues.apache.org/bugzilla/show_bug.cgi?id=46823 --- Comment #4 from Andreas L. Delmelle 2009-03-09 14:05:29 PST --- (In reply to comment #3) > I should have looked at the FO more closely... still, this is not a very good > example for someone wanting to try FOP out. It would be better to remove the > error on overflow and generate some useful output for the user. WDYT? Good idea. Indeed, a dubious demo file. :-) -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46823] LayoutException when rendering ./examples/fo/basic/blockcontainer.fo
https://issues.apache.org/bugzilla/show_bug.cgi?id=46823 --- Comment #3 from Adrian Cumiskey 2009-03-09 13:58:31 PST --- I should have looked at the FO more closely... still, this is not a very good example for someone wanting to try FOP out. It would be better to remove the error on overflow and generate some useful output for the user. WDYT? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Error output of junit-layout-standard
Hi all Just updated my local sandbox, and noticed an error in the build log that I didn't quite expect: [junit] - Standard Error - [junit] Mar 9, 2009 9:00:01 PM org.apache.fop.area.AreaTreeParser $Handler setTraits [junit] SEVERE: Background image not available: ../../resources/ images/bgimg300dpi.jpg [junit] java.io.FileNotFoundException: Image not found: ../../ resources/images/bgimg300dpi.jpg ... [junit] at org.apache.fop.intermediate.IFTester.createIF(IFTester.java:145) [junit] at org.apache.fop.intermediate.IFTester.doIFChecks(IFTester.java:163) Does anyone else get this? I haven't investigated yet which testcase it points to, so before I start digging, if this rings a bell... It doesn't cause a failure, though. Build successful. Cheers Andreas
DO NOT REPLY [Bug 46826] reference-orientation treated as an inherited property
https://issues.apache.org/bugzilla/show_bug.cgi?id=46826 --- Comment #3 from Andreas L. Delmelle 2009-03-09 13:16:50 PST --- Created an attachment (id=23362) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23362) Proposed fix Patch fixing the issue: very self-contained, since it's only the region-reference-areas' placement that seemed to depend on it. An additional parameter to a private method seemed reasonable enough to meet the requirements of CTM.getCTMAndRelDims(). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46826] reference-orientation treated as an inherited property
https://issues.apache.org/bugzilla/show_bug.cgi?id=46826 --- Comment #2 from Andreas L. Delmelle 2009-03-09 11:48:49 PST --- (In reply to comment #1) > CTM.getCTMAndRelDims() seems to expect a *relative* reference-orientation > (with > respect to the ancestor reference-area), Note: the emphasis is due to the fact that the method signature and javadoc indicate that it's an 'absolute' value. When checking the method body, we get the idea of what this 'absolute' refers to. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46826] reference-orientation treated as an inherited property
https://issues.apache.org/bugzilla/show_bug.cgi?id=46826 --- Comment #1 from Andreas L. Delmelle 2009-03-09 11:32:21 PST --- Just to keep track of the progress: CTM.getCTMAndRelDims() seems to expect a *relative* reference-orientation (with respect to the ancestor reference-area), so this would mean that we need to pass in the difference between the simple-page-master's reference-orientation and that of the region. Simplest case: CTM.getCTMAndRelDims() expects -90. In current FOP Trunk it gets 90 (inherited value). After fixing FOPropertyMapping, it gets 0. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46826] New: reference-orientation treated as an inherited property
https://issues.apache.org/bugzilla/show_bug.cgi?id=46826 Summary: reference-orientation treated as an inherited property Product: Fop Version: 1.0dev Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: fo tree AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: adelme...@apache.org The "reference-orientation" property is currently treated as an inheritable property (see FOPropertMapping.createLayoutProperties()), but this is not defined as such in the XSL-FO 1.1 Recommendation (see: 7.21.3, http://www.w3.org/TR/xsl/#reference-orientation) Simply changing the boolean in FOPropertyMapping reveals that we have somehow always worked around this issue. The generation of the region-reference-areas seems to depend on its 'reference-orientation % 90' being equal to that of the simple-page-master. See for example: RegionBody.getViewportRectangle() and Page.setRegionReferencePosition(). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46160] Automatic breaking of long landscape elements (tables) across multiple pages
https://issues.apache.org/bugzilla/show_bug.cgi?id=46160 --- Comment #7 from Andreas L. Delmelle 2009-03-09 11:06:32 PST --- (In reply to comment #6) > > Testing some combinations, I've just noticed a small error in FOP Trunk: > reference-orientation is treated as an inherited property, while it most > certainly is not. Since a lot of tests seem to be depending on it, it may take > a while to fix this, although, purely codewise, it's only a matter of changing > a boolean switch in FOPropertyMapping... :-/ I'm currently looking closer into this one, and it seems the related checks in the tests are entirely correct (mainly simple-page-master_reference-orientation_*). Only, somehow the erroneous inheritance of the property has been taken into account when creating the region-viewport/region-reference area pair. Currently, in Page.makeRegionViewport(), an absolute rectangle is created (in page-coordinates) for the viewport-area. When setting the region-reference-area position, however, the 'width/ipd' that is obtained from this absolute rectangle should actually be the 'height/bpd' of the region-reference-area. What happens is that the absolute rectangle takes into account the reference-orientation specified on the simple-page-master. When creating the reference-area, though, we use the same pageCTM, but with the region's reference-orientation (which is 0, meaning no rotation with respect to the viewport). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46823] LayoutException when rendering ./examples/fo/basic/blockcontainer.fo
https://issues.apache.org/bugzilla/show_bug.cgi?id=46823 --- Comment #2 from Andreas L. Delmelle 2009-03-09 10:53:45 PST --- Sorry, a bit too quick, but there is a logical explanation: I had commented out the last fo:block-container, which has a overflow='error-if-overflow', so the fact that you get an exception is expected. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46823] LayoutException when rendering ./examples/fo/basic/blockcontainer.fo
https://issues.apache.org/bugzilla/show_bug.cgi?id=46823 --- Comment #1 from Andreas L. Delmelle 2009-03-09 10:50:04 PST --- FWIW: in spite of the fact that this bug is marked as applicable to 'ALL' versions, I cannot reproduce the issue with FOP Trunk on Mac OS X (tried rendering to PDF or AWT). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46823] New: LayoutException when rendering ./examples/fo/basic/blockcontainer.fo
https://issues.apache.org/bugzilla/show_bug.cgi?id=46823 Summary: LayoutException when rendering ./examples/fo/basic/blockcontainer.fo Product: Fop Version: all Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: page-master/layout AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: d...@cumiskey.com Rendering our own ./examples/fo/basic/blockcontainer.fo causes the BlockContainerLayoutManager to be unable to recover from content overflow. Here is the exception: org.apache.fop.layoutmgr.LayoutException: Content overflows the viewport of an fo:block-container in block-progression direction by 100800 millipoints. Content will be clipped. (See position 155:44) at org.apache.fop.layoutmgr.LayoutException$LayoutExceptionFactory.createException(LayoutException.java:92) at org.apache.fop.events.EventExceptionManager.throwException(EventExceptionManager.java:54) at org.apache.fop.events.DefaultEventBroadcaster$1.invoke(DefaultEventBroadcaster.java:152) at $Proxy0.viewportOverflow(Unknown Source) at org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElementsAbsolute(BlockContainerLayoutManager.java:533) at org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(BlockContainerLayoutManager.java:196) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:304) at org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:118) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:115) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:144) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:553) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:136) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:303) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:265) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:107) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:234) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:120) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:346) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:177) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484) at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:236) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:128) at org.apache.fop.cli.Main.startFOP(Main.java:174) at org.apache.fop.cli.Main.main(Main.java:205) -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
