[odf-discuss] OOo OOXML filters
marbux at gmail.com
Tue Dec 12 13:11:33 EST 2006
On 12/12/06, Alex Hudson <alex at stratagia.co.uk> wrote:
> marbux wrote:
> > On 12/12/06, Alex Hudson <alex at stratagia.co.uk> wrote:
> >> I don't think that's true - at least, OXML's inclusion of XPath is
> >> neither here nor there.
> > You'd get a big argument on that from Gary Edwards and Florian Reuter. :-)
> I think wires have probably been crossed. OXML doesn't need to include
> XPath any more than ODF does.
Sorry for the careless language. I guess a better way of putting it is
that EOOXML is far from fully XPath-addressable and that mucks with
its transformation via an XSLT.
> >> Ditto, the style models of the two formats are sufficiently different
> >> that converting in XSLT would be painful.
> > But that is what the Novell/Microsoft/CleverAge project is doing.
> No, it's not. They're doing the main structural conversion in XSLT, but
> then they're using a post-processing output to do transformations that
> are too difficult/cumbersome to do in XSLT.
> The two examples I gave are being coded in C# in the CleverAge project.
> > Not things like <office:font-decls><style:font-decl>? How are they not
> > processing instructions?
> Because they're tags.
Thank you for the vocabulary lesson. I guess that means the language
in section 1.5 needs clarification.
More information about the odf-discuss