Some more research on the saxon replacement

2011-10-04 Thread Pedro Giffuni
Hi;

I was happily lurking around with opengrok to fix a long standing
issue in the FreeBSD port related to gperf (yucks!) and I found
with surprise that writerfilter/source/ooxml/rngtocxx and a lot
of other files make reference to xalan but of course, ...
we don't carry xalan!

Now I did a search for saxon, and apart from configure and a
couple of .xsl files we only use saxon here:
/filter/source/xsltfilter/XSLTransformer.java

So... I went to our wonderful new bitbucket repository and I
found this comment from 2008:

There is no module 'xalan' any more, has been removed by CWS xsltfilter10.

So now I looked in the history for saxon and effectively
xsltfilter10 appears again (repeatedly) and there is a hint
on the the reason for the replacement:
#i91376# - xslt2 processor for OOo xmll filters

I think the reason for the replacement is that Apache
xalan doesn't support xslt version 2, and the fact that
the latest version was released in 2007 doesn't help
nowadays.

So after some detective work I got to the same options we
had before: if we don't need xslt2 we may be able to move
back to Xalan but ideally we should be looking at Zorba
instead:
http://www.zorba-xquery.com/

cheers,

Pedro.



Re: saxon

2011-09-16 Thread Pedro F. Giffuni
Hi again;

I noticed this nice package came in through FreshPorts:

http://www.zorba-xquery.com/

It appears to have all the functionality of saxon under
an Apache version 2 license, so it could be another
alternative to consider along with Xalan/Xerces.

I should also mention that I contacted the saxon authors
and while they would've really liked to adopt an Apache
License this is not really possible anytime soon due
to some contributed code and difficulties getting all
the approvals. Apparently IBM also went through such
a process with them before and ended giving up.

cheers,

Pedro.

--- On Mon, 8/29/11, Mathias Bauer  wrote:

 Am 29.08.2011 17:41, schrieb Pedro F. Giffuni:
 
  Looking a bit into Matthias' list, there's the saxon
 issue.
  
  I looked for a replacement and it would look like the
  Apache Xalan project could be an alternative:
  
     http://xalan.apache.org/
  
  If, for some reason, we want to keep saxon, please
 note:
  
  - In principle it would seem like it's required by
 doc
  developers only, right? So in principle we shouldn't
  require it unless we are regenerating the help files.
  BTW, the DITA toolkit also uses saxon.
  
  - The version we use is extremely outdated and without
 support
  of any kind. I would recommend checking out the
 Homepage and
  adopt either the last Saxon-B or, preferable,
 Saxon-HE.
  Also the saxon patch in OO mentions a bug in ant that
 was
  solved long ago.
 
 saxon is used at least for our xslt filters (or only for
 some of them, I
 don't know). Until noone investigated that further, we
 can't exclude
 that we need a replacement.
 
 Regards,
 Mathias
 



saxon

2011-08-29 Thread Pedro F. Giffuni
Looking a bit into Matthias' list, there's the saxon issue.

I looked for a replacement and it would look like the
Apache Xalan project could be an alternative:

   http://xalan.apache.org/

If, for some reason, we want to keep saxon, please note:

- In principle it would seem like it's required by doc
developers only, right? So in principle we shouldn't
require it unless we are regenerating the help files.
BTW, the DITA toolkit also uses saxon.

- The version we use is extremely outdated and without support
of any kind. I would recommend checking out the Homepage and
adopt either the last Saxon-B or, preferable, Saxon-HE.
Also the saxon patch in OO mentions a bug in ant that was
solved long ago.


regards,

Pedro.


Re: saxon

2011-08-29 Thread Mathias Bauer
Am 29.08.2011 17:41, schrieb Pedro F. Giffuni:

 Looking a bit into Matthias' list, there's the saxon issue.
 
 I looked for a replacement and it would look like the
 Apache Xalan project could be an alternative:
 
http://xalan.apache.org/
 
 If, for some reason, we want to keep saxon, please note:
 
 - In principle it would seem like it's required by doc
 developers only, right? So in principle we shouldn't
 require it unless we are regenerating the help files.
 BTW, the DITA toolkit also uses saxon.
 
 - The version we use is extremely outdated and without support
 of any kind. I would recommend checking out the Homepage and
 adopt either the last Saxon-B or, preferable, Saxon-HE.
 Also the saxon patch in OO mentions a bug in ant that was
 solved long ago.

saxon is used at least for our xslt filters (or only for some of them, I
don't know). Until noone investigated that further, we can't exclude
that we need a replacement.

Regards,
Mathias