The mechanisms for redirecting the standard error stream vary a little from
one command line processor to another, but in most environments
"2>error.log" should work. If not, it's really an operating system question
rather than a Saxon or XSLT problem, but I guess we can help if you tell us
exactly what OS environment you are in and what command shell you are using.

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: Frank Marent [mailto:frank.marent@xxxxxxxxxxx] 
> Sent: 21 September 2006 14:20
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  writing error file
> 
> hi
> 
> still confused and not able to get xsl:message in a file. i'm 
> using saxon 8.7.3J, calling from a .bat file.
> 
> 
> david:
> > saxon file.xml style.xsl 2> error.log
> 
> no. 2> or 2>> (to append messages) sends errors and 
> recoverable errors from saxon to the file but *not* 
> xsl:message messages.
> 
> 
> george:
> > You can get (in general) the output of the xsl:message but you need 
> > processor specific code for that. Also this requires 
> configuring the 
> > processor in a specific way, thus you need to have control over the 
> > transformation execution.
> 
> what processor specific code would i need for that configuring?
> 
> 
> michael:
> > There may well be product configuration options that allow you to 
> > control where xsl:message output is sent and how it is formatted.
> 
> i checked the saxon options but could not find an 
> appriopriate option. is the -m option usable on the 
> (non-java) command line or .bat level for that?
> 
> 
> thanks in advance
> for your help that is very appreciated
> 
> frank