Hi Gioele,
I've gotten so far as to have a working implementation of XSLTFilter
which uses libxml2/libxslt to do the XSL transformation. It's still
missing some details like passing parameters to the xslt script, but it
works for the flat xml export and for xhtml export as well. Using this
On Tue, 2010-12-14 at 20:58 +0100, Thorsten Behrens wrote:
Michael Meeks wrote:
Riight; interesting. Ultimately XSLT requires a DOM to operate on, so I
suppose if we get SAX events from OO.o, we will need to map these to
libxml's nodes.
..
Hm, just getting a DOM tree is even easier -
Hi Peter,
On Mon, 2010-12-13 at 22:21 +0100, Peter Jentsch wrote:
I got the message that xslt processing should be done by libxml/libxslt
not by xalan. Because I'm new to libxml, I first need to have closer
look at libxslts transformation API (and how to use that from LO, which
brings it's
Hi Peter,
On Sun, 2010-12-12 at 17:20 +0100, Peter Jentsch wrote:
I'll have a look at libxslt and try to add support for libxslt to
XSLTFilter.cxx. I the long run I guess it'll be desirable to let XSLT
filter components tell XSLTFilter wether they want saxon9 / XSLT2.0 or
not using an
Hi Gioele,
I got the message that xslt processing should be done by libxml/libxslt
not by xalan. Because I'm new to libxml, I first need to have closer
look at libxslts transformation API (and how to use that from LO, which
brings it's own xml processing API). Currently it looks as if it could
Hi Michael,
I'm from Germany, where XSLT at least currently is slightly more popular
than COBOL.
http://www.google.com/trends?q=COBOL%2C
+XSLTctab=0geo=degeor=alldate=allsort=0
I guess you're right about XSLT 2.0 being at bit underdetermined though.
Cheers,
Peter
Am Montag, den
On Mon, 13 Dec 2010 22:30:50 +0100, Peter Jentsch pj...@guineapics.de wrote:
Hi Michael,
I'm from Germany, where XSLT at least currently is slightly more popular
than COBOL.
But compared to, say, python, both are just background noise :)
Hi Giole, Peter, *,
On Sun, Dec 12, 2010 at 1:27 PM, Gioele Barabucci gio...@svario.it wrote:
IIRC the idea [1] was to move as much XSLT processing as possible to libxml,
not to Xalan, as libxml is already used internally by LibreOffice.
The main goal behind this task is to avoid the need for
Hi, I'm looking for an easy task to start hacking on OOo and because
I've got some experience with XSLT and Java I stumbled upon that
de-java-ising task for the XSLT export filter. Now because the whole
XSLT processing is based on saxon9j I'm wondering if the task makes any
sense? I aware of
