[GUMP] Build Failure - xml-fop
This email is autogenerated from the output from: http://cvs.apache.org/builds/gump/2003-03-05/xml-fop.html Buildfile: build.xml Caught exception (org.apache.tools.ant.BuildException) while expanding libs-run-classpath: /home/rubys/jakarta/xml-fop/build not found. init-avail: init-filters-jdk14: [echo] JDK 1.4 present. [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen init-filters-jdk13: init: [echo] --- Fop 1.0dev [1999-2003] [echo] See build.properties and build-local.properties for additional build settings [filter] Reading filters from /home/rubys/jakarta/xml-fop/build/src/codegen/filter prepare: [echo] Preparing the build directories [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/gensrc [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fo/properties [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14 [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph codegen: [echo] Resetting codegen directory [copy] Copying 33 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/gensrc/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/gensrc/org/apache/fop/fo/properties/fo_ignore_this.dummy [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fo/properties/FOPropertyMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/propmap.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fo/properties/foenums_ignore_this.dummy [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/encodings.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/CodePointMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/Courier.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/Courier.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/CourierOblique.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/CourierOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/CourierBold.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/CourierBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/CourierBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/CourierBoldOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/Helvetica.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/Helvetica.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/HelveticaBold.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/HelveticaBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/HelveticaOblique.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/HelveticaOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/HelveticaBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/gensrc/org/apache/fop/fonts/base14/HelveticaBoldOblique.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/TimesRoman.xml to
Re: batik transcoders
Hi Keiron On 05.03.2003 04:18:39 Keiron Liddle wrote: The PDF transcoder could be packaged with Batik so that it can be used by users of Batik only and also used independanlty from the rest of FOP. You mean Batik will have pdf-transcoder.jar and ps-transcoder.jar in their distributions? Not the source, right? What about factoring out the code for the transcoders and supporting classes (like fonts) into a separate container/subproject accessible by both the FOP and Batik teams? XML-Commons, maybe? That way we could encourage the Batik guys to participate in the future development of the PDF- and PS-related SVG stuff. Just a thought. So will there be any problems. There is th/e pdf-transcoder build target that creates the transcoder jar. We could create a tag for the release (call it beta2?). We do need to make it clear that a FOP release cannot be used at the same time as this jar due to various changes. +1. We could give the transcoders a bit more visibility on our site. The PDF transcoder seems to be working fine. There are a couple of problems. Issues: - the use of avalon Enumeration requires avalon in the path. It is only used as an interface for one of the font classes, do we really need that Not really at the moment. But as soon as I have this licensing issues and an initial release of my barcode package behind me, I wanted to go into full Avalon-refactoring mode. And that brings some more Avalon stuff into FOP especially the renderers, fonts and image support. I'd like to propose this: - I'll modify the build so we can generate a raw pdf-transcoder.jar as it is now (needs avalon-framework.jar), but along with another (pdf-transcoder-all.jar) that also contains the necessary Avalon classes. - I'll do the documentation involved. - do we need all of the font classes for transcoding, which ones can be left out ATM the PFM parser and the apps subpackage are the only ones that can be left out, I think. There are some minor bugs with patterns in patterns, drawing images and fonts but there won't be any fixes soon. Wouldn't it make sense to work with the Batik team to get the PDF and PS transcoders into their test infrastructure so we have some good feedback and can quickly improve on the quality to match the AWT output? Also what is the status of the PS transcoder? Could this be included. I haven't set up the PS transcoder, yet. But I could do that soon. I'm still hoping for George to send in a patch for his PostScript work. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/svg SVGElement.java
jeremias2003/03/05 07:08:45
Modified:src/org/apache/fop/svg SVGElement.java
Log:
Make it compile with latest Batik CVS. The new methods will throw an NYI ATM!
Long license
Revision ChangesPath
1.34 +64 -6 xml-fop/src/org/apache/fop/svg/SVGElement.java
Index: SVGElement.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/svg/SVGElement.java,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- SVGElement.java 10 Sep 2002 15:07:13 - 1.33
+++ SVGElement.java 5 Mar 2003 15:08:45 - 1.34
@@ -1,10 +1,53 @@
/*
* $Id$
- * Copyright (C) 2001-2002 The Apache Software Foundation. All rights reserved.
- * For details on use and redistribution please refer to the
- * LICENSE file included with these sources.
- */
-
+ *
+ *The Apache Software License, Version 1.1
+ *
+ *
+ * Copyright (C) 1999-2003 The Apache Software Foundation. All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without modifica-
+ * tion, are permitted provided that the following conditions are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright notice,
+ *this list of conditions and the following disclaimer.
+ *
+ * 2. Redistributions in binary form must reproduce the above copyright notice,
+ *this list of conditions and the following disclaimer in the documentation
+ *and/or other materials provided with the distribution.
+ *
+ * 3. The end-user documentation included with the redistribution, if any, must
+ *include the following acknowledgment: This product includes software
+ *developed by the Apache Software Foundation (http://www.apache.org/).
+ *Alternately, this acknowledgment may appear in the software itself, if
+ *and wherever such third-party acknowledgments normally appear.
+ *
+ * 4. The names FOP and Apache Software Foundation must not be used to
+ *endorse or promote products derived from this software without prior
+ *written permission. For written permission, please contact
+ *[EMAIL PROTECTED]
+ *
+ * 5. Products derived from this software may not be called Apache, nor may
+ *Apache appear in their name, without prior written permission of the
+ *Apache Software Foundation.
+ *
+ * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
+ * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+ * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+ * APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+ * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU-
+ * DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
+ * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+ * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ *
+ *
+ * This software consists of voluntary contributions made by many individuals
+ * on behalf of the Apache Software Foundation and was originally created by
+ * James Tauber [EMAIL PROTECTED]. For more information on the Apache
+ * Software Foundation, please see http://www.apache.org/.
+ */
package org.apache.fop.svg;
// FOP
@@ -91,6 +134,21 @@
return new Rectangle2D.Double(0, 0, view.getX(), view.getY());
}
+/**
+ * Returns the transform from the global transform space to pixels.
+ */
+public AffineTransform getScreenTransform() {
+throw new UnsupportedOperationException(NYI);
+}
+
+/**
+ * Sets the transform to be used from the global transform space
+ * to pixels.
+ */
+public void setScreenTransform(AffineTransform at) {
+throw new UnsupportedOperationException(NYI);
+}
+
public AffineTransform getCTM() {
return new AffineTransform();
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ASCII text output and pagination
Hi all, I'm using FOP to generate PDF and corresponding ASCII text output files. I'm using FOP to generate the corresponding ASCII output instead of just straight XSL because the reports I'm creating contain many tables with varying widths and columns. I also didn't want to have to worry about line breaking. The ASCII text output is actually working quite nicely. Figuring out what font-family (Courier), font-size (7.3pt), and line-height (10.5pt) to use solved the problems I was having with missing spaces and sequential lines in the output overlaying one another. There is still one problem I need to solve - pagination. The text output files that I'm creating do not need pagination, since they are just one long virtual page. But FOP is inserting page breaks at the page boundries. Is there a way to tell FOP not to insert page breaks in text mode? I know I can solve the problem by creating a simple-page-master with an arbitrarily long page-height, and then do some post-processing on the generated output file. But I thought I'd see if there's a more elegant solution. If FOP cannot currently surpress page breaks in text mode, how hard would it be for me to add this functionality myself? Can anybody familiar with the ASCII renderer point me where to look? Thanks! -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: ASCII text output and pagination
The correct thing to do whould be to use media-usage=bounded-in-one-dimension on fo:root. The problem is that this isn't implemented in FOP, yet. And it's not only a matter of changing the ASCII renderer, I'm afraid. You would have to teach the layout engine not to make any page breaks and to increase the page length as necessary. If you decide to try fixing that I would recommend you to work with us on the redesign to implement this feature because the maintenance branch (from which 0.20.5 originates) will soon be discontinued. The other problem is that the ASCII renderer hasn't been brought back in the redesign. So it would involve helping us with that one, too. On 05.03.2003 16:14:54 Illiano, Vincent wrote: Hi all, I'm using FOP to generate PDF and corresponding ASCII text output files. I'm using FOP to generate the corresponding ASCII output instead of just straight XSL because the reports I'm creating contain many tables with varying widths and columns. I also didn't want to have to worry about line breaking. The ASCII text output is actually working quite nicely. Figuring out what font-family (Courier), font-size (7.3pt), and line-height (10.5pt) to use solved the problems I was having with missing spaces and sequential lines in the output overlaying one another. There is still one problem I need to solve - pagination. The text output files that I'm creating do not need pagination, since they are just one long virtual page. But FOP is inserting page breaks at the page boundries. Is there a way to tell FOP not to insert page breaks in text mode? I know I can solve the problem by creating a simple-page-master with an arbitrarily long page-height, and then do some post-processing on the generated output file. But I thought I'd see if there's a more elegant solution. If FOP cannot currently surpress page breaks in text mode, how hard would it be for me to add this functionality myself? Can anybody familiar with the ASCII renderer point me where to look? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: ASCII text output and pagination
Hi Jeremias, Thanks for the quick response. I am willing to add media-usage support to FOP. I have a couple of questions on this, though. Given that I need this functionality now, if I add it to the redesigned FOP branch, when will I be able to use it? When will the first release of the redesiged FOP be available? If I decide to put the support in the maintainance branch because I need it now, would it be difficult to port it later to the new FOP? I guess we should also ask the question if there are other FOP users out there who would like to see ASCII support in the redesigned FOP. I, personally, have found it very useful! One more thing. I am not familiar with the layout engines. How difficult will it be to teach it not to make page breaks and to increase the page length dynamically? Thanks again for your response, -Vincent -- From: Jeremias Maerki[SMTP:[EMAIL PROTECTED] Reply To: [EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 10:28 AM To: [EMAIL PROTECTED] Subject: Re: ASCII text output and pagination The correct thing to do whould be to use media-usage=bounded-in-one-dimension on fo:root. The problem is that this isn't implemented in FOP, yet. And it's not only a matter of changing the ASCII renderer, I'm afraid. You would have to teach the layout engine not to make any page breaks and to increase the page length as necessary. If you decide to try fixing that I would recommend you to work with us on the redesign to implement this feature because the maintenance branch (from which 0.20.5 originates) will soon be discontinued. The other problem is that the ASCII renderer hasn't been brought back in the redesign. So it would involve helping us with that one, too. On 05.03.2003 16:14:54 Illiano, Vincent wrote: Hi all, I'm using FOP to generate PDF and corresponding ASCII text output files. I'm using FOP to generate the corresponding ASCII output instead of just straight XSL because the reports I'm creating contain many tables with varying widths and columns. I also didn't want to have to worry about line breaking. The ASCII text output is actually working quite nicely. Figuring out what font-family (Courier), font-size (7.3pt), and line-height (10.5pt) to use solved the problems I was having with missing spaces and sequential lines in the output overlaying one another. There is still one problem I need to solve - pagination. The text output files that I'm creating do not need pagination, since they are just one long virtual page. But FOP is inserting page breaks at the page boundries. Is there a way to tell FOP not to insert page breaks in text mode? I know I can solve the problem by creating a simple-page-master with an arbitrarily long page-height, and then do some post-processing on the generated output file. But I thought I'd see if there's a more elegant solution. If FOP cannot currently surpress page breaks in text mode, how hard would it be for me to add this functionality myself? Can anybody familiar with the ASCII renderer point me where to look? Jeremias Maerki - 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: ASCII text output and pagination
On 05.03.2003 16:53:15 Illiano, Vincent wrote: Thanks for the quick response. I am willing to add media-usage support to FOP. I have a couple of questions on this, though. Given that I need this functionality now, if I add it to the redesigned FOP branch, when will I be able to use it? If the functionality available in the redesign already fits your needs (check that please) you can start using it immediately. Just download it from CVS as indicated on our website. When will the first release of the redesiged FOP be available? Unknown. There's still a lot to do. But please do have a look at the redesign. If I decide to put the support in the maintainance branch because I need it now, would it be difficult to port it later to the new FOP? I think, yes. The reason is that the layout engine is completely different. The renderers are still pretty similar, but your functionality need to be implemented in the layout engine. I guess we should also ask the question if there are other FOP users out there who would like to see ASCII support in the redesigned FOP. I, personally, have found it very useful! One more thing. I am not familiar with the layout engines. How difficult will it be to teach it not to make page breaks and to increase the page length dynamically? Hmm, I can't answer that off-hand. I'm the peripheral guy here, sort of, read: specialist for everything but layout. :-) I hope Keiron can answer that. If you need your functionality real quick, I suggest you go the post-processing way. But it would certainly be cool to have new people jump in and help. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: ASCII text output and pagination
Ok, I think I'd like to pursue 2 possibilities. If someone out there listening in on this discussion can give me a pointer to the ASCII layout engine and a pointer on how to teach it to increment to page length, then I will take a shot at implementing bounding-in-one-dimension in the maintainance branch at least. If some of the more experienced FOP developers agree with me that ASCII rendered output support would be a nice feature for the redesigned FOP, and it's feasible, then I'd like to contribute. Thoughts, suggestions? Thanks, -Vincent -- From: Jeremias Maerki[SMTP:[EMAIL PROTECTED] Reply To: [EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 11:07 AM To: [EMAIL PROTECTED] Subject: Re: ASCII text output and pagination On 05.03.2003 16:53:15 Illiano, Vincent wrote: Thanks for the quick response. I am willing to add media-usage support to FOP. I have a couple of questions on this, though. Given that I need this functionality now, if I add it to the redesigned FOP branch, when will I be able to use it? If the functionality available in the redesign already fits your needs (check that please) you can start using it immediately. Just download it from CVS as indicated on our website. When will the first release of the redesiged FOP be available? Unknown. There's still a lot to do. But please do have a look at the redesign. If I decide to put the support in the maintainance branch because I need it now, would it be difficult to port it later to the new FOP? I think, yes. The reason is that the layout engine is completely different. The renderers are still pretty similar, but your functionality need to be implemented in the layout engine. I guess we should also ask the question if there are other FOP users out there who would like to see ASCII support in the redesigned FOP. I, personally, have found it very useful! One more thing. I am not familiar with the layout engines. How difficult will it be to teach it not to make page breaks and to increase the page length dynamically? Hmm, I can't answer that off-hand. I'm the peripheral guy here, sort of, read: specialist for everything but layout. :-) I hope Keiron can answer that. If you need your functionality real quick, I suggest you go the post-processing way. But it would certainly be cool to have new people jump in and help. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/area/inline Viewport.java Word.java Container.java InlineParent.java Character.java UnresolvedPageNumber.java ForeignObject.java InlineArea.java Anchor.java Leader.java Image.java FilledArea.java Space.java
jeremias2003/03/05 08:45:43 Modified:src/org/apache/fop/area/inline Viewport.java Word.java Container.java InlineParent.java Character.java UnresolvedPageNumber.java ForeignObject.java InlineArea.java Anchor.java Leader.java Image.java FilledArea.java Space.java Log: Switched to long licence Revision ChangesPath 1.7 +49 -6 xml-fop/src/org/apache/fop/area/inline/Viewport.java Index: Viewport.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/area/inline/Viewport.java,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- Viewport.java 14 Nov 2002 11:13:33 - 1.6 +++ Viewport.java 5 Mar 2003 16:45:42 - 1.7 @@ -1,10 +1,53 @@ /* * $Id$ - * Copyright (C) 2001-2002 The Apache Software Foundation. All rights reserved. - * For details on use and redistribution please refer to the - * LICENSE file included with these sources. - */ - + * + *The Apache Software License, Version 1.1 + * + * + * Copyright (C) 1999-2003 The Apache Software Foundation. All rights reserved. + * + * Redistribution and use in source and binary forms, with or without modifica- + * tion, are permitted provided that the following conditions are met: + * + * 1. Redistributions of source code must retain the above copyright notice, + *this list of conditions and the following disclaimer. + * + * 2. Redistributions in binary form must reproduce the above copyright notice, + *this list of conditions and the following disclaimer in the documentation + *and/or other materials provided with the distribution. + * + * 3. The end-user documentation included with the redistribution, if any, must + *include the following acknowledgment: This product includes software + *developed by the Apache Software Foundation (http://www.apache.org/). + *Alternately, this acknowledgment may appear in the software itself, if + *and wherever such third-party acknowledgments normally appear. + * + * 4. The names FOP and Apache Software Foundation must not be used to + *endorse or promote products derived from this software without prior + *written permission. For written permission, please contact + *[EMAIL PROTECTED] + * + * 5. Products derived from this software may not be called Apache, nor may + *Apache appear in their name, without prior written permission of the + *Apache Software Foundation. + * + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, + * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND + * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + * APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, + * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU- + * DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS + * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON + * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF + * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + * + * + * This software consists of voluntary contributions made by many individuals + * on behalf of the Apache Software Foundation and was originally created by + * James Tauber [EMAIL PROTECTED]. For more information on the Apache + * Software Foundation, please see http://www.apache.org/. + */ package org.apache.fop.area.inline; import org.apache.fop.area.Area; 1.10 +49 -6 xml-fop/src/org/apache/fop/area/inline/Word.java Index: Word.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/area/inline/Word.java,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- Word.java 23 Jan 2003 18:59:08 - 1.9 +++ Word.java 5 Mar 2003 16:45:42 - 1.10 @@ -1,10 +1,53 @@ /* * $Id$ - * Copyright (C) 2001-2002 The Apache Software Foundation. All rights reserved. - * For details on use and redistribution please refer to the - * LICENSE file included with these sources. - */ - + * + *The Apache Software License, Version 1.1 + *
DO NOT REPLY [Bug 17681] New: - Margin attributes not suported
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=17681. 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=17681 Margin attributes not suported Summary: Margin attributes not suported Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Margins are not supported for fo:block, fo:block-container, fo:table-cell (except margin-left which renders well) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.3 - New directory
pietsch 2003/03/05 10:54:28 xml-fop/src/java-1.3 - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.3/org - New directory
pietsch 2003/03/05 10:54:38 xml-fop/src/java-1.3/org - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.3/org/apache - New directory
pietsch 2003/03/05 10:55:12 xml-fop/src/java-1.3/org/apache - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.3/org/apache/fop - New directory
pietsch 2003/03/05 10:55:20 xml-fop/src/java-1.3/org/apache/fop - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.3/org/apache/fop/pdf - New directory
pietsch 2003/03/05 10:55:29 xml-fop/src/java-1.3/org/apache/fop/pdf - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.4 - New directory
pietsch 2003/03/05 10:56:00 xml-fop/src/java-1.4 - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.4/org - New directory
pietsch 2003/03/05 10:56:09 xml-fop/src/java-1.4/org - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.4/org/apache - New directory
pietsch 2003/03/05 10:56:17 xml-fop/src/java-1.4/org/apache - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.4/org/apache/fop - New directory
pietsch 2003/03/05 10:56:25 xml-fop/src/java-1.4/org/apache/fop - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/java-1.4/org/apache/fop/pdf - New directory
pietsch 2003/03/05 10:56:33 xml-fop/src/java-1.4/org/apache/fop/pdf - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/render/pdf PDFRenderer.java
pietsch 2003/03/05 10:58:16
Modified:.Tag: fop-0_20_2-maintain build.xml
src/org/apache/fop/apps Tag: fop-0_20_2-maintain
CommandLineOptions.java
src/org/apache/fop/pdf Tag: fop-0_20_2-maintain
PDFDocument.java PDFXObject.java
src/org/apache/fop/render/pdf Tag: fop-0_20_2-maintain
PDFRenderer.java
Added: src/java-1.3/org/apache/fop/pdf Tag: fop-0_20_2-maintain
PDFEncryption.java
src/java-1.4/org/apache/fop/pdf Tag: fop-0_20_2-maintain
PDFEncryption.java
Log:
Added PDF encryption.
Submitted by: Patrick C. Lankswert [EMAIL PROTECTED]
Revision ChangesPath
No revision
No revision
1.44.2.38 +10 -3 xml-fop/build.xml
Index: build.xml
===
RCS file: /home/cvs/xml-fop/build.xml,v
retrieving revision 1.44.2.37
retrieving revision 1.44.2.38
diff -u -r1.44.2.37 -r1.44.2.38
--- build.xml 18 Feb 2003 12:27:34 - 1.44.2.37
+++ build.xml 5 Mar 2003 18:58:14 - 1.44.2.38
@@ -189,7 +189,7 @@
tstamp/
property name=Name value=Fop/
property name=name value=fop/
-property name=version value=0.20.5rc2/
+property name=version value=0.20.5rc3/
filter token=version value=${version}/
property name=year value=1999-2003/
@@ -302,11 +302,17 @@
target name=init-filters-jdk13 depends=init-avail unless=jdk14.present
echo message=JDK 1.3 or earlier present./
copy file=src/codegen/jdk13.filter toFile=build/src/codegen/filter/
+copy todir=build/src
+ fileset dir=src/java-1.3/
+/copy
/target
target name=init-filters-jdk14 depends=init-avail if=jdk14.present
echo message=JDK 1.4 present./
copy file=src/codegen/jdk14.filter toFile=build/src/codegen/filter/
+copy todir=build/src
+ fileset dir=src/java-1.4/
+/copy
/target
@@ -371,8 +377,9 @@
target name=prepare-src depends=prepare, prepare-jimi, prepare-jai,
prepare-trax
!-- copy src files --
copy todir=${build.src} filtering=yes
- fileset dir=${src.dir}
-
excludes=**/${jimi},**/${jai},**/${tiff},**/${xsltransform},**/${trax},**/apps/TraxInputHandler.java/
+ fileset dir=${src.dir}
+includes=**/*.java
+
excludes=java-*/**,**/${jimi},**/${jai},**/${tiff},**/${xsltransform},**/${trax},**/apps/TraxInputHandler.java/
filterset
filter token=XSLFO-STD value=${xslfo.std}/
filter token=XSLFO-STDID value=${xslfo.std.id}/
No revision
No revision
1.1.2.1 +156 -0xml-fop/src/java-1.3/org/apache/fop/pdf/Attic/PDFEncryption.java
No revision
No revision
1.1.2.1 +421 -0xml-fop/src/java-1.4/org/apache/fop/pdf/Attic/PDFEncryption.java
No revision
No revision
1.14.2.10 +95 -30xml-fop/src/org/apache/fop/apps/CommandLineOptions.java
Index: CommandLineOptions.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/apps/CommandLineOptions.java,v
retrieving revision 1.14.2.9
retrieving revision 1.14.2.10
diff -u -r1.14.2.9 -r1.14.2.10
--- CommandLineOptions.java 25 Feb 2003 10:18:31 - 1.14.2.9
+++ CommandLineOptions.java 5 Mar 2003 18:58:15 - 1.14.2.10
@@ -147,6 +147,26 @@
}
+private boolean pdfEncryptionAvailable = false;
+private boolean pdfEncryptionChecked = false;
+private boolean encryptionAvailable() {
+if (!pdfEncryptionChecked) {
+try {
+Class c = Class.forName(javax.crypto.Cipher);
+pdfEncryptionAvailable
+= org.apache.fop.pdf.PDFEncryption.encryptionAvailable();
+}
+catch(ClassNotFoundException e) {
+pdfEncryptionAvailable = false;
+}
+pdfEncryptionChecked = true;
+if (!pdfEncryptionAvailable) {
+log.warn(PDF encryption not available.);
+}
+}
+return pdfEncryptionAvailable;
+}
+
/**
* parses the commandline arguments
* @return true if parse was successful and procesing can continue, false if
processing should stop
@@ -219,6 +239,44 @@
outfile = new File(args[i + 1]);
i++;
}
+} else if (args[i].equals(-o)) {
+if ((i + 1 == args.length) || (args[i + 1].charAt(0) == '-')) {
+
cvs commit: xml-fop CHANGES
pietsch 2003/03/05 11:02:05 Modified:.Tag: fop-0_20_2-maintain CHANGES Log: Update CHANGES for PDF encryption. Revision ChangesPath No revision No revision 1.10.2.53 +3 -0 xml-fop/CHANGES Index: CHANGES === RCS file: /home/cvs/xml-fop/CHANGES,v retrieving revision 1.10.2.52 retrieving revision 1.10.2.53 diff -u -r1.10.2.52 -r1.10.2.53 --- CHANGES 2 Mar 2003 16:55:15 - 1.10.2.52 +++ CHANGES 5 Mar 2003 19:02:05 - 1.10.2.53 @@ -1,5 +1,8 @@ == Done since 0.20.4 release +- Added PDF encryption. Available options: no printing, no copy, no + edit, no annotations. + Submitted by Patrick C. Lankswert [EMAIL PROTECTED] - Fixed text alingment for lines containing forward pointing page number citations. This should greatly improve TOC layout. (J.Pietschmann) - Fixed repeatedly laid out small caps text (for example in static - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encryption
Patrick C. Lankswert wrote: Add jce-jdk13-118.jar (for 1.3.x) to %JAVA_HOME%\jre\lib\ext and add security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider to %JAVA_HOME%\jre\lib\security\java.security in the appropriate section. This should work. This is how it is done to support any implementation. Thank you, I already discovered this myself last night. It was just that shutting down the work environment in order to re-login as Administrator for changing java.security at 2:10am isn't worth it, so I decided to go to bed. Now everything runs well and is already committed to the maintenance branch, I'll update the docs and HEAD later. IF you would like it HARD CODED to bouncy castle's implementation which does not require the java.security changes, It's probably a bad idea to tie FOP to a specific provider. In particular as Mozilla also has an Open Source implementation, which is perhaps even faster due to native code (anybody ready to try it?) J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
inline-container support
Hi! I've got a fo-task for which I need a working fo:inline-container-object. This feature seems not to be implemented in the 0.20.x-version. I would like to know weather support for this element is planned for the coming versions (maintenance or redesigned-branch). Are any milestones planned? Would it be possible / difficult to take part in the implementation-process myself if no support is planned? Best regards, Jens Wissmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: inline-container support
Jens Wissmann wrote: I would like to know weather support for this element is planned for the coming versions (maintenance or redesigned-branch). Are any milestones planned? No, yes, and no. Would it be possible / difficult to take part in the implementation-process myself if no support is planned? If youcan supply an explicit width, either absolute or as percentage of the width of the parent block, it's not all that hard: create a block area and add lines until you run out of either content or bpd. Then the more tricky aspects kick in: what to do if the bpd ends first, and how to vertical-align the whole beast. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/extensions Outline.java ExtensionElementMapping.java Label.java BookmarkData.java ExtensionObj.java Bookmarks.java
jeremias2003/03/05 12:40:18 Modified:src/org/apache/fop/extensions Outline.java ExtensionElementMapping.java Label.java BookmarkData.java ExtensionObj.java Bookmarks.java Log: Switched to long licence Revision ChangesPath 1.10 +49 -6 xml-fop/src/org/apache/fop/extensions/Outline.java Index: Outline.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/extensions/Outline.java,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- Outline.java 13 Sep 2002 09:29:49 - 1.9 +++ Outline.java 5 Mar 2003 20:40:18 - 1.10 @@ -1,10 +1,53 @@ /* * $Id$ - * Copyright (C) 2001-2002 The Apache Software Foundation. All rights reserved. - * For details on use and redistribution please refer to the - * LICENSE file included with these sources. - */ - + * + *The Apache Software License, Version 1.1 + * + * + * Copyright (C) 1999-2003 The Apache Software Foundation. All rights reserved. + * + * Redistribution and use in source and binary forms, with or without modifica- + * tion, are permitted provided that the following conditions are met: + * + * 1. Redistributions of source code must retain the above copyright notice, + *this list of conditions and the following disclaimer. + * + * 2. Redistributions in binary form must reproduce the above copyright notice, + *this list of conditions and the following disclaimer in the documentation + *and/or other materials provided with the distribution. + * + * 3. The end-user documentation included with the redistribution, if any, must + *include the following acknowledgment: This product includes software + *developed by the Apache Software Foundation (http://www.apache.org/). + *Alternately, this acknowledgment may appear in the software itself, if + *and wherever such third-party acknowledgments normally appear. + * + * 4. The names FOP and Apache Software Foundation must not be used to + *endorse or promote products derived from this software without prior + *written permission. For written permission, please contact + *[EMAIL PROTECTED] + * + * 5. Products derived from this software may not be called Apache, nor may + *Apache appear in their name, without prior written permission of the + *Apache Software Foundation. + * + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, + * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND + * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + * APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, + * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU- + * DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS + * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON + * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF + * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + * + * + * This software consists of voluntary contributions made by many individuals + * on behalf of the Apache Software Foundation and was originally created by + * James Tauber [EMAIL PROTECTED]. For more information on the Apache + * Software Foundation, please see http://www.apache.org/. + */ package org.apache.fop.extensions; import org.apache.fop.fo.FONode; 1.10 +49 -6 xml-fop/src/org/apache/fop/extensions/ExtensionElementMapping.java Index: ExtensionElementMapping.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/extensions/ExtensionElementMapping.java,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- ExtensionElementMapping.java 13 Sep 2002 09:29:49 - 1.9 +++ ExtensionElementMapping.java 5 Mar 2003 20:40:18 - 1.10 @@ -1,10 +1,53 @@ /* * $Id$ - * Copyright (C) 2001-2002 The Apache Software Foundation. All rights reserved. - * For details on use and redistribution please refer to the - * LICENSE file included with these sources. - */ - + * + *The Apache Software License, Version 1.1 + * + * + *
cvs commit: xml-fop/src/org/apache/fop/fo/expr InheritedPropFunction.java FopPropValFunction.java PropertyParser.java FromTableColumnFunction.java PropertyException.java PPColWidthFunction.java Function.java AbsFunction.java NumericProperty.java MaxFunction.java LabelEndFunction.java RGBColorFunction.java FloorFunction.java NearestSpecPropFunction.java CeilingFunction.java RoundFunction.java BodyStartFunction.java FunctionBase.java MinFunction.java NCnameProperty.java FromParentFunction.java PropertyTokenizer.java
jeremias2003/03/05 13:59:48 Modified:src/org/apache/fop/fo/expr InheritedPropFunction.java FopPropValFunction.java PropertyParser.java FromTableColumnFunction.java PropertyException.java PPColWidthFunction.java Function.java AbsFunction.java NumericProperty.java MaxFunction.java LabelEndFunction.java RGBColorFunction.java FloorFunction.java NearestSpecPropFunction.java CeilingFunction.java RoundFunction.java BodyStartFunction.java FunctionBase.java MinFunction.java NCnameProperty.java FromParentFunction.java PropertyTokenizer.java Log: Switched to long licence Some general checkstyle fixing Revision ChangesPath 1.3 +49 -6 xml-fop/src/org/apache/fop/fo/expr/InheritedPropFunction.java Index: InheritedPropFunction.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/expr/InheritedPropFunction.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- InheritedPropFunction.java30 Jul 2001 20:29:21 - 1.2 +++ InheritedPropFunction.java5 Mar 2003 21:59:47 - 1.3 @@ -1,10 +1,53 @@ /* * $Id$ - * Copyright (C) 2001 The Apache Software Foundation. All rights reserved. - * For details on use and redistribution please refer to the - * LICENSE file included with these sources. - */ - + * + *The Apache Software License, Version 1.1 + * + * + * Copyright (C) 1999-2003 The Apache Software Foundation. All rights reserved. + * + * Redistribution and use in source and binary forms, with or without modifica- + * tion, are permitted provided that the following conditions are met: + * + * 1. Redistributions of source code must retain the above copyright notice, + *this list of conditions and the following disclaimer. + * + * 2. Redistributions in binary form must reproduce the above copyright notice, + *this list of conditions and the following disclaimer in the documentation + *and/or other materials provided with the distribution. + * + * 3. The end-user documentation included with the redistribution, if any, must + *include the following acknowledgment: This product includes software + *developed by the Apache Software Foundation (http://www.apache.org/). + *Alternately, this acknowledgment may appear in the software itself, if + *and wherever such third-party acknowledgments normally appear. + * + * 4. The names FOP and Apache Software Foundation must not be used to + *endorse or promote products derived from this software without prior + *written permission. For written permission, please contact + *[EMAIL PROTECTED] + * + * 5. Products derived from this software may not be called Apache, nor may + *Apache appear in their name, without prior written permission of the + *Apache Software Foundation. + * + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, + * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND + * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE + * APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, + * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU- + * DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS + * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON + * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF + * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + * + * + * This software consists of voluntary contributions made by many individuals + * on behalf of the Apache Software Foundation and was originally created by + * James Tauber [EMAIL PROTECTED]. For more information on the Apache + * Software Foundation, please see http://www.apache.org/. + */ package org.apache.fop.fo.expr; import org.apache.fop.fo.Property; 1.4 +49 -6 xml-fop/src/org/apache/fop/fo/expr/FopPropValFunction.java Index: FopPropValFunction.java === RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/expr/FopPropValFunction.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u
cvs commit: xml-fop/src/documentation/content/xdocs pdfencryption.xml book.xml running.xml
pietsch 2003/03/05 15:15:25 Modified:src/documentation/content/xdocs book.xml running.xml Added: src/documentation/content/xdocs pdfencryption.xml Log: Added documentation for PDF encryption to xdocs. Revision ChangesPath 1.9 +1 -0 xml-fop/src/documentation/content/xdocs/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/book.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- book.xml 27 Jan 2003 20:59:55 - 1.8 +++ book.xml 5 Mar 2003 23:15:25 - 1.9 @@ -38,6 +38,7 @@ menu-item label=SVG href=svg.html/ menu-item label=Extensions href=extensions.html/ menu-item label=Fonts href=fonts.html/ + menu-item label=PDF encryption href=pdfencryption.html/ menu-item label=Configuration href=configuration.html/ /menu 1.5 +68 -62xml-fop/src/documentation/content/xdocs/running.xml Index: running.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/running.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- running.xml 18 Jan 2003 18:04:58 - 1.4 +++ running.xml 5 Mar 2003 23:15:25 - 1.5 @@ -3,77 +3,83 @@ http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd; document -header - titleRunning FOP/title -/header + header +titleRunning FOP/title + /header -body - section -titleInstallation/title + body section - titleOverview/title - pThe following software must be installed:/p - ul -liJava 1.2.x or later./li -liFOP. The jump href=http://xml.apache.org/fop/download.html;FOP distribution/jump includes all libraries that you will need to run a basic FOP installation. These can be found in the xml-fop/lib directory. These libraries include the following:/li + titleInstallation/title + section +titleOverview/title +pThe following software must be installed:/p ul - liApache jump href=http://xml.apache.org/xerces-j/index.html;Xerces-J/jump for XML parsing. You can use other XML parsers which support SAX and DOM./li - liApache Xalan, an XSLT processor./li - liApache jump href=http://xml.apache.org/batik/;Batik/jump, an SVG library./li + liJava 1.2.x or later./li + liFOP. The jump href=http://xml.apache.org/fop/download.html;FOP distribution/jump includes all libraries that you will need to run a basic FOP installation. These can be found in the xml-fop/lib directory. These libraries include the following:/li + ul +liApache jump href=http://xml.apache.org/xerces-j/index.html;Xerces-J/jump for XML parsing. You can use other XML parsers which support SAX and DOM./li +liApache Xalan, an XSLT processor./li +liApache jump href=http://xml.apache.org/batik/;Batik/jump, an SVG library./li + /ul + liOptional Libraries/li /ul -liOptional Libraries/li - /ul + /section + section +titleInstructions/title +pBasic FOP installation consists of first unzipping the code.gz/code file that is the distribution medium, then unarchiving the resulting code.tar/code file in a directory/folder that is convenient on your system. Please consult your operating system documentation or Zip application software documentation for instructions specific to your site./p + /section + section +titleProblems/title +pSome Mac OSX users have experienced filename truncation problems using Stuffit to unzip and unarchive their distribution media. This is a legacy of older Mac operating systems, which had a 31-character pathname limit. Several Mac OSX users have recommended that Mac OSX users use the shell command codetar -xzf/code instead./p + /section /section section - titleInstructions/title - pBasic FOP installation consists of first unzipping the code.gz/code file that is the distribution medium, then unarchiving the resulting code.tar/code file in a directory/folder that is convenient on your system. Please consult your operating system documentation or Zip application software documentation for instructions specific to your site./p -/section -section - titleProblems/title - pSome Mac OSX users have experienced filename truncation problems using Stuffit to unzip and unarchive their distribution media. This is a legacy of older Mac operating systems, which had a 31-character pathname limit. Several Mac OSX users
Re: batik transcoders
Hi Jeremias, You mean Batik will have pdf-transcoder.jar and ps-transcoder.jar in their distributions? Not the source, right? That is correct. What about factoring out the code for the transcoders and supporting classes (like fonts) into a separate container/subproject accessible by both the FOP and Batik teams? XML-Commons, maybe? That way we could encourage the Batik guys to participate in the future development of the PDF- and PS-related SVG stuff. Just a thought. That could be a good idea for the future. For the short term just a bundling. So will there be any problems. There is th/e pdf-transcoder build target that creates the transcoder jar. We could create a tag for the release (call it beta2?). We do need to make it clear that a FOP release cannot be used at the same time as this jar due to various changes. +1. We could give the transcoders a bit more visibility on our site. The PDF transcoder seems to be working fine. There are a couple of problems. Issues: - the use of avalon Enumeration requires avalon in the path. It is only used as an interface for one of the font classes, do we really need that Not really at the moment. But as soon as I have this licensing issues and an initial release of my barcode package behind me, I wanted to go into full Avalon-refactoring mode. And that brings some more Avalon stuff into FOP especially the renderers, fonts and image support. Thats fine. I'd like to propose this: - I'll modify the build so we can generate a raw pdf-transcoder.jar as it is now (needs avalon-framework.jar), but along with another (pdf-transcoder-all.jar) that also contains the necessary Avalon classes. - I'll do the documentation involved. Okay. - do we need all of the font classes for transcoding, which ones can be left out ATM the PFM parser and the apps subpackage are the only ones that can be left out, I think. There are some minor bugs with patterns in patterns, drawing images and fonts but there won't be any fixes soon. Wouldn't it make sense to work with the Batik team to get the PDF and PS transcoders into their test infrastructure so we have some good feedback and can quickly improve on the quality to match the AWT output? If I understand their testing properly, it is currently no setup in a way that could handle PDF/PS output. They have various levels of testing: xml parsing, dom, bridge, gvt, image output and various others. The image output is the one that is parallel with the PDF/PS transcoding, it is done by comparing the result with a reference image stored in cvs. Someone needs to know what the reference should be like. Also there are PDF version/viewer version issues. I'll see what can be sorted out. Also what is the status of the PS transcoder? Could this be included. I haven't set up the PS transcoder, yet. But I could do that soon. I'm still hoping for George to send in a patch for his PostScript work. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: inline-container support
Hi Jens, Hi! I've got a fo-task for which I need a working fo:inline-container-object. This feature seems not to be implemented in the 0.20.x-version. I would like to know weather support for this element is planned for the coming versions (maintenance or redesigned-branch). Are any milestones planned? In the redesign it is not planned as such but we do want to implement it. Would it be possible / difficult to take part in the implementation-process myself if no support is planned? Do you want to get started on implementing it in the redesign? What we will need is an InlineContainerLayoutManager that returns a single inline object as with other layout managers such as image. The inline-container area will have width, height and alignment. The renderers will need to handle the inline container, this might already be done but it wouldn't be tested. Inside the inline container it will need to find all the breaks and then to calculate the height. The IPD must be fixed and this will be passed down to the child layout managers. Once it has all the breaks all it need to do is set the height. When the areas are added it will get all the child LM's to add there areas from the breaks, then it will add the inline container to the parent and do the alignment. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
ssh problems
Fopdevs, Has anyone else expereinced any difficulties with ssh access to CVS? I have been having intermittent problems for some days now, and often cannot access CVS at all. -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: ssh problems
Looks like a timing problem. I may have been trying to hit the server at a bad time. Working now, failed earlier. Peter Peter B. West wrote: Fopdevs, Has anyone else expereinced any difficulties with ssh access to CVS? I have been having intermittent problems for some days now, and often cannot access CVS at all. -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties propertyExpressions.html
pbwest 2003/03/05 21:07:14 Removed: src/documentation/content/design/alt.design/properties propertyExpressions.html Log: Using propertyExpressions.ehtml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties simple-properties.html introduction.html index.html getInitialValue.html enumerated-values.html classes-overview.html PropertyConsts-class.html
pbwest 2003/03/05 21:09:44 Removed: src/documentation/content/design/alt.design/properties simple-properties.html introduction.html index.html getInitialValue.html enumerated-values.html classes-overview.html PropertyConsts-class.html Log: Using .ehtml files - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/design/alt.design alt-design-frameset.html codeframe.html logo.html
pbwest 2003/03/05 21:21:06 Removed: src/documentation/content/design/alt.design alt-design-frameset.html codeframe.html logo.html Log: Using .ehtml files - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/design/alt.design/properties book.xml classes-overview.ehtml enumerated-values.ehtml getInitialValue.ehtml index.xml PropertyConsts-class.ehtml propertyExpressions.ehtml simple-properties.ehtml
pbwest 2003/03/05 21:23:01
Added: src/documentation/content/xdocs/design/alt.design/properties
book.xml classes-overview.ehtml
enumerated-values.ehtml getInitialValue.ehtml
index.xml PropertyConsts-class.ehtml
propertyExpressions.ehtml simple-properties.ehtml
Log:
Using .ehtml files
Revision ChangesPath
1.4 +0 -0
xml-fop/src/documentation/content/xdocs/design/alt.design/properties/book.xml
1.1
xml-fop/src/documentation/content/xdocs/design/alt.design/properties/classes-overview.ehtml
Index: classes-overview.ehtml
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
META http-equiv= Content-Type content= text/html; charset=ISO-8859-1
titleProperty classes overview/title
script type=text/javascript src=resources/codedisplay.js
/script
/head
body marginheight= 0 marginwidth= 0 topmargin= 0 leftmargin= 0 text=
#00 bgcolor= #FF
div class= content
h1Property classes overview/h1
p
font size= -2 bynbsp;Peter B. West/font
/p
ul class= minitoc
li
a href = #N10014 Properties: packages/a
ul class= minitoc
li
a href = #N10019 org.apache.fop.fo/a
/li
li
a href = #N100AC org.apache.fop.fo.properties/a
/li
li
a href = #N100EE org.apache.fop.fo.expr/a
/li
li
a href = #N10134 org.apache.fop.datatypes/a
/li
li
a href = #N101A2
org.apache.fop.datatypes.indirect/a
/li
/ul
/li
/ul
a name= N10014 /a h3Properties: packages/h3 a name=
N10019 /a h4org.apache.fop.fo/h4
dl
dt
span id=span00 /span
a href = javascript:toggleCode('span00',
'PropNames.html#PropNamesClass', '50%', '100%'
) emPropNames/em/a
/dt
dd
This class maintains an array of span id=span01
/spana href= javascript:toggleCode( 'span01',
'PropNames.html#propertyNames', '50%', '100%' ) property
names/a, synchronized to a complete set of property name
span id=span02 /spana href = javascript:toggleCode(
'span02', 'PropNames.html#NO_PROPERTY', '50%', '100%' )
constants/a for indexing property-based arrays. It
includes methods to span id=span03 /spana href =
javascript:toggleCode( 'span03',
'PropNames.html#getPropertyName', '50%', '100%' ) convert
an index to a name/a and to span id=span04 /spana
href = javascript:toggleCode( 'span04',
'PropNames.html#getPropertyIndex', '50%', '100%' ) convert
a property name to an index/a.
/dd
dt
a href = PropertyConsts-class.html emPropertyConsts/em/a
/dt
dd
A singleton instance of span class= codefrag
PropertyConsts/span is created by the static initializer
of the span id=span05 /spana href =
javascript:toggleCode( 'span05',
'PropertyConsts.html#pconsts', '50%', '100%' ) pconsts/a
field. Working from the property indices defined in
PropNames, the methods in this class collect and supply the
values of fields defined in property objects into
arrays.br The heart of this class in the method span
id=span06 /spana href = javascript:toggleCode(
'span06', 'PropertyConsts.html#setupProperty', '50%', '100%'
) setupProperty/a, which constructs the property name
from the index, instantiates a singleton of the appropriate
class, and extracts static fields by reflection from that
instance into the arrays of field values.
/dd
dt
span id=span07 /spana href = javascript:toggleCode(
'span07', 'PropertySets.html#PropertySetsClass', '50%',
'100%' ) emPropertySets/em/a
/dt
dd
This class provides a number of span class= codefrag
ROBitSet/spans representing many of the sets of
properties defined in emSection 7/em of the
specification. Note that the span id=span08 /span
a href= javascript:toggleCode( 'span08',
'PropertySets.html#borderProps', '50%', '100%' )
emBorder/em/a, span id=span09 /span a href=
javascript:toggleCode( 'span09',
'PropertySets.html#paddingProps', '50%', '100%' )
emPadding/em/a and span id=span10
RE: Encryption
I agree with you concerning sticking with the standard JCE interface, but in the end I want what works. I feel for you since you have to live with my code ;-) (until someone does it better), so my tact is facilitate the transition with the minimal cost to you. If there is anything you need reworked, just let me know. Once we all agree it is production quality, I'm gonna turn around and use it... call it enlightened self-interest. Cheers and thanks again, Pat -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2003 2:21 PM To: [EMAIL PROTECTED] Subject: Re: Encryption Patrick C. Lankswert wrote: Add jce-jdk13-118.jar (for 1.3.x) to %JAVA_HOME%\jre\lib\ext and add security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider to %JAVA_HOME%\jre\lib\security\java.security in the appropriate section. This should work. This is how it is done to support any implementation. Thank you, I already discovered this myself last night. It was just that shutting down the work environment in order to re-login as Administrator for changing java.security at 2:10am isn't worth it, so I decided to go to bed. Now everything runs well and is already committed to the maintenance branch, I'll update the docs and HEAD later. IF you would like it HARD CODED to bouncy castle's implementation which does not require the java.security changes, It's probably a bad idea to tie FOP to a specific provider. In particular as Mozilla also has an Open Source implementation, which is perhaps even faster due to native code (anybody ready to try it?) J.Pietschmann - 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: batik transcoders
Hi Keiron On 06.03.2003 00:45:01 Keiron Liddle wrote: snip/ There are some minor bugs with patterns in patterns, drawing images and fonts but there won't be any fixes soon. Wouldn't it make sense to work with the Batik team to get the PDF and PS transcoders into their test infrastructure so we have some good feedback and can quickly improve on the quality to match the AWT output? If I understand their testing properly, it is currently no setup in a way that could handle PDF/PS output. They have various levels of testing: xml parsing, dom, bridge, gvt, image output and various others. The image output is the one that is parallel with the PDF/PS transcoding, it is done by comparing the result with a reference image stored in cvs. Someone needs to know what the reference should be like. Also there are PDF version/viewer version issues. I'll see what can be sorted out. I see. I was also thinking about using GhostScript for converting PostScript and PDF files to bitmaps for testing and then calculating differential images. Add to that a little GUI that let's you browse through a testsuite and inspect the three bitmaps (ref, actual, differential). This could be used for both SVG and XSL-FO stuff. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
