RE: cygwinized XSL processor? (or sed for path transform?)

2003-03-12 Thread Al Slater
Hi

 http://sourceforge.net/project/showfiles.php?group_id=29872

 ) and Xalan (from

 http://xml.apache.org/xalan-j/


There is a C++ Xalan (xalan-c) available from
http://xml.apache.org/xalan-c/index.html

I don't know if it builds OOTB on cygwin though.

regards

Al Slater



--
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/



Re: cygwinized XSL processor? (or sed for path transform?)

2003-03-12 Thread Tom Roche
On Tue, 11 Mar 2003, Tom Roche wrote:
 my script does a lot of path translations like
 cygpath=/g/eclipse/builds/foo
 winpath=g:\\eclipse\\builds\\foo
 and it doesn't iterate over the paths. (Not a big deal, but it
 offends my software aesthetics :-)
Igor Pechtchanski Tue, 11 Mar 2003 17:57:49 -0500 (EST)
 I suspect the -p and -f options to cygpath might be of some help
 to you.
No, but cygpath -a is a great help! I can iterate over the windows
paths, and get the cygwin paths from them with `cygpath -a $winpath`.
Thanks for the suggestion!
--
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/


Re: cygwinized XSL processor? (or sed for path transform?)

2003-03-11 Thread Marcel Telka

Napsan da 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:   [EMAIL PROTECTED]  |
|homepage: http://telka.sk/ |
|jabber:   [EMAIL PROTECTED] |
+---+

--
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/



Re: cygwinized XSL processor? (or sed for path transform?)

2003-03-11 Thread Frank Schmitt
Tom Roche [EMAIL PROTECTED] writes:

 ). Instant Saxon is native windows, which is nice for this
 application, except that it chokes on the cygwin paths emitted by my
 script.

Use the cygpath utility, it can transform Cygwin paths to Windows and
vice versa.

-- 
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.


--
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/



Re: cygwinized XSL processor? (or sed for path transform?)

2003-03-11 Thread Igor Pechtchanski
On Tue, 11 Mar 2003, Tom Roche wrote:

 [snip]
 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 :-)
 [snip]
 Alternatively, if I had more sed chops, I could script the path
 transformation, but I don't know how to do that either. (Could someone
 tell me how to do that?)

I suspect the -p and -f options to cygpath might be of some help to
you.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
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/