4

We are thinking to use Altova StyleVision. We can create a good report template with it. Altova's default browser shows our work very well. However, generated XSLT files are not supported by the modern web browser.

Any suggestions?

MrWhite
  • 43,179
  • 8
  • 60
  • 84
Harun ERGUL
  • 5,770
  • 5
  • 53
  • 62
  • 3
    It's very hard to answer "why" questions, especially questions about how browser vendors choose to invest their money. However open their products may be, the process by which they make decisions has most of us completely bewildered. – Michael Kay Dec 04 '14 at 22:22
  • 1
    is it very difficult to support XSLT 2.0? I heard W3 recommend even XSLT 3.0 . – Harun ERGUL Dec 09 '14 at 15:21
  • Implementing XSLT 2.0 is probably a 10 person-year project, depending of course on the competence of the implementor. – Michael Kay Dec 10 '14 at 14:27
  • The cost may be big for us but it shouldn't be problem for Microsoft and Google.thanks for response :) – Harun ERGUL Dec 10 '14 at 15:01
  • 2
    You would think so. But even in MS and Google, someone who wants to start a project that costs money has to put forward a business justification, and in a world where the people who want the software don't actually want to pay for it, I've no idea how that is done. – Michael Kay Dec 11 '14 at 00:56

2 Answers2

4

"Why" questions are always complicated as there's generally not a single answer. But I think part of the answer is that there isn't a good implementation of XSLT 2.0 written in C or C++, in the way that libxslt (the backend of xsltproc) and Xalan exist for XSLT 1.0. It's not my intention to start a language war, but for better or worse, most browsers are written in C or C++.

Richard Smith
  • 2,953
  • 2
  • 15
  • 15
2

Saxon CE (http://saxonica.com/ce/index.xml) brings XSLT 2.0 to modern browsers with Javascript enabled, so perhaps that is an option for you. Otherwise you will need to make sure you run the XSLT on the server and provide the transformation result to the browser.

Martin Honnen
  • 160,499
  • 6
  • 90
  • 110
  • 2
    Martin's answer is as good as it gets, unfortunately, as the risk of losing browser support for XSLT altogether is probably greater than the likelihood of ever seeing XSLT 2.0 natively supported. – kjhughes Dec 04 '14 at 20:11