cvs commit: xml-fop/src/documentation/content/xdocs team.xml
cbowditch2004/04/08 06:17:15 Modified:src/documentation/content/xdocs team.xml Log: added Luca Furini to contributor section Revision ChangesPath 1.30 +5 -2 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- team.xml 4 Apr 2004 14:27:23 - 1.29 +++ team.xml 8 Apr 2004 13:17:15 - 1.30 @@ -66,6 +66,9 @@ is a TeX/LaTeX and XML expert with Elsevier at its Amsterdam office. See his fork href=http://www.leverkruid.nl;home page/fork for some of his private projects./li +!-- Luca prefers the mail address with AT, to stop spam, etc. -- + lilink href=mailto:lfurini AT cs.unibo.itLuca Furini/link +is a student of Computer Studies at the University of Bologna (Italy)/li /ul /section section id=founder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
outputting intermediate XSL-FO file
I wanted to re-visit the issue of giving FOP the option of outputting the intermediate file XSL-FO file (a la ./xalan.sh -IN input.xml -XSL input.xsl -OUT output.fo). I still think it makes sense to enable FOP to have the option to retain this intermediate file. The primary benefit is to make it easier to respond to fop-user@ questions. Having to explaining the proper use of xalan.bat/.sh to a user means requiring the user to learn 'one more app' when it isn't really necessary. I'd rather tell the user: Let's look at the intermediate XSL-FO file by adding '-tempfile' to your FOP string: ./fop.sh -xml input.xml -xsl input.xsl -tempfile The location for the tempfile could be tempfiles/ or could be output as '[datestamp]_input.xml.fo' or something. The nicest part of this, is that the fop-user uses the same fop they always use, but merely add one arg to output the intermediate file. Apologies if this topic has already been beaten to death. At the very least, we need to add a FAQ on the FOP site, indicating in one paragraph how to do this for themselves. Perhaps that'll be something to add in the near future. Web Maestro Clay Begin forwarded message: From: Clay Leeds [EMAIL PROTECTED] Date: April 8, 2004 7:57:01 AM PDT To: [EMAIL PROTECTED] Subject: Re: only display the text in XSL file but does not display the image Reply-To: [EMAIL PROTECTED] On Apr 8, 2004, at 7:37 AM, Jerry wrote: 2. It also helps if you just do the XSLT transformation on the command line (as I suggested earlier). By checking the generated FO afterwards you can see if everything is alright. Sorry I am not sure how to use XSLT to test it from command line. Assuming you are using fop-0.20.5, xalan.bat (or xalan.sh on Un*x a.k.a 'xalan' in this post) can be used to generate (and review!) the 'intermediate' XSL-FO file. Running xalan with no arguments gives you the help you should need to run xalan properly. Here's a boost: ./xalan.sh -IN [input.xml] -XSL [input.xsl] -OUT [output.fo] (without any of the '[' and ']' of course!) That should to it! Look at the 'output.fo' file, to 'see if everything is alright'... I don't know the answers to the other questions, but hopefully this answers *this* question. Web Maestro Clay - [EMAIL PROTECTED] -- Web Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Offline
Team, just to let you know that I will be off line until Monday 19th April. Best regards, Chris
cvs commit: xml-fop/src/java/org/apache/fop/apps CommandLineOptions.java Fop.java
gmazza 2004/04/08 20:05:40
Modified:src/java/org/apache/fop/apps CommandLineOptions.java
Fop.java
Log:
3/4ths of Simon's patch committed at the moment, with minor changes
made.
Revision ChangesPath
1.17 +19 -37xml-fop/src/java/org/apache/fop/apps/CommandLineOptions.java
Index: CommandLineOptions.java
===
RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/apps/CommandLineOptions.java,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- CommandLineOptions.java 31 Mar 2004 10:55:05 - 1.16
+++ CommandLineOptions.java 9 Apr 2004 03:05:40 - 1.17
@@ -1,5 +1,4 @@
-/*
- * Copyright 1999-2004 The Apache Software Foundation.
+/* Copyright 1999-2004 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the License);
* you may not use this file except in compliance with the License.
@@ -24,6 +23,8 @@
import java.util.Locale;
import java.util.Vector;
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
import org.apache.commons.logging.impl.SimpleLog;
/**
@@ -59,7 +60,7 @@
public static final int RTF_OUTPUT = 10;
/* show configuration information */
-private Boolean dumpConfiguration = Boolean.FALSE;
+private Boolean showConfiguration = Boolean.FALSE;
/* suppress any progress information */
private Boolean quiet = Boolean.FALSE;
/* for area tree XML output, only down to block area level */
@@ -81,7 +82,7 @@
private java.util.HashMap rendererOptions;
-private SimpleLog log;
+private Log log;
private Vector xsltParams = null;
@@ -94,14 +95,16 @@
public CommandLineOptions(String[] args)
throws FOPException, FileNotFoundException {
-log = new SimpleLog(FOP);
-log.setLevel(SimpleLog.LOG_LEVEL_INFO);
-
+log = LogFactory.getLog(FOP);
+
boolean optionsParsed = true;
rendererOptions = new java.util.HashMap();
try {
optionsParsed = parseOptions(args);
if (optionsParsed) {
+if (showConfiguration == Boolean.TRUE) {
+dumpConfiguration();
+}
checkSettings();
}
} catch (FOPException e) {
@@ -117,7 +120,7 @@
* Get the logger.
* @return the logger
*/
-public SimpleLog getLogger() {
+public Log getLogger() {
return log;
}
@@ -131,14 +134,14 @@
for (int i = 0; i args.length; i++) {
if (args[i].equals(-d) || args[i].equals(--full-error-dump)) {
log = new SimpleLog(FOP);
-log.setLevel(SimpleLog.LOG_LEVEL_DEBUG);
+((SimpleLog) log).setLevel(SimpleLog.LOG_LEVEL_DEBUG);
} else if (args[i].equals(-x)
|| args[i].equals(--dump-config)) {
-dumpConfiguration = Boolean.TRUE;
+showConfiguration = Boolean.TRUE;
} else if (args[i].equals(-q) || args[i].equals(--quiet)) {
quiet = Boolean.TRUE;
log = new SimpleLog(FOP);
-log.setLevel(SimpleLog.LOG_LEVEL_ERROR);
+((SimpleLog) log).setLevel(SimpleLog.LOG_LEVEL_ERROR);
} else if (args[i].equals(-c)) {
i = i + parseConfigurationOption(args, i);
} else if (args[i].equals(-l)) {
@@ -548,22 +551,6 @@
}
/**
- * Indicates if FOP should be silent.
- * @return true if should be silent
- */
-public Boolean isQuiet() {
-return quiet;
-}
-
-/**
- * Indicates if FOP should dump its configuration during runtime.
- * @return true if config dump is enabled
- */
-public Boolean dumpConfiguration() {
-return dumpConfiguration;
-}
-
-/**
* Indicates whether the XML renderer should generate course area XML
* @return true if coarse area XML is desired
*/
@@ -643,7 +630,7 @@
/**
* debug mode. outputs all commandline settings
*/
-private void debug() {
+private void dumpConfiguration() {
log.debug(Input mode: );
switch (inputmode) {
case NOT_SET:
@@ -712,25 +699,20 @@
log.debug(unknown input type);
}
-
log.debug(OPTIONS);
+
if (userConfigFile != null) {
log.debug(user configuration file:
+ userConfigFile.toString());
} else {
log.debug(no user configuration file is used [default]);
}
-
DO NOT REPLY [Bug 28237] - [PATCH] Use the commons logging LogFactory also in Fop.java
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28237.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28237
[PATCH] Use the commons logging LogFactory also in Fop.java
--- Additional Comments From [EMAIL PROTECTED] 2004-04-09 03:18 ---
Thanks for the explanation, Simon. I understand a lot more now and have
committed most of your patch, but with a few changes. Please take a look at the
new version and let me know what you think.
Changes I didn't commit were a couple of minor issues I had some question
on--namely, your wrapping and creating of new logs based on -d and -q options in
CLO.parseOptions():
(a) why place within isDebugEnabled() and isWarnEnabled() conditionals, why does
this matter?
(b) one conditional is !isDebugEnabled() with a negative but the other is the
positive isWarnEnabled()--was this a bug?
(c) Finally, did you actually mean isErrorEnabled() for the latter?
BTW, please always use { } for the conditionals instead of single-lines [1]:
if (a b) {
c = d;
}
http://xml.apache.org/fop/dev/conventions.html
Thanks again,
Glen
