From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5707 invoked by alias); 28 Nov 2005 22:26:53 -0000 Received: (qmail 5671 invoked by uid 22791); 28 Nov 2005 22:26:53 -0000 X-Spam-Check-By: sourceware.org Received: from host1.berger.blasberg-computer.de (HELO host1.berger.blasberg-computer.de) (85.159.13.42) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 28 Nov 2005 22:26:50 +0000 Received: from /spool/local by gymel.de with [XMail 1.22 LMAIL Server] for from ; Mon, 28 Nov 2005 23:27:12 +0100 To: cygwin@cygwin.com From: Thomas Berger Subject: X-AuthUser: thb Received: from [192.168.168.134] by local.gymel.com with [XMail 1.22 ESMTP Server] id for from ; Mon, 28 Nov 2005 23:27:09 +0100 Message-ID: <438B8421.4080106@Gymel.com> Date: Mon, 28 Nov 2005 22:45:00 -0000 Reply-To: thb@gymel.com User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) MIME-Version: 1.0 Subject: [Fwd: xsltproc from libxstl-1.1.15-1] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2005-11/txt/msg00876.txt.bz2 Woah Gerrit, WDYDWMLF (what did you do with my line feeds)? o.k. since the libxml maintainer choose to forward my struggles to the list, here comes the readable form: I'm using xsltproc from .bat-Files under cmd/command and so far had no problems with Backslashes for paths on the command line (at least when the last component is divided by a proper slash from the actual file name). >>>>>> Using libxml 20622, libxslt 10115-CVS1027 and libexslt 812-CVS1027 xsltproc was compiled against libxml 20622, libxslt 10115 and libexslt 812 libxslt 10115 was compiled against libxml 20622 libexslt 812 was compiled against libxml 20622 <<< Thus (ini2bat.xsl contains with >set -H2k=G:\hans2k >xsltproc --load-trace --noout %-H2k%/util/confxml/ini2bat.xsl %-H2k%/config/empty.xml yields: Loaded URL="G:\hans2k/util/confxml/ini2bat.xsl" ID="(null)" warning: failed to load external entity "lib/readconf.xsl" compilation error: file G:\hans2k/util/confxml/ini2bat.xsl line 7 element import xsl:import : unable to load lib/readconf.xsl and with >set -H2k=G:/hans2k >xsltproc --load-trace --noout %-H2k%/util/confxml/ini2bat.xsl %-H2k%/config/empty.xml yields: Loaded URL="G:/hans2k/util/confxml/ini2bat.xsl" ID="(null)" Loaded URL="G:///hans2k/util/confxml/lib/readconf.xsl" ID="(null)" ... The previous version worked o.k. (for me): >>>>>> Using libxml 20620, libxslt 10114-CVS1011 and libexslt 812-CVS1011 xsltproc was compiled against libxml 20620, libxslt 10114 and libexslt 812 libxslt 10114 was compiled against libxml 20620 libexslt 812 was compiled against libxml 20620 <<< Loaded URL="G:\hans2k/util/confxml/ini2bat.xsl" ID="(null)" Loaded URL="G%3A%5Chans2k/util/confxml/lib/readconf.xsl" ID="(null)" ... At the moment I cannot see any possibilty to "slashify" my file paths prior to calling xsltproc. unfortunately I got lost studying the sources. In uri.c of libxml is no special path processing for CYGWIN, but there hasn't, since cygwin takes care of paths? My guess is, that test on "\" in IS_UNWISE cancels processing of those paths in several routines in uri.c thus it would be wise to (re?)introduce some CYGWIN-specific normalization in xmlCanonicPath in uri.c . However the comment "This really need to be cleaned up by someone with a Windows box" for the win32-specific normalization is not really encouraging... Do you have any ideas? simple testcase below: ---------- foo.xsl -------------- --------------------------------- ---------- bar.xsl ----------------- ------------------------------------ call as xsltproc --load-trace u:/bla/foo.xsl u:/bla/foo.xsl vs. xsltproc --load-trace u:\bla/foo.xsl u:/bla/foo.xsl Greetings Thomas Berger -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/