Tag: xslt


xmlvm

The goal of XMLVM is to offer a flexible and extensible cross-compiler toolchain. Instead of cross-compiling on a source code level, XMLVM cross-compiles byte code instructions from Sun Microsystem’s virtual machine and Microsoft’s Common Language Runtime. The benefit of this approach is that byte code instructions are easier to cross-compile and the difficult parsing of a high-level programming language is left to a regular compiler. In XMLVM, byte code-based programs are represented as XML documents. This allows manipulation and translation of XMLVM-based programs using advanced XML technologies such as XSLT, XQuery, and XPath.


WSDL viewer

WSDL has its constructive logic, but it is hard to read / understand the content by business professionals (mostly non-programmers). Here is a small tool to visualize the web-service in a more intuitive way.

Comparing XSLT and XQuery

This paper will attempt an objective side-by-side comparison of the two languages: not just from the point of view of technical features, but also looking at usability, vendor support, performance, portability, and other decision factors. Is it true, for example, that XQuery is better for data and XSLT is better for documents? Is one or the other language easier to learn depending on your computing background? As well as trying to answer these questions, the paper will also illustrate how the two languages can interoperate, so that each can be used for the parts of an application where it is most appropriate.

Comparing XSLT and XQuery

This paper will attempt an objective side-by-side comparison of the two languages: not just from the point of view of technical features, but also looking at usability, vendor support, performance, portability, and other decision factors. Is it true, for example, that XQuery is better for data and XSLT is better for documents? Is one or the other language easier to learn depending on your computing background? As well as trying to answer these questions, the paper will also illustrate how the two languages can interoperate, so that each can be used for the parts of an application where it is most appropriate.

Signs on the Sand: Detecting version of Microsoft XSLT engine from within XSLT

Sometimes it’s useful to detect which XSLT engine your XSLT stylersheet is being executed by, e.g. to shortcut processing using an engine-specific extension function or to workaround a bug in particlular engine. Now that Microsoft alone ships 3 different XSLT engines – MSXML3/MSXML4/MSXML5/MSXML6, XslTransform and XslCompiledTransform, detecting XSLT engine from within XSLT stylesheet may be vital requirement. Here is how it can be done.

xslt2Xforms – cross browser W3C Xforms processor

xslt2Xforms is a cross browser “W3C Xforms” processor. This xsl stylesheet adds the W3C Xforms support in your web project using Xhtml, Javascript and Css.
The result code is cross-browser compliant (tested on Internet Explorer 6 and Mozilla 1.7). This stylesheet seems to work with all recent xslt engines.

This is vaporware for the time being but who knows…

Sarissa is a JavaScript meta-API. It bridges the gap of DOM XML extentions between Internet Explorer and Mozilla (or Moz-based) browsers. It is an effort to provide a common interface for those extentions, bringing them closer to eachother.

CSSToXSLFO

CSSToXSLFO is a utility which can convert an XML document, together with a CSS2 style sheet, into an XSLFO document. It has special support for the XHTML vocabulary, because that is the most obvious language it would be used for. The tool has a number of page-related extensions. It also comes with an API in the form of an XML filter.

Improve your XSLT coding five ways

Whether you’re a beginner with XSLT or a seasoned programmer, you’ll surely find that these five tips from Benoit Marchal will improve your coding and give you new ideas. The handful of tips cover using CSS with XSL style sheets (including HTML entities), incorporating client-side JavaScript, working with multiple input documents, and using XSLT to generate style sheets automatically. The article includes sample code to adapt and reuse

Sarissa Documentation

Sarissa is a JavaScript meta-API. It bridges the gap of DOM XML extentions between Internet Explorer and Mozilla (or Moz-based) browsers. It is an effort to provide a common interface for those extentions, bringing them closer to eachother.
Sarissa implements some of IE extentions for Mozilla. These are:

  • The xml property, which gives the serialized XML String of a DOM Object.

  • The HTMLElement.innerText property, which gives the text of a node with the tags stripped out

  • The DOMDocument.async property, which controls synchronous/asynchronous loading of XML documents

.

Load More