DO NOT REPLY [Bug 18559] - Not enough error messages (Marformed format string)
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. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18559 Not enough error messages (Marformed format string) [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-04-01 11:10 --- This is a Xalan problem. Try running the XSL transformation only (without FOP). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18576] New: - FOP lops off page numbers in TOC
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. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18576 FOP lops off page numbers in TOC Summary: FOP lops off page numbers in TOC Product: Fop Version: 0.20.5 Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I used xsltproc and the DocBook XSL stylesheets, version 1.60.1 to make a .fo file, and converted the .fo file with FOP. The generated table of contents is missing the page numbers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18576] - FOP lops off page numbers in TOC
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. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18576 FOP lops off page numbers in TOC --- Additional Comments From [EMAIL PROTECTED] 2003-04-01 18:50 --- Created an attachment (id=5588) Tarball with sample XML, FO, and PDF files - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18576] - FOP lops off page numbers in TOC
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. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18576 FOP lops off page numbers in TOC [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-04-01 21:26 --- *** This bug has been marked as a duplicate of 635 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 635] - Doesn't support id= attribute in fo:page-sequence
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. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=635 Doesn't support id= attribute in fo:page-sequence [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-04-01 21:26 --- *** Bug 18576 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Is the -c user config option implemented???
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 yet implemented on the developer branch. Could someone please confirm if this is correct and tell me the status of re-enabling the -c option on the developer branch? Thanks, Bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: web site changes
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 simplified: 5 sections instead of 6. Here's my suggestion: Project (combines Project Status) Introduction(was Index) Latest News Status Changes Download FOP Release Notes Logo Contest! Using FOP Running Embedding Ant Task Output Formats Configuration FOP Extras SVG Support FOP Extensions Fonts PDF Encryption Resources Getting Help FAQs Examples XSL-FO Compliance Developing Getting Involved Reporting Bugs (was Bugs in Resources) Compiling Testing To Do List (was Todo in Project) Patch Queue Thanks, Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop status.xml
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: /home/cvs/xml-fop/status.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- status.xml28 Mar 2003 08:27:17 - 1.27 +++ status.xml2 Apr 2003 00:40:04 - 1.28 @@ -41,17 +41,6 @@ /action action context=code dev=open - Add markers to page when areas added. - When an area is added that is created by an FO that contains markers - then the markers can also be added. There are four types of positions - for markers. -/action -action context=code dev=open - Retrieve markers from page. - When doing the static areas the markers will need to be available for - retrieving. The marker can then be layed out as normal. -/action -action context=code dev=open Implement spacing between blocks and the adjustment to actual height when adding areas. /action @@ -115,6 +104,17 @@ changes release version=2003 date=2003 +action context=code dev=KLL type=update + Added markers to page when areas added. + When an area is added that is created by an FO that contains markers + then the markers can also be added. There are four types of positions + for markers. +/action +action context=code dev=KLL type=update + Retrieved markers from page. + When doing the static areas the markers will need to be available for + retrieving. Layout currently has some issues. +/action action context=code dev=JM type=update PDF and PS transcoders now have a common base class. It also optionally supports Avalon Logging and Configuration. Support for - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is the -c user config option implemented???
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 CommandLineStarter.run() which calls commandLineOptions.getOutputFile() and commandLineOptions.getRendererOptions(). I want to use the -c option to import a font refed in a userconfig.xml file as per http://xml.apache.org/fop/fonts.html#Register+the+fonts+within+FOP- N10261 I can see that CommandLineOptions.parseOptions(...) is caching my userconfig.xml file in its userConfigFile member. Grepping the source does not reveal anyone calling the getUserConfigFile() accessor and I'm unable to find anyone parsing the userConfigFile, so this is what I mean when I say that I suspect configuration is not completely re-enabled. To get the configuration we will probably use the DefaultConfigurationBuilder in avalon framework: http://avalon.apache.org/framework/api/index.html The buildFromFile will return a Configuration object which holds all the configuration data. If you then look in org.apache.fop.render.pdf.PDFRenderer in the configure method you will see that it reads the filter and font information. I don't think there is any code to hook this up. You could do the filename to Configuration object in the Driver. Then it could call configure on the Renderer. I think it will need to get a child Configuration object that matches the mime type for the renderer. Take a look at xml-fop/conf/fop.xconf for a draft of the configuration XML format. Good luck. If you need any more help then give us a yell. So, I guess my question now is: Are CommandLineOptions.userConfigFile font tags being processed? If so, then where? If not, then... yes, given some pointers, I'm interested in helping to get it working. -- Bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: web site changes
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, the dtd has a place for the standard's URL, and each of the standard's components can use that as a base URL, so that I can actually add links to all of the components as well. The underlying xml file has some of this data in it -- I just need to complete that job tweak the stylesheet to build the link. I got pretty bogged down in just getting the document to show up -- thanks for reminding me about this. Also, the menu on the left can probably be further simplified: 5 sections instead of 6. Here's my suggestion: Project (combines Project Status) Introduction(was Index) Latest News Status Changes Download FOP Release Notes Logo Contest! Using FOP Running Embedding Ant Task Output Formats Configuration FOP Extras SVG Support FOP Extensions Fonts PDF Encryption Resources Getting Help FAQs Examples XSL-FO Compliance Developing Getting Involved Reporting Bugs (was Bugs in Resources) Compiling Testing To Do List (was Todo in Project) Patch Queue Thanks, Glen There are some good ideas here. I also want to move some of the Developing stuff over to the Development tab. I'm still bogged down in some of the mechanics of getting Forrest to do what we want, but I have flagged this message for followup, so I will hopefully get back to it within a week or so. Thanks for the good input. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Is the -c user config option implemented???
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 org.apache.avalon.framework.configuration.DefaultConfigurationBuilder;
import org.apache.avalon.framework.container.ContainerUtil;
import org.apache.avalon.framework.context.DefaultContext;
import org.apache.avalon.framework.logger.ConsoleLogger;
import org.apache.avalon.framework.logger.LogEnabled;
import org.apache.avalon.framework.logger.Logger;
import org.apache.fop.apps.Driver;
import org.apache.fop.apps.FOPException;
import org.apache.fop.fo.FOUserAgent;
import org.apache.fop.pdf.PDFEncryptionParams;
[..]
public void convertFO2PDF(File fo, File pdf) throws Exception {
Logger console = new ConsoleLogger(ConsoleLogger.LEVEL_INFO);
DefaultConfigurationBuilder cfgBuilder = new DefaultConfigurationBuilder();
Configuration cfg = cfgBuilder.buildFromFile(
D:/Java/workspace/FOP Main Sandbox/src/xml/pdf-renderer-cfg.xml);
//Construct driver
Driver driver = new Driver();
//Setup logger
driver.enableLogging(console);
FOUserAgent ua = new FOUserAgent();
ua.enableLogging(console);
ua.setBaseURL();
//ua.setPDFEncryptionParams(new PDFEncryptionParams(null, owner, false,
false, true, true));
driver.setUserAgent(ua);
driver.initialize();
//Setup Renderer (output format)
driver.setRenderer(Driver.RENDER_PDF);
ContainerUtil.configure(driver.getRenderer(), cfg.getChild(pdf-renderer));
driver.getRenderer().setCreator(DebugFO2PDF.class.getName() + (dödeldädel));
//Setup output
OutputStream out = new java.io.FileOutputStream(pdf);
out = new java.io.BufferedOutputStream(out);
try {
driver.setOutputStream(out);
//Setup input
InputStream in = new java.io.FileInputStream(fo);
try {
driver.setInputSource(new InputSource(in));
//Process FO
driver.run();
} finally {
in.close();
}
} finally {
out.close();
}
}
We decided at one time to rewrite the CLI using Commons CLI so I'm not
sure if it is worth a lot of effort to fix the current CLI in the
redesign. Also, doing the move to Commons CLI now could mean some
rewriting as soon as the Avalon Container is in place. But that's
probably not so bad. As Keiron said, just yell if you need help. I'm
looking forward to any patch on the redesign!
On 02.04.2003 05:27:26 Keiron Liddle wrote:
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 CommandLineStarter.run()
which calls commandLineOptions.getOutputFile() and
commandLineOptions.getRendererOptions().
I want to use the -c option to import a font refed in a userconfig.xml
file as per
http://xml.apache.org/fop/fonts.html#Register+the+fonts+within+FOP-
N10261
I can see that CommandLineOptions.parseOptions(...) is caching my
userconfig.xml file in its userConfigFile member. Grepping the source
does not reveal anyone calling the getUserConfigFile() accessor and I'm
unable to find anyone parsing the userConfigFile, so this is what I
mean when I say that I suspect configuration is not completely
re-enabled.
To get the configuration we will probably use the DefaultConfigurationBuilder in
avalon framework:
http://avalon.apache.org/framework/api/index.html
The buildFromFile will return a Configuration object which holds all the
configuration data.
If you then look in org.apache.fop.render.pdf.PDFRenderer in the configure
method you will see that it reads the filter and font information.
I don't think there is any code to hook this up.
You could do the filename to Configuration object in the Driver. Then it could call
configure on the Renderer. I think it will need to get a child Configuration object
that matches the mime type for the renderer. Take a look at xml-fop/conf/fop.xconf
for a draft of the configuration XML format.
Good luck. If you need any more help then give us a yell.
So, I guess my question now is: Are CommandLineOptions.userConfigFile
font tags being processed? If so, then where? If not, then... yes,
given some pointers, I'm interested in helping to get it working.
Jeremias Maerki
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL
