Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 11 Mar 2003 23:25:53 +0100
From: Marcel Telka <marcel AT telka DOT sk>
To: cygwin AT cygwin DOT com
Subject: Re: cygwinized XSL processor? (or sed for path transform?)
Message-ID: <20030311222553.GG1051@aragorn>
References: <3E6E60B4 DOT 1010102 AT pobox DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3E6E60B4.1010102@pobox.com>; from Tom_Roche@pobox.com on Ut, mar 11, 2003 at 23:18:28 +0100
Lines: 46


Napísané dňa 2003.03.11 23:18, (autor: Tom Roche):
> Is there a cygwinized XSL processor? What I mean, why I ask:
> 
> Occasionally I need to strip cruft out of a bunch (~1k) of xml files.
> Since they're distributed throughout a filesystem, and some additional
> processing is required, I use a bash script to get the input files.
> Feeding them to the processor should be trivial, but unfortunately the
> only command-line XSL processors I know about are Instant Saxon (from
> 
> http://sourceforge.net/project/showfiles.php?group_id=29872
> 
> ) and Xalan (from
> 
> http://xml.apache.org/xalan-j/
> 
> ). Instant Saxon is native windows, which is nice for this
> application, except that it chokes on the cygwin paths emitted by my
> script. Running Xalan from the commandline (like
> 
> java org.apache.xalan.xslt.Process -in <file> -xsl <file> -out <file>
> 
> ) would involve running a java, which (I suspect) would also choke on
> cygwin paths. As a result, my script does a lot of path translations
> like
> 
> cygpath="/g/eclipse/builds/20030311_1000-WB210-AD-V51D-W2/eclipse/plugins"
> winpath="g:\\eclipse\\builds\\20030311_1000-WB210-AD-V51D-W2\\eclipse\\plugins"
> 
> and it doesn't iterate over the paths. (Not a big deal, but it offends
> my software aesthetics :-)
> 
> If I had a cygwinized XSL processor I wouldn't hafta do this. Does
> anyone know where I can get one?

What about xsltproc (a part of the libxslt package)?


Regards.

-- 
+-------------------------------------------+
| Marcel Telka   e-mail:   marcel AT telka DOT sk  |
|                homepage: http://telka.sk/ |
|                jabber:   marcel AT jabber DOT sk |
+-------------------------------------------+

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/