[Libreoffice] De-Java-ise flat XML export

Peter Jentsch <pjotr -AT- guineapics.de>
Sat, 11 Dec 2010 22:42:28 +0100

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 saxon9n, the .NET version, but I don't think
requiring .NET would be a major improvement compared to requiring Java. 
Am I missing something? Xalan C++ doesn't support XSLT 2.0, does anybody
known if XSLT export filters promise to support XSLT 2.0 (or XSLT 1.1)?

Cheers,
Peter

Context

[Libreoffice] De-Java-ise flat XML export · Peter Jentsch
- Re: [Libreoffice] De-Java-ise flat XML export · Gioele Barabucci
  - Re: [Libreoffice] De-Java-ise flat XML export · Christian Lohmaier
    - Re: [Libreoffice] De-Java-ise flat XML export · Peter Jentsch
      - Re: [Libreoffice] De-Java-ise flat XML export · Michael Meeks
        
        Re: [Libreoffice] De-Java-ise flat XML export · Peter Jentsch
        
        Re: [Libreoffice] De-Java-ise flat XML export · Sebastian Spaeth
  - Re: [Libreoffice] De-Java-ise flat XML export · Peter Jentsch
    - Re: [Libreoffice] De-Java-ise flat XML export · Michael Meeks
      - Re: [Libreoffice] De-Java-ise flat XML export · Thorsten Behrens
        
        Re: [Libreoffice] De-Java-ise flat XML export · Michael Meeks

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.