From smckenzie@borland.com Mon Mar 31 19:44:20 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from outgoing.borland.com (unknown [143.186.72.221]) by mail.gnome.org (Postfix) with ESMTP id 24232180FD for ; Mon, 31 Mar 2003 19:44:20 -0500 (EST) Received: from borland.com (bigip-snat.inprise.com [10.186.98.50]) by sv-mta1.inprise.com (iPlanet Messaging Server 5.2 HotFix 1.10 (built Jan 23 2003)) with ESMTP id <0HCN00JHF3DUFV@sv-mta1.inprise.com> for xslt@gnome.org; Mon, 31 Mar 2003 16:44:18 -0800 (PST) Date: Mon, 31 Mar 2003 16:48:17 -0800 From: "Shawn O. McKenzie" To: xslt@gnome.org Message-id: <3E88E1D1.6010709@borland.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 Subject: [xslt] libxslt bug? stripping namespace prefix in element output. Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Howdee. I have been beating my head against a problem and am wondering if it is a bug. I am having problems outputing elements in an html file that have a different namespace prefix. Something like Here is a simple example. Given an XML file of: And a stylesheet of: I get an output of: onetwothreefour So, it seems to be stripping the foo: prefix off the foo:whatever element. Does this using both xsltproc and Python. Seems to work fine on Microsoft's processor and on Saxon. From veillard@redhat.com Tue Apr 1 04:31:40 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 2186E182DE for ; Tue, 1 Apr 2003 04:31:38 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h319TOE05051; Tue, 1 Apr 2003 04:29:24 -0500 Date: Tue, 1 Apr 2003 04:29:24 -0500 From: Daniel Veillard To: smckenzie@borland.com Cc: xslt@gnome.org Subject: Re: [xslt] libxslt bug? stripping namespace prefix in element output. Message-ID: <20030401042924.G31240@redhat.com> References: <3E88E1D1.6010709@borland.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3E88E1D1.6010709@borland.com>; from smckenzie@borland.com on Mon, Mar 31, 2003 at 04:48:17PM -0800 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Mar 31, 2003 at 04:48:17PM -0800, Shawn O. McKenzie wrote: > Howdee. > > I have been beating my head against a problem and am wondering if it is > a bug. I am having problems outputing elements in an html file that have > a different namespace prefix. Something like Term="foo"/> [...] > > I get an output of: > > > onetwothreefour > > > So, it seems to be stripping the foo: prefix off the foo:whatever > element. Does this using both xsltproc and Python. Seems to work fine on > Microsoft's processor and on Saxon. As pointed by http://xmlsoft.org/XSLT/bugs.html the first thing to do is to check with a recent version. Since you don't indicate it I'm pretty sure it's just that you're using an older one, this has been fixed a few releases ago in libxml2. So upgrade ! paphio:~/tmp -> xsltproc tst.xsl tst.xml onetwothreefour paphio:~/tmp -> But your report was useful anyway, as you can see there was a bug in the namespace handling resulting in repeated xmlns:foo declarations. I fixed it in CVS and added it to the regression tests: paphio:~/tmp -> xsltproc tst.xsl tst.xml onetwothreefour paphio:~/tmp -> This looks better, thanks, Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard@redhat.com Tue Apr 1 09:29:45 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 8D4B218A9B for ; Tue, 1 Apr 2003 09:29:45 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h31ETej14388 for xslt@gnome.org; Tue, 1 Apr 2003 09:29:40 -0500 Date: Tue, 1 Apr 2003 09:29:40 -0500 From: Daniel Veillard To: xslt@gnome.org Message-ID: <20030401092940.I31240@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: [xslt] Release of libxslt-1.0.29 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: It's a real release, not an April Fool joke ! ftp://xmlsoft.org/ http://xmlsoft.org/XSLT/ This includes a few bug fixes from last week release and a significant speedup for large (flat) documents which also requires libxml2-2.5.6: * performance improvements especially for large flat documents * bug fixes: Result Value Tree handling, XML IDs, keys(), extra namespace declarations with xsl:elements. * portability: python and trio fixes (Albert Chin), python on Solaris (Ben Phillips) Thanks for the bug reports and patches, Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From gena01@lk.net Tue Apr 1 15:18:47 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from capital.lk.net (capital.lk.net [207.87.225.1]) by mail.gnome.org (Postfix) with ESMTP id B2FAB18B78 for ; Tue, 1 Apr 2003 15:18:47 -0500 (EST) Received: (from nobody@localhost) by capital.lk.net (8.11.6/8.11.6) id h31KIlM24817; Tue, 1 Apr 2003 15:18:47 -0500 Date: Tue, 1 Apr 2003 15:18:47 -0500 Message-Id: <200304012018.h31KIlM24817@capital.lk.net> X-Authentication-Warning: capital.lk.net: nobody set sender to gena01@lk.net using -f From: "Gennady Feldman" To: xslt@gnome.org Subject: Re: [xslt] Release of libxslt-1.0.29 X-Mailer: NeoMail 1.23 X-IPAddress: 198.140.63.114 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > It's a real release, not an April Fool joke ! > ftp://xmlsoft.org/ > http://xmlsoft.org/XSLT/ > > This includes a few bug fixes from last week release and a significant > speedup for large (flat) documents which also requires libxml2-2.5.6: > * performance improvements especially for large flat documents > * bug fixes: Result Value Tree handling, XML IDs, keys(), extra namespace > declarations with xsl:elements. > * portability: python and trio fixes (Albert Chin), python on Solaris > (Ben Phillips) > > Thanks for the bug reports and patches, > > Daniel > [clipped] First of all great work on the latest releases of libxml2 and libxslt. I had some issues with our work proxy, took me like 2-3 hours to finally download the source files using FTP (was truncating the files). I am recompiling all of them right now. A couple of things that I needed to do to get the stuff compiling. Currently the way I compile stuff is extract the .tar.gz archives and do "aclocal" "autoconf" "configure" then edit Makefile change "rpmbuild" to "rpm" and then do "make rpm". In latest releases I had to edit the docs/Makefile since it wouldn't build because of some xml2-refs.xml file (or something close to that) until I removed it as a dependency. Also doing "rpm --rebuild" on libxslt .src.rpm doesn't work since somehow it doesn't generate the libraries and fails during build. I am doing a similar approach using the .tar.gz w/ "make rpm". Oh yeah almost forgot somehow Makefile uses "gtar" instead of regular "tar". I am on Suse 8.0 system w/ an old rpm (3.0.6) G.F. aka Gena01 http://www.gena01.com From ke@suse.de Wed Apr 2 09:47:52 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by mail.gnome.org (Postfix) with ESMTP id A894D18106 for ; Wed, 2 Apr 2003 09:47:52 -0500 (EST) Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id CA13714783; Wed, 2 Apr 2003 16:47:51 +0200 (MEST) X-Authentication-Warning: frechet.suse.de: ke set sender to ke@suse.de using -f To: xslt@gnome.org Cc: gena01@lk.net Subject: Re: [xslt] Release of libxslt-1.0.29 From: Karl Eichwalder Date: Wed, 02 Apr 2003 16:47:49 +0200 In-Reply-To: <200304012018.h31KIlM24817@capital.lk.net> ("Gennady Feldman"'s message of "Tue, 1 Apr 2003 15:18:47 -0500") Message-ID: User-Agent: Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.3.50 (gnu/linux) References: <200304012018.h31KIlM24817@capital.lk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: "Gennady Feldman" writes: > First of all great work on the latest releases of libxml2 and libxslt. I > had some issues with our work proxy, took me like 2-3 hours to finally > download the source files using FTP (was truncating the files). Often I've good luck with: ftp://ftp.linux.org.uk/mirrors/ftp.gnome.org/sources/ > I am recompiling all of them right now. A couple of things that I > needed to do to get the stuff compiling. Currently the way I compile > stuff is extract the .tar.gz archives and do "aclocal" "autoconf" > "configure" That's what I'm usually doing, too. You can try the spec files coming with my test builds resp. source RPMs: ftp://ftp.suse.com/pub/people/ke/SRPM/ > I am on Suse 8.0 system w/ an old rpm (3.0.6) If wanted I can also build RPMs for SuSE Linux 8.0; at the moment, on ftp://ftp.suse.com/pub/people/ke only 8.1 and 8.2 is up-to-date. Just drop me a line. -- Linux frechet 2.4.19-4GB #1 Thu Nov 14 11:46:51 UTC 2002 i686 unknown 4:41pm up 11 days, 2:02, 11 users, load average: 0.17, 0.31, 0.48 work : ke@suse.de Karl Eichwalder home : keichwa@gmx.net From sbwoodside@yahoo.com Thu Apr 3 01:48:21 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from tomts22-srv.bellnexxia.net (tomts22.bellnexxia.net [209.226.175.184]) by mail.gnome.org (Postfix) with ESMTP id 13A7818104 for ; Thu, 3 Apr 2003 01:48:21 -0500 (EST) Received: from yahoo.com ([65.93.184.5]) by tomts22-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20030403064820.SOIJ25567.tomts22-srv.bellnexxia.net@yahoo.com>; Thu, 3 Apr 2003 01:48:20 -0500 Date: Thu, 3 Apr 2003 01:48:19 -0500 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed From: S Woodside To: axkit-users@axkit.org, xslt@gnome.org Content-Transfer-Encoding: 7bit Message-Id: <411C83E4-65A0-11D7-9A55-000393414368@yahoo.com> X-Mailer: Apple Mail (2.551) Subject: [xslt] more on the xslt namespace pipeline issue Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Here's another go at the pipeline namespace problem. AxKit is 1.6.1 Using libxml 20425, libxslt 10019 and libexslt 710 /=======================================================\ a_instance.xml The source document. \=======================================================/ /=======================================================\ test1.xml This is applied to the above instance file. \=======================================================/ RNG Form /=======================================================\ b_instance.xml This file is the product of the command: % xsltproc test1.xsl a_instance.xml Or equivalently it is the same as the file from AxTrace named "_2fa_instance.xml.1" They are the same, which is as things should be. \=======================================================/ RNG Form /=======================================================\ test2.xml This is applied to b_instance, the above file, when it's loaded with AxKit. It's also applied to a_instance, the first file, as the second stage, when that's loaded with AxKit. Note how various different namespacing prefixes are used (or not used) ... that will reveal the bug. \=======================================================/

[should be followed by text]

[should be followed by nothing]

[should be in h1]

/=======================================================\ OUTPUT A http://localhost/exp/bug1/a_instance.xml Demonstrates the incorrect output. \=======================================================/ RNG Form

[should be followed by text]

[should be followed by nothing] RNG Form /=======================================================\ OUTPUT B http://localhost/exp/bug1/b_instance.xml Demonstrates the correct output. \=======================================================/

[should be in h1] RNG Form

[should be followed by text] RNG Form

[should be followed by nothing] From robin.berjon@expway.fr Thu Apr 3 04:20:17 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mwinf0404.wanadoo.fr (smtp3.wanadoo.fr [193.252.22.27]) by mail.gnome.org (Postfix) with ESMTP id 13FD31817F for ; Thu, 3 Apr 2003 04:20:17 -0500 (EST) Received: from expway.fr (APastourelles-107-2-4-235.abo.wanadoo.fr [193.252.9.235]) by mwinf0404.wanadoo.fr (SMTP Server) with ESMTP id B0F3D38002C6; Thu, 3 Apr 2003 11:20:13 +0200 (CEST) Message-ID: <3E8BFC51.9010100@expway.fr> Date: Thu, 03 Apr 2003 11:18:09 +0200 From: Robin Berjon Organization: Expway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-gb, en, fr MIME-Version: 1.0 To: S Woodside Cc: axkit-users@axkit.org, xslt@gnome.org References: <411C83E4-65A0-11D7-9A55-000393414368@yahoo.com> In-Reply-To: <411C83E4-65A0-11D7-9A55-000393414368@yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xslt] Re: more on the xslt namespace pipeline issue Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: robin.berjon@expway.fr List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: S Woodside wrote: > Here's another go at the pipeline namespace problem. > AxKit is 1.6.1 > Using libxml 20425, libxslt 10019 and libexslt 710 And at last we have the answer! It's pretty simple actually. One *crucial* thing to know here is that in AxKit, the two passes don't have an intermediate XML step, a DOM is passed straight from the first stylesheet to the second one. Using xsltproc, that is not the case: there is a temporary intermediate XML document stored in a file. Let's narrow down to the problem: > /=======================================================\ > test1.xml > This is applied to the above instance file. > \=======================================================/ > > xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > version="1.0" > > > > > > > RNG Form > > > > Here you are creating three nested elements: btest in no namespace, rngform in the http://simonwoodside.com/rng namespace, and (important) title in no namespace. Using the JC notation, that is: {}btest {http://simonwoodside.com/rng}rngform {}title When passing a DOM around, what I believe is the correct namespace information will be passed around. However when you save to an intermediate file you get this: > > > RNG Form > > As we can see, thanks to namespace defaulting, we now have: {}btest {http://simonwoodside.com/rng}rngform {http://simonwoodside.com/rng}}title Which is an entirely different document. Properly serialising that would have required libxml to add xmlns='' on title, except that's only possible starting with namespaces 1.1. Another option would have been to add a random prefix to rngform, but that wouldn't be nice. Unless I am solidly mistaken on how XSLT should treat namespace contexts in xsl:element, the bug is yours and the AxKit processing pipeline expresses the most logical output. IIRC xsl:element/@name takes a QName. You should thus be able to fix your bug with: RNG Form which should generate: RNG Form -- Robin Berjon Research Engineer, Expway http://expway.fr/ 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488 From veillard@redhat.com Thu Apr 3 04:35:48 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id E523318284 for ; Thu, 3 Apr 2003 04:35:47 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h339Zkh24386; Thu, 3 Apr 2003 04:35:46 -0500 Date: Thu, 3 Apr 2003 04:35:46 -0500 From: Daniel Veillard To: S Woodside Cc: xslt@gnome.org, axkit-users@axkit.org Subject: Re: [xslt] Re: more on the xslt namespace pipeline issue Message-ID: <20030403043546.S31240@redhat.com> References: <411C83E4-65A0-11D7-9A55-000393414368@yahoo.com> <3E8BFC51.9010100@expway.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3E8BFC51.9010100@expway.fr>; from robin.berjon@expway.fr on Thu, Apr 03, 2003 at 11:18:09AM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 03, 2003 at 11:18:09AM +0200, Robin Berjon wrote: > S Woodside wrote: > > Here's another go at the pipeline namespace problem. > > AxKit is 1.6.1 > > Using libxml 20425, libxslt 10019 and libexslt 710 Okay, I'm not happy at all !!! Very first thing to do is to UPGRADE :-(( Sorry, libxslt 10019 is from July 6 2002. Not taking the time to upgrade while it's explicitely asked for in the bug reporting page show no respects for the development and bug fixing efforts done. Why should I look at your report in more detail or try to reproduce the problem if you don't even do that basic step. If the bug was already fixed, how would you know ? Even if this is a problem in the current release you would have to upgrade anyway, so what ? Please have the basic courtesy to upgrade to the latest versions and report before asking for more help ! Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard@redhat.com Thu Apr 3 04:40:06 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id C669D18118 for ; Thu, 3 Apr 2003 04:40:05 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h339e5a25592; Thu, 3 Apr 2003 04:40:05 -0500 Date: Thu, 3 Apr 2003 04:40:05 -0500 From: Daniel Veillard To: xslt@gnome.org Cc: S Woodside , axkit-users@axkit.org Subject: Re: [xslt] Re: more on the xslt namespace pipeline issue Message-ID: <20030403044005.T31240@redhat.com> References: <411C83E4-65A0-11D7-9A55-000393414368@yahoo.com> <3E8BFC51.9010100@expway.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3E8BFC51.9010100@expway.fr>; from robin.berjon@expway.fr on Thu, Apr 03, 2003 at 11:18:09AM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 03, 2003 at 11:18:09AM +0200, Robin Berjon wrote: > Which is an entirely different document. Properly serialising that would have > required libxml to add xmlns='' on title, And I believe that had been fixed in the lasts releases, Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From sbwoodside@yahoo.com Thu Apr 3 16:49:27 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from tomts12-srv.bellnexxia.net (tomts12.bellnexxia.net [209.226.175.56]) by mail.gnome.org (Postfix) with ESMTP id 04E3818118 for ; Thu, 3 Apr 2003 16:49:27 -0500 (EST) Received: from yahoo.com ([65.93.181.251]) by tomts12-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20030403214925.ZOH20288.tomts12-srv.bellnexxia.net@yahoo.com>; Thu, 3 Apr 2003 16:49:25 -0500 Date: Thu, 3 Apr 2003 16:49:27 -0500 Subject: Re: [xslt] Re: more on the xslt namespace pipeline issue Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: xslt@gnome.org, axkit-users@axkit.org, Benjamin Reed To: veillard@redhat.com From: S Woodside In-Reply-To: <20030403043546.S31240@redhat.com> Message-Id: <243474A6-661E-11D7-9A55-000393414368@yahoo.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.551) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thursday, April 3, 2003, at 04:35 AM, Daniel Veillard wrote: >> S Woodside wrote: >>> Here's another go at the pipeline namespace problem. >>> AxKit is 1.6.1 >>> Using libxml 20425, libxslt 10019 and libexslt 710 > Okay, I'm not happy at all !!! Very first thing to do is to UPGRADE > :-(( Aeia! I am sorry. I guess that I am using the latest from the fink package system on Mac OS X but it is out of date. I see latest is 1.0.29 so I will download and install that manually ... Simon From sbwoodside@yahoo.com Fri Apr 4 01:19:11 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52]) by mail.gnome.org (Postfix) with ESMTP id 836F4181B5 for ; Fri, 4 Apr 2003 01:19:11 -0500 (EST) Received: from yahoo.com ([65.93.181.251]) by tomts8-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20030404061909.GUZJ18377.tomts8-srv.bellnexxia.net@yahoo.com>; Fri, 4 Apr 2003 01:19:09 -0500 Date: Fri, 4 Apr 2003 01:19:09 -0500 Subject: Re: [xslt] Re: more on the xslt namespace pipeline issue Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: xslt@gnome.org, axkit-users@axkit.org To: veillard@redhat.com From: S Woodside In-Reply-To: <20030403044005.T31240@redhat.com> Message-Id: <589BB218-6665-11D7-9DB7-000393414368@yahoo.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.551) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thursday, April 3, 2003, at 04:40 AM, Daniel Veillard wrote: > On Thu, Apr 03, 2003 at 11:18:09AM +0200, Robin Berjon wrote: >> Which is an entirely different document. Properly serialising that >> would have >> required libxml to add xmlns='' on title, > > And I believe that had been fixed in the lasts releases, OK -- I'm now running Using libxml 20506, libxslt 10027 and libexslt 718 xsltproc was compiled against libxml 20506, libxslt 10027 and libexslt 718 libxslt 10027 was compiled against libxml 20506 libexslt 718 was compiled against libxml 20506 from fink and the bug is still present. I'll install 1.0.29 next and see what happens with that. simon > > Daniel > > -- > Daniel Veillard | Red Hat Network https://rhn.redhat.com/ > veillard@redhat.com | libxml GNOME XML XSLT toolkit > http://xmlsoft.org/ > http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ > > -- www.simonwoodside.com -- 99% Devil, 1% Angel From jpesenti@yahoo.com Fri Apr 4 08:27:31 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from web12303.mail.yahoo.com (web12303.mail.yahoo.com [216.136.173.101]) by mail.gnome.org (Postfix) with SMTP id 7371B180EE for ; Fri, 4 Apr 2003 08:27:31 -0500 (EST) Message-ID: <20030404132731.3263.qmail@web12303.mail.yahoo.com> Received: from [12.101.25.68] by web12303.mail.yahoo.com via HTTP; Fri, 04 Apr 2003 05:27:31 PST Date: Fri, 4 Apr 2003 05:27:31 -0800 (PST) From: Jerome Pesenti To: xslt@gnome.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [xslt] Exslt support Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Is there an ongoing effort to implement the remaining exslt functionalities not yet supported? If so, is there a timeline? Can we help? Regards, Jerome __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com From veillard@redhat.com Fri Apr 4 08:45:12 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 6076B180EE for ; Fri, 4 Apr 2003 08:45:12 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h34DjBj29097 for xslt@gnome.org; Fri, 4 Apr 2003 08:45:11 -0500 Date: Fri, 4 Apr 2003 08:45:11 -0500 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Exslt support Message-ID: <20030404084511.I31240@redhat.com> References: <20030404132731.3263.qmail@web12303.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030404132731.3263.qmail@web12303.mail.yahoo.com>; from jpesenti@yahoo.com on Fri, Apr 04, 2003 at 05:27:31AM -0800 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 04, 2003 at 05:27:31AM -0800, Jerome Pesenti wrote: > Is there an ongoing effort to implement the > remaining exslt functionalities not yet supported? If > so, is there a timeline? Can we help? There is no clear effort toward completing them. So far people contributed pieces when they needed it and they were missing. I take patches :-) Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From jpesenti@yahoo.com Fri Apr 4 09:02:27 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from web12306.mail.yahoo.com (web12306.mail.yahoo.com [216.136.173.104]) by mail.gnome.org (Postfix) with SMTP id 108C918582 for ; Fri, 4 Apr 2003 09:02:27 -0500 (EST) Message-ID: <20030404140226.41974.qmail@web12306.mail.yahoo.com> Received: from [12.101.25.68] by web12306.mail.yahoo.com via HTTP; Fri, 04 Apr 2003 06:02:26 PST Date: Fri, 4 Apr 2003 06:02:26 -0800 (PST) From: Jerome Pesenti Subject: Re: [xslt] Exslt support To: xslt@gnome.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Daniel, Any suggestion/restriction on what regular expression package to use in order to implement the regex module of exslt? GNU regex is under the GPL but inside libc you can find it under the LGPL, which I assume would be fine.... Also, it seems that you developed your own regex package in order to support schemas, how does it compare to GNU regex? Thanks for you insight. Jerome __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com From veillard@redhat.com Fri Apr 4 09:28:05 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 41A151812E for ; Fri, 4 Apr 2003 09:28:05 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h34ES4j05900 for xslt@gnome.org; Fri, 4 Apr 2003 09:28:04 -0500 Date: Fri, 4 Apr 2003 09:28:04 -0500 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Exslt support Message-ID: <20030404092804.L31240@redhat.com> References: <20030404140226.41974.qmail@web12306.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030404140226.41974.qmail@web12306.mail.yahoo.com>; from jpesenti@yahoo.com on Fri, Apr 04, 2003 at 06:02:26AM -0800 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 04, 2003 at 06:02:26AM -0800, Jerome Pesenti wrote: > Daniel, > Any suggestion/restriction on what regular expression > package to use in order to implement the regex module > of exslt? GNU regex is under the GPL but inside libc > you can find it under the LGPL, which I assume would > be fine.... Also, it seems that you developed your own > regex package in order to support schemas, how does it > compare to GNU regex? that it's part of libxml2 so the regexp to use. Its definition is at file:///u/veillard/Schemas/xmlschema-2.html#regexs I hope this match with EXSLT, if not feedback should be given to EXSLT so that they use XML releated regexps. I will not embed GNU regex, I do not want to depend on external libraries, especially when Licences are different from libxml2/libxslt ones. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard@redhat.com Fri Apr 4 10:00:39 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id A07F8180EE for ; Fri, 4 Apr 2003 10:00:39 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h34F0aj13548 for xslt@gnome.org; Fri, 4 Apr 2003 10:00:36 -0500 Date: Fri, 4 Apr 2003 10:00:36 -0500 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Exslt support Message-ID: <20030404100036.M31240@redhat.com> References: <20030404140226.41974.qmail@web12306.mail.yahoo.com> <20030404092804.L31240@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030404092804.L31240@redhat.com>; from veillard@redhat.com on Fri, Apr 04, 2003 at 09:28:04AM -0500 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 04, 2003 at 09:28:04AM -0500, Daniel Veillard wrote: > On Fri, Apr 04, 2003 at 06:02:26AM -0800, Jerome Pesenti wrote: > > Daniel, > > Any suggestion/restriction on what regular expression > > package to use in order to implement the regex module > > of exslt? GNU regex is under the GPL but inside libc > > you can find it under the LGPL, which I assume would > > be fine.... Also, it seems that you developed your own > > regex package in order to support schemas, how does it > > compare to GNU regex? > > that it's part of libxml2 so the regexp to use. Its > definition is at file:///u/veillard/Schemas/xmlschema-2.html#regexs oops http://www.w3.org/TR/xmlschema-2/#regexs > I hope this match with EXSLT, if not feedback should be given to EXSLT > so that they use XML releated regexps. > I will not embed GNU regex, I do not want to depend on external > libraries, especially when Licences are different from libxml2/libxslt > ones. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From sbwoodside@yahoo.com Fri Apr 4 22:22:13 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from tomts15-srv.bellnexxia.net (tomts15-srv.bellnexxia.net [209.226.175.3]) by mail.gnome.org (Postfix) with ESMTP id B7CD6180DD for ; Fri, 4 Apr 2003 22:22:13 -0500 (EST) Received: from yahoo.com ([65.93.190.206]) by tomts15-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20030405032212.MZLO21409.tomts15-srv.bellnexxia.net@yahoo.com>; Fri, 4 Apr 2003 22:22:12 -0500 Date: Fri, 4 Apr 2003 22:22:11 -0500 Subject: Re: [xslt] Re: more on the xslt namespace pipeline issue Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: S Woodside To: axkit-users@axkit.org, xslt@gnome.org Content-Transfer-Encoding: 7bit In-Reply-To: <3E8E1498.70603@befunk.com> Message-Id: X-Mailer: Apple Mail (2.551) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: I have now updated to 1.0.29 of libxslt and the testcase I posted earlier is working now. Daniel, sorry about wasting your time. Robin Berjon wrote: > When passing a DOM around, what I believe is the correct namespace > information will be passed around. However when you save to an > intermediate file you get this: > > > > RNG Form > > Now I am very confused about this difference between the DOM and the serialized output. I have never used DOM. Now I am running: Using libxml 20506, libxslt 10029 and libexslt 719 % xsltproc a_instance.xml RNG Form > As we can see, thanks to namespace defaulting, we now have: > > {}btest > {http://simonwoodside.com/rng}rngform > {http://simonwoodside.com/rng}}title After reading http://www.jclark.com/xml/xmlns.htm it seems to me that this is correct! Is there some difference between the inheritance of an unprefixed name in input from a file as opposed to in output of a DOM? > Which is an entirely different document. Properly serialising that > would have required libxml to add xmlns='' on title, except that's > only possible starting with namespaces 1.1. Another option would have > been to add a random prefix to rngform, but that wouldn't be nice. I can see now that adding the xmlns='' on title in the trace file gives the same behaviour as AxKit uses internally, but 1) It is still different than the latest xsltproc's output 2) It seems to me that according to the rules of XSLT it is incorrect (after re-reading the entire XSLT FAQ section on namespaces, I do not see how this can be correct). > Unless I am solidly mistaken on how XSLT should treat namespace > contexts in xsl:element, the bug is yours and the AxKit processing > pipeline expresses the most logical output. It seems clear to me that on reading input files, the elements should inherit an unprefixed namespace in XSLT ... and this is how AxKit behaves in the first stage of the pipeline. Why should the rules change in the intermediate stages? I am looking at this from a black-box perspective, it seems to me that the results of the pipeline should be exactly the same as the results of manually pipelining it, using xsltproc. My head hurts from this stuff. Simon From veillard@redhat.com Sat Apr 5 01:55:02 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id A438D18184 for ; Sat, 5 Apr 2003 01:55:02 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h356t2h18109; Sat, 5 Apr 2003 01:55:02 -0500 Date: Sat, 5 Apr 2003 01:55:02 -0500 From: Daniel Veillard To: xslt@gnome.org Cc: axkit-users@axkit.org Subject: Re: [xslt] Re: more on the xslt namespace pipeline issue Message-ID: <20030405015502.R31240@redhat.com> References: <3E8E1498.70603@befunk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from sbwoodside@yahoo.com on Fri, Apr 04, 2003 at 10:22:11PM -0500 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 04, 2003 at 10:22:11PM -0500, S Woodside wrote: > I have now updated to 1.0.29 of libxslt and the testcase I posted > earlier is working now. Daniel, sorry about wasting your time. okay, good to know it was actually fixed :-) Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From junkaddr@hotmail.com Sat Apr 5 23:41:13 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from hotmail.com (f123.law11.hotmail.com [64.4.17.123]) by mail.gnome.org (Postfix) with ESMTP id 9785D180F2 for ; Sat, 5 Apr 2003 23:41:12 -0500 (EST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 5 Apr 2003 20:41:11 -0800 Received: from 205.221.183.76 by lw11fd.law11.hotmail.msn.com with HTTP; Sun, 06 Apr 2003 04:41:11 GMT X-Originating-IP: [205.221.183.76] X-Originating-Email: [junkaddr@hotmail.com] From: "Brett Kail" To: xslt@gnome.org Date: Sat, 05 Apr 2003 22:41:11 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 06 Apr 2003 04:41:11.0481 (UTC) FILETIME=[BF993290:01C2FBF6] Subject: [xslt] func:result not recognized Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hello, I'm attempting to use , but it seems that is not being recognized. Given the following... ...xsltproc says: ELEMENT fake PBM: Node has no parent ELEMENT func:result namespace func href=http://exslt.org/functions namespace my href=my ATTRIBUTE select TEXT content=1 ELEMENT more namespace my href=my namespace func href=http://exslt.org/functions {my}func: cannot write to result tree while executing a function xmlXPathCompiledEval: evaluation failed runtime error: file test.xslt line 14 element value-of xsltValueOf: text copy failed It seems that is not being recognized, but I do not know why. xsltproc --dumpextensions says: [...] Registered Extension Elements: {http://exslt.org/common}document {http://exslt.org/functions}result {http://xmlsoft.org/XSLT/}test ...so it appears that the extensions are being registered. Does anyone know why this might be failing? Thanks, -Brett _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From gregor@focusresearch.com Sun Apr 6 08:22:18 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from domino1.kennedytech.com (unknown [63.69.80.18]) by mail.gnome.org (Postfix) with ESMTP id 80C36181E6 for ; Sun, 6 Apr 2003 08:22:17 -0400 (EDT) To: xslt@gnome.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 From: gregor@focusresearch.com Message-ID: Date: Sun, 6 Apr 2003 08:18:08 -0400 X-MIMETrack: Serialize by Router on Domino1/KTC(Release 5.0.10 |March 22, 2002) at 04/06/2003 08:18:09 AM Content-Type: multipart/mixed; boundary="=_mixed 0043F02285256D00_=" Subject: [xslt] Possible namespace-related bug in xsltproc Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: --=_mixed 0043F02285256D00_= Content-Type: text/plain; charset="us-ascii" [[ Moderator -- I posted this last night but it got queued. I've joined the list, so I'm reposting myself rather than waiting for it to go through your queue. I hope that is OK. ]] I've been tinkering with using xsltproc to apply XSL templates to modify SVG images produced by Sodipodi. I've been battling with behavior that I thought was due to mistakes made by me. Since that didn't lead to resolution, I entertained the possibility that xsltproc could have a problem. I've found that for an SVG document with a default namespace declaration in the root element, I have to run in --novalid mode, and I have to remove the xmlns="..." attribute from the root element to get even a simple XSL stylesheet to apply the way I think it should. I've distilled this down to a simple example, which I'll attach here. The tarball below contains a Makefile and a README that shows the output I get when running the Makefile. Also included is a simple SVG file with (bad.svg) and without (better.svg) the problem xmlns attribute. The same example.xsl file is used for all four tests (with and without --novalid for bad.svg and better.svg). Note that the example.xsl file contains xmlns attributes in its root element, as I've heard is required for proper execution of XSLT against XML with namespaces. Can any of you shed some light on this one for me? Does this fail with your setup, too? Have I committed any misdemeanors in the XSLT? Or, is there a namespace-related bug in xsltproc to which I'm falling victim? Regards, -- Gregor Purdy --=_mixed 0043F02285256D00_= Content-Type: application/octet-stream; name="bug.tar.gz" Content-Disposition: attachment; filename="bug.tar.gz" Content-Transfer-Encoding: base64 H4sIAFFgjz4AA+1ZWW/bRhD2a/grJmwBxal56YwVS61rO4kB50CstimKPlDkUiRMLgnuUrL66zuz PCRflZPGLtpqYFnmcnbu+WZJT4uZtfPAZNtdezDo4bdtD/rdK98V7dBCp9+3HXuwYztO2+nvQO+h DSMqhHRzgJ1ZzmZpfjffpvv/Uppi/vFjivnswXRgUu3+tbyv5d8ZdPpV/nu9QRdrwWn32oMdsB/M ojX6n+f/4PvLJIY5y0WU8pHumLYOjHupH/HZSP9p8sp4oQOGiPtunHI20nmqfz/WDp4evz+a/Prh BLBw4MNPP56dHoFuWNYvnSPLOp4cw/nPr6GNybX37a5lnbzTNT2UMhta1mKxMBcdM81n1uSjRTzW x5MjAzcYzQaUYKFkxzZ96evabxocPD2cTM5OzyekUQNAs7kYXsYRv4Cj48PJIXzz6vTTyTHcosbZ 39+3FKs+1n4n6w0DjnLmSubDIpIhnKPDGX7g2fp2Ua2aXppY+i4YBu4t1UPkj3RloaPTZc06bEJp mx3HLG8qW0e3GIb+2uTnimtYC2rYGyNEWuQeC3AfMzmTZYyqm0YVKLgSmNtUrsWCuBeRL8OR3nbs JFELIYtmocSV/UG10rjmp97UFVgDVpgmzCo7wrrBw93kOs8aymAGAA58FgjaV8aRrhy7o4OlbjbC SJI/j9hixUoG6OXlLI98kbkeVuqSwu3s91/0In7z7uXNuyJMF8Qx0mVesEoxqs6ZJ0sO5JHLGB0J Ui4NEf3Bhk77ZRDF8fCbAMm21YWRkg65HNpmb99pd51yNS9iNmRzxlPffylknl4wQ4V66GTypV6r IANIpePYzVqdkc7A7DWLTVZWfOhVd8WAEXAGttl9MVDOHFBVjbXN/U+Z+XhyePz25OEwZgP+d3pd p5n/9kDhv43HhS3+PwKVuQdEFYij6aWIJeg/FjMdTi7dJIuZhhDVMeyuYfe01yoE8M6ED0XuL+Gg jMkPQeoVImeCubkXElaONW0SRgLwxwWfJSnHFnAlwiKkAS5h0YFSmESyWa7UZ3nq7Wl4F5eSJRTc R0Cl+YONTGvYuCBDtqQWLmKE7zS/MEkfg4hnhVSDB3uQwcIVgNL8wruO8nuA8kgKfDo/m2iKW9kq ZJFFPrDS9z3FkvJ4CVmRZ6lgZMAijLyQ2GWqofg5trbim7LQnUdoOGELx47NWakVxUYkrgQUETIm zSpAIZo4ZYyDZKKZRVUgDJzFiFr4lWcJPAvyNIGPyPPGldpZxItLeGHau6Ur61vaV7fkRVCICvz3 MM8YUG0euYAcQcT9XTTlMJAsR6cxR56kMEuyDXHtwp1hEPKCQytxL1gLXYYZ4wxzWfqcFhJDrlH1 0GUVN2HCe07JS1wvjDiKUMFAmYvQleh0ljEcURpi17dAgmmcV6mvZZi4ANXIgLH6C5WtMxoGT+du vErXzS01x/WtVzYwid7Xe8qL+2m6ufGKviqsflpGlIE7TecYC4yLYFhngB1TxBK7hNfuQZymF8Qe RxgUygIGaQy3nNHwCDYG/Gk+9FvTnpEeNcTGwGKWMC4p7DyVGGfphQzzDYfc37seHTzz+QKKTFu3 ADZZcIcBAsc2dd4ULQCscFXVlYukGW2SVFUCAhfLPt+t+rcOCDZZIciItRBHCCHM9elenWKULOuu LxWrVvWjIMBy456qOFrOCJvoGsvUnVZ/BgqaAhc1anTOoLMCwxUvdmuo4mo3HfiaaO6q7l6rkzpl 2r0CVkZq9Ut9YdSExEODSpNHaaor5momn2LuzrFH+YzFy73bSu65nzLxvJRxi4DPtuzN4Zun5S1N O5VYtiwRIEoTUD72stLtKtDA4JIDC4XKnlsgWtapkOtAIQpPYWIDhvAdfHp7Bjg3phEvQ69SGwms i1cVtMgwZwzFCibKRir1B24UEypVOK9YfSaiHIGyKietxOOozGaMFafE7MFpK1EWuws3LwuCL5EN g4oFs5pLhFkazQkqJ1FkNAd80umnpQ2VxzjkIpxVpCXBq5xCjw780wN+A9H57y1CMM3Ah9Kx4fyH Z736/U+v7/QdOv/1++3t+e8xqILAYTOCrg+GNai7bchV24a3DWHtyT2nunZN6SZpnzv6tZUTwztm +F223nE60G7G4h6Sv/Ag4cXM5UPtSZ6AEXxhou7Kv3oybwx4mBrb9P6vP1j1v93uI3+n3dn2/6PQ 9v3fY73/277Z277Ze8w3e/cjyt/aMPpaYq/QxvNft736/89A4X+37Wzx/zHor/G/kAHiP+E91sZw 7ZGt3tDCDa3P/RcHyhq17sAvfNCyJviAKRANk9bno95XgNqxVrorGXYFvelSr05GLaulMIxuuVkW L42aQai2XN9ylwiMw98XQrCCUtTD+c0d1tVMfT2k2NKWtrSlLW1pS/8V+hN3iB20ACgAAA== --=_mixed 0043F02285256D00_=-- From cbozeman@hiwaay.net Sun Apr 6 09:20:27 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.hiwaay.net (ant.hiwaay.net [216.180.54.10]) by mail.gnome.org (Postfix) with ESMTP id 2BD7318506 for ; Sun, 6 Apr 2003 09:20:27 -0400 (EDT) Received: from tnt6-216-180-4-186.dialup.hiwaay.net (tnt6-216-180-4-186.dialup.hiwaay.net [216.180.4.186]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h36DKPYb995644 for ; Sun, 6 Apr 2003 08:20:25 -0500 (CDT) Subject: Re: [xslt] Possible namespace-related bug in xsltproc From: Charles Bozeman To: xslt@gnome.org In-Reply-To: References: Content-Type: text/plain Organization: Message-Id: <1049635235.1061.17.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 06 Apr 2003 07:20:35 -0600 Content-Transfer-Encoding: 7bit Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: xsltproc is working like it is supposed to. The bug.svg file has a default namespace but your stylesheet does not handle the default namespace. replace lines: xmlns="http://www.w3.org/2000/svg" with xmlns:s="http://www.w3.org/2000/svg" to get the stylesheet to work on bug.svg BTW, this is the type of question you should ask on the XSL-list. Daniel states this on the libxslt webpages (http://xmlsoft.org/XSLT/bugs.html). On Sun, 2003-04-06 at 06:18, gregor@focusresearch.com wrote: > [[ Moderator -- I posted this last night but it got queued. I've > joined the list, so I'm reposting myself rather than waiting for > it to go through your queue. I hope that is OK. ]] > > I've been tinkering with using xsltproc to apply XSL templates > to modify SVG images produced by Sodipodi. > > I've been battling with behavior that I thought was due to > mistakes made by me. Since that didn't lead to resolution, > I entertained the possibility that xsltproc could have a > problem. > > I've found that for an SVG document with a default namespace > declaration in the root element, I have to run in --novalid > mode, and I have to remove the xmlns="..." attribute from the > root element to get even a simple XSL stylesheet to > apply the way I think it should. > > I've distilled this down to a simple example, which I'll attach here. > The tarball below contains a Makefile and a README that > shows the output I get when running the Makefile. Also included > is a simple SVG file with (bad.svg) and without (better.svg) the > problem xmlns attribute. The same example.xsl file is used for > all four tests (with and without --novalid for bad.svg and better.svg). > Note that the example.xsl file contains xmlns attributes in its root > element, as I've heard is required for proper execution of XSLT > against XML with namespaces. > > Can any of you shed some light on this one for me? Does this > fail with your setup, too? Have I committed any misdemeanors > in the XSLT? Or, is there a namespace-related bug in xsltproc > to which I'm falling victim? > > > > > Regards, > > -- Gregor Purdy -- Charles Bozeman From gregor@focusresearch.com Sun Apr 6 09:34:50 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from domino1.kennedytech.com (unknown [63.69.80.18]) by mail.gnome.org (Postfix) with ESMTP id D8ABC184AE for ; Sun, 6 Apr 2003 09:34:49 -0400 (EDT) To: Charles Bozeman Cc: xslt@gnome.org Subject: Re: [xslt] Possible namespace-related bug in xsltproc MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 From: gregor@focusresearch.com Message-ID: Date: Sun, 6 Apr 2003 09:30:46 -0400 X-MIMETrack: Serialize by Router on Domino1/KTC(Release 5.0.10 |March 22, 2002) at 04/06/2003 09:30:41 AM, Serialize complete at 04/06/2003 09:30:41 AM Content-Type: text/plain; charset="us-ascii" Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Charles -- Thanks for the pointer. Now 3 cases work and 1 case fails, the opposite of the prior behavior (better-novalid.out is the one that fails to print "HAH!" now). I'll go work with my original stuff some more to see if that helps enough to let me move on. The reason I thought to post to this list was that the behavior was inconsistent (--novalid affects the output), which it seems to me shouldn't be the case... Regards, -- Gregor Purdy Charles Bozeman Sent by: xslt-admin@gnome.org 04/06/2003 09:20 AM Please respond to xslt To: xslt@gnome.org cc: Subject: Re: [xslt] Possible namespace-related bug in xsltproc xsltproc is working like it is supposed to. The bug.svg file has a default namespace but your stylesheet does not handle the default namespace. replace lines: xmlns="http://www.w3.org/2000/svg" with xmlns:s="http://www.w3.org/2000/svg" to get the stylesheet to work on bug.svg BTW, this is the type of question you should ask on the XSL-list. Daniel states this on the libxslt webpages (http://xmlsoft.org/XSLT/bugs.html). On Sun, 2003-04-06 at 06:18, gregor@focusresearch.com wrote: > [[ Moderator -- I posted this last night but it got queued. I've > joined the list, so I'm reposting myself rather than waiting for > it to go through your queue. I hope that is OK. ]] > > I've been tinkering with using xsltproc to apply XSL templates > to modify SVG images produced by Sodipodi. > > I've been battling with behavior that I thought was due to > mistakes made by me. Since that didn't lead to resolution, > I entertained the possibility that xsltproc could have a > problem. > > I've found that for an SVG document with a default namespace > declaration in the root element, I have to run in --novalid > mode, and I have to remove the xmlns="..." attribute from the > root element to get even a simple XSL stylesheet to > apply the way I think it should. > > I've distilled this down to a simple example, which I'll attach here. > The tarball below contains a Makefile and a README that > shows the output I get when running the Makefile. Also included > is a simple SVG file with (bad.svg) and without (better.svg) the > problem xmlns attribute. The same example.xsl file is used for > all four tests (with and without --novalid for bad.svg and better.svg). > Note that the example.xsl file contains xmlns attributes in its root > element, as I've heard is required for proper execution of XSLT > against XML with namespaces. > > Can any of you shed some light on this one for me? Does this > fail with your setup, too? Have I committed any misdemeanors > in the XSLT? Or, is there a namespace-related bug in xsltproc > to which I'm falling victim? > > > > > Regards, > > -- Gregor Purdy -- Charles Bozeman _______________________________________________ xslt mailing list, project page http://xmlsoft.org/XSLT/ xslt@gnome.org http://mail.gnome.org/mailman/listinfo/xslt From gpurdy@kennedytech.com Sat Apr 5 18:14:45 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from domino1.kennedytech.com (unknown [63.69.80.18]) by mail.gnome.org (Postfix) with ESMTP id E689818143 for ; Sat, 5 Apr 2003 18:14:44 -0500 (EST) To: xslt@gnome.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 From: gpurdy@kennedytech.com Message-ID: Date: Sat, 5 Apr 2003 18:10:39 -0500 X-MIMETrack: Serialize by Router on Domino1/KTC(Release 5.0.10 |March 22, 2002) at 04/05/2003 06:10:41 PM Content-Type: multipart/mixed; boundary="=_mixed 007FAC2585256CFF_=" Subject: [xslt] Possible namespace-related bug in xsltproc Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: --=_mixed 007FAC2585256CFF_= Content-Type: text/plain; charset="us-ascii" I've been tinkering with using xsltproc to apply XSL templates to modify SVG images produced by Sodipodi. I've been battling with behavior that I thought was due to mistakes made by me. Since that didn't lead to resolution, I entertained the possibility that xsltproc could have a problem. I've found that for an SVG document with a default namespace declaration in the root element, I have to run in --novalid mode, and I have to remove the xmlns="..." attribute from the root element to get even a simple XSL stylesheet to apply the way I think it should. I've distilled this down to a simple example, which I'll attach here. The tarball below contains a Makefile and a README that shows the output I get when running the Makefile. Also included is a simple SVG file with (bad.svg) and without (better.svg) the problem xmlns attribute. The same example.xsl file is used for all four tests (with and without --novalid for bad.svg and better.svg). Note that the example.xsl file contains xmlns attributes in its root element, as I've heard is required for proper execution of XSLT against XML with namespaces. Can any of you shed some light on this one for me? Does this fail with your setup, too? Have I committed any misdemeanors in the XSLT? Or, is there a namespace-related bug in xsltproc to which I'm falling victim? Regards, -- Gregor Purdy --=_mixed 007FAC2585256CFF_= Content-Type: application/octet-stream; name="bug.tar.gz" Content-Disposition: attachment; filename="bug.tar.gz" Content-Transfer-Encoding: base64 H4sIAFFgjz4AA+1ZWW/bRhD2a/grJmwBxal56YwVS61rO4kB50CstimKPlDkUiRMLgnuUrL66zuz PCRflZPGLtpqYFnmcnbu+WZJT4uZtfPAZNtdezDo4bdtD/rdK98V7dBCp9+3HXuwYztO2+nvQO+h DSMqhHRzgJ1ZzmZpfjffpvv/Uppi/vFjivnswXRgUu3+tbyv5d8ZdPpV/nu9QRdrwWn32oMdsB/M ojX6n+f/4PvLJIY5y0WU8pHumLYOjHupH/HZSP9p8sp4oQOGiPtunHI20nmqfz/WDp4evz+a/Prh BLBw4MNPP56dHoFuWNYvnSPLOp4cw/nPr6GNybX37a5lnbzTNT2UMhta1mKxMBcdM81n1uSjRTzW x5MjAzcYzQaUYKFkxzZ96evabxocPD2cTM5OzyekUQNAs7kYXsYRv4Cj48PJIXzz6vTTyTHcosbZ 39+3FKs+1n4n6w0DjnLmSubDIpIhnKPDGX7g2fp2Ua2aXppY+i4YBu4t1UPkj3RloaPTZc06bEJp mx3HLG8qW0e3GIb+2uTnimtYC2rYGyNEWuQeC3AfMzmTZYyqm0YVKLgSmNtUrsWCuBeRL8OR3nbs JFELIYtmocSV/UG10rjmp97UFVgDVpgmzCo7wrrBw93kOs8aymAGAA58FgjaV8aRrhy7o4OlbjbC SJI/j9hixUoG6OXlLI98kbkeVuqSwu3s91/0In7z7uXNuyJMF8Qx0mVesEoxqs6ZJ0sO5JHLGB0J Ui4NEf3Bhk77ZRDF8fCbAMm21YWRkg65HNpmb99pd51yNS9iNmRzxlPffylknl4wQ4V66GTypV6r IANIpePYzVqdkc7A7DWLTVZWfOhVd8WAEXAGttl9MVDOHFBVjbXN/U+Z+XhyePz25OEwZgP+d3pd p5n/9kDhv43HhS3+PwKVuQdEFYij6aWIJeg/FjMdTi7dJIuZhhDVMeyuYfe01yoE8M6ED0XuL+Gg jMkPQeoVImeCubkXElaONW0SRgLwxwWfJSnHFnAlwiKkAS5h0YFSmESyWa7UZ3nq7Wl4F5eSJRTc R0Cl+YONTGvYuCBDtqQWLmKE7zS/MEkfg4hnhVSDB3uQwcIVgNL8wruO8nuA8kgKfDo/m2iKW9kq ZJFFPrDS9z3FkvJ4CVmRZ6lgZMAijLyQ2GWqofg5trbim7LQnUdoOGELx47NWakVxUYkrgQUETIm zSpAIZo4ZYyDZKKZRVUgDJzFiFr4lWcJPAvyNIGPyPPGldpZxItLeGHau6Ur61vaV7fkRVCICvz3 MM8YUG0euYAcQcT9XTTlMJAsR6cxR56kMEuyDXHtwp1hEPKCQytxL1gLXYYZ4wxzWfqcFhJDrlH1 0GUVN2HCe07JS1wvjDiKUMFAmYvQleh0ljEcURpi17dAgmmcV6mvZZi4ANXIgLH6C5WtMxoGT+du vErXzS01x/WtVzYwid7Xe8qL+2m6ufGKviqsflpGlIE7TecYC4yLYFhngB1TxBK7hNfuQZymF8Qe RxgUygIGaQy3nNHwCDYG/Gk+9FvTnpEeNcTGwGKWMC4p7DyVGGfphQzzDYfc37seHTzz+QKKTFu3 ADZZcIcBAsc2dd4ULQCscFXVlYukGW2SVFUCAhfLPt+t+rcOCDZZIciItRBHCCHM9elenWKULOuu LxWrVvWjIMBy456qOFrOCJvoGsvUnVZ/BgqaAhc1anTOoLMCwxUvdmuo4mo3HfiaaO6q7l6rkzpl 2r0CVkZq9Ut9YdSExEODSpNHaaor5momn2LuzrFH+YzFy73bSu65nzLxvJRxi4DPtuzN4Zun5S1N O5VYtiwRIEoTUD72stLtKtDA4JIDC4XKnlsgWtapkOtAIQpPYWIDhvAdfHp7Bjg3phEvQ69SGwms i1cVtMgwZwzFCibKRir1B24UEypVOK9YfSaiHIGyKietxOOozGaMFafE7MFpK1EWuws3LwuCL5EN g4oFs5pLhFkazQkqJ1FkNAd80umnpQ2VxzjkIpxVpCXBq5xCjw780wN+A9H57y1CMM3Ah9Kx4fyH Z736/U+v7/QdOv/1++3t+e8xqILAYTOCrg+GNai7bchV24a3DWHtyT2nunZN6SZpnzv6tZUTwztm +F223nE60G7G4h6Sv/Ag4cXM5UPtSZ6AEXxhou7Kv3oybwx4mBrb9P6vP1j1v93uI3+n3dn2/6PQ 9v3fY73/277Z277Ze8w3e/cjyt/aMPpaYq/QxvNft736/89A4X+37Wzx/zHor/G/kAHiP+E91sZw 7ZGt3tDCDa3P/RcHyhq17sAvfNCyJviAKRANk9bno95XgNqxVrorGXYFvelSr05GLaulMIxuuVkW L42aQai2XN9ylwiMw98XQrCCUtTD+c0d1tVMfT2k2NKWtrSlLW1pS/8V+hN3iB20ACgAAA== --=_mixed 007FAC2585256CFF_=-- From veillard@redhat.com Sun Apr 6 12:23:17 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 5BB6618108 for ; Sun, 6 Apr 2003 12:23:17 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h36GNF826116; Sun, 6 Apr 2003 12:23:15 -0400 Date: Sun, 6 Apr 2003 12:23:15 -0400 From: Daniel Veillard To: gpurdy@kennedytech.com Cc: xslt@gnome.org Subject: Re: [xslt] Possible namespace-related bug in xsltproc Message-ID: <20030406122315.B3563@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from gpurdy@kennedytech.com on Sat, Apr 05, 2003 at 06:10:39PM -0500 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Sat, Apr 05, 2003 at 06:10:39PM -0500, gpurdy@kennedytech.com wrote: > Can any of you shed some light on this one for me? Does this > fail with your setup, too? Have I committed any misdemeanors > in the XSLT? Or, is there a namespace-related bug in xsltproc > to which I'm falling victim? I bet your main problem is that you don't understand the XPath/XSLT spec. the SVG elements are in the SVG namespace. and the XPath expression "svg" will NOT match element of name svg but in a namespace. Check the archives of the list for explanations and workaround, this has been explained many time... Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard@redhat.com Sun Apr 6 12:25:52 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 5B7AF18112 for ; Sun, 6 Apr 2003 12:25:52 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h36GPqW26546 for xslt@gnome.org; Sun, 6 Apr 2003 12:25:52 -0400 Date: Sun, 6 Apr 2003 12:25:52 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] func:result not recognized Message-ID: <20030406122552.C3563@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from junkaddr@hotmail.com on Sat, Apr 05, 2003 at 10:41:11PM -0600 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Sat, Apr 05, 2003 at 10:41:11PM -0600, Brett Kail wrote: > Hello, > > I'm attempting to use , but it seems that is > not being recognized. What about reading the regression tests for this functionality ? tests/exslt/functions/function.1.xsl Cut and paste is not hard and avoid mistakes (extension-element-prefixes) Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard@redhat.com Sun Apr 6 12:28:08 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id C8550184AE for ; Sun, 6 Apr 2003 12:28:08 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h36GS8n26888; Sun, 6 Apr 2003 12:28:08 -0400 Date: Sun, 6 Apr 2003 12:28:08 -0400 From: Daniel Veillard To: xslt@gnome.org Cc: Charles Bozeman Subject: Re: [xslt] Possible namespace-related bug in xsltproc Message-ID: <20030406122808.D3563@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from gregor@focusresearch.com on Sun, Apr 06, 2003 at 09:30:46AM -0400 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Sun, Apr 06, 2003 at 09:30:46AM -0400, gregor@focusresearch.com wrote: > The reason I thought to post to this list was that the behavior was > inconsistent (--novalid affects the output), which it seems to me > shouldn't be the case... paphio:~/XSLT -> xsltproc | grep novalid --novalid skip the Dtd loading phase paphio:~/XSLT -> If you ask the processor to not read the DTD, then the namespace declaration inherited from the DTD will not be found. You asked for a non-conformant behaviour, you get it ! Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From sbwoodside@yahoo.com Mon Apr 7 00:11:33 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52]) by mail.gnome.org (Postfix) with ESMTP id 6B096180F7 for ; Mon, 7 Apr 2003 00:11:33 -0400 (EDT) Received: from yahoo.com ([65.93.189.238]) by tomts8-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20030407041131.BSWN18377.tomts8-srv.bellnexxia.net@yahoo.com>; Mon, 7 Apr 2003 00:11:31 -0400 Date: Mon, 7 Apr 2003 00:11:32 -0400 Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: xslt@gnome.org To: axkit-users@axkit.org From: S Woodside Content-Transfer-Encoding: 7bit Message-Id: <03CAF304-68AF-11D7-9E19-000393414368@yahoo.com> X-Mailer: Apple Mail (2.551) Subject: [xslt] Fwd: FYI: local install of XML::LibXML and XML::LibXSLT Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Whoops, wrong mail address again (OS X). A little more detail .. the problem with XML::LibXML not detecting the library was the same problem with xsubpp although it took a while to figure that out. The Makefile.PL generated a Conftest.PL type test to see if the library was available. Makefile.PL generated a Makefile with the hard-coded path in it, which is why I said it was a MakeMaker problem. changing to this XSUBPPDIR = /home/simon/local/share/perl/5.6.1/ExtUtils made the problem go away. Simon Begin forwarded message: > From: Simon Woodside > Date: Sun Apr 6, 2003 11:36:03 PM America/Montreal > To: axkit-users@axkit.org > Cc: xslt@gnome.org > Subject: FYI: local install of XML::LibXML > > FYI > > I installed XML::LibXML locally (without root) into a situation where > my libxml2 was also installed locally. I was having trouble with it > not detecting the installed library that I eventually resolved by > commenting out the tests in Makefile.PL > > I had > PERL5LIB=/home/simon/local/lib/perl/5.6.1:/home/simon/local/share/ > perl/5.6.1 > > and I ran perl Makefile.PL PREFIX=/home/simon/local > > Then running make gave the following error: > make: *** No rule to make target > `/usr/share/perl/5.6.1/ExtUtils/xsubpp', needed by `LibXML.c'. Stop. > > This is a problem (I guess) with MakeMaker not applying the proper > prefix to find xsubpp (which is installed in > /home/simon/local/share/perl/5.6.1/ExtUtils/) I hacked the Makefile to > manually change the path. > > simon > > -- anti-spam: do not post that address publicly www.simonwoodside.com -- 99% Devil, 1% Angel From junkaddr@hotmail.com Mon Apr 7 08:27:23 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from hotmail.com (f64.law11.hotmail.com [64.4.17.64]) by mail.gnome.org (Postfix) with ESMTP id 3577C18527 for ; Mon, 7 Apr 2003 08:27:23 -0400 (EDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 7 Apr 2003 05:27:22 -0700 Received: from 205.221.183.76 by lw11fd.law11.hotmail.msn.com with HTTP; Mon, 07 Apr 2003 12:27:22 GMT X-Originating-IP: [205.221.183.76] X-Originating-Email: [junkaddr@hotmail.com] From: "Brett Kail" To: xslt@gnome.org Subject: Re: [xslt] func:result not recognized Date: Mon, 07 Apr 2003 07:27:22 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 07 Apr 2003 12:27:22.0366 (UTC) FILETIME=[09F549E0:01C2FD01] Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hello, > What about reading the regression tests for this functionality ? I'm not all that familiar with the libxslt source (yet! :)), and it did not occur to me that there would be regression tests for the exslt implementations. Many thanks for your patience; I now see my error :). -Brett _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus From veillard@redhat.com Mon Apr 7 08:49:42 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 3C23218518 for ; Mon, 7 Apr 2003 08:49:42 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h37Cnfi30521 for xslt@gnome.org; Mon, 7 Apr 2003 08:49:41 -0400 Date: Mon, 7 Apr 2003 08:49:41 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] func:result not recognized Message-ID: <20030407084941.F29447@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from junkaddr@hotmail.com on Mon, Apr 07, 2003 at 07:27:22AM -0500 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Apr 07, 2003 at 07:27:22AM -0500, Brett Kail wrote: > Hello, > > > What about reading the regression tests for this functionality ? > > I'm not all that familiar with the libxslt source (yet! :)), and it did not > occur to me that there would be regression tests for the exslt > implementations. Well Charles Bozeman provided them IIRC! Even I can't remember all the syntax, it's easier to start from working examples for me ... Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From cbozeman@hiwaay.net Mon Apr 7 09:48:30 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.hiwaay.net (ant.hiwaay.net [216.180.54.10]) by mail.gnome.org (Postfix) with ESMTP id CD436183B6 for ; Mon, 7 Apr 2003 09:48:29 -0400 (EDT) Received: from ant.hiwaay.net (ant.hiwaay.net [216.180.54.10]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h37DmTYb927610 for ; Mon, 7 Apr 2003 08:48:29 -0500 (CDT) Received: (from httpd@localhost) by ant.hiwaay.net (8.12.9/8.12.9/DefSubmit) id h37DmSFc925120 for xslt@gnome.org; Mon, 7 Apr 2003 08:48:28 -0500 (CDT) To: xslt@gnome.org Subject: Re: [xslt] func:result not recognized Message-ID: <1049723308.3e9181ac945da@mail.hiwaay.net> Date: Mon, 07 Apr 2003 08:48:28 -0500 (CDT) From: cbozeman@hiwaay.net References: <20030407084941.F29447@redhat.com> In-Reply-To: <20030407084941.F29447@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.8 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Quoting Daniel Veillard : > Well Charles Bozeman provided them IIRC! Even I can't remember > all the syntax, it's easier to start from working examples for me ... I believe Thomas Broyer provided the regression tests, most of my contributions have been limited to data/time/duration stuff as well as some other minor stuff. Thomas did the bulk of the work on libexslt. Charlie B. From oliver@rutherfurd.net Mon Apr 7 13:55:20 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mail11.atl.registeredsite.com (mail11.atl.registeredsite.com [64.224.219.85]) by mail.gnome.org (Postfix) with ESMTP id 3608B1865A for ; Mon, 7 Apr 2003 13:55:20 -0400 (EDT) Received: from mail.rutherfurd.net ([209.35.109.224]) by mail11.atl.registeredsite.com (8.12.8/8.12.6) with ESMTP id h37HtCuM020113; Mon, 7 Apr 2003 13:55:15 -0400 Received: from rutherfurd.net [209.35.109.224] by mail.rutherfurd.net with ESMTP (SMTPD32-6.06) id AB78C8B500B8; Mon, 07 Apr 2003 13:55:07 -0400 Message-ID: <3E91BA87.10406@rutherfurd.net> Date: Mon, 07 Apr 2003 13:51:03 -0400 From: Ollie Rutherfurd User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: xslt@gnome.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xslt] replacing spaces in an attribute value during transformation Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi, I'm using xsltproc to split an xml document into a number of smaller documents. For the filenames of the smaller documents I'd like to an attribute value with spaces replaced with underscores and invalid characters (such as "?" removed). I've tried to use the str:replace templates and functions on http://exslt.org/, but haven't had much success. When I try to use str.replace template like so: xsltproc crashes with an access violation. If I try to use the function like so: I get the error: {http://exslt.org/strings}replace: called with too many arguments xmlXPathCompiledEval: 2 object left on the stack runtime error: file split-articles.xsl line 34 element value-of xsltValueOf: text copy failed no result for tupleArticle.xml I'm using: Using libxml 20506, libxslt 10029 and libexslt 719 xsltproc was compiled against libxml 20506, libxslt 10029 and libexslt 719 libxslt 10029 was compiled against libxml 20506 libexslt 719 was compiled against libxml 20506 I've tried googling around for similar error messages, but haven't found anything specifically related to this. Am I calling the functions incorrectly? Does anyone have any suggestions for how I can replace the spaces? Thanks, -Ollie -- Ollie Rutherfurd http://www.rutherfurd.net/ From gnome-xslt@m.gmane.org Mon Apr 7 15:31:43 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mail.gnome.org (Postfix) with ESMTP id 9A7E7180FB for ; Mon, 7 Apr 2003 15:31:42 -0400 (EDT) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 192cK9-0008TG-00 for ; Mon, 07 Apr 2003 21:30:33 +0200 Mail-Followup-To: xslt@gnome.org X-Injected-Via-Gmane: http://gmane.org/ To: xslt@gnome.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 192cAL-0007ee-00 for ; Mon, 07 Apr 2003 21:20:25 +0200 From: Steinar Bang Date: Mon, 07 Apr 2003 21:20:51 +0200 Organization: Probably a good idea Lines: 52 Message-ID: <8765pqnmgc.fsf@doohan.bang.priv.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@main.gmane.org Mail-Copies-To: never User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Common Lisp, i386-debian-linux) Cancel-Lock: sha1:4WOXfJbHSwTjExkBY9yN99qu4b0= Subject: [xslt] has no namespace in external entity Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Platform: debian testing/unstable (sarge), DocBook XML 4.2 DocBook XSL 1.60.1 xsltproc 1.0.27 Is XInclude of text files supposed to work from an external entity used in an XML document? If the answer is yes, I can whip up a simple test case of where it doesn't work, and report a bug. If the answer is no, I will try to use XInclude all the way. I'm trying to replace the use of the DocBook XSL include extensions with XInclude to include text files into , as outlined in Bob Stayton's book[1], so that I can use xsltproc instead of Saxon. However I run into problems where I have used external entities to make documents modular. The element doesn't work, when used in an external entity. I get the message: extsection.xml:7: warning: Namespace prefix xi is not defined element, I have made the following changes to the DocBook XML DTD in the internal subset. This works for psgml, and seems to work for used from the top level document: ]> Thanx! - Steinar [1] From veillard@redhat.com Mon Apr 7 16:13:30 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 2D49F186F2 for ; Mon, 7 Apr 2003 16:13:30 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h37KDMt08665; Mon, 7 Apr 2003 16:13:22 -0400 Date: Mon, 7 Apr 2003 16:13:22 -0400 From: Daniel Veillard To: sb@dod.no Cc: xslt@gnome.org Subject: Re: [xslt] has no namespace in external entity Message-ID: <20030407161322.I29447@redhat.com> References: <8765pqnmgc.fsf@doohan.bang.priv.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <8765pqnmgc.fsf@doohan.bang.priv.no>; from sb@dod.no on Mon, Apr 07, 2003 at 09:20:51PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Apr 07, 2003 at 09:20:51PM +0200, Steinar Bang wrote: > extsection.xml:7: warning: Namespace prefix xi is not defined > and this will be garanteed to work. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From gnome-xslt@m.gmane.org Mon Apr 7 17:32:00 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mail.gnome.org (Postfix) with ESMTP id 46105181F2 for ; Mon, 7 Apr 2003 17:32:00 -0400 (EDT) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 192eCc-0000S0-00 for ; Mon, 07 Apr 2003 23:30:54 +0200 Mail-Followup-To: xslt@gnome.org X-Injected-Via-Gmane: http://gmane.org/ To: xslt@gnome.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 192eC6-0000QG-00 for ; Mon, 07 Apr 2003 23:30:22 +0200 From: Steinar Bang Date: Mon, 07 Apr 2003 23:30:49 +0200 Organization: Probably a good idea Lines: 31 Message-ID: <87smsum1va.fsf@doohan.bang.priv.no> References: <8765pqnmgc.fsf@doohan.bang.priv.no> <20030407161322.I29447@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@main.gmane.org Mail-Copies-To: never User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Common Lisp, i386-debian-linux) Cancel-Lock: sha1:1qQfDm4AWU0SHCqesKOgFCR39YY= Subject: [xslt] Re: has no namespace in external entity Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: >>>>> Daniel Veillard : > On Mon, Apr 07, 2003 at 09:20:51PM +0200, Steinar Bang wrote: >> extsection.xml:7: warning: Namespace prefix xi is not defined >> xmlns:xi='http://www.w3.org/2001/XInclude'/> > and this will be garanteed to work. Ah, OK. That should mean that a #FIXED xmlns:xi attribute on , should do the trick as well? ie. like this: ]> And it does indeed work. Thanx Daniel! From veillard@redhat.com Mon Apr 7 17:46:07 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id BDBEB1818C for ; Mon, 7 Apr 2003 17:46:07 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h37Lk7M04316 for xslt@gnome.org; Mon, 7 Apr 2003 17:46:07 -0400 Date: Mon, 7 Apr 2003 17:46:07 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Re: has no namespace in external entity Message-ID: <20030407174607.L29447@redhat.com> References: <8765pqnmgc.fsf@doohan.bang.priv.no> <20030407161322.I29447@redhat.com> <87smsum1va.fsf@doohan.bang.priv.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <87smsum1va.fsf@doohan.bang.priv.no>; from sb@dod.no on Mon, Apr 07, 2003 at 11:30:49PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Apr 07, 2003 at 11:30:49PM +0200, Steinar Bang wrote: > >>>>> Daniel Veillard : > > > On Mon, Apr 07, 2003 at 09:20:51PM +0200, Steinar Bang wrote: > >> extsection.xml:7: warning: Namespace prefix xi is not defined > >> > > > xmlns:xi='http://www.w3.org/2001/XInclude'/> > > > and this will be garanteed to work. > > Ah, OK. That should mean that a #FIXED xmlns:xi attribute on > , should do the trick as well? ie. like this: yup, except it would not been dependant on reading the DTD. Using defaulted attribute is always a bit dangerous because parser may not read the DTD (and I find it myself disturbing, because reading the xml you can't see where the namespace prefix is declared or what it is bound to, this becomes especially nasty for default namespaces...) > And it does indeed work. okay, good. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From Mark_Vakoc@jdedwards.com Tue Apr 8 15:52:31 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from ns2.jdedwards.com (ns2.jdedwards.com [199.166.248.75]) by mail.gnome.org (Postfix) with ESMTP id 3E091185F8 for ; Tue, 8 Apr 2003 15:52:31 -0400 (EDT) Received: from denvscans4.jdedwards.com ([10.0.14.76]) by ns2.jdedwards.com (8.11.6/8.9.1) with SMTP id h38JqVF14308 for ; Tue, 8 Apr 2003 13:52:31 -0600 Received: from 10.0.14.88 by denvscans4.jdedwards.com (InterScan E-Mail VirusWall NT); Tue, 08 Apr 2003 13:52:29 -0600 Received: from denmails3.jdedwards.com ([10.0.14.80]) by densmtps2.jdedwards.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 8 Apr 2003 13:50:12 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message Date: Tue, 8 Apr 2003 13:50:12 -0600 Message-ID: <09B3671D58690A4193A7F8F15F416B23111B28@denmails3.jdedwards.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Result Tree Fragments Thread-Index: AcL+CBGFYtQi+CYgRyqtHlR/5qZ2wg== From: "Vakoc, Mark" To: X-OriginalArrivalTime: 08 Apr 2003 19:50:12.0922 (UTC) FILETIME=[11A821A0:01C2FE08] Subject: [xslt] Result Tree Fragments Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi Daniel, all, I'm trying to debug the bug I entered: = http://bugzilla.gnome.org/show_bug.cgi?id=3D110023 It appears that you have changed the method for managing result tree = fragments. It appears that any extension functions that return a result = tree fragment need to be modified, including str:tokenize() and such. Before the container node for the result tree fragment (rtf) nodes was a = child of the source document so the nodes would get free'd when the = document is free'd. Under the new system when would the nodes contained = in the RTF ever get freed? Do I need to modify all my extension = functions that return a RTF to use this new method? If so str:tokenize = and any other extensions that return a RTF need to be modified as well? } else { /* * This is a result tree fragment. */ xmlDocPtr container; xmlNodePtr oldInsert; xmlDocPtr oldoutput; container =3D xmlNewDoc(NULL); if (container =3D=3D NULL) return(NULL); container->name =3D (char *) xmlStrdup(BAD_CAST " fake node = libxslt"); container->doc =3D container; container->parent =3D NULL; oldoutput =3D ctxt->output; ctxt->output =3D container; oldInsert =3D ctxt->insert; ctxt->insert =3D (xmlNodePtr) container; xsltApplyOneTemplate(ctxt, ctxt->node, elem->tree, NULL, NULL); ctxt->insert =3D oldInsert; ctxt->output =3D oldoutput; result =3D xmlXPathNewValueTree((xmlNodePtr) container); if (result =3D=3D NULL) { result =3D xmlXPathNewCString(""); } else { /* * Tag the subtree for removal once consumed */ result->boolval =3D 1; } #ifdef WITH_XSLT_DEBUG_VARIABLE #ifdef LIBXML_DEBUG_ENABLED if ((xsltGenericDebugContext =3D=3D stdout) || (xsltGenericDebugContext =3D=3D stderr)) xmlXPathDebugDumpObject((FILE *)xsltGenericDebugContext, result, 0); #endif #endif } From Mark_Vakoc@jdedwards.com Tue Apr 8 16:28:12 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from ns2.jdedwards.com (ns2.jdedwards.com [199.166.248.75]) by mail.gnome.org (Postfix) with ESMTP id 935B4180D7 for ; Tue, 8 Apr 2003 16:28:11 -0400 (EDT) Received: from denvscans4.jdedwards.com ([10.0.14.76]) by ns2.jdedwards.com (8.11.6/8.9.1) with SMTP id h38KSBF26757 for ; Tue, 8 Apr 2003 14:28:11 -0600 Received: from 10.0.14.51 by denvscans4.jdedwards.com (InterScan E-Mail VirusWall NT); Tue, 08 Apr 2003 14:28:10 -0600 Received: by cormails11.jdedwards.com with Internet Mail Service (5.5.2653.19) id ; Tue, 8 Apr 2003 14:32:51 -0600 Message-ID: <09B3671D58690A4193A7F8F15F416B23FF2556@denmails3.jdedwards.com> From: "Vakoc, Mark" To: "'xslt@gnome.org'" Subject: RE: [xslt] Result Tree Fragments Date: Tue, 8 Apr 2003 14:28:05 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C2FE0D.5C606139" Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C2FE0D.5C606139 Content-Type: text/plain; charset="iso-8859-1" Perhaps an answer to my own question: Daniel, can you verify that the attached patch for str:tokenize() is the correct method for returning Result Tree Fragments from extension functions. This also fixes what appeared to be a memory leak in that 'str' and 'delimiters' were never freed if the operation was successful. I've also attached the patch to the bug. -----Original Message----- From: Vakoc, Mark Sent: Tuesday, April 08, 2003 1:50 PM To: xslt@gnome.org Subject: [xslt] Result Tree Fragments Hi Daniel, all, I'm trying to debug the bug I entered: http://bugzilla.gnome.org/show_bug.cgi?id=110023 It appears that you have changed the method for managing result tree fragments. It appears that any extension functions that return a result tree fragment need to be modified, including str:tokenize() and such. Before the container node for the result tree fragment (rtf) nodes was a child of the source document so the nodes would get free'd when the document is free'd. Under the new system when would the nodes contained in the RTF ever get freed? Do I need to modify all my extension functions that return a RTF to use this new method? If so str:tokenize and any other extensions that return a RTF need to be modified as well? } else { /* * This is a result tree fragment. */ xmlDocPtr container; xmlNodePtr oldInsert; xmlDocPtr oldoutput; container = xmlNewDoc(NULL); if (container == NULL) return(NULL); container->name = (char *) xmlStrdup(BAD_CAST " fake node libxslt"); container->doc = container; container->parent = NULL; oldoutput = ctxt->output; ctxt->output = container; oldInsert = ctxt->insert; ctxt->insert = (xmlNodePtr) container; xsltApplyOneTemplate(ctxt, ctxt->node, elem->tree, NULL, NULL); ctxt->insert = oldInsert; ctxt->output = oldoutput; result = xmlXPathNewValueTree((xmlNodePtr) container); if (result == NULL) { result = xmlXPathNewCString(""); } else { /* * Tag the subtree for removal once consumed */ result->boolval = 1; } #ifdef WITH_XSLT_DEBUG_VARIABLE #ifdef LIBXML_DEBUG_ENABLED if ((xsltGenericDebugContext == stdout) || (xsltGenericDebugContext == stderr)) xmlXPathDebugDumpObject((FILE *)xsltGenericDebugContext, result, 0); #endif #endif } _______________________________________________ xslt mailing list, project page http://xmlsoft.org/XSLT/ xslt@gnome.org http://mail.gnome.org/mailman/listinfo/xslt ------_=_NextPart_000_01C2FE0D.5C606139 Content-Type: application/octet-stream; name="strings.diff" Content-Disposition: attachment; filename="strings.diff" Index: strings.c =================================================================== RCS file: /cvs/gnome/libxslt/libexslt/strings.c,v retrieving revision 1.8 diff -c -r1.8 strings.c *** strings.c 2 Jan 2003 22:30:08 -0000 1.8 --- strings.c 8 Apr 2003 20:25:02 -0000 *************** *** 34,40 **** xmlChar *str, *delimiters, *cur; const xmlChar *token, *delimiter; xmlNodePtr node; ! xmlDocPtr doc; xmlXPathObjectPtr ret; if ((nargs < 1) || (nargs > 2)) { --- 34,41 ---- xmlChar *str, *delimiters, *cur; const xmlChar *token, *delimiter; xmlNodePtr node; ! xmlDocPtr container; ! xmlXPathObjectPtr ret; if ((nargs < 1) || (nargs > 2)) { *************** *** 58,111 **** return; } ! doc = xsltXPathGetTransformContext(ctxt)->document->doc; ! ret = xmlXPathNewNodeSet (NULL); ! if (ret != NULL) { ! ret->boolval = 1; ! /* ! * This is a hack: token elements are added as children of a ! * fake element node. This is necessary to free them up ! * correctly when freeing the node-set. ! */ ! ret->user = (void *) xmlNewDocNode (doc, NULL, ! (const xmlChar *) "fake", NULL); ! if (ret->user == NULL) ! goto error; ! } ! for (cur = str, token = str; *cur != 0; cur++) { ! for (delimiter = delimiters; *delimiter != 0; delimiter++) { ! if (*cur == *delimiter) { ! if (cur == token) { ! /* discard empty tokens */ ! break; } - *cur = 0; - node = xmlNewDocNode (doc, NULL, - (const xmlChar *) "token", token); - *cur = *delimiter; - token = cur + 1; - - xmlAddChild ((xmlNodePtr) ret->user, node); - xmlXPathNodeSetAdd (ret->nodesetval, node); - break; - } } ! } ! node = xmlNewDocNode (doc, NULL, (const xmlChar *) "token", token); ! xmlAddChild ((xmlNodePtr) ret->user, node); ! xmlXPathNodeSetAdd (ret->nodesetval, node); ! ! valuePush (ctxt, ret); ! ret = NULL; /* hack to prevent freeing ret later */ ! ! error: ! if (ret != NULL) ! xmlXPathFreeObject (ret); if (str != NULL) xmlFree(str); if (delimiters != NULL) xmlFree(delimiters); } /** --- 59,102 ---- return; } ! /* Return a result tree fragment */ ! container = xmlNewDoc(NULL); ! if (container != NULL) { ! container->name = (char *) xmlStrdup(BAD_CAST " fake node libxslt"); ! container->doc = container; ! ret = xmlXPathNewValueTree((xmlNodePtr) container); ! if (ret != NULL) { ! /* Tag the subtree for removal once consumed */ ! ret->boolval = 1; ! for (cur = str, token = str; *cur != 0; cur++) { ! for (delimiter = delimiters; *delimiter != 0; delimiter++) { ! if (*cur == *delimiter) { ! if (cur == token) { ! /* discard empty tokens */ ! break; ! } ! *cur = 0; ! node = xmlNewChild ( (xmlNodePtr) container, NULL, ! (const xmlChar *) "token", token); ! *cur = *delimiter; ! token = cur + 1; ! break; ! } ! } ! } ! node = xmlNewChild ((xmlNodePtr) container, NULL, (const xmlChar *) "token", token); } } ! if (str != NULL) xmlFree(str); if (delimiters != NULL) xmlFree(delimiters); + if (ret != NULL) + valuePush (ctxt, ret); + else + valuePush(ctxt,xmlXPathNewNodeSet(NULL)); } /** ------_=_NextPart_000_01C2FE0D.5C606139-- From ave@stacksoft.ru Wed Apr 9 06:43:58 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from ns.stacksoft.ru (ns.stacksoft.ru [217.73.199.113]) by mail.gnome.org (Postfix) with ESMTP id 09A90182C1 for ; Wed, 9 Apr 2003 06:43:58 -0400 (EDT) Received: from alef (eagle.stack.net [217.73.199.130]) by ns.stacksoft.ru (8.12.6/8.11.6) with ESMTP id h39Ahw8G035058 for ; Wed, 9 Apr 2003 14:43:58 +0400 (MSD) (envelope-from ave@stacksoft.ru) Date: Wed, 9 Apr 2003 14:48:22 +0400 From: Alexey Efimov X-Mailer: The Bat! (v1.61) Organization: Stack Soft X-Priority: 3 (Normal) Message-ID: <170-1780151362.20030409144822@stacksoft.ru> To: xslt@gnome.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [xslt] exslt in Windows port Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: Alexey Efimov List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hello, I have the latest release of libxslt at Windows 2000 (from http://zlatkovic.com/projects/libxml/binaries.html) and at HP-UX (built from source). Number of exslt functions in Windows port is too small. At Windows: --------------- >C:\bin\xml\libxml\common\xsltproc -V Using libxml 20506, libxslt 10029 and libexslt 719 xsltproc was compiled against libxml 20506, libxslt 10029 and libexslt 719 libxslt 10029 was compiled against libxml 20506 libexslt 719 was compiled against libxml 20506 >C:\bin\xml\libxml\common\xsltproc --dumpextensions > ext This command gives me just 57 lines (including only 6 math functions). At HP-UX: --------------- >$xsl -V Using libxml 20506, libxslt 10029 and libexslt 719 xsltproc was compiled against libxml 20402, libxslt 10019 and libexslt 710 libxslt 10029 was compiled against libxml 20402 libexslt 719 was compiled against libxml 20402 >$xsl --dumpextensions | wc 69 74 2460 >$xsl --dumpextensions | grep math | wc 18 18 509 Why such difference is present? Am I doing something wrong? Thanks in advance, Alexey. From veillard@redhat.com Wed Apr 9 07:03:32 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id A9AA918808 for ; Wed, 9 Apr 2003 07:03:32 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h39B3WN05559 for xslt@gnome.org; Wed, 9 Apr 2003 07:03:32 -0400 Date: Wed, 9 Apr 2003 07:03:32 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] exslt in Windows port Message-ID: <20030409070332.N10927@redhat.com> References: <170-1780151362.20030409144822@stacksoft.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <170-1780151362.20030409144822@stacksoft.ru>; from ave@stacksoft.ru on Wed, Apr 09, 2003 at 02:48:22PM +0400 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wed, Apr 09, 2003 at 02:48:22PM +0400, Alexey Efimov wrote: > Hello, > > I have the latest release of libxslt at Windows 2000 (from > http://zlatkovic.com/projects/libxml/binaries.html) and at HP-UX > (built from source). Number of exslt functions in Windows port is too > small. Seems some of the EXSLT math module is related to the presence of the math.h header file ... If windows has it, HAVE_MATH_H should be defined in win32config.h > Why such difference is present? Am I doing something wrong? Seems the code need some love for Windows... Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From gena01@lk.net Wed Apr 9 11:56:10 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from capital.lk.net (capital.lk.net [207.87.225.1]) by mail.gnome.org (Postfix) with ESMTP id 7E93C18875 for ; Wed, 9 Apr 2003 11:56:10 -0400 (EDT) Received: (from nobody@localhost) by capital.lk.net (8.11.6/8.11.6) id h39Fu7015791; Wed, 9 Apr 2003 11:56:07 -0400 Date: Wed, 9 Apr 2003 11:56:07 -0400 Message-Id: <200304091556.h39Fu7015791@capital.lk.net> X-Authentication-Warning: capital.lk.net: nobody set sender to gena01@lk.net using -f From: "Gennady Feldman" To: xslt@gnome.org X-Mailer: NeoMail 1.23 X-IPAddress: 198.140.63.114 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=NEOMAIL_ATT_0.797844634697871" Subject: [xslt] Segmentation fault w/ latest libxslt. Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: This is a multi-part message in MIME format. ------=NEOMAIL_ATT_0.797844634697871 Content-Type: text/plain; charset=iso-8859-1 When testing some of my XSL scripts I stumbled onto a segmentation fault in my mod-xslt module. This was very peculiar to me since I had the the same XSL files work fine before. So I tried running xsltproc with the same XSL file and it did a segmentation fault. Now this used to work fine with the previous version of libxslt, so I guess it got broken in 1.0.29. I have managed to produce a cut down version of a reproducible simple test case. I am attaching my sample test.xml and test.xsl files. Just run xsltproc with test.xsl and test.xml G.F. aka Gena01 http://www.gena01.com ------=NEOMAIL_ATT_0.797844634697871 Content-Type: text/xml; name="test.xml" Content-Transfer-Encoding: base64 PD94bWwgdmVyc2lvbj0iMS4wIiA/PgoKPHJvb3Q+Cgk8ZWxlbWVudCBhdHRyPSJhYWEiLz4KCTxl bGVtZW50IGF0dHI9ImJiYiIvPgo8L3Jvb3Q+Cg== ------=NEOMAIL_ATT_0.797844634697871 Content-Type: text/xml; name="test.xsl" Content-Transfer-Encoding: base64 PD94bWwgdmVyc2lvbj0iMS4wIiA/Pgo8eHNsOnN0eWxlc2hlZXQgdmVyc2lvbj0iMS4wIiAKCQl4 bWxuczp4c2w9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkvWFNML1RyYW5zZm9ybSIKCQl4bWxuczpl eHNsPSJodHRwOi8vZXhzbHQub3JnL2NvbW1vbiIKICAgICAgICAgICAgICAgIGV4dGVuc2lvbi1l bGVtZW50LXByZWZpeGVzPSJleHNsIj4KCjx4c2w6dGVtcGxhdGUgbWF0Y2g9InJvb3QiPgoJPGh0 bWw+Cgk8aGVhZD4KCQk8dGl0bGU+UmVncmVzc2lvbiBUZXN0PC90aXRsZT4KCTwvaGVhZD4KCTxi b2R5PgoJCTx4c2w6dmFyaWFibGUgbmFtZT0ibm9kZXMiPgoJCQk8eHNsOmZvci1lYWNoIHNlbGVj dD0iZWxlbWVudCI+CgkJCQk8eHNsOmNvcHk+CgkJCQkJPHhzbDpjb3B5LW9mIHNlbGVjdD0iQCoi Lz4KCQkJCQkKCQkJCTwveHNsOmNvcHk+CgkJCTwveHNsOmZvci1lYWNoPgoJCTwveHNsOnZhcmlh YmxlPgkJCgoJCTx4c2w6Zm9yLWVhY2ggc2VsZWN0PSJleHNsOm5vZGUtc2V0KCRub2RlcykvZWxl bWVudCI+Cgk8ZGl2IGNsYXNzPSJ7QGF0dHJ9Ij4KCQk8eHNsOnRleHQ+IEFBQSA8L3hzbDp0ZXh0 PgoJPC9kaXY+CgoJCTwveHNsOmZvci1lYWNoPgoJPC9ib2R5PgoJPC9odG1sPgo8L3hzbDp0ZW1w bGF0ZT4KCgo8L3hzbDpzdHlsZXNoZWV0PgoK ------=NEOMAIL_ATT_0.797844634697871-- From veillard@redhat.com Wed Apr 9 12:11:08 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id CCC4518283 for ; Wed, 9 Apr 2003 12:11:05 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h39GB3i11101 for xslt@gnome.org; Wed, 9 Apr 2003 12:11:03 -0400 Date: Wed, 9 Apr 2003 12:11:03 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Segmentation fault w/ latest libxslt. Message-ID: <20030409121103.D22996@redhat.com> References: <200304091556.h39Fu7015791@capital.lk.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200304091556.h39Fu7015791@capital.lk.net>; from gena01@lk.net on Wed, Apr 09, 2003 at 11:56:07AM -0400 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wed, Apr 09, 2003 at 11:56:07AM -0400, Gennady Feldman wrote: > When testing some of my XSL scripts I stumbled onto a segmentation fault > in my mod-xslt module. This was very peculiar to me since I had the the > same XSL files work fine before. So I tried running xsltproc with the > same XSL file and it did a segmentation fault. Now this used to work > fine with the previous version of libxslt, so I guess it got broken in > 1.0.29. I have managed to produce a cut down version of a reproducible > simple test case. I am attaching my sample test.xml and test.xsl files. > Just run xsltproc with test.xsl and test.xml Fixed in CVS, see http://bugzilla.gnome.org/show_bug.cgi?id=110023 Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From Mark_Vakoc@jdedwards.com Wed Apr 9 12:21:23 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from ns1.jdedwards.com (ns1.jdedwards.com [199.166.248.147]) by mail.gnome.org (Postfix) with ESMTP id 9C00918204 for ; Wed, 9 Apr 2003 12:21:22 -0400 (EDT) Received: from denvscans3.jdedwards.com ([10.0.14.77]) by ns1.jdedwards.com (8.11.6/8.9.1) with SMTP id h39GLMU04364 for ; Wed, 9 Apr 2003 10:21:22 -0600 Received: from 10.0.14.50 by denvscans3.jdedwards.com (InterScan E-Mail VirusWall NT); Wed, 09 Apr 2003 10:21:21 -0600 Received: by cormails5.jdedwards.com with Internet Mail Service (5.5.2653.19) id ; Wed, 9 Apr 2003 10:20:59 -0600 Message-ID: <09B3671D58690A4193A7F8F15F416B23111B29@denmails3.jdedwards.com> From: "Vakoc, Mark" To: xslt@gnome.org Subject: RE: [xslt] Result Tree Fragments Date: Wed, 9 Apr 2003 10:20:42 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) content-class: urn:content-classes:message Content-Type: text/plain; charset="iso-8859-1" Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Well I haven't heard anything but this fixes my own testcase in bug 110023 so I think it's safe to apply. > -----Original Message----- > From: Vakoc, Mark > Sent: Tuesday, April 08, 2003 2:28 PM > To: 'xslt@gnome.org' > Subject: RE: [xslt] Result Tree Fragments > > > Perhaps an answer to my own question: > > Daniel, can you verify that the attached patch for > str:tokenize() is the > correct method for returning Result Tree Fragments from > extension functions. > > This also fixes what appeared to be a memory leak in that 'str' and > 'delimiters' were never freed if the operation was successful. > > I've also attached the patch to the bug. > > > -----Original Message----- > From: Vakoc, Mark > Sent: Tuesday, April 08, 2003 1:50 PM > To: xslt@gnome.org > Subject: [xslt] Result Tree Fragments > > > > Hi Daniel, all, > > I'm trying to debug the bug I entered: > http://bugzilla.gnome.org/show_bug.cgi?id=110023 > > It appears that you have changed the method for managing result tree > fragments. It appears that any extension functions that > return a result > tree fragment need to be modified, including str:tokenize() and such. > > Before the container node for the result tree fragment (rtf) > nodes was a > child of the source document so the nodes would get free'd > when the document > is free'd. Under the new system when would the nodes > contained in the RTF > ever get freed? Do I need to modify all my extension > functions that return > a RTF to use this new method? If so str:tokenize and any > other extensions > that return a RTF need to be modified as well? > > } else { > /* > * This is a result tree fragment. > */ > xmlDocPtr container; > xmlNodePtr oldInsert; > xmlDocPtr oldoutput; > > container = xmlNewDoc(NULL); > if (container == NULL) > return(NULL); > container->name = (char *) xmlStrdup(BAD_CAST " fake node > libxslt"); > container->doc = container; > container->parent = NULL; > > oldoutput = ctxt->output; > ctxt->output = container; > oldInsert = ctxt->insert; > ctxt->insert = (xmlNodePtr) container; > xsltApplyOneTemplate(ctxt, ctxt->node, elem->tree, > NULL, NULL); > ctxt->insert = oldInsert; > ctxt->output = oldoutput; > > result = xmlXPathNewValueTree((xmlNodePtr) container); > if (result == NULL) { > result = xmlXPathNewCString(""); > } else { > /* > * Tag the subtree for removal once consumed > */ > result->boolval = 1; > } > #ifdef WITH_XSLT_DEBUG_VARIABLE > #ifdef LIBXML_DEBUG_ENABLED > if ((xsltGenericDebugContext == stdout) || > (xsltGenericDebugContext == stderr)) > xmlXPathDebugDumpObject((FILE *)xsltGenericDebugContext, > result, 0); > #endif > #endif > } > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt > > From Mark_Vakoc@jdedwards.com Wed Apr 9 13:11:18 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from ns2.jdedwards.com (ns2.jdedwards.com [199.166.248.75]) by mail.gnome.org (Postfix) with ESMTP id 2CF17184D3 for ; Wed, 9 Apr 2003 13:11:18 -0400 (EDT) Received: from denvscans4.jdedwards.com ([10.0.14.76]) by ns2.jdedwards.com (8.11.6/8.9.1) with SMTP id h39HBHF27782 for ; Wed, 9 Apr 2003 11:11:17 -0600 Received: from 10.0.14.50 by denvscans4.jdedwards.com (InterScan E-Mail VirusWall NT); Wed, 09 Apr 2003 11:11:17 -0600 Received: by cormails5.jdedwards.com with Internet Mail Service (5.5.2653.19) id ; Wed, 9 Apr 2003 11:10:54 -0600 Message-ID: <09B3671D58690A4193A7F8F15F416B23FF255B@denmails3.jdedwards.com> From: "Vakoc, Mark" To: xslt@gnome.org Date: Wed, 9 Apr 2003 11:06:40 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) content-class: urn:content-classes:message Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C2FEBA.63B56680" Subject: [xslt] fix for set:distinct() Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C2FEBA.63B56680 Content-Type: text/plain; charset="iso-8859-1" Possible double free error fixed. Attached is a patch and a testcase. <> <> ------_=_NextPart_000_01C2FEBA.63B56680 Content-Type: application/octet-stream; name="distinct.xsl" Content-Disposition: attachment; filename="distinct.xsl"

------_=_NextPart_000_01C2FEBA.63B56680 Content-Type: application/octet-stream; name="sets.diff" Content-Disposition: attachment; filename="sets.diff" Index: libexslt/sets.c =================================================================== RCS file: /cvs/gnome/libxslt/libexslt/sets.c,v retrieving revision 1.10 diff -c -r1.10 sets.c *** libexslt/sets.c 18 Mar 2002 19:53:54 -0000 1.10 --- libexslt/sets.c 9 Apr 2003 17:05:56 -0000 *************** *** 113,119 **** /* !!! must be sorted !!! */ ret = xmlXPathDistinctSorted(ns); ! xmlXPathFreeNodeSet(ns); xmlXPathReturnNodeSet(ctxt, ret); } --- 113,120 ---- /* !!! must be sorted !!! */ ret = xmlXPathDistinctSorted(ns); ! if (ret != ns) ! xmlXPathFreeNodeSet(ns); xmlXPathReturnNodeSet(ctxt, ret); } ------_=_NextPart_000_01C2FEBA.63B56680-- From gena01@lk.net Wed Apr 9 13:37:19 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from capital.lk.net (capital.lk.net [207.87.225.1]) by mail.gnome.org (Postfix) with ESMTP id 7D8F5181C9 for ; Wed, 9 Apr 2003 13:37:19 -0400 (EDT) Received: (from nobody@localhost) by capital.lk.net (8.11.6/8.11.6) id h39HbJ420188; Wed, 9 Apr 2003 13:37:19 -0400 Date: Wed, 9 Apr 2003 13:37:19 -0400 Message-Id: <200304091737.h39HbJ420188@capital.lk.net> X-Authentication-Warning: capital.lk.net: nobody set sender to gena01@lk.net using -f From: "Gennady Feldman" To: xslt@gnome.org Subject: Re: [xslt] Segmentation fault w/ latest libxslt. X-Mailer: NeoMail 1.23 X-IPAddress: 198.140.63.114 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: [clipped] > > Fixed in CVS, see http://bugzilla.gnome.org/show_bug.cgi?id=110023 > > Daniel > [clipped] Confirmed as it is fixed in CVS. I have rebuilt the rpm with latest CVS snapshot and have it running on my development machine. G.F. aka Gena01 http://www.gena01.com From veillard@redhat.com Wed Apr 9 16:03:52 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 5A240181AB for ; Wed, 9 Apr 2003 16:03:50 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h39K3lQ11470 for xslt@gnome.org; Wed, 9 Apr 2003 16:03:47 -0400 Date: Wed, 9 Apr 2003 16:03:47 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Result Tree Fragments Message-ID: <20030409160347.E22996@redhat.com> References: <09B3671D58690A4193A7F8F15F416B23111B29@denmails3.jdedwards.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <09B3671D58690A4193A7F8F15F416B23111B29@denmails3.jdedwards.com>; from Mark_Vakoc@jdedwards.com on Wed, Apr 09, 2003 at 10:20:42AM -0600 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wed, Apr 09, 2003 at 10:20:42AM -0600, Vakoc, Mark wrote: > Well I haven't heard anything but this fixes my own testcase in bug 110023 > so I think it's safe to apply. yep, sorry didn't had time yet to look in details. > > -----Original Message----- > > From: Vakoc, Mark > > Sent: Tuesday, April 08, 2003 2:28 PM > > To: 'xslt@gnome.org' > > Subject: RE: [xslt] Result Tree Fragments > > > > > > Perhaps an answer to my own question: > > > > Daniel, can you verify that the attached patch for > > str:tokenize() is the > > correct method for returning Result Tree Fragments from > > extension functions. Hum, right, creating a real document node is what libxslt does now for RTFs, it's more unified, simplifies the template processing for those, etc ... context->document becoming NULL is an annoyance but really a side effect of the node-set() extension which wasn't in the initial spec and which I didn't design for. It's annoying to change some design at this point but it's really due to the huge deployment of this extension function. > > This also fixes what appeared to be a memory leak in that 'str' and > > 'delimiters' were never freed if the operation was successful. > > > > I've also attached the patch to the bug. I applied the patch, thanks ! Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard@redhat.com Wed Apr 9 16:15:08 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id F12D218880 for ; Wed, 9 Apr 2003 16:15:07 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h39KF7W16132 for xslt@gnome.org; Wed, 9 Apr 2003 16:15:07 -0400 Date: Wed, 9 Apr 2003 16:15:07 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] fix for set:distinct() Message-ID: <20030409161507.F22996@redhat.com> References: <09B3671D58690A4193A7F8F15F416B23FF255B@denmails3.jdedwards.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <09B3671D58690A4193A7F8F15F416B23FF255B@denmails3.jdedwards.com>; from Mark_Vakoc@jdedwards.com on Wed, Apr 09, 2003 at 11:06:40AM -0600 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wed, Apr 09, 2003 at 11:06:40AM -0600, Vakoc, Mark wrote: > Possible double free error fixed. Attached is a patch and a testcase. Right, but there is still a memory leak ... apparently an RTF containing just

is not freed, I need to investigate paphio:~/XSLT/tests/general -> xsltproc ./bug-116.xsl ./../docs/bug-116.xml paphio:~/XSLT/tests/general -> cat .memdump 10:12:05 PM MEMORY ALLOCATED : 157, MAX was 27171 BLOCK NUMBER SIZE TYPE 0 632 2 malloc() in none(0) "p" 1 631 52 malloc() in none(0) pointer to #632 at index 8 2 630 19 malloc() in none(0) " fake node libxslt" 3 629 4 malloc() in none(0) "1.0" 4 628 80 malloc() in none(0) pointer to #630 at index 8 paphio:~/XSLT/tests/general -> Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From srperan@sherlock.dif.um.es Thu Apr 10 05:39:08 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from unimur.um.es (unknown [155.54.1.1]) by mail.gnome.org (Postfix) with ESMTP id EE2A418888 for ; Thu, 10 Apr 2003 05:39:02 -0400 (EDT) Received: from sherlock (sherlock.dif.um.es [155.54.15.166]) by unimur.um.es (8.9.1b+Sun/8.9.1) with ESMTP id LAA06142; Thu, 10 Apr 2003 11:39:01 +0200 (MEST) From: srperan@sherlock.dif.um.es Received: from srperan by sherlock with local (Exim 3.36 #1 (Debian)) id 193YbQ-0005yl-00; Thu, 10 Apr 2003 11:44:16 +0200 Date: Thu, 10 Apr 2003 11:44:16 +0200 To: xslt@gnome.org Cc: dsevilla@ditec.um.es Message-ID: <20030410094416.GB22874@sherlock.dif.um.es> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030410083807.14118.27712.Mailman@moniker.gnome.org> User-Agent: Mutt/1.5.3i Subject: [xslt] Question about white space output Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hello. I am using libxslt to process a XML file and output a plain text file and I need to insert white spaces. I have tried with   but this returns a symbol, not whitespace. I have read that this is an encoding problem but I can tell to libxslt that the output must be ISO-8859-1. I have tried with #x20, #x9, #xD and #xA without results. Thanks Jose Luis Peran From veillard@redhat.com Thu Apr 10 06:17:50 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 61AC718325 for ; Thu, 10 Apr 2003 06:17:50 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3AAHoK15065; Thu, 10 Apr 2003 06:17:50 -0400 Date: Thu, 10 Apr 2003 06:17:50 -0400 From: Daniel Veillard To: xslt@gnome.org, srperan@sherlock.dif.um.es Cc: dsevilla@ditec.um.es Subject: Re: [xslt] Question about white space output Message-ID: <20030410061749.C28785@redhat.com> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030410094416.GB22874@sherlock.dif.um.es>; from srperan@sherlock.dif.um.es on Thu, Apr 10, 2003 at 11:44:16AM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 11:44:16AM +0200, srperan@sherlock.dif.um.es wrote: > Hello. I am using libxslt to process a XML file and output a plain text > file and I need to insert white spaces. I have tried with >   but this returns a symbol, not whitespace. What symbol ? This is probably equivalent to the   > I have read that this is an encoding problem Where ? how ? by whom ? Pointer please ! If someone think there is a bug in libxslt, he better state it clearly and give a full example, you included ! Have you read http://xmlsoft.org/XSLT/bugs.html ? If yes why didn't you follow the guidelines "send the command showing the error as well as the input and stylesheet" > but I can tell to libxslt that the > output must be ISO-8859-1. Your report is terribly unprecise. You "can" or you "did" ask for ISO-8859-1 ? You don't even tell what kind of output you asked for, xml ? html ? text ? I doubt it's a bug, on the other hand you sound very confused. And your report contains no way to check what you're trying to argue about, nor even to try to get an idea of what exactly is the problem. As a result we are both loosing time :-( . Follow the guidelines, they are there for good reasons ! Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From srperan@sherlock.dif.um.es Thu Apr 10 07:29:29 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from unimur.um.es (unknown [155.54.1.1]) by mail.gnome.org (Postfix) with ESMTP id 5B49A188E1 for ; Thu, 10 Apr 2003 07:29:28 -0400 (EDT) Received: from sherlock (sherlock.dif.um.es [155.54.15.166]) by unimur.um.es (8.9.1b+Sun/8.9.1) with ESMTP id NAA13090 for ; Thu, 10 Apr 2003 13:29:27 +0200 (MEST) From: srperan@sherlock.dif.um.es Received: from srperan by sherlock with local (Exim 3.36 #1 (Debian)) id 193aKJ-000640-00 for ; Thu, 10 Apr 2003 13:34:43 +0200 Date: Thu, 10 Apr 2003 13:34:42 +0200 To: xslt@gnome.org Subject: Re: [xslt] Question about white space output Message-ID: <20030410113442.GA23217@sherlock.dif.um.es> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030410061749.C28785@redhat.com> User-Agent: Mutt/1.5.3i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Well, maybe I did not explain correctly. Excuse me, but my english is not very good. I have a XML file, and I use libxslt to process it. The output is a TEXT file. I want to insert white spaces into the output TEXT file. I am not talking about a libxslt bug. I am just asking how to do it. I have been reading past messages and I have seen similar questions, but I think those questions was not regarding a TEXT output. I will be more explicit. We have this XML piece : and using this template, we want to obtain a TEXT output: typedef sequence <, > ; sequence <, > sequence <, > When we process this, we obtain this output : typedef sequence < sequence < sequence < long >>>secuencia2; When we need : typedef sequence < sequence < sequence < long > > > secuencia2; Now, the question is, how can I insert the white spaces between symbols? symbols? Thank You. Jose Luis Peran Daniel Veillard wrote: > On Thu, Apr 10, 2003 at 11:44:16AM +0200, srperan@sherlock.dif.um.es wrote: > > Hello. I am using libxslt to process a XML file and output a plain text > > file and I need to insert white spaces. I have tried with > >   but this returns a symbol, not whitespace. > > What symbol ? This is probably equivalent to the   > > > I have read that this is an encoding problem > > Where ? how ? by whom ? Pointer please ! If someone think there is a bug > in libxslt, he better state it clearly and give a full example, you > included ! Have you read http://xmlsoft.org/XSLT/bugs.html ? If yes > why didn't you follow the guidelines > "send the command showing the error as well as the input and stylesheet" > > > but I can tell to libxslt that the > > output must be ISO-8859-1. > > Your report is terribly unprecise. You "can" or you "did" ask for > ISO-8859-1 ? > You don't even tell what kind of output you asked for, xml ? html ? text ? > I doubt it's a bug, on the other hand you sound very confused. And your > report contains no way to check what you're trying to argue about, nor > even to try to get an idea of what exactly is the problem. As a result > we are both loosing time :-( . Follow the guidelines, they are there for > good reasons ! > > Daniel > > -- > Daniel Veillard | Red Hat Network https://rhn.redhat.com/ > veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ > http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt From rm@mh-freiburg.de Thu Apr 10 07:42:28 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from forte.mh-freiburg.de (mail.mh-freiburg.de [193.197.131.2]) by mail.gnome.org (Postfix) with ESMTP id A45171858A for ; Thu, 10 Apr 2003 07:42:27 -0400 (EDT) Received: from forte (forte [127.0.0.1]) by forte.mh-freiburg.de (Postfix) with ESMTP id E925E1B334A for ; Thu, 10 Apr 2003 13:42:26 +0200 (MEST) Received: from forte.mh-freiburg.de (forte [127.0.0.1]) by forte (AvMailGate-2.0.1.10) id 04456-0AEF6985; Thu, 10 Apr 2003 13:41:49 +0200 Received: by forte.mh-freiburg.de (Postfix, from userid 104) id BD0991B334A; Thu, 10 Apr 2003 13:41:49 +0200 (MEST) Date: Thu, 10 Apr 2003 13:41:49 +0200 To: xslt@gnome.org Subject: Re: [xslt] Question about white space output Message-ID: <20030410134149.A29152@forte.mh-freiburg.de> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> <20030410113442.GA23217@sherlock.dif.um.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <20030410113442.GA23217@sherlock.dif.um.es>; from srperan@sherlock.dif.um.es on Thu, Apr 10, 2003 at 01:34:42PM +0200 From: rm@mh-freiburg.de (Le grande pinguin) X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.10; AVE: 6.19.0.3; VDF: 6.19.0.6; host: forte) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 01:34:42PM +0200, srperan@sherlock.dif.um.es wrote: > Well, maybe I did not explain correctly. Excuse me, but my english is > not very good. No need to apologize, o lot of us aren't native speakers. But (IMHU) Daniel's main point was: be precise in what you provide as context information. Best: provide a small (but complete!, see below) sample case that demonstrates the problem (input, stylefile, output, expected output). Also, since this is _not_ a "general tipps and help for XSLT" mailing list: have you tested your data with other XSLT processors and do they give different output? If not there's a good chance that your XSLT is incorrect. > I have a XML file, and I use libxslt to process it. The output is a TEXT > file. > I want to insert white spaces into the output TEXT file. > I am not talking about a libxslt bug. I am just asking how to do it. > > I have been reading past messages and I have seen similar questions, but > I think those questions was not regarding a TEXT output. > I will be more explicit. We have this XML piece : > > > > > > > > > > > and using this template, we want to obtain a TEXT output: This is _not_ enough! There's the stylesheet tag missing. Even more important: what's the value of the 'method' attribute of the 'xsl:output' tag (you _did_ use a 'method' attribute, or?). > > > typedef sequence < select="sequence"/>, select="@max"/> > select="@name"/>; > sequence < select="@type"/>, select="@max"/> > > sequence < select="sequence"/>, > > > > > > > > When we process this, we obtain this output : > > typedef sequence < sequence < sequence < long >>>secuencia2; > > When we need : > > typedef sequence < sequence < sequence < long > > > secuencia2; > > Now, the question is, how can I insert the white spaces between symbols? > symbols? Hmm, hmmm: > There's whitespace at the beginning and end of the text node .... Depending on your output method that's dangerous. How about: > hth Ralf Mattes > > Thank You. > > Jose Luis Peran > > > > > > Daniel Veillard wrote: > > On Thu, Apr 10, 2003 at 11:44:16AM +0200, srperan@sherlock.dif.um.es wrote: > > > Hello. I am using libxslt to process a XML file and output a plain text > > > file and I need to insert white spaces. I have tried with > > >   but this returns a symbol, not whitespace. > > > > What symbol ? This is probably equivalent to the   > > > > > I have read that this is an encoding problem > > > > Where ? how ? by whom ? Pointer please ! If someone think there is a bug > > in libxslt, he better state it clearly and give a full example, you > > included ! Have you read http://xmlsoft.org/XSLT/bugs.html ? If yes > > why didn't you follow the guidelines > > "send the command showing the error as well as the input and stylesheet" > > > > > but I can tell to libxslt that the > > > output must be ISO-8859-1. > > > > Your report is terribly unprecise. You "can" or you "did" ask for > > ISO-8859-1 ? > > You don't even tell what kind of output you asked for, xml ? html ? text ? > > I doubt it's a bug, on the other hand you sound very confused. And your > > report contains no way to check what you're trying to argue about, nor > > even to try to get an idea of what exactly is the problem. As a result > > we are both loosing time :-( . Follow the guidelines, they are there for > > good reasons ! > > > > Daniel > > > > -- > > Daniel Veillard | Red Hat Network https://rhn.redhat.com/ > > veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ > > http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ > > _______________________________________________ > > xslt mailing list, project page http://xmlsoft.org/XSLT/ > > xslt@gnome.org > > http://mail.gnome.org/mailman/listinfo/xslt > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt From srperan@sherlock.dif.um.es Thu Apr 10 07:57:52 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from unimur.um.es (unimur.um.es [155.54.1.1]) by mail.gnome.org (Postfix) with ESMTP id BD88C1817C for ; Thu, 10 Apr 2003 07:57:46 -0400 (EDT) Received: from sherlock (sherlock.dif.um.es [155.54.15.166]) by unimur.um.es (8.9.1b+Sun/8.9.1) with ESMTP id NAA14640 for ; Thu, 10 Apr 2003 13:57:42 +0200 (MEST) From: srperan@sherlock.dif.um.es Received: from srperan by sherlock with local (Exim 3.36 #1 (Debian)) id 193ale-000654-00 for ; Thu, 10 Apr 2003 14:02:58 +0200 Date: Thu, 10 Apr 2003 14:02:58 +0200 To: xslt@gnome.org Subject: Re: [xslt] Question about white space output Message-ID: <20030410120258.GA23360@sherlock.dif.um.es> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> <20030410113442.GA23217@sherlock.dif.um.es> <20030410134149.A29152@forte.mh-freiburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030410134149.A29152@forte.mh-freiburg.de> User-Agent: Mutt/1.5.3i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 01:41:49PM +0200, Le grande pinguin wrote: > On Thu, Apr 10, 2003 at 01:34:42PM +0200, srperan@sherlock.dif.um.es wrote: > > Well, maybe I did not explain correctly. Excuse me, but my english is > > not very good. > > No need to apologize, o lot of us aren't native speakers. > But (IMHU) Daniel's main point was: be precise in what you provide > as context information. Best: provide a small (but complete!, see below) > sample case that demonstrates the problem (input, stylefile, output, > expected output). Also, since this is _not_ a "general tipps and > help for XSLT" mailing list: have you tested your data with other > XSLT processors and do they give different output? If not there's a good > chance that your XSLT is incorrect. > I know this list is not a help list, but I am two days with this and I need to solve this, so I though I can ask here. I have tried with xalan, but I obtain a parse error (This error is strange because I obtain the error in a line without errors, I have seen that). My xsl and xml filer are correct, I am sure. > > I have a XML file, and I use libxslt to process it. The output is a TEXT > > file. > > I want to insert white spaces into the output TEXT file. > > I am not talking about a libxslt bug. I am just asking how to do it. > > > > I have been reading past messages and I have seen similar questions, but > > I think those questions was not regarding a TEXT output. > > I will be more explicit. We have this XML piece : > > > > > > > > > > > > > > > > > > > > > > and using this template, we want to obtain a TEXT output: > > This is _not_ enough! There's the stylesheet tag missing. Even more > important: what's the value of the 'method' attribute of the > 'xsl:output' tag (you _did_ use a 'method' attribute, or?). > Here is the header of the XSL file : > > > > > > typedef sequence < > select="sequence"/>, > select="@max"/> > > select="@name"/>; > > sequence < > select="@type"/>, > select="@max"/> > > > sequence < > select="sequence"/>, > > > > > > > > > > > > > > > When we process this, we obtain this output : > > > > typedef sequence < sequence < sequence < long >>>secuencia2; > > > > When we need : > > > > typedef sequence < sequence < sequence < long > > > secuencia2; > > > > Now, the question is, how can I insert the white spaces between symbols? > > symbols? > > > Hmm, hmmm: > > > > There's whitespace at the beginning and end of the text node .... > Depending on your output method that's dangerous. How about: > > > > > It doesnt work :( > hth Ralf Mattes > > > > Thank You. > > > > Jose Luis Peran > > > > > > > > > > > > Daniel Veillard wrote: > > > On Thu, Apr 10, 2003 at 11:44:16AM +0200, srperan@sherlock.dif.um.es wrote: > > > > Hello. I am using libxslt to process a XML file and output a plain text > > > > file and I need to insert white spaces. I have tried with > > > >   but this returns a symbol, not whitespace. > > > > > > What symbol ? This is probably equivalent to the   > > > > > > > I have read that this is an encoding problem > > > > > > Where ? how ? by whom ? Pointer please ! If someone think there is a bug > > > in libxslt, he better state it clearly and give a full example, you > > > included ! Have you read http://xmlsoft.org/XSLT/bugs.html ? If yes > > > why didn't you follow the guidelines > > > "send the command showing the error as well as the input and stylesheet" > > > > > > > but I can tell to libxslt that the > > > > output must be ISO-8859-1. > > > > > > Your report is terribly unprecise. You "can" or you "did" ask for > > > ISO-8859-1 ? > > > You don't even tell what kind of output you asked for, xml ? html ? text ? > > > I doubt it's a bug, on the other hand you sound very confused. And your > > > report contains no way to check what you're trying to argue about, nor > > > even to try to get an idea of what exactly is the problem. As a result > > > we are both loosing time :-( . Follow the guidelines, they are there for > > > good reasons ! > > > > > > Daniel > > > > > > -- > > > Daniel Veillard | Red Hat Network https://rhn.redhat.com/ > > > veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ > > > http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ > > > _______________________________________________ > > > xslt mailing list, project page http://xmlsoft.org/XSLT/ > > > xslt@gnome.org > > > http://mail.gnome.org/mailman/listinfo/xslt > > _______________________________________________ > > xslt mailing list, project page http://xmlsoft.org/XSLT/ > > xslt@gnome.org > > http://mail.gnome.org/mailman/listinfo/xslt > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt From veillard@redhat.com Thu Apr 10 08:03:25 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 0A4921817C for ; Thu, 10 Apr 2003 08:03:25 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3AC3OL03955 for xslt@gnome.org; Thu, 10 Apr 2003 08:03:24 -0400 Date: Thu, 10 Apr 2003 08:03:24 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Question about white space output Message-ID: <20030410080324.D28785@redhat.com> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> <20030410113442.GA23217@sherlock.dif.um.es> <20030410134149.A29152@forte.mh-freiburg.de> <20030410120258.GA23360@sherlock.dif.um.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030410120258.GA23360@sherlock.dif.um.es>; from srperan@sherlock.dif.um.es on Thu, Apr 10, 2003 at 02:02:58PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 02:02:58PM +0200, srperan@sherlock.dif.um.es wrote: > > This is _not_ enough! There's the stylesheet tag missing. Even more > > important: what's the value of the 'method' attribute of the > > 'xsl:output' tag (you _did_ use a 'method' attribute, or?). > > > > Here is the header of the XSL file : > > xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > > > > provide the input and stayle sheets in full forms as attachement if you want me to look at this. I wrote it in the page, I asked it by mail. If you don't want to spend the time to follow the instruction why should I spend the time to look at your problem ? This is really irritating :-( Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From morus@tanto-xipolis.de Thu Apr 10 08:07:51 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.tanto-xipolis.de (mail.xipolis.net [213.61.178.42]) by mail.gnome.org (Postfix) with ESMTP id DEB341884D for ; Thu, 10 Apr 2003 08:07:50 -0400 (EDT) Received: from morus.xipolis.net (unknown [10.0.1.4]) by mail.tanto-xipolis.de (Postfix on SuSE Linux 7.3 (i386)) with ESMTP id 9EBC919B718; Thu, 10 Apr 2003 14:07:49 +0200 (CEST) Received: (from morus@localhost) by morus.xipolis.net (8.11.6/8.11.6/SuSE Linux 0.5) id h3AC83418897; Thu, 10 Apr 2003 14:08:03 +0200 From: Morus Walter MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <16021.24227.629044.347232@morus.xipolis.net> Date: Thu, 10 Apr 2003 14:08:03 +0200 To: xslt@gnome.org Cc: srperan@sherlock.dif.um.es Subject: Re: [xslt] Question about white space output In-Reply-To: <20030410113442.GA23217@sherlock.dif.um.es> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> <20030410113442.GA23217@sherlock.dif.um.es> X-Mailer: VM 6.95 under 21.4 (patch 4) "Artificial Intelligence" XEmacs Lucid Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: srperan@sherlock.dif.um.es writes: > When we process this, we obtain this output : >=20 > typedef sequence < sequence < sequence < long >>>secuencia2; >=20 > When we need : >=20 > typedef sequence < sequence < sequence < long > > > secuencia2; >=20 > Now, the question is, how can I insert the white spaces between symbo= ls? > symbols? >=20 Well, this is basically a xslt question and is more suited to a general= xslt mailing list than to this list, which is specifically on libxslt. Unfortunately you left out relevant information again (what output-enco= ding does your stylesheet provide? How do you process?) Using copy & paste from your mail and adding what's needed I get =09typedef sequence <, > ; =09=09sequence <, > =09=09=09sequence <, =09=09=09> =09=09=09 =09=09=09 and xsltproc (2.5.4) gives typedef sequence > > secuencia2; which isn't what you want, but isn't what you get either. I guess your stylesheet got modified during mail. If I use=20 =20 =09typedef sequence < , > ; =09=09sequence < , > =09=09=09sequence < , =09=09=09 > = =09=09=09 I get typedef sequence < sequence < sequence < long > > > secuencia2; which seems to be what you want (unless you have a problem with two blanks). If you didn't specify ISO-8859-1 output encoding it's no surpise that you found something like '=C2 ' for nbsp since the default encoding is utf8 and that's nbsp's utf8 represantation. So it's just adding the WS to the text in the stylesheet apropiatly. (And perhaps knowing that pure whitespace between elements should be put into ...; otherwise it's removed). HTH =09Morus From srperan@sherlock.dif.um.es Thu Apr 10 11:54:03 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from unimur.um.es (unknown [155.54.1.1]) by mail.gnome.org (Postfix) with ESMTP id BFBD61826D for ; Thu, 10 Apr 2003 11:54:02 -0400 (EDT) Received: from sherlock (sherlock.dif.um.es [155.54.15.166]) by unimur.um.es (8.9.1b+Sun/8.9.1) with ESMTP id RAA26835 for ; Thu, 10 Apr 2003 17:54:01 +0200 (MEST) From: srperan@sherlock.dif.um.es Received: from srperan by sherlock with local (Exim 3.36 #1 (Debian)) id 193eSN-0006My-00 for ; Thu, 10 Apr 2003 17:59:19 +0200 Date: Thu, 10 Apr 2003 17:59:19 +0200 To: xslt@gnome.org Subject: Re: [xslt] Question about white space output Message-ID: <20030410155919.GA24152@sherlock.dif.um.es> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> <20030410113442.GA23217@sherlock.dif.um.es> <16021.24227.629044.347232@morus.xipolis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16021.24227.629044.347232@morus.xipolis.net> User-Agent: Mutt/1.5.3i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 02:08:03PM +0200, Morus Walter wrote: > > If I use > > > > > > > > typedef sequence < select="sequence"/>, select="@max"/> > select="@name"/>; > sequence < select="@type"/>, select="@max"/> > > sequence < select="sequence"/>, > > > > > > > I get > typedef sequence < sequence < sequence < long > > > secuencia2; > which seems to be what you want (unless you have a problem with two > blanks). Yes, that is the output I obtain with xsltproc, but when I use my program, it returns an incorrect output. Maybe I have some mistake in my parsing code, but I dont see it. My code just check xml file with a dtd, parse file and process the file with libxslt. I dont see where can be the problem. Can you help me, please? Thanks Jose Luis Peran > > If you didn't specify ISO-8859-1 output encoding it's no surpise that > you found something like '? ' for nbsp since the default encoding is > utf8 and that's nbsp's utf8 represantation. > I specify ISO-8859-1 encoding, so this is not the problem > So it's just adding the WS to the text in the stylesheet apropiatly. > (And perhaps knowing that pure whitespace between elements should be > put into ...; otherwise it's removed). > I have added ... and it doesnt correct the problem. > HTH > Morus > _______________________________________________ From rm@mh-freiburg.de Thu Apr 10 12:02:56 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from forte.mh-freiburg.de (mail.mh-freiburg.de [193.197.131.2]) by mail.gnome.org (Postfix) with ESMTP id 002F31835C for ; Thu, 10 Apr 2003 12:02:55 -0400 (EDT) Received: from forte (forte [127.0.0.1]) by forte.mh-freiburg.de (Postfix) with ESMTP id 758051B3347 for ; Thu, 10 Apr 2003 18:02:55 +0200 (MEST) Received: from forte.mh-freiburg.de (forte [127.0.0.1]) by forte (AvMailGate-2.0.1.10) id 08344-6D1A0CE2; Thu, 10 Apr 2003 18:02:10 +0200 Received: by forte.mh-freiburg.de (Postfix, from userid 104) id A8A971B3347; Thu, 10 Apr 2003 18:02:10 +0200 (MEST) Date: Thu, 10 Apr 2003 18:02:10 +0200 To: xslt@gnome.org Subject: Re: [xslt] Question about white space output Message-ID: <20030410180210.A9654@forte.mh-freiburg.de> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> <20030410113442.GA23217@sherlock.dif.um.es> <16021.24227.629044.347232@morus.xipolis.net> <20030410155919.GA24152@sherlock.dif.um.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <20030410155919.GA24152@sherlock.dif.um.es>; from srperan@sherlock.dif.um.es on Thu, Apr 10, 2003 at 05:59:19PM +0200 From: rm@mh-freiburg.de (Le grande pinguin) X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.10; AVE: 6.19.0.3; VDF: 6.19.0.6; host: forte) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 05:59:19PM +0200, srperan@sherlock.dif.um.es wrote: > > Yes, that is the output I obtain with xsltproc, but when I use my > program, it returns an incorrect output. Maybe I have some mistake in my > parsing code, but I dont see it. > > My code just check xml file with a dtd, parse file and process the file > with libxslt. I dont see where can be the problem. > Can you help me, please? Not without the neccessary information. This is the first time you tell us that there is a custom program involved. Where's the code? Can you reduce the code to a minimal example that exposes the problem? How actually do you serialize the document (i _assume_ we are talking about an xmlDocPtr here, or?). ralf mattes > Thanks > Jose Luis Peran > > > > > If you didn't specify ISO-8859-1 output encoding it's no surpise that > > you found something like '? ' for nbsp since the default encoding is > > utf8 and that's nbsp's utf8 represantation. > > > > I specify ISO-8859-1 encoding, so this is not the problem > > > So it's just adding the WS to the text in the stylesheet apropiatly. > > (And perhaps knowing that pure whitespace between elements should be > > put into ...; otherwise it's removed). > > > > I have added ... and it doesnt correct the problem. > > > HTH > > Morus > > _______________________________________________ > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt From srperan@sherlock.dif.um.es Thu Apr 10 12:41:40 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from unimur.um.es (unknown [155.54.1.1]) by mail.gnome.org (Postfix) with ESMTP id 73F2518213 for ; Thu, 10 Apr 2003 12:41:39 -0400 (EDT) Received: from sherlock (sherlock.dif.um.es [155.54.15.166]) by unimur.um.es (8.9.1b+Sun/8.9.1) with ESMTP id SAA29884 for ; Thu, 10 Apr 2003 18:41:35 +0200 (MEST) From: srperan@sherlock.dif.um.es Received: from srperan by sherlock with local (Exim 3.36 #1 (Debian)) id 193fCP-0006Qe-00 for ; Thu, 10 Apr 2003 18:46:53 +0200 Date: Thu, 10 Apr 2003 18:46:53 +0200 To: xslt@gnome.org Subject: Re: [xslt] Question about white space output Message-ID: <20030410164653.GA24674@sherlock.dif.um.es> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> <20030410113442.GA23217@sherlock.dif.um.es> <16021.24227.629044.347232@morus.xipolis.net> <20030410155919.GA24152@sherlock.dif.um.es> <20030410180210.A9654@forte.mh-freiburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20030410180210.A9654@forte.mh-freiburg.de> User-Agent: Mutt/1.5.3i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 06:02:10PM +0200, Le grande pinguin wrote: > On Thu, Apr 10, 2003 at 05:59:19PM +0200, srperan@sherlock.dif.um.es wrote: > > > > Yes, that is the output I obtain with xsltproc, but when I use my > > program, it returns an incorrect output. Maybe I have some mistake in my > > parsing code, but I dont see it. > > > > My code just check xml file with a dtd, parse file and process the file > > with libxslt. I dont see where can be the problem. > > Can you help me, please? > > Not without the neccessary information. This is the first time you > tell us that there is a custom program involved. Where's the code? > Can you reduce the code to a minimal example that exposes the problem? > How actually do you serialize the document (i _assume_ we are talking > about an xmlDocPtr here, or?). > > ralf mattes I really apologize, my brain is too hot today after too many hours thinking about it and I dont say you important info. Please, forgive me. This is the basic code for the parsing : int XSLTProcess::convert() { // process the input file and get the converted file through stdout xsltStylesheetPtr cur; xmlDocPtr doc, res; const char *params[16 + 1]; params[0] = NULL; //Read the stylesheet cur = xsltParseStylesheetFile(inputXSLFile); //Get the xmlDoctr doc = inputXMLTree.getXMLDoc(); // if (cur == NULL) // cout << "hola mundo\n\n"; //Apply stylesheet res = xsltApplyStylesheet(cur, doc, params); //and save the output file xsltSaveResultToFile(stdout, res, cur); } I think you see the basic source. It´s easy to understand. The main function, creates a XSLTProcess instance and calls to convert. When creating the XSLTProcess instance, it creares a XMLTree instance with the following constructor : XMLTree::XMLTree(char *xmlfile) throw ( XMLDocumentException ) { char *dtdfile = "./xmlfiles/dtdidl.dtd"; //Create a XMLTree object that contain a sintax tree of xmlfile doc = xmlParseFile(xmlfile); //Validate the xml file with the dtd file if ( !ValidateFileWithDTD ( dtdfile ) ) throw XMLDocumentException("The XML document isn't correct.\n"); if (doc == NULL) //if doc == NULL the document is not correct throw XMLDocumentException("I can't parse the XML document"); root = xmlDocGetRootElement(doc); }; The function ValidateFileWithDTD just do that. It´s simple, and I dont see the problem. Lots of thanks again, and again, forgive me > > Thanks > > Jose Luis Peran > > > > > > > > If you didn't specify ISO-8859-1 output encoding it's no surpise that > > > you found something like '? ' for nbsp since the default encoding is > > > utf8 and that's nbsp's utf8 represantation. > > > > > > > I specify ISO-8859-1 encoding, so this is not the problem > > > > > So it's just adding the WS to the text in the stylesheet apropiatly. > > > (And perhaps knowing that pure whitespace between elements should be > > > put into ...; otherwise it's removed). > > > > > > > I have added ... and it doesnt correct the problem. > > > > > HTH > > > Morus > > > _______________________________________________ > > _______________________________________________ > > xslt mailing list, project page http://xmlsoft.org/XSLT/ > > xslt@gnome.org > > http://mail.gnome.org/mailman/listinfo/xslt > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt From igor@zlatkovic.com Thu Apr 10 12:42:17 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from post.webmailer.de (natsmtp00.webmailer.de [192.67.198.74]) by mail.gnome.org (Postfix) with ESMTP id 7837818376 for ; Thu, 10 Apr 2003 12:42:17 -0400 (EDT) Received: from mail.zlatkovic.com (pD951B59D.dip.t-dialin.net [217.81.181.157]) by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h3AGgGbw000950 for ; Thu, 10 Apr 2003 18:42:16 +0200 (MEST) Received: from 192.168.9.71 (ident=unknown) by mail.zlatkovic.com with esmtp (MasqMail 0.1.16) id 193f7v-7ok-00 for xslt@gnome.org; Thu, 10 Apr 2003 18:42:15 +0200 Message-ID: <3E959EE6.9050306@zlatkovic.com> Date: Thu, 10 Apr 2003 18:42:14 +0200 From: Igor Zlatkovic User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-gb, en MIME-Version: 1.0 To: xslt@gnome.org Subject: Re: [xslt] Question about white space output References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> <20030410113442.GA23217@sherlock.dif.um.es> <16021.24227.629044.347232@morus.xipolis.net> <20030410155919.GA24152@sherlock.dif.um.es> In-Reply-To: <20030410155919.GA24152@sherlock.dif.um.es> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: srperan@sherlock.dif.um.es wrote: > Yes, that is the output I obtain with xsltproc, but when I use my > program, it returns an incorrect output. Maybe I have some mistake in my > parsing code, but I dont see it. > > My code just check xml file with a dtd, parse file and process the file > with libxslt. I dont see where can be the problem. > Can you help me, please? Okay, I think I have understood what you need. Why bother with the complicated oddities of various software packages? Why bang your head against the wall for problems that just won't solve themselves? Sit back, relax and let an expirienced professional ban the demon in an instant. An uncomplicated and fast consulting service will save you a lot of headaches and money. Just have your breakfast and read your favourite newspapers, a skilled consultant will solve your problems before your coffee gets cold! Please contact me with a formal inquiry and in a week, you'll hardly remember anything was ever wrong. :-) PS: I charge 120 EUR per hour plus applicable taxes and expenses. PPS: If my bayesian filter doesn't fire on this message, then I'll have to practice this for a while :-) From aduhon@firstam.com Thu Apr 10 14:32:12 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from fada1smt02.firstam-reis.com (mail2.firstam-reis.com [206.103.66.183]) by mail.gnome.org (Postfix) with ESMTP id ED1AB183C2 for ; Thu, 10 Apr 2003 14:32:11 -0400 (EDT) Received: from fada1sxc02.firstam-reis.com (fada1sxc02.firstam-reis.com [172.16.3.2]) by fada1smt02.FirstAm-REIS.com (PMDF V6.1-1 #40534) with ESMTP id <0HD5008D54OWE0@fada1smt02.FirstAm-REIS.com> for xslt@gnome.org; Thu, 10 Apr 2003 13:29:20 -0500 (CDT) Received: by fada1sxc02.firstam-reis.com with Internet Mail Service (5.5.2653.19) id <2NVWHT1L>; Thu, 10 Apr 2003 13:32:09 -0500 Content-return: allowed Date: Thu, 10 Apr 2003 13:32:07 -0500 From: "Duhon, Andrew" To: "'xslt@gnome.org'" Message-id: MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: multipart/alternative; boundary="Boundary_(ID_gkNQ0eApz37UtpNRHxepiw)" Subject: [xslt] xsltApplyOneTemplate Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --Boundary_(ID_gkNQ0eApz37UtpNRHxepiw) Content-type: text/plain Content-transfer-encoding: 7BIT Hi, I am having a problem with applying a stylesheet. Most of the xml docs and stylesheets we are using are processed in a relatively short time, less than a second. However we have on the at is taking almost a minute. I have traced it down to the xsltApplOneTemplate being called over 39,000 times. What I am trying to figure out is if it is the complexity of the xml or the complexity of the stylesheet that is causing this. Any feedback would be greatly appreciated. Andy --Boundary_(ID_gkNQ0eApz37UtpNRHxepiw) Content-type: text/html Content-transfer-encoding: 7BIT xsltApplyOneTemplate

Hi,
        I am having a problem with applying a stylesheet. Most of the xml docs and stylesheets we are using are processed in a relatively short time, less than a second. However we have on the at is taking almost a minute. I have traced it down to the xsltApplOneTemplate being called over 39,000 times. What I am trying to figure out is if it is the complexity of the xml or the complexity of the stylesheet that is causing this. Any feedback would be greatly appreciated.

Andy

--Boundary_(ID_gkNQ0eApz37UtpNRHxepiw)-- From veillard@redhat.com Thu Apr 10 15:54:07 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 510751894C for ; Thu, 10 Apr 2003 15:54:07 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3AJs6217249 for xslt@gnome.org; Thu, 10 Apr 2003 15:54:06 -0400 Date: Thu, 10 Apr 2003 15:54:06 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] xsltApplyOneTemplate Message-ID: <20030410155406.O28785@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from aduhon@firstam.com on Thu, Apr 10, 2003 at 01:32:07PM -0500 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 01:32:07PM -0500, Duhon, Andrew wrote: > Hi, > I am having a problem with applying a stylesheet. Most of the xml > docs and stylesheets we are using are processed in a relatively short time, > less than a second. However we have on the at is taking almost a minute. I > have traced it down to the xsltApplOneTemplate being called over 39,000 > times. What I am trying to figure out is if it is the complexity of the xml > or the complexity of the stylesheet that is causing this. Any feedback would > be greatly appreciated. Without any useful data, the answer is "both" Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From srperan@sherlock.dif.um.es Fri Apr 11 04:55:21 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from unimur.um.es (unknown [155.54.1.1]) by mail.gnome.org (Postfix) with ESMTP id 8427218500 for ; Fri, 11 Apr 2003 04:55:16 -0400 (EDT) Received: from sherlock (sherlock.dif.um.es [155.54.15.166]) by unimur.um.es (8.9.1b+Sun/8.9.1) with ESMTP id KAA08050 for ; Fri, 11 Apr 2003 10:55:12 +0200 (MEST) From: srperan@sherlock.dif.um.es Received: from srperan by sherlock with local (Exim 3.36 #1 (Debian)) id 193uOl-0006pH-00 for ; Fri, 11 Apr 2003 11:00:39 +0200 Date: Fri, 11 Apr 2003 11:00:39 +0200 To: xslt@gnome.org Subject: Re: [xslt] xsltApplyOneTemplate Message-ID: <20030411090039.GA26178@sherlock.dif.um.es> References: <20030410155406.O28785@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030410155406.O28785@redhat.com> User-Agent: Mutt/1.5.3i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 03:54:06PM -0400, Daniel Veillard wrote: > On Thu, Apr 10, 2003 at 01:32:07PM -0500, Duhon, Andrew wrote: > > Hi, > > I am having a problem with applying a stylesheet. Most of the xml > > docs and stylesheets we are using are processed in a relatively short time, > > less than a second. However we have on the at is taking almost a minute. I > > have traced it down to the xsltApplOneTemplate being called over 39,000 > > times. What I am trying to figure out is if it is the complexity of the xml > > or the complexity of the stylesheet that is causing this. Any feedback would > > be greatly appreciated. > > Without any useful data, the answer is "both" > > Daniel > > Yes, in this list you must paste your social security number, shoes size and at least the 80% of your source code if you want an answer. -- > Daniel Veillard | Red Hat Network https://rhn.redhat.com/ > veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ > http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt From veillard@redhat.com Fri Apr 11 05:19:37 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 00E0618444 for ; Fri, 11 Apr 2003 05:19:36 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3B9Ja920199 for xslt@gnome.org; Fri, 11 Apr 2003 05:19:36 -0400 Date: Fri, 11 Apr 2003 05:19:36 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] xsltApplyOneTemplate Message-ID: <20030411051936.P28785@redhat.com> References: <20030410155406.O28785@redhat.com> <20030411090039.GA26178@sherlock.dif.um.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030411090039.GA26178@sherlock.dif.um.es>; from srperan@sherlock.dif.um.es on Fri, Apr 11, 2003 at 11:00:39AM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 11, 2003 at 11:00:39AM +0200, srperan@sherlock.dif.um.es wrote: > On Thu, Apr 10, 2003 at 03:54:06PM -0400, Daniel Veillard wrote: > > On Thu, Apr 10, 2003 at 01:32:07PM -0500, Duhon, Andrew wrote: > > > Hi, > > > I am having a problem with applying a stylesheet. Most of the xml > > > docs and stylesheets we are using are processed in a relatively short time, > > > less than a second. However we have on the at is taking almost a minute. I > > > have traced it down to the xsltApplOneTemplate being called over 39,000 > > > times. What I am trying to figure out is if it is the complexity of the xml > > > or the complexity of the stylesheet that is causing this. Any feedback would > > > be greatly appreciated. > > > > Without any useful data, the answer is "both" > > Yes, in this list you must paste your social security number, shoes size not having the slightliest idea of what his data looks like nor for the stylesheet, it's completely impossible to give any informations about performance results. So it's generic information about XSLT performances, and yes it heavilly depends BOTH on the stylesheet AND on the data processed (and the software used to do the XSLT transformation). The exact same question uneditaed could have been posted on any other XSLT related mailing-list there is nothing specific to libxslt in the question and nothing allowing to make a more precise answer. > and at least the 80% of your source code if you want an answer. That's your point of view, not mine. I simply don't have time to debug code from people using the libraries. I state that very clearly, don't send me code unless it's obvious I won't spend time examining it because I simply can't. The only thing I immediately noticed in your code is that it's a memory leak generator, you never seem to free the structures used, even when they are only referenced as local variable and not passed on exit of the function. Again I don't have time to debug other's people code, I think I do already quite enough for the community and I need to sleep sometimes. So take your rant back, use a debugger and stop whining. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From rm@mh-freiburg.de Fri Apr 11 06:01:35 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from forte.mh-freiburg.de (mail.mh-freiburg.de [193.197.131.2]) by mail.gnome.org (Postfix) with ESMTP id 7668A183DE for ; Fri, 11 Apr 2003 06:01:35 -0400 (EDT) Received: from forte (forte [127.0.0.1]) by forte.mh-freiburg.de (Postfix) with ESMTP id 08E7B1B3347 for ; Fri, 11 Apr 2003 12:01:35 +0200 (MEST) Received: from forte.mh-freiburg.de (forte [127.0.0.1]) by forte (AvMailGate-2.0.1.10) id 24749-2543F5DE; Fri, 11 Apr 2003 12:01:15 +0200 Received: by forte.mh-freiburg.de (Postfix, from userid 104) id 015221B3347; Fri, 11 Apr 2003 12:01:14 +0200 (MEST) Date: Fri, 11 Apr 2003 12:01:14 +0200 To: xslt@gnome.org Subject: Re: [xslt] Question about white space output Message-ID: <20030411120114.A23164@forte.mh-freiburg.de> References: <20030410083807.14118.27712.Mailman@moniker.gnome.org> <20030410094416.GB22874@sherlock.dif.um.es> <20030410061749.C28785@redhat.com> <20030410113442.GA23217@sherlock.dif.um.es> <16021.24227.629044.347232@morus.xipolis.net> <20030410155919.GA24152@sherlock.dif.um.es> <20030410180210.A9654@forte.mh-freiburg.de> <20030410164653.GA24674@sherlock.dif.um.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <20030410164653.GA24674@sherlock.dif.um.es>; from srperan@sherlock.dif.um.es on Thu, Apr 10, 2003 at 06:46:53PM +0200 From: rm@mh-freiburg.de (Le grande pinguin) X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.10; AVE: 6.19.0.3; VDF: 6.19.0.6; host: forte) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 10, 2003 at 06:46:53PM +0200, srperan@sherlock.dif.um.es wrote: > > [...] > > This is the basic code for the parsing : > int XSLTProcess::convert() { > // process the input file and get the converted file through stdout > > xsltStylesheetPtr cur; > xmlDocPtr doc, res; > const char *params[16 + 1]; > > params[0] = NULL; > > > > //Read the stylesheet > cur = xsltParseStylesheetFile(inputXSLFile); > > //Get the xmlDoctr > doc = inputXMLTree.getXMLDoc(); > > // if (cur == NULL) > // cout << "hola mundo\n\n"; > > //Apply stylesheet > res = xsltApplyStylesheet(cur, doc, params); > > //and save the output file Why don't you start up your debugger and set a breakpoint on the following function? Once debugger stops at the call to this function you can step in and have a look at the (xmlChar *) 'encoding' (the pointer gets set by the macro XSLT_GET_IMPORT_PTR which expands to a while loop that iterates through the linked list of imported stylesheets). > xsltSaveResultToFile(stdout, res, cur); hth Ralf Mattes From morus@tanto-xipolis.de Fri Apr 11 06:50:34 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.tanto-xipolis.de (mail.xipolis.net [213.61.178.42]) by mail.gnome.org (Postfix) with ESMTP id 5CE0018974 for ; Fri, 11 Apr 2003 06:50:34 -0400 (EDT) Received: from morus.xipolis.net (unknown [10.0.1.4]) by mail.tanto-xipolis.de (Postfix on SuSE Linux 7.3 (i386)) with ESMTP id 1FDE019B71A; Fri, 11 Apr 2003 12:50:33 +0200 (CEST) Received: (from morus@localhost) by morus.xipolis.net (8.11.6/8.11.6/SuSE Linux 0.5) id h3BAono23418; Fri, 11 Apr 2003 12:50:49 +0200 From: Morus Walter MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16022.40457.127304.338847@morus.xipolis.net> Date: Fri, 11 Apr 2003 12:50:49 +0200 To: xslt@gnome.org, srperan@sherlock.dif.um.es Subject: Re: [xslt] xsltApplyOneTemplate In-Reply-To: <20030411090039.GA26178@sherlock.dif.um.es> References: <20030410155406.O28785@redhat.com> <20030411090039.GA26178@sherlock.dif.um.es> X-Mailer: VM 6.95 under 21.4 (patch 4) "Artificial Intelligence" XEmacs Lucid Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: srperan@sherlock.dif.um.es writes: > > Yes, in this list you must paste your social security number, shoes size > and at least the 80% of your source code if you want an answer. > I suggest that you read http://www.catb.org/~esr/faqs/smart-questions.html and reconsider what you did here. HTH Morus From srperan@sherlock.dif.um.es Fri Apr 11 07:33:43 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from unimur.um.es (unknown [155.54.1.1]) by mail.gnome.org (Postfix) with ESMTP id 6D8E8180E0 for ; Fri, 11 Apr 2003 07:33:42 -0400 (EDT) Received: from sherlock (sherlock.dif.um.es [155.54.15.166]) by unimur.um.es (8.9.1b+Sun/8.9.1) with ESMTP id NAA17933 for ; Fri, 11 Apr 2003 13:33:41 +0200 (MEST) From: srperan@sherlock.dif.um.es Received: from srperan by sherlock with local (Exim 3.36 #1 (Debian)) id 193wsA-0006sb-00 for ; Fri, 11 Apr 2003 13:39:10 +0200 Date: Fri, 11 Apr 2003 13:39:10 +0200 To: xslt@gnome.org Subject: Re: [xslt] xsltApplyOneTemplate Message-ID: <20030411113910.GA26411@sherlock.dif.um.es> References: <20030410155406.O28785@redhat.com> <20030411090039.GA26178@sherlock.dif.um.es> <16022.40457.127304.338847@morus.xipolis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16022.40457.127304.338847@morus.xipolis.net> User-Agent: Mutt/1.5.3i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 11, 2003 at 12:50:49PM +0200, Morus Walter wrote: > srperan@sherlock.dif.um.es writes: > > > > Yes, in this list you must paste your social security number, shoes size > > and at least the 80% of your source code if you want an answer. > > > I suggest that you read > http://www.catb.org/~esr/faqs/smart-questions.html > and reconsider what you did here. > > HTH > Morus > Just joking. Where is your humor sense? ;) Well, This is my last post to this list and I want to say something I really hate those hackers rules, I think it is totally in the wrong way, but I will paste here one : http://www.catb.org/~esr/faqs/hacker-howto.html#believe4 Usually good hackers as probably you are, become unpleasant people. I have been subscribed to many mail list and in some of them I have been an experienced "hacker" about the list theme and when somebody ask you something you think is a stupid question you get angry with this people and say those thing like RTFM or STFW. But one day I noticed that this behaviour just took me to be in a foul mood. I found out that this was against my way of living and I decided to change. It was difficult, but it helpep me to make friends and be a better person. Thanks for your patience. I will solve my problem myself. Jose _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt From hrauch@heitec.de Fri Apr 11 08:36:24 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from christel.heitec.net (christel.heitec.net [213.70.109.3]) by mail.gnome.org (Postfix) with ESMTP id 4057318469 for ; Fri, 11 Apr 2003 08:36:23 -0400 (EDT) Received: from prag.info.er.heitec.net (paladin.heitec.net [193.101.232.30]) by christel.heitec.net (Postfix) with ESMTP id 197FAB820F; Fri, 11 Apr 2003 14:36:17 +0200 (CEST) Received: by prag.info.er.heitec.net (Postfix, from userid 1001) id 42E9D6C33; Fri, 11 Apr 2003 14:36:16 +0200 (CEST) Date: Fri, 11 Apr 2003 14:36:16 +0200 From: Holger Rauch To: xslt@gnome.org, srperan@sherlock.dif.um.es Subject: Re: [xslt] xsltApplyOneTemplate Message-ID: <20030411123616.GA5036@heitec.net> Mail-Followup-To: xslt@gnome.org, srperan@sherlock.dif.um.es References: <20030410155406.O28785@redhat.com> <20030411090039.GA26178@sherlock.dif.um.es> <16022.40457.127304.338847@morus.xipolis.net> <20030411113910.GA26411@sherlock.dif.um.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20030411113910.GA26411@sherlock.dif.um.es> User-Agent: Mutt/1.3.28i Organization: HEITEC AG Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, 11 Apr 2003, srperan@sherlock.dif.um.es wrote: > [...] > Just joking. Where is your humor sense? ;) Denying people information when they specifically ask for it has got nothing whatsoever to do with a sense of humor. It's just plain ignorance. > Well, This is my last post to this list and I want to say something > I really hate those hackers rules, These are not "hackers rules", but rather rules that ensure that the people being willing to answer questions also have time for further libxslt development. (I also found libxslt a bit difficult to handle in the beginning, but I was willing to respect that those who are subscribed to this and/or the libml2 maling list cannot spend all their time answering questions asked by those who don't want to abide by the rules. > Usually good hackers as probably you are, become unpleasant people. How can you judge people as being unpleasant without knowing them better? > I have been subscribed to many mail list and in some of them I have been > an experienced "hacker" about the list theme and when somebody ask you > something you think is a stupid question you get angry with this people > and say those thing like RTFM or STFW. I think nobody considered your question stupid. You should be able to make a distinction between a asking stupid question and not having provided relevant information (the latter applies to you). Greetings, Holger From aduhon@firstam.com Fri Apr 11 08:48:43 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from fada1smt02.firstam-reis.com (mail2.firstam-reis.com [206.103.66.183]) by mail.gnome.org (Postfix) with ESMTP id E164A189A6 for ; Fri, 11 Apr 2003 08:48:42 -0400 (EDT) Received: from fada1sxc02.firstam-reis.com (fada1sxc02.firstam-reis.com [172.16.3.2]) by fada1smt02.FirstAm-REIS.com (PMDF V6.1-1 #40534) with ESMTP id <0HD6000FEJGBPW@fada1smt02.FirstAm-REIS.com> for xslt@gnome.org; Fri, 11 Apr 2003 07:45:48 -0500 (CDT) Received: by fada1sxc02.firstam-reis.com with Internet Mail Service (5.5.2653.19) id <2NVW22ZC>; Fri, 11 Apr 2003 07:48:36 -0500 Content-return: allowed Date: Fri, 11 Apr 2003 07:48:36 -0500 From: "Duhon, Andrew" Subject: RE: [xslt] xsltApplyOneTemplate To: "'xslt@gnome.org'" , srperan@sherlock.dif.um.es Message-id: MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: multipart/alternative; boundary="Boundary_(ID_4XUWWBUXtQVatGdg4h3g1g)" Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --Boundary_(ID_4XUWWBUXtQVatGdg4h3g1g) Content-type: text/plain Content-transfer-encoding: 7BIT This is why I didn't want to join this list in the first place. I only did it to get a simple answer to a simple question. I got it. Not as detailed as I would have liked, but I do respect the gentleman's time. Regardless, this has now turned into a thread about the guy who used Daniel's response to me to as an opportunity to take a jab or joke, whichever. So I don't any option but to unsubscribe from this list. Andy p.s. Daniel I do appreciate you taking the time to respond to my post. -----Original Message----- From: Holger Rauch [mailto:holger.rauch@heitec.de] Sent: Friday, April 11, 2003 7:36 AM To: xslt@gnome.org; srperan@sherlock.dif.um.es Subject: Re: [xslt] xsltApplyOneTemplate On Fri, 11 Apr 2003, srperan@sherlock.dif.um.es wrote: > [...] > Just joking. Where is your humor sense? ;) Denying people information when they specifically ask for it has got nothing whatsoever to do with a sense of humor. It's just plain ignorance. > Well, This is my last post to this list and I want to say something I > really hate those hackers rules, These are not "hackers rules", but rather rules that ensure that the people being willing to answer questions also have time for further libxslt development. (I also found libxslt a bit difficult to handle in the beginning, but I was willing to respect that those who are subscribed to this and/or the libml2 maling list cannot spend all their time answering questions asked by those who don't want to abide by the rules. > Usually good hackers as probably you are, become unpleasant people. How can you judge people as being unpleasant without knowing them better? > I have been subscribed to many mail list and in some of them I have > been an experienced "hacker" about the list theme and when somebody > ask you something you think is a stupid question you get angry with > this people and say those thing like RTFM or STFW. I think nobody considered your question stupid. You should be able to make a distinction between a asking stupid question and not having provided relevant information (the latter applies to you). Greetings, Holger _______________________________________________ xslt mailing list, project page http://xmlsoft.org/XSLT/ xslt@gnome.org http://mail.gnome.org/mailman/listinfo/xslt --Boundary_(ID_4XUWWBUXtQVatGdg4h3g1g) Content-type: text/html Content-transfer-encoding: 7BIT RE: [xslt] xsltApplyOneTemplate

This is why I didn't want to join this list in the first place. I only did it to get a simple answer to a simple question. I got it. Not as detailed as I would have liked, but I do respect the gentleman's time. Regardless, this has now turned into a thread about the guy who used Daniel's response to me to as an opportunity to take a jab or joke, whichever. So I don't any option but to unsubscribe from this list.

Andy

p.s. Daniel I do appreciate you taking the time to respond to my post.

-----Original Message-----
From: Holger Rauch [mailto:holger.rauch@heitec.de]
Sent: Friday, April 11, 2003 7:36 AM
To: xslt@gnome.org; srperan@sherlock.dif.um.es
Subject: Re: [xslt] xsltApplyOneTemplate


On Fri, 11 Apr 2003, srperan@sherlock.dif.um.es wrote:

> [...]
> Just joking. Where is your humor sense? ;)

Denying people information when they specifically ask for it has got nothing whatsoever to do with a sense of humor. It's just plain ignorance.

> Well, This is my last post to this list and I want to say something I
> really hate those hackers rules,

These are not "hackers rules", but rather rules that ensure that the people being willing to answer questions also have time for further libxslt development. (I also found libxslt a bit difficult to handle in the beginning, but I was willing to respect that those who are subscribed to this and/or the libml2 maling list cannot spend all their time answering questions asked by those who don't want to abide by the rules.

> Usually good hackers as probably you are, become unpleasant people.

How can you judge people as being unpleasant without knowing them better?

> I have been subscribed to many mail list and in some of them I have
> been an experienced "hacker" about the list theme and when somebody
> ask you something you think is a stupid question you get angry with
> this people and say those thing like RTFM or STFW.

I think nobody considered your question stupid. You should be able to make a distinction between a asking stupid question and not having provided relevant information (the latter applies to you).

Greetings,

        Holger
_______________________________________________
xslt mailing list, project page http://xmlsoft.org/XSLT/ xslt@gnome.org http://mail.gnome.org/mailman/listinfo/xslt

--Boundary_(ID_4XUWWBUXtQVatGdg4h3g1g)-- From veillard@redhat.com Fri Apr 11 09:02:55 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id D145A1811B for ; Fri, 11 Apr 2003 09:02:54 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3BD2sw23010; Fri, 11 Apr 2003 09:02:54 -0400 Date: Fri, 11 Apr 2003 09:02:54 -0400 From: Daniel Veillard To: xslt@gnome.org Cc: srperan@sherlock.dif.um.es Subject: Re: [xslt] xsltApplyOneTemplate Message-ID: <20030411090254.W28785@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from aduhon@firstam.com on Fri, Apr 11, 2003 at 07:48:36AM -0500 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 11, 2003 at 07:48:36AM -0500, Duhon, Andrew wrote: > This is why I didn't want to join this list in the first place. I only did > it to get a simple answer to a simple question. I got it. Not as detailed as > I would have liked, but I do respect the gentleman's time. Regardless, this It's not a simple question at all. It's a short question, but very very hard to answer when having a full context to analyze it. And without context, it's just impossible to answer in a detailed fashion, and when I say impossible I really mean *impossible* . That's why when I bounced your original message I asked: 1/ that you subscribe to the list 2/ that you follow the rules and gave a pointer to the http://xmlsoft.org/XSLT/bug.html page I expected you would take the time to actually provide the data as explained by that page. You did not. You simply subscribed and posted back the exact same question without any sort of context. Hence my laconic answer. I cannot force you to give me the data I need to answer your question in a meaningful way. You cannot force me to give you uninformed answers either. I'm just getting angry at the people who thing what I say can be ignored, get a consultant, pay him massive amount of cash and then maybe you will get the uninformed answer you wanted at least I'm sure you will consider his answer *because you paid for it* ! Providing free expertise seems only the best way to get abused including moraly, it doesn't mean I'm gonna stop, but it does mean I feel more and more morally acceptable to drop request for help, or simply tell people to fuck off ... Abuse of free wealth seems the best way to loose it ! Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From sebastian.rahtz@computing-services.oxford.ac.uk Fri Apr 11 09:56:18 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from oxmail.ox.ac.uk (oxmail2.ox.ac.uk [163.1.2.2]) by mail.gnome.org (Postfix) with ESMTP id 37637189EB for ; Fri, 11 Apr 2003 09:56:18 -0400 (EDT) Received: from smtp0.herald.ox.ac.uk ([163.1.0.246]) by oxmail.ox.ac.uk with esmtp (Exim 4.14) id 193z0q-0007AS-7q; Fri, 11 Apr 2003 14:56:16 +0100 Received: from spqr.oucs.ox.ac.uk ([163.1.15.17]) by smtp0.herald.ox.ac.uk with esmtp (Exim 3.35 #1) id 193z0q-0000uH-00; Fri, 11 Apr 2003 14:56:16 +0100 Subject: Re: [xslt] xsltApplyOneTemplate From: Sebastian Rahtz To: xslt@gnome.org Cc: srperan@sherlock.dif.um.es In-Reply-To: <20030411090254.W28785@redhat.com> References: <20030411090254.W28785@redhat.com> Content-Type: text/plain Organization: OUCS Message-Id: <1050065031.32445.78.camel@spqr.oucs.ox.ac.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 11 Apr 2003 14:43:51 +0200 Content-Transfer-Encoding: 7bit Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Just for the record, I think Daniel's attitude to questions is fine! It's consistent and it's understandable. On the occasions I have had libxml/xslt problems, I have had answers which got better as I asked better questions (and vice versa :-}), which seems admirable. I wish more people were so straightforward. -- Sebastian Rahtz OUCS Information Manager 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431 From kbuchcik@4commerce.de Fri Apr 11 12:36:53 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mailc0910.dte2k.de (mail.t-intra.de [62.156.147.75]) by mail.gnome.org (Postfix) with ESMTP id ABF9E18540 for ; Fri, 11 Apr 2003 12:36:52 -0400 (EDT) Received: from mailc0908.dte2k.de ([10.50.185.8]) by mailc0910.dte2k.de with Microsoft SMTPSVC(5.0.2195.5329); Fri, 11 Apr 2003 18:36:52 +0200 Received: from kisone ([80.129.162.7]) by mailc0908.dte2k.de with Microsoft SMTPSVC(5.0.2195.5329); Fri, 11 Apr 2003 18:36:51 +0200 From: Kasimier Buchcik To: X-Priority: 3 Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Fri, 11 Apr 2003 18:31:55 +0200 Received: from 4commerce.de (LIBRA [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 2VMFS60Q; Fri, 11 Apr 2003 18:31:54 +0200 Message-ID: <3E96EE63.7010405@4commerce.de> Date: Fri, 11 Apr 2003 18:33:39 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en X-eMessageService: eMission.SMTPServer Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 11 Apr 2003 16:36:52.0007 (UTC) FILETIME=[8E363B70:01C30048] Subject: [xslt] "libxslt with thread-enabled libxml2?" Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi, is it possible to build libxslt in conjunction with libxml2 *with*=20 thread-support? If no, is there any chance that this feature will be=20 implemented soon? I did a make of libxml2 (ver. 2.5.4) with thread support turned on; then=20 tried to build libxslt (ver. 1.0.27) on top of the resulting libxml2 files. I got the following error: Creating library binaries\libxslt.lib and object binaries\libxslt.exp transform.obj : error LNK2001: unresolved external symbol=20 __imp__xmlGenericError No errors did occur when building libxslt using libxml2 *without* thread=20 support. Thanks and greetings, Kasimier Buchcik 4commerce technologies From igor@zlatkovic.com Fri Apr 11 14:17:55 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from post.webmailer.de (natsmtp01.webmailer.de [192.67.198.81]) by mail.gnome.org (Postfix) with ESMTP id 0667B180DB for ; Fri, 11 Apr 2003 14:17:55 -0400 (EDT) Received: from mail.zlatkovic.com (pD951B221.dip.t-dialin.net [217.81.178.33]) by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h3BIHrBG007720 for ; Fri, 11 Apr 2003 20:17:53 +0200 (MEST) Received: from 192.168.9.71 (ident=unknown) by mail.zlatkovic.com with esmtp (MasqMail 0.1.16) id 194360-5o9-00 for xslt@gnome.org; Fri, 11 Apr 2003 20:17:52 +0200 Received: from igor by astaroth.zlatkovic.com with local (MasqMail 0.1.16) id 194360-6zp-00 for xslt@gnome.org; Fri, 11 Apr 2003 20:17:52 +0200 Date: Fri, 11 Apr 2003 20:17:52 +0200 From: Igor Zlatkovic To: xslt@gnome.org Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Message-ID: <20030411181752.GA25631@astaroth.zlatkovic.com> Mail-Followup-To: xslt@gnome.org References: <3E96EE63.7010405@4commerce.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E96EE63.7010405@4commerce.de> User-Agent: Mutt/1.5.3i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Well, well, well... libxslt does not have any thread synchronisation machanisms right now. Even if it would compile, you would curse Dr.Watson's name once it bangs at runtime. You would have to provide your own thread-sync anyway. That being said, as I see it, you used the multi-threaded libxml for linking libxslt, but you used single-threaded libxml headers when compiling libxslt. By that, I mean LIBXML_THREAD_ENABLED was not defined. Can that be? Whatever, don't bother to compile. As said, you must provide thread sync at the application level for libxslt anyway, so you can protect libxml at the same level as well without any additional effort. Ciao, Igor On Fri, Apr 11, 2003 at 06:33:39PM +0200, Kasimier Buchcik wrote: > Hi, > > is it possible to build libxslt in conjunction with libxml2 *with* > thread-support? If no, is there any chance that this feature will be > implemented soon? > > I did a make of libxml2 (ver. 2.5.4) with thread support turned on; then > tried to build libxslt (ver. 1.0.27) on top of the resulting libxml2 files. > > I got the following error: > > Creating library binaries\libxslt.lib and object binaries\libxslt.exp > transform.obj : error LNK2001: unresolved external symbol > __imp__xmlGenericError > > No errors did occur when building libxslt using libxml2 *without* thread > support. > > Thanks and greetings, > > Kasimier Buchcik > > 4commerce technologies From veillard@redhat.com Fri Apr 11 14:57:43 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id E63EB18105 for ; Fri, 11 Apr 2003 14:57:42 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3BIvg800401 for xslt@gnome.org; Fri, 11 Apr 2003 14:57:42 -0400 Date: Fri, 11 Apr 2003 14:57:42 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Message-ID: <20030411145742.Z28785@redhat.com> References: <3E96EE63.7010405@4commerce.de> <20030411181752.GA25631@astaroth.zlatkovic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030411181752.GA25631@astaroth.zlatkovic.com>; from igor@zlatkovic.com on Fri, Apr 11, 2003 at 08:17:52PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 11, 2003 at 08:17:52PM +0200, Igor Zlatkovic wrote: > Whatever, don't bother to compile. As said, you must provide thread sync > at the application level for libxslt anyway, so you can protect libxml > at the same level as well without any additional effort. Hum, could you be more precise if something is needed at the code level. I expect to switch libxml2 compilation to be thread aware on Linux (now that some performances problems with memory allocation when compiling with threads have been addressed). So if libxslt needs work I'm interested of getting your advice :-) Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From mlists@pmade.org Fri Apr 11 15:50:03 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from pmade.org (pmade.org [206.157.70.61]) by mail.gnome.org (Postfix) with ESMTP id EC9FC183F8 for ; Fri, 11 Apr 2003 15:50:02 -0400 (EDT) Received: from pmade.org (localhost [127.0.0.1]) by pmade.org (8.12.8/8.12.6) with ESMTP id h3BJo25T057771 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 11 Apr 2003 12:50:02 -0700 (PDT) (envelope-from mlists@pmade.org) Received: (from pjones@localhost) by pmade.org (8.12.8/8.12.6/Submit) id h3BJo1QZ057770 for xslt@gnome.org; Fri, 11 Apr 2003 12:50:01 -0700 (PDT) X-Authentication-Warning: pmade.org: pjones set sender to mlists@pmade.org using -f Date: Fri, 11 Apr 2003 12:50:01 -0700 From: Peter Jones To: xslt@gnome.org Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Message-ID: <20030411195001.GJ36907@pmade.org> Mail-Followup-To: xslt@gnome.org References: <3E96EE63.7010405@4commerce.de> <20030411181752.GA25631@astaroth.zlatkovic.com> <20030411145742.Z28785@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030411145742.Z28785@redhat.com> User-Agent: Mutt/1.4i X-BOFH-Excuse: Reformatting Page. Wait... Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hey, remember back when Daniel Veillard said: > I expect to switch libxml2 compilation to be thread aware on Linux Maybe I am missing something here, but why does libxslt need to be "thread aware"? I should point out my definition of thread aware, vs. thread safe. Thread aware is when the library detects that it is being used in a multithreaded application and uses things like mutexes to protect parts of the library that are not thread safe. Thread safe is when the library does not care if the application is multithreaded or not. It does not use things such as global variables, or function static variables. There is no need to use mutexes or anything else related to threads. Now, maybe we are talking about some of the libxslt callbacks. If I wanted to write an XPath extension function I would need to give libxslt a callback function. If libxslt was tread aware, it would lock some mutex before it called my callback (maybe). If it was thread safe, it would allow me to use a context pointer that gets passed to the callback, and the callback would decide whether or not a mutex needs to be locked. It is definitely a matter of opinion and preference, but I don't think libxslt should be thread aware, just thread safe. The bonus of thread safety, is it usually yields a better design, e.g. no global variables. -- Peter Jones [ http://pmade.org ] PGP Fingerprint: 0A2B F8AB 63CF F7A2 556F F892 5B43 7370 A4B6 E0DF From igor@zlatkovic.com Fri Apr 11 17:02:33 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from post.webmailer.de (natsmtp00.webmailer.de [192.67.198.74]) by mail.gnome.org (Postfix) with ESMTP id 3C6C11815D for ; Fri, 11 Apr 2003 17:02:33 -0400 (EDT) Received: from mail.zlatkovic.com (pD951B221.dip.t-dialin.net [217.81.178.33]) by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h3BL2PWk017483 for ; Fri, 11 Apr 2003 23:02:26 +0200 (MEST) Received: from 192.168.9.71 (ident=unknown) by mail.zlatkovic.com with esmtp (MasqMail 0.1.16) id 1945fF-6Uc-00 for xslt@gnome.org; Fri, 11 Apr 2003 23:02:25 +0200 Received: from igor by astaroth.zlatkovic.com with local (MasqMail 0.1.16) id 1945fF-7XK-00 for xslt@gnome.org; Fri, 11 Apr 2003 23:02:25 +0200 Date: Fri, 11 Apr 2003 23:02:25 +0200 From: Igor Zlatkovic To: xslt@gnome.org Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Message-ID: <20030411210225.GA28443@astaroth.zlatkovic.com> Mail-Followup-To: xslt@gnome.org References: <3E96EE63.7010405@4commerce.de> <20030411181752.GA25631@astaroth.zlatkovic.com> <20030411145742.Z28785@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030411145742.Z28785@redhat.com> User-Agent: Mutt/1.5.3i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 11, 2003 at 02:57:42PM -0400, Daniel Veillard wrote: > Hum, could you be more precise if something is needed at the code level. > I expect to switch libxml2 compilation to be thread aware on Linux > (now that some performances problems with memory allocation when compiling > with threads have been addressed). So if libxslt needs work I'm interested > of getting your advice :-) Well, I guess libxslt will need the same protection libxml allready has. Imagine ten threads applying the same stylesheet on ten different documents. Each thread has its own vision of what, say, xsltGenericError or xsltMaxDepth should contain and start setting and resetting these at the whim of the kernel scheduler. I have never tested it, but that doesn't sound good to me :-) That aside, I strongly believe that thread sync on that level should be left to the application code. Neither libxml nor libxslt can ever know what an application will do with them. Libxml and libxslt don't need or use asynchronous processing, like I call some function implemented in these and do other work until I receive a notification about the results. As long this remains that way, I would leave thread sync to the applications, there is no better place for that. Ciao, Igor From igor@zlatkovic.com Fri Apr 11 17:31:50 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from post.webmailer.de (natsmtp00.webmailer.de [192.67.198.74]) by mail.gnome.org (Postfix) with ESMTP id 1485518A64 for ; Fri, 11 Apr 2003 17:31:50 -0400 (EDT) Received: from mail.zlatkovic.com (pD951B221.dip.t-dialin.net [217.81.178.33]) by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h3BLVmDa012341 for ; Fri, 11 Apr 2003 23:31:49 +0200 (MEST) Received: from 192.168.9.71 (ident=unknown) by mail.zlatkovic.com with esmtp (MasqMail 0.1.16) id 19467g-6cM-00 for xslt@gnome.org; Fri, 11 Apr 2003 23:31:48 +0200 Received: from igor by astaroth.zlatkovic.com with local (MasqMail 0.1.16) id 19467g-7dK-00 for xslt@gnome.org; Fri, 11 Apr 2003 23:31:48 +0200 Date: Fri, 11 Apr 2003 23:31:48 +0200 From: Igor Zlatkovic To: xslt@gnome.org Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Message-ID: <20030411213148.GB28443@astaroth.zlatkovic.com> Mail-Followup-To: xslt@gnome.org References: <3E96EE63.7010405@4commerce.de> <20030411181752.GA25631@astaroth.zlatkovic.com> <20030411145742.Z28785@redhat.com> <20030411195001.GJ36907@pmade.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030411195001.GJ36907@pmade.org> User-Agent: Mutt/1.5.3i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 11, 2003 at 12:50:01PM -0700, Peter Jones wrote: > Hey, remember back when Daniel Veillard said: > > I expect to switch libxml2 compilation to be thread aware on Linux > > Maybe I am missing something here, but why does libxslt need to be > "thread aware"? > > I should point out my definition of thread aware, vs. thread safe. > > Thread aware is when the library detects that it is being used in a > multithreaded application and uses things like mutexes to protect parts > of the library that are not thread safe. > > Thread safe is when the library does not care if the application is > multithreaded or not. It does not use things such as global variables, > or function static variables. There is no need to use mutexes or > anything else related to threads. Unfortunately, there are global variables and breaking the binary compatibility by removing them would break a half of the world. Neither GNOME nor KDE desktops would work. The impact would be unbearable. > Now, maybe we are talking about some of the libxslt callbacks. If I > wanted to write an XPath extension function I would need to give libxslt > a callback function. > > If libxslt was tread aware, it would lock some mutex before it called my > callback (maybe). If it was thread safe, it would allow me to use a > context pointer that gets passed to the callback, and the callback would > decide whether or not a mutex needs to be locked. > > It is definitely a matter of opinion and preference, but I don't think > libxslt should be thread aware, just thread safe. The bonus of thread > safety, is it usually yields a better design, e.g. no global variables. All fine, but its an utopia. libxml2 must remain functional when used with things which are allready compiled. I agree, variables should never be exported from a library, functions for their manipulation should be exported instead. The contents of internal structures should never be revealed to the application, apps should use pointers to these as opaque handles instead. This gives more work at the API and takes some flexibility, but makes it possible never to break source or binary compatibility. This is not where we are. Libxml wasn't designed yesterday, it exists for quite a few years now. Its designers began long ago, never dreaming about all the problems and oddities multiple platforms would bring. Today, libxml and libxslt are not just about to be released, but present the very base for the most of what people see on their screen. It is not the matter of preference. Now the art of programming is asked for. And the art is not to produce the code for another programmer to admire its design. The art is to produce executables which ease the life of the end-user and make her cry for more :-) Ciao, Igor From mlists@pmade.org Fri Apr 11 17:46:26 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from pmade.org (pmade.org [206.157.70.61]) by mail.gnome.org (Postfix) with ESMTP id 55E7618103 for ; Fri, 11 Apr 2003 17:46:26 -0400 (EDT) Received: from pmade.org (localhost [127.0.0.1]) by pmade.org (8.12.8/8.12.6) with ESMTP id h3BLkP5T059719 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 11 Apr 2003 14:46:25 -0700 (PDT) (envelope-from mlists@pmade.org) Received: (from pjones@localhost) by pmade.org (8.12.8/8.12.6/Submit) id h3BLkPrA059718 for xslt@gnome.org; Fri, 11 Apr 2003 14:46:25 -0700 (PDT) X-Authentication-Warning: pmade.org: pjones set sender to mlists@pmade.org using -f Date: Fri, 11 Apr 2003 14:46:25 -0700 From: Peter Jones To: xslt@gnome.org Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Message-ID: <20030411214625.GL36907@pmade.org> Mail-Followup-To: xslt@gnome.org References: <3E96EE63.7010405@4commerce.de> <20030411181752.GA25631@astaroth.zlatkovic.com> <20030411145742.Z28785@redhat.com> <20030411195001.GJ36907@pmade.org> <20030411213148.GB28443@astaroth.zlatkovic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030411213148.GB28443@astaroth.zlatkovic.com> User-Agent: Mutt/1.4i X-BOFH-Excuse: Reformatting Page. Wait... Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hey, remember back when Igor Zlatkovic said: > It is not the matter of preference. Now the art of programming is asked > for. And the art is not to produce the code for another programmer to > admire its design. The art is to produce executables which ease the life > of the end-user and make her cry for more :-) Who are the average users of libxml2? I would assume that it would be software developers. True, there are an extreme number of end-users that are indirectly using libxml2. So, if the average users of libxml2 are software developers, the goal is not to produce executables that ease the life of an end-user, the goal is to produce a library with a clean and easy to use interface. I don't expect anyone to break binary compatibility in libxml2 or libxslt. I just don't want to see the addition of thread related functionality, like mutexes. I have used libxml2 and libxslt in single and multithreaded applications with no problems. I did have to review the source to those libraries to make sure I avoided functions that were not thread-safe, but that is much more light weight than adding thread awareness to them. -- Peter Jones [ http://pmade.org ] PGP Fingerprint: 0A2B F8AB 63CF F7A2 556F F892 5B43 7370 A4B6 E0DF From veillard@redhat.com Fri Apr 11 17:59:55 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 8517E1847B for ; Fri, 11 Apr 2003 17:59:55 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3BLxt310701 for xslt@gnome.org; Fri, 11 Apr 2003 17:59:55 -0400 Date: Fri, 11 Apr 2003 17:59:55 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Message-ID: <20030411175955.A28785@redhat.com> References: <3E96EE63.7010405@4commerce.de> <20030411181752.GA25631@astaroth.zlatkovic.com> <20030411145742.Z28785@redhat.com> <20030411210225.GA28443@astaroth.zlatkovic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030411210225.GA28443@astaroth.zlatkovic.com>; from igor@zlatkovic.com on Fri, Apr 11, 2003 at 11:02:25PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 11, 2003 at 11:02:25PM +0200, Igor Zlatkovic wrote: > On Fri, Apr 11, 2003 at 02:57:42PM -0400, Daniel Veillard wrote: > > Hum, could you be more precise if something is needed at the code level. > > I expect to switch libxml2 compilation to be thread aware on Linux > > (now that some performances problems with memory allocation when compiling > > with threads have been addressed). So if libxslt needs work I'm interested > > of getting your advice :-) > > Well, I guess libxslt will need the same protection libxml allready has. > Imagine ten threads applying the same stylesheet on ten different > documents. Each thread has its own vision of what, say, xsltGenericError > or xsltMaxDepth should contain and start setting and resetting these at > the whim of the kernel scheduler. I have never tested it, but that > doesn't sound good to me :-) Well per transformation error context is simple allow to register them at the transformation context level and if not defined cascade to the global one. Actually it's already the case c.f. fields error and errctx in the transformation context. Concerning xsltMaxDepth it really is a global setting, one should not need to tune it per transformation. Each thread runs it's own transformation with it own context and the stylesheets are read-only, that works already ... > That aside, I strongly believe that thread sync on that level should be > left to the application code. Neither libxml nor libxslt can ever know > what an application will do with them. My question was whether once needed to change something now to compile libxslt with thread support on Windows. > Libxml and libxslt don't need or use asynchronous processing, like I > call some function implemented in these and do other work until I > receive a notification about the results. As long this remains that way, > I would leave thread sync to the applications, there is no better place > for that. Yep I didn't intended to change that level. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard@redhat.com Fri Apr 11 18:06:00 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 7FFD918394 for ; Fri, 11 Apr 2003 18:06:00 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3BM60O11701 for xslt@gnome.org; Fri, 11 Apr 2003 18:06:00 -0400 Date: Fri, 11 Apr 2003 18:06:00 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Message-ID: <20030411180600.B28785@redhat.com> References: <3E96EE63.7010405@4commerce.de> <20030411181752.GA25631@astaroth.zlatkovic.com> <20030411145742.Z28785@redhat.com> <20030411195001.GJ36907@pmade.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030411195001.GJ36907@pmade.org>; from mlists@pmade.org on Fri, Apr 11, 2003 at 12:50:01PM -0700 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 11, 2003 at 12:50:01PM -0700, Peter Jones wrote: > Hey, remember back when Daniel Veillard said: > > I expect to switch libxml2 compilation to be thread aware on Linux > > Maybe I am missing something here, but why does libxslt need to be > "thread aware"? > > I should point out my definition of thread aware, vs. thread safe. > > Thread aware is when the library detects that it is being used in a > multithreaded application and uses things like mutexes to protect parts > of the library that are not thread safe. Actually libxml2 XPath already have some thread awareness, but it doesn't need to be changed. > Now, maybe we are talking about some of the libxslt callbacks. If I Not specifically ... > wanted to write an XPath extension function I would need to give libxslt > a callback function. > If libxslt was tread aware, it would lock some mutex before it called my > callback (maybe). If it was thread safe, it would allow me to use a > context pointer that gets passed to the callback, and the callback would > decide whether or not a mutex needs to be locked. I would defer thtis to the application level. > It is definitely a matter of opinion and preference, but I don't think > libxslt should be thread aware, just thread safe. The bonus of thread > safety, is it usually yields a better design, e.g. no global variables. There are global variables in libxslt. But they should not be a problem in practice. My initial mail is just ... "I'm gonna make --enable-thread the default compilation switch on Linux and I'm asking for possible problems at the libxslt level..." If it works, then fine :-) Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From igor@zlatkovic.com Sun Apr 13 17:17:01 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from post.webmailer.de (natsmtp00.webmailer.de [192.67.198.74]) by mail.gnome.org (Postfix) with ESMTP id 03A8E1810B for ; Sun, 13 Apr 2003 17:17:01 -0400 (EDT) Received: from mail.zlatkovic.com (pD9E26DB3.dip.t-dialin.net [217.226.109.179]) by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h3DLGxbw018328 for ; Sun, 13 Apr 2003 23:16:59 +0200 (MEST) Received: from 192.168.9.72 (ident=unknown) by mail.zlatkovic.com with smtp (MasqMail 0.1.16) id 194oqR-1cK-00 for xslt@gnome.org; Sun, 13 Apr 2003 23:16:59 +0200 Message-ID: <000a01c30202$06018960$4809a8c0@raven> From: Igor Zlatkovic To: References: <3E96EE63.7010405@4commerce.de> <20030411181752.GA25631@astaroth.zlatkovic.com> <20030411145742.Z28785@redhat.com> <20030411210225.GA28443@astaroth.zlatkovic.com> <20030411175955.A28785@redhat.com> Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Date: Sun, 13 Apr 2003 23:17:00 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > My question was whether once needed to change something now to compile > libxslt with thread support on Windows. Yes, there was a small issue, I commited the fix. All of it is limited to the Windows makefile, the C code needs no treatment. Now, if you'll enable the thread-support in libxml per default on Unix, I'll do the same on Windows. Ciao, Igor From veillard@redhat.com Sun Apr 13 17:25:04 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 67C2A185E8 for ; Sun, 13 Apr 2003 17:25:04 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3DLP4n26700 for xslt@gnome.org; Sun, 13 Apr 2003 17:25:04 -0400 Date: Sun, 13 Apr 2003 17:25:03 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] "libxslt with thread-enabled libxml2?" Message-ID: <20030413172503.J28785@redhat.com> References: <3E96EE63.7010405@4commerce.de> <20030411181752.GA25631@astaroth.zlatkovic.com> <20030411145742.Z28785@redhat.com> <20030411210225.GA28443@astaroth.zlatkovic.com> <20030411175955.A28785@redhat.com> <000a01c30202$06018960$4809a8c0@raven> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <000a01c30202$06018960$4809a8c0@raven>; from igor@zlatkovic.com on Sun, Apr 13, 2003 at 11:17:00PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Sun, Apr 13, 2003 at 11:17:00PM +0200, Igor Zlatkovic wrote: > > My question was whether once needed to change something now to compile > > libxslt with thread support on Windows. > > Yes, there was a small issue, I commited the fix. All of it is limited to > the Windows makefile, the C code needs no treatment. Now, if you'll enable > the thread-support in libxml per default on Unix, I'll do the same on > Windows. Well, I need to do a bit of testing first, but I intend to do so if the tests output doesn't show a significant performance drop on Red Hat 9. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From kbuchcik@4commerce.de Mon Apr 14 06:31:35 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mailc0910.dte2k.de (mail.t-intra.de [62.156.147.75]) by mail.gnome.org (Postfix) with ESMTP id AE010186B9 for ; Mon, 14 Apr 2003 06:31:34 -0400 (EDT) Received: from mailc0906.dte2k.de ([10.50.185.6]) by mailc0910.dte2k.de with Microsoft SMTPSVC(5.0.2195.5329); Mon, 14 Apr 2003 12:31:33 +0200 Received: from kisone ([80.129.168.3]) by mailc0906.dte2k.de with Microsoft SMTPSVC(5.0.2195.5329); Mon, 14 Apr 2003 12:31:32 +0200 From: Kasimier Buchcik To: X-Priority: 3 Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Mon, 14 Apr 2003 12:28:12 +0200 Received: from 4commerce.de (LIBRA [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 2VMFS7FF; Mon, 14 Apr 2003 12:28:12 +0200 Message-ID: <3E9A8D96.1060402@4commerce.de> Date: Mon, 14 Apr 2003 12:29:42 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en X-eMessageService: eMission.SMTPServer Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 14 Apr 2003 10:31:32.0715 (UTC) FILETIME=[0488F3B0:01C30271] Subject: [xslt] "Re: libxslt with thread-enabled libxml2?" Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi, On Fri, 11 Apr 2003 20:17:52 +0200, Igor Zlatkovic wrote: > That being said, as I see it, you used the multi-threaded libxml for > linking libxslt, but you used single-threaded libxml headers when > compiling libxslt. By that, I mean LIBXML_THREAD_ENABLED was not > defined. Can that be? Well, maby I did domething wrong. Here is what I performed: libxml2 (ver. 2.5.4) cscript configure.js threads=3Dnative prefix=3D=20 include=3D\include lib=3D\lib nmake libxslt (ver. 1.0.27) cscript configure.js prefix=3D=20 include=3D\include;\include=20 lib=3D\lib nmake I guess or hope that libxslt has taken the headers of the previously=20 builded multi-threaded libxml, since it was pointed to that include=20 folder. Additionally I did not find LIBXML_THREAD_ENABLED in the libxslt=20 sources. So I wonder if that would make some difference to the=20 compilation of libsxlt, if this is what you meant. I would be glad if=20 someone could send me some info about how to build those dlls properly. On Fri, 11 Apr 2003 18:06:00 -0400, Daniel Veillard wrote: > My initial mail is just ... > "I'm gonna make --enable-thread the default compilation switch on Linux > and I'm asking for possible problems at the libxslt level..." > If it works, then fine I'm not sure if this works. *If* I performed the build of libxslt the=20 way it was intended, then something needs to be changed. We originally implemented thread safety at the application level, but=20 were curious about switching to libxml2 thread support. The problem is:=20 we cannot run the multi-threaded libxml2.dll in conjunction with the=20 straight forward builded libxslt.dll. We get some complains about a non=20 existent xmlGenericError entry point;=20 "libxml2-2.5.4\win32\libxml2.def.src" declares the export of=20 __xmlGenericError and not xmlGenericError if LIBXML_THREAD_ENABLED is=20 on). As far as I am concerned "xmlGenericError" is used extensively in=20 the libxslt sources. Thanks and greetings, Kasimier Buchcik -- 4commerce technologies From igor@zlatkovic.com Mon Apr 14 07:21:18 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from post.webmailer.de (natsmtp01.webmailer.de [192.67.198.81]) by mail.gnome.org (Postfix) with ESMTP id EE89E186F1 for ; Mon, 14 Apr 2003 07:21:17 -0400 (EDT) Received: from mail.zlatkovic.com (p5080FE7F.dip.t-dialin.net [80.128.254.127]) by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h3EBLDsD023031 for ; Mon, 14 Apr 2003 13:21:13 +0200 (MEST) Received: from 192.168.9.72 (ident=unknown) by mail.zlatkovic.com with smtp (MasqMail 0.1.16) id 19521R-56X-00 for xslt@gnome.org; Mon, 14 Apr 2003 13:21:13 +0200 Message-ID: <001601c30277$f6fd8740$4809a8c0@raven> From: Igor Zlatkovic To: References: <3E9A8D96.1060402@4commerce.de> Subject: Re: [xslt] "Re: libxslt with thread-enabled libxml2?" Date: Mon, 14 Apr 2003 13:21:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > Well, maby I did domething wrong. Here is what I performed: > libxml2 (ver. 2.5.4) > > [...] That's okay. My mistake. Libxslt compilation must define _REENTRANT as well, or LIBXML_THREAD_ENABLE has no effect. I commited the fix yesterday, the compilation works now. Ciao, Igor From stephane.bidoul@softwareag.com Mon Apr 14 11:09:01 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from server8.software-ag.de (server8.software-ag.de [193.26.193.23]) by mail.gnome.org (Postfix) with ESMTP id 0AFB918728 for ; Mon, 14 Apr 2003 11:09:01 -0400 (EDT) Received: from acsesbi by server8.software-ag.de; (8.11.6/8.9.3) id h3EF8vf07621; Mon, 14 Apr 2003 17:08:58 +0200 From: "Stephane Bidoul" To: Subject: RE: [xslt] exslt in Windows port Date: Mon, 14 Apr 2003 17:08:57 +0200 Message-ID: <000001c30297$c89f82c0$ca14200a@acsesbi> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0) Importance: Normal In-Reply-To: <20030409070332.N10927@redhat.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > On Wed, Apr 09, 2003 at 02:48:22PM +0400, Alexey Efimov wrote: > > Hello, > > > > I have the latest release of libxslt at Windows 2000 (from > > http://zlatkovic.com/projects/libxml/binaries.html) and at HP-UX > > (built from source). Number of exslt functions in Windows > port is too > > small. > > Seems some of the EXSLT math module is related to the presence > of the math.h header file ... If windows has it, HAVE_MATH_H > should be defined in win32config.h > > > Why such difference is present? Am I doing something wrong? > > Seems the code need some love for Windows... Indeed, exsltMathRegister has #if HAVE_MATH_H. The following patch works for me... Index: win32config.h =================================================================== RCS file: /cvs/gnome/libxslt/libxslt/win32config.h,v retrieving revision 1.8 diff -c -r1.8 win32config.h *** win32config.h 14 Nov 2002 17:48:57 -0000 1.8 --- win32config.h 12 Apr 2003 15:57:14 -0000 *************** *** 8,13 **** --- 8,14 ---- #define HAVE_LOCALTIME #define HAVE_GMTIME #define HAVE_TIME + #define HAVE_MATH_H 1 #define HAVE_FCNTL_H -sbi From igor@zlatkovic.com Mon Apr 14 11:47:15 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from post.webmailer.de (natsmtp01.webmailer.de [192.67.198.81]) by mail.gnome.org (Postfix) with ESMTP id A907418717 for ; Mon, 14 Apr 2003 11:47:14 -0400 (EDT) Received: from mail.zlatkovic.com (p5080FE7F.dip.t-dialin.net [80.128.254.127]) by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h3EFlD8H017625; Mon, 14 Apr 2003 17:47:13 +0200 (MEST) Received: from 192.168.9.72 (ident=unknown) by mail.zlatkovic.com with smtp (MasqMail 0.1.16) id 1956Aq-6N5-00; Mon, 14 Apr 2003 17:47:12 +0200 Message-ID: <002f01c3029d$1fd13070$4809a8c0@raven> From: Igor Zlatkovic To: , References: <000001c30297$c89f82c0$ca14200a@acsesbi> Subject: Re: [xslt] exslt in Windows port Date: Mon, 14 Apr 2003 17:47:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > Indeed, exsltMathRegister has #if HAVE_MATH_H. > The following patch works for me... > > Index: win32config.h > =================================================================== > RCS file: /cvs/gnome/libxslt/libxslt/win32config.h,v > retrieving revision 1.8 > diff -c -r1.8 win32config.h > *** win32config.h 14 Nov 2002 17:48:57 -0000 1.8 > --- win32config.h 12 Apr 2003 15:57:14 -0000 > *************** > *** 8,13 **** > --- 8,14 ---- > #define HAVE_LOCALTIME > #define HAVE_GMTIME > #define HAVE_TIME > + #define HAVE_MATH_H 1 > > #define HAVE_FCNTL_H Good enough, I'll commit it. Thanks. Ciao, Igor From kbuchcik@4commerce.de Tue Apr 15 12:21:19 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mail.gnome.org (Postfix) with ESMTP id 77E9D18702 for ; Tue, 15 Apr 2003 12:21:19 -0400 (EDT) Received: from port-212-202-229-162.reverse.qsc.de ([212.202.229.162] helo=kisone) by mx01.qsc.de with smtp (Exim 3.35 #1) id 195TBO-0006u7-00 for xslt@gnome.org; Tue, 15 Apr 2003 18:21:18 +0200 From: Kasimier Buchcik To: X-Priority: 3 Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Tue, 15 Apr 2003 18:16:49 +0200 Received: from 4commerce.de (LIBRA [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 20ARL8Z8; Tue, 15 Apr 2003 18:16:48 +0200 Message-ID: <3E9C3330.8060700@4commerce.de> Date: Tue, 15 Apr 2003 18:28:32 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en X-eMessageService: eMission.SMTPServer Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: [xslt] unresolved external symbol Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi, On Mon, 14 Apr 2003 13:21:16 +0200, Igor Zlatkovic wrote: > Libxslt compilation must define _REENTRANT=20 > as well, or LIBXML_THREAD_ENABLE has no effect. I see. > I commited the fix yesterday, the compilation works now. Thanks for the quick fixing. I still have (non thread-specific) problems=20 with the compilation: I tried to build libxslt (ver. 1.0.29) on top of libxml2 (ver. 2.5.6).=20 Both were configured using "configure.js" with default settings. The following errors occured during the build of libxslt: documents.obj : error LNK2001: unresolved external symbol=20 _xmlXPathOrderDocElems transform.obj : error LNK2001: unresolved external symbol=20 _xmlXPathOrderDocElems On the other hand: building libxslt (ver. 1.0.28) on top of libxml2=20 (ver. 2.5.6) works fine. Any clues? Greetings, Kasimier Buchcik -- 4commerce technologies From Mark_Vakoc@jdedwards.com Tue Apr 15 12:23:58 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from ns2.jdedwards.com (ns2.jdedwards.com [199.166.248.75]) by mail.gnome.org (Postfix) with ESMTP id 61AC618702 for ; Tue, 15 Apr 2003 12:23:58 -0400 (EDT) Received: from denvscans4.jdedwards.com ([10.0.14.76]) by ns2.jdedwards.com (8.11.6/8.9.1) with SMTP id h3FGNwr06896 for ; Tue, 15 Apr 2003 10:23:58 -0600 Received: from 10.0.14.51 by denvscans4.jdedwards.com (InterScan E-Mail VirusWall NT); Tue, 15 Apr 2003 10:23:57 -0600 Received: by cormails11.jdedwards.com with Internet Mail Service (5.5.2653.19) id ; Tue, 15 Apr 2003 10:28:45 -0600 Message-ID: <09B3671D58690A4193A7F8F15F416B23FF2565@denmails3.jdedwards.com> From: "Vakoc, Mark" To: "'xslt@gnome.org'" Subject: RE: [xslt] unresolved external symbol Date: Tue, 15 Apr 2003 10:23:53 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > > documents.obj : error LNK2001: unresolved external symbol > _xmlXPathOrderDocElems > transform.obj : error LNK2001: unresolved external symbol > _xmlXPathOrderDocElems > This function needs to be added to libxml2.def.src file and libxml2 needs to be recompiled. From kbuchcik@4commerce.de Tue Apr 15 12:51:19 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mail.gnome.org (Postfix) with ESMTP id 04248180E5 for ; Tue, 15 Apr 2003 12:51:19 -0400 (EDT) Received: from port-212-202-229-162.reverse.qsc.de ([212.202.229.162] helo=kisone) by mx01.qsc.de with smtp (Exim 3.35 #1) id 195TeQ-0007Bb-00 for xslt@gnome.org; Tue, 15 Apr 2003 18:51:18 +0200 From: Kasimier Buchcik To: X-Priority: 3 Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Tue, 15 Apr 2003 18:48:18 +0200 Received: from 4commerce.de (LIBRA [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 20ARL851; Tue, 15 Apr 2003 18:48:18 +0200 Message-ID: <3E9C3A95.1030305@4commerce.de> Date: Tue, 15 Apr 2003 19:00:05 +0200 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en References: <09B3671D58690A4193A7F8F15F416B23FF2565@denmails3.jdedwards.com> In-Reply-To: <09B3671D58690A4193A7F8F15F416B23FF2565@denmails3.jdedwards.com> X-eMessageService: eMission.SMTPServer Subject: 'Re: "RE: [xslt] unresolved external symbol"' Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Vakoc, Mark wrote: >>documents.obj : error LNK2001: unresolved external symbol=20 >>_xmlXPathOrderDocElems >>transform.obj : error LNK2001: unresolved external symbol=20 >>_xmlXPathOrderDocElems >> >=20 >=20 > This function needs to be added to libxml2.def.src file and libxml2 needs = to > be recompiled. :-) Thank you. That did it. Libxslt compiles smoothly now. Greetings, Kasimier Buchcik -- 4commerce technologies From fl@opikanoba.org Wed Apr 16 04:08:13 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from localhost (AStrasbourg-206-1-17-162.abo.wanadoo.fr [81.48.190.162]) by mail.gnome.org (Postfix) with ESMTP id CAFB118300 for ; Wed, 16 Apr 2003 04:08:12 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 004CF38260 for ; Wed, 16 Apr 2003 10:08:10 +0200 (CEST) From: =?iso-8859-15?q?Fr=E9d=E9ric=20Laurent?= Organization: http://www.opikanoba.org To: xslt@gnome.org Date: Wed, 16 Apr 2003 10:08:10 +0200 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200304161008.10138.fl@opikanoba.org> Subject: [xslt] exslt function supported by xsltproc Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: hello According to the exslt website [1], the power function (math module) is available in libxslt Moreover if I make a test : xsltproc --dumpextensions Registered XSLT Extensions =2D------------------------- Registered Extension Functions: {http://exslt.org/math}lowest {http://exslt.org/math}constant {http://exslt.org/math}power =2E.. So, I've got power :-) Then, with a very simple test like this : =2D------------- 8< ------- testpower.xsl --------------------------------= =2D---- =2D------------- 8< -------------------------------------------------------= =2D---- and a foo.xml I try to run and=20 xsltproc testpower.xsl foo.xml runtime error: file testpower.xsl line 8 element call-template xsl:call-template : template power not found no result for foo.xml [1] http://exslt.org/math/functions/power/index.html I don't understand what I have missed ! thanks for yours answers =2D-=20 =46r=E9d=E9ric Laurent http://www.opikanoba.org From veillard@redhat.com Wed Apr 16 04:16:56 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id F120B1861B for ; Wed, 16 Apr 2003 04:16:55 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3G8GtO25202 for xslt@gnome.org; Wed, 16 Apr 2003 04:16:55 -0400 Date: Wed, 16 Apr 2003 04:16:55 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] exslt function supported by xsltproc Message-ID: <20030416041655.G28785@redhat.com> References: <200304161008.10138.fl@opikanoba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <200304161008.10138.fl@opikanoba.org>; from fl@opikanoba.org on Wed, Apr 16, 2003 at 10:08:10AM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wed, Apr 16, 2003 at 10:08:10AM +0200, Frédéric Laurent wrote: > Registered Extension Functions: > {http://exslt.org/math}power [...] > > > [...] > I don't understand what I have missed ! it's registered as a function, call-template is not the proper construct to call it then, it looks suspicious to use a template to call a math function, that doesn't look right at all. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From frederic.laurent@opikanoba.org Wed Apr 16 04:33:05 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from localhost (AStrasbourg-206-1-17-162.abo.wanadoo.fr [81.48.190.162]) by mail.gnome.org (Postfix) with ESMTP id 606C91879E for ; Wed, 16 Apr 2003 04:33:05 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id C406638260 for ; Wed, 16 Apr 2003 10:33:04 +0200 (CEST) From: =?iso-8859-1?q?Fr=E9d=E9ric=20Laurent?= Organization: http://www.opikanoba.org To: xslt@gnome.org Subject: Re: [xslt] exslt function supported by xsltproc Date: Wed, 16 Apr 2003 10:33:04 +0200 User-Agent: KMail/1.5 References: <200304161008.10138.fl@opikanoba.org> <20030416041655.G28785@redhat.com> In-Reply-To: <20030416041655.G28785@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200304161033.04281.frederic.laurent@opikanoba.org> Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wednesday 16 April 2003 10:16, Daniel Veillard wrote: > On Wed, Apr 16, 2003 at 10:08:10AM +0200, Fr=E9d=E9ric Laurent wrote: > > Registered Extension Functions: > > {http://exslt.org/math}power > > [...] > > > > > > > > > [...] > > > I don't understand what I have missed ! > > it's registered as a function, call-template is not the proper > construct to call it then, it looks suspicious to use a template > to call a math function, that doesn't look right at all. > > Daniel ok, you're right, so stupid am I :-( in fact, I misread the exslt howto where the following example=20 makes me follow the wrong way... so=20 works better ! Thanks Daniel, my problem of the day is solved, I can go back to bed :-D =2D-=20 =46r=E9d=E9ric Laurent http://www.opikanoba.org From cyberthymia@yahoo.co.uk Wed Apr 16 05:13:21 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by mail.gnome.org (Postfix) with SMTP id A4A7F187A2 for ; Wed, 16 Apr 2003 05:13:20 -0400 (EDT) Received: from unknown (HELO ARIEL) (cyberthymia@212.125.86.68 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 16 Apr 2003 09:13:19 -0000 Message-ID: <005301c303f8$6c078230$4e0aa8c0@3b2.com> From: "Cyberthymia" To: References: <200304161008.10138.fl@opikanoba.org> <20030416041655.G28785@redhat.com> Subject: Re: [xslt] exslt function supported by xsltproc Date: Wed, 16 Apr 2003 10:13:17 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: From: "Daniel Veillard" > On Wed, Apr 16, 2003 at 10:08:10AM +0200, Frédéric Laurent wrote: > > Registered Extension Functions: > > {http://exslt.org/math}power > > [...] > > > > > > > > [...] > > I don't understand what I have missed ! > > it's registered as a function, call-template is not the proper > construct to call it then, it looks suspicious to use a template > to call a math function, that doesn't look right at all. > The description of the power function includes an example use of the template syntax: http://exslt.org/math/functions/power/index.html In order to make this work though you need to download http://exslt.org/math/math.zip which contains lots of examples of all the different maths functions, including the wrappers for the functions to let you use templates if you so desire. Richard From gabor@hojtsy.hu Mon Apr 21 08:49:37 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from vadangyal.vnet.hu (mail.vnet.hu [213.163.59.4]) by mail.gnome.org (Postfix) with ESMTP id 6DD7818489 for ; Mon, 21 Apr 2003 08:49:37 -0400 (EDT) Received: from hojtsy.hu (62-77-248-55.vnet.hu [62.77.248.55]) by mail.vnet.hu (iPlanet Messaging Server 5.1 Patch 1 (built Jun 6 2002)) with ESMTPA id <0HDP00AJW2AOUM@mail.vnet.hu> for xslt@gnome.org; Mon, 21 Apr 2003 14:49:37 +0200 (CEST) Date: Mon, 21 Apr 2003 14:51:20 +0200 From: Gabor Hojtsy To: xslt@gnome.org Message-id: <3EA3E948.80606@hojtsy.hu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: hu, en, en-us User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 Subject: [xslt] disable-output-escaping disfunctional Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi! I am using the latest libxml/libxslt dlls and binaries for Windows, having a very bad experience with disable-output-escaping. I would like to use some xslt to generate PHP code, using template fragments, such as: , 'prev' =< This used to generate: 'prev' => But it does not generate that anymore. Its output is: 'prev' =< I have tried the above with: - disable-output-escaping="no" - CDATA without any output-esc. spec. - CDATA with disable-output-esc - without any params - with > in the template, instead of < All of these prodoced the very same output, which I would like to avoid. My question is how to come over this problem? The XSLT spec says, then disable-output-escaping should work as I expect it... Thanks for the answer, Gabor Hojtsy [Goba] From veillard@redhat.com Mon Apr 21 09:52:59 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 43C53180D7 for ; Mon, 21 Apr 2003 09:52:59 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3LDqwh22731 for xslt@gnome.org; Mon, 21 Apr 2003 09:52:58 -0400 Date: Mon, 21 Apr 2003 09:52:58 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] disable-output-escaping disfunctional Message-ID: <20030421095258.N18010@redhat.com> References: <3EA3E948.80606@hojtsy.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3EA3E948.80606@hojtsy.hu>; from gabor@hojtsy.hu on Mon, Apr 21, 2003 at 02:51:20PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Apr 21, 2003 at 02:51:20PM +0200, Gabor Hojtsy wrote: > I have tried the above with: > > - disable-output-escaping="no" [...] > All of these prodoced the very same output, which I would like to avoid. > My question is how to come over this problem? The XSLT spec says, then > disable-output-escaping should work as I expect it... reread the spec ... disable-output-escaping="yes" Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From gabor@hojtsy.hu Mon Apr 21 10:27:07 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from vadangyal.vnet.hu (mail.vnet.hu [213.163.59.4]) by mail.gnome.org (Postfix) with ESMTP id 0D5F8180D7 for ; Mon, 21 Apr 2003 10:27:07 -0400 (EDT) Received: from hojtsy.hu (62-77-248-55.vnet.hu [62.77.248.55]) by mail.vnet.hu (iPlanet Messaging Server 5.1 Patch 1 (built Jun 6 2002)) with ESMTPA id <0HDP00B5M6T310@mail.vnet.hu> for xslt@gnome.org; Mon, 21 Apr 2003 16:27:06 +0200 (CEST) Date: Mon, 21 Apr 2003 16:28:47 +0200 From: Gabor Hojtsy Subject: Re: [xslt] disable-output-escaping disfunctional To: xslt@gnome.org Message-id: <3EA4001F.9070106@hojtsy.hu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: hu, en, en-us User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > On Mon, Apr 21, 2003 at 02:51:20PM +0200, Gabor Hojtsy wrote: > > I have tried the above with: > > > > - disable-output-escaping="no" > [...] > > All of these prodoced the very same output, which I would like > to avoid. > > My question is how to come over this problem? The XSLT spec > says, then > > disable-output-escaping should work as I expect it... > > reread the spec ... disable-output-escaping="yes" Please reread my letter Daniel. :) As I said, I expected "yes" to work the same way as the spec says. Then I tried "no" and many other options, but everything I have tried resulted in the very same thing, and none of them was what I wanted to achive. I have seen a bugfix about this, but as I am using a way newer version of libxml/libxslt, I expected it to work... BTW versions are (latest available for Windows): C:\>xsltproc -V Using libxml 20506, libxslt 10029 and libexslt 719 xsltproc was compiled against libxml 20506, libxslt 10029 and libexslt 719 libxslt 10029 was compiled against libxml 20506 libexslt 719 was compiled against libxml 20506 And the sheet is using the html output method. Thanks, Goba From veillard@redhat.com Mon Apr 21 10:39:45 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id C7366180D7 for ; Mon, 21 Apr 2003 10:39:44 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3LEdig02728 for xslt@gnome.org; Mon, 21 Apr 2003 10:39:44 -0400 Date: Mon, 21 Apr 2003 10:39:44 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] disable-output-escaping disfunctional Message-ID: <20030421103944.R18010@redhat.com> References: <3EA4001F.9070106@hojtsy.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3EA4001F.9070106@hojtsy.hu>; from gabor@hojtsy.hu on Mon, Apr 21, 2003 at 04:28:47PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Apr 21, 2003 at 04:28:47PM +0200, Gabor Hojtsy wrote: > And the sheet is using the html output method. Which might be the reason. This was not stated in your first mail. And you didn't provide a full example (xml + xsl) demonstrating the problem as requested by: http://xmlsoft.org/XSLT/bugs.html Yes I tend to spend very little time on report where the reporter didn't spent the time to actually formulate the problem as asked, sorry, life is too short... Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From gabor@hojtsy.hu Mon Apr 21 10:57:37 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from vadangyal.vnet.hu (mail.vnet.hu [213.163.59.4]) by mail.gnome.org (Postfix) with ESMTP id 25863180D7 for ; Mon, 21 Apr 2003 10:57:37 -0400 (EDT) Received: from hojtsy.hu (62-77-248-55.vnet.hu [62.77.248.55]) by mail.vnet.hu (iPlanet Messaging Server 5.1 Patch 1 (built Jun 6 2002)) with ESMTPA id <0HDP00B7087L2H@mail.vnet.hu> for xslt@gnome.org; Mon, 21 Apr 2003 16:57:37 +0200 (CEST) Date: Mon, 21 Apr 2003 16:59:02 +0200 From: Gabor Hojtsy Subject: Re: [xslt] disable-output-escaping disfunctional To: xslt@gnome.org Message-id: <3EA40736.70303@hojtsy.hu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: hu, en, en-us User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > On Mon, Apr 21, 2003 at 04:28:47PM +0200, Gabor Hojtsy wrote: > > And the sheet is using the html output method. > > Which might be the reason. This was not stated in your first mail. > And you didn't provide a full example (xml + xsl) demonstrating the > problem > as requested by: > http://xmlsoft.org/XSLT/bugs.html > > Yes I tend to spend very little time on report where the reporter > didn't spent the time to actually formulate the problem as asked, > > sorry, life is too short... No problem, I also provide open support at some places, and are familiar with such guys asking silly and/or irrelevant questions. :) *But* rereading my mail, it is clear that I am using an xsl:text tag, which is not connected to any XML source data. So presenting any XML files used would be out of context, and a reason for confusion. So as the problem is not in connection with any XML source data, I have not included any... By the way, I'll work on on my own, and will try to find the solution... Goba From veillard@redhat.com Mon Apr 21 11:17:40 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 7DB9318566 for ; Mon, 21 Apr 2003 11:17:40 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3LFHeM14580 for xslt@gnome.org; Mon, 21 Apr 2003 11:17:40 -0400 Date: Mon, 21 Apr 2003 11:17:40 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] disable-output-escaping disfunctional Message-ID: <20030421111740.S18010@redhat.com> References: <3EA40736.70303@hojtsy.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3EA40736.70303@hojtsy.hu>; from gabor@hojtsy.hu on Mon, Apr 21, 2003 at 04:59:02PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Apr 21, 2003 at 04:59:02PM +0200, Gabor Hojtsy wrote: > No problem, I also provide open support at some places, and are familiar > with such guys asking silly and/or irrelevant questions. :) > > *But* rereading my mail, it is clear that I am using an xsl:text tag, > which is not connected to any XML source data. So presenting any XML > files used would be out of context, and a reason for confusion. So as > the problem is not in connection with any XML source data, I have not > included any... > > By the way, I'll work on on my own, and will try to find the solution... Only a reproductible testcase allows me to put a breakpoint at the right location on xsltproc and find quickly where the problem might be. If you don't provide the input, then I have to *GUESS* and this takes time I don't have. You still didn't provided that stylesheet. There is a *HUGE* amount of things which may influence the serializer, for example HTML and XML code path are *totally* different. There is no excuse to not providing the input, I need the XSLT and even if the XML is then I don't have to spend time figuring out if it is needed or not. You may spend 4 hours trying on your side, or spend 2mn providing me the input and letting me figure it out in 5mn if you like, the only thing if that I won't spend the 4 hours guessing if you do not spend the time to put an attachment to your mail... Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From gabor@hojtsy.hu Mon Apr 21 12:10:53 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from vadangyal.vnet.hu (mail.vnet.hu [213.163.59.4]) by mail.gnome.org (Postfix) with ESMTP id 14CFE1810C for ; Mon, 21 Apr 2003 12:10:52 -0400 (EDT) Received: from hojtsy.hu (62-77-248-55.vnet.hu [62.77.248.55]) by mail.vnet.hu (iPlanet Messaging Server 5.1 Patch 1 (built Jun 6 2002)) with ESMTPA id <0HDP00BETBLZ5G@mail.vnet.hu> for xslt@gnome.org; Mon, 21 Apr 2003 18:10:52 +0200 (CEST) Date: Mon, 21 Apr 2003 18:12:32 +0200 From: Gabor Hojtsy Subject: Re: [xslt] disable-output-escaping disfunctional To: xslt@gnome.org Message-id: <3EA41870.9090508@hojtsy.hu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: hu, en, en-us User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > Only a reproductible testcase allows me to put a breakpoint at the > right location on xsltproc and find quickly where the problem might > be. > If you don't provide the input, then I have to *GUESS* and this > takes time I don't have. > You still didn't provided that stylesheet. There is a *HUGE* > amount of things which may influence the serializer, for example > HTML and XML code path are *totally* different. > There is no excuse to not providing the input, I need the XSLT and > even if the XML is then I don't have to spend time figuring > out if it is needed or not. > > You may spend 4 hours trying on your side, or spend 2mn providing > me the input and letting me figure it out in 5mn if you like, the > only thing if that I won't spend the 4 hours guessing if you do > not spend the time to put an attachment to your mail... Well, what I have done for the last hour is to put up a test case about this, but I was unable to. Using a simple XML document and an XSL file with one template with the xsl:text thing in question everything seems to be working well... The real document is a 13MB 'XML document', and it is the documentation of the PHP language. It is actually a very small XML file with a huge list of external parsed entities, and the sum of all is 13MB. The XSL sheets are the DocBook XSL sheets as a base, and there are some customizations we have. The xsl:text in question is in one of the customizations I am going to get ready for primetime. What I was able to come up with so far is to reduce the source document from 13MB to which is the perfect root element for DocBook. Running our customized DocBook sheets on this still resulted in the bogus behaviour. Having that simple and this simple template: < The problem does not seem to come up. So the bug is probably only appears in a particular stylesheet context... The processor clearly uses the HTML output method (it outputs DOCTYPE information at the top of the output files). I have tried to switch to the XML output method with success, but without 'fixing the bug'. So the output was in XML (eg. and
), but disable-output-escaping still didn't work. So the bug does not seem to be connected to the HTML output method. As disable-output-escaping is a local statement for the xslt processor, it cannot be overriden by it's context. Therefore I still strongly beleive that I have found a bug in xsltproc/libxml and not a bug in the DocBook sheets. I have prepared a 2MB testcase. It includes the DocBook XSL sheets HTML part, and our customizations in question, and a PHP Manual Light ( :) ). In a tgz it is just 220Kb, so I can put it up somewhere in case you are willing to test it, and find out why it is not working. It is fully testable, with an XML file and an XSL sheet (at least it works for me standing alone)... Thanks for being helpful, Goba From veillard@redhat.com Mon Apr 21 12:34:23 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 25AB0184A0 for ; Mon, 21 Apr 2003 12:34:23 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3LGYM105309 for xslt@gnome.org; Mon, 21 Apr 2003 12:34:22 -0400 Date: Mon, 21 Apr 2003 12:34:22 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] disable-output-escaping disfunctional Message-ID: <20030421123422.T18010@redhat.com> References: <3EA41870.9090508@hojtsy.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3EA41870.9090508@hojtsy.hu>; from gabor@hojtsy.hu on Mon, Apr 21, 2003 at 06:12:32PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Apr 21, 2003 at 06:12:32PM +0200, Gabor Hojtsy wrote: > The processor clearly uses the HTML output method (it outputs DOCTYPE > information at the top of the output files). I have tried to switch to > the XML output method with success, but without 'fixing the bug'. So the > output was in XML (eg.
and
), but > disable-output-escaping still didn't work. So the bug does not seem to > be connected to the HTML output method. > > As disable-output-escaping is a local statement for the xslt processor, > it cannot be overriden by it's context. Therefore I still strongly > beleive that I have found a bug in xsltproc/libxml and not a bug in the > DocBook sheets. Have you read the following from the spec 16.4 Disabling Output Escaping: "It is an error for output escaping to be disabled for a text node that is used for something other than a text node in the result tree. Thus, it is an error to disable output escaping for an xsl:value-of or xsl:text element that is used to generate the string-value of a comment, processing instruction or attribute node; it is also an error to convert a result tree fragment to a number or a string if the result tree fragment contains a text node for which escaping was disabled. In both cases, an XSLT processor may signal the error; if it does not signal the error, it must recover by ignoring the disable-output-escaping attribute." So basically if you use disable-output-escaping for something which is not a text node immediately used as output then, it is normal for libxslt/xsltproc to ignore that statement completely. Like if you use it to build a variable or a result value tree passed to a node-set() extension then this is guaranteed to be ignored rightfully. In general the rule is *do not use disable-output-escaping" ! It just prove you're trying to do something which is wrong from a structure transformation point of view. > I have prepared a 2MB testcase. It includes the DocBook XSL sheets HTML > part, and our customizations in question, and a PHP Manual Light > ( :) ). In a tgz it is just 220Kb, so I can put it up somewhere > in case you are willing to test it, and find out why it is not working. > It is fully testable, with an XML file and an XSL sheet (at least it > works for me standing alone)... Please check first for what I just pointed out, if this is not the case then yes put it online somewhere. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From gabor@hojtsy.hu Mon Apr 21 13:27:55 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from vadangyal.vnet.hu (mail.vnet.hu [213.163.59.4]) by mail.gnome.org (Postfix) with ESMTP id 8A3CE18157 for ; Mon, 21 Apr 2003 13:27:55 -0400 (EDT) Received: from hojtsy.hu (62-77-248-55.vnet.hu [62.77.248.55]) by mail.vnet.hu (iPlanet Messaging Server 5.1 Patch 1 (built Jun 6 2002)) with ESMTPA id <0HDP00BV8F6CA5@mail.vnet.hu> for xslt@gnome.org; Mon, 21 Apr 2003 19:27:55 +0200 (CEST) Date: Mon, 21 Apr 2003 19:29:34 +0200 From: Gabor Hojtsy Subject: Re: [xslt] disable-output-escaping disfunctional In-reply-to: <20030421123422.T18010@redhat.com> To: xslt@gnome.org Message-id: <3EA42A7E.6090009@hojtsy.hu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: hu, en, en-us User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 References: <3EA41870.9090508@hojtsy.hu> <20030421123422.T18010@redhat.com> Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: >>As disable-output-escaping is a local statement for the xslt processor, >>it cannot be overriden by it's context. Therefore I still strongly >>beleive that I have found a bug in xsltproc/libxml and not a bug in the >>DocBook sheets. > > Have you read the following from the spec 16.4 Disabling Output Escaping: > > "It is an error for output escaping to be disabled for a text node that > is used for something other than a text node in the result tree. Thus, > it is an error to disable output escaping for an xsl:value-of or xsl:text > element that is used to generate the string-value of a comment, processing > instruction or attribute node; it is also an error to convert a result > tree fragment to a number or a string if the result tree fragment > contains a text node for which escaping was disabled. In both cases, > an XSLT processor may signal the error; if it does not signal the error, > it must recover by ignoring the disable-output-escaping attribute." > > So basically if you use disable-output-escaping for something which > is not a text node immediately used as output then, it is normal for > libxslt/xsltproc to ignore that statement completely. Like if you use > it to build a variable or a result value tree passed to a node-set() > extension then this is guaranteed to be ignored rightfully. > In general the rule is *do not use disable-output-escaping* ! > It just prove you're trying to do something which is wrong from a > structure transformation point of view. Well, maybe what I am trying to do is wrong. :( I have read that statement above, *but* was unaware of the method used to generate separate chunks. The PHP manual from it's 13MB source size comes down to 19MB of PHP files (~3200 files). To generate these files, is used, and the content of the chunks is copied there with , which is probably very similarly handled as mentioned in the spec. While the template itself generates a text node, it is not immediately sent out to the output, but stored in a variable for chunking, so it is affected by the rule you quoted above. Well, it is at least clear to me, that there is no way to make that disable-output-escaping work there, and we need to add a postprocessor that runs after xsltproc to make the output ready for PHP. Just a very simple test case for reference, for anybody finding this message in a search engine searching for a solution ;) XSLT: > XML:
This outputs >, regardless of the disable-output-escaping="yes" setting, and as you pointed out, this is perfectly in conformance with the XSLT spec. I am so said coming to this conclusion, but I am closer to a solution at least... Thanks for your help, and excuse me for waisting your time, Goba From veillard@redhat.com Mon Apr 21 18:42:29 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 4A6B0185C3 for ; Mon, 21 Apr 2003 18:42:29 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3LMgTG10121 for xslt@gnome.org; Mon, 21 Apr 2003 18:42:29 -0400 Date: Mon, 21 Apr 2003 18:42:28 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] disable-output-escaping disfunctional Message-ID: <20030421184228.U18010@redhat.com> References: <3EA41870.9090508@hojtsy.hu> <20030421123422.T18010@redhat.com> <3EA42A7E.6090009@hojtsy.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3EA42A7E.6090009@hojtsy.hu>; from gabor@hojtsy.hu on Mon, Apr 21, 2003 at 07:29:34PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Apr 21, 2003 at 07:29:34PM +0200, Gabor Hojtsy wrote: > Well, it is at least clear to me, that there is no way to make that > disable-output-escaping work there, and we need to add a postprocessor > that runs after xsltproc to make the output ready for PHP. Maybe the premice is true, but the conclusion might be a bit hasty. What is it exactly that you are trying to generate, there might be better ways than disable-output-escaping ... Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From gabor@hojtsy.hu Tue Apr 22 06:45:53 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from vadangyal.vnet.hu (mail.vnet.hu [213.163.59.4]) by mail.gnome.org (Postfix) with ESMTP id 2686D180E0 for ; Tue, 22 Apr 2003 06:45:53 -0400 (EDT) Received: from developer2 (adsl107.226.axelero.hu [195.228.226.107]) by mail.vnet.hu (iPlanet Messaging Server 5.1 Patch 1 (built Jun 6 2002)) with ESMTPA id <0HDQ00C8OR8GQU@mail.vnet.hu> for xslt@gnome.org; Tue, 22 Apr 2003 12:45:52 +0200 (CEST) Date: Tue, 22 Apr 2003 12:41:39 +0200 From: Gabor Hojtsy Subject: Re: [xslt] disable-output-escaping disfunctional To: xslt@gnome.org Message-id: <004a01c308bb$c1819f30$0f00000a@developer2> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <3EA41870.9090508@hojtsy.hu> <20030421123422.T18010@redhat.com> <3EA42A7E.6090009@hojtsy.hu> <20030421184228.U18010@redhat.com> Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > > Well, it is at least clear to me, that there is no way to make that > > disable-output-escaping work there, and we need to add a postprocessor > > that runs after xsltproc to make the output ready for PHP. > > Maybe the premice is true, but the conclusion might be a bit hasty. > What is it exactly that you are trying to generate, there might be > better ways than disable-output-escaping ... Well, I have found out that putting those things into PI generating XSL tags, the output-escaping gets disabled. I hope it is not a bug of xsltproc :), though it seems it is form the spec: | Thus, it is an error to disable output escaping for | an xsl:value-of or xsl:text element that is used to | generate the string-value of a comment, processing | instruction or attribute node I would be said, if it turns out that this is a bug, and it gets fixed... BTW what I would like to generate are PHP associative array structures, which are defined this way: $colors = array( "grass" => "green", "lemon" => "yellow" ); Here > is needed, and it is quite odd looking to generate some other code to fill in the array, just to not contain >... Goba From sbwoodside@yahoo.com Tue Apr 22 21:11:28 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from tomts22-srv.bellnexxia.net (tomts22-srv.bellnexxia.net [209.226.175.184]) by mail.gnome.org (Postfix) with ESMTP id D9F6F180F5 for ; Tue, 22 Apr 2003 21:11:27 -0400 (EDT) Received: from yahoo.com ([65.93.189.40]) by tomts22-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20030423011126.ZYBD26395.tomts22-srv.bellnexxia.net@yahoo.com>; Tue, 22 Apr 2003 21:11:26 -0400 Date: Tue, 22 Apr 2003 21:11:26 -0400 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed From: S Woodside To: axkit-users@axkit.org, xslt@gnome.org Content-Transfer-Encoding: 7bit Message-Id: <81836219-7528-11D7-89E4-000393414368@yahoo.com> X-Mailer: Apple Mail (2.552) Subject: [xslt] bug? warning given as error Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: This seems like a possible bug in Apache::AxKit::Provider::File. For a document() call on a non-existing file, xsltproc gives a warning, on the same test files AxKit gives an error. Using libxml 20506, libxslt 10029 and libexslt 719 AxKit 1.6.1 I generated a simple testcase. ========================= test.xml ========================= bar ========================= test.xsl ========================= ========================= Output in xsltproc & AxKit ========================= foobar ========================= Error condition ========================= Change the line marked with *** to: ========================= Output in xsltproc ========================= % xsltproc test.xml warning: failed to load external entity "test.xmasdfl" foo ========================= Output in AxKit ========================= ... [Tue Apr 22 21:00:30 2003] [warn] [client 127.0.0.1] [AxKit] [LibXSLT] performing transformation [Tue Apr 22 21:00:30 2003] [warn] [client 127.0.0.1] [AxKit] LibXSLT match_uri: /test.xmasdfl [Tue Apr 22 21:00:30 2003] [warn] [client 127.0.0.1] [AxKit] LibXSLT open_content_uri: /test.xmasdfl [Tue Apr 22 21:00:30 2003] [warn] [client 127.0.0.1] [AxKit] Content Provider Override: Apache::AxKit::Provider::File [Tue Apr 22 21:00:30 2003] [warn] [client 127.0.0.1] [AxKit] decoding from UTF-8 [Tue Apr 22 21:00:30 2003] [warn] [client 127.0.0.1] [AxKit] [req] File Provider given $r: /Library/WebServer/Apache2/test.xmasdfl [Tue Apr 22 21:00:30 2003] [warn] [client 127.0.0.1] [AxKit] encoding to UTF-8 [Tue Apr 22 21:00:30 2003] [warn] [client 127.0.0.1] [AxKit] Caught an exception [Tue Apr 22 21:00:30 2003] [error] [client 127.0.0.1] [AxKit] [UnCaught] File '/Library/WebServer/Apache2/test.xmasdfl' does not exist or is not readable [Tue Apr 22 21:00:30 2003] [error] [client 127.0.0.1] [AxKit] [Backtrace] File '/Library/WebServer/Apache2/test.xmasdfl' does not exist or is not readable at /Library/Perl/Error.pm line 148 Error::throw('Apache::AxKit::Exception::IO', '-text', 'File \'/Library/WebServer/Apache2/test.xmasdfl\' does not exist ...') called at /Library/Perl/darwin/Apache/AxKit/Provider/File.pm line 215 Apache::AxKit::Provider::File::get_fh('Apache::AxKit::Provider::File=HAS H(0x4b18c4)') called at /Library/Perl/darwin/Apache/AxKit/Provider/File.pm line 239 Apache::AxKit::Provider::File::get_strref('Apache::AxKit::Provider::File =HASH(0x4b18c4)') called at /Library/Perl/darwin/Apache/AxKit/Language/LibXSLT.pm line 180 Apache::AxKit::Language::LibXSLT::open_content_uri('/test.xmasdfl') called at /Library/Perl/darwin/Apache/AxKit/Language/LibXSLT.pm line 122 Apache::AxKit::Language::LibXSLT::handler('Apache::AxKit::Language::LibX SLT', 'AxKit::Apache=SCALAR(0x499518)', 'Apache::AxKit::Provider::File=HASH(0x497f28)', 'Apache::AxKit::Provider::File=HASH(0x147320)', 1) called at /Library/Perl/darwin/AxKit.pm line 739 AxKit::process_request('AxKit::Apache=SCALAR(0x499518)', 'Apache::AxKit::Provider::File=HASH(0x497f28)', 'ARRAY(0xa629c8)', undef) called at /Library/Perl/darwin/AxKit.pm line 461 AxKit::run_axkit_engine('AxKit::Apache=SCALAR(0x499518)', 'Apache::AxKit::Provider::File=HASH(0x497f28)') called at /Library/Perl/darwin/AxKit.pm line 288 eval {...} called at /Library/Perl/darwin/AxKit.pm line 279 AxKit::main_handler('AxKit::Apache=SCALAR(0x499518)', 'Apache::AxKit::Provider::File=HASH(0x497f28)') called at /Library/Perl/darwin/AxKit.pm line 247 AxKit::handler('AxKit::Apache=SCALAR(0x499518)') called at /dev/null line 0 eval {...} called at /dev/null line 0 -- www.simonwoodside.com -- 99% Devil, 1% Angel From cow@compsoc.man.ac.uk Tue Apr 22 17:09:03 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by mail.gnome.org (Postfix) with ESMTP id 884C2186C8 for ; Tue, 22 Apr 2003 17:09:03 -0400 (EDT) Received: from compsoc.umu.man.ac.uk ([130.88.22.5] helo=mrtall.compsoc.man.ac.uk ident=exim) by serenity.mcc.ac.uk with esmtp (Exim 4.14) id 19850b-0005eT-Qn for xslt@gnome.org; Tue, 22 Apr 2003 22:08:57 +0100 Received: from cow by mrtall.compsoc.man.ac.uk with local (Exim 3.33 #1) id 19850b-0003TK-00 for xslt@gnome.org; Tue, 22 Apr 2003 22:08:57 +0100 Date: Tue, 22 Apr 2003 22:08:57 +0100 From: Jonathan Wakely To: xslt@gnome.org Message-ID: <20030422210857.GA9361@compsoc.man.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-PGP-Key: http://www.compsoc.man.ac.uk/~cow/pgpkey.asc X-Spam-Score: -13.6 (-------------) X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *19850b-0005eT-Qn*4Gtl0YP/8Hc* Subject: [xslt] [patch] improve libexslt man page Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi, Following on from this mail http://mail.gnome.org/archives/xslt/2003-January/msg00038.html (a mere 3 months later!) here is a patch to improve the libexslt man page. I've listed the header and library name in the SYNOPSIS along with the prototypes for the exslt*Register() functions. In the CALLING section I've added that the registration functions must be called to enable EXSLT support in libxslt. Additionally I've improved the formatting somewhat, based on the man page guidelines at the linux doc. project (www.tldp.org). It now uses a more conventional formatting style (in that I copied it from a number of existing manuals) and the indenting is fixed. I'd like to this patch applied, but ideally I'd also like to see the file renamed from libexslt.4 to libexslt.3 (and the section number changed on the first line of the file) since libraries should be described in section 3 of the manual. If I provide a patch for the necessary changes to Makefile.in could someone else actually rename the file? I'm not sure how to show that in a patch. thanks, jon -- "In times like these, it helps to recall that there have always been times like these." - Paul Harvey From veillard@redhat.com Wed Apr 23 03:14:05 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 4BEDE185D1 for ; Wed, 23 Apr 2003 03:14:05 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3N7E5k25664; Wed, 23 Apr 2003 03:14:05 -0400 Date: Wed, 23 Apr 2003 03:14:04 -0400 From: Daniel Veillard To: xslt@gnome.org Cc: axkit-users@axkit.org Subject: Re: [xslt] bug? warning given as error Message-ID: <20030423031404.E18010@redhat.com> References: <81836219-7528-11D7-89E4-000393414368@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <81836219-7528-11D7-89E4-000393414368@yahoo.com>; from sbwoodside@yahoo.com on Tue, Apr 22, 2003 at 09:11:26PM -0400 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Tue, Apr 22, 2003 at 09:11:26PM -0400, S Woodside wrote: > This seems like a possible bug in Apache::AxKit::Provider::File. For a > document() call on a non-existing file, xsltproc gives a warning, on > the same test files AxKit gives an error. > Using libxml 20506, libxslt 10029 and libexslt 719 > AxKit 1.6.1 The spec states in section 12.1 Multiple Source Documents "If there is an error retrieving the resource, then the XSLT processor may signal an error; if it does not signal an error, it must recover by returning an empty node-set." So both behaviours are correct. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard@redhat.com Wed Apr 23 03:18:49 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 95E6E181F7 for ; Wed, 23 Apr 2003 03:18:49 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3N7Het26480; Wed, 23 Apr 2003 03:17:40 -0400 Date: Wed, 23 Apr 2003 03:17:40 -0400 From: Daniel Veillard To: cow@compsoc.man.ac.uk Cc: xslt@gnome.org Subject: Re: [xslt] [patch] improve libexslt man page Message-ID: <20030423031740.F18010@redhat.com> References: <20030422210857.GA9361@compsoc.man.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030422210857.GA9361@compsoc.man.ac.uk>; from cow@compsoc.man.ac.uk on Tue, Apr 22, 2003 at 10:08:57PM +0100 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Tue, Apr 22, 2003 at 10:08:57PM +0100, Jonathan Wakely wrote: > Hi, > > Following on from this mail > http://mail.gnome.org/archives/xslt/2003-January/msg00038.html > (a mere 3 months later!) here is a patch to improve the libexslt man > page. Hum, didn't you forgot to attach the patch ;-) > I'd like to this patch applied, but ideally I'd also like to see the > file renamed from libexslt.4 to libexslt.3 (and the section number > changed on the first line of the file) since libraries should be > described in section 3 of the manual. If I provide a patch for the > necessary changes to Makefile.in could someone else actually rename > the file? I'm not sure how to show that in a patch. I would do the renaming, yes. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From sbwoodside@yahoo.com Wed Apr 23 03:20:34 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from tomts20-srv.bellnexxia.net (tomts20.bellnexxia.net [209.226.175.74]) by mail.gnome.org (Postfix) with ESMTP id 7863B185D1 for ; Wed, 23 Apr 2003 03:20:33 -0400 (EDT) Received: from yahoo.com ([65.93.189.40]) by tomts20-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20030423072032.MKPZ20140.tomts20-srv.bellnexxia.net@yahoo.com>; Wed, 23 Apr 2003 03:20:32 -0400 Date: Wed, 23 Apr 2003 03:20:31 -0400 Subject: Re: [xslt] bug? warning given as error Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: axkit-users@axkit.org To: xslt@gnome.org From: S Woodside In-Reply-To: <20030423031404.E18010@redhat.com> Message-Id: <10F739B1-755C-11D7-89E4-000393414368@yahoo.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wednesday, April 23, 2003, at 03:14 AM, Daniel Veillard wrote: > On Tue, Apr 22, 2003 at 09:11:26PM -0400, S Woodside wrote: >> This seems like a possible bug in Apache::AxKit::Provider::File. For a >> document() call on a non-existing file, xsltproc gives a warning, on >> the same test files AxKit gives an error. >> Using libxml 20506, libxslt 10029 and libexslt 719 >> AxKit 1.6.1 > > The spec states in section 12.1 Multiple Source Documents > "If there is an error retrieving the resource, then the XSLT processor > may signal an error; if it does not signal an error, it must recover > by returning an empty node-set." > > So both behaviours are correct. > Yes, I know. However the xsltproc behaviour is more useful ... so perhaps it is not a bug but a feature request then, to interpret the spec towards the warning and not the error, in Apache::AxKit::Provider::File or wherever the relevant code is living. simon From sbwoodside@yahoo.com Wed Apr 23 12:18:29 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from tomts24-srv.bellnexxia.net (tomts24.bellnexxia.net [209.226.175.187]) by mail.gnome.org (Postfix) with ESMTP id 404FC18175 for ; Wed, 23 Apr 2003 12:18:29 -0400 (EDT) Received: from yahoo.com ([65.93.183.135]) by tomts24-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20030423161827.ZUUA1119.tomts24-srv.bellnexxia.net@yahoo.com>; Wed, 23 Apr 2003 12:18:27 -0400 Date: Wed, 23 Apr 2003 12:18:27 -0400 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: axkit-users@axkit.org, xslt@gnome.org, xsl-list@lists.mulberrytech.com To: Chris Leishman From: S Woodside In-Reply-To: <36199566-7597-11D7-BE48-003065F97418@leishman.org> Message-Id: <3729D898-75A7-11D7-89E4-000393414368@yahoo.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Subject: [xslt] document not there ambiguity (was: bug? warning given as error) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wednesday, April 23, 2003, at 10:23 AM, Chris Leishman wrote: >> The spec states in section 12.1 Multiple Source Documents >> "If there is an error retrieving the resource, then the XSLT >> processor >> may signal an error; if it does not signal an error, it must recover >> by returning an empty node-set." >> >> So both behaviours are correct. > > ....and people wonder why the different implementations are so > incompatible.... > > Really...what where the W3C thinking? Perhaps someone should start a > list of 'standard implementation choices for implementing the xslt > standard' (rolls eyes) and maybe that'll become YAWNS (Yet Another W3C > uNsuccessful Standard). They're already on the way... the WD for xslt 2.0 says this about "unparsed-text" function "[ERR117] It is a dynamic error if a URI cannot be used to retrieve a resource containing text. The processor must either signal the error, or must recover by treating the URI as if it referenced a resource containing a zero-length string." Just glancing at the XPath 2.0 / xquery 1.0 WD I can't tell but it seems the same for fn:document: 14.5.3 "An error in processing the fragment identifier is classed as a dynamic error. In such cases, then an error is raised ("Error processing fragment identifier"), or the processor must recover by returning an empty sequence." hooray :-\ simon -- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel From Mark_Vakoc@jdedwards.com Wed Apr 23 16:48:05 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from ns2.jdedwards.com (ns2.jdedwards.com [199.166.248.75]) by mail.gnome.org (Postfix) with ESMTP id 5AAD41865F for ; Wed, 23 Apr 2003 16:48:04 -0400 (EDT) Received: from denvscans4.jdedwards.com ([10.0.14.76]) by ns2.jdedwards.com (8.11.6/8.9.1) with SMTP id h3NKm3M15787 for ; Wed, 23 Apr 2003 14:48:04 -0600 Received: from 10.0.14.51 by denvscans4.jdedwards.com (InterScan E-Mail VirusWall NT); Wed, 23 Apr 2003 14:48:03 -0600 Received: by cormails11.jdedwards.com with Internet Mail Service (5.5.2653.19) id ; Wed, 23 Apr 2003 14:53:00 -0600 Message-ID: <09B3671D58690A4193A7F8F15F416B23FF2588@denmails3.jdedwards.com> From: "Vakoc, Mark" To: "'xslt@gnome.org'" Date: Wed, 23 Apr 2003 14:47:59 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C309D9.9FDC7433" Subject: [xslt] str:tokenize behavior Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C309D9.9FDC7433 Content-Type: text/plain; charset="iso-8859-1" Hey Daniel, it's back... The attached stylesheet seems to exhibit incorrect behavior when using str:tokenize() in the select of . Does xsltForEach need to check that the node-set obtained from evaluating is a RTF and if so call the applyOneTemplate on the children of the 'container' element? ---------------------------------------------------------------------------- --------------------------- C:\test>type tokenize.xsl C:\test>gssxslt tokenize.xsl tokenize.xsl Thisisstrangebehavior C:\test>gssxslt --version Using libxml 20506, libxslt 10029 and libexslt 719 xsltproc was compiled against libxml 20506, libxslt 10029 and libexslt 719 libxslt 10029 was compiled against libxml 20506 libexslt 719 was compiled against libxml 20506 C:\test> ---------------------------------------------------------------------------- --------------------------------- I would expect output along the lines of Thisisstrangebehavior Thanks. <> ------_=_NextPart_000_01C309D9.9FDC7433 Content-Type: application/octet-stream; name="tokenize.xsl" Content-Disposition: attachment; filename="tokenize.xsl" ------_=_NextPart_000_01C309D9.9FDC7433-- From veillard@redhat.com Wed Apr 23 19:40:13 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 75D9B187C9 for ; Wed, 23 Apr 2003 19:40:13 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3NNe6f22479 for xslt@gnome.org; Wed, 23 Apr 2003 19:40:06 -0400 Date: Wed, 23 Apr 2003 19:40:06 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] str:tokenize behavior Message-ID: <20030423194006.R18010@redhat.com> References: <09B3671D58690A4193A7F8F15F416B23FF2588@denmails3.jdedwards.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <09B3671D58690A4193A7F8F15F416B23FF2588@denmails3.jdedwards.com>; from Mark_Vakoc@jdedwards.com on Wed, Apr 23, 2003 at 02:47:59PM -0600 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wed, Apr 23, 2003 at 02:47:59PM -0600, Vakoc, Mark wrote: > Hey Daniel, it's back... > > The attached stylesheet seems to exhibit incorrect behavior when using > str:tokenize() in the select of . Does xsltForEach need to > check that the node-set obtained from evaluating is a RTF and if so call the > applyOneTemplate on the children of the 'container' element? Yup, looks like the problem. Plus the tokenize function returns an XPATH_NODESET intead of a XPATH_XSLT_TREE making the detection nearly impossible ... In a nutshell seems: - the tokenize function need to return a XPATH_XSLT_TREE (easy) - xsltForEach need to detect the case of and XPATH_XSLT_TREE and iterate on the children instead of the document node. I'm off to bed, maybe tomorrow... But I would like to get a release out I'm not sure if I will block due to EXSLT... Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From Mark_Vakoc@jdedwards.com Thu Apr 24 00:36:13 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from ns1.jdedwards.com (ns1.jdedwards.com [199.166.248.147]) by mail.gnome.org (Postfix) with ESMTP id E2907180D9 for ; Thu, 24 Apr 2003 00:36:12 -0400 (EDT) Received: from denvscans3.jdedwards.com ([10.0.14.77]) by ns1.jdedwards.com (8.11.6/8.9.1) with SMTP id h3O4aCE15029 for ; Wed, 23 Apr 2003 22:36:12 -0600 Received: from 10.0.14.51 by denvscans3.jdedwards.com (InterScan E-Mail VirusWall NT); Wed, 23 Apr 2003 22:36:11 -0600 Received: by cormails11.jdedwards.com with Internet Mail Service (5.5.2653.19) id ; Wed, 23 Apr 2003 22:41:09 -0600 Message-ID: <09B3671D58690A4193A7F8F15F416B23111B2B@denmails3.jdedwards.com> From: "Vakoc, Mark" To: "'xslt@gnome.org'" Subject: RE: [xslt] str:tokenize behavior Date: Wed, 23 Apr 2003 22:36:07 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > Yup, looks like the problem. Plus the tokenize function returns > an XPATH_NODESET intead of a XPATH_XSLT_TREE making the detection >nearly impossible ... In a nutshell seems: > - the tokenize function need to return a XPATH_XSLT_TREE (easy) > - xsltForEach need to detect the case of and XPATH_XSLT_TREE > and iterate on the children instead of the document node. Hmmm... This could be a little tough. If the function returns XPATH_XSLT_TREE and xsltForEach treats this as a node set then that would allow essentially allow xsltForEach to work against any RTF, which isn't correct, such as below ..... Somehow we need to know that the RTF returned by extension functions such as str:tokenize isn't a RTF like the one created above. That is why I had it return the XPATH_NODESET object type. Might the solution be to internally create a new xpath object type, say XPATH_XSLT_NODESET for extension functions that return RTF node-sets? This way libxslt can know when iterating across the nodes using xsl:for-each and xsl:apply-templates against a extension function's return RTF is legal and not perform an automatic node-set() conversion against actual RTFs. I'll look into this tomorrow as well. Mark From veillard@redhat.com Thu Apr 24 04:53:03 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 0918018115 for ; Thu, 24 Apr 2003 04:53:03 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3O8r2K27692 for xslt@gnome.org; Thu, 24 Apr 2003 04:53:02 -0400 Date: Thu, 24 Apr 2003 04:53:02 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] str:tokenize behavior Message-ID: <20030424045302.V18010@redhat.com> References: <09B3671D58690A4193A7F8F15F416B23111B2B@denmails3.jdedwards.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <09B3671D58690A4193A7F8F15F416B23111B2B@denmails3.jdedwards.com>; from Mark_Vakoc@jdedwards.com on Wed, Apr 23, 2003 at 10:36:07PM -0600 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wed, Apr 23, 2003 at 10:36:07PM -0600, Vakoc, Mark wrote: > > Yup, looks like the problem. Plus the tokenize function returns > > an XPATH_NODESET intead of a XPATH_XSLT_TREE making the detection > >nearly impossible ... In a nutshell seems: > > - the tokenize function need to return a XPATH_XSLT_TREE (easy) > > - xsltForEach need to detect the case of and XPATH_XSLT_TREE > > and iterate on the children instead of the document node. > > Hmmm... This could be a little tough. If the function returns > XPATH_XSLT_TREE and xsltForEach treats this as a node set then that would > allow essentially allow xsltForEach to work against any RTF, which isn't > correct, such as below > > > > ..... > > Somehow we need to know that the RTF returned by extension functions such as > str:tokenize isn't a RTF like the one created above. That is why I had it > return the XPATH_NODESET object type. Hum, there is 2 options: - either this must behave like a node set, an in this case the nodeset should contain the list of nodes not, the parent document element - or check in xsltForEach for the boolean bit of the XPATH_NODESET nodeset object, and if there is only one node, it's a doc with the "fake" name then process at the children level. Seems to me the first option is the most coherent. > Might the solution be to internally create a new xpath object type, say > XPATH_XSLT_NODESET for extension functions that return RTF node-sets? This > way libxslt can know when iterating across the nodes using xsl:for-each and > xsl:apply-templates against a extension function's return RTF is legal and > not perform an automatic node-set() conversion against actual RTFs. Well adding one more type would make the code even more complex. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From Mark_Vakoc@jdedwards.com Thu Apr 24 13:09:36 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from ns1.jdedwards.com (ns1.jdedwards.com [199.166.248.147]) by mail.gnome.org (Postfix) with ESMTP id 33BEA185E8 for ; Thu, 24 Apr 2003 13:09:36 -0400 (EDT) Received: from denvscans3.jdedwards.com ([10.0.14.77]) by ns1.jdedwards.com (8.11.6/8.9.1) with SMTP id h3OH9ZE13317 for ; Thu, 24 Apr 2003 11:09:35 -0600 Received: from 10.0.14.51 by denvscans3.jdedwards.com (InterScan E-Mail VirusWall NT); Thu, 24 Apr 2003 11:09:35 -0600 Received: by cormails11.jdedwards.com with Internet Mail Service (5.5.2653.19) id ; Thu, 24 Apr 2003 11:14:33 -0600 Message-ID: <09B3671D58690A4193A7F8F15F416B23111B2C@denmails3.jdedwards.com> From: "Vakoc, Mark" To: "'xslt@gnome.org'" Subject: RE: [xslt] str:tokenize behavior Date: Thu, 24 Apr 2003 11:09:31 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > Hum, there is 2 options: > - either this must behave like a node set, an in this case the > nodeset should contain the list of nodes not, the > parent document > element > - or check in xsltForEach for the boolean bit of the XPATH_NODESET > nodeset object, and if there is only one node, it's a doc with > the "fake" name then process at the children level. > Seems to me the first option is the most coherent. > So if I'm understanding option one correctly it would look something like this: container = xmlNewDoc(NULL); if (container != NULL) { container->name = (char *) xmlStrdup(BAD_CAST " fake node libxslt"); container->doc = container; ret = xmlXPathNewValueTree(NULL); if (ret != NULL) { /* Create your RTF nodes here */ xmlNodePtr cur = xmlNewChild((xmlNodePtr) container,NULL,"token",NULL); if (cur) xmlXPathNodeSetAdd(ret->nodesetval,cur); } The nodes would get freed properly because ret->user = container Also, if this is hte approach, wouldn't exsl:node-set need to be modified to added the children nodes of 'container' to hte nodeset (and remove container itself) when converting from XPATH_XSLT_TREE to XPATH_NODESET? From jpesenti@yahoo.com Thu Apr 24 14:01:25 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from web12304.mail.yahoo.com (web12304.mail.yahoo.com [216.136.173.102]) by mail.gnome.org (Postfix) with SMTP id 0972418704 for ; Thu, 24 Apr 2003 14:01:25 -0400 (EDT) Message-ID: <20030424180124.32919.qmail@web12304.mail.yahoo.com> Received: from [12.101.25.68] by web12304.mail.yahoo.com via HTTP; Thu, 24 Apr 2003 11:01:24 PDT Date: Thu, 24 Apr 2003 11:01:24 -0700 (PDT) From: Jerome Pesenti To: xslt@gnome.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [xslt] BUG: @xxx intepreted as */@xxx in match ? Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Here is an example. Regards, Jerome [pesenti@dev /tmp]$ cat test.xsl NAME [pesenti@dev /tmp]$ [pesenti@dev /tmp]$ xsltproc test.xsl test.xsl NAME xsl:template NAME xsl:template NAME [pesenti@dev /tmp]$ xsltproc --version Using libxml 20430, libxslt 10024 and libexslt 715 xsltproc was compiled against libxml 20430, libxslt 10024 and libexslt 715 libxslt 10024 was compiled against libxml 20430 libexslt 715 was compiled against libxml 20430 On RedHat 7.2 __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com From fl@opikanoba.org Fri Apr 25 07:38:19 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from localhost (AStrasbourg-206-1-28-33.abo.wanadoo.fr [81.48.244.33]) by mail.gnome.org (Postfix) with ESMTP id 0B26918281 for ; Fri, 25 Apr 2003 07:38:19 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 2AD9D383E9 for ; Fri, 25 Apr 2003 13:38:20 +0200 (CEST) From: =?iso-8859-15?q?Fr=E9d=E9ric=20Laurent?= To: xslt@gnome.org Date: Fri, 25 Apr 2003 13:38:19 +0200 User-Agent: KMail/1.5 Organization: http://www.opikanoba.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200304251338.19692.fl@opikanoba.org> Subject: [xslt] confirmation of comprehension :-) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi I'm interessed in xslt extension with xsltproc. I write a simple extension function wich I plan to use in my xsl stylesheet. Then in order to do my simple test with these=20 extension function, can I tell the xsltproc program to register my own function and make a xsltproc foo.xsl foo.xml ? As I read the documentation, I have to write=20 a main C program, which =2D register the extension function =2D call the xslt process (in the same way of the python example : http://xmlsoft.org/XSLT/python.htm= l) In these case, I can't use the xsltproc as is... Am I right ? thanks in advance =2D-=20 =46r=E9d=E9ric Laurent http://www.opikanoba.org From veillard@redhat.com Fri Apr 25 07:52:02 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 8272E182C8 for ; Fri, 25 Apr 2003 07:52:02 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3PBq2U10489 for xslt@gnome.org; Fri, 25 Apr 2003 07:52:02 -0400 Date: Fri, 25 Apr 2003 07:52:02 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] confirmation of comprehension :-) Message-ID: <20030425075202.K18010@redhat.com> References: <200304251338.19692.fl@opikanoba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <200304251338.19692.fl@opikanoba.org>; from fl@opikanoba.org on Fri, Apr 25, 2003 at 01:38:19PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 25, 2003 at 01:38:19PM +0200, Frédéric Laurent wrote: > As I read the documentation, I have to write > a main C program, which > - register the extension function > - call the xslt process > (in the same way of the python example : http://xmlsoft.org/XSLT/python.html) > In these case, I can't use the xsltproc as is... > > Am I right ? yes, Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From frederic.laurent@opikanoba.org Fri Apr 25 08:09:38 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from localhost (AStrasbourg-206-1-28-33.abo.wanadoo.fr [81.48.244.33]) by mail.gnome.org (Postfix) with ESMTP id 5DEB1189BA for ; Fri, 25 Apr 2003 08:09:38 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 992E9383E9 for ; Fri, 25 Apr 2003 14:09:40 +0200 (CEST) From: =?iso-8859-1?q?Fr=E9d=E9ric=20Laurent?= Organization: http://www.opikanoba.org To: xslt@gnome.org Subject: Re: [xslt] confirmation of comprehension :-) Date: Fri, 25 Apr 2003 14:09:39 +0200 User-Agent: KMail/1.5 References: <200304251338.19692.fl@opikanoba.org> <20030425075202.K18010@redhat.com> In-Reply-To: <20030425075202.K18010@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200304251409.39766.frederic.laurent@opikanoba.org> Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Friday 25 April 2003 13:52, Daniel Veillard wrote: > On Fri, Apr 25, 2003 at 01:38:19PM +0200, Fr=E9d=E9ric Laurent wrote: > > As I read the documentation, I have to write > > a main C program, which > > - register the extension function > > - call the xslt process > > (in the same way of the python example : > > http://xmlsoft.org/XSLT/python.html) In these case, I can't use the > > xsltproc as is... > > > > Am I right ? > > yes, > > Daniel Thanks Daniel for your quick response. Another question : is it planned to provide a simple mecanism for adding extension functions in order to avoid the writing a C program that have to register it and launch the processor ? Like xalan, for instance, where nothing have to be done to use your own function... simple question, no particular need behind... thanks =2D-=20 =46r=E9d=E9ric Laurent http://www.opikanoba.org From rm@mh-freiburg.de Sat Apr 26 12:02:27 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from forte.mh-freiburg.de (mail.mh-freiburg.de [193.197.131.2]) by mail.gnome.org (Postfix) with ESMTP id 804DC18458 for ; Sat, 26 Apr 2003 12:02:26 -0400 (EDT) Received: from forte (forte [127.0.0.1]) by forte.mh-freiburg.de (Postfix) with ESMTP id D63981B334B for ; Sat, 26 Apr 2003 18:02:24 +0200 (MEST) Received: from forte.mh-freiburg.de (forte [127.0.0.1]) by forte (AvMailGate-2.0.1.10) id 11555-6AA92D42; Sat, 26 Apr 2003 18:02:00 +0200 Received: by forte.mh-freiburg.de (Postfix, from userid 104) id 17BC61B334B; Sat, 26 Apr 2003 18:02:00 +0200 (MEST) Date: Sat, 26 Apr 2003 18:02:00 +0200 To: xslt@gnome.org Subject: Re: [xslt] confirmation of comprehension :-) Message-ID: <20030426180200.A11471@forte.mh-freiburg.de> References: <200304251338.19692.fl@opikanoba.org> <20030425075202.K18010@redhat.com> <200304251409.39766.frederic.laurent@opikanoba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <200304251409.39766.frederic.laurent@opikanoba.org>; from frederic.laurent@opikanoba.org on Fri, Apr 25, 2003 at 02:09:39PM +0200 From: rm@mh-freiburg.de (Le grande pinguin) X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.10; AVE: 6.19.0.3; VDF: 6.19.0.8; host: forte) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Apr 25, 2003 at 02:09:39PM +0200, Fr?d?ric Laurent wrote: > On Friday 25 April 2003 13:52, Daniel Veillard wrote: > > On Fri, Apr 25, 2003 at 01:38:19PM +0200, Fr?d?ric Laurent wrote: > > > As I read the documentation, I have to write > > > a main C program, which > > > - register the extension function > > > - call the xslt process > > > (in the same way of the python example : > > > http://xmlsoft.org/XSLT/python.html) In these case, I can't use the > > > xsltproc as is... > > > > > > Am I right ? > > > > yes, > > > > Daniel > > Thanks Daniel for your quick response. > Another question : is it planned to provide a simple > mecanism for adding extension functions in order to > avoid the writing a C program that have to register > it and launch the processor ? > Like xalan, for instance, where nothing have to be > done to use your own function... Hmm, you need to code the extension in java, or? Since xsltproc is open source it seems like little overhead. I could imagine a plugin architecture, but that would mean dealing with dynamically loaded libs (and that's a pain, even with libtool -- or maybe partly because of). If there's interest i could provide some code, but i never tested it outside the realms of OSs in my office ;-) Ralf Mattes > simple question, no particular need behind... > > thanks > > -- > Fr?d?ric Laurent > http://www.opikanoba.org > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt From igor@zlatkovic.com Sun Apr 27 10:08:12 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from post.webmailer.de (natsmtp01.webmailer.de [192.67.198.81]) by mail.gnome.org (Postfix) with ESMTP id 5BDDE1832C for ; Sun, 27 Apr 2003 10:08:12 -0400 (EDT) Received: from mail.zlatkovic.com (pD9E268FC.dip.t-dialin.net [217.226.104.252]) by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h3RE8BCt029246 for ; Sun, 27 Apr 2003 16:08:11 +0200 (MEST) Received: from 192.168.9.72 (ident=unknown) by mail.zlatkovic.com with smtp (MasqMail 0.1.16) id 199mp8-6Op-00 for xslt@gnome.org; Sun, 27 Apr 2003 16:08:10 +0200 Message-ID: <001101c30cc6$70687e20$4809a8c0@raven> From: Igor Zlatkovic To: Date: Sun, 27 Apr 2003 16:08:12 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [xslt] elem uninitialised? Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi there, In the file variables.c, on the line 757, a variable 'elem' is declared: xsltStackElemPtr elem; The next time this variable is referenced on the line 810, with: xsltFreeStackElem(elem); Should this be executed, elem will contain garbage at the point it is passed to xsltFreeStackElem, because it was never initialised. That doesn't look right. Should I fix? Ciao, Igor From igor@zlatkovic.com Sun Apr 27 12:18:40 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from post.webmailer.de (natsmtp00.webmailer.de [192.67.198.74]) by mail.gnome.org (Postfix) with ESMTP id 38BED183B8; Sun, 27 Apr 2003 12:18:40 -0400 (EDT) Received: from mail.zlatkovic.com (pD9E268FC.dip.t-dialin.net [217.226.104.252]) by post.webmailer.de (8.12.8/8.8.7) with ESMTP id h3RGIYhj019893; Sun, 27 Apr 2003 18:18:35 +0200 (MEST) Received: from 192.168.9.72 (ident=unknown) by mail.zlatkovic.com with smtp (MasqMail 0.1.16) id 199orK-70I-00; Sun, 27 Apr 2003 18:18:34 +0200 Message-ID: <002801c30cd8$a74063b0$4809a8c0@raven> From: Igor Zlatkovic To: , , Date: Sun, 27 Apr 2003 18:18:35 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [xslt] Windows binaries Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi there, as of version 2.5.7, libxml2 binary packages for Windows are distributed with thread-support enabled. This means that this version is not binary-compatible to the previous versions. When upgrading, please upgrade all packages you use which depend on libxml2, means libxslt and xmlsec. Older libxslt and libxmlsec will not work with threaded libxml2. If you have your own programs which are linked to the binary libxml* packages, you will have to recompile them. Please feed me back about how wise this is and about any problems. If it doesn't work for everybody, we'll switch back to threadless distribution. Ciao, Igor From veillard@redhat.com Sun Apr 27 13:49:39 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id BC3A21810B for ; Sun, 27 Apr 2003 13:49:39 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3RHndK28442 for xslt@gnome.org; Sun, 27 Apr 2003 13:49:39 -0400 Date: Sun, 27 Apr 2003 13:49:39 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] elem uninitialised? Message-ID: <20030427134939.D4073@redhat.com> References: <001101c30cc6$70687e20$4809a8c0@raven> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <001101c30cc6$70687e20$4809a8c0@raven>; from igor@zlatkovic.com on Sun, Apr 27, 2003 at 04:08:12PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Sun, Apr 27, 2003 at 04:08:12PM +0200, Igor Zlatkovic wrote: > Hi there, > > In the file variables.c, on the line 757, a variable 'elem' > is declared: > > xsltStackElemPtr elem; > > The next time this variable is referenced on the line 810, > with: > > xsltFreeStackElem(elem); > > Should this be executed, elem will contain garbage at the > point it is passed to xsltFreeStackElem, because it was > never initialised. That doesn't look right. Should I fix? Yup, thanks ! Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From stephane.bidoul@softwareag.com Sun Apr 27 15:59:10 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from server8a.software-ag.de (server8a.software-ag.de [193.26.193.47]) by mail.gnome.org (Postfix) with ESMTP id B5FCB181D8 for ; Sun, 27 Apr 2003 15:59:09 -0400 (EDT) Received: from cat by server8a.software-ag.de; (8.11.6/8.9.3) id h3RJx8013615; Sun, 27 Apr 2003 21:59:08 +0200 Message-ID: <003401c30cf7$7aca4e80$3fafbd9d@cat> From: =?iso-8859-1?Q?St=E9phane_Bidoul?= To: Date: Sun, 27 Apr 2003 21:59:14 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0031_01C30D08.3DF2D610" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: [xslt] stylesheet.errors Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: This is a multi-part message in MIME format. ------=_NextPart_000_0031_01C30D08.3DF2D610 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, I'd like to have two more accessors in the python bindings: stylesheet.error and stylesheet.warnings. It's the only way I found to find out if a stylesheet compilation succeeded. I attached a patch proposal. -sbi ------=_NextPart_000_0031_01C30D08.3DF2D610 Content-Type: application/octet-stream; name="pythonaccessors.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="pythonaccessors.patch" Index: libxslt-python-api.xml=0A= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A= RCS file: /cvs/gnome/libxslt/python/libxslt-python-api.xml,v=0A= retrieving revision 1.9=0A= diff -r1.9 libxslt-python-api.xml=0A= 174a175,184=0A= > =0A= > Get the errors field of a stylesheet=0A= > =0A= > =0A= > =0A= > =0A= > Get the warnings field of a stylesheet=0A= > =0A= > =0A= > =0A= ------=_NextPart_000_0031_01C30D08.3DF2D610-- From veillard@redhat.com Sun Apr 27 18:20:11 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id B25261819D for ; Sun, 27 Apr 2003 18:20:11 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3RMKBN01544 for xslt@gnome.org; Sun, 27 Apr 2003 18:20:11 -0400 Date: Sun, 27 Apr 2003 18:20:11 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] stylesheet.errors Message-ID: <20030427182011.G4073@redhat.com> References: <003401c30cf7$7aca4e80$3fafbd9d@cat> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <003401c30cf7$7aca4e80$3fafbd9d@cat>; from stephane.bidoul@softwareag.com on Sun, Apr 27, 2003 at 09:59:14PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Sun, Apr 27, 2003 at 09:59:14PM +0200, Stéphane Bidoul wrote: > Hi, > > I'd like to have two more accessors in the python bindings: > stylesheet.error and stylesheet.warnings. > It's the only way I found to find out > if a stylesheet compilation succeeded. Hum, if it fails you will get None. > I attached a patch proposal. I don't really understand you suggestion, if you want a abinary answer then (result == None) is the one. If you want to get the error/warning messages then this should not be a Get functions but Set functions. So can you explain a bit, I'm lost, Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From niklasmls@doriath.saers.com Sun Apr 27 20:04:02 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from doriath.saers.com (doriath.religion.no [193.156.192.198]) by mail.gnome.org (Postfix) with ESMTP id 3A4CB18203 for ; Sun, 27 Apr 2003 20:04:02 -0400 (EDT) Received: by doriath.saers.com (Postfix, from userid 1001) id 91C6B3EB3; Mon, 28 Apr 2003 02:04:01 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by doriath.saers.com (Postfix) with ESMTP id 797C83E95 for ; Mon, 28 Apr 2003 02:04:01 +0200 (CEST) Date: Mon, 28 Apr 2003 02:04:01 +0200 (CEST) From: Niklas Saers Mailinglistaccount To: xslt@gnome.org Message-ID: <20030428015719.V98835@doriath.saers.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [xslt] Problem Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Dear sirs, For the Docbook XML found in http://niklas.saers.com/thesis/xml.tar.gz I get the following errors when doing a xsltproc --catalogs custom.xsl oppgave.xml > index.html No template for "/book/chapter/section/para" (or any of its leaves) exists in the context named "title" in the "en" localization. No template for "/book/chapter/section/para" (or any of its leaves) exists in the context named "title" in the "en" localization. No template for "/book/chapter/section/para" (or any of its leaves) exists in the context named "title" in the "en" localization. I'm handing in my masters thesis in two days and all the sudden xsltproc has started giving me these warnings. I have no idea what it is referring to (I'm fairly certain I don't have a book, followed by a chapter, asection, a para element within a title element) so I'm asking for your help. I've just finished proofreading it and I'm worried that some text is not presented because of this error. I have run xsltproc with --verbose, but I cannot find out from it what the problems are. It's output is in http://niklas.saers.com/thesis/warn.gz Would you be so kind as to suggest what may be causing this? Sincerely yours Niklas Saers From jfleck@inkstain.net Sun Apr 27 21:34:39 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from taka.swcp.com (taka.swcp.com [198.59.115.12]) by mail.gnome.org (Postfix) with ESMTP id 9EB741819A for ; Sun, 27 Apr 2003 21:34:39 -0400 (EDT) Received: from [10.0.0.2] (216.184.14.36.unused.swcp.com [216.184.14.36]) by taka.swcp.com (8.12.9/8.12.9) with ESMTP id h3S1YaL3087024 for ; Sun, 27 Apr 2003 19:34:37 -0600 (MDT) Subject: Re: [xslt] Problem From: John Fleck To: xslt@gnome.org In-Reply-To: <20030428015719.V98835@doriath.saers.com> References: <20030428015719.V98835@doriath.saers.com> Content-Type: text/plain Organization: Message-Id: <1051493705.13545.19.camel@jelloiii> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 (1.2.0-3) Date: 27 Apr 2003 19:35:05 -0600 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-23.8 required=10.0 tests=DEAR_SOMETHING,EMAIL_ATTRIBUTION,IN_REP_TO, QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES version=2.53 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Niklas - Your document is not valid docbook. Have you tried to validate it using xmllint? For example, this is incorrect: ************* A descriptive project model for the FreeBSD Project ************ Should be: *********** A descriptive project model for the FreeBSD Project *********** As another example, "url" is the correct attribute for a ulink, not link. You have biblioentries that aren't in a bibliography. The list goes on. For xsltproc to do the transformation correctly, you have to have valid docbook. xmllint --noout --valid --noent oppgave.xml will show you the many docbook validity errors. Cheers, John On Sun, 2003-04-27 at 18:04, Niklas Saers Mailinglistaccount wrote: > Dear sirs, > > For the Docbook XML found in http://niklas.saers.com/thesis/xml.tar.gz I > get the following errors when doing a > xsltproc --catalogs custom.xsl oppgave.xml > index.html > > No template for "/book/chapter/section/para" (or any of its leaves) exists > in the context named "title" in the "en" localization. > No template for "/book/chapter/section/para" (or any of its leaves) exists > in the context named "title" in the "en" localization. > No template for "/book/chapter/section/para" (or any of its leaves) exists > in the context named "title" in the "en" localization. > > I'm handing in my masters thesis in two days and all the sudden xsltproc > has started giving me these warnings. I have no idea what it is referring > to (I'm fairly certain I don't have a book, followed by a chapter, > asection, a para element within a title element) so I'm asking for your > help. I've just finished proofreading it and I'm worried that some text is > not presented because of this error. > > I have run xsltproc with --verbose, but I cannot find out from it > what the problems are. It's output is in > http://niklas.saers.com/thesis/warn.gz > > Would you be so kind as to suggest what may be causing this? > > Sincerely yours > > Niklas Saers > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt -- John Fleck jfleck@inkstain.net (h) jfleck@abqjournal.com (w) http://www.inkstain.net http://www.abqjournal.com http://www.gnome.org/learn/users-guide/latest/ "Not only isn't reality real - it's an illusion created by unreal people to sell real people unnecesary cars." - Griffy From niklasmls@doriath.saers.com Mon Apr 28 03:32:53 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from doriath.saers.com (doriath.religion.no [193.156.192.198]) by mail.gnome.org (Postfix) with ESMTP id 3456F18449 for ; Mon, 28 Apr 2003 03:32:53 -0400 (EDT) Received: by doriath.saers.com (Postfix, from userid 1001) id 9E2CA3E8F; Mon, 28 Apr 2003 09:32:52 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by doriath.saers.com (Postfix) with ESMTP id 9803C3E3B for ; Mon, 28 Apr 2003 09:32:52 +0200 (CEST) Date: Mon, 28 Apr 2003 09:32:52 +0200 (CEST) From: Niklas Saers Mailinglistaccount To: xslt@gnome.org Subject: Re: [xslt] Problem In-Reply-To: <1051493705.13545.19.camel@jelloiii> Message-ID: <20030428092934.D3440@doriath.saers.com> References: <20030428015719.V98835@doriath.saers.com> <1051493705.13545.19.camel@jelloiii> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi John, > xmllint --noout --valid --noent oppgave.xml will show you the many > docbook validity errors. Thank you very much. I used xmllint, but not with any parameters. Cheers Nik From stephane.bidoul@softwareag.com Mon Apr 28 12:12:37 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from server8a.software-ag.de (server8a.software-ag.de [193.26.193.47]) by mail.gnome.org (Postfix) with ESMTP id AE42B1818D for ; Mon, 28 Apr 2003 12:12:36 -0400 (EDT) Received: from acsesbi by server8a.software-ag.de; (8.11.6/8.9.3) id h3SGCU022440; Mon, 28 Apr 2003 18:12:31 +0200 From: "Stéphane Bidoul" To: "'Daniel Veillard'" Cc: Subject: RE: [xslt] stylesheet.errors Date: Mon, 28 Apr 2003 18:13:14 +0200 Message-ID: <003301c30da1$1767f310$57261eac@acsesbi> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <20030427182011.G4073@redhat.com> Importance: Normal Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > > I'd like to have two more accessors in the python bindings: > > stylesheet.error and stylesheet.warnings. > > It's the only way I found to find out > > if a stylesheet compilation succeeded. > > Hum, if it fails you will get None. > > > I attached a patch proposal. > > I don't really understand you suggestion, if you want a abinary > answer then (result == None) is the one. If you want to get the > error/warning messages then this should not be a Get functions but > Set functions. So can you explain a bit, I'm lost, > Well, I tested first with a stylesheet containing some element and parseStylesheetDoc returned a stylesheet object that was not None. I later found out that the errors where actually warnings and that libxslt considered the stylesheet as correct. In the meantime, I looked at xsltproc.c and found out that it checked the errors field in addition to checking that xsltParseStylesheetDoc did not return null (around line 770), so I supposed I needed access to that field to detect compilation errors. Now if you tell me that it will always be None in case of errors, that's what I need. Btw, to get the error messages, I assume I need to use the global error handler, since there is no "compilation context", right? -sbi From veillard@redhat.com Mon Apr 28 13:22:32 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 75F6718120 for ; Mon, 28 Apr 2003 13:22:32 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3SHMRH15057; Mon, 28 Apr 2003 13:22:27 -0400 Date: Mon, 28 Apr 2003 13:22:27 -0400 From: Daniel Veillard To: =?iso-8859-1?Q?St=E9phane_Bidoul?= Cc: xslt@gnome.org Subject: Re: [xslt] stylesheet.errors Message-ID: <20030428132227.M4073@redhat.com> References: <20030427182011.G4073@redhat.com> <003301c30da1$1767f310$57261eac@acsesbi> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <003301c30da1$1767f310$57261eac@acsesbi>; from stephane.bidoul@softwareag.com on Mon, Apr 28, 2003 at 06:13:14PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Mon, Apr 28, 2003 at 06:13:14PM +0200, Stéphane Bidoul wrote: > Well, I tested first with a stylesheet containing some > element and parseStylesheetDoc returned > a stylesheet object that was not None. I later found out that > the errors where actually warnings and that libxslt > considered the stylesheet as correct. yup, > In the meantime, I looked at xsltproc.c and found out > that it checked the errors field in addition to checking > that xsltParseStylesheetDoc did not return null > (around line 770), so I supposed I needed access to > that field to detect compilation errors. Well, no, that should not be necessary > Now if you tell me that it will always be None in case > of errors, that's what I need. > > Btw, to get the error messages, I assume I need to use the > global error handler, since there is no "compilation > context", right? Well there is a compilation context but it's not exposed at the API level, and there is no way to attach a specific error handler ... Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From sacerdot@CS.UniBO.IT Tue Apr 29 13:04:08 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from poa.cs.unibo.it (poa.cs.unibo.it [130.136.10.113]) by mail.gnome.org (Postfix) with ESMTP id E4777184C7 for ; Tue, 29 Apr 2003 13:04:07 -0400 (EDT) Received: from le1.cs.unibo.it (backle.cs.unibo.it [130.136.10.110]) by poa.cs.unibo.it (Postfix) with ESMTP id 24CED35804 for ; Tue, 29 Apr 2003 19:04:07 +0200 (CEST) Received: from marcello.cs.unibo.it (marcello.cs.unibo.it [130.136.5.29]) by le1.cs.unibo.it (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id TAA19390 for ; Tue, 29 Apr 2003 19:04:08 +0200 Received: (from sacerdot@localhost) by marcello.cs.unibo.it (8.9.3/8.9.3/Debian 8.9.3-21) id TAA01601 for xslt@gnome.org; Tue, 29 Apr 2003 19:04:24 +0200 Date: Tue, 29 Apr 2003 19:04:24 +0200 From: Claudio Sacerdoti Coen To: xslt@gnome.org Message-ID: <20030429190424.D1389@cs.unibo.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: Debian GNU/Linux X-Organization: Department of computer science, University of Bologna, Eurpean Union Subject: [xslt] Setting xsl:output parameters on compiled stylesheets Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Dear libxslt users/developers, is there a safe way to change the xsl:output arguments of a compiled stylesheet? E.g: I would like to change the xsl:output/@method (i.e. the method field of the _xsltStylesheet structure defined in xsltInternals.h) Note 1: I need to be able to change all the xsl:output arguments and not only the method. Note 2: I would not like to have to change the fields of the internal data structures "by hand". Xalan, for example, provides a public method to do this that takes in input the name and value of the property to be changed. Thanks a lot in advance, C.S.C. -- ---------------------------------------------------------------- Real name: Claudio Sacerdoti Coen PhD Student in Computer Science at University of Bologna E-mail: sacerdot@cs.unibo.it http://www.cs.unibo.it/~sacerdot ---------------------------------------------------------------- From veillard@redhat.com Tue Apr 29 13:17:47 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id C76D6185E8 for ; Tue, 29 Apr 2003 13:17:46 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3THHkP31299 for xslt@gnome.org; Tue, 29 Apr 2003 13:17:46 -0400 Date: Tue, 29 Apr 2003 13:17:46 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Setting xsl:output parameters on compiled stylesheets Message-ID: <20030429131746.H27943@redhat.com> References: <20030429190424.D1389@cs.unibo.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030429190424.D1389@cs.unibo.it>; from sacerdot@cs.unibo.it on Tue, Apr 29, 2003 at 07:04:24PM +0200 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Tue, Apr 29, 2003 at 07:04:24PM +0200, Claudio Sacerdoti Coen wrote: > Dear libxslt users/developers, > > is there a safe way to change the xsl:output arguments of a compiled > stylesheet? E.g: I would like to change the xsl:output/@method > (i.e. the method field of the _xsltStylesheet structure defined in > xsltInternals.h) > > Note 1: I need to be able to change all the xsl:output arguments and > not only the method. > > Note 2: I would not like to have to change the fields of the internal > data structures "by hand". Xalan, for example, provides a public method > to do this that takes in input the name and value of the property to > be changed. You can edit the fields. But there are no functions to do this. Tweaking the stylesheet once compiled is not clean, by essence, you can access the result and tweak it, but there is no guaranteed way to make this. You will have to access the fields. Note also that there can be more than one xsl:output instance per stylesheet. Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From veillard@redhat.com Tue Apr 29 15:58:57 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 5EA24184D3 for ; Tue, 29 Apr 2003 15:58:57 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3TJwvY27459 for xslt@gnome.org; Tue, 29 Apr 2003 15:58:57 -0400 Date: Tue, 29 Apr 2003 15:58:57 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Setting xsl:output parameters on compiled stylesheets Message-ID: <20030429155856.I27943@redhat.com> References: <20030429190424.D1389@cs.unibo.it> <20030429131746.H27943@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030429131746.H27943@redhat.com>; from veillard@redhat.com on Tue, Apr 29, 2003 at 01:17:46PM -0400 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Tue, Apr 29, 2003 at 01:17:46PM -0400, Daniel Veillard wrote: > On Tue, Apr 29, 2003 at 07:04:24PM +0200, Claudio Sacerdoti Coen wrote: > > Dear libxslt users/developers, > > > > is there a safe way to change the xsl:output arguments of a compiled > > stylesheet? E.g: I would like to change the xsl:output/@method > > (i.e. the method field of the _xsltStylesheet structure defined in > > xsltInternals.h) > > > > Note 1: I need to be able to change all the xsl:output arguments and > > not only the method. > > > > Note 2: I would not like to have to change the fields of the internal > > data structures "by hand". Xalan, for example, provides a public method > > to do this that takes in input the name and value of the property to > > be changed. > > You can edit the fields. But there are no functions to do this. > Tweaking the stylesheet once compiled is not clean, by essence, > you can access the result and tweak it, but there is no guaranteed > way to make this. You will have to access the fields. Note also that > there can be more than one xsl:output instance per stylesheet. I have reread the specific section in the XSLT-1.0 spec. It seems that the attribute of the xsl:output element should not influence any of the compilation steps, so modifying those specific element should not generate incoherencies. There is no API for it but at least this sounds safe. If you have a good API to suggest, do so, Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From sacerdot@CS.UniBO.IT Wed Apr 30 05:41:26 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from poa.cs.unibo.it (poa.cs.unibo.it [130.136.10.113]) by mail.gnome.org (Postfix) with ESMTP id 66DB718252 for ; Wed, 30 Apr 2003 05:41:26 -0400 (EDT) Received: from le1.cs.unibo.it (backle.cs.unibo.it [130.136.10.110]) by poa.cs.unibo.it (Postfix) with ESMTP id 14A5635805 for ; Wed, 30 Apr 2003 11:41:25 +0200 (CEST) Received: from marcello.cs.unibo.it (marcello.cs.unibo.it [130.136.5.29]) by le1.cs.unibo.it (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id LAA16862 for ; Wed, 30 Apr 2003 11:41:26 +0200 Received: (from sacerdot@localhost) by marcello.cs.unibo.it (8.9.3/8.9.3/Debian 8.9.3-21) id LAA03242 for xslt@gnome.org; Wed, 30 Apr 2003 11:41:15 +0200 Date: Wed, 30 Apr 2003 11:41:15 +0200 From: Claudio Sacerdoti Coen To: xslt@gnome.org Subject: Re: [xslt] Setting xsl:output parameters on compiled stylesheets Message-ID: <20030430114115.A3200@cs.unibo.it> References: <20030429190424.D1389@cs.unibo.it> <20030429131746.H27943@redhat.com> <20030429155856.I27943@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030429155856.I27943@redhat.com>; from veillard@redhat.com on Tue, Apr 29, 2003 at 03:58:57PM -0400 X-Operating-System: Debian GNU/Linux X-Organization: Department of computer science, University of Bologna, Eurpean Union Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > I have reread the specific section in the XSLT-1.0 spec. It seems > that the attribute of the xsl:output element should not influence > any of the compilation steps, Good news. > so modifying those specific element > should not generate incoherencies. There is no API for it but at least > this sounds safe. If you have a good API to suggest, do so, I have only a couple of APIs in mind: 1. just provide a couple of ``high-level'' functions: // returns the value of a given property; returns NULL if the // property argument is not the name of a property xmlChar * xsltGetProperty(xsltStylesheetPtr style, xmlChar *property) // set the value of a given property; returns the old value; // returns NULL if the property argument is not the name of a property xmlChar * xsltSetProperty(xsltStylesheetPtr style, xmlChar *property, xmlChar *value) Open issue: when a property is not setted, what is the value that should be returned by xsltGetProperty? Two possibilities: A. the empty string B. the libxslt/XSLT default value (but for the "method" property the default value is not fixed, but it is dependent from the output) - Pros: the API will not change when more properties will be added to - Pros: user-friendly - Cons: "complex" implementation - Cons: if in the future XSLT will have a new property which interferes with the compilation phase, we will be obliged to return NULL - Cons: dynamic errors can occur 2. provide a couple of get-set methods for every settable property XXX xmlChar * xsltGetPropertyXXXX(xsltStylesheetPtr style) xmlChar * xsltSetPropertyXXXX(xsltStylesheetPtr style, xmlChar *value) The open issue of 1. is open even in this case. - Pros: easy implementation - Pros: no dynamic errors (NULL is never returned) - Cons: much less user-friendly - Cons: the API must be extended every time a new property is add to XSLT Regards, C.S.C. -- ---------------------------------------------------------------- Real name: Claudio Sacerdoti Coen PhD Student in Computer Science at University of Bologna E-mail: sacerdot@cs.unibo.it http://www.cs.unibo.it/~sacerdot ---------------------------------------------------------------- From veillard@redhat.com Wed Apr 30 16:44:08 2003 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 0E099181A7 for ; Wed, 30 Apr 2003 16:44:08 -0400 (EDT) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id h3UKi7409892 for xslt@gnome.org; Wed, 30 Apr 2003 16:44:07 -0400 Date: Wed, 30 Apr 2003 16:44:07 -0400 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] str:tokenize behavior Message-ID: <20030430164407.X27943@redhat.com> References: <09B3671D58690A4193A7F8F15F416B23111B2C@denmails3.jdedwards.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <09B3671D58690A4193A7F8F15F416B23111B2C@denmails3.jdedwards.com>; from Mark_Vakoc@jdedwards.com on Thu, Apr 24, 2003 at 11:09:31AM -0600 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Apr 24, 2003 at 11:09:31AM -0600, Vakoc, Mark wrote: > > Hum, there is 2 options: > > - either this must behave like a node set, an in this case the > > nodeset should contain the list of nodes not, the > > parent document > > element Okay I finally addressed this in what I think is the correct way. 1/ this is expected to be a node set, so it should allocated as such 2/ the problem of freeing the tree is independant and addressed by allocating and freeing it with new APIs Basically it becomes: ------------------------ ... we need a pointer to the transformation context now ... xsltTransformContextPtr tctxt; ... tctxt = xsltXPathGetTransformContext(ctxt); if (tctxt == NULL) { xsltTransformError(xsltXPathGetTransformContext(ctxt), NULL, NULL, "exslt:tokenize : internal error tctxt == NULL\n"); goto fail; } container = xsltCreateRVT(tctxt); if (container != NULL) { xsltRegisterTmpRVT(tctxt, container); ret = xmlXPathNewNodeSet(NULL); if (ret != NULL) { ret->boolval = 0; /* Freeing is not handled there anymore */ .... and within the loop ..... xmlXPathNodeSetAddUnique(ret->nodesetval, node); ------------------------ The XSLT processor exports new APIs to create a result value tree and register it in the transformation context. When getting out of scope old RVT are freed automatically by the XSLT processor. This should clean things up a lot and finally give a good fondation for handling result value trees and functions creating temporary trees. I commited this to CVS, and added your test case to the exslt regression tests. I will be out of IP connectivity till Sunday, and I will try to make a release then. In the meantime could you check it out and verify that this code allows to rewrite your extensions functions in a clean (and possibly simpler) way ? thanks Daniel -- Daniel Veillard | Red Hat Network https://rhn.redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/