[DOCUMENTATION] Understanding part 8+9
Hi Fopers, I have read my name on the FO status thread and I have realized I have forgotten some of my work :) Here are the Understanding series part 8 and 9 formated in xml acording document-v10.dtd. congratulation to the newly voted commiters ! Hope it helps Cyril area_tree.xml Description: application/xml renderers.xml Description: application/xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Problems with baseline-shift
Hi all, I'm trying to do the following: xsl:template match=superscript xsl:if test=string(.) fo:inline baseline-shift='super' xsl:apply-templates/ /fo:inline /xsl:if /xsl:template The XML file can look something like: paragraph blablabla superscripttest/superscript blablabla /paragraph That is, I'm trying to shift the text to superscript... Like in 1*10^8, with the 8 'hanging' above the rest.. However, it does not work.. Nothing happens. What have I done wrong? Thanks! Emma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Problems with baseline-shift
Hi, try vertical-align=super. Regards, Etwin - Original Message - From: Emma Larsson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 2:00 PM Subject: Problems with baseline-shift Hi all, I'm trying to do the following: xsl:template match=superscript xsl:if test=string(.) fo:inline baseline-shift='super' xsl:apply-templates/ /fo:inline /xsl:if /xsl:template The XML file can look something like: paragraph blablabla superscripttest/superscript blablabla /paragraph That is, I'm trying to shift the text to superscript... Like in 1*10^8, with the 8 'hanging' above the rest.. However, it does not work.. Nothing happens. What have I done wrong? Thanks! Emma - 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: Problems with baseline-shift
I think baseline-shift is not implemented, yet. Try vertical-align instead. There's an example in docs/examples/footnotes/columns.fo. Please post this kind of question on the fop-user mailing list in the future. Thanks! I'm trying to do the following: xsl:template match=superscript xsl:if test=string(.) fo:inline baseline-shift='super' xsl:apply-templates/ /fo:inline /xsl:if /xsl:template The XML file can look something like: paragraph blablabla superscripttest/superscript blablabla /paragraph That is, I'm trying to shift the text to superscript... Like in 1*10^8, with the 8 'hanging' above the rest.. However, it does not work.. Nothing happens. What have I done wrong? 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]
Re: Problems with baseline-shift
What element is vertical-align attribute to? I can't find it.. Thanks for the quick respond! /Emma - Original Message - From: Etwin van Krimpen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 2:10 PM Subject: Re: Problems with baseline-shift Hi, try vertical-align=super. Regards, Etwin - Original Message - From: Emma Larsson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 2:00 PM Subject: Problems with baseline-shift Hi all, I'm trying to do the following: xsl:template match=superscript xsl:if test=string(.) fo:inline baseline-shift='super' xsl:apply-templates/ /fo:inline /xsl:if /xsl:template The XML file can look something like: paragraph blablabla superscripttest/superscript blablabla /paragraph That is, I'm trying to shift the text to superscript... Like in 1*10^8, with the 8 'hanging' above the rest.. However, it does not work.. Nothing happens. What have I done wrong? Thanks! Emma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [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]
AW: Problems with baseline-shift
fo:inline vertical-align=super .../fo:inline -Ursprüngliche Nachricht- Von: Emma Larsson [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 18. April 2002 14:13 An: [EMAIL PROTECTED] Betreff: Re: Problems with baseline-shift What element is vertical-align attribute to? I can't find it.. Thanks for the quick respond! /Emma - Original Message - From: Etwin van Krimpen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 2:10 PM Subject: Re: Problems with baseline-shift Hi, try vertical-align=super. Regards, Etwin - Original Message - From: Emma Larsson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 2:00 PM Subject: Problems with baseline-shift Hi all, I'm trying to do the following: xsl:template match=superscript xsl:if test=string(.) fo:inline baseline-shift='super' xsl:apply-templates/ /fo:inline /xsl:if /xsl:template The XML file can look something like: paragraph blablabla superscripttest/superscript blablabla /paragraph That is, I'm trying to shift the text to superscript... Like in 1*10^8, with the 8 'hanging' above the rest.. However, it does not work.. Nothing happens. What have I done wrong? Thanks! Emma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Problems with baseline-shift
Thank you.. I'm sorry about posting this question to the wrong list.. It wont happen again! - Original Message - From: Henrik Holle [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 2:15 PM Subject: AW: Problems with baseline-shift fo:inline vertical-align=super .../fo:inline -Ursprüngliche Nachricht- Von: Emma Larsson [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 18. April 2002 14:13 An: [EMAIL PROTECTED] Betreff: Re: Problems with baseline-shift What element is vertical-align attribute to? I can't find it.. Thanks for the quick respond! /Emma - Original Message - From: Etwin van Krimpen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 2:10 PM Subject: Re: Problems with baseline-shift Hi, try vertical-align=super. Regards, Etwin - Original Message - From: Emma Larsson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 2:00 PM Subject: Problems with baseline-shift Hi all, I'm trying to do the following: xsl:template match=superscript xsl:if test=string(.) fo:inline baseline-shift='super' xsl:apply-templates/ /fo:inline /xsl:if /xsl:template The XML file can look something like: paragraph blablabla superscripttest/superscript blablabla /paragraph That is, I'm trying to shift the text to superscript... Like in 1*10^8, with the 8 'hanging' above the rest.. However, it does not work.. Nothing happens. What have I done wrong? Thanks! Emma - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[GUMP] Build Failure - xml-fop
This email is autogenerated from the output from: http://jakarta.apache.org/builds/gump/2002-04-18/xml-fop.html Buildfile: build.xml init-avail: init-filters-xalan2: [copy] Copying 1 file to /home/rubys/jakarta/xml-fop/build/src/codegen init: [echo] --- Fop 1.0dev [1999-2002] prepare: [echo] Preparing the build directories [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/svg [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/conf [mkdir] Created dir: /home/rubys/jakarta/xml-fop/build/classes/hyph [copy] Copying 3 files to /home/rubys/jakarta/xml-fop/build/classes/conf codegen: [echo] Resetting codegen directory [copy] Copying 30 files to /home/rubys/jakarta/xml-fop/build/src/codegen [echo] Generating the java files from xml resources [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/allprops.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/Constants.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/genconst.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/fo_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/properties.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/FOPropertyMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/propmap.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/foproperties.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/fo/properties/foenums_ignore_this.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/enumgen.xsl [style] Processing /home/rubys/jakarta/xml-fop/build/src/codegen/charlist.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/CodePointMapping.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/code-point-mapping.xsl [style] Transforming into /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBold.java [style] Loading stylesheet /home/rubys/jakarta/xml-fop/build/src/codegen/font-file.xsl [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Courier.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Courier.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierBoldOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/CourierOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/CourierOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Helvetica.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Helvetica.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBold.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaBoldOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaBoldOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/HelveticaOblique.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/HelveticaOblique.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/Symbol.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/Symbol.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBold.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBold.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesBoldItalic.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesBoldItalic.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesItalic.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesItalic.java [style] Processing /home/rubys/jakarta/xml-fop/src/codegen/TimesRoman.xml to /home/rubys/jakarta/xml-fop/build/src/org/apache/fop/render/pdf/fonts/TimesRoman.java [style] Processing
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-18 13:41 --- As I was trying to say, it is not the PDF file that the problem is with. The problem is with the XML file. Anyway I found the following URL on the web and will try that out. http://archive.covalent.net/xml/general/2000/05/0193.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
wrong lists - 2cents
Just my random, well-intentioned 2 cents on the frequency with which user questions show up here. Mind you, I don't find them all that annoying; some - including me - would say it doesn't hurt to have developers see what the real world is up to. But I have noticed that increasingly folks show signs of having been told (off list) that they're asking in the wrong place. I can't help but wonder if some of the user questions that stray onto this list do so because of confusion engendered by the list names. I can imagine someone thinking ah, I, a developer building a fop app, need help; I'll send my question to this here fop-dev list I could go on about the disinclination of certain red-blooded developers to ever believe they are a user but maybe I won't go there ;-) Perhaps a simple rename of the current fop-dev to Fop-internals would help ? btw Some might say the web page is pretty explicit about which list is which - to which I might say and your point is ? 'best -Ralph LaChance Oh my, I hope this doesn't launch a firestorm ;-) - 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-18 13:50 --- Sorry, this happens when a lot of people have problems with the OutputStream. Reopen the bug if the problem does not go away when replacing the XML parser or xalan with a different version. I'll then try to investigate. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Embedding FOP
-Original Message- From: Hans-Jürgen Wiesner [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 10:21 AM To: [EMAIL PROTECTED] Subject: Embedding FOP [snip] INFO10191 [fop ] (): building formatting object tree DEBUG 10191 [fop ] (): setting up fonts ERROR 10191 [fop ] (): Unknown formatting object ^html The message text of the exception says: Root element must be root, not (none):html This seems to mean my DTD, which I deleteted; if I use a valid DTD: !DOCTYPE xhtml PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; This may sound like a bizarre question, but you are transforming the XHTML to a FO document before you attemt to render it, right? To the best of my knowledge, you must perform your own transforms and provide FOP with valid FO. Are you using a technique like the recommended one for going from an XML document to FO like this one listed on the FOP website: Driver driver = new Driver(); driver.setRenderer(Driver.RENDER_PDF); InputHandler inputHandler = new XSLTInputHandler(xmlFile, xslFile); XMLReader parser = inputHandler.getParser(); driver.setOutputStream(new FileOutputStream(outFile)); driver.render(parser, inputHandler.getInputSource()); I just ask because, if your XHTML what's getting into driver.render(), it's going to blow up. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: wrong lists - 2cents
Hi Ralph Just my random, well-intentioned 2 cents on the frequency with which user questions show up here. Mind you, I don't find them all that annoying; some - including me - would say it doesn't hurt to have developers see what the real world is up to. But I have noticed that increasingly folks show signs of having been told (off list) that they're asking in the wrong place. It's not that we're not also on the fop-user list, you know. I think we're just trying to get users to finally use fop-user for their questions. More and more, they can also help themselves. That's a good sign. I mean we have a big user base already and a relatively small developer circle on the other side. And some of them are working hard on the redesign so that some user requirements are even possible to implement. But I think nobody has ever been told off without an answer to the question a the same time. It has taken a long time to separate fop-dev and fop-user. To do that people had/have to be redirected (as politely as possible, of course). I can't help but wonder if some of the user questions that stray onto this list do so because of confusion engendered by the list names. I can imagine someone thinking ah, I, a developer building a fop app, need help; I'll send my question to this here fop-dev list I could go on about the disinclination of certain red-blooded developers to ever believe they are a user but maybe I won't go there ;-) Perhaps a simple rename of the current fop-dev to Fop-internals would help ? You may be right. It may be a weak argument that the dev/user scheme is used all over the XML project. In this regard your thought should probably be targeted one level higher up. btw Some might say the web page is pretty explicit about which list is which - to which I might say and your point is ? Oh my, I hope this doesn't launch a firestorm ;-) We'll see. :-) 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]
Re: Printing Page Setup
You could use XSLT parameters to set page-width/height and borders. I've a problem with setup the printed page sizes. In the Application the user (must have) has the possibility to change the papar format of the printed documents. I'm using AWTRenderer to preview some files on screen before printing. My xsl templates have an Page Master like this: fo:simple-page-master master-reference=A4 width=... If the user wants to print out the rendered page for example in letter format with defined margines I've to scale width and height of the rendered page before sending graphic to printer. I cannot using scalefactor because of the geometry of the page isn't compatible to the original. Can anyone explain me what I've todo. Writing different templates for each possible Paper-Size isn't acceptable. 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]
RE: linefeed-treatment=preserve
We do what you are asking. According to our FO expert (not me) using fo:block white-space-collapse=false has the side effect (in FOP) of causing FOP to recognize carriage returns. Jim [PARA]Jim Urban - [EMAIL PROTECTED][TAB][PARA]Clinical Connectivity Suite Product Manager[PARA]Suite 295[PARA]500 Park Blvd.[PARA]Itasca, IL 60143[PARA]Voice: (630) 250-3045 x106[PARA]Fax: (630) 250-3046[PARA][PARA]Advancing Healthcare Performance[PARA]www.parkcitysolutions.com[PARA] -Original Message- From: Shawn Bedard [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 11:14 AM To: [EMAIL PROTECTED] Subject: 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Indenting Tables
Roger Tribe wrote: I am trying to indent individual tables from the page margin without success. This appears to be intentional, though inconvenient. I read the spec about a dozen times, or so, and the behaviour appears to be conformant. Tables are not block level elements for some strange reason. I usually create an invisible column serving as margin: fo:table table-layout=fixed fo:table-column column-width=2cm/ fo:table-column border-color=black border-style=solid border-width=.5mm column-width=3cm/ fo:table-body fo:table-row fo:table-cell/ fo:table-cell fo:blockstuff/fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table If you use XSLT to generate the file, it should not be too hard to keep block margins and the table column width consistent. I have tried using margin-left, start-indent and position-absolute on the table node and although the text position within the cell moves, Thats because table cell areas are reference areas. You have to reset most block properties on the table element if you don't want to have them inherited. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Keep-Together
David B. Bitton wrote: Can someone give me a 100 words or less on keep-together? What I'm most confused is using 1 through 9 as apposed to always. I think my keep-together problem would be solved with this, but I'm not sure how to use it. Tx :) I don't think keep-together will solve your problem if you are using FOP, because it's not implemented. For the numbers: they indicate the strength of the keep condition, higher numbers mean greater strength. This is useful because long stretches of keep may have to be broken anyway. An example: fo:block keep-together=1 fo:block keep-together=3 /fo:block fo:block keep-together=5 /fo:block /fo:block If the span is too long to fit the available space (the page, for example), or there are other conditions which lead the renderer to the conclusion that there should be a break anyway (for example because large white areas look awful), the strenght of the keep-condition is used to determine your preferences for a break. In the example above, the renderer will first check whether a break between the two embedded blocks will be acceptable, because that's the keep whith the lowest precedence. If that fails, it will try to break within the first embedded block, and if this still fails, it will try the second. Does this help? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Problem embeding pdf in browser using security constraint inTomcat 4.0.3
Alberto Alarcon wrote: Hi I am using FOP to embbed pdf files in browser with a servlet, using tomacat 4.0.3, I try the FOPSERVLET example and its working fine, but if = I put the security constraint in the web.xml file of my context , I get a white page, instead of de pdf file, the pdf file is generated correctly, = if I save to disk, i can see it, but is not showed in the browser. What do you mean by security constraint? Do you get your PDF again if you remove the security constraint? It this case it is likely that this is a problem with your server. Otherwise, it may be your browser, some IEx versions are known to have problems starting Acrobat reader under certain circumstances. fop Fop-0.20.3rc It is recommended to upgrade to the final 0.20.3 release in all cases. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: linefeed-treatment=preserve
Shawn Bedard wrote: 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? You can try enclose CR delimited blocks at the XSLT level. The usual approach is to write a recursive template xsl:template name=make-block xsl:param name=text fo:blockxsl:value-of select= substring-before($text,'#xA')/ /fo:block xsl:call-template name=make-block xsl:with-param select= substring-after($text,'#xA')/ /xsl:call-template /xsl:template Use this like xsl:template match=description fo:block xsl:call-template name=make-block xsl:with-param select=. /xsl:call-template /xsl:template Put font, spacing and other properties on the enclosing block. If you have mixed content, this is more of a challenging problem, as the approach above wont work. Look at the XSL FAQ and into the XSL mailing list archive for more tricks: http://www.mulberrytech.com/xsl/xsl-list/ HTH J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: wrong lists - 2cents
Jeremias Maerki wrote: You may be right. It may be a weak argument that the dev/user scheme is used all over the XML project. In this regard your thought should probably be targeted one level higher up. Well, it's an apache standard, and the generally copied charters state clearly: dev: discussions *among* developers user: user discussions and help There is the option to use bugzilla for feature requests (i don't know whether this is used for FOP, is is handled this way for Ant) J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Embedding FOP
Hans-Jürgen Wiesner wrote: Hello all, I'm new to FOP and are charged with embedding it in a Servlet application. We need to send a JSP as HTML or PDF, depending on the user. So we made a JSP which outputs valid XHTML and tried to convert that via FO into PDF. After much experimentation, I succeeded in installing a filter intercepting the JSP-Servlets output to convert it by calling FOP. The conversion works on the command line; however, I have great problems embedding FOP in my filter. It is usually not a good idea to use JSP to generate XML for further processing. Well, you can use a SAX event stream to overcome the unfortunate design of the XSLTInputHandler, look here: http://marc.theaimsgroup.com/?l=fop-userm=101735493205659w=2 This way you can supply an arbitrary XML source to your transformer. For generating the data, i suggest to look into writing your own SAX source. The basics are much easier than many people think: implement the javax.xml.parser.XMLReader interface, and if necessary provide your own implementation of an InputSource to provide run time parametrization. The next problem is that FOP doesn't convert when called from my filter. I get an exception from driver.render(); the logger tells me: INFO10191 [fop ] (): building formatting object tree DEBUG 10191 [fop ] (): setting up fonts ERROR 10191 [fop ] (): Unknown formatting object ^html Your transformation transforms your XML to XHTML. You have to write a transformation which transforms into XSLFO. FOP can not render XHTML (it would be named XHTMLP if it could) J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
inital background-image patch
Guys, An initial maintenance-branch patch for background-image and background-repeat property support can be found at: http://web.vee.net/fop/background-image_0.01.patch This patch is *not* ready to get comitted to the repository, rather I'm posting it to a) get some help testing it, b) get feedback about the nature and scope of the changes I've made. So please, have a look at it, try it out, and send me as much feedback as possible, especially on: - The API changes to AbstractRenderer. - Changing addRectFoo() to only ever expect +ve heights. - Seeing if the MIF and TXT renderers still work as advertised (but without bg image support). To support background images, the following has changed: - Implemented the background-image and background-repeat properties. - PropertyManager resolves the bg image source to a FopImage when first retreiving an instance of BackgroundProps. - Areas now store an instance of BackgroundProps rather than just the background color. - AbstractRenderer has a concrete doBackground() method, and abstract drawImageFoo() methods to support doBackground(), renderImageArea() and possibly others. - PDFRenderer and PrintRenderer have been modified to use doBackground() and provide concrete implementations of the drawImageFoo() methods. As a direct result: - PDFRenderer.renderImageArea() has been generalized and moved into AbstractRenderer. - Start of support for working region-foo backgrounds has been added - The addRectFoo() methods should now expect only +ve heights Stuff that isn't working: - All renderers other than PDFRenderer, and possibly the MIF renderer and TXTRenderer. - Image cropping, so on a tiled background, the last row and column of images are scaled rather than cropped if the width/height if the content area isn't an exact multiple of the image's width/height. Binaries for testing can be found at: http://web.vee.net/fop/fop-background-image-0.01-bin.tar.gz http://web.vee.net/fop/fop-background-image-0.01-bin.zip Please *do not* use this binary in a production system. Thanks (especially for reading this far ;), Mike. -- Michael Gratton [EMAIL PROTECTED] Recall Design http://www.recalldesign.com/ s: 53 Gilbert Street Adelaide SA 5000 Australia t: +61 8 8217 0500 f: +61 8 8217 0555 smime.p7s Description: S/MIME Cryptographic Signature
