DO NOT REPLY [Bug 9145] New: - Error when trying to use the Methode render(XMLReader, XSLTInputHandler) of the Class Driver
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9145. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9145 Error when trying to use the Methode render(XMLReader, XSLTInputHandler) of the Class Driver Summary: Error when trying to use the Methode render(XMLReader, XSLTInputHandler) of the Class Driver Product: Fop Version: 0.20.1 Platform: PC OS/Version: Other Status: NEW Severity: Critical Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I try to use the FOP in a Java Application with a XSLTInputHandler, I get the Error: DEBUG 10215 [fop ] (): using SAX parser org.apache.xerces.parsers.SAXParser java.lang.NoSuchMethodError: java.lang.String org.w3c.dom.Node.getLocalName() void org.apache.xalan.transformer.TransformerImpl.run() void java.lang.Thread.run() The codeline which produce this Error is: _fopDriver.render(_saxXMLReader, _fopXSLTInputHandler.getInputSource()); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 9113] - Strange indentation on hyphenation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9113. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9113 Strange indentation on hyphenation [EMAIL PROTECTED] changed: What|Removed |Added Component|pdf renderer|general - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FW: Environment problem
Sorry for crossposting, but the problem occures, if I try to get the Parser from FOInputHandler in the junit test case. inputHandler.getParser() throws a FOPException: org.apache.fop.apps.FOPException: org.apache.xerces.parsers.SAXParser is not a SAX driver at org.apache.fop.apps.InputHandler.createParser(InputHandler.java:75) at org.apache.fop.apps.FOInputHandler.getParser(FOInputHandler.java:40) based on a ClassCastException: java.lang.ClassCastException: org.apache.xerces.parsers.StandardParserConfiguration at org.apache.xerces.parsers.SAXParser.init(SAXParser.java:95) at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:232) at org.apache.fop.apps.InputHandler.createParser(InputHandler.java:66) at org.apache.fop.apps.FOInputHandler.getParser(FOInputHandler.java:40) ... The SAX2 final version isn't correct set only in the test case (in the application every thing works fine)!? -Original Message- From: Torsten Erler [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 16. Mai 2002 09:37 To: Xalan-Dev (E-mail) Subject: Environment problem Hi all I've a incomprehensibly problem with the SAX environment. If I start my project and run EnvironmentCheck all is ok: # BEGIN writeEnvironmentReport($Revision: 1.10 $): Useful stuff found: version.DOM.draftlevel=2.0fd java.class.path=snip (too long) version.JAXP=1.1 java.ext.dirs=D:\javasoft\jdk1.3.1\jre\lib\ext version.xerces2=Xerces-J 2.0.1 version.xerces1=not-present version.xalan2_2=Xalan Java 2.3.1 version.xalan1=not-present version.ant=not-present java.version=1.3.1_03 version.DOM=2.0 version.crimson=not-present sun.boot.class.path=D:\javasoft\jdk1.3.1\jre\lib\rt.jar;D:\jav asoft\jdk1.3.1 \jre\lib\i18n.jar;D:\javasoft\jdk1.3.1\jre\lib\sunrsasign.jar; D:\javasoft\jd k1.3.1\jre\classes # BEGIN Listing XML-related jars in: foundclasses.java.class.path xml-apis.jar-apparent.version=xml-apis.jar from xalan-j_2_3_0 from xml-commons-1.0.b2 xml-apis.jar-path=f:\java\projects\star\beta\java\ext\tools\li b\xalan-2.3.1_ xml-apis.jar #- END Listing XML-related jars in: foundclasses.java.class.path - version.SAX=2.0 version.xalan2x=Xalan Java 2.3.1 #- END writeEnvironmentReport: Useful properties found: - # YAHOO! Your environment seems to be OK. Then, I have a test class and if I start this unit test with 100% identically classpath the result is: # BEGIN writeEnvironmentReport($Revision: 1.10 $): Useful stuff found: version.DOM.draftlevel=2.0fd java.class.path=snip (too long) version.JAXP=1.1 java.ext.dirs=D:\javasoft\jdk1.3.1\jre\lib\ext version.xerces2=Xerces-J 2.0.1 version.xerces1=not-present version.xalan2_2=Xalan Java 2.3.1 ERROR.version.SAX=ERROR attempting to load SAX version 2 class: java.lang.NoSuchMethodException: setAttributes ERROR.=At least one error was found! version.xalan1=not-present version.ant=not-present version.SAX-backlevel=2.0beta2-or-earlier java.version=1.3.1_03 version.DOM=2.0 version.crimson=not-present sun.boot.class.path=D:\javasoft\jdk1.3.1\jre\lib\rt.jar;D:\jav asoft\jdk1.3.1 \jre\lib\i18n.jar;D:\javasoft\jdk1.3.1\jre\lib\sunrsasign.jar; D:\javasoft\jd k1.3.1\jre\classes # BEGIN Listing XML-related jars in: foundclasses.java.class.path xml-apis.jar-apparent.version=xml-apis.jar from xalan-j_2_3_0 from xml-commons-1.0.b2 xml-apis.jar-path=f:\java\projects\star\beta\java\ext\tools\li b\xalan-2.3.1_ xml-apis.jar #- END Listing XML-related jars in: foundclasses.java.class.path - version.xalan2x=Xalan Java 2.3.1 #- END writeEnvironmentReport: Useful properties found: - # WARNING: Potential problems found in your environment! #Check any 'ERROR' items above against the Xalan FAQs #to correct potential problems with your classes/jars #http://xml.apache.org/xalan-j/faq.html Can anyone help me? I don't understand the difference, because the classpath and the sequence of jar files is the same in both cases! ThanX Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: status on website
Hi, Comment: Good idea. Suggestion: It probably wouldn't hurt to go ahead (on the page) and answer the inevitable, Can you please tell me when to expect the release FOP0.20.4|FOP10 DR1 announced on your status page? The same answer that would otherwise appear here, that is. Complaint: My coffee pot is busted. ;) Thanks, Joe Keiron Liddle keiron@aftexs To: FOP [EMAIL PROTECTED] w.com cc: Subject: status on website 05/16/2002 04:42 AM Please respond to fop-dev Hi, I added some status info to the website. So hopefully this will answer some peoples questions (I'm sure they will still want to know more things that are unknown). Any comments, complaints, suggestions? (apart from my poor spelling!) Keiron. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Environment problem (fixed)
Hi, just for information, for anyone, who gets in the same trouble! I've found the problem with the obsoleter SAX-2 implementation. In my classpath are 2 different xml-api's (I know about that, but I cannot avoid that, because of foreign parts in our app are delivered with this api contained in the jar file). To solve this, the xalan/xerxes libraries are in front of my classpath and it works fine, but JUnit uses two different classloader, the System ClassLoader and for reloading classes in gui (swing) testing they are using their own Class Loader. This loader seems to ignore the sequence of libraries in the classpath and returns the wrong implementation class (SAX 2.0beta2). Now I've disabled class reloading and all works perfect (May god be praised). cu Torsten :) ---snip - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 6997] - Row-spanned row data breaks over a page within a column
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6997. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6997 Row-spanned row data breaks over a page within a column --- Additional Comments From [EMAIL PROTECTED] 2002-05-16 11:09 --- Created an attachment (id=1877) Additionnal XFO testcase which is broken - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 6997] - Row-spanned row data breaks over a page within a column
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6997. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6997 Row-spanned row data breaks over a page within a column --- Additional Comments From [EMAIL PROTECTED] 2002-05-16 11:10 --- Created an attachment (id=1878) Additionnal XFO testcase which is broken, resulting broken PDF document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 6997] - Row-spanned row data breaks over a page within a column
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6997. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6997 Row-spanned row data breaks over a page within a column --- Additional Comments From [EMAIL PROTECTED] 2002-05-16 11:21 --- I believe I experienced the same problem and sent an additionnal broken testcase XFO document. I also joined the resulting broken PDF; see end of page 2. The first cell of the row 16:15 is spanned across 9 rows (this cell holds the row-group header). This spanned row crosses the page boundary, but is neverthless rendered on end of page 2, overflowing the xsl-region-body and xsl- footer reference areas. The cells of the subsequent rows, on page 3, are then shifted one column left. In this testcase, I do not use any border properties. The row that crosses the page boundary can be found between the '[BEGIN]' and '[END]' text markers within the testcase XFO document. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [PATCH] Proper use of font encodings for native fonts
Keiron Liddle schrieb: One reason for waiting was to see how it would work. There are some user issues that have popped up but nothing too serious. It would be good to know how people should deal with this situation. A new patch would certainly help. Christian might be able to say more about this. Ok (sorry a bit late) .. the patch corrected the mapping of the symbol fonts (more precise: the mapping of characters with a unicode value 255) This causes a problem with old stylesheets (if the affected characters are used) but a pointer to docs/examples/fo/fonts.fo seemes to resolve the issue. Yes, a new patch from Rainer would be nice. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[GUMP] Build Failure - xml-fop
This email is autogenerated from the output from: http://jakarta.apache.org/builds/gump/2002-05-16/xml-fop.html Buildfile: build.xml init-avail: init-filters-xalan2: [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen init: [echo] --- Fop 1.0dev [1999-2002] prepare: [echo] Preparing the build directories [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph [copy] Copying 3 files to /home/rubys/jakarta/xml-fop/build/classes/conf codegen: [echo] Resetting codegen directory [copy] Copying 30 files to /home/rubys/jakarta/xml-fop/build/src/codegen [echo] Generating the java files from xml resources [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/allprops.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/Constants.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/genconst.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/fo_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl [style] home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl:178:42: Fatal Error! Variable accessed before it is bound! [style] Failed to process /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml BUILD FAILED /home/rubys/jakarta/xml-fop/build.xml:420: Fatal error during transformation Total time: 14 seconds - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Compile error with FOP
Hy Keiron.
I suppose you have an SCM problem with Batik class. The actual release
delivered with FOP last build xml-fop_20020516103601.tar.gz
As you wrote PDFGraphics2D.java, I send you that mail. As I'm not very
graphics today, I just wrote this empty method
public VolatileImage createCompatibleVolatileImage(int width, int
height){
return null;
}
in the source, to perform Fop build.
But running result build, I get the following.
..
[DEBUG] fo:block: handleWhiteSpace
[DEBUG] fo:block: handleWhiteSpace
[DEBUG] fo:block: handleWhiteSpace
[DEBUG] fo:block: handleWhiteSpace
LineBPLayoutManager.initProperties called
PageMaster.makePage
InlineStackingBPLayoutManager.initProperties called
WARNING: child LM not a BPLayoutManager:
org.apache.fop.layoutmgr.BlockLayoutManager
null
org.apache.fop.apps.FOPException
at org.apache.fop.apps.Driver.render(Driver.java:478)
at
org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:71)
at org.apache.fop.apps.Fop.main(Fop.java:18)
-
java.lang.NullPointerException
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1094)
at org.apache.fop.apps.Driver.render(Driver.java:473)
at
org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:71)
at org.apache.fop.apps.Fop.main(Fop.java:18)
-
java.lang.NullPointerException
at
org.apache.fop.layoutmgr.LineBPLayoutManager.getNextBreakPoss(LineBPLayoutMa
nager.java:249)
at
org.apache.fop.layoutmgr.LineBPLayoutManager.generateAreas(LineBPLayoutManag
er.java:413)
at
org.apache.fop.layoutmgr.BlockLayoutManager.generateAreas(BlockLayoutManager
.java:96)
at
org.apache.fop.layoutmgr.BlockLayoutManager.generateAreas(BlockLayoutManager
.java:96)
at
org.apache.fop.layoutmgr.AbstractLayoutManager.generateAreas(AbstractLayoutM
anager.java:65)
at
org.apache.fop.layoutmgr.AbstractLayoutManager.generateAreas(AbstractLayoutM
anager.java:65)
at
org.apache.fop.layoutmgr.PageLayoutManager.run(PageLayoutManager.java:67)
at
org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:332)
at
org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:195)
at
org.apache.fop.fo.pagination.PageSequence.end(PageSequence.java:281)
at
org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:122)
at
org.apache.xerces.parsers.SAXParser.endElement(SAXParser.java:1403)
at
org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLValidator
.java:1480)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1149)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1081)
at org.apache.fop.apps.Driver.render(Driver.java:473)
at
org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:71)
at org.apache.fop.apps.Fop.main(Fop.java:18)
.
I would like to give more help to the project, but as I need longer than
24Hours per day currently...
Thanks to work actively with FOP.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
AW: direct rendering of images to pdf
These notes apply to fo:external-graphic under FOP 0.20.1: o FOP images are kept as XObjects until the end of job, because - the image is written to the output file - and the complete image object is added to the XObjects vector in order to build the ressource dictionary at the end of the PDF document. But the ressource dictionary needs only PDF object references - not the images themselves. So if the addImage-method of PDFDocument-class is changed like this, only images within a page are kept in memory. old code: this.xObjects.add(xObject); this.xObjectsMap.put(url, xObject); deleted: does not hurt, because never written new code: this.xObjects.addElement(new PDFXObject(this.objectcount, this.xObjectCount)); // just adding an object ID as reference does it Still memory usage rises from start to end of job: most likely FOP images hang forever uncompressed in the area tree. Hansuli Anderegg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Font Metrics AWT
I have found the problem and worked out its repair.
The modified code is attached below.
The problem stems from a bug in java's handling of drawing of
AttributedStrings when a font attribute is specified. Bug parade
#4650042 describes a similar problem unique to jdk 1.4, but
makes also suggests that there are other more general problems
w/ fonts and AttributedStrings.
In our case, calling
drawString (string) instead of
drawString (AttributedString...) solves the problem.
The fix simply draws the text using the string version of
drawString and then to draw the underline (if defined)
separately.
I have tested it on jre 1.3.0, jre 1.3.0_02 and jre/jdk 1.4.0 -
all on WinNT4/sp5
attached is the changed code -- it only affects one method
in AWTRenderer.
Will someone commit it ?
At 09:12 AM 5/10/02, you wrote:
Hi all!
Now I've downloaded the sdk version 1.3.1_03 from sun but the result is the
same like before.
I've attached a screenshot to this mail.
My workflow:
I go to the Driver, set the Logger and my Renderer(extended from
AWTRenderer), and call render(XMLReader,InputSource) on the Driver,
After that I go to my Renderer and render each page in a loop and add the
result within a JLabel to a JPanel, which is showing for the User.
code piece:
driver.render( parser, inputHandler.getInputSource() );
for (int i = 0; i renderer.getNumberOfPages(); i++)
{
renderer.render(i);
JLabel label = new JLabel( new ImageIcon(
renderer.getLastRenderedPage() ) );
panel.add( label, new GridBagConstraints(0, i, 1, 1, 0.0, 0.0
,GridBagConstraints.WEST, GridBagConstraints.NONE, new
Insets(6, 6, 6,
6), 0, 0));
}
the result is below
Can anyone help me or tell me my mistake?
ThanX Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
' Best,
-Ralph LaChance
AWTRenderer.renderWordArea.zip
Description: Zip archive
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: new batik
Keiron Liddle schrieb: Hi, Since a new beta of batik has been released I think we can go with this for the next release. I will put the new batik into cvs and update the code to work with it. Is it possible to make Fop work without batik.jar ? (of course if no svg is used) Keiron. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Character encoding on other platforms (previously os/390)
[EMAIL PROTECTED] schrieb: I've had a couple folks ask me for the modified code so the proper character encoding is returned on the toString().getBytes() is US-ASCII. This is cool that other people besides me need this. [..] I downloaded this snapshot xml-fop_20020515162132 and I don't see any modification to the code. Is this change going to be incorporated or has been incorporated in a way that I missed? It hasn't been incorporated yet but it's on my todo list and should be in the next maintenance release. Many Thanks, Jason West Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: status on website
Keiron Liddle schrieb: Hi, I added some status info to the website. So hopefully this will answer Cool some peoples questions (I'm sure they will still want to know more things that are unknown). Sure ;-) Any comments, complaints, suggestions? (apart from my poor spelling!) Maybe put it on top of the page (or an extra page?) I fear quite a few people won't scroll down that far ... Keiron. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
AW: new batik
Hello Christian, yes, it is possible to run FOP without batik, but you have to change the source. You have to remove all the imports to packages svg... and kick out all the references to classes having to do with svg. In fact we did this and we have a working version based on FOP 0.20.3 running without batik and producing nice PDF/PostScript/AWT (without svg). We had to do this since we are running FOP with VisualAge+WebSphere on jdk 1.2.2. Hope this helps. Greetings, Patrick Dipl. Inform. Patrick Chaumette T-Systems ITS GmbH Service Prozesse Retail Hausanschrift: Fasanenweg 9, 70771 Leinfelden-Echterdingen Postanschrift: Postfach 100258, 70746 Leinfelden-Echterdingen Telefon: (0711)972-2437 Telefax: (0711)972-1949 E-Mail: [EMAIL PROTECTED] Internet: http://www.t-systems.de -Ursprüngliche Nachricht- Von: Christian Geisert [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 16. Mai 2002 17:53 An: [EMAIL PROTECTED] Betreff: Re: new batik Keiron Liddle schrieb: Hi, Since a new beta of batik has been released I think we can go with this for the next release. I will put the new batik into cvs and update the code to work with it. Is it possible to make Fop work without batik.jar ? (of course if no svg is used) Keiron. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Compile error with FOP
GALLO Jean-Claude wrote: I suppose you have an SCM problem with Batik class. The actual release delivered with FOP last build xml-fop_20020516103601.tar.gz ... But running result build, I get the following. .. WARNING: child LM not a BPLayoutManager: org.apache.fop.layoutmgr.BlockLayoutManager null ... java.lang.NullPointerException at org.apache.fop.layoutmgr.LineBPLayoutManager.getNextBreakPoss(LineBPLayoutMa You appear to have donwload a development snapshot. They don't work at all. Get a regular distribution, the last one is 0.20.3 J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
