RE: External links around graphics (no text) don't work.
I'm not sure on version - too many different machines and OS's. Probably 0.20.4. Also recently changed up to j2sdk1.4.0 (everywhere I think). I will try 0.20.5rc2 (haven't loaded it yet - mine just says 0.20.5rc)), recreate the test and see if the problem persists. If there have been some fixes then hopefully should work. I'll only repost with example if it doesn't work. Thanks for the prompt response. -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: 21 February 2003 18:40 To: [EMAIL PROTECTED] Subject: Re: External links around graphics (no text) don't work. Mike Trotman wrote: > I am using FOP to produce PDF output. I need to produce a graphic > which is a link to a web page. The external link feature works fine if > the content is text - but if it is only a graphic then I can't find > the link. What FOP version are you using? There has been some fixess in this area for the most recent version. If you use already 0.20.5rc2, please provide a small, self-contained example (including all graphics!) which demonstrates the problem. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Stack Trace (was: newbie hyphenation...)
Aaron Weber wrote: Funny thing is, I don't know that I even *have* any tables, at least not that I put in myself... DocBook might have put in something for you. Anyway, here's the stack trace: [ERROR] null ... java.lang.NullPointerException at org.apache.fop.fo.PropertyManager.getTextDecoration(PropertyManager.java:328) at org.apache.fop.fo.FObjMixed.(FObjMixed.java:28) at org.apache.fop.fo.flow.Block.(Block.java:72) at org.apache.fop.fo.flow.Block$Maker.make(Block.java:37) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:255) This means you have content outside a flow, which is illegal. This should not happen. Upgrade your DocBook XSL, be sure your DocBook docs validate, and complain on the DocBook list if this persists. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Stack Trace (was: newbie hyphenation...)
I'll see about getting newer Docbook XSL setups and customizing them for table widths. Funny thing is, I don't know that I even *have* any tables, at least not that I put in myself... Anyway, here's the stack trace: [ERROR] null org.apache.fop.apps.FOPException at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:74) at org.apache.fop.apps.Fop.main(Fop.java:19) - java.lang.NullPointerException at org.apache.fop.fo.PropertyManager.getTextDecoration(PropertyManager.java:328) at org.apache.fop.fo.FObjMixed.(FObjMixed.java:28) at org.apache.fop.fo.flow.Block.(Block.java:72) at org.apache.fop.fo.flow.Block$Maker.make(Block.java:37) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:255) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.fop.apps.Driver.render(Driver.java:457) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:69) at org.apache.fop.apps.Fop.main(Fop.java:19) - java.lang.NullPointerException at org.apache.fop.fo.PropertyManager.getTextDecoration(PropertyManager.java:328) at org.apache.fop.fo.FObjMixed.(FObjMixed.java:28) at org.apache.fop.fo.flow.Block.(Block.java:72) at org.apache.fop.fo.flow.Block$Maker.make(Block.java:37) at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:255) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.fop.apps.Driver.render(Driver.java:457) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:69) at org.apache.fop.apps.Fop.main(Fop.java:19) On Fri, 2003-02-21 at 13:35, J.Pietschmann wrote: Aaron Weber wrote: > [INFO] area contents overflows area This happens if, well, the contents overflows the allocated area. Usually caused by long words and word-like strings in table cells. > [ERROR] null Possibilities - Most often, a mandatory (for FOP) property was not set. - Footnotes on the last page which did not fit that page. - Unspecified problems with markers. Run FOP with the -d flag to get a stacktrace, and post the first few lines here. > Any tips? I'll try & get rid of the offending table-layout issues, > but... I don't know about adding table-column width attributes to every > table in the document. Upgrade to the latest DocBook XSL, which fixes many issues. Also, you can specify table column widths in DocBook, check the DocBook documentation. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: External links around graphics (no text) don't work.
Mike Trotman wrote: I am using FOP to produce PDF output. I need to produce a graphic which is a link to a web page. The external link feature works fine if the content is text - but if it is only a graphic then I can't find the link. What FOP version are you using? There has been some fixess in this area for the most recent version. If you use already 0.20.5rc2, please provide a small, self-contained example (including all graphics!) which demonstrates the problem. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TOC page number problem
Doray, Arnold wrote: Hi, I'm trying to create a TOC for a report, and I've run into a problem: The page number for the last entry in the TOC is the same as the previous one, IF the TOC reaches the bottom of the page. If the TOC extends over a few pages, this "repeat" occurs at the end of each page. All other page numbers in the TOC are OK. This problem does not occur if the TOC does not reach the end of the page. To create the TOC, I've used , and the TOC itself is in a . The TOC and the body of the report reside in different page-sequences. The actual page numbering in the report's body is OK. Could you post the FO here? There have been lots of complaints about this and related issues, however, they are hard to track down without a possiblity to reporduce them. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: More newbie hyphenation and option flag issues with docbook.xml --> fo -->pdf
Aaron Weber wrote: [INFO] area contents overflows area This happens if, well, the contents overflows the allocated area. Usually caused by long words and word-like strings in table cells. [ERROR] null Possibilities - Most often, a mandatory (for FOP) property was not set. - Footnotes on the last page which did not fit that page. - Unspecified problems with markers. Run FOP with the -d flag to get a stacktrace, and post the first few lines here. Any tips? I'll try & get rid of the offending table-layout issues, but... I don't know about adding table-column width attributes to every table in the document. Upgrade to the latest DocBook XSL, which fixes many issues. Also, you can specify table column widths in DocBook, check the DocBook documentation. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fo:basic-link from
Not the best way to enter a list, replying to your own first post, but I found a solution so I thought I'd post it. Instead of explicity using , I used so this: > > select="url"/> > blue > > becomes this: blue and it works as expected. Curious behavior and if someone wanted to explain the difference, that would be nifty but, obviously, not vital. Thanks again and sorry for this. Steven Berkowitz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
fo:basic-link from
I'm trying to have url's included inline in a paragraph. The relevant code is: --- blue --- Where the summary element in the XML is mixed content containing a link element. When I try to convert the XML document to PDF, I get the following error: "org.apache.fops.apps.FOPException: inline formatting objects cannot be directly under flow" Okay, if I surround the ... block with tags, the PDF is generated but the link is placed on its own line, which is obviously not a desired result. Any suggestions, work arounds, etc., would be most appreciated. TIA, Steven Berkowitz PS - if this is an XSL:FO issue and not a FOP issue, feel free to tell me RTFM, I've got a thick skin. Googling around, though didn't get me anywhere, so here we are. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Common formatting
sorry I've no idea :-( - Original Message - From: "Matthew Lancashire" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 21, 2003 1:47 PM Subject: RE: Common formatting > Is there anyway to point an XSL stylesheet to a CSS maybe? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP and Acrobat Reader: full screen
Aaron Weber wrote: For most monitors isn't that 4:3 width:height? and then the widescreen ones are 13:9? Yeah, most of the resolutions normal monitors support match that 4:3 aspect ratio but there are some exceptions... for example, 1280x1024 is 5:4. I don't know about those widescreen monitors, but at least with TV's the widescreen picture is 16:9, not 13:9... haven't used (seen?) one. -- -- Santtu "Japsu" Pajukanta -- [EMAIL PROTECTED] -- ICQ#: 115011651 "Any job worth doing with a laser is worth doing with many, many lasers", -Khrima in ADVENTURERS! the comic by Mark Shallow - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Common formatting
Is there anyway to point an XSL stylesheet to a CSS maybe? -Original Message- From: Myriam Delperier [mailto:[EMAIL PROTECTED] Sent: 21 Feb 2003 12:36 To: [EMAIL PROTECTED] Subject: Re: Common formatting you can have a stylesheet named attributes.xsl in this one you can have for examples 12pt blue then in your others stylesheets if you want for example a block to have thoses attributes you can make something like - Original Message - From: "Matthew Lancashire" <[EMAIL PROTECTED]> To: "Fop-User-Help (E-mail)" <[EMAIL PROTECTED]> Sent: Friday, February 21, 2003 1:30 PM Subject: Common formatting > What is the easiest methond of defineing what font/colour/sizes an element > has without re-coding the definitions in each xsl. > > e.g. > A text field of name has font arial, colour grey and size 12 point.. > It appears in 20 xml documents that are to be tranformed by fop to pdf. > I do not want to have to type the fo formatting commands into 20 xsl-fo > stylesheets because of the maintenance overhead. I want some standard class > of some sort > that I can apply to the xsl element that pics up the style from one place. > hence if the cont changes to courier I only need to change it once and not > in each of the 20 xsl style sheets. > > > > Matthew Lancashire > IT Project Manager > Initial Electronic Security Ltd > > Tel: +44 1282 473554 > Fax: +44 1254 267552 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
External links around graphics (no text) don't work.
Title: Message I am using FOP to produce PDF output. I need to produce a graphic which is a link to a web page. The external link feature works fine if the content is text - but if it is only a graphic then I can't find the link. If I have mixed text and graphics - then only the text seems to get the link. Anyone else encountered this or knows a fix? Mike Trotman Datalucid Limited
Re: Common formatting
Le Vendredi, 21 fév 2003, à 13:30 Europe/Zurich, Matthew Lancashire a écrit : What is the easiest methond of defineing what font/colour/sizes an element has without re-coding the definitions in each xsl. You could use "use-attribute-sets" to apply common attributes, along with "xsl:import" to include common attribute sets definitions in all your XSLT files. An alternative would be to use CSS-like "class names" attributes on your elements, and replace these with the actual attributes in a second XSLT transform. -- Bertrand Delacretaz (codeconsult.ch, jfor.org) XML, java, XSLT, Cocoon, FOP, mentoring/programming/teaching blogspace http://www.codeconsult.ch/bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Common formatting
I use an external XML file containing groups of elements that can be used to assign attributes to a FO element - given a unique key. I load this into a variable in XSLT and do lookups and assign attributes using a template 'with-param's as I process the output nodes. I just need to be able to tell for each output element what key it requires. If the content drives the style then I have a simple rule for deriving the key from the content. If not then I have to hard code the key into the particular XSLT. I actually do something a bit more complicated to determine scope / inheritance of the attributes and if they reformat the context element but as a general approach it is pretty flexible and nice and modular / re-useable and can also provide CSS stylesheets so I get HTML looking same as PDF. Mike Trotman -Original Message- From: Matthew Lancashire [mailto:[EMAIL PROTECTED] Sent: 21 February 2003 12:30 To: Fop-User-Help (E-mail) Subject: Common formatting What is the easiest methond of defineing what font/colour/sizes an element has without re-coding the definitions in each xsl. e.g. A text field of name has font arial, colour grey and size 12 point.. It appears in 20 xml documents that are to be tranformed by fop to pdf. I do not want to have to type the fo formatting commands into 20 xsl-fo stylesheets because of the maintenance overhead. I want some standard class of some sort that I can apply to the xsl element that pics up the style from one place. hence if the cont changes to courier I only need to change it once and not in each of the 20 xsl style sheets. Matthew Lancashire IT Project Manager Initial Electronic Security Ltd Tel: +44 1282 473554 Fax: +44 1254 267552 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Common formatting
you can have a stylesheet named attributes.xsl in this one you can have for examples 12pt blue then in your others stylesheets if you want for example a block to have thoses attributes you can make something like - Original Message - From: "Matthew Lancashire" <[EMAIL PROTECTED]> To: "Fop-User-Help (E-mail)" <[EMAIL PROTECTED]> Sent: Friday, February 21, 2003 1:30 PM Subject: Common formatting > What is the easiest methond of defineing what font/colour/sizes an element > has without re-coding the definitions in each xsl. > > e.g. > A text field of name has font arial, colour grey and size 12 point.. > It appears in 20 xml documents that are to be tranformed by fop to pdf. > I do not want to have to type the fo formatting commands into 20 xsl-fo > stylesheets because of the maintenance overhead. I want some standard class > of some sort > that I can apply to the xsl element that pics up the style from one place. > hence if the cont changes to courier I only need to change it once and not > in each of the 20 xsl style sheets. > > > > Matthew Lancashire > IT Project Manager > Initial Electronic Security Ltd > > Tel: +44 1282 473554 > Fax: +44 1254 267552 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Common formatting
What is the easiest methond of defineing what font/colour/sizes an element has without re-coding the definitions in each xsl. e.g. A text field of name has font arial, colour grey and size 12 point.. It appears in 20 xml documents that are to be tranformed by fop to pdf. I do not want to have to type the fo formatting commands into 20 xsl-fo stylesheets because of the maintenance overhead. I want some standard class of some sort that I can apply to the xsl element that pics up the style from one place. hence if the cont changes to courier I only need to change it once and not in each of the 20 xsl style sheets. Matthew Lancashire IT Project Manager Initial Electronic Security Ltd Tel: +44 1282 473554 Fax: +44 1254 267552 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Table's warning (was More newbie hyphenation and option flag issues ...)
>> [WARNING] table-layout=auto is not supported, using fixed! For this one, just use the attribute table-layout of fo:table tags : [WARNING] current implementation of tables requires a table-column for each column, indicating column-width To avoid this one, put a table-column tag for each column in your table after the fo:table tag : Cheers, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: page-number
you right it was just because I had a break-before="odd-page" - Original Message - From: "J.Pietschmann" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 21, 2003 12:40 AM Subject: Re: page-number > Myriam Delperier wrote: > > i've made an error when i wrote the message i've put it on the third. > > but it doesn't work. > > If i don't do anything my page has the number 3 > > and if I put the attribute the page still has the number 3 but i've got 2 > > white pages before : page1 anf page 2 > > That's odd. Can you post the FO demonstrating the effect, preferably > trimmed down to a handy file? > > J.Pietschmann > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: schema
thanks for your answer, so I think if i want to know if an attribute is supported for an element with my version of fop I've to have a look at the java code :-) - Original Message - From: "Oleg Tkachenko" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 20, 2003 6:46 PM Subject: Re: schema > Myriam Delperier wrote: > > Which schema should I use, to be sure that my fo files are well formatted > > for my version of fop? > Unfortunately xsl-fo syntax cannot be fully expressed in W3C XML Schema. There > is a plan to create schematron schema or XSL validator (as in XEP), but it's > not implemented yet. > -- > Oleg Tkachenko > Multiconn Technologies, Israel > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP and Acrobat Reader: full screen
For most monitors isn't that 4:3 width:height? and then the widescreen ones are 13:9? Aaron. On Thu, 2003-02-20 at 18:35, J.Pietschmann wrote: Hans Åkermark wrote: > I am trying to export PDF from XML via FOP to be shown as a presentation in > Acrobat Reader (we use one XSL for the print version and another for the > presentation). My difficulty is the presentation that I want to view in the > Full Screen mode (CTRL+L in Reader). The problem is to define the proper > page size to ensure that no black areas are shown outside all pages. You need to measure the height:width aspect of the window filled with the content and use the same for you page master. If your monitor has square pixels, you can measure the window with an usual ruler, in cm. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
TOC page number problem
Hi, I'm trying to create a TOC for a report, and I've run into a problem: The page number for the last entry in the TOC is the same as the previous one, IF the TOC reaches the bottom of the page. If the TOC extends over a few pages, this "repeat" occurs at the end of each page. All other page numbers in the TOC are OK. This problem does not occur if the TOC does not reach the end of the page. To create the TOC, I've used , and the TOC itself is in a . The TOC and the body of the report reside in different page-sequences. The actual page numbering in the report's body is OK. I'd greatly appreciate any pointers. Arnold Doray Fugro GEOS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: text disappear in svg
On 20.02.2003 07:12:04 Raimo Manninen wrote: > When I set strokeSVGText to false texts in svg images disappears. > This happens with some pdf viewers and sometimes when printed. > I tested this with fop-0.20.4 and fop-0.20.5rc2. > No problems when strokeSVGText is true but quality is then bad, as we > know. This is a known problem, and I brought it up myself some time back, on this list. It might be a Batik problem, not FOP. It has been suggested that you use stroked text, but for some of us, that's impractical if there are images with enough text in them - the PDF file size becomes significantly larger. I've had to insert timeseries graphs in the past, and found that the files became 10 times larger if the text were stroked. My "solution" was to use non-stroked text, and require my users to view PDFs with Acrobat Reader 5, which renders and prints the PDFs correctly, unlike Reader 4 and Ghostview. Acrobat 4 displays the PDF correctly, but fails to print the file on some printers; Ghostview neither displays correctly nor prints. Arnold Doray Fugro GEOS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: More newbie hyphenation and option flag issues with docbook.xml --> fo -->pdf
Excellent! A quick search and replace has gotten rid of the hyphenation problems, (language="en" --> language="en_GB") and deleting a couple more unsupported tags has gotten rid of all my errors! Now, I'm down to [WARNING] table-layout=auto is not supported, using fixed! [WARNING] current implementation of tables requires a table-column for each column, indicating column-width [WARNING] table-layout=auto is not supported, using fixed! [WARNING] current implementation of tables requires a table-column for each column, indicating column-width a couple of.. [INFO] area contents overflows area [INFO] area contents overflows area [INFO] area contents overflows area and of course at the end: [ERROR] null and failure. :( Really, I want to be able to automate the Docbook XML --> PDF transition, and avoid editing the autogenerated .fo files by hand as much as possible (autogenerated is almost always synonomous with "hard to edit by hand," and any sort of manual intervention means extra opportunity for confusion, error, and trouble when we need to regenerate after a change to the original). We've got the XML-->HTML transition down fine, fortunately... Any tips? I'll try & get rid of the offending table-layout issues, but... I don't know about adding table-column width attributes to every table in the document. Yours, Aaron. On Thu, 2003-02-20 at 19:44, J.Pietschmann wrote: > Aaron Weber wrote: > > [ERROR] Couldn't find hyphenation pattern en > Ah! Set the language to en_GB. > > J.Pietschmann > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: More newbie hyphenation and option flag issues with docbook.xml --> fo -->pdf
Aaron Weber wrote: [ERROR] Couldn't find hyphenation pattern en Ah! Set the language to en_GB. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Writing efficient XSL
Title: RE: Writing efficient XSL I can tell you from experience FOP processing on Unix is much slower than Windows/Intel and garbage collection is much less efficient. From my understanding, this is all mainly due to the differences in JVM and hotspot implementation. But 5 mintues for 20 pages still seems very high. Can you attach your FO (zipped)? I'll look at it. Are you processing images or SVG? -Original Message-From: Lee, Insoo [mailto:[EMAIL PROTECTED]Sent: Thursday, February 20, 2003 4:09 PMTo: '[EMAIL PROTECTED]'Subject: RE: Writing efficient XSL Matt, My max memory goes up to 256MB.. When I generate *.fo by merging XML with XSL : that takes 40 seconds.. (Using command like java -cp ~leeins/weblogic/3rd_party_jars_SUN/xalan-j_2_3_1_01.jar:/home/amchitmgr/build/jakarta-ant-1.5.1/lib/xml-apis.jar:/home/amchitmgr/build/jakarta-ant-1.5.1/lib/xercesImpl.jar org.apache.xalan.xslt.Process -IN rates.xml -XSL rates_pdf.xsl -OUT rates.fo) When I put this rates.fo thru Driver, it takes 5 minutes... generating 20 pages of pdf file... Where is the bottleneck? The machine is UNIX with 8 CPU and 10GB memroy... it seems that JDK1.3 and Xalan2.4.1 performs slightly better.., but not much.. Thanks -Original Message-From: Savino, Matt C [mailto:[EMAIL PROTECTED]Sent: Thursday, February 20, 2003 6:35 PMTo: [EMAIL PROTECTED]Subject: RE: Writing efficient XSL If you can "generate the FO object relatively quickly", then you should be already past the XSL stage and into the FO processing (Driver.run()). Unless I am interpreting this wrong. If so try writing your FO out to a file to see how long it takes. How many pages is your report when it finally finishes? Other people on this board are better experts when it comes to performance-tuning your FO. 20 minutes sounds excessive for about anything though. What is your heap size? -Matt -Original Message-From: Lee, Insoo [mailto:[EMAIL PROTECTED]Sent: Thursday, February 20, 2003 3:17 PMTo: '[EMAIL PROTECTED]'Subject: RE: Writing efficient XSL Hi, I have something like this Prior Day Rates for 19 Feb 2003 1 Feb 2003 19 Feb 2003 leeins 1%20Feb%202003 19%20Feb%202003 Thu%2023%20Jan%202003%203:05:34%20PM%20ET Thu 23 Jan 2003 3:05:34 PM ET 0 ALL GF6 ILA Treasury Obligations Inst 0.2156000 1.02 1.0449400 1.0642200 NA 0.99 1.26 1. 1 Feb 2003 GBP 20 Feb 2003 My Fund 38XX2B765 and 1,000 or so FUND_ROW Thanks! -Original Message-From: Calero, Roberto [mailto:[EMAIL PROTECTED]Sent: Thursday, February 20, 2003 5:35 PMTo: '[EMAIL PROTECTED]'Subject: RE: Writing efficient XSLImportance: High How about the data file? -Original Message- From: Lee, Insoo [mailto:[EMAIL PROTECTED]] Sent: Friday, February 21, 2003 4:01 AM To: [EMAIL PROTECTED] Subject: Writing efficient XSL Could you please take a quick look at my XSL and see where I can improve it?... I know it's a very vague request, but I would appreciate any comments or advice... I can generate FO object relative quickly, but when generating 20 pages, it takes about 5 minutes.. (Driver.run()) and I think my XSL is not efficiently written.. I basically have one big table because I need to repeat column headings.. people say I need to make smaller tables, but how would I do that without counting lines to be on one page... (without relying on page header) Thanks xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"> Helvetica bold 8pt left Helvetica 8pt Helvetica 8pt right Helvetica bold 8pt http://www.w3.org/1999/XSL/Format"> page-width="29.7cm" page-height="21.0cm" margin-top="0.5cm" margin-bottom="0.5cm" margin-left="1.5cm" margin-right="1.5cm"> margin-top="0.5cm" margin-bottom="1.5cm"/>
RE: Writing efficient XSL
Hello, Is there quick sample that I can take a look? So, I would have to 1) count the # of lines per page and dump out to a table everytime page changes 2) rely on region-before for column headings... - Only thing is the column needs to be dynamic depending on the contents... -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: Thursday, February 20, 2003 6:47 PM To: [EMAIL PROTECTED] Subject: Re: Writing efficient XSL Lee, Insoo wrote: > I basically have one big table because I need to repeat column > headings.. Have you checked whether you can put the repeating header into the static-content of the region-before? > I can generate FO object relative quickly, but when generating 20 pages, it > takes about 5 minutes.. (Driver.run()) Depending on your environment, this is not necessarily a bad time. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Writing efficient XSL
Title: RE: Writing efficient XSL Matt, My max memory goes up to 256MB.. When I generate *.fo by merging XML with XSL : that takes 40 seconds.. (Using command like java -cp ~leeins/weblogic/3rd_party_jars_SUN/xalan-j_2_3_1_01.jar:/home/amchitmgr/build/jakarta-ant-1.5.1/lib/xml-apis.jar:/home/amchitmgr/build/jakarta-ant-1.5.1/lib/xercesImpl.jar org.apache.xalan.xslt.Process -IN rates.xml -XSL rates_pdf.xsl -OUT rates.fo) When I put this rates.fo thru Driver, it takes 5 minutes... generating 20 pages of pdf file... Where is the bottleneck? The machine is UNIX with 8 CPU and 10GB memroy... it seems that JDK1.3 and Xalan2.4.1 performs slightly better.., but not much.. Thanks -Original Message-From: Savino, Matt C [mailto:[EMAIL PROTECTED]Sent: Thursday, February 20, 2003 6:35 PMTo: [EMAIL PROTECTED]Subject: RE: Writing efficient XSL If you can "generate the FO object relatively quickly", then you should be already past the XSL stage and into the FO processing (Driver.run()). Unless I am interpreting this wrong. If so try writing your FO out to a file to see how long it takes. How many pages is your report when it finally finishes? Other people on this board are better experts when it comes to performance-tuning your FO. 20 minutes sounds excessive for about anything though. What is your heap size? -Matt -Original Message-From: Lee, Insoo [mailto:[EMAIL PROTECTED]Sent: Thursday, February 20, 2003 3:17 PMTo: '[EMAIL PROTECTED]'Subject: RE: Writing efficient XSL Hi, I have something like this Prior Day Rates for 19 Feb 2003 1 Feb 2003 19 Feb 2003 leeins 1%20Feb%202003 19%20Feb%202003 Thu%2023%20Jan%202003%203:05:34%20PM%20ET Thu 23 Jan 2003 3:05:34 PM ET 0 ALL GF6 ILA Treasury Obligations Inst 0.2156000 1.02 1.0449400 1.0642200 NA 0.99 1.26 1. 1 Feb 2003 GBP 20 Feb 2003 My Fund 38XX2B765 and 1,000 or so FUND_ROW Thanks! -Original Message-From: Calero, Roberto [mailto:[EMAIL PROTECTED]Sent: Thursday, February 20, 2003 5:35 PMTo: '[EMAIL PROTECTED]'Subject: RE: Writing efficient XSLImportance: High How about the data file? -Original Message- From: Lee, Insoo [mailto:[EMAIL PROTECTED]] Sent: Friday, February 21, 2003 4:01 AM To: [EMAIL PROTECTED] Subject: Writing efficient XSL Could you please take a quick look at my XSL and see where I can improve it?... I know it's a very vague request, but I would appreciate any comments or advice... I can generate FO object relative quickly, but when generating 20 pages, it takes about 5 minutes.. (Driver.run()) and I think my XSL is not efficiently written.. I basically have one big table because I need to repeat column headings.. people say I need to make smaller tables, but how would I do that without counting lines to be on one page... (without relying on page header) Thanks xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format"> Helvetica bold 8pt left Helvetica 8pt Helvetica 8pt right Helvetica bold 8pt http://www.w3.org/1999/XSL/Format"> page-width="29.7cm" page-height="21.0cm" margin-top="0.5cm" margin-bottom="0.5cm" margin-left="1.5cm" margin-right="1.5cm"> margin-top="0.5cm" margin-bottom="1.5cm"/> extent="0cm"/> extent="0.5cm"/> table-layout="fixed"> border-collapse="collapse" number-columns-spanned="11"> font-family="Helvetica" space-after="0pt"
