Re: Status on http://xml.apache.org/fop/index.html
On Thu, 2002-06-06 at 16:03, patrick andries wrote: I think it was about a month ago, a status section was added to the FOP main page. A good idea. Four questions : 1) Could it be possible to add a date to this status : [last updated xx-March-2002] ? Yes 2) Could it be possible to move this section higher ? It is difficult to spot. Would a page of its own be good enough? 3) What does the following paragraph mean ? « Development for 1.0DR1 is addressing the design issues for layout and performance. This is focusing on making it possible to be conformant to the spec and be able to handle large documents. This is roughly 30% towards a developers release that should have: similar functionality to previous FOP releases, a rough API and a suitable design for developers to work on more functionality. » It means we don't know but we are working on it. What is « roughly 30% towards » ? The work already done or the 1.0DR 1 ? Could this sentence please be rewritten ? It is a rough estimate that gives a bit of information without really saying much. Do you want less information so you aren't tempted to make predictions or do you want more information that will end up being wrong? 4) What has changed in the last month ? (I.e. could we get at least a monthly update if we must live with «The timing of these events depends on progress made so it is not possible to predict any dates » ?) Are you volunteering to help out with this? Do you think this would be that useful at the moment? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: SAX, fopservlet and 0.20.2
J: Thanks - that clarifies it. The newer xalan did and, with the upgrade to the newer fop and the namespace fix, it is now working (although I had to rename my servlet from fop to fop.pdf to get the pdf output in IE). I now have to work on performance - my users don't like waiting 30min to and hour for their pdf reports. Thanks! -Lou J.Pietschmann [EMAIL PROTECTED] on 06/06/2002 16:00:59 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: SAX, fopservlet and 0.20.2 [EMAIL PROTECTED] wrote: I am now testing using the glossary xml/xsl files in the example directory, but with the same results. It works fine from the command line, but NPE whenever I introduce the SAXResult or SAXSource. I'm starting to think it might be something with me environment. Also, if I stream it to a file using StreamResult, I can then take the resultant fo and use the Fop command line utility on that and it is fine. It is possible that it is a problem involving undeclared namespaces. GGet a recent Xalan or get Saxon (http://saxon.sourceforge.net) at run your stylesheet: xalan -in foo.xml -xsl foo.xsl -out foo.fo The Xalan included in the FOP distribution sometimes throws NPEs by itself and sometimes passes null namespaces to FOP which cause NPEs, but the latter might be masked by serialisation and reparsing. A more recent Xalan will provide a proper error message. Sorry, the xml.apache.org stated you needed the sax api, not sax.jar - xalan should cover this? Not Xalan, Xerces (included in the FOP distribution. 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: Status on http://xml.apache.org/fop/index.html
- Original Message - From: Keiron Liddle [EMAIL PROTECTED] To: FOP [EMAIL PROTECTED] 3) What does the following paragraph mean ? « Development for 1.0DR1 is addressing the design issues for layout and performance. This is focusing on making it possible to be conformant to the spec and be able to handle large documents. This is roughly 30% towards a developers release that should have: similar functionality to previous FOP releases, a rough API and a suitable design for developers to work on more functionality. » It means we don't know but we are working on it. What is « roughly 30% towards » ? The work already done or the 1.0DR 1 ? Could this sentence please be rewritten ? It is a rough estimate that gives a bit of information without really saying much. Do you want less information so you aren't tempted to make predictions or do you want more information that will end up being wrong? [PA] Don't take my remarks wrong : I don't mind not having much information, I just don't want to be misled. I do simply not understand the sentence. What is « this » in « this is roughly » ? Do you mean that the redesign will end up when it ends (and we have no idea when) with 30% of the current functionality (« this is roughly 30%» ...« similar functionality to the previous FOP releases » ? If this is not what you intend some people to understand, the sentence should be rewritten. 4) What has changed in the last month ? (I.e. could we get at least a monthly update if we must live with «The timing of these events depends on progress made so it is not possible to predict any dates » ?) Are you volunteering to help out with this? [PA] In fact, about two to three months ago I voluntereed (I was between jobs) and no one answered. Now I'm rather taken by my new job, but my employer will be happy to help implement features if there is a least a chance of a release sometimes (I have stated several times that we want line numbering(*), for instance, for our government customers). We could also help implement other features (in the recommendation this time) but again if our investment were to come to fruition relatively quickly, we are too small a company to do otherwise. Patrick Andries (*) Which I **prototyped** on my machine in FOP 0.23 to the customer's satisfaction. - 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-06-07/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] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/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/src/org/apache/fop/fo/properties/foenums_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/charlist.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/CodePointMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl [style] Transforming into /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Courier.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Helvetica.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Helvetica.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBold.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBoldOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Symbol.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Symbol.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBold.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBoldItalic.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBoldItalic.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesItalic.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesItalic.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesRoman.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesRoman.java [style] Processing
Re: [REDESIGN - LAYOUTMGR] Status request/update
Hi Karen, I'm not really doing any layout stuff at the moment. I wanted to get some movement in those other areas. So the layout stuff is open. I gather you have the ideas on how it should be put together. I hoping the structure handler stuff will be able to be hooked up to provide the ASAP processing. Keiron. On Thu, 2002-06-06 at 22:38, Karen Lease wrote: Keiron, I see you're currently occupied with lots of non-layout changes (structure renderer, IDs, etc). Are you also doing background work in the layoutmgr area or are you leaving the field open for me (and others of course)? I'm currently working on a block-level version of the inline-level BP layoutmgr logic I wrote. I hope to get simple block layout going by this weekend and hook it up with the inline BP managers. My plan is to have it handle break conditions, then keeps, followed by multi-column pages and spans. I've got some float handling logic jotted down but that is a bit further off! If you are other folks are preparing stuff in this area, let's try to coordinate. Regards, Karen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Status on http://xml.apache.org/fop/index.html
On Fri, 2002-06-07 at 15:14, patrick andries wrote: [PA] Don't take my remarks wrong : I don't mind not having much information, I just don't want to be misled. I do simply not understand the sentence. What is « this » in « this is roughly » ? Do you mean that the redesign will end up when it ends (and we have no idea when) with 30% of the current functionality (« this is roughly 30%» ...« similar functionality to the previous FOP releases » ? If this is not what you intend some people to understand, the sentence should be rewritten. No, that's not what it means. It says This [the Development for 1.0DR1] is roughly 30% towards a developers release then.. that [the release] should have: similar functionality to previous FOP releases, a rough API and a suitable design for developers to work on more functionality. So we are 30% towards a developers release. The functionality should be similar to previous releases. I'll try to rewrite it. [PA] In fact, about two to three months ago I voluntereed (I was between jobs) and no one answered. Now I'm rather taken by my new job, but my employer will be happy to help implement features if there is a least a chance of a release sometimes (I have stated several times that we want line numbering(*), for instance, for our government customers). I'm not sure how to answer this. Yes it is good that you offered to do something. The problem is to expect someone to answer at that time to say they *want* what you are offering to do. With open source I would suggest that things work the other way around. If you do something and make it available then people will want it by using it and contributing to it. I'm sure there are articles around that explain it much better. Ultimately it is up to you and how much time/effort you have to spare. Don't take silence as a negative. It is better to make specific suggestions and code. Well, I hope there will be a (redesign) release sometime :) Thanks for the feedback. I'll try to make the status a bit better. We could also help implement other features (in the recommendation this time) but again if our investment were to come to fruition relatively quickly, we are too small a company to do otherwise. Patrick Andries (*) Which I **prototyped** on my machine in FOP 0.23 to the customer's satisfaction. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/render/pdf PDFRenderer.java
jeremias2002/06/07 13:12:35
Modified:src/org/apache/fop/render/pdf Tag: fop-0_20_2-maintain
PDFRenderer.java
Log:
Removed Tc that were inserted in [...] TJ commands. (Bug 9054)
Instead, fixed letter-spacing.
Completed javadocs
Pretty-print using JRefactory (I hope I got the settings right. Otherwise, please
tell me.)
Revision ChangesPath
No revision
No revision
1.91.2.4 +324 -276 xml-fop/src/org/apache/fop/render/pdf/PDFRenderer.java
Index: PDFRenderer.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/pdf/PDFRenderer.java,v
retrieving revision 1.91.2.3
retrieving revision 1.91.2.4
diff -u -r1.91.2.3 -r1.91.2.4
--- PDFRenderer.java 8 May 2002 15:18:48 - 1.91.2.3
+++ PDFRenderer.java 7 Jun 2002 20:12:35 - 1.91.2.4
@@ -1,10 +1,9 @@
/*
- * $Id: PDFRenderer.java,v 1.91.2.3 2002/05/08 15:18:48 chrisg Exp $
+ * $Id: PDFRenderer.java,v 1.91.2.4 2002/06/07 20:12:35 jeremias Exp $
* 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.
*/
-
package org.apache.fop.render.pdf;
// FOP
@@ -49,16 +48,17 @@
import java.awt.Dimension;
/**
- * Renderer that renders areas to PDF
+ * p
+ *
+ * Renderer that renders areas to PDF./p p
*
- * Modified by Mark Lillywhite, [EMAIL PROTECTED] to use the
- * new Renderer interface. The PDF renderer is by far the trickiest
- * renderer and the best supported by FOP. It also required some
- * reworking in the way that Pages, Catalogs and the Root object
- * were written to the stream. The output document should now still
- * be a 100% compatible PDF document, but hte order of the document
- * writing is significantly different. See also the changes
- * to PDFPage, PDFPages and PDFRoot.
+ * Modified by Mark Lillywhite, [EMAIL PROTECTED] to use the new Renderer
+ * interface. The PDF renderer is by far the trickiest renderer and the best
+ * supported by FOP. It also required some reworking in the way that Pages,
+ * Catalogs and the Root object were written to the stream. The output document
+ * should now still be a 100% compatible PDF document, but the order of the
+ * document writing is significantly different. See also the changes to
+ * PDFPage, PDFPages and PDFRoot./p
*/
public class PDFRenderer extends PrintRenderer {
@@ -89,25 +89,27 @@
PDFColor currentColor;
+float currentLetterSpacing = Float.NaN;
+
/**
* true if a TJ command is left to be written
*/
boolean textOpen = false;
/**
- * the previous Y coordinate of the last word written.
- * Used to decide if we can draw the next word on the same line.
+ * the previous Y coordinate of the last word written. Used to decide if we
+ * can draw the next word on the same line.
*/
int prevWordY = 0;
/**
- * the previous X coordinate of the last word written.
- * used to calculate how much space between two words
+ * the previous X coordinate of the last word written. used to calculate
+ * how much space between two words
*/
int prevWordX = 0;
/**
- * The width of the previous word. Used to calculate space between
+ * The width of the previous word. Used to calculate space between
*/
int prevWordWidth = 0;
@@ -132,6 +134,8 @@
/**
* set up renderer options
+ *
+ * @param options Options for the renderer
*/
public void setOptions(Hashtable options) {
this.options = options;
@@ -140,19 +144,31 @@
/**
* set the PDF document's producer
*
- * @param producer string indicating application producing PDF
+ * @param producer string indicating application producing PDF
*/
public void setProducer(String producer) {
this.pdfDoc.setProducer(producer);
}
+/**
+ * Starts the renderer
+ *
+ * @param stream OutputStream to be written to
+ * @exception IOException In case of an IO problem
+ */
public void startRenderer(OutputStream stream)
-throws IOException {
+throws IOException {
pdfDoc.outputHeader(stream);
}
+/**
+ * Called when the renderer has finished its work
+ *
+ * @param stream OutputStream to be written to
+ * @exception IOException In cas of an IO problem
+ */
public void stopRenderer(OutputStream stream)
-throws IOException {
+throws IOException {
renderRootExtensions(extensions);
cvs commit: xml-fop/docs/examples/fo textdeko.fo
jeremias2002/06/07 13:13:25 Modified:docs/examples/fo Tag: fop-0_20_2-maintain textdeko.fo Log: Added a few samples of letter-spacing attribute. Revision ChangesPath No revision No revision 1.3.4.4 +5 -0 xml-fop/docs/examples/fo/textdeko.fo Index: textdeko.fo === RCS file: /home/cvs/xml-fop/docs/examples/fo/textdeko.fo,v retrieving revision 1.3.4.3 retrieving revision 1.3.4.4 diff -u -r1.3.4.3 -r1.3.4.4 --- textdeko.fo 9 Jan 2002 11:32:57 - 1.3.4.3 +++ textdeko.fo 7 Jun 2002 20:13:23 - 1.3.4.4 @@ -278,6 +278,11 @@ #160;#160;#160;#160;#160;#160;#160;#160;#160;#160;#160;#160;#160; #160;#160;#160;#160;#160;#160;#160;#160;#160;#160;#160;#160;#160;/fo:inline /fo:block + + fo:blockThe following blocks demonstrate the letter-spacing attribute:/fo:block + fo:blockThis block does not use any letter-spacing./fo:block + fo:block letter-spacing=1mmThis block uses a letter-spacing of 1mm./fo:block + fo:blockThis block uses an fo:inline element to demonstrate fo:inline letter-spacing=1mmletter-spacing/fo:inline./fo:block /fo:flow /fo:page-sequence - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/docs/examples runtests.bat
jeremias2002/06/07 13:14:30 Modified:docs/examples Tag: fop-0_20_2-maintain runtests.bat Log: Fixed classpath. Xerces was wrong. Revision ChangesPath No revision No revision 1.11.2.5 +1 -1 xml-fop/docs/examples/runtests.bat Index: runtests.bat === RCS file: /home/cvs/xml-fop/docs/examples/runtests.bat,v retrieving revision 1.11.2.4 retrieving revision 1.11.2.5 diff -u -r1.11.2.4 -r1.11.2.5 --- runtests.bat 2 Jun 2002 00:13:25 - 1.11.2.4 +++ runtests.bat 7 Jun 2002 20:14:30 - 1.11.2.5 @@ -7,7 +7,7 @@ set LIBDIR=..\..\lib -set LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip;%LIBDIR%\ant-1.4.1.jar;%LIBDIR%\batik.jar;%LIBDIR%\buildtools.jar;%LIBDIR%\xercesImpl.jar;%LIBDIR%\xml-apis.jar;%LIBDIR%\xalan-2.3.1.jar;%LIBDIR%\bsf.jar;%LIBDIR%\avalon-framework-cvs-20020315.jar;%LIBDIR%\jimi-1.0.jar;%LIBDIR%\..\build\fop.jar +set LOCALCLASSPATH=%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\lib\classes.zip;%LIBDIR%\ant-1.4.1.jar;%LIBDIR%\batik.jar;%LIBDIR%\buildtools.jar;%LIBDIR%\xercesImpl-2.0.1.jar;%LIBDIR%\xml-apis.jar;%LIBDIR%\xalan-2.3.1.jar;%LIBDIR%\bsf.jar;%LIBDIR%\avalon-framework-cvs-20020315.jar;%LIBDIR%\jimi-1.0.jar;%LIBDIR%\..\build\fop.jar set ANT_HOME=%LIBDIR% echo Starting Tests ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 9054] - PDF Tc Text operator BUG
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=9054. 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=9054 PDF Tc Text operator BUG [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-06-07 20:17 --- This is now fixed in CVS (I hope). TouchUp in Acrobat 4.05 works. Please test with your other tools and provide feedback. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
