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=18559.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=18576.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=18576.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=18576.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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=635.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I'm reviewing the developer branch code and believe that although
CommandLineOptions parses the -c option and caches a userConfigFile,
the config file is not processed. FOP 0.20.5rc2 has an
org.apache.fop.configuration package for handling the -c option. Hence
it appears the -c option is not
In compliance.html, it may be nice to have the W3C XSL-FO 1.0 standard
phrase in the first sentence hyperlinked to the specification (as is done
already on index.html). I suspect that link would get very heavy usage if
placed on that page.
Also, the menu on the left can probably be further
keiron 2003/04/01 16:40:04
Modified:.status.xml
Log:
updated status re markers
Revision ChangesPath
1.28 +11 -11xml-fop/status.xml
Index: status.xml
===
RCS file:
Thanks Keiron for the feedback!
I found and reviewed the discussion regarding the move to Avalon (ref:
http://marc.theaimsgroup.com/?l=fop-devm=10226606705w=2 ).
I also appreciate your point that some aspects of configuration have
already been 're-enabled'; as exemplified in
Mazza, Glen R., ,CPMS wrote:
In compliance.html, it may be nice to have the W3C XSL-FO 1.0 standard
phrase in the first sentence hyperlinked to the specification (as is done
already on index.html). I suspect that link would get very heavy usage if
placed on that page.
Good point. Actually,
Here's some sample code I use for configuring the PDFRenderer for the
moment:
import org.apache.avalon.framework.ExceptionUtil;
import org.apache.avalon.framework.configuration.Configurable;
import org.apache.avalon.framework.configuration.Configuration;
import
11 matches
Mail list logo