Issue 83500 - Implement possibility to choose XSLT 2.0 capable external XSLT(XQuery) processor for import/export filters
Summary: Implement possibility to choose XSLT 2.0 capable external XSLT(XQuery) proces...
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 2.3
Hardware: All All
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-11-09 16:22 UTC by vsedov
Modified: 2013-02-07 22:41 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description vsedov 2007-11-09 16:22:53 UTC
Look like migration from sxw to odt xml schema require complex XSLT code
review/rewrite circle (good chance for XSLT version upgrade). For now W3C XSLT
2.0 have status as final recommendation and stable.  XSLT 2.0 in compare with
XSLT 1.0 have much better design, more powerful functions set & much more
improvements (most notable examples: multiple document output, parameters
tunneling, user defined functions, native nodeset construction and reuse,
sequences, XPath 2.0 support, xsl:next-match element, possibility to tokenize
strings using RegExps, schema-aware optimizations possibility). I guess it also
can be possible for use XQuery 1.0 for some cases of transformations (some
developers sometime prefer XQuery over XSLT).

p.s. possibly i choose wrong component - it good also for spreadsheets, draws &
presentations but i can`t find proper component/subcomponent (: sorry :)
Comment 1 michael.ruess 2007-11-12 09:07:20 UTC
Reassigned to requirements.
Comment 2 xquery 2009-04-03 05:47:48 UTC
please close it - it already implemented
Comment 3 gleppert 2009-04-03 07:59:18 UTC
Does this mean that it is now generally possible to deal with external style
sheets, e.g. access external css-files during XHTML import?

Thank you!