On 29/08/2012 08:53, santhosh k wrote:
Let's turn this around. You tell me how you are running the
transformation (from the command line? from a Java or .NET
application? using what API?) and I'll see if we can tell what you
are doing wrong.
Thank you very much.
Its a very useful information for me.
It will be helpful for me if you can provide an example
>If you are not seeing an error, then there is something wrong
>way you are doing error handling.
1) How to handle the error from saxon.
By default, Saxon writes error messages to the standard error
output. In GUI applications, this is often not visible. You
therefore have to arrange to send the error messages somewhere else,
either a window on the screen or a log file.
The choice affects the way in which the result tree produced by the
transformation is serialized (that is, converted to a stream of
I would like to know what is the difference between providing
xsl:output as xml, html and xhtml.
There's plenty of information available on this. I would recommend
reading the relevant section of my book (XSLT 2.0 Programmer's
Reference). Failing that, there are many tutorials available, and
there's always the W3C specification itself.