20 May
2008
20 May
'08
2:59 p.m.
[Ricardo Rodriguez] Your EPEC Network ICT Team wrote:
Sergiu, Vicent,
Thanks for your inputs.
Sergiu Dumitriu wrote:
It is a bug, but an unfixable one. The problem is that Radeox works with
regular expressions, and regular expressions are not strong enough to
capture an paragraph.
Vincent Massol wrote:
OK. Please, could you take a look to the modified diagram? My main
concern is to find a "standard" way of representing processes within
XWiki. I know I am not the only one looking for such a thing! :-) So,
any idea will be welcome.
http://tinyurl.com/3ge3me
I think the pieces are now clear for me. A quite different thing is to
be able to deal with each of them to modify the output.
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…
> 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.
>
>
Is this a Radeox bug or does it make sense in this environment? As for heading margins, I've been playing with a
rtf file with different
indentations and margins applied to headings and paragraphs. It seems to
move fine at least between Word, Pages and OpenOffice. In Mac, Suse
Linux and Windows.
As far as I see, the next step for me is to configure a developing
environment for XWiki here and learn at least how to trap at least the
two intermediary XHTMLs and the XSL-FO documents to keep track of
changes and issues.
Please, if you have any idea about how to modify heading margins,
pictures size and <p> appearance, it will be really welcome! Thanks!
We could try to use a newer version of fop and css4j. I already updated
fop in the trunk. css4j needs some testing, as the version we're using
is pretty old (0.4, compared to 0.9.1), and the API might have changed.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/