RE: [REDESIGN] Line layout manager discussion
Keiron Liddle wrote: On Sat, 2002-05-04 at 18:07, Arved Sandstrom wrote: I couldn't tell from the SVG source what you prepared the file with. I would like to use SVG myself. There is no way I am going to handcode it, though (just as with FO). I actually wrote it by hand. I tried using an editor but gave up, instead I just edit by hand and view it using batik. In this case it was fairly easy since everything is placed in a definite position. Editing SVG with Adobe Illustrator 10 works ok (small wonder), though the licence is fairly expensive if you don't use it regularly. The drawing app in OpenOffice may have SVG export, too - I heard, but didn't check myself. Fallback: If you send me design documents in vector graphics files of (almost) any kind, I can do the SVG conversion for you. I'm in office even on most weekends so this may work ok for some time. Arnd Beissner -- Cappelino Informationstechnologie GmbH Arnd Beißner Bahnhofstr. 3, 71063 Sindelfingen, Germany Email: [EMAIL PROTECTED] Phone: +49-7031-463458 Mobile: +49-173-3016917 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
AW: Is SVG a preferred way to draw form lines?
At least 2 aspects are to be considered: document design/generation and operation o SVG - document design: do you have a tool? - operation: uses Batik starts new processes and generates images o xsl:fo table with borders, backgrounds - document design: type xsl:fo on the hard way? - operation: FOP only But will Adobe extend PDF and Acrobat to handle SVG XML? Hansuli Anderegg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
AW: [REDESIGN] Line layout manager discussion
By writing renderer code with FOP 0.20.1 I observed : A basic link fo:basic-link internal-destination=dest0link wordst/fo:basic-link arrives 3 times in the PDFrenderer asynchronously, without any connection between each other. 1. as word link 2. as word words 3. as annotation rectangle This is OK with PDF. But there is an assumption on the operation of the output device. Other document formats: link rendering needs access to all related data. How about FOP extensions, new versions of xsl:fo? Deep area tree, linear sequential representation, semantics - I cannot tell. It has to be device independent. Fetching info randomly from the area tree? Some document formats need a list of fonts used at the beginning of the document or each page. Can the renderer retrieve this info from the the area tree in advance? Elimination of intermediate storage makes renderer programming straight forward. Hansuli Anderegg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [REDESIGN] Line layout manager discussion
Hi All, What it boils down to seems to be if the inline fo returns the block area or generates an inline area that contains the block area. If it generates an inline area then it will set traits on that area (border, background, link, padding etc.). If that is the case why is a footnote inline not allowed to have a block level child. Since this is effectively the same as using an inline-container. Here is another confusing statement, that makes sense for inline-container. 4.6 The dimensions of the content-rectangle for an inline-area without children is computed as specified by the generating formatting object, as are those of an inline-area with block-area children. Does computed as specified mean specified on the fo or derived from the context. From a practical viewpoint it makes sense to wrap the block in an inline area with the traits and treat the block normally in layout terms but it still feels uncomfortable. It also introduces a whole lot of other questions about line height, padding etc. Keiron. On Mon, 2002-05-06 at 03:52, Peter B. West wrote: Arved, Again, I agree that, in the conceptual area tree described in the spec, blocks embedded in inline-area generating FOs in the fo tree (e.g., fo:inline and fo:basic-link), themselves embedded in a parent fo:block, do not bubble up to the same level as the parent fo:block. Going back to your diagram, I am talking about the fo:block embedded in the basic-link. I have attached another diagram describing a subset of your original example. Let me clarify what I meant by the term bubble up in the reply to Karen. Then what seems to me to be the *intention* that layout within fo:inline and fo:basic-link proceed as though these wrappers were layout-transparent, would be made clear. That is, blocks bubbling up from below will be stacked in the BPDir without IPDir attachments from surrounding inline-areas. This refers to the spec's conceptual area tree. It arises out of my misapprehension that the nesting of fo:blocks within inline-area generators would involve a nesting of the layout within the generated inline-area. The fo:inline inline-area in the area tree would grow within the bounds of the containing line-area and block area, but limited by it. It doesn't work that way, though, as we have all discussed. These block areas bubble-up, not in terms of their containment within the appropriate set of line-area-inline-area-block-area, bu in terms of their layout consequences. Apart from any layout-altering properties defined on the containing inline-area generator, e.g.font or border changes, the text and any nested blocks are treated for layout as though they had occurred as direct children of the outer fo:block. That's what the term layout-transparent means. That, at least, is what I take the *intention* of the authors to be. And that is why I want to see some clarification of the relationship between 4.7.2 Line-building and 4.7.3 Inline-building. It seems to me that the spec decrees that the initial text of the basic-link (In basic-link in my example) is constructed into an inline-area by the Inline-building process of 4.7.3. In order to do this, it has to know about the constraints that it inherits from the already partially constructed line-area which contains Text in block . It seems to me that, conceptually at least, in the conceptual area tree model of the spec, the inline-building process needs to take account of all of the glyph substitution, insertion and deletion considerations that apply to 4.7.2, because it is now the responsibility of the inline-area generator to generate a *single* inline-area to complete the pending line-area of the parent. To do that, it will have to be able to do its own line-breaking. Clarifying this is a matter of the coherence and consistency of the spec. It is also important if you are tempted, as I am, by the idea of mimicking this conceptual model and procedure in actual code. All of the above may just mean that, while I thought I had been brought around to your way of thinking on this aspect of the spec, I may still be thinking about it very differently. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 1972] - text color not working after a page break
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=1972. 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=1972 text color not working after a page break --- Additional Comments From [EMAIL PROTECTED] 2002-05-06 11:32 --- Seems that this was actually a duplicate of Bug 1972. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8819] New: - Footnotes lost
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=8819. 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=8819 Footnotes lost Summary: Footnotes lost Product: Fop Version: 0.20.3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Footnotest which do not fit on the current page are shifted en-block to the next page. Common practise would be to fit as much as possible on the current page, subject to widows/orphans and other common typographical restrictions. The current algorithm drops footnotes on occasion, see example. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8819] - Footnotes lost
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=8819. 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=8819 Footnotes lost --- Additional Comments From [EMAIL PROTECTED] 2002-05-06 12:21 --- Created an attachment (id=1791) FO file demonstrating lost footnote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 2555] - fo:wrapper doesn't display some content
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=2555. 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=2555 fo:wrapper doesn't display some content [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 2567] - initial-page-number=auto does not work properly...
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=2567. 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=2567 initial-page-number=auto does not work properly... [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 2638] - How to include non xml svg?
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=2638. 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=2638 How to include non xml svg? [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 2808] - rotate() performed twice in transform() also having translate()
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=2808. 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=2808 rotate() performed twice in transform() also having translate() [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Additional Comments From [EMAIL PROTECTED] 2002-05-06 13:26 --- An interesting point is that the testcase works without a definition of the xlink prefix. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 2880] - Incorrect rendering on non-ASCII machines
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=2880. 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=2880 Incorrect rendering on non-ASCII machines [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-05-06 13:33 --- One of the problems is that PDF is in part a binary format because of embedded images (in particular compressed images). *** This bug has been marked as a duplicate of 2532 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 2532] - FOP 0.17 does not work with WebSphere V3.5 OS/390
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=2532. 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=2532 FOP 0.17 does not work with WebSphere V3.5 OS/390 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-05-06 13:33 --- *** Bug 2880 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 2964] - problems with height of cells in tables
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=2964. 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=2964 problems with height of cells in tables --- Additional Comments From [EMAIL PROTECTED] 2002-05-06 15:59 --- The attached file crashes FOP 0.20.3 with a NullPointerException while trying to get the next page master. I think this is a new bug. Apart from this the described bug is still there. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4535] - PCL renderer 1.13 not rendering SVG
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=4535. 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=4535 PCL renderer 1.13 not rendering SVG [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3007] - broken basic-link when referencing a following page
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=3007. 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=3007 broken basic-link when referencing a following page [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-06 16:13 --- The test case works in 0.20.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Java 1.1.x
I have a client who is using a Domino server. Domino only supports the Java 1.1.8 SDK. I have been unable to find a version of FOP that will run with this SDK. Does anyone have any suggestions? Thank you in advance, Kendall Adkins [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Border properties
Arved, thanks for the explanations. I still find it confusing that in the following (default western script) the left visible edges would not line up: fo:blockstuff/fo:block fo:block border-style=solid border-width=5mmMore stuff /fo:block In order to have it line up, the start-indent has to be set to 5mm. This, well, sucks. I'm pretty sure there are other who'll be confused too. Is this some CSS inheritance I have missed? I took a quick look at table.fo (the FO) and I think this will probably help out. I have to admit if there is one area of the spec that I am not particularly familiar with it is tables - in this case I don't think there is any weirdness involved stemming from table border properties. Well, table borders apparently are handled the same way as ordinary block borders, i experimented a bit. This appears to be consistent. The problem remains: Now, what is the problem bug 684 complains about? I still have no idea: is the problem fixed or not? For a start, I'm not quite sure what the problem reporter meant, because I've never seen tables.fo rendered by an older FOP version. I have to say it looks ok for me, but then I have missed important things before. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Java 1.1.x
It is really old, but you could try this one: http://xml.apache.org/dist/fop/old/fop-0_14_1_jdk11.jar If you want to try building a version from CVS, you could try to get a version from just before Batik was added. There used to be an option on the build script package-jdk11 I think that got most of the way to a functioning version with JDK 1.1 (with limitations). You may need to fix some things, but it is a start. Art -Original Message- From: Kendall Adkins [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 2:18 PM To: [EMAIL PROTECTED] Subject: Java 1.1.x I have a client who is using a Domino server. Domino only supports the Java 1.1.8 SDK. I have been unable to find a version of FOP that will run with this SDK. Does anyone have any suggestions? Thank you in advance, Kendall Adkins [EMAIL PROTECTED] - 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: [REDESIGN] Line layout manager discussion
Interleaved commentary... -Original Message- From: Keiron Liddle [mailto:[EMAIL PROTECTED]] Sent: May 6, 2002 5:21 AM To: [EMAIL PROTECTED] Subject: Re: [REDESIGN] Line layout manager discussion Hi All, What it boils down to seems to be if the inline fo returns the block area or generates an inline area that contains the block area. If it generates an inline area then it will set traits on that area (border, background, link, padding etc.). From 4.7.3 my understanding is that any (normal) areas returned by children of the inline formatting object always become children of normal inline areas that the FO generates. Similarly for a block, by 4.7.2. So the inline FO can never _return_ a normal block area. I guess it depends on one's understanding of return. I take this not to include any nested areas. The normal block area comes back, sure, but as a child of a normal inline area. If that is the case why is a footnote inline not allowed to have a block level child. Since this is effectively the same as using an inline-container. Probably just the semantics of what the inline does for a footnote, rather than any technical reason. Here is another confusing statement, that makes sense for inline-container. 4.6 The dimensions of the content-rectangle for an inline-area without children is computed as specified by the generating formatting object, as are those of an inline-area with block-area children. Does computed as specified mean specified on the fo or derived from the context. I'm thinking, as specified on the FO. From a practical viewpoint it makes sense to wrap the block in an inline area with the traits and treat the block normally in layout terms but it still feels uncomfortable. It also introduces a whole lot of other questions about line height, padding etc. The use of line-height for inlines is as a synonym for height; one _can_ use height but only for replaced inline-level FOs. So for an original inline, say, we'd ignore a height but use line-height instead, which more often than not is just going to inherit from the block containing it. I think this is pretty straightforward. I don't know if this is what you were getting at, though. Because I figure you're on top of this already. Regards, Arved - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/datastructs - New directory
pbwest 02/05/06 21:32:42 xml-fop/src/org/apache/fop/datastructs - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop build-notes
pbwest 02/05/06 21:34:32 Added: .Tag: FOP_0-20-0_Alt-Design build-notes Log: Notes on minimalist experimental build. Revision ChangesPath No revision No revision 1.1.2.1 +57 -0 xml-fop/Attic/build-notes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/datastructs CircularBuffer.java ROClassArray.java ROIntArray.java ROIntegerArray.java ROMethodArray.java ROStringArray.java SyncedCircularBuffer.java TNode.java TNodeTest.java Tree.java package.html
pbwest 02/05/06 21:37:53 Added: src/org/apache/fop/datastructs Tag: FOP_0-20-0_Alt-Design CircularBuffer.java ROClassArray.java ROIntArray.java ROIntegerArray.java ROMethodArray.java ROStringArray.java SyncedCircularBuffer.java TNode.java TNodeTest.java Tree.java package.html Log: Classes for complex data structures. Revision ChangesPath No revision No revision 1.1.2.1 +96 -0 xml-fop/src/org/apache/fop/datastructs/Attic/CircularBuffer.java 1.1.2.1 +39 -0 xml-fop/src/org/apache/fop/datastructs/Attic/ROClassArray.java 1.1.2.1 +57 -0 xml-fop/src/org/apache/fop/datastructs/Attic/ROIntArray.java 1.1.2.1 +44 -0 xml-fop/src/org/apache/fop/datastructs/Attic/ROIntegerArray.java 1.1.2.1 +38 -0 xml-fop/src/org/apache/fop/datastructs/Attic/ROMethodArray.java 1.1.2.1 +35 -0 xml-fop/src/org/apache/fop/datastructs/Attic/ROStringArray.java 1.1.2.1 +176 -0 xml-fop/src/org/apache/fop/datastructs/Attic/SyncedCircularBuffer.java 1.1.2.1 +82 -0 xml-fop/src/org/apache/fop/datastructs/Attic/TNode.java 1.1.2.1 +188 -0xml-fop/src/org/apache/fop/datastructs/Attic/TNodeTest.java 1.1.2.1 +1040 -0 xml-fop/src/org/apache/fop/datastructs/Attic/Tree.java 1.1.2.1 +6 -0 xml-fop/src/org/apache/fop/datastructs/Attic/package.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/apps CommandLineStarter.java Driver.java Fop.java
pbwest 02/05/06 21:51:00
Modified:src/org/apache/fop/apps Tag: FOP_0-20-0_Alt-Design
CommandLineStarter.java Driver.java Fop.java
Log:
Initial commit for minimalist experimental development environment
Revision ChangesPath
No revision
No revision
1.9.2.1 +3 -64 xml-fop/src/org/apache/fop/apps/CommandLineStarter.java
Index: CommandLineStarter.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/apps/CommandLineStarter.java,v
retrieving revision 1.9
retrieving revision 1.9.2.1
diff -u -r1.9 -r1.9.2.1
--- CommandLineStarter.java 1 Aug 2001 23:08:54 - 1.9
+++ CommandLineStarter.java 7 May 2002 04:51:00 - 1.9.2.1
@@ -1,5 +1,5 @@
/*
- * $Id: CommandLineStarter.java,v 1.9 2001/08/01 23:08:54 gears Exp $
+ * $Id: CommandLineStarter.java,v 1.9.2.1 2002/05/07 04:51:00 pbwest 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.
@@ -7,70 +7,9 @@
package org.apache.fop.apps;
-// SAX
-import org.xml.sax.XMLReader;
-import org.xml.sax.InputSource;
-import org.xml.sax.SAXException;
-import org.xml.sax.SAXParseException;
+public class CommandLineStarter {
-// Java
-import java.io.*;
-import java.net.URL;
-
-
-// FOP
-import org.apache.fop.messaging.MessageHandler;
-import org.apache.fop.configuration.Configuration;
-
-/**
- * super class for all classes which start Fop from the commandline
- *
- * Modified to use new streaming API by Mark Lillywhite, [EMAIL PROTECTED]
- */
-
-public class CommandLineStarter extends Starter {
-
-CommandLineOptions commandLineOptions;
-boolean errorDump;
-
-public CommandLineStarter(CommandLineOptions commandLineOptions)
-throws FOPException {
-this.commandLineOptions = commandLineOptions;
-options.setCommandLineOptions(commandLineOptions);
-errorDump = Configuration.getBooleanValue(debugMode).booleanValue();
-super.setInputHandler(commandLineOptions.getInputHandler());
-}
-
-/**
- * Run the format.
- * @exception FOPException if there is an error during processing
- */
-public void run() throws FOPException {
-String version = Version.getVersion();
-MessageHandler.logln(version);
-
-XMLReader parser = inputHandler.getParser();
-setParserFeatures(parser);
-
-Driver driver = new Driver();
-driver.setBufferFile(commandLineOptions.getBufferFile());
-
-if (errorDump) {
-driver.setErrorDump(true);
-}
-
-try {
-driver.setRenderer(commandLineOptions.getRenderer());
-driver.setOutputStream(new
FileOutputStream(commandLineOptions.getOutputFile()));
-
driver.getRenderer().setOptions(commandLineOptions.getRendererOptions());
-driver.render(parser, inputHandler.getInputSource());
-System.exit(0);
-} catch (Exception e) {
-if (e instanceof FOPException) {
-throw (FOPException)e;
-}
-throw new FOPException(e);
-}
+public CommandLineStarter() throws FOPException {
}
}
1.31.2.1 +77 -519 xml-fop/src/org/apache/fop/apps/Driver.java
Index: Driver.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/apps/Driver.java,v
retrieving revision 1.31
retrieving revision 1.31.2.1
diff -u -r1.31 -r1.31.2.1
--- Driver.java 1 Aug 2001 23:08:54 - 1.31
+++ Driver.java 7 May 2002 04:51:00 - 1.31.2.1
@@ -1,5 +1,5 @@
/*
- * $Id: Driver.java,v 1.31 2001/08/01 23:08:54 gears Exp $
+ * $Id: Driver.java,v 1.31.2.1 2002/05/07 04:51:00 pbwest 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.
@@ -8,163 +8,93 @@
package org.apache.fop.apps;
// FOP
-import org.apache.fop.fo.FOTreeBuilder;
-import org.apache.fop.fo.ElementMapping;
+import org.apache.fop.fo.FOTree;
+import org.apache.fop.datastructs.SyncedCircularBuffer;
import org.apache.fop.layout.AreaTree;
-import org.apache.fop.render.Renderer;
-import org.apache.fop.messaging.MessageHandler;
-import org.apache.fop.configuration.ConfigurationReader;
+import org.apache.fop.xml.XMLSerialHandler;
import org.apache.fop.configuration.Configuration;
-import org.apache.fop.tools.DocumentInputSource;
-import org.apache.fop.tools.DocumentReader;
-
-import
cvs commit: xml-fop/src/org/apache/fop/apps Options.java
pbwest 02/05/06 21:52:35
Modified:src/org/apache/fop/apps Tag: FOP_0-20-0_Alt-Design
Options.java
Log:
Options merged with CommandLineOptions for experimental development.
Revision ChangesPath
No revision
No revision
1.9.4.1 +813 -77 xml-fop/src/org/apache/fop/apps/Options.java
Index: Options.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/apps/Options.java,v
retrieving revision 1.9
retrieving revision 1.9.4.1
diff -u -r1.9 -r1.9.4.1
--- Options.java 10 Aug 2001 08:18:43 - 1.9
+++ Options.java 7 May 2002 04:52:35 - 1.9.4.1
@@ -1,5 +1,5 @@
/*
- * $Id: Options.java,v 1.9 2001/08/10 08:18:43 keiron Exp $
+ * $Id: Options.java,v 1.9.4.1 2002/05/07 04:52:35 pbwest 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.
@@ -12,101 +12,322 @@
// java
import java.io.File;
+import java.io.FileNotFoundException;
import java.io.InputStream;
+import java.util.HashMap;
+import java.util.Set;
+import java.util.Iterator;
// fop
import org.apache.fop.messaging.MessageHandler;
import org.apache.fop.configuration.Configuration;
import org.apache.fop.configuration.ConfigurationReader;
+import org.apache.fop.configuration.LanguageFileReader;
/**
* Options handles loading of configuration files and
* additional setting of commandline options
*/
public class Options {
-boolean errorDump = false;
-public Options() throws FOPException {
-this.loadStandardConfiguration();
-initOptions();
+/**
+ * Render to PDF. OutputStream must be set
+ */
+public static final int RENDER_PDF = 1;
+
+/* input / output not set */
+private static final int NOT_SET = 0;
+/* input: fo file */
+private static final int FO_INPUT = 1;
+/* input: xml+xsl file */
+private static final int XSLT_INPUT = 2;
+private static final int LAST_INPUT_MODE = XSLT_INPUT;
+
+/* output: pdf file */
+private static final int PDF_OUTPUT = 1;
+private static final int LAST_OUTPUT_MODE = PDF_OUTPUT;
+
+private static final String defaultConfigFile = config.xml;
+private static final String defaultUserConfigFile = userconfig.xml;
+/**
+ * An array of String indexed by the integer constants representing
+ * the various input modes. Provided so that integer modes can be
+ * mapped to a more descriptive string, and vice versa.
+ */
+public static final String[] inputModes;
+/**
+ * An array of String indexed by the integer constants representing
+ * the various output modes. Provided so that integer modes can be
+ * mapped to a more descriptive string, and vice versa.
+ */
+public static final String[] outputModes;
+
+static {
+inputModes = new String[LAST_INPUT_MODE + 1];
+inputModes[NOT_SET] = NotSet;
+inputModes[FO_INPUT] = fo;
+inputModes[XSLT_INPUT] = xslt;
+
+outputModes = new String[LAST_OUTPUT_MODE + 1];
+outputModes[NOT_SET] = NotSet;
+outputModes[PDF_OUTPUT] = pdf;
}
-public Options(File userConfigFile) throws FOPException {
-this();
-this.loadUserconfiguration(userConfigFile);
+/**
+ * @param mode the mode whose index in the array inputModes is to be
+ * returned.
+ * @return the int index of the mode string in the array, or -1 if the
+ * mode string is not found in the array
+ */
+public static int inputModeIndex(String mode)
+throws FOPException {
+for (int i = 0; i = LAST_INPUT_MODE; i++) {
+if (inputModes[i] != null)
+if (mode.equals(inputModes[i]))
+return i;
+}
+throw new FOPException(Input mode + mode + not known);
}
-public Options(CommandLineOptions clOptions) throws FOPException {
-this();
-this.setCommandLineOptions(clOptions);
+/**
+ * @param mode the mode whose index in the array outputModes is to be
+ * returned.
+ * @return the int index of the mode string in the array, or -1 if the
+ * mode string is not found in the array
+ */
+public static int outputModeIndex(String mode)
+throws FOPException {
+for (int i = 0; i = LAST_INPUT_MODE; i++) {
+if (outputModes[i] != null)
+if (mode.equals(outputModes[i]))
+return i;
+}
+throw new FOPException(Output mode + mode + not
cvs commit: xml-fop/src/org/apache/fop/fo package.html
pbwest 02/05/06 22:19:50 Added: src/org/apache/fop/fo Tag: FOP_0-20-0_Alt-Design package.html Log: Revision ChangesPath No revision No revision 1.1.2.1 +7 -0 xml-fop/src/org/apache/fop/fo/Attic/package.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo FONode.java
pbwest 02/05/06 22:23:06
Modified:src/org/apache/fop/fo Tag: FOP_0-20-0_Alt-Design FONode.java
Log:
Experimental version of FONode
Revision ChangesPath
No revision
No revision
1.19.2.1 +81 -230 xml-fop/src/org/apache/fop/fo/FONode.java
Index: FONode.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/FONode.java,v
retrieving revision 1.19
retrieving revision 1.19.2.1
diff -u -r1.19 -r1.19.2.1
--- FONode.java 1 Aug 2001 23:08:54 - 1.19
+++ FONode.java 7 May 2002 05:23:06 - 1.19.2.1
@@ -1,244 +1,95 @@
+package org.apache.fop.fo;
+
+import org.apache.fop.fo.FOTree;
+import org.apache.fop.fo.FOAttributes;
+import org.apache.fop.fo.FObjects;
+import org.apache.fop.fo.expr.PropertyException;
+import org.apache.fop.fo.expr.PropertyParser;
+import org.apache.fop.fo.expr.PropertyValue;
+import org.apache.fop.fo.expr.PropertyValueList;
+import org.apache.fop.datastructs.Tree;
+import org.apache.fop.datastructs.SyncedCircularBuffer;
+import org.apache.fop.apps.FOPException;
+import org.apache.fop.xml.XMLEvent;
+
+import org.xml.sax.Attributes;
+
+import java.util.LinkedList;
+import java.util.ArrayList;
+
/*
- * $Id: FONode.java,v 1.19 2001/08/01 23:08:54 gears Exp $
+ * FONode.java
+ * Created: Sat Nov 10 01:39:37 2001
+ *
* 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.
+ *
+ * @author a href=mailto:[EMAIL PROTECTED];Peter B. West/a
+ * @version $Revision: 1.19.2.1 $ $Name: $
*/
-
-
-package org.apache.fop.fo;
-
-// FOP
-import org.apache.fop.apps.FOPException;
-import org.apache.fop.layout.Area;
-import org.apache.fop.layout.AreaClass;
-import org.apache.fop.layout.LinkSet;
-import org.apache.fop.system.BufferManager;
-import org.apache.fop.fo.flow.Marker;
-
-// Java
-import java.util.Vector;
-import java.util.Hashtable;
-
/**
- * base class for nodes in the formatting object tree
- *
- * Modified by Mark Lillywhite [EMAIL PROTECTED] Made
- * Vector a protected member. (/me things this should be
- * a private member with an API for adding children;
- * this woudl save a lot of memory because the Vector
- * would not have to be instantiated unless the node had
- * children).
+ * Class for nodes in the FO tree.
*/
-abstract public class FONode {
-
-protected FObj parent;
-
-protected String areaClass = AreaClass.UNASSIGNED;
-
-public BufferManager bufferManager;
-protected Vector children = new Vector();// made public for searching for
id's
-
-/**
- * value of marker before layout begins
- */
-public final static int START = -1000;
-
-/**
- * value of marker after break-after
- */
-public final static int BREAK_AFTER = -1001;
+public class FONode extends FOTree.Node{
/**
- * where the layout was up to.
- * for FObjs it is the child number
- * for FOText it is the character number
+ * Constants for the set of attributes of interest with this FONode
*/
-protected int marker = START;
-
-protected boolean isInTableCell = false;
-
-protected int forcedStartOffset = 0;
-protected int forcedWidth = 0;
-
-protected int widows = 0;
-protected int orphans = 0;
-
-protected LinkSet linkSet;
-
-// count of areas generated-by/returned-by
-public int areasGenerated = 0;
-
-// markers
-protected Hashtable markers;
-
-protected FONode(FObj parent) {
-this.parent = parent;
-if (parent != null) {
-this.bufferManager = parent.bufferManager;
+public static final int
+NONE = 0
+ ,ROOT = 1
+ ,LAYOUT = 2
+ ,FLOW = 3
+;
+
+/** The ttFOTree/tt of which this node is a member. */
+protected FOTree foTree;
+/** The ttXMLEvent/tt which triggered this node. */
+protected XMLEvent event;
+/** The buffer from which parser events are drawn. */
+protected SyncedCircularBuffer xmlevents;
+/** The array of property value stacks */
+protected LinkedList[] propertyStacks;
+/** The attributes defined on this node. */
+public FOAttributes foAttributes;
+/** The property expression parser in the FOTree. */
+protected PropertyParser exprParser;
+
+/**
+ * @param foTree an ttFOTree/tt to which this node belongs
+ * @param parent an ttFONode/tt, the parent node of this node in
+ * ifoTree/i
+ * @param event the ttXMLEvent/tt that triggered the creation of this
+ * node
+ */
+
cvs commit: xml-fop/src/org/apache/fop/fo BoxPropShorthandParser.java CharacterProperty.java ColorProfile.java ColorTypeProperty.java CondLengthProperty.java Declarations.java ElementMapping.java EnumProperty.java FOText.java FOTreeBuilder.java FObj.java FObjMixed.java GenericShorthandParser.java KeepProperty.java LengthPairProperty.java LengthProperty.java LengthRangeProperty.java ListProperty.java NumberProperty.java Property.java PropertyList.java PropertyListBuilder.java PropertyManager.java ShorthandParser.java SpaceProperty.java StandardElementMapping.java Status.java StringProperty.java Title.java ToBeImplementedElement.java TreeBuilder.java Unknown.java XTElementMapping.java XTFOTreeBuilder.java
pbwest 02/05/06 22:30:51 Removed: src/org/apache/fop/fo Tag: FOP_0-20-0_Alt-Design BoxPropShorthandParser.java CharacterProperty.java ColorProfile.java ColorTypeProperty.java CondLengthProperty.java Declarations.java ElementMapping.java EnumProperty.java FOText.java FOTreeBuilder.java FObj.java FObjMixed.java GenericShorthandParser.java KeepProperty.java LengthPairProperty.java LengthProperty.java LengthRangeProperty.java ListProperty.java NumberProperty.java Property.java PropertyList.java PropertyListBuilder.java PropertyManager.java ShorthandParser.java SpaceProperty.java StandardElementMapping.java Status.java StringProperty.java Title.java ToBeImplementedElement.java TreeBuilder.java Unknown.java XTElementMapping.java XTFOTreeBuilder.java Log: Stripped-down environment for experimental development. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/expr PropertyParser.java PropertyTokenizer.java
pbwest 02/05/06 22:37:16
Modified:src/org/apache/fop/fo/expr Tag: FOP_0-20-0_Alt-Design
PropertyParser.java PropertyTokenizer.java
Log:
Initial version of experimental property expression parsing.
Revision ChangesPath
No revision
No revision
1.5.2.1 +435 -287 xml-fop/src/org/apache/fop/fo/expr/PropertyParser.java
Index: PropertyParser.java
===
RCS file: /home/cvs/xml-fop/src/org/apache/fop/fo/expr/PropertyParser.java,v
retrieving revision 1.5
retrieving revision 1.5.2.1
diff -u -r1.5 -r1.5.2.1
--- PropertyParser.java 30 Jul 2001 20:29:21 - 1.5
+++ PropertyParser.java 7 May 2002 05:37:16 - 1.5.2.1
@@ -1,5 +1,5 @@
/*
- * $Id: PropertyParser.java,v 1.5 2001/07/30 20:29:21 tore Exp $
+ * $Id: PropertyParser.java,v 1.5.2.1 2002/05/07 05:37:16 pbwest 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.
@@ -7,140 +7,195 @@
package org.apache.fop.fo.expr;
-import org.apache.fop.fo.Property;
-import org.apache.fop.fo.ListProperty;
-import org.apache.fop.fo.LengthProperty;
-import org.apache.fop.fo.NumberProperty;
-import org.apache.fop.fo.StringProperty;
-import org.apache.fop.fo.ColorTypeProperty;
-import org.apache.fop.datatypes.*;
+import org.apache.fop.fo.PropertyConsts;
+import org.apache.fop.fo.Properties;
+import org.apache.fop.fo.PropNames;
+
+import org.apache.fop.fo.expr.PropertyValue;
+import org.apache.fop.fo.expr.PropertyValueList;
+import org.apache.fop.datatypes.Numeric;
+import org.apache.fop.datatypes.Literal;
+import org.apache.fop.datatypes.NCName;
+import org.apache.fop.datatypes.Percentage;
+import org.apache.fop.datatypes.Ems;
+import org.apache.fop.datatypes.IntegerType;
+import org.apache.fop.datatypes.Length;
+import org.apache.fop.datatypes.Time;
+import org.apache.fop.datatypes.Frequency;
+import org.apache.fop.datatypes.Angle;
+import org.apache.fop.datatypes.Bool;
+import org.apache.fop.datatypes.Inherit;
+import org.apache.fop.datatypes.Auto;
+import org.apache.fop.datatypes.None;
+import org.apache.fop.datatypes.ColorType;
+import org.apache.fop.datatypes.StringType;
+import org.apache.fop.datatypes.MimeType;
+import org.apache.fop.datatypes.UriType;
+import org.apache.fop.datatypes.FromParent;
+import org.apache.fop.datatypes.FromNearestSpecified;
+//import org.apache.fop.datatypes.*;
-import java.util.Hashtable;
+import java.util.HashMap;
/**
* Class to parse XSL FO property expression.
- * This class is heavily based on the epxression parser in James Clark's
+ * This class is heavily based on the expression parser in James Clark's
* XT, an XSLT processor.
+ *
+ * PropertyParser objects are re-usable. The constructor simply creates the
+ * object. To parse an expression, the public method iParse/i is
+ * called.
*/
public class PropertyParser extends PropertyTokenizer {
-private PropertyInfo propInfo;// Maker and propertyList related info
-
-static private final String RELUNIT = em;
-static private final Numeric negOne = new Numeric(new Double(-1.0));
-static final private Hashtable functionTable = new Hashtable();
-
-static {
-// Initialize the Hashtable of XSL-defined functions
-functionTable.put(ceiling, new CeilingFunction());
-functionTable.put(floor, new FloorFunction());
-functionTable.put(round, new RoundFunction());
-functionTable.put(min, new MinFunction());
-functionTable.put(max, new MaxFunction());
-functionTable.put(abs, new AbsFunction());
-functionTable.put(rgb, new RGBColorFunction());
-functionTable.put(from-table-column, new FromTableColumnFunction());
-functionTable.put(inherited-property-value,
- new InheritedPropFunction());
-functionTable.put(from-parent, new FromParentFunction());
-functionTable.put(from-nearest-specified-value,
- new NearestSpecPropFunction());
-functionTable.put(proportional-column-width,
- new PPColWidthFunction());
-functionTable.put(label-end, new LabelEndFunction());
-functionTable.put(body-start, new BodyStartFunction());
-// NOTE: used from code generated for corresponding properties
-functionTable.put(_fop-property-value, new FopPropValFunction());
-
-/**
- * * NOT YET IMPLEMENTED!!!
- * functionTable.put(icc-color, new ICCcolorFunction());
- * functionTable.put(system-color, new SystemColorFunction());
- *
cvs commit: xml-fop/src/org/apache/fop/fo/expr AbstractPropertyValue.java PropertyTriplet.java PropertyValue.java PropertyValueList.java package.html
pbwest 02/05/06 22:40:16 Added: src/org/apache/fop/fo/expr Tag: FOP_0-20-0_Alt-Design AbstractPropertyValue.java PropertyTriplet.java PropertyValue.java PropertyValueList.java package.html Log: Initial commit of experimental property expression handling files. Revision ChangesPath No revision No revision 1.1.2.1 +119 -0 xml-fop/src/org/apache/fop/fo/expr/Attic/AbstractPropertyValue.java 1.1.2.1 +205 -0xml-fop/src/org/apache/fop/fo/expr/Attic/PropertyTriplet.java 1.1.2.1 +48 -0 xml-fop/src/org/apache/fop/fo/expr/Attic/PropertyValue.java 1.1.2.1 +227 -0xml-fop/src/org/apache/fop/fo/expr/Attic/PropertyValueList.java 1.1.2.1 +6 -0 xml-fop/src/org/apache/fop/fo/expr/Attic/package.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/expr AbsFunction.java BodyStartFunction.java CeilingFunction.java FloorFunction.java FopPropValFunction.java FromParentFunction.java FromTableColumnFunction.java Function.java FunctionBase.java InheritedPropFunction.java LabelEndFunction.java MaxFunction.java MinFunction.java NCnameProperty.java NearestSpecPropFunction.java Numeric.java NumericProperty.java PPColWidthFunction.java PropertyInfo.java RGBColorFunction.java RoundFunction.java
pbwest 02/05/06 22:42:39 Removed: src/org/apache/fop/fo/expr Tag: FOP_0-20-0_Alt-Design AbsFunction.java BodyStartFunction.java CeilingFunction.java FloorFunction.java FopPropValFunction.java FromParentFunction.java FromTableColumnFunction.java Function.java FunctionBase.java InheritedPropFunction.java LabelEndFunction.java MaxFunction.java MinFunction.java NCnameProperty.java NearestSpecPropFunction.java Numeric.java NumericProperty.java PPColWidthFunction.java PropertyInfo.java RGBColorFunction.java RoundFunction.java Log: Stripped-down environment for experimental development. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Border properties
I think I remember what was (!) wrong: There was a time where FOP displayed the table(s) on page 6 of table.fo in the following manner: +--- |bad +--- +-- |bad +-- +-- |bad +-- +-- |bad +-- The left indentation of each consecutive table (!) was incremented by exactly the left border width of the previous table. That bug was in FOP for quite a few months! I don't know anymore who fixed it in the end. So I'm going to mark the bug as closed for you. The problem remains: Now, what is the problem bug 684 complains about? I still have no idea: is the problem fixed or not? For a start, I'm not quite sure what the problem reporter meant, because I've never seen tables.fo rendered by an older FOP version. I have to say it looks ok for me, but then I have missed important things before. Cheers, Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Tel. +41 41 317 2020 - Fax +41 41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 684] - border width in tables adds up
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=684. 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=684 border width in tables adds up [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED OS/Version||All Priority||High Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-07 05:47 --- This was fixed some time ago. I think I remember what was (!) wrong: There was a time where FOP displayed the table(s) on page 6 of table.fo in the following manner: +--- |bad +--- +-- |bad +-- +-- |bad +-- +-- |bad +-- The left indentation of each consecutive table (!) was incremented by exactly the left border width of the previous table. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/pagination ConditionalPageMasterReference.java LayoutMasterSet.java PageMasterReference.java PageNumberGenerator.java PageSequence.java PageSequenceMaster.java Region.java RegionAfter.java RegionBefore.java RegionBody.java RegionEnd.java RegionStart.java RepeatablePageMasterAlternatives.java RepeatablePageMasterReference.java Root.java SimplePageMaster.java SinglePageMasterReference.java SubSequenceSpecifier.java
pbwest 02/05/06 22:48:13 Removed: src/org/apache/fop/fo/pagination Tag: FOP_0-20-0_Alt-Design ConditionalPageMasterReference.java LayoutMasterSet.java PageMasterReference.java PageNumberGenerator.java PageSequence.java PageSequenceMaster.java Region.java RegionAfter.java RegionBefore.java RegionBody.java RegionEnd.java RegionStart.java RepeatablePageMasterAlternatives.java RepeatablePageMasterReference.java Root.java SimplePageMaster.java SinglePageMasterReference.java SubSequenceSpecifier.java Log: Stripped-down experimental develoment environment. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/pagination FoConditionalPageMasterReference.java FoLayoutMasterSet.java FoPageSequenceMaster.java FoRepeatablePageMasterAlternatives.java FoSimplePageMaster.java FoSinglePageMasterReference.java
pbwest 02/05/06 22:50:04 Added: src/org/apache/fop/fo/pagination Tag: FOP_0-20-0_Alt-Design FoConditionalPageMasterReference.java FoLayoutMasterSet.java FoPageSequenceMaster.java FoRepeatablePageMasterAlternatives.java FoSimplePageMaster.java FoSinglePageMasterReference.java Log: Initial commit of experimental page-handling. Revision ChangesPath No revision No revision 1.1.2.1 +38 -0 xml-fop/src/org/apache/fop/fo/pagination/Attic/FoConditionalPageMasterReference.java 1.1.2.1 +155 -0 xml-fop/src/org/apache/fop/fo/pagination/Attic/FoLayoutMasterSet.java 1.1.2.1 +175 -0 xml-fop/src/org/apache/fop/fo/pagination/Attic/FoPageSequenceMaster.java 1.1.2.1 +51 -0 xml-fop/src/org/apache/fop/fo/pagination/Attic/FoRepeatablePageMasterAlternatives.java 1.1.2.1 +55 -0 xml-fop/src/org/apache/fop/fo/pagination/Attic/FoSimplePageMaster.java 1.1.2.1 +35 -0 xml-fop/src/org/apache/fop/fo/pagination/Attic/FoSinglePageMasterReference.java - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/fo/flow BasicLink.java BidiOverride.java BlockContainer.java Block.java Character.java ExternalGraphic.java Float.java Flow.java FootnoteBody.java Footnote.java InitialPropertySet.java InlineContainer.java Inline.java InstreamForeignObject.java Leader.java ListBlock.java ListItemBody.java ListItem.java ListItemLabel.java Marker.java MultiCase.java MultiProperties.java MultiPropertySet.java MultiSwitch.java MultiToggle.java PageNumberCitation.java PageNumber.java RetrieveMarker.java RowSpanMgr.java StaticContent.java TableAndCaption.java TableBody.java TableCaption.java TableCell.java TableColumn.java TableFooter.java TableHeader.java Table.java TableRow.java Wrapper.java
pbwest 02/05/06 22:57:01 Removed: src/org/apache/fop/fo/flow Tag: FOP_0-20-0_Alt-Design BasicLink.java BidiOverride.java BlockContainer.java Block.java Character.java ExternalGraphic.java Float.java Flow.java FootnoteBody.java Footnote.java InitialPropertySet.java InlineContainer.java Inline.java InstreamForeignObject.java Leader.java ListBlock.java ListItemBody.java ListItem.java ListItemLabel.java Marker.java MultiCase.java MultiProperties.java MultiPropertySet.java MultiSwitch.java MultiToggle.java PageNumberCitation.java PageNumber.java RetrieveMarker.java RowSpanMgr.java StaticContent.java TableAndCaption.java TableBody.java TableCaption.java TableCell.java TableColumn.java TableFooter.java TableHeader.java Table.java TableRow.java Wrapper.java Log: Stripped-down experimental environment. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Image in an XML
Hello I'm working with FOP 20.3. As input I have a xml-stream and a xsl-File. Now I would like to have an image in my xml, not in the xsl. The image comes from a database. Is there any possibility to do that, without writing the image in a file ? How have I to encode it, for Fop ? Regards P.Steiner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/org/apache/fop/apps AWTStarter.java CommandLineOptions.java PDFOutputHandler.java PrintStarter.java Starter.java StreamRenderer.java TraxInputHandler.java XSLTInputHandler.java XTDriver.java
pbwest 02/05/06 23:00:09 Removed: src/org/apache/fop/apps Tag: FOP_0-20-0_Alt-Design AWTStarter.java CommandLineOptions.java PDFOutputHandler.java PrintStarter.java Starter.java StreamRenderer.java TraxInputHandler.java XSLTInputHandler.java XTDriver.java Log: Stripped-down experimental environment. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Image in an XML
Priska.Steiner wrote: Hello I'm working with FOP 20.3. As input I have a xml-stream and a xsl-File. Now I would like to have an image in my xml, not in the xsl. The image comes from a database. Is there any possibility to do that, without writing the image in a file ? How have I to encode it, for Fop ? What you could do - I successfully did that for a customer - is: embed the image in the XML file - base64 encoded. Then write an extension function for Xalan that decodes the image and creates a temp file containing the image. This has worked nicely for me - I used this method with exported Domino databases in XML format. Hope this helps, Arnd Beissner -- Cappelino Informationstechnologie GmbH Arnd Beißner Bahnhofstr. 3, 71063 Sindelfingen, Germany Email: [EMAIL PROTECTED] Phone: +49-7031-463458 Mobile: +49-173-3016917 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Image in an XML
I'd implement a custom protocol handler in a way that you can access your images in the database using a URL that could look like this: myimages://mydatabase/id (where id might be the primary key to the image). This way you don't have to encode anything because you're getting a binary stream directly from the blob in the database. And you're not bound to XML. Every Java application (ex. a Servlet or a JSP) can refer to this kind of URL once it is implemented and registered. I've already written a couple of protocol handlers and I'm very happy with the results. A good tutorial on Protocol Handlers can be found here. http://developer.java.sun.com/developer/onlineTraining/protocolhandlers/ I'm working with FOP 20.3. As input I have a xml-stream and a xsl-File. Now I would like to have an image in my xml, not in the xsl. The image comes from a database. Is there any possibility to do that, without writing the image in a file ? How have I to encode it, for Fop ? Cheers, Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Tel. +41 41 317 2020 - Fax +41 41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
