Vincent Massol wrote: > On May 18, 2008, at 11:17 PM, [Ricardo Rodriguez] Your EPEC Network > ICT Team wrote: > >> Vincent Massol wrote: >>> The diagram is not completely correct. The PDFClass's xhtmlxsl and >>> fopxsl properties are not indicated correctly. >>> The xhtmlxsl one overrides (replaces, if defined) the default >>> xhtml2fo.xsl one and the fopxsl one overrides (replaces, if defined) >>> the fop.xsl one. >>> >>> Also the style property doesn't replace the pdf.css file (and not >>> pdf.class as mentioned on the diagram) but comes in addition to it. >>> The resulting CSS is pdf.css + the css specified in the style >>> property. >>> >>> Thanks >>> -Vincent >> Thanks, Vincent, >> >> I've uploaded a new release http://tinyurl.com/5oatx4 >> >> Please, what process does use xhtmlfo.xsl stylesheet to transform >> intermediary XHTML 2 to the XSL-FO document? > > a XSL Transformation.
... performed with standard JDK APIs (actually uses xalan inside). See http://www.w3.org/TR/xslt and http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/transform/package-summary.html >> At this point and considering that the resulting CSS is pdf.css + the >> css specified in the style property as you said before, the main issue >> is to know what CSS rules will be accepted there. >> >> For instance, how could I control the appearance of text within >> paragraph tags? I've tried a number of options without success. > > I don't know offhand sorry. > There could be a problem with paragraphs, as Radeox doesn't output correct tags, so instead of having <p>the text</p>, it outputs <p/>the text (the paragraph is outside the text, not around it). As for heading margins, I don't know, maybe FOP has a bug here, or rtf doesn't support that. I'll play around when I have more free time. -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
