Re: Confused with Fop extensions, distinct.
On Tuesday 16 April 2002 11:13, you wrote: I have tried to read the docs. I had used distinct before but not in an embedded application. Function not supported. Is my error message. I have inclued my stack Trace. My includes in my application. and my stylesheet. Thanks in advance for any help you can give. Check your spelling in namespace declarations and make certain the class name is coirrect for the version of Xalan you are using. I posted the following to cocoon-users a few weeks ago: This note is mostly for the benefit of anyone else searching for help with Redirect. Sorry if Xalan is a bit off topic for Cocoon2, but I expect that a lot of XSLT users will be using Cocoon as a framework for Xalan-J/XSLT-based applications. I spotted Redirect in Chapter 8(?) of XSLT by Doug Tidwell, August 2001, O'Reilly and Associates. It does work in Cocoon2 but I had a few problems getting it to run. I finally solved it by looking at the Xalan-J docs at xml.apache.org as well as the source code for Redirect. The Redirect class seems to have moved from org.apache.xalan.xslt.extensions.Redirect to the more concise org.apache.xalan.lib.Redirect. The comments in Redirect are actually useful! (thank you Mr Boag!) It appears that you need to include several namespaces in the stylesheet tag. This was another source of 'the fog of war' for me. xsl:stylesheet version=1.0 xmlns:lxslt=http://xml.apache.org/xslt; xmlns:redirect=org.apache.xalan.lib.Redirect extension-element-prefixes=redirect ... rest omitted ... This did not work for me when I followed examples from various sources. I have one minor complaint about Redirect (may apply to all extensions). This facility is terrific but it is strangely silent when things go wrong. For example, I used file=concat(... at one point and created a directory named concat( When I had mis-spelled namespace URI's nothing worked and it did so silently. When the lxslt declaration was missing ... same thing. I know I had perms wrong and was rewarded again with silence. Thanks again. Hope this helps. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
non rendered characters
Sorry to bother you all again, [sorry if you receive twice this: I mail it again because I had problems on the first attempt.] I've included here a sample .fo file and its .pdf version (in a .zip archive) that demonstrate the problem: I've noticed that text() of tags that occur at page-break as well as the characters that preceed in the same word-unit (surrounded by whitespaces) are not rendered at all in PDF and AWT view. Look at the beginning of page 15 in the pdf file: 'tensible' for 'extensible' [Efo:inlinex/fo:inlinetensible]; notice that even though the first 'e' is not surrounded by any tag, it is not rendered either. One more thing: if I process a 'simple.xml' file with occurrences like [Erx/rtensible], the same happens, even if I dont write any template for the 'r' element. Thank you all for your answers. N. Mazziotta sample.zip Description: Zip compressed data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Indenting Tables
Hi, I am fairly new to FOP and XSLFO so forgive me if I sound a bit vague... The product I am writing produces letters with the layout and content produced on the fly. The letters will have numerous tables included, but the left starting positions of each table will vary. I am trying to indentindividualtables from the page margin without success. I have tried using margin-left, start-indent and position-absolute on the table node and although the text position within the cell moves, the start of the first cell in the table always appears at the page margin. Being a newbie I am not sure if the problem lies with my FO knowledge or it is the capabilities of FOP. I would very much appreciate a FO snippet. thanks R. Tribe
Re: Driver.run() bug in FOP 0.20-3?
Rhett Aultman wrote: Greetings FOP team. I was noticing the other day that, when I attempted to embed FOP in some software that I was writing, that the default activity for Driver.run() when no other XML parser is specified is this- [..] I saw no mention of this in Bugzilla, but I could have easily missed it. Is this a known issue that someone is resolving? If it is not, I'm happy to volunteer. The CVS version (maintenance branch) has been already changed to use JAXP for obtaining a XML parser (SAXParserFactory) J. Rhett Aultman Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3497] - id already exists error when using span=all attribute
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=3497. 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=3497 id already exists error when using span=all attribute --- Additional Comments From [EMAIL PROTECTED] 2002-04-17 18:20 --- Created an attachment (id=1606) Possible fix, for ids associated with fo:block - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3497] - id already exists error when using span=all attribute
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=3497. 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=3497 id already exists error when using span=all attribute --- Additional Comments From [EMAIL PROTECTED] 2002-04-17 18:23 --- As far as I have been able to tell, this is due to FOP having to reconsider how it is laying out the elements on the page. It starts filling up one column, then encounters the span=all block so it has to rebalance what came before. It rolls back the layout, but leaves any id registered so far still registered. The solution is to make sure that ids are unregistered after a rollback. The attached patch fixes the problem when the id that supposedly exists belongs to a fo:block. A better solution would fix the problem for all the objects that call IDReferences().createID(). The patch was created against version 0.20.3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Problem embeding pdf in browser using security constraint in Tomcat 4.0.3
Hi I am using FOP to embbed pdf files in browser with a servlet, usingtomacat 4.0.3, I try the FOPSERVLET example and its working fine, but if =Iput the security constraint in the web.xml file of my context , I get awhite page, instead of de pdf file, the pdf file is generated correctly, =ifI save to disk, i can see it, but is not showed in the browser.Greetings,Alberto AlarconI am using tomcat 4.0.3fop Fop-0.20.3rcand jdk 1.3.1_02
DO NOT REPLY [Bug 6863] - FOP does not close file stream, hence cannot delete XML file
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=6863. 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=6863 FOP does not close file stream, hence cannot delete XML file --- Additional Comments From [EMAIL PROTECTED] 2002-04-17 20:22 --- Created an attachment (id=1607) Sample code that I am using - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 6863] - FOP does not close file stream, hence cannot delete XML file
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=6863. 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=6863 FOP does not close file stream, hence cannot delete XML file --- Additional Comments From [EMAIL PROTECTED] 2002-04-17 20:29 --- Created an attachment (id=1608) Sample code that I am using - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 6863] - FOP does not close file stream, hence cannot delete XML file
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=6863. 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=6863 FOP does not close file stream, hence cannot delete XML file [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2002-04-17 20:37 --- I attached my sample source Java code that I am using.I did not know that attaching it would actually send you an -email so you may have received the sample code in an earlier e-mail too. As you can see I creating an XML file and passing it as an argument to my method called generatePDF. I pass that File object as an argument to the constructor of XSLTInputHandler, then I perform the FOP conversion. Then in the finally clause of the print method I am deleting the XML file since I no longer need it. I have been noticing that the delete method in the File class has been returning true (successful) on Unix but has been returning false (Failed) on NT. Also the file itself is actually deleted on Unix but not deleted on NT. I thought this could be happening because of threading that may be taking place in the FOP library and hence introduced a sleep just before the delete, did not help. I would appreciate it if you could let me know how to fix this proble. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
linefeed-treatment=preserve
Greetings FOP experts. I am building report engine for tomcat. What I do is stream the data into and XML file and the resulting file is passed to the XSLTInputHandler with appropriate XSLT. Currently everything works quite well, however, all carriage returns in the data are stripped out during the PDF conversion in the XSLTInputHandler. After reading the XSL spec on w3c this seems to be behaving as expected: The default linefeed-treatment is set to be treat-as-space so all CRs are changed to spaces :(. As well, when I try to set linefeed-treatment=preserve I get the following warning during parsing: property - linefeed-treatment is not implemented yet. It seems to me that there has to be a way to get around this. Surely, someone out there has CRs in their data that they want to render? Thanks, Shawn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8229] New: - PNG image support??
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=8229. 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=8229 PNG image support?? Summary: PNG image support?? Product: Fop Version: 0.20.3 Platform: Other OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: images AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Just want to find out is that any reason whey you guys don't support PNG image in the current version? If there any plan to add that back to the FOP package? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
External Links
By looking at PDF I think a link has to be coded like this (copy in the samples): fo:basic-link external-destination=destinationlink_rectangle/fo:basic-link o destination: an URI, where it makes a difference if there is an extension .pdf or not o link_rectangle: the rectangle on the page to click on So, if you want to have an image in the rectangle: fo:basic-link external-destination=http://nagoya.apache.org/the_image_to_be_pointed_to.jp g fo:external-graphic src=my_rendered_image.jpg/ /fo:basic-link The destination has to be a full URI for a file! Hansuli Anderegg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 6863] - FOP does not close file stream, hence cannot delete XML file
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=6863. 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=6863 FOP does not close file stream, hence cannot delete XML file [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-04-18 05:46 --- As Keiron already stated, the caller is responsible for closing the stream. You have to call out.close() after Driver.render()!. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8229] - PNG image support??
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=8229. 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=8229 PNG image support?? [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2002-04-18 05:51 --- Well, that's not really a reason to open a bug case. You could have dropped us a mail on the fop-user mailing list (or read the stuff on the website). PNG is supported through the JIMI image library from Sun. jimi.jar had to be removed from the distribution because of licence reasons. Just get jimi.jar, out it in the lib directory and do a full rebuild of FOP and you'll have your PNG support. See also: http://xml.apache.org/fop/relnotes.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
