VS: Win32
Hi, Practically you have to be a Java programmer at a basic level to be able to use FOP. (This is my opinion) Or maybe you can use it for learning XSL-FO in other case, if someone deploys the servlet on your machine Teemu Talja [EMAIL PROTECTED] [EMAIL PROTECTED] työpuhelin 0307 20138 GSM 040 55 43 156 -Alkuperäinen viesti- Lähettäjä:Alastair Growcott [SMTP:[EMAIL PROTECTED] Lähetetty:22. maaliskuuta 2002 17:55 Vastaanottaja:[EMAIL PROTECTED] Aihe: Win32 Hi, I am a sad person who does not have Java on my machine, or any idea how to use it even if I did get my hands on a copy (I actually have a very nice Java developer environment with lots of help files on a CD-ROM, but not with me for another month or so). Hence although I have downloaded the distribution release of FOP (including all the nice help files and read-me files), I can't really use it. Is there anyone out there who can give me a nice easy to use Win32 executable built from a reasonably recent release of the FOP Java code. I would very appreciative. But probably not in a fiscal manner :) Alastair Growcott.
fop exits after first loop
hi, i have a little problem. i have various xml-files and wanted to convert the to pdf. so i have written a loop in which i create and fill the string array and make a new org.apache.fop.apps.Fop object with the string array as parameters. but after the first loop my programm exits. as if it was finished. is there a System.exit(0) line in the fop code?. can anybody help me? cu mk
Keep togehter within page
Hello i am new on this mailgroup, so i dont't know how many times my question has been asked before. The attribute keep together within page doesnt work exactly. Anywhere i read that the fop folks of apache are on their way to solve this problem. Any updates for this answer? Greets jochen Dipl.-Inform. (FH) Skillworks AG Hafenstrasse 10 78462 Konstanz Germany
Caught the exception !
I had to use the command line. Here's what i get: javax.xml.transform.TransformerException at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1212) at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2894) at java.lang.Thread.run(Thread.java:484) - java.lang.NullPointerException at org.apache.fop.fo.pagination.PageSequence.isFlowForMasterNameDone(PageSequence.java:591) at org.apache.fop.fo.pagination.PageSequence.getNextPageMasterName(PageSequence.java:477) at org.apache.fop.fo.pagination.PageSequence.getNextSimplePageMaster(PageSequence.java:455) at org.apache.fop.fo.pagination.PageSequence.getNextPageMaster(PageSequence.java:523) at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:334) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:268) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:200) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:182) at org.apache.xalan.transformer.ResultTreeHandler.endElement(ResultTreeHandler.java:284) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:749) at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:495) at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:193) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2154) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2097) at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2029) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1189) at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2894) at java.lang.Thread.run(Thread.java:484) (plz see my previous post to know what it's all about) Regards, Guillaume Mathe Smartinnov
Oops let me reformulate - page sequence reset ?
Hi, I've solved that exception problem - it was only a matter of 'master-name' instead of 'master-reference' in 'conditional-page-master-reference'. Anyway, i don't have the expected results. How can i start over the page-sequence each time i start a new subdoc ? This way i have a new 'first', 'rest' etc.. set of pages. For those who missed the first post, here's a xml structure i have: doc subdoc part-a/ part-b/ /subdoc subdoc part-a/ part-b/ /subdoc ... /doc part-a is one-page, part-b is multi-page. I want special static contents on each part-a, and other static contents on each part-b. So what's the best way to do this ? Regards, Guillaume Mathe Smartinnov
Re: AW: feature and limitation lists
Here's a DTD segregated by FOP imlemented and non-implemented features. The implemented and non-implemented values have not been segregated. Chuck Paussa Fries, Markus, fiscus GmbH, Bonn wrote: On 2002.03.21 09:47 Fries, Markus, fiscus GmbH, Bonn wrote: Hi, a lot of questions on this list are caused by properties which are not implemented. Often there are workarounds though. I think it would make sense to put some real effort into http://xml.apache.org/fop/limitations.html and http://xml.apache.org/fop/implemented.html. Or maybe there is such a collection already of which I don't know? Regards, Markus Fries Hi, If you have any suggestions about how to do this easily then share your ideas with us. Do you have some volunteers in mind to put the real effort into getting this done? Hi, I can think of one volunteer so far :). I have to do some documentation on that stuff for my project anyway and if my supervisor does not mind I can share that. Jens: I've suggested (or asked) to create a special fop.dtd (not a fo.dtd). This wouldn't regard all limitation and no workarounds, but it would be a very good tool for imlementing applications using FOP. ... A fop.dtd will answer all these question like: Feature XYZ is not working, is it a bug in my FO document or a missing FOP feature. Maybe workarounds can be mentioned in the fop.dtd, too. Since fo.dtd exists, it wouldn't be too much work to add these comments. Yes, I think this would be very helpful. But it has one drawback though. You realize only after implementing that s.th. doesn't work and expensive rework is necessary. Anyway the fop.dtd sounds like a very good start. When it gets running we can think of rearranging the collected information in addiditional documentation. What do you think? Best regards Markus Fries attachment: fop4d.zip
Re: feature and limitation lists
Here's an FOP specific xsd. I sent the segregated DTD in a previous response on this same thread. It's a pain to make a usable XSD from a DTD because the conversion tools tend to explode everything out and you get enormous repeating elements. Anyway. Here it is for what it's worth. Chuck Paussa MAISONNY Benoit wrote: Say we have an FO schema (possibly converted from that fo.dtd) and from that we remove what FOP doesn't do yet. Then we can easily compare both schemas with XSLT and generate a nice report. (I would volunteer to try and write that XSLT/report if people think it can be useful). Then we can add comments or annotations to tell about workarounds and about what is implemented BUT still is not working as expected. However, I suppose it would be a lot of work to remove unimplemented things from fo.dtd or fo.xsd. What do you think? Benoit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, March 21, 2002 1:33 PM To: [EMAIL PROTECTED] Subject: RE: feature and limitation lists Hello, Markus wrote: If you have any suggestions about how to do this easily then share your ideas with us. I've suggested (or asked) to create a special fop.dtd (not a fo.dtd). This wouldn't regard all limitation and no workarounds, but it would be a very good tool for imlementing applications using FOP. E.g.: fo.dtd (I know that there's no official fo.dtd, I took the one created by Nikolai Grigoriev [EMAIL PROTECTED]): -8X8X--- !ENTITY % area-properties clip CDATA #IMPLIED [..] [ ... block-properties is an entity based (indirectly) on area-properties ... ] !ELEMENT fo:block (#PCDATA | fo:initial-property-set | %basic-inlines; | %basic-blocks; | %out-of-lines; | %wrappers;)* !ATTLIST fo:block %block-properties; -8X8X--- FOP.dtd: -8X8X--- !ENTITY % area-properties !-- clip CDATA #IMPLIED not implemented by FOP yet --- [..] [ ... block-properties is an entity based (indirectly) on area-properties ... ] !ELEMENT fo:block (#PCDATA | fo:initial-property-set | %basic-inlines; | %basic-blocks; | %out-of-lines; | %wrappers;)* !ATTLIST fo:block %block-properties; -8X8X--- I don't know how FOP is implementing these features, maybe it would be easier to remove these entities and list all attributes and content elements explicit. But maybe these entities represent the internal implementation structure... A fop.dtd will answer all these question like: Feature XYZ is not working, is it a bug in my FO document or a missing FOP feature. Maybe workarounds can be mentioned in the fop.dtd, too. Since fo.dtd exists, it wouldn't be too much work to add these comments. Regards, Jens attachment: fop4da.zip
RE: Reporting Engine !!
Look up JReport at www.jinfonet.net see whether they have FO support yet. I have been using RTF2FO and XEP (or FOP). - sb -
RE: Reporting Engine !!
how do I unsubscribe from this mailing list? -Original Message- From: Buonincontri, Steve (CAP, MMF, ITSS) [mailto:[EMAIL PROTECTED] Sent: Monday, March 25, 2002 10:17 AM To: [EMAIL PROTECTED] Subject: RE: Reporting Engine !! Look up JReport at www.jinfonet.net see whether they have FO support yet. I have been using RTF2FO and XEP (or FOP). - sb -
Widows and Orphans Setting
Hi folks I have a problem. I am trying to use the attributes widows and orphans to control the page break. I wish to avoid the situation that a title dos not come at the end of a page alone. It should come in the next page, if there is no space for 3-4 lines following it. Please refer to the fop extract below. I still end up with the situation that the title appears in one page and the text appears in the next page. Where am I going wrong ? Thanx a million in advance Rgds Jay * FOP EXTRACT fo:block text-align=start orphans=3 widows=3 Here is a title fo:block space-after=0.0cm This is the text that should come under the title.. There are many lines. This is cut off in this mail.. /fo:block /fo:block END OF FOP EXTRACT *
AW: Reporting Engine !!
To remove your address from the list, send a message to: [EMAIL PROTECTED] -Ursprüngliche Nachricht- Von: Woods, John T. [mailto:[EMAIL PROTECTED] Gesendet: Montag, 25. März 2002 19:21 An: '[EMAIL PROTECTED]' Betreff: RE: Reporting Engine !! how do I unsubscribe from this mailing list? -Original Message- From: Buonincontri, Steve (CAP, MMF, ITSS) [mailto:[EMAIL PROTECTED] Sent: Monday, March 25, 2002 10:17 AM To: [EMAIL PROTECTED] Subject: RE: Reporting Engine !! Look up JReport at www.jinfonet.net see whether they have FO support yet. I have been using RTF2FO and XEP (or FOP). - sb -
long word wrapping problem solved in Fop-0.20.1 ???
Title: long word wrapping problem solved in Fop-0.20.1 ??? I have a word 12345678 and the space defined in table-column is 1 inch then it spills over. If the words are spaced out ,then wrapping occurs 1 2 3 4 5 6 7 8. So you see, fo:block wrap-option=wrap in Fop-0.20.1 is still not working ? I would be glad if anyone of you could help me out. Thanks, Jie -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED]] Sent: Monday, March 25, 2002 11:30 AM To: [EMAIL PROTECTED] Subject: Re: Adding columns using XSL Josh Campbell wrote: I've got a column of numbers being pulled out of XML that I want to total at the bottom of the page using the XSL. I don't know how many rows of figures will be generated so need something that can just take all the values in a column and add them up Check out the sum() function: http://www.w3.org/TR/xpath#section-Number-Functions If your XML is something like this records record namefoo/nameprice99.0/price record /record namebar/nameprice100.0/price /record /records use it like xsl:template match=records xsl:textTotal: /xsl:text xsl:value-of select=sum(record/price)/ /xsl:template If your problem is more complicated, ask on the XSL list (http://www.mulberrytech.com/xsl/xsl-list/), because you have an XSLT problem rather than a FOP problem. Provide some more details: a relevant snippet of your XML, and how to derive the total you are after. If your computation involves something like price*quantity per record, look into the list archives first. J.Pietschmann
Re: Oops let me reformulate - page sequence reset ?
Guillaume Mathe wrote: How can i start over the page-sequence each time i start a new subdoc ? doc subdoc part-a/ part-b/ /subdoc subdoc part-a/ part-b/ /subdoc Generate multiple fo:page-sequence elements: xsl:template match=/ fo:root fo:layout-master-set ... /fo:layout-master-set xsl:apply-templates/ /fo:root /xsl:template xsl:template match=subdoc fo:page-sequence master-reference=... fo:static-content ... fo:static-content fo:flow xsl:apply-templates /fo:flow /fo:page-sequence /xsl:template Look up the initial-page-number attribute for fo:page-sequence starting with something else than page 1. J.Pietschmann
Re: Widows and Orphans Setting
S. Jayaraman wrote: I have a problem. I am trying to use the attributes widows and orphans to control the page break. You are probably out of luck. The table of implemented features (you can find it in your distribution, file docs/html-docs/implemented.html or on the Apache Fop site) does not mention either property, and states All other properties are not implemented. The implementation of this and some related features is the object of the current efford, but it will take some time to get it done. J.Pietschmann
Re: XSLTInputHandler question
Jeff Pennal wrote: I want to create an XSLTInputSource, but I have dynamically generated the XML file in memory and I do not want to commit it to disk just to have a File object to point to. You have to use DOM or, preferably, SAX to wire your transformer to the FO processor. Try something like this: // set up your transformation Transformer transformer =TransformerFactory.newInstance().newTransformer(xsltSource); // prepare FOP Driver driver=new Driver(); driver.setOutputStream(...); driver.setRenderer(Driver.RENDER_PDF); // transform, this also drives the formatter transformer.transform(xmlSource, new SAXResult(driver.getContentHandler())); HTH J.Pietschmann
FOP rendering of SVG fonts
I am attempting to embed an SVG image in an XSL-FO file referenced by a URL to produce a PDF output stream. I am using Fop 0.20.3 and the supplied batik.jar to dynamically produce the SVG image ( from a KavaChart chart ). This approach works fine until I try and set a particular font in the SVG image (chart), as the image fonts in the resulting PDF doesn't look that great. I have configured my userconfig.xml with the entry keystrokeSVGText/key valuefalse/value /entry settings so Fop uses the PDF fonts for SVG. The image fonts look better, but the spaces between words appear like square blocks []. Are there any plans to enhance Fop's font rendering of SVG images, or any alternative workarounds I could try ? Many Thanks, Simon Toulson. -- Simon Toulson CREDIT | FIRST SUISSE | BOSTON Equity Capital Markets IT, London Direct: +44-207-888-5268 This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business units of CREDIT SUISSE FIRST BOSTON reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. Unless otherwise stated, any pricing information given in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation.
