css2xslfo-support Mailing List for CSSToXSLFO (Page 2)
Brought to you by:
wdonne
You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
(9) |
Apr
(6) |
May
(24) |
Jun
(14) |
Jul
|
Aug
(4) |
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
|
Feb
(4) |
Mar
(17) |
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(2) |
2007 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(11) |
Jul
(2) |
Aug
(6) |
Sep
|
Oct
(1) |
Nov
(7) |
Dec
(5) |
2008 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(12) |
Jul
(2) |
Aug
(4) |
Sep
(5) |
Oct
(21) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(16) |
Oct
|
Nov
|
Dec
|
From: Erik T. <er...@so...> - 2009-09-17 13:02:51
|
Hi Werner, Thank you for your explanation, I can probably fake full image link coverage by fooling around with large font sizes. Kind regards, Erik. Werner Donn wrote: > Hi Erik, > > Just now I tested it with both FOP and XEP4 and the results are the same. > There is a link around the image, but only the bottom part of it is > sensitive. Hover the image and you will see only the area equal to the > line height at the bottom is sensitive. > > I think this stems from the fact that the "img" element is an inline > element. > The display type of "img" is "graphic", which is treated as inline. > This is > consistent with the XSL-FO element "external-graphic" being an inline > element. > > The area of the image that is in the line is covered by the link. Put > some text > before are after it to see it. I'm afraid this is a difference in > behaviour > between CSS and XSL-FO. In fact CSS2 doesn't specify anything about > images. > > Best regards, > > Werner. > > On 17 Sep 2009, at 11:58, Erik Terpstra wrote: > >> Hi, >> >> It looks like it is not possible to put a link around an image? >> Like: <a href="..."><img src="..."/></a> >> Is there some way to get this to work? Or am I doing something wrong? >> I am using Apache FOP as the back-end. >> >> TIA, >> >> Erik. >> >> ------------------------------------------------------------------------------ >> >> Come build with us! The BlackBerry® Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and >> stay >> ahead of the curve. Join us from November 9-12, 2009. Register >> now! >> http://p.sf.net/sfu/devconf >> _______________________________________________ >> css2xslfo-support mailing list >> css...@li... >> https://lists.sourceforge.net/lists/listinfo/css2xslfo-support > > -- > http://www.pincette.biz/ > Handling your documents with care, wherever you are. > |
From: Erik T. <er...@so...> - 2009-09-17 10:39:13
|
Hi, It looks like it is not possible to put a link around an image? Like: <a href="..."><img src="..."/></a> Is there some way to get this to work? Or am I doing something wrong? I am using Apache FOP as the back-end. TIA, Erik. |
From: Werner D. <wer...@re...> - 2009-06-10 10:49:30
|
Hi, This means the W3C server was not available at that time. The HTTP response code 503 stands for "Service Unavailable". However, CSSToXSLFO has a catalog on board for XHTML, so it should have to go to W3C in order to obtain the DTD entities. Due to an error this catalog was not present in version 1.5.2. Since version 1.6 this has been fixed. Which version do you use? Best regards, Werner. On 10 Jun 2009, at 08:05, parames waran wrote: > > Hi , > I got the following error while convert the xhtml to xslfo. > > be.re.css.CSSToXSLFOException: Server returned HTTP response code: > 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:138) > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:71) > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:62) > > > kindly provide the solution to solve this issue. > > Regards, > Parames. > > Bring your gang together. Do your thing. Find your favourite Yahoo! > Group > .------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects_______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support -- Werner Donné -- Re http://www.pincette.biz Engelbeekstraat 8 http://www.re.be BE-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: parames w. <par...@ya...> - 2009-06-10 06:06:08
|
Hi , I got the following error while convert the xhtml to xslfo. be.re.css.CSSToXSLFOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:138) at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:71) at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:62) kindly provide the solution to solve this issue. Regards, Parames. Explore and discover exciting holidays and getaways with Yahoo! India Travel http://in.travel.yahoo.com/ |
From: Werner D. <wer...@re...> - 2008-10-29 12:38:14
|
Hi, If print.css is in the right location then there may be a problem with the access rights. How did you include it? From the message I would say that either print.css is next to the document or next to another style sheet that includes it. Best regards, Werner. On 29 Oct 2008, at 12:48, parames waran wrote: > Hi werner I am getting the exception "be.re.css.CSSToXSLFOException: > print.css can't be opened." > > But the print.css file is in right location.What I need to done to > fix this issue .and what is the root cause of this issue . > > Please help me to fix this issue. > > > be.re.css.CSSToXSLFOException: print.css can't be opened. > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:138) > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:71) > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:62) > at > com > .gale.presentation.util.JSTLHelper.convertCSSToXSLFO(JSTLHelper.java: > 3147) > at > com > .gale > .presentation > .http.filter.XHTMLToPDFFilter.doFilter(XHTMLToPDFFilter.java:58) > at > org > .apache > .catalina > .core > .ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java: > 215) > at > org > .apache > .catalina > .core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at > org > .apache > .catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java: > 210) > at > org > .apache > .catalina.core.StandardContextValve.invoke(StandardContextValve.java: > 174) > at > org > .apache > .catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at > org > .apache > .catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) > at > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java: > 542) > at > org > .apache > .catalina.core.StandardEngineValve.invoke(StandardEngineValve.java: > 108) > at > org > .apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java: > 151) > at > org > .apache.coyote.http11.Http11Processor.process(Http11Processor.java: > 870) > at org.apache.coyote.http11.Http11BaseProtocol > $Http11ConnectionHandler.processConnection(Http11BaseProtocol.java: > 665) > at > org > .apache > .tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java: > 528) > at > org > .apache > .tomcat > .util > .net > .LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) > at org.apache.tomcat.util.threads.ThreadPool > $ControlRunnable.run(ThreadPool.java:685) > at java.lang.Thread.run(Thread.java:619) > > > > Regards. > Parameswaran.M > > > > Connect with friends all over the world. Get Yahoo! India > Messenger at http://in.messenger.yahoo.com/?wm=n/ -- Werner Donné -- Re http://www.pincette.biz Engelbeekstraat 8 http://www.re.be BE-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: parames w. <par...@ya...> - 2008-10-29 11:48:53
|
Hi werner I am getting the exception "be.re.css.CSSToXSLFOException: print.css can't be opened." But the print.css file is in right location.What I need to done to fix this issue .and what is the root cause of this issue . Please help me to fix this issue. be.re.css.CSSToXSLFOException: print.css can't be opened. at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:138) at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:71) at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:62) at com.gale.presentation.util.JSTLHelper.convertCSSToXSLFO(JSTLHelper.java:3147) at com.gale.presentation.http.filter.XHTMLToPDFFilter.doFilter(XHTMLToPDFFilter.java:58) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:542) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Thread.java:619) Regards. Parameswaran.M Connect with friends all over the world. Get Yahoo! India Messenger at http://in.messenger.yahoo.com/?wm=n/ |
From: Werner D. <wer...@re...> - 2008-10-28 15:59:30
|
Hi Param, This was indeed an issue you encountered a while ago. The fix means that the catalog and the XHTML DTD files are again included in the package and used automatically when you use the XHTML namespace. I think it is still better to generate a document type declaration, but you no longer have to do something to resolve the XHTML public identifier to an entity. Best regards, Werner. On 28 Oct 2008, at 07:21, parames waran wrote: > > > Hi werner I like to know the meaning of the following bug fixed in > new release of css2xslfo. > > 1984171: The XHTML catalog is no longer included--so i do not need > to include the following line in my jspx. > > <jsp:output omit-xml-declaration="true" doctype-root-element="html" > doctype-public="-//W3C//DTD XHTML 1.1//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd > " /> > > please clarify this doubt .. > > > Regards. > Parameswaran.M > > > > Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/ -- Werner Donné -- Re http://www.pincette.biz Engelbeekstraat 8 http://www.re.be BE-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: parames w. <par...@ya...> - 2008-10-28 06:21:53
|
Hi werner I like to know the meaning of the following bug fixed in new release of css2xslfo. 1984171: The XHTML catalog is no longer included--so i do not need to include the following line in my jspx. <jsp:output omit-xml-declaration="true" doctype-root-element="html" doctype-public="-//W3C//DTD XHTML 1.1//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" /> please clarify this doubt .. Regards. Parameswaran.M Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/ |
From: <aro...@cl...> - 2008-10-17 14:25:43
|
Thank you Werner, That's a very nice offer. Unfortunately I spoke with management and they'd prefer I don't get into this right now and want me to move in a different direction. I'm sorry. Maybe later I'll write back and you can help us debug the issue. Again, thanks for your generosity and I'm sorry I can't send you the sample files at this time. -- Aaron Werner Donné <wer...@re...> wrote on 17-10-2008 03:20:34 AM: > Hi Aaron, > > That is probably a bug. Can you send the original document with the > style sheets in a ZIP to su...@re...? You can also add a PDF from > one of the other tools, so I can see what should be produced. > > Best regards, > > Werner. > > On 16 Oct 2008, at 18:54, aro...@cl... wrote: > > > > > Wow! thanks Werner, Brad, and Sergey. You are all very responsive. > > > > I'm getting a little further now after adding: > > > > visits > > { > > region: body; > > } > > > > unfortunately, I get a type of null pointer exception. Do I need to > > define some other specifier since this is a pure XML document > > without the XHTML trimmings? > > > > Thanks, > > -- Aaron > > > > Here's the stack trace: > > > > null > > be.re.css.CSSToXSLFOException > > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:138) > > at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:267) > > Caused by: > > java.util.EmptyStackException > > at > > com.sun.org.apache.xml.internal.utils.IntStack.peek(IntStack.java:125) > > at > > com > > .sun > > .org > > .apache > > .xml.internal.dtm.ref.sax2dtm.SAX2DTM2.endElement(SAX2DTM2.java:2239) > > at > > com > > .sun > > .org.apache.xalan.internal.xsltc.dom.SAXImpl.endElement(SAXImpl.java: > > 936) > > at > > com > > .sun > > .org > > .apache > > .xalan > > .internal > > .xsltc > > .trax.TransformerHandlerImpl.endElement(TransformerHandlerImpl.java: > > 273) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at be.re.css.PageSetupFilter.endElement(PageSetupFilter.java: > > 315) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > be.re.css.BlockContainerFilter.endElement(BlockContainerFilter.java: > > 72) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at be.re.css.FootnoteFilter.endElement(FootnoteFilter.java:68) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at be.re.css.LinkFilter.endElement(LinkFilter.java:51) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > be > > .re.css.WidthAndMarginsFilter.endElement(WidthAndMarginsFilter.java: > > 159) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at be.re.css.CenterFilter.endElement(CenterFilter.java:94) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > be.re.css.NormalizeTableFilter.endElement(NormalizeTableFilter.java: > > 190) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > be > > .re > > .css > > .XHTMLAttributeTranslationFilter > > .endElement(XHTMLAttributeTranslationFilter.java:272) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at be.re.css.ForeignFilter.endElement(ForeignFilter.java:48) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > be > > .re.css.DisplayNonePropagator.endElement(DisplayNonePropagator.java: > > 45) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at be.re.css.WrapperFilter.endElement(WrapperFilter.java:45) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at be.re.css.FOMarkerFilter.endElement(FOMarkerFilter.java:98) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at be.re.css.ProjectorFilter.endElement(ProjectorFilter.java: > > 439) > > at > > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > > at > > com > > .sun > > .org > > .apache > > .xerces > > .internal > > .parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633) > > at > > com > > .sun > > .org > > .apache > > .xerces > > .internal > > .impl > > .XMLNSDocumentScannerImpl > > .scanEndElement(XMLNSDocumentScannerImpl.java:719) > > at > > com > > .sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl > > $ > > FragmentContentDispatcher > > .dispatch(XMLDocumentFragmentScannerImpl.java:1685) > > at > > com > > .sun > > .org > > .apache > > .xerces > > .internal > > .impl > > .XMLDocumentFragmentScannerImpl > > .scanDocument(XMLDocumentFragmentScannerImpl.java:368) > > at > > com > > .sun > > .org > > .apache > > .xerces > > .internal.parsers.XML11Configuration.parse(XML11Configuration.java: > > 834) > > at > > com > > .sun > > .org > > .apache > > .xerces > > .internal.parsers.XML11Configuration.parse(XML11Configuration.java: > > 764) > > at > > com > > .sun > > .org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java: > > 148) > > at > > com > > .sun > > .org > > .apache > > .xerces > > .internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) > > at > > be > > .re > > .xml > > .sax.ProtectEventHandlerFilter.parse(ProtectEventHandlerFilter.java: > > 56) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at be.re.xml.sax.FilterOfFilters.parse(FilterOfFilters.java: > > 165) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at > > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > > at be.re.xml.sax.FilterOfFilters.parse(FilterOfFilters.java: > > 165) > > at be.re.css.CSSToXSLFOFilter.parse(CSSToXSLFOFilter.java:324) > > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:133) > > at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:267) > > > > Werner Donné <wer...@re...> wrote on 16-10-2008 03:39:48 AM: > > > > > Hi Aaron, > > > > > > If you add the following rule for the "visits" element it should > > work: > > > > > > visits > > > { > > > region: body; > > > } > > > > > > The notion of having regions stems from the fact that an XSL-FO > > document > > > is made up of regions and page sequences. For each new page sequence > > > I have to regenerate stuff starting from the element that > > represents the > > > body region. > > > > > > I understand you are annoyed by that. It is, however, not so easy to > > > choose a default body region. At first sight the document element > > would > > > be a good candidate, but some XML languages define some > > preliminary meta > > > information. As a consequence, a lower element may have to be the > > body > > > region. I could scan the CSS files to check if some element > > already has > > > been assigned as the body region and use the document element if > > there > > > isn't one. However, it is not certain the rule would apply to any > > > element > > > at all and moreover, the "style" attribute could have been used > > inside > > > the > > > document to assign the body region. In order to solve this I would > > have > > > to examine the complete document first. This is not possible, > > because > > > the > > > tool works as a streaming filter. That is to reduce memory > > consumption > > > for very large documents. > > > > > > Best regards, > > > > > > Werner. > > > > > > On 15 Oct 2008, at 20:48, aro...@cl... wrote: > > > > > > > > > > > Hi, > > > > > > > > I'm just getting started trying to use css2xslfo. At the moment, I > > > > just want to see it produce an FO document but I'm getting a file > > > > with zero bytes. > > > > > > > > I tried the following: > > > > > > > > java -Dbe.re.stack -jar css2xslfo1_6.jar visitDump.xml -fo > > > > visitDump.fo > > > > > > > > I don't get any warnings of any sort. It chugs away but then > > creates > > > > an empty "visitDump.fo" file. > > > > > > > > The xml source file is not xhtml, just pure xml. It looks > > something > > > > like so: > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > <?xml-stylesheet href="visitDump.css" type="text/css" > > media="all"?> > > > > <visits> > > > > <protocol> > > > > <protocol_descriptor>Hello</protocol_descriptor> > > > > ... > > > > </protocol> > > > > ... > > > > </visits> > > > > > > > > Ultimately I'd like to connect it to FOP to produce a PDF but > > right > > > > now, I'm not able to get it to do the FO part yet. Any ideas on > > what > > > > I might be missing? > > > > > > > > Thanks in advance, > > > > -- > > > > Aaron > > > > > > ------------------------------------------------------------------------- > > > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > > > challenge > > > > Build the coolest Linux based applications with Moblin SDK & win > > > > great prizes > > > > Grand prize is a trip for two to an Open Source event anywhere in > > > > the world > > > > http://moblin-contest.org/redirect.php? > > > banner_id=100&url=/_______________________________________________ > > > > css2xslfo-support mailing list > > > > css...@li... > > > > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support > > > > > > -- > > > Werner Donné -- Re http://www. > > > pincette.biz > > > Engelbeekstraat 8 > > > http://www.re.be > > > BE-3300 Tienen > > > tel: (+32) 486 425803 e-mail: wer...@re... > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > challenge > > Build the coolest Linux based applications with Moblin SDK & win > > great prizes > > Grand prize is a trip for two to an Open Source event anywhere in > > the world > > http://moblin-contest.org/redirect.php? > banner_id=100&url=/_______________________________________________ > > css2xslfo-support mailing list > > css...@li... > > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support > > -- > Werner Donné -- Re http://www. > pincette.biz > Engelbeekstraat 8 > http://www.re.be > BE-3300 Tienen > tel: (+32) 486 425803 e-mail: wer...@re... > > > > > |
From: Werner D. <wer...@re...> - 2008-10-17 07:20:44
|
Hi Aaron, That is probably a bug. Can you send the original document with the style sheets in a ZIP to su...@re...? You can also add a PDF from one of the other tools, so I can see what should be produced. Best regards, Werner. On 16 Oct 2008, at 18:54, aro...@cl... wrote: > > Wow! thanks Werner, Brad, and Sergey. You are all very responsive. > > I'm getting a little further now after adding: > > visits > { > region: body; > } > > unfortunately, I get a type of null pointer exception. Do I need to > define some other specifier since this is a pure XML document > without the XHTML trimmings? > > Thanks, > -- Aaron > > Here's the stack trace: > > null > be.re.css.CSSToXSLFOException > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:138) > at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:267) > Caused by: > java.util.EmptyStackException > at > com.sun.org.apache.xml.internal.utils.IntStack.peek(IntStack.java:125) > at > com > .sun > .org > .apache > .xml.internal.dtm.ref.sax2dtm.SAX2DTM2.endElement(SAX2DTM2.java:2239) > at > com > .sun > .org.apache.xalan.internal.xsltc.dom.SAXImpl.endElement(SAXImpl.java: > 936) > at > com > .sun > .org > .apache > .xalan > .internal > .xsltc > .trax.TransformerHandlerImpl.endElement(TransformerHandlerImpl.java: > 273) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at be.re.css.PageSetupFilter.endElement(PageSetupFilter.java: > 315) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > be.re.css.BlockContainerFilter.endElement(BlockContainerFilter.java: > 72) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at be.re.css.FootnoteFilter.endElement(FootnoteFilter.java:68) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at be.re.css.LinkFilter.endElement(LinkFilter.java:51) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > be > .re.css.WidthAndMarginsFilter.endElement(WidthAndMarginsFilter.java: > 159) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at be.re.css.CenterFilter.endElement(CenterFilter.java:94) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > be.re.css.NormalizeTableFilter.endElement(NormalizeTableFilter.java: > 190) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > be > .re > .css > .XHTMLAttributeTranslationFilter > .endElement(XHTMLAttributeTranslationFilter.java:272) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at be.re.css.ForeignFilter.endElement(ForeignFilter.java:48) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > be > .re.css.DisplayNonePropagator.endElement(DisplayNonePropagator.java: > 45) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at be.re.css.WrapperFilter.endElement(WrapperFilter.java:45) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at be.re.css.FOMarkerFilter.endElement(FOMarkerFilter.java:98) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at be.re.css.ProjectorFilter.endElement(ProjectorFilter.java: > 439) > at > org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) > at > com > .sun > .org > .apache > .xerces > .internal > .parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633) > at > com > .sun > .org > .apache > .xerces > .internal > .impl > .XMLNSDocumentScannerImpl > .scanEndElement(XMLNSDocumentScannerImpl.java:719) > at > com > .sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl > $ > FragmentContentDispatcher > .dispatch(XMLDocumentFragmentScannerImpl.java:1685) > at > com > .sun > .org > .apache > .xerces > .internal > .impl > .XMLDocumentFragmentScannerImpl > .scanDocument(XMLDocumentFragmentScannerImpl.java:368) > at > com > .sun > .org > .apache > .xerces > .internal.parsers.XML11Configuration.parse(XML11Configuration.java: > 834) > at > com > .sun > .org > .apache > .xerces > .internal.parsers.XML11Configuration.parse(XML11Configuration.java: > 764) > at > com > .sun > .org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java: > 148) > at > com > .sun > .org > .apache > .xerces > .internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) > at > be > .re > .xml > .sax.ProtectEventHandlerFilter.parse(ProtectEventHandlerFilter.java: > 56) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at be.re.xml.sax.FilterOfFilters.parse(FilterOfFilters.java: > 165) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at > org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) > at be.re.xml.sax.FilterOfFilters.parse(FilterOfFilters.java: > 165) > at be.re.css.CSSToXSLFOFilter.parse(CSSToXSLFOFilter.java:324) > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:133) > at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:267) > > Werner Donné <wer...@re...> wrote on 16-10-2008 03:39:48 AM: > > > Hi Aaron, > > > > If you add the following rule for the "visits" element it should > work: > > > > visits > > { > > region: body; > > } > > > > The notion of having regions stems from the fact that an XSL-FO > document > > is made up of regions and page sequences. For each new page sequence > > I have to regenerate stuff starting from the element that > represents the > > body region. > > > > I understand you are annoyed by that. It is, however, not so easy to > > choose a default body region. At first sight the document element > would > > be a good candidate, but some XML languages define some > preliminary meta > > information. As a consequence, a lower element may have to be the > body > > region. I could scan the CSS files to check if some element > already has > > been assigned as the body region and use the document element if > there > > isn't one. However, it is not certain the rule would apply to any > > element > > at all and moreover, the "style" attribute could have been used > inside > > the > > document to assign the body region. In order to solve this I would > have > > to examine the complete document first. This is not possible, > because > > the > > tool works as a streaming filter. That is to reduce memory > consumption > > for very large documents. > > > > Best regards, > > > > Werner. > > > > On 15 Oct 2008, at 20:48, aro...@cl... wrote: > > > > > > > > Hi, > > > > > > I'm just getting started trying to use css2xslfo. At the moment, I > > > just want to see it produce an FO document but I'm getting a file > > > with zero bytes. > > > > > > I tried the following: > > > > > > java -Dbe.re.stack -jar css2xslfo1_6.jar visitDump.xml -fo > > > visitDump.fo > > > > > > I don't get any warnings of any sort. It chugs away but then > creates > > > an empty "visitDump.fo" file. > > > > > > The xml source file is not xhtml, just pure xml. It looks > something > > > like so: > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > <?xml-stylesheet href="visitDump.css" type="text/css" > media="all"?> > > > <visits> > > > <protocol> > > > <protocol_descriptor>Hello</protocol_descriptor> > > > ... > > > </protocol> > > > ... > > > </visits> > > > > > > Ultimately I'd like to connect it to FOP to produce a PDF but > right > > > now, I'm not able to get it to do the FO part yet. Any ideas on > what > > > I might be missing? > > > > > > Thanks in advance, > > > -- > > > Aaron > > > > ------------------------------------------------------------------------- > > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > > challenge > > > Build the coolest Linux based applications with Moblin SDK & win > > > great prizes > > > Grand prize is a trip for two to an Open Source event anywhere in > > > the world > > > http://moblin-contest.org/redirect.php? > > banner_id=100&url=/_______________________________________________ > > > css2xslfo-support mailing list > > > css...@li... > > > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support > > > > -- > > Werner Donné -- Re http://www. > > pincette.biz > > Engelbeekstraat 8 > > http://www.re.be > > BE-3300 Tienen > > tel: (+32) 486 425803 e-mail: wer...@re... > > > > > > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support -- Werner Donné -- Re http://www.pincette.biz Engelbeekstraat 8 http://www.re.be BE-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: Brad C. <bk...@mu...> - 2008-10-16 20:03:39
|
aro...@cl... wrote: > > Hi Brad, > > That's good to know :-) > > Question, with the multi-meg files, are there any carriage returns? > That *might* be a clue. We're on linux, so technically there aren't any CR characters in the file. There are NL characters though. I doubt that makes any difference, werner says it's a streaming processor, so it's probably using SAX events. Oxygen and other editors want to break things into lines so you can read the file, but SAX doesn't care. I'm sorry I can't be more helpful, I'm not a java programmer, just an end user. I wouldn't be able to try the "no NL" file experiment before next week.. I'm moving between houses right now, closing tomorrow! -- Brad Clements, bk...@mu... (315)268-1000 http://www.murkworks.com AOL-IM: BKClements |
From: <aro...@cl...> - 2008-10-16 19:10:52
|
Oops! Sorry, I meant to say the 60kb file in the paragraph below. The 16kb one without carriage returns was fine in both Oxygen and TextWrangler. -- Aaron aro...@cl... wrote on 16-10-2008 03:07:21 PM: > > Hi Brad, > > That's good to know :-) > > Question, with the multi-meg files, are there any carriage returns? > That *might* be a clue. > > The 16kb file xml source file I have does not have any carriage > returns. I noticed when I opened it in "Oxygen" it gave a message > saying that the length was too long and that it had to reformat the > file and add hard returns before displaying it. Also, with > "TextWranger", I couldn't edit the file past a certain point without > adding "soft returns" to the document. > > Brad, would it be relatively easy to remove all carriage returns and > try running a multi-meg file through its paces? > > Cheers, > -- Aaron > > Brad Clements <bk...@mu...> wrote on 16-10-2008 02:41:29 PM: > > > All I can add to this is that we routinely generate PDFs that are 3 or 4 > > megs of output, whose source file is quite a bit larger than 16kb. > > > > Maybe there's some kind of rendering overflow that's not related to the > > size of the input file, but rather how the contents are being rendered. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support |
From: <aro...@cl...> - 2008-10-16 19:07:30
|
Hi Brad, That's good to know :-) Question, with the multi-meg files, are there any carriage returns? That *might* be a clue. The 16kb file xml source file I have does not have any carriage returns. I noticed when I opened it in "Oxygen" it gave a message saying that the length was too long and that it had to reformat the file and add hard returns before displaying it. Also, with "TextWranger", I couldn't edit the file past a certain point without adding "soft returns" to the document. Brad, would it be relatively easy to remove all carriage returns and try running a multi-meg file through its paces? Cheers, -- Aaron Brad Clements <bk...@mu...> wrote on 16-10-2008 02:41:29 PM: > All I can add to this is that we routinely generate PDFs that are 3 or 4 > megs of output, whose source file is quite a bit larger than 16kb. > > Maybe there's some kind of rendering overflow that's not related to the > size of the input file, but rather how the contents are being rendered. > |
From: Brad C. <bk...@mu...> - 2008-10-16 18:41:40
|
All I can add to this is that we routinely generate PDFs that are 3 or 4 megs of output, whose source file is quite a bit larger than 16kb. Maybe there's some kind of rendering overflow that's not related to the size of the input file, but rather how the contents are being rendered. aro...@cl... wrote: > > Hi Everyone, > > After some more experimentation it seems that maybe the original file > I sent was "too large to handle." Does that seem possible? The source > xml file is 60kb. Again, it worked fine in PrinceXML and Flying Saucer > without errors or warnings. As far as I can discern, it seems like a > good xml source document. It contained 8 "visitVersions" so I just ran > a report with only a single visitVersion and tried again (a 16kb file > this time). This worked, in that it produced both FO and ultimately > PDF when used with Apache FOP. > > The resulting output is not as pretty as what I saw with Flying Saucer > and PrinceXML because various styles were not showing properly. > Bolding for example was absent. Also, even though "landscape" was > specified it was coming out in portrait mode. These style and > orientation problems might not be an issue with your FO producing > app... they might be more of a problem with Apache FOP but I don't > really know. > > One last bit, either I read it wrong or the documentation needs to be > updated. I tried the following command but failed: > > java -cp "lib/" -jar lib/css2fopnew1_6.jar visitReport.xml > paper-size=letter -pdf visitReport.pdf > > I needed to issue the following command to get it to work: > > java -cp "lib/" -jar lib/css2fopnew1_6.jar visitReport.xml > paper-size=letter -fop -pdf visitReport.pdf > > The key piece missing, the "-fop" argument. When I read the docs, it > seemed that "-pdf" was something that didn't need to be escaped into > an FOP specific argument... But maybe that was just me. The one line > examples don't actually show PDF creation so I probably just > interpreted the documentation wrong. hmm, I don't generate .fo files, I just create .pdf files directly and I do not use the -fop option. I am still using css2fopnew1_5_2.jar -- Brad Clements, bk...@mu... (315)268-1000 http://www.murkworks.com AOL-IM: BKClements |
From: <aro...@cl...> - 2008-10-16 18:01:33
|
Hi Everyone, After some more experimentation it seems that maybe the original file I sent was "too large to handle." Does that seem possible? The source xml file is 60kb. Again, it worked fine in PrinceXML and Flying Saucer without errors or warnings. As far as I can discern, it seems like a good xml source document. It contained 8 "visitVersions" so I just ran a report with only a single visitVersion and tried again (a 16kb file this time). This worked, in that it produced both FO and ultimately PDF when used with Apache FOP. The resulting output is not as pretty as what I saw with Flying Saucer and PrinceXML because various styles were not showing properly. Bolding for example was absent. Also, even though "landscape" was specified it was coming out in portrait mode. These style and orientation problems might not be an issue with your FO producing app... they might be more of a problem with Apache FOP but I don't really know. One last bit, either I read it wrong or the documentation needs to be updated. I tried the following command but failed: java -cp "lib/" -jar lib/css2fopnew1_6.jar visitReport.xml paper-size=letter -pdf visitReport.pdf I needed to issue the following command to get it to work: java -cp "lib/" -jar lib/css2fopnew1_6.jar visitReport.xml paper-size=letter -fop -pdf visitReport.pdf The key piece missing, the "-fop" argument. When I read the docs, it seemed that "-pdf" was something that didn't need to be escaped into an FOP specific argument... But maybe that was just me. The one line examples don't actually show PDF creation so I probably just interpreted the documentation wrong. Thanks, -- Aaron |
From: <aro...@cl...> - 2008-10-16 16:54:40
|
Wow! thanks Werner, Brad, and Sergey. You are all very responsive. I'm getting a little further now after adding: visits { region: body; } unfortunately, I get a type of null pointer exception. Do I need to define some other specifier since this is a pure XML document without the XHTML trimmings? Thanks, -- Aaron Here's the stack trace: null be.re.css.CSSToXSLFOException at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:138) at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:267) Caused by: java.util.EmptyStackException at com.sun.org.apache.xml.internal.utils.IntStack.peek(IntStack.java:125) at com.sun.org.apache.xml.internal.dtm.ref.sax2dtm.SAX2DTM2.endElement(SAX2DTM2.java:2239) at com.sun.org.apache.xalan.internal.xsltc.dom.SAXImpl.endElement(SAXImpl.java:936) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerHandlerImpl.endElement(TransformerHandlerImpl.java:273) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.PageSetupFilter.endElement(PageSetupFilter.java:315) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.BlockContainerFilter.endElement(BlockContainerFilter.java:72) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.FootnoteFilter.endElement(FootnoteFilter.java:68) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.LinkFilter.endElement(LinkFilter.java:51) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.WidthAndMarginsFilter.endElement(WidthAndMarginsFilter.java:159) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.CenterFilter.endElement(CenterFilter.java:94) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.NormalizeTableFilter.endElement(NormalizeTableFilter.java:190) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.XHTMLAttributeTranslationFilter.endElement(XHTMLAttributeTranslationFilter.java:272) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.ForeignFilter.endElement(ForeignFilter.java:48) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.DisplayNonePropagator.endElement(DisplayNonePropagator.java:45) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.WrapperFilter.endElement(WrapperFilter.java:45) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.FOMarkerFilter.endElement(FOMarkerFilter.java:98) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at be.re.css.ProjectorFilter.endElement(ProjectorFilter.java:439) at org.xml.sax.helpers.XMLFilterImpl.endElement(XMLFilterImpl.java:546) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) at be.re.xml.sax.ProtectEventHandlerFilter.parse(ProtectEventHandlerFilter.java:56) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at be.re.xml.sax.FilterOfFilters.parse(FilterOfFilters.java:165) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at be.re.xml.sax.FilterOfFilters.parse(FilterOfFilters.java:165) at be.re.css.CSSToXSLFOFilter.parse(CSSToXSLFOFilter.java:324) at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:133) at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:267) Werner Donné <wer...@re...> wrote on 16-10-2008 03:39:48 AM: > Hi Aaron, > > If you add the following rule for the "visits" element it should work: > > visits > { > region: body; > } > > The notion of having regions stems from the fact that an XSL-FO document > is made up of regions and page sequences. For each new page sequence > I have to regenerate stuff starting from the element that represents the > body region. > > I understand you are annoyed by that. It is, however, not so easy to > choose a default body region. At first sight the document element would > be a good candidate, but some XML languages define some preliminary meta > information. As a consequence, a lower element may have to be the body > region. I could scan the CSS files to check if some element already has > been assigned as the body region and use the document element if there > isn't one. However, it is not certain the rule would apply to any > element > at all and moreover, the "style" attribute could have been used inside > the > document to assign the body region. In order to solve this I would have > to examine the complete document first. This is not possible, because > the > tool works as a streaming filter. That is to reduce memory consumption > for very large documents. > > Best regards, > > Werner. > > On 15 Oct 2008, at 20:48, aro...@cl... wrote: > > > > > Hi, > > > > I'm just getting started trying to use css2xslfo. At the moment, I > > just want to see it produce an FO document but I'm getting a file > > with zero bytes. > > > > I tried the following: > > > > java -Dbe.re.stack -jar css2xslfo1_6.jar visitDump.xml -fo > > visitDump.fo > > > > I don't get any warnings of any sort. It chugs away but then creates > > an empty "visitDump.fo" file. > > > > The xml source file is not xhtml, just pure xml. It looks something > > like so: > > > > <?xml version="1.0" encoding="UTF-8"?> > > <?xml-stylesheet href="visitDump.css" type="text/css" media="all"?> > > <visits> > > <protocol> > > <protocol_descriptor>Hello</protocol_descriptor> > > ... > > </protocol> > > ... > > </visits> > > > > Ultimately I'd like to connect it to FOP to produce a PDF but right > > now, I'm not able to get it to do the FO part yet. Any ideas on what > > I might be missing? > > > > Thanks in advance, > > -- > > Aaron > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > challenge > > Build the coolest Linux based applications with Moblin SDK & win > > great prizes > > Grand prize is a trip for two to an Open Source event anywhere in > > the world > > http://moblin-contest.org/redirect.php? > banner_id=100&url=/_______________________________________________ > > css2xslfo-support mailing list > > css...@li... > > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support > > -- > Werner Donné -- Re http://www. > pincette.biz > Engelbeekstraat 8 > http://www.re.be > BE-3300 Tienen > tel: (+32) 486 425803 e-mail: wer...@re... > > > > > |
From: Werner D. <wer...@re...> - 2008-10-16 13:42:39
|
Sergey, I have created feature request 2171585 for this. Best regards, Werner. On 16 Oct 2008, at 14:44, USHAKOV, Sergey wrote: > Thanks Werner for the clarification. I agree that XML is a strict > stuff that > requires equally strict approach :) > > Still thinking about the newbies, I might propose that maybe not > only a > warning to be issued when 'html' tag is found without a proper > namespace, > but moreover a warning like "No formattable data found" or something > similar > to be issued whenever the output file is going to be empty. This > would give > the user a warm feeling that at least he has no problem with tool > configuration, and the problem is only in the data supplied... :) > > Thanks and best regards, > Sergey > > > > ----- Original Message ----- > From: "Werner Donné" <wer...@re...> > To: "USHAKOV, Sergey" <us...@in...> > Cc: <css...@li...> > Sent: Thursday, October 16, 2008 3:54 PM > Subject: Re: [css2xslfo-support] Fw: An empty output .fo file with no > complaints > > > Hi Sergey, > > Thank you for the message. In your case the tool is silent because > technically speaking there is no problem. Using XHTML tags without > the XHTML namespace is considered to be another XML language. Since > CSSToXSLFO is intended to work with any XML language it goes through > the document and finds no match, which is legal in CSS. You would > have the same behaviour with an XSLT style sheet for example. > > Technically, the built-in User Agent style sheet is written for the > XHTML namespace, which is why nothing matches. If you would write > an alternative User Agent style sheet without a namespace, your > document > would work. > > Of course, since there is built-in support for XHTML I could write out > a warning when the "html" tag is used without the XHTML namespace, > which is what I will do for the next release. > > Best regards, > > Werner. > > On 16 Oct 2008, at 13:11, USHAKOV, Sergey wrote: > >> Hi Werner, >> >> this is a copy of my message for the topic similar to the one being >> discussed now, that recently got bounced from sourceforge mail >> server. >> The >> reason of my problem is evidently different, and it is just a >> coinncidence >> that two similar subjects got spoken of simultaneously. >> >> The problem is solved for me now, so my message is just for your >> information. >> >> My best regards, >> Sergey >> >> >> ----- Original Message ----- >> From: "USHAKOV, Sergey" <us...@in...> >> To: <css...@li...> >> Sent: Tuesday, October 14, 2008 8:18 AM >> Subject: An empty output .fo file with no complaints >> >> >>> Hi Werner, >>> >>> I have recently come across a case when the output .fo file was >>> created >>> with zero size, and no complaints were visible. >>> >>> Finally it came out that the namespace identifier of the source >>> xhtml >>> file >>> was wrong, and fixing it solved the problem. >>> >>> I am not sure if keeping silence about encountered problems is the >>> intended behavior for your tool :) so I thought it might be good >>> to let >>> you know... >>> >>> Thanks and best regards, >>> Sergey >> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> css2xslfo-support mailing list >> css...@li... >> https://lists.sourceforge.net/lists/listinfo/css2xslfo-support > > -- > Werner Donné -- Re > http://www.pincette.biz > Engelbeekstraat 8 > http://www.re.be > BE-3300 Tienen > tel: (+32) 486 425803 e-mail: wer...@re... > > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support -- Werner Donné -- Re http://www.pincette.biz Engelbeekstraat 8 http://www.re.be BE-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: USHAKOV, S. <us...@in...> - 2008-10-16 12:45:33
|
Thanks Werner for the clarification. I agree that XML is a strict stuff that requires equally strict approach :) Still thinking about the newbies, I might propose that maybe not only a warning to be issued when 'html' tag is found without a proper namespace, but moreover a warning like "No formattable data found" or something similar to be issued whenever the output file is going to be empty. This would give the user a warm feeling that at least he has no problem with tool configuration, and the problem is only in the data supplied... :) Thanks and best regards, Sergey ----- Original Message ----- From: "Werner Donné" <wer...@re...> To: "USHAKOV, Sergey" <us...@in...> Cc: <css...@li...> Sent: Thursday, October 16, 2008 3:54 PM Subject: Re: [css2xslfo-support] Fw: An empty output .fo file with no complaints Hi Sergey, Thank you for the message. In your case the tool is silent because technically speaking there is no problem. Using XHTML tags without the XHTML namespace is considered to be another XML language. Since CSSToXSLFO is intended to work with any XML language it goes through the document and finds no match, which is legal in CSS. You would have the same behaviour with an XSLT style sheet for example. Technically, the built-in User Agent style sheet is written for the XHTML namespace, which is why nothing matches. If you would write an alternative User Agent style sheet without a namespace, your document would work. Of course, since there is built-in support for XHTML I could write out a warning when the "html" tag is used without the XHTML namespace, which is what I will do for the next release. Best regards, Werner. On 16 Oct 2008, at 13:11, USHAKOV, Sergey wrote: > Hi Werner, > > this is a copy of my message for the topic similar to the one being > discussed now, that recently got bounced from sourceforge mail server. > The > reason of my problem is evidently different, and it is just a > coinncidence > that two similar subjects got spoken of simultaneously. > > The problem is solved for me now, so my message is just for your > information. > > My best regards, > Sergey > > > ----- Original Message ----- > From: "USHAKOV, Sergey" <us...@in...> > To: <css...@li...> > Sent: Tuesday, October 14, 2008 8:18 AM > Subject: An empty output .fo file with no complaints > > >> Hi Werner, >> >> I have recently come across a case when the output .fo file was created >> with zero size, and no complaints were visible. >> >> Finally it came out that the namespace identifier of the source xhtml >> file >> was wrong, and fixing it solved the problem. >> >> I am not sure if keeping silence about encountered problems is the >> intended behavior for your tool :) so I thought it might be good to let >> you know... >> >> Thanks and best regards, >> Sergey > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support -- Werner Donné -- Re http://www.pincette.biz Engelbeekstraat 8 http://www.re.be BE-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: Werner D. <wer...@re...> - 2008-10-16 12:06:40
|
Hi Sergey, Thank you for the message. In your case the tool is silent because technically speaking there is no problem. Using XHTML tags without the XHTML namespace is considered to be another XML language. Since CSSToXSLFO is intended to work with any XML language it goes through the document and finds no match, which is legal in CSS. You would have the same behaviour with an XSLT style sheet for example. Technically, the built-in User Agent style sheet is written for the XHTML namespace, which is why nothing matches. If you would write an alternative User Agent style sheet without a namespace, your document would work. Of course, since there is built-in support for XHTML I could write out a warning when the "html" tag is used without the XHTML namespace, which is what I will do for the next release. Best regards, Werner. On 16 Oct 2008, at 13:11, USHAKOV, Sergey wrote: > Hi Werner, > > this is a copy of my message for the topic similar to the one being > discussed now, that recently got bounced from sourceforge mail > server. The > reason of my problem is evidently different, and it is just a > coinncidence > that two similar subjects got spoken of simultaneously. > > The problem is solved for me now, so my message is just for your > information. > > My best regards, > Sergey > > > ----- Original Message ----- > From: "USHAKOV, Sergey" <us...@in...> > To: <css...@li...> > Sent: Tuesday, October 14, 2008 8:18 AM > Subject: An empty output .fo file with no complaints > > >> Hi Werner, >> >> I have recently come across a case when the output .fo file was >> created >> with zero size, and no complaints were visible. >> >> Finally it came out that the namespace identifier of the source >> xhtml file >> was wrong, and fixing it solved the problem. >> >> I am not sure if keeping silence about encountered problems is the >> intended behavior for your tool :) so I thought it might be good >> to let >> you know... >> >> Thanks and best regards, >> Sergey > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support -- Werner Donné -- Re http://www.pincette.biz Engelbeekstraat 8 http://www.re.be BE-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: USHAKOV, S. <us...@in...> - 2008-10-16 11:12:00
|
Hi Werner, this is a copy of my message for the topic similar to the one being discussed now, that recently got bounced from sourceforge mail server. The reason of my problem is evidently different, and it is just a coinncidence that two similar subjects got spoken of simultaneously. The problem is solved for me now, so my message is just for your information. My best regards, Sergey ----- Original Message ----- From: "USHAKOV, Sergey" <us...@in...> To: <css...@li...> Sent: Tuesday, October 14, 2008 8:18 AM Subject: An empty output .fo file with no complaints > Hi Werner, > > I have recently come across a case when the output .fo file was created > with zero size, and no complaints were visible. > > Finally it came out that the namespace identifier of the source xhtml file > was wrong, and fixing it solved the problem. > > I am not sure if keeping silence about encountered problems is the > intended behavior for your tool :) so I thought it might be good to let > you know... > > Thanks and best regards, > Sergey |
From: Werner D. <wer...@re...> - 2008-10-16 07:40:03
|
Hi Aaron, If you add the following rule for the "visits" element it should work: visits { region: body; } The notion of having regions stems from the fact that an XSL-FO document is made up of regions and page sequences. For each new page sequence I have to regenerate stuff starting from the element that represents the body region. I understand you are annoyed by that. It is, however, not so easy to choose a default body region. At first sight the document element would be a good candidate, but some XML languages define some preliminary meta information. As a consequence, a lower element may have to be the body region. I could scan the CSS files to check if some element already has been assigned as the body region and use the document element if there isn't one. However, it is not certain the rule would apply to any element at all and moreover, the "style" attribute could have been used inside the document to assign the body region. In order to solve this I would have to examine the complete document first. This is not possible, because the tool works as a streaming filter. That is to reduce memory consumption for very large documents. Best regards, Werner. On 15 Oct 2008, at 20:48, aro...@cl... wrote: > > Hi, > > I'm just getting started trying to use css2xslfo. At the moment, I > just want to see it produce an FO document but I'm getting a file > with zero bytes. > > I tried the following: > > java -Dbe.re.stack -jar css2xslfo1_6.jar visitDump.xml -fo > visitDump.fo > > I don't get any warnings of any sort. It chugs away but then creates > an empty "visitDump.fo" file. > > The xml source file is not xhtml, just pure xml. It looks something > like so: > > <?xml version="1.0" encoding="UTF-8"?> > <?xml-stylesheet href="visitDump.css" type="text/css" media="all"?> > <visits> > <protocol> > <protocol_descriptor>Hello</protocol_descriptor> > ... > </protocol> > ... > </visits> > > Ultimately I'd like to connect it to FOP to produce a PDF but right > now, I'm not able to get it to do the FO part yet. Any ideas on what > I might be missing? > > Thanks in advance, > -- > Aaron > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support -- Werner Donné -- Re http://www.pincette.biz Engelbeekstraat 8 http://www.re.be BE-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: Brad C. <bk...@mu...> - 2008-10-15 21:10:13
|
aro...@cl... wrote: > > Hi Brad, > > That gives me a clue. Perhaps I'm misunderstanding what css2xslfo is > supposed to do. I've looked at PrinceXML and "Flying Saucer" both of > which produced a pdf of the xml source file and honored > "page-brake-inside" directives. > > Why should I have to mark up my CSS and XML with various regions? I > could see how it would be useful for footnotes and book printing but > why am I forced to add these? I think you only have to have one region defined, that is 'body'. I think the default body region is the entire page, and css2xslfo just needs to know which element (and children) goes into the body region. I think the default mime-type is 'xhtml', so probably css2xslfo is looking for a <body> element. > > I noticed that the "manual.xhtml" that comes with the css2xslfo > download has many @page directives with regions and the like. It's > able to parse and produce an fo when I invoke a similar command from > the terminal. I don't think that's a very good example, it has lots of complicated regions. I've only used css2xslfo to generate pdfs from xhtml, but it should work with xml as long as you tell it how to display your xml elements. > > I looked through the css2xslfo manual and nothing jumped out at me as > to why I'd have to set regions... Actually, I'm looking at the simplest code I have in-use. It's xhtml and the only unusual css is declaring the page size: <style type="text/css"> @page { margin:0.15in 0.3in 0.15in 0.3in; size: 8.5in 11in; } and the html doesn't have any special styles on it, the <body> element gets rendered on the entire page. > > I *could* probably get permission to post our .css file but I'd prefer > to understand what minimum elements I'd need to setup in it. I could > probably just do that without you having to look over some alien .css > file. I don't know what the minimum is for xml, but at least for xhtml, the minimum appears to be setting the page size (and maybe only that because the default is A4?) -- Brad Clements, bk...@mu... (315)268-1000 http://www.murkworks.com AOL-IM: BKClements |
From: <aro...@cl...> - 2008-10-15 20:53:26
|
Hi Brad, That gives me a clue. Perhaps I'm misunderstanding what css2xslfo is supposed to do. I've looked at PrinceXML and "Flying Saucer" both of which produced a pdf of the xml source file and honored "page-brake-inside" directives. Why should I have to mark up my CSS and XML with various regions? I could see how it would be useful for footnotes and book printing but why am I forced to add these? I noticed that the "manual.xhtml" that comes with the css2xslfo download has many @page directives with regions and the like. It's able to parse and produce an fo when I invoke a similar command from the terminal. I looked through the css2xslfo manual and nothing jumped out at me as to why I'd have to set regions... I *could* probably get permission to post our .css file but I'd prefer to understand what minimum elements I'd need to setup in it. I could probably just do that without you having to look over some alien .css file. Thanks, -- Aaron Brad Clements <bk...@mu...> wrote on 15-10-2008 03:39:30 PM: > It's difficult to answer your question w/o see what's in the > visitDump.css file. > > css2xslfo has to be told what data is 'the body' of each page, which > data goes into various regions, etc. > > > aro...@cl... wrote: > > > > Hi, > > > > I'm just getting started trying to use css2xslfo. At the moment, I > > just want to see it produce an FO document but I'm getting a file with > > zero bytes. > > > > I tried the following: > > > > java -Dbe.re.stack -jar css2xslfo1_6.jar visitDump.xml -fo visitDump.fo > > > > I don't get any warnings of any sort. It chugs away but then creates > > an empty "visitDump.fo" file. > > > > The xml source file is not xhtml, just pure xml. It looks something > > like so: > > > > <?xml version="1.0" encoding="UTF-8"?> > > <?xml-stylesheet href="visitDump.css" type="text/css" media="all"?> > > <visits> > > <protocol> > > <protocol_descriptor>Hello</protocol_descriptor> > > ... > > </protocol> > > ... > > </visits> > > > > Ultimately I'd like to connect it to FOP to produce a PDF but right > > now, I'm not able to get it to do the FO part yet. Any ideas on what I > > might be missing? > > > > Thanks in advance, > > -- Aaron > > ------------------------------------------------------------------------ > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer'schallenge > > Build the coolest Linux based applications with Moblin SDK & win > great prizes > > Grand prize is a trip for two to an Open Source event anywhere in the world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > css2xslfo-support mailing list > > css...@li... > > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support > > > > > -- > Brad Clements, bk...@mu... (315)268-1000 > http://www.murkworks.com > AOL-IM: BKClements > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support |
From: Brad C. <bk...@mu...> - 2008-10-15 19:57:54
|
It's difficult to answer your question w/o see what's in the visitDump.css file. css2xslfo has to be told what data is 'the body' of each page, which data goes into various regions, etc. aro...@cl... wrote: > > Hi, > > I'm just getting started trying to use css2xslfo. At the moment, I > just want to see it produce an FO document but I'm getting a file with > zero bytes. > > I tried the following: > > java -Dbe.re.stack -jar css2xslfo1_6.jar visitDump.xml -fo visitDump.fo > > I don't get any warnings of any sort. It chugs away but then creates > an empty "visitDump.fo" file. > > The xml source file is not xhtml, just pure xml. It looks something > like so: > > <?xml version="1.0" encoding="UTF-8"?> > <?xml-stylesheet href="visitDump.css" type="text/css" media="all"?> > <visits> > <protocol> > <protocol_descriptor>Hello</protocol_descriptor> > ... > </protocol> > ... > </visits> > > Ultimately I'd like to connect it to FOP to produce a PDF but right > now, I'm not able to get it to do the FO part yet. Any ideas on what I > might be missing? > > Thanks in advance, > -- Aaron > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ------------------------------------------------------------------------ > > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support > -- Brad Clements, bk...@mu... (315)268-1000 http://www.murkworks.com AOL-IM: BKClements |
From: <aro...@cl...> - 2008-10-15 19:03:25
|
Hi, I'm just getting started trying to use css2xslfo. At the moment, I just want to see it produce an FO document but I'm getting a file with zero bytes. I tried the following: java -Dbe.re.stack -jar css2xslfo1_6.jar visitDump.xml -fo visitDump.fo I don't get any warnings of any sort. It chugs away but then creates an empty "visitDump.fo" file. The xml source file is not xhtml, just pure xml. It looks something like so: <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet href="visitDump.css" type="text/css" media="all"?> <visits> <protocol> <protocol_descriptor>Hello</protocol_descriptor> ... </protocol> ... </visits> Ultimately I'd like to connect it to FOP to produce a PDF but right now, I'm not able to get it to do the FO part yet. Any ideas on what I might be missing? Thanks in advance, -- Aaron |