[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] saxon command line error "2>error.txt"


Subject: RE: [xsl] saxon command line error "2>error.txt"
From: "Michael Kay" <mhk@xxxxxxxxx>
Date: Thu, 20 May 2004 15:52:24 +0100

You seem to have got the wrong end of the stick.

One Saxon user asked how to redirect error output on Windows 95.

Another Saxon user told him that Windows 95 didn't have this capability.

End of story, as far as I'm concerned. 

Michael Kay

> -----Original Message-----
> From: M. David Peterson [mailto:m.david@xxxxxxxxxx] 
> Sent: 20 May 2004 14:31
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE: [xsl] saxon command line error "2>error.txt"
> 
> Hey Mike,
> 
> I question the relevance in the issues with Windows 95 in that I know
> very few people, developers especially, that are sitting on top of a
> Win95 box.  Now I do understand that there is still an installed based
> of Windows 95 users out there but what does this fact have to do with
> the ability to get the errors found during testing output to 
> a text file
> when running on top of Windows 95?  Is this functionality you want to
> provide within an application you are creating where having access to
> these errors will be crucial in the support of this product?
> 
> The reason I bring this up is because Pieter Siegers and myself have
> just begun the first stage of porting Saxon 7.9.x over to .NET.
> Understanding real world issues with the current Saxon implementation
> will help us in potentially fixing some of these issues before the
> initial code base is released.  But, given the fact that 
> Windows 95 will
> not run a .NET app, even taking the CLR out of the equation, this
> particular issue is something that would get ignored anyway.
> 
> None the less, can you please explain the need for Saxon to have the
> ability to output errors to a .txt file when it is running on a Win95
> box?  I understand the need and desire to reach out to as 
> many customers
> as possible with any and every product you might develop.  But there
> does come a point in time where the cost of developing for and
> supporting a particular segment of your potential market goes 
> beyond ANY
> profit that could be realized from this same group.
> 
> Anyway, if you feel there is something that Pieter and I need to look
> for in our port to .NET please let us know.
> 
> Thanks!
> 
> <M:D/>
> 
> > -----Original Message-----
> > From: Mike Ferrando [mailto:mikeferrando@xxxxxxxxx]
> > Sent: Thursday, May 20, 2004 8:05 AM
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: RE: [xsl] saxon command line error "2>error.txt"
> > 
> > Michael,
> > I re-checked and both e-mails suggesting this redirect are yours.
> > 
> > http://www.geocrawler.com/mail/msg_raw.php3?msg_id=9920530
> > http://www.biglist.com/lists/xsl-list/archives/200312/msg00276.html
> > 
> > I had a suspicion that the syntax was for the OS. But the error I
> > receive is gives the SAXON options for the commandline.
> > 
> > It just struck me as odd that I found no option that was able to
> > direct the errors to a file. I thought I must be doing something
> > wrong or have misunderstood the options (where to place the syntax).
> > 
> > James Clark's SP has an option that outputs an error file (-f), why
> > can't SAXON have one? Why depend on the OS, when you can write in an
> > option?
> > 
> > My second thought was that, if I have to deal with the OS, maybe I
> > could capture the output in the window to an error.txt file. Thus, I
> > ask concerning an alternative syntax for the command line.
> > 
> > I don't understand the relevancy of your statements concerning
> > documentation.
> > 
> > Thanks.
> > 
> > Mike F.
> > Washington, DC
> > 
> > --- Michael Kay <mhk@xxxxxxxxx> wrote:
> > > I'm sorry, but I've never managed to find any documentation worthy
> > > of the
> > > name for the command line processor in any version of 
> Windows. This
> > > is an
> > > operating system "feature", nothing to do with Saxon or even Java.
> > >
> > > Michael Kay
> > >
> > > > -----Original Message-----
> > > > From: Mike Ferrando [mailto:mikeferrando@xxxxxxxxx]
> > > > Sent: 20 May 2004 08:45
> > > > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > > > Subject: [xsl] saxon command line error "2>error.txt"
> > > >
> > > > Friends,
> > > > I searched through the archive and found a number of e-mails
> > > > concerning outputing the errors of a saxon run to a txt file.
> > > >
> > > > The syntax was "2>error.txt". (Is there a specific 
> place for this
> > > > syntax in the command line?)
> > > >
> > > > My command line works fine for Windows 2000 and XP, but I am
> > > getting
> > > > errors from SAXON on Windows 95 (4.00).
> > > >
> > > > Should I change the command line for Windows 95? What
> > > alternatives do
> > > > I have?
> > > >
> > > > [this should be one line without breaks]
> > > > c:\>saxon.exe -l -w0 -o archivista_x.xml archivista.xml
> > > v1v2002_4.xsl
> > > > "replace=v1v2002_4" 2>error.txt
> > > >
> > > > Mike Ferrando
> > > > Washington, DC
> > > >
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Domains  Claim yours for only $14.70/year
> > > > http://smallbusiness.promotions.yahoo.com/offer
> > >
> > 
> > 
> > 
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Domains - Claim yours for only $14.70/year
> > http://smallbusiness.promotions.yahoo.com/offer


Current Thread