RE: odf2xhtml
"G. Ken Holman" <[email protected]> Fri, 09 Apr 2010 12:14:59 -0400
| Newsgroups | gmane.comp.openoffice.devel.xml |
|---|---|
| Message-ID | <[email protected]> |
At 2010-04-09 18:08 +0200, Emmanuel Begue wrote: >What does it mean that "the new OpenOffice 3" _has_ to use Saxon HE? >- "new OOo 3": starting with which version? >- "has to": legally? or just "will use", or "may use"...? My understanding is "has to" because the version of Saxon that supports functions costs money, and I don't see OOo putting in anything that costs money. If OOo stayed with saxon9.jar then any faults/improvements would not be addressed. > > For portability I never used them in my OpenOffice XSLT 2 > > stylesheets, so I'm safe. > >I was nearly as careful but not perfectly: I use (extensively) >saxon:next-in-chain to chain stylesheets and have a more >modular code. > >What would be the alternative to saxon:next-in-chain when >using Saxon HE? Temporary trees, imported stylesheets and modes ... though admittedly not nearly as convenient as "next-in-chain". But using extensions at any time is risky. I underscore that in my class. I might start citing your predicament as another example of why. I have three public classes coming up in the next three months and I'll see what students have to say about the situation in which you find yourself. . . . . . . . . . . . . Ken -- XSLT/XQuery training: San Carlos, California 2010-04-26/30 Principles of XSLT for XQuery Writers: San Francisco,CA 2010-05-03 XSLT/XQuery training: Ottawa, Canada 2010-05-10/14 XSLT/XQuery/UBL/Code List training: Trondheim,Norway 2010-06-02/11 Vote for your XML training: http://www.CraneSoftwrights.com/i/i/ Crane Softwrights Ltd. http://www.CraneSoftwrights.com/i/ G. Ken Holman mailto:[email protected] Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/i/bc Legal business disclaimers: http://www.CraneSoftwrights.com/legal