From jim.crafton@verizon.net  Sun Oct  5 13:56:06 2003
Return-Path: <jim.crafton@verizon.net>
Delivered-To: xslt@gnome.org
Received: from out012.verizon.net (out012pub.verizon.net [206.46.170.137])
	by mail.gnome.org (Postfix) with ESMTP id D176218160
	for <xslt@gnome.org>; Sun,  5 Oct 2003 13:56:05 -0400 (EDT)
Received: from verizon.net ([162.84.228.99]) by out012.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20031005175619.SFSV20366.out012.verizon.net@verizon.net>
          for <xslt@gnome.org>; Sun, 5 Oct 2003 12:56:19 -0500
Message-ID: <3F805EC3.6040102@verizon.net>
Date: Sun, 05 Oct 2003 14:11:15 -0400
From: Jim Crafton <jim.crafton@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: xslt@gnome.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out012.verizon.net from [162.84.228.99] at Sun, 5 Oct 2003 12:56:18 -0500
Subject: [xslt] xsltproc docbook and user.header.navigation handling
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

I have a bunch of docbook files, plus a custom xsl stylesheet, and a 
makefile that is used to build the whole thing. In the xsl sheet i 
override the
<xsl:template name="user.header.navigation"> template. In this I have 
some header html wrapped in a CDATA tag. This all used to output 
flawlessly until I upgraded my cygwin install (which I beleive also 
upgraded xsltproc). Now the output has all the "<" characters 
transformed to "&lt;" and so on. Looking on google and this mailing list 
it appears that this is a feature that was added per the xml spec. If 
so, how can I get the output to resemble html again with the "<" 
characters intact?

This is a fragment of what I have in the stylsheet that used to work:
<xsl:template name="user.header.navigation">   
    <![CDATA[   
<table width="100%" border="0" cellpadding="0" cellspacing="0">
 <tr>
  <td class="logoCell" width="400" height="80" valign="top">
   <table width="400" border="0" cellpadding="0" cellspacing="0">
    <tr>
......rest clipped
]]>
</xsl:template>

I used to get output like:

<table width="100%" border="0" cellpadding="0" cellspacing="0">
 <tr>
  <td class="logoCell" width="400" height="80" valign="top">
   <table width="400" border="0" cellpadding="0" cellspacing="0">
    <tr>
and so on.

Now I get :

&lt;table width=&quot;100%&quot; border=&quot;0&quot; cellpadding=&quot;0&quot; cellspacing=&quot;0&quot;&gt;
 &lt;tr&gt;

  &lt;td class=&quot;logoCell&quot; width=&quot;400&quot; height=&quot;80&quot; valign=&quot;top&quot;&gt;
   &lt;table width=&quot;400&quot; border=&quot;0&quot; cellpadding=&quot;0&quot; cellspacing=&quot;0&quot;&gt;

    &lt;tr&gt;

I didn't see (or understand, perhaps) how to solve this, apologies if this has been answered before.

Cheers

Jim








From shaunm@gnome.org  Sun Oct  5 16:23:54 2003
Return-Path: <shaunm@gnome.org>
Delivered-To: xslt@gnome.org
Received: from router.housenet.net (adsl-68-22-248-73.dsl.chmpil.ameritech.net [68.22.248.73])
	by mail.gnome.org (Postfix) with ESMTP id 1E91718138
	for <xslt@gnome.org>; Sun,  5 Oct 2003 16:23:54 -0400 (EDT)
Received: from cornholio.housenet.net (cornholio.housenet.net [10.0.0.240])
	by router.housenet.net (8.11.6/8.11.6) with ESMTP id h95JdmZ10888
	for <xslt@gnome.org>; Sun, 5 Oct 2003 14:39:49 -0500
Subject: Re: [xslt] xsltproc docbook and user.header.navigation handling
From: Shaun McCance <shaunm@gnome.org>
To: xslt@gnome.org
In-Reply-To: <3F805EC3.6040102@verizon.net>
References: <3F805EC3.6040102@verizon.net>
Content-Type: text/plain
Message-Id: <1065385447.11449.10.camel@cornholio.housenet.net>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4 
Date: Sun, 05 Oct 2003 15:24:07 -0500
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Sun, 2003-10-05 at 13:11, Jim Crafton wrote:
> I have a bunch of docbook files, plus a custom xsl stylesheet, and a 
> makefile that is used to build the whole thing. In the xsl sheet i 
> override the
> <xsl:template name="user.header.navigation"> template. In this I have 
> some header html wrapped in a CDATA tag. This all used to output 
> flawlessly until I upgraded my cygwin install (which I beleive also 
> upgraded xsltproc). Now the output has all the "<" characters 
> transformed to "&lt;" and so on. Looking on google and this mailing list 
> it appears that this is a feature that was added per the xml spec. If 
> so, how can I get the output to resemble html again with the "<" 
> characters intact?
> 
> This is a fragment of what I have in the stylsheet that used to work:
> <xsl:template name="user.header.navigation">   
>     <![CDATA[   
> <table width="100%" border="0" cellpadding="0" cellspacing="0">
>  <tr>
>   <td class="logoCell" width="400" height="80" valign="top">
>    <table width="400" border="0" cellpadding="0" cellspacing="0">
>     <tr>
> ......rest clipped
> ]]>
> </xsl:template>
> 
> I used to get output like:
> 
> <table width="100%" border="0" cellpadding="0" cellspacing="0">
>  <tr>
>   <td class="logoCell" width="400" height="80" valign="top">
>    <table width="400" border="0" cellpadding="0" cellspacing="0">
>     <tr>
> and so on.
> 
> Now I get :
> 
> &lt;table width=&quot;100%&quot; border=&quot;0&quot; cellpadding=&quot;0&quot;
> cellspacing=&quot;0&quot;&gt;
>  &lt;tr&gt;
> 
>   &lt;td class=&quot;logoCell&quot; width=&quot;400&quot; height=&quot;80&quot;
> valign=&quot;top&quot;&gt;
>    &lt;table width=&quot;400&quot; border=&quot;0&quot; cellpadding=&quot;0&quot;
> cellspacing=&quot;0&quot;&gt;
> 
>     &lt;tr&gt;
> 
> I didn't see (or understand, perhaps) how to solve this, apologies if this has
> been answered before.

I don't know why this ever worked, but it's wrong.  You can't put XML in
a CDATA and expect to to get actual XML output.  A CDATA is logically
equivalent to normal text.  It's just a way for humans to avoid having
to escape lots of characters.

What you want is to disable output escaping on a text node.  You can use
the disable-output-escaping attributes on xsl:text for this.  So:

<xsl:text disable-output-escaping="yes">
<![CDATA[<table>]>
</xsl:text>

And now I have to tell you never to use disable-output-escaping.  It's a
horrible hack, and it's very fragile.  I presume that you're intending
to have some unbalanced tags in user.header.navigation, and that you're
balancing them out in user.footer.navigation.  The clean and correct way
of handling this is to override chunk-element-content (assuming this is
Norm's XSLT).

--
Shaun




From jim.crafton@verizon.net  Sun Oct  5 19:08:04 2003
Return-Path: <jim.crafton@verizon.net>
Delivered-To: xslt@gnome.org
Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143])
	by mail.gnome.org (Postfix) with ESMTP id 2D8F718109
	for <xslt@gnome.org>; Sun,  5 Oct 2003 19:08:04 -0400 (EDT)
Received: from verizon.net ([162.84.228.99]) by out005.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20031005230817.CXLE15786.out005.verizon.net@verizon.net>
          for <xslt@gnome.org>; Sun, 5 Oct 2003 18:08:17 -0500
Message-ID: <3F80A7E5.3050307@verizon.net>
Date: Sun, 05 Oct 2003 19:23:17 -0400
From: Jim Crafton <jim.crafton@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: xslt@gnome.org
Subject: Re: [xslt] xsltproc docbook and user.header.navigation handling
References: <3F805EC3.6040102@verizon.net> <1065385447.11449.10.camel@cornholio.housenet.net>
In-Reply-To: <1065385447.11449.10.camel@cornholio.housenet.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [162.84.228.99] at Sun, 5 Oct 2003 18:08:17 -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
List-Help: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Shaun,
Thanks for the quick reply!

>I don't know why this ever worked, but it's wrong.  
>
I tried changing to an earlier version of libxml/libxslt ("Using libxml 
20410, libxslt 10009 and libexslt 702")
and it worked .

>What you want is to disable output escaping on a text node.  You can use
>the disable-output-escaping attributes on xsl:text for this.  So:
>
><xsl:text disable-output-escaping="yes">
><![CDATA[<table>]>
></xsl:text>
>
>  
>
Actually I tried this. And *still* got the "wrong" output. What I got was
&lt;table&gt;

>And now I have to tell you never to use disable-output-escaping.  It's a
>horrible hack, and it's very fragile.  I presume that you're intending
>to have some unbalanced tags in user.header.navigation, and that you're
>balancing them out in user.footer.navigation. 
>
Yes, exactly

> The clean and correct way
>of handling this is to override chunk-element-content (assuming this is
>Norm's XSLT).
>  
>
I am using norms xsl sheets ( docbook-xsl-1.60.1 ). Do you have a brief 
example of how I would accomplish this using the technique you 
described? Thanks a bunch!

Cheers

Jim


From pike@kw.nl  Mon Oct  6 03:34:53 2003
Return-Path: <pike@kw.nl>
Delivered-To: xslt@gnome.org
Received: from pluto.isd-holland.nl (pluto.isd-holland.nl [213.227.130.157])
	by mail.gnome.org (Postfix) with ESMTP id 35FF018285
	for <xslt@gnome.org>; Mon,  6 Oct 2003 03:34:53 -0400 (EDT)
Received: from kw.nl (unknown [213.132.214.175])
	by pluto.isd-holland.nl (Postfix) with ESMTP id A833967006
	for <xslt@gnome.org>; Mon,  6 Oct 2003 09:31:32 +0200 (CEST)
Date: Mon, 6 Oct 2003 09:35:04 +0200
Subject: Re: [xslt] xsltproc docbook and user.header.navigation handling
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Pike <pike@kw.nl>
To: xslt@gnome.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <3F805EC3.6040102@verizon.net>
Message-Id: <9A442389-F7CF-11D7-BDF9-000393633FDA@kw.nl>
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi

> This is a fragment of what I have in the stylsheet that used to work:
> <xsl:template name="user.header.navigation">      <![CDATA[   <table 
> width="100%" border="0" cellpadding="0" cellspacing="0">
> <tr>
>  <td class="logoCell" width="400" height="80" valign="top">
>   <table width="400" border="0" cellpadding="0" cellspacing="0">
>    <tr>
> ......rest clipped
> ]]>
> </xsl:template>

keep it simple:

<xsl:template name="user.header.navigation">
	<table width="100%" border="0" cellpadding="0" cellspacing="0">
		<tr>
			<td class="logoCell" width="400" height="80" valign="top">
  				<table width="400" border="0" cellpadding="0" cellspacing="0">
    					<tr>
			......rest clipped
</xsl:template>

make sure to use valid xhtml (that is, your html should be valid xml,
hence write <br/> instead of <br> etc)

Shaun is right, your stylesheet _should_ never have worked the
way it was, that is , it should output escaped entities like &lt;

gluck,
*-pike
==========
Signature #1
==========


From shaunm@gnome.org  Mon Oct  6 15:36:37 2003
Return-Path: <shaunm@gnome.org>
Delivered-To: xslt@gnome.org
Received: from router.housenet.net (adsl-68-22-248-73.dsl.chmpil.ameritech.net [68.22.248.73])
	by mail.gnome.org (Postfix) with ESMTP id C6E8918249
	for <xslt@gnome.org>; Mon,  6 Oct 2003 15:36:36 -0400 (EDT)
Received: from cornholio.housenet.net (cornholio.housenet.net [10.0.0.240])
	by router.housenet.net (8.11.6/8.11.6) with ESMTP id h96IqdZ17866;
	Mon, 6 Oct 2003 13:52:39 -0500
Subject: Re: [xslt] xsltproc docbook and user.header.navigation handling
From: Shaun McCance <shaunm@gnome.org>
To: xslt@gnome.org
Cc: Jim Crafton <jim.crafton@verizon.net>
In-Reply-To: <3F80A7E5.3050307@verizon.net>
References: <3F805EC3.6040102@verizon.net>
	 <1065385447.11449.10.camel@cornholio.housenet.net>
	 <3F80A7E5.3050307@verizon.net>
Content-Type: text/plain
Message-Id: <1065469009.30598.5.camel@cornholio.housenet.net>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.4 
Date: Mon, 06 Oct 2003 14:36:50 -0500
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Sun, 2003-10-05 at 18:23, Jim Crafton wrote:
> Shaun,
> Thanks for the quick reply!
> 
> >I don't know why this ever worked, but it's wrong.  
> >
> I tried changing to an earlier version of libxml/libxslt ("Using libxml 
> 20410, libxslt 10009 and libexslt 702")
> and it worked .

OK.  That was a bug then.

> >What you want is to disable output escaping on a text node.  You can use
> >the disable-output-escaping attributes on xsl:text for this.  So:
> >
> ><xsl:text disable-output-escaping="yes">
> ><![CDATA[<table>]>
> ></xsl:text>
> >
> >  
> >
> Actually I tried this. And *still* got the "wrong" output. What I got was
> &lt;table&gt;

Right.  This is just horribly fragile.  There are all sorts of things
that could go on in the stylesheets that could cause this not to work. 
Generally speaking, disable-output-escaping is best avoided.  Also note
that an XSLT processor is not required to support it, so even if it did
work, there's no guarantee your XSLT will work elsewhere.

> >And now I have to tell you never to use disable-output-escaping.  It's a
> >horrible hack, and it's very fragile.  I presume that you're intending
> >to have some unbalanced tags in user.header.navigation, and that you're
> >balancing them out in user.footer.navigation. 
> >
> Yes, exactly
> 
> > The clean and correct way
> >of handling this is to override chunk-element-content (assuming this is
> >Norm's XSLT).
> >  
> >
> I am using norms xsl sheets ( docbook-xsl-1.60.1 ). Do you have a brief 
> example of how I would accomplish this using the technique you 
> described? Thanks a bunch!

Create a stylesheet that imports Norm's stylesheets with

<xsl:import
href="http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl"/>

Then look at chunk-common.xsl in Norm's stylesheets and copy the
template chunk-element-content.  Change it to your liking.

--
Shaun



From kbuchcik@4commerce.de  Tue Oct  7 07:42:16 2003
Return-Path: <kbuchcik@4commerce.de>
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 562B6189E7
	for <xslt@gnome.org>; Tue,  7 Oct 2003 07:42:16 -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 1A6qEX-0002yE-00
	for xslt@gnome.org; Tue, 07 Oct 2003 13:42:29 +0200
From: Kasimier Buchcik <kbuchcik@4commerce.de>
To: <xslt@gnome.org>
X-Priority: 3
Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Tue, 7 Oct 2003 13:36:54 +0200
Received: from 4commerce.de (10.1.72.2 [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 4BSL5PTL; Tue, 7 Oct 2003 13:36:54 +0200
Message-ID: <3F82A5CC.5010404@4commerce.de>
Date: Tue, 07 Oct 2003 13:38:52 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
References: <3F66EDCB.7040503@4commerce.de> <20030916083255.G26189@redhat.com> <3F6716CD.4060106@4commerce.de> <20030916095808.I26189@redhat.com> <3F68539F.1090401@4commerce.de> <20030917090528.F26189@redhat.com> <3F687690.9030506@4commerce.de> <20030917105851.G26189@redhat.com> <3F687F5C.5080300@4commerce.de>
In-Reply-To: <3F687F5C.5080300@4commerce.de>
X-eMessageService: eMission.SMTPServer
Subject: "Re: [xslt] Apply stylesheet to a subbranch of a document"
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi Daniel,

> Daniel Veillard wrote:
>=20
>=20
>>  Well try the function modification, we will put a big warning in the API
>>description

This mail refers to this initial mail:
   http://mail.gnome.org/archives/xslt/2003-September/msg00019.html

We modified xsltApplyStylesheetInternal to provide the ability to apply=20
a stylesheet to a subbranch of a document. It worked well by simply=20
changing the initial context node. But we ended up wondering why the=20
heck we should mess with the specs. Originally I was influenced by the=20
behaviour of the m$xml 4 parser on that issue. IOW: keep it as it is; we=20
will find an other way.
Anyway, thanks for the discussion!

By the way: serializing documents took long time if using functions like=20
xmlDocDumpFormatMemoryEnc, until we discovered that serializing directly=20
to file was way faster (by the factor of 50 sometimes). I know that=20
there was a message about this issue already somewhere on the list; so=20
this is just a hint for those who transform huge documents and process=20
further with the resulting xml-text. We did a workaround by serializing=20
to file and then reloading the document.


Greetings,

Kasimier Buchcik


From veillard@redhat.com  Tue Oct  7 07:54:25 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 34D771856A
	for <xslt@gnome.org>; Tue,  7 Oct 2003 07:54:25 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h97BsdF28143
	for xslt@gnome.org; Tue, 7 Oct 2003 07:54:39 -0400
Date: Tue, 7 Oct 2003 07:54:38 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: "Re: [xslt] Apply stylesheet to a subbranch of a document"
Message-ID: <20031007075438.E31459@redhat.com>
References: <3F66EDCB.7040503@4commerce.de> <20030916083255.G26189@redhat.com> <3F6716CD.4060106@4commerce.de> <20030916095808.I26189@redhat.com> <3F68539F.1090401@4commerce.de> <20030917090528.F26189@redhat.com> <3F687690.9030506@4commerce.de> <20030917105851.G26189@redhat.com> <3F687F5C.5080300@4commerce.de> <3F82A5CC.5010404@4commerce.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3F82A5CC.5010404@4commerce.de>; from kbuchcik@4commerce.de on Tue, Oct 07, 2003 at 01:38: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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Tue, Oct 07, 2003 at 01:38:52PM +0200, Kasimier Buchcik wrote:
> Hi Daniel,
> 
> > Daniel Veillard wrote:
> > 
> > 
> >>  Well try the function modification, we will put a big warning in the API
> >>description
> 
> This mail refers to this initial mail:
>    http://mail.gnome.org/archives/xslt/2003-September/msg00019.html
> 
> We modified xsltApplyStylesheetInternal to provide the ability to apply 
> a stylesheet to a subbranch of a document. It worked well by simply 
> changing the initial context node. But we ended up wondering why the 
> heck we should mess with the specs. Originally I was influenced by the 
> behaviour of the m$xml 4 parser on that issue. IOW: keep it as it is; we 
> will find an other way.

  Hum, okay. I wonder a bit what made you change your mind,
but that's fine :-)

> Anyway, thanks for the discussion!

  no problem.

> By the way: serializing documents took long time if using functions like 
> xmlDocDumpFormatMemoryEnc, until we discovered that serializing directly 
> to file was way faster (by the factor of 50 sometimes). I know that 
> there was a message about this issue already somewhere on the list; so 
> this is just a hint for those who transform huge documents and process 
> further with the resulting xml-text. We did a workaround by serializing 
> to file and then reloading the document.

  Hum, wasn't that fixed in the last versions ? If not open a bug in bugzilla
so it get checked and fixed if it's not already. 

  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 kbuchcik@4commerce.de  Tue Oct  7 09:06:46 2003
Return-Path: <kbuchcik@4commerce.de>
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 629A518A9B
	for <xslt@gnome.org>; Tue,  7 Oct 2003 09:06:46 -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 1A6rYJ-0005rR-00
	for xslt@gnome.org; Tue, 07 Oct 2003 15:06:59 +0200
From: Kasimier Buchcik <kbuchcik@4commerce.de>
To: <xslt@gnome.org>
X-Priority: 3
Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Tue, 7 Oct 2003 15:01:41 +0200
Received: from 4commerce.de (10.1.72.2 [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 4BSL5PTY; Tue, 7 Oct 2003 15:01:41 +0200
Message-ID: <3F82B9B5.5070101@4commerce.de>
Date: Tue, 07 Oct 2003 15:03:49 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
References: <3F66EDCB.7040503@4commerce.de> <20030916083255.G26189@redhat.com> <3F6716CD.4060106@4commerce.de> <20030916095808.I26189@redhat.com> <3F68539F.1090401@4commerce.de> <20030917090528.F26189@redhat.com> <3F687690.9030506@4commerce.de> <20030917105851.G26189@redhat.com> <3F687F5C.5080300@4commerce.de> <3F82A5CC.5010404@4commerce.de> <20031007075438.E31459@redhat.com>
In-Reply-To: <20031007075438.E31459@redhat.com>
X-eMessageService: eMission.SMTPServer
Subject: "Re: [xslt] Apply stylesheet to a subbranch of a document"
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Daniel Veillard wrote:

> On Tue, Oct 07, 2003 at 01:38:52PM +0200, Kasimier Buchcik wrote:

>>>Daniel Veillard wrote:

>>>> Well try the function modification, we will put a big warning in the AP=
I
>>>>description
>>
>>This mail refers to this initial mail:
>>   http://mail.gnome.org/archives/xslt/2003-September/msg00019.html
>>
>>We modified xsltApplyStylesheetInternal to provide the ability to apply=20
>>a stylesheet to a subbranch of a document. It worked well by simply=20
>>changing the initial context node. But we ended up wondering why the=20
>>heck we should mess with the specs. Originally I was influenced by the=20
>>behaviour of the m$xml 4 parser on that issue. IOW: keep it as it is; we=20
>>will find an other way.
>=20
>   Hum, okay. I wonder a bit what made you change your mind,
> but that's fine :-)

Let's say some people that I get my money from did not want to take the=20
risk to use functionallity that is not in the specs and thus might be=20
not available in other parsers. Well, they convinced my at last.

>>Anyway, thanks for the discussion!
>=20
>   no problem.
>=20
>>By the way: serializing documents took long time if using functions like=20
>>xmlDocDumpFormatMemoryEnc, until we discovered that serializing directly=20
>>to file was way faster (by the factor of 50 sometimes). I know that=20
>>there was a message about this issue already somewhere on the list; so=20
>>this is just a hint for those who transform huge documents and process=20
>>further with the resulting xml-text. We did a workaround by serializing=20
>>to file and then reloading the document.


Actually it's not a libxslt but a libxml2 issue, so you want to move it=20
there.

Using libxml2 2.5.10 (Igor's win binaries) I get the following times for=20
  the serialization of a 7.7 MB xml-file:

xmlSaveFormatFileEnc      : 2.1 s
xmlDocDumpFormatMemoryEnc : 77.2 s

 > Hum, wasn't that fixed in the last versions ? If not open a bug in=20
bugzilla
 > so it get checked and fixed if it's not already.

I don't know if you still confirm that this is an unexpected behaviour.=20
Should I still report it to bugzilla?

Thanks,

Kasimier Buchcik


From veillard@redhat.com  Tue Oct  7 09:47:40 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 027C8184AC
	for <xslt@gnome.org>; Tue,  7 Oct 2003 09:47:40 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h97Dlro08408
	for xslt@gnome.org; Tue, 7 Oct 2003 09:47:53 -0400
Date: Tue, 7 Oct 2003 09:47:53 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: "Re: [xslt] Apply stylesheet to a subbranch of a document"
Message-ID: <20031007094753.F31459@redhat.com>
References: <3F6716CD.4060106@4commerce.de> <20030916095808.I26189@redhat.com> <3F68539F.1090401@4commerce.de> <20030917090528.F26189@redhat.com> <3F687690.9030506@4commerce.de> <20030917105851.G26189@redhat.com> <3F687F5C.5080300@4commerce.de> <3F82A5CC.5010404@4commerce.de> <20031007075438.E31459@redhat.com> <3F82B9B5.5070101@4commerce.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3F82B9B5.5070101@4commerce.de>; from kbuchcik@4commerce.de on Tue, Oct 07, 2003 at 03:03: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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Tue, Oct 07, 2003 at 03:03:49PM +0200, Kasimier Buchcik wrote:
> Let's say some people that I get my money from did not want to take the 
> risk to use functionallity that is not in the specs and thus might be 
> not available in other parsers. Well, they convinced my at last.

  Sounds wise to me :-)

> >>By the way: serializing documents took long time if using functions like 
> >>xmlDocDumpFormatMemoryEnc, until we discovered that serializing directly 
> >>to file was way faster (by the factor of 50 sometimes). I know that 
> >>there was a message about this issue already somewhere on the list; so 
> >>this is just a hint for those who transform huge documents and process 
> >>further with the resulting xml-text. We did a workaround by serializing 
> >>to file and then reloading the document.
> 
> 
> Actually it's not a libxslt but a libxml2 issue, so you want to move it 
> there.
> 
> Using libxml2 2.5.10 (Igor's win binaries) I get the following times for 
>   the serialization of a 7.7 MB xml-file:
> 
> xmlSaveFormatFileEnc      : 2.1 s
> xmlDocDumpFormatMemoryEnc : 77.2 s

  Urgh, yes I have seens some problems like that before, and fixed a couple
durring the summer.

> I don't know if you still confirm that this is an unexpected behaviour. 

  Well that's definitely unexpected. The question is if it can be replicated
in CVS.

> Should I still report it to bugzilla?

  yes please !

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  Tue Oct  7 09:56:46 2003
Return-Path: <kbuchcik@4commerce.de>
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 467521847D
	for <xslt@gnome.org>; Tue,  7 Oct 2003 09:56:46 -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 1A6sKh-0007Z9-00
	for xslt@gnome.org; Tue, 07 Oct 2003 15:56:59 +0200
From: Kasimier Buchcik <kbuchcik@4commerce.de>
To: <xslt@gnome.org>
X-Priority: 3
Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Tue, 7 Oct 2003 15:53:42 +0200
Received: from 4commerce.de (10.1.72.2 [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 4BSL5P42; Tue, 7 Oct 2003 15:53:41 +0200
Message-ID: <3F82C5E7.2010801@4commerce.de>
Date: Tue, 07 Oct 2003 15:55:51 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
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] hook a callback into the transformation process
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi,

I hope someone has a suggestion for the following problem:
consider libxslt has to perform a time intensive transformation, during=20
which a database connection might get lost; is it possible to hook into=20
the transformation process (via a callback) to be able to periodically=20
check the database connection and abort the transformation if needed?
I know that we could use two threads, one to observe the db-connection=20
the other to run the transformation, but I'm interested in a solution=20
with less overhead. When would it be wise to fire such a callback (e.g.=20
every called template, every for-each, ect.) ?
Any hints?

Thanks,

Kasimier Buchcik


From veillard@redhat.com  Tue Oct  7 10:03:53 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 518B918B13
	for <xslt@gnome.org>; Tue,  7 Oct 2003 10:03:53 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h97E47P16709
	for xslt@gnome.org; Tue, 7 Oct 2003 10:04:07 -0400
Date: Tue, 7 Oct 2003 10:04:07 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: [xslt] hook a callback into the transformation process
Message-ID: <20031007100407.G31459@redhat.com>
References: <3F82C5E7.2010801@4commerce.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3F82C5E7.2010801@4commerce.de>; from kbuchcik@4commerce.de on Tue, Oct 07, 2003 at 03:55: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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Tue, Oct 07, 2003 at 03:55:51PM +0200, Kasimier Buchcik wrote:
> Hi,
> 
> I hope someone has a suggestion for the following problem:
> consider libxslt has to perform a time intensive transformation, during 
> which a database connection might get lost; is it possible to hook into 
> the transformation process (via a callback) to be able to periodically 
> check the database connection and abort the transformation if needed?
> I know that we could use two threads, one to observe the db-connection 
> the other to run the transformation, but I'm interested in a solution 
> with less overhead. When would it be wise to fire such a callback (e.g. 
> every called template, every for-each, ect.) ?
> Any hints?

  You can try to use the debugger callback see xsltSetDebuggerCallbacks()
in xsltutils.[ch]

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  Wed Oct  8 05:01:50 2003
Return-Path: <kbuchcik@4commerce.de>
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 57EF118280
	for <xslt@gnome.org>; Wed,  8 Oct 2003 05:01:50 -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 1A7ACp-0005cb-00
	for xslt@gnome.org; Wed, 08 Oct 2003 11:02:03 +0200
From: Kasimier Buchcik <kbuchcik@4commerce.de>
To: <xslt@gnome.org>
X-Priority: 3
Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Wed, 8 Oct 2003 10:59:05 +0200
Received: from 4commerce.de (10.1.72.2 [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 4BSL5PX4; Wed, 8 Oct 2003 10:59:05 +0200
Message-ID: <3F83D250.7070208@4commerce.de>
Date: Wed, 08 Oct 2003 11:01:04 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
References: <3F82C5E7.2010801@4commerce.de> <20031007100407.G31459@redhat.com>
In-Reply-To: <20031007100407.G31459@redhat.com>
X-eMessageService: eMission.SMTPServer
Subject: "Re: [xslt] hook a callback into the transformation process"
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Daniel Veillard wrote:
> On Tue, Oct 07, 2003 at 03:55:51PM +0200, Kasimier Buchcik wrote:
>>I hope someone has a suggestion for the following problem:
>>consider libxslt has to perform a time intensive transformation, during=20
>>which a database connection might get lost; is it possible to hook into=20
>>the transformation process (via a callback) to be able to periodically=20
>>check the database connection and abort the transformation if needed?
>>I know that we could use two threads, one to observe the db-connection=20
>>the other to run the transformation, but I'm interested in a solution=20
>>with less overhead. When would it be wise to fire such a callback (e.g.=20
>>every called template, every for-each, ect.) ?
>>Any hints?
>=20
>=20
>   You can try to use the debugger callback see xsltSetDebuggerCallbacks()
> in xsltutils.[ch]
>=20

Thanks, I will try that one.

Greetings,

Kasimier Buchcik


From kbuchcik@4commerce.de  Tue Oct 14 07:42:40 2003
Return-Path: <kbuchcik@4commerce.de>
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 5DDF818163
	for <xslt@gnome.org>; Tue, 14 Oct 2003 07:42:40 -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 1A9NZm-0000aA-00
	for xslt@gnome.org; Tue, 14 Oct 2003 13:42:54 +0200
From: Kasimier Buchcik <kbuchcik@4commerce.de>
To: <xslt@gnome.org>
X-Priority: 3
Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Tue, 14 Oct 2003 13:37:55 +0200
Received: from 4commerce.de (10.1.72.2 [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 47243F2V; Tue, 14 Oct 2003 13:37:54 +0200
Message-ID: <3F8BE0C4.4010303@4commerce.de>
Date: Tue, 14 Oct 2003 13:40:52 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
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] debugger callbacks
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi,

I tried to use xsltSetDebuggerCallbacks to get some callbacks during the=20
transformation, but the registered functions are not called. Since a=20
call of xslAddCall, fires the registered callback, I assume that=20
xsltDebuggerCurrentCallbacks is correctly initialized.
I guess libxslt (version see below) was compiled with WITH_DEBUGGER.

Any hint about what I could have done wrong here?

Used modules (Igor's win binaries):
libxml2 2.5.10
libxslt 1.0.32


Thanks,

Kasimier Buchcik


From troels@fast.no  Wed Oct 15 10:13:59 2003
Return-Path: <troels@fast.no>
Delivered-To: xslt@gnome.org
Received: from nimitz.osl.fast.no (mailoslo.fast.no [217.144.235.131])
	by mail.gnome.org (Postfix) with ESMTP id 2F7FF18284
	for <xslt@gnome.org>; Wed, 15 Oct 2003 10:13:59 -0400 (EDT)
Received: from TROELS (troels.tromso.fast.no [192.168.32.54])
	by nimitz.osl.fast.no (8.12.9/8.12.9) with ESMTP id h9FEEDNx017406
	for <xslt@gnome.org>; Wed, 15 Oct 2003 16:14:13 +0200 (MEST)
From: "Troels Walsted Hansen" <troels@fast.no>
To: <xslt@gnome.org>
Date: Wed, 15 Oct 2003 16:14:11 +0200
Organization: Fast Search & Transfer ASA
Message-ID: <003b01c39326$9c7d17f0$3620a8c0@TROELS>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_003C_01C39337.6005E7F0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Subject: [xslt] configure runs wrong python executable
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

This is a multi-part message in MIME format.

------=_NextPart_000_003C_01C39337.6005E7F0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I think the attached patch is correct and necessary to build libxslt
with a python executable with is not in the global PATH. Patch against
libxslt 1.0.33.

Please CC any replies, I am not subscribed to the list.

--=20
Troels Walsted Hansen, M.Sc.          Mail:  troels@fast.no
Senior Software Engineer              Web:   http://www.fast.no
Fast Search & Transfer ASA            Phone: +47 77 69 66 88
P.O. Box 621                          Fax:   +47 77 69 66 89
NO-9257 Troms=F8, NORWAY                Mob:   +47 48 01 11 04

------=_NextPart_000_003C_01C39337.6005E7F0
Content-Type: application/octet-stream;
	name="configure.in_pythonlocation.patch"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="configure.in_pythonlocation.patch"

--- configure.in.orig	Wed Oct 15 16:07:13 2003=0A=
+++ configure.in	Wed Oct 15 16:07:37 2003=0A=
@@ -171,7 +171,7 @@=0A=
     then=0A=
         PYTHON_VERSION=3D`$PYTHON -c "import sys; print =
sys.version[[0:3]]"`=0A=
 	echo Found Python version $PYTHON_VERSION=0A=
-	LIBXML2_PYTHON=3D`python -c "try : import libxml2 ; print 1=0A=
+	LIBXML2_PYTHON=3D`$PYTHON -c "try : import libxml2 ; print 1=0A=
 except: print 0"`=0A=
 	if test "$LIBXML2_PYTHON" =3D "1"=0A=
 	then=0A=

------=_NextPart_000_003C_01C39337.6005E7F0--


From veillard@redhat.com  Wed Oct 15 11:32:32 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 9D28F185F0
	for <xslt@gnome.org>; Wed, 15 Oct 2003 11:32:31 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9FFWYD03924;
	Wed, 15 Oct 2003 11:32:34 -0400
Date: Wed, 15 Oct 2003 11:32:34 -0400
From: Daniel Veillard <veillard@redhat.com>
To: troels@fast.no
Cc: xslt@gnome.org
Subject: Re: [xslt] configure runs wrong python executable
Message-ID: <20031015113234.K16905@redhat.com>
References: <003b01c39326$9c7d17f0$3620a8c0@TROELS>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <003b01c39326$9c7d17f0$3620a8c0@TROELS>; from troels@fast.no on Wed, Oct 15, 2003 at 04:14:11PM +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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wed, Oct 15, 2003 at 04:14:11PM +0200, Troels Walsted Hansen wrote:
> I think the attached patch is correct and necessary to build libxslt
> with a python executable with is not in the global PATH. Patch against
> libxslt 1.0.33.

  that makes sense, applied and commited,

    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 k_isdale@tpg.com.au  Wed Oct 15 12:43:06 2003
Return-Path: <k_isdale@tpg.com.au>
Delivered-To: xslt@gnome.org
Received: from mail3.tpgi.com.au (mail.tpgi.com.au [203.12.160.59])
	by mail.gnome.org (Postfix) with ESMTP id CDEC918196
	for <xslt@gnome.org>; Wed, 15 Oct 2003 12:43:04 -0400 (EDT)
Received: from crevasse.isdale.tpg.com.au (203-219-14-18-qld.tpgi.com.au [203.219.14.18])
	(authenticated (0 bits))
	by mail3.tpgi.com.au (8.11.6/8.11.6) with ESMTP id h9FGhCT22199;
	Thu, 16 Oct 2003 02:43:13 +1000
From: Keith Isdale <k_isdale@tpg.com.au>
To: Kasimier Buchcik <kbuchcik@4commerce.de>
Subject: Re:[xslt] debugger callbacks
Date: Thu, 16 Oct 2003 02:48:36 +1000
User-Agent: KMail/1.5
Cc: xslt@gnome.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310160248.36167.k_isdale@tpg.com.au>
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Have you set xslDebugStatus to something other than XSLT_DEBUG_NONE, see 
<libxslt/xsltutils.h>.  You may find you can get the information that you 
want using xsldbg :-). 

------
Known cavates for the debugger callback functions are:
	o Be careful if you are modifing the data XSLT engine data structures  during 
a debugging step as you could put the tranformation engine into a bad state 
and give misleading resuilts.  
	o Be aware that the callbacks may not be in the same order as you would read 
the text source for the XSLT script.  
	o The XSLT pre-processing step will remove certain redundant  nodes, such as 
comment nodes, from the XSLT script before main work of  XSLT transformation 
is done. 
	o Line number information may or may not be available for any given XmlNode 
due to optimizations done during the pre-processing step
	o Whilst the xslAddCall and xslDropCall are always done in pairs the call 
stack depth can get over stated.  This is because transformation of some XSLT 
commands, for example xsl:for-each, increase the call stack depth otherwise 
there would be no way to know how to "break  out"  of the for loop. 


------

Daniel: Maybe these cavates could be added to the libxslt FAQ. I had trouble 
when I did  a search on xslDebugStatus in the XSLT API.  And I was suprised 
to get a "Error 404"  when pointing my browser at 
	http://xmlsoft.org/XSLT/XSLT/html/libxslt-transform.html#XSLHANDLEDEBUGGER
as suggested by the "xslHandleDebugger" link resulting from pointing my 
browser at 
http://xmlsoft.org/XSLT/search.php?query=xslDebugStatus+&submit=Search+...
(URL tested on Mozilla and Konqueror). 


Kasimier wrote;
> I tried to use xsltSetDebuggerCallbacks to get some callbacks during the=20
> transformation, but the registered functions are not called. Since a=20
> call of xslAddCall, fires the registered callback, I assume that=20
> xsltDebuggerCurrentCallbacks is correctly initialized.
> I guess libxslt (version see below) was compiled with WITH_DEBUGGER.

-- 
Keith  Isdale
http://sourceforge.net.projects/xsldbg  |   xsldbg helping understand 
stylesheets
http://xsldbg.sourceforge.net
 


From kbuchcik@4commerce.de  Thu Oct 16 07:32:21 2003
Return-Path: <kbuchcik@4commerce.de>
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 A99FA18466
	for <xslt@gnome.org>; Thu, 16 Oct 2003 07:32:20 -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 1AA6Ms-0004CK-00
	for xslt@gnome.org; Thu, 16 Oct 2003 13:32:34 +0200
From: Kasimier Buchcik <kbuchcik@4commerce.de>
To: <xslt@gnome.org>
X-Priority: 3
Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Thu, 16 Oct 2003 13:27:00 +0200
Received: from 4commerce.de (10.1.72.2 [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 47243FTV; Thu, 16 Oct 2003 13:27:00 +0200
Message-ID: <3F8E812E.4060600@4commerce.de>
Date: Thu, 16 Oct 2003 13:29:50 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
References: <200310160248.36167.k_isdale@tpg.com.au>
In-Reply-To: <200310160248.36167.k_isdale@tpg.com.au>
X-eMessageService: eMission.SMTPServer
Subject: "Re:[xslt] debugger callbacks"
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi,

Keith Isdale wrote:
> Have you set xslDebugStatus to something other than XSLT_DEBUG_NONE, see=20
> <libxslt/xsltutils.h>.  You may find you can get the information that you=20
> want using xsldbg :-).=20

No I did not set xslDebugStatus. Does this variable need to be set to=20
something? I learned that is it declared in "deprecated.c", but I cannot=20
set any variables, since I'm using Delphi 6 with the Pascal bindings to=20
access the libxslt library.

Could you implement a function that sets this variable?

> Known cavates for the debugger callback functions are:
> =09o Be careful if you are modifing the data XSLT engine data structures  =
du=
ring=20
> a debugging step as you could put the tranformation engine into a bad stat=
e=20
> and give misleading resuilts. =20
> =09o Be aware that the callbacks may not be in the same order as you would=
 r=
ead=20
> the text source for the XSLT script. =20
> =09o The XSLT pre-processing step will remove certain redundant  nodes, su=
ch=
 as=20
> comment nodes, from the XSLT script before main work of  XSLT transformati=
on=20
> is done.=20
> =09o Line number information may or may not be available for any given Xml=
No=
de=20
> due to optimizations done during the pre-processing step
> =09o Whilst the xslAddCall and xslDropCall are always done in pairs the ca=
ll=
=20
> stack depth can get over stated.  This is because transformation of some X=
SLT=20
> commands, for example xsl:for-each, increase the call stack depth otherwis=
e=20
> there would be no way to know how to "break  out"  of the for loop.=20
>=20
>=20
> ------
>=20
> Daniel: Maybe these cavates could be added to the libxslt FAQ. I had troub=
le=20
> when I did  a search on xslDebugStatus in the XSLT API.  And I was suprise=
d=20
> to get a "Error 404"  when pointing my browser at=20
> =09http://xmlsoft.org/XSLT/XSLT/html/libxslt-transform.html#XSLHANDLEDEBUG=
GE=
R
> as suggested by the "xslHandleDebugger" link resulting from pointing my=20
> browser at=20
> http://xmlsoft.org/XSLT/search.php?query=3DxslDebugStatus+&submit=3DSearch=
+...
> (URL tested on Mozilla and Konqueror).=20
>=20
>=20
> Kasimier wrote;
>=20
>>I tried to use xsltSetDebuggerCallbacks to get some callbacks during the=
=3D2=
0
>>transformation, but the registered functions are not called. Since a=3D20
>>call of xslAddCall, fires the registered callback, I assume that=3D20
>>xsltDebuggerCurrentCallbacks is correctly initialized.
>>I guess libxslt (version see below) was compiled with WITH_DEBUGGER.

Thanks for the hints Keith,

Kasimier Buchcik


From thijs@vandervossen.net  Thu Oct 16 09:13:27 2003
Return-Path: <thijs@vandervossen.net>
Delivered-To: xslt@gnome.org
Received: from doofpot.nl (mx1.cambrium.nl [217.19.16.130])
	by mail.gnome.org (Postfix) with ESMTP id 2576318D2F
	for <xslt@gnome.org>; Thu, 16 Oct 2003 09:13:27 -0400 (EDT)
Received: (qmail 24850 invoked from network); 16 Oct 2003 13:06:48 -0000
Received: from 217-19-22-138.dsl.cambrium.nl (217.19.22.138)
  by mx1.cambrium.nl with RC4-MD5 encrypted SMTP; 16 Oct 2003 13:06:48 -0000
From: Thijs van der Vossen <thijs@vandervossen.net>
To: xslt@gnome.org
Date: Thu, 16 Oct 2003 15:13:37 +0200
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310161513.37832.thijs@vandervossen.net>
Subject: [xslt] document() source
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Currently I am trying to find a way to have the xslt document() function get 
xml from other sources than the filesystem when using libxslt from Python.

This has been talked about before on this list, for example in 
http://mail.gnome.org/archives/xslt/2002-January/msg00010.html and 
http://mail.gnome.org/archives/xml/2001-March/msg00022.html

>From the last post I understand I would need to register some callbacks with 
xmlRegisterInputCallbacks(), but I can't seem to find this method anywhere in 
the Python bindings and I do not see any other way to register I/O handlers 
from Python.

Does anyone have any idea how to register I/O handlers or another way to have 
the document() function get xml for other sources?

Regards,
Thijs

-- 
Fingertips __ www.fngtps.com __ +31.(0)20.4896540

From veillard@redhat.com  Thu Oct 16 09:26:28 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id A71F518AA1
	for <xslt@gnome.org>; Thu, 16 Oct 2003 09:26:28 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9GDQfI20931;
	Thu, 16 Oct 2003 09:26:41 -0400
Date: Thu, 16 Oct 2003 09:26:41 -0400
From: Daniel Veillard <veillard@redhat.com>
To: thijs@vandervossen.net
Cc: xslt@gnome.org
Subject: Re: [xslt] document() source
Message-ID: <20031016092641.F16905@redhat.com>
References: <200310161513.37832.thijs@vandervossen.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: <200310161513.37832.thijs@vandervossen.net>; from thijs@vandervossen.net on Thu, Oct 16, 2003 at 03:13:37PM +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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Thu, Oct 16, 2003 at 03:13:37PM +0200, Thijs van der Vossen wrote:
> Currently I am trying to find a way to have the xslt document() function get 
> xml from other sources than the filesystem when using libxslt from Python.

  ftp and http should work as they are provided by default within libxml2

> This has been talked about before on this list, for example in 
> http://mail.gnome.org/archives/xslt/2002-January/msg00010.html and 
> http://mail.gnome.org/archives/xml/2001-March/msg00022.html
> 
> >From the last post I understand I would need to register some callbacks with 
> xmlRegisterInputCallbacks(), but I can't seem to find this method anywhere in 
> the Python bindings and I do not see any other way to register I/O handlers 
> from Python.
> 
> Does anyone have any idea how to register I/O handlers or another way to have 
> the document() function get xml for other sources?

  have you read the libxml2 examples in libxml2/python/tests especially
  resolver.py ?

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 thijs@fngtps.com  Thu Oct 16 10:10:29 2003
Return-Path: <thijs@fngtps.com>
Delivered-To: xslt@gnome.org
Received: from doofpot.nl (mx1.cambrium.nl [217.19.16.130])
	by mail.gnome.org (Postfix) with ESMTP id 29032184EF
	for <xslt@gnome.org>; Thu, 16 Oct 2003 10:10:29 -0400 (EDT)
Received: (qmail 28770 invoked from network); 16 Oct 2003 14:03:50 -0000
Received: from 217-19-22-138.dsl.cambrium.nl (217.19.22.138)
  by mx1.cambrium.nl with RC4-MD5 encrypted SMTP; 16 Oct 2003 14:03:50 -0000
From: Thijs van der Vossen <thijs@fngtps.com>
Subject: Re: [xslt] document() source
Date: Thu, 16 Oct 2003 16:10:42 +0200
User-Agent: KMail/1.5
To: Daniel Veillard <veillard@redhat.com>
Cc: xslt@gnome.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310161610.42687.thijs@fngtps.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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Thursday 16 October 2003 15:26, you wrote:
> On Thu, Oct 16, 2003 at 03:13:37PM +0200, Thijs van der Vossen wrote:
> > Currently I am trying to find a way to have the xslt document() function
> > get xml from other sources than the filesystem when using libxslt from
> > Python.
>
> ftp and http should work as they are provided by default within libxml2

Sorry, I was not specific enough here. I have a database system and strings
with xml data I would like to use as a source.

> > Does anyone have any idea how to register I/O handlers or another way to
> > have the document() function get xml for other sources?
>
> have you read the libxml2 examples in libxml2/python/tests especially
> resolver.py ?

Thanks. I have now and it cleared up things considerably. Writing a custom
entity resolver and registering it with libxml2.setEntityLoader() works fine.

Is it possible to write an custom entity resolver that tries to call the
libxml2 default entity resolver first, falling back on custom code when that
fails to load the external entity? When an external entity cannot be loaded I
get a warning message on stdout, but it looks like no Exception is triggered.
I also have no idea what the default entity resolver looks like or where it
is defined in libxml2 of libxml2mod

Maybe it would be better to have the custom entity resolver work with a
specific uri scheme only, letting the default entity resolver handle the
others?

Regards,
Thijs

-- 
Fingertips __ www.fngtps.com __ +31.(0)20.4896540

From veillard@redhat.com  Thu Oct 16 10:53:41 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id B58FD18776
	for <xslt@gnome.org>; Thu, 16 Oct 2003 10:53:40 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9GErsw04450;
	Thu, 16 Oct 2003 10:53:54 -0400
Date: Thu, 16 Oct 2003 10:53:53 -0400
From: Daniel Veillard <veillard@redhat.com>
To: Thijs van der Vossen <thijs@fngtps.com>
Cc: xslt@gnome.org
Subject: Re: [xslt] document() source
Message-ID: <20031016105353.H16905@redhat.com>
References: <200310161610.42687.thijs@fngtps.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: <200310161610.42687.thijs@fngtps.com>; from thijs@fngtps.com on Thu, Oct 16, 2003 at 04:10:42PM +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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Thu, Oct 16, 2003 at 04:10:42PM +0200, Thijs van der Vossen wrote:
> On Thursday 16 October 2003 15:26, you wrote:
> > > Does anyone have any idea how to register I/O handlers or another way to
> > > have the document() function get xml for other sources?
> >
> > have you read the libxml2 examples in libxml2/python/tests especially
> > resolver.py ?
> 
> Thanks. I have now and it cleared up things considerably. Writing a custom
> entity resolver and registering it with libxml2.setEntityLoader() works fine.
> 
> Is it possible to write an custom entity resolver that tries to call the
> libxml2 default entity resolver first, falling back on custom code when that
> fails to load the external entity? When an external entity cannot be loaded I

  Hum, it's easy in C, and would need some work in Python.

> get a warning message on stdout, but it looks like no Exception is triggered.

  Right, it's still basically C code, not python, you have to catch the 
errors, then generate an exception from there might work.

> I also have no idea what the default entity resolver looks like or where it
> is defined in libxml2 of libxml2mod

  xmlIO.c in libxml2

> Maybe it would be better to have the custom entity resolver work with a
> specific uri scheme only, letting the default entity resolver handle the
> others?

  Would require Python wrappers for the xmlIO.h layer. Patch welcome !

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 thijs@vandervossen.net  Thu Oct 16 10:04:11 2003
Return-Path: <thijs@vandervossen.net>
Delivered-To: xslt@gnome.org
Received: from doofpot.nl (mx1.cambrium.nl [217.19.16.130])
	by mail.gnome.org (Postfix) with ESMTP id D7C00184EF
	for <xslt@gnome.org>; Thu, 16 Oct 2003 10:04:10 -0400 (EDT)
Received: (qmail 10560 invoked from network); 16 Oct 2003 13:57:32 -0000
Received: from 217-19-22-138.dsl.cambrium.nl (217.19.22.138)
  by mx1.cambrium.nl with RC4-MD5 encrypted SMTP; 16 Oct 2003 13:57:32 -0000
From: Thijs van der Vossen <thijs@vandervossen.net>
To: xslt@gnome.org
Subject: Re: [xslt] document() source
Date: Thu, 16 Oct 2003 16:04:24 +0200
User-Agent: KMail/1.5
References: <200310161513.37832.thijs@vandervossen.net> <20031016092641.F16905@redhat.com>
In-Reply-To: <20031016092641.F16905@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310161604.24922.thijs@vandervossen.net>
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Thursday 16 October 2003 15:26, you wrote:
> On Thu, Oct 16, 2003 at 03:13:37PM +0200, Thijs van der Vossen wrote:
> > Currently I am trying to find a way to have the xslt document() function
> > get xml from other sources than the filesystem when using libxslt from
> > Python.
>
>   ftp and http should work as they are provided by default within libxml2

Sorry, I was not specific enough here. I have a database system and strings 
with xml data I would like to use as a source.

> > Does anyone have any idea how to register I/O handlers or another way to
> > have the document() function get xml for other sources?
>
>   have you read the libxml2 examples in libxml2/python/tests especially
>   resolver.py ?

Thanks. I have now and it cleared up things considerably. Writing a custom 
entity resolver and registering it with libxml2.setEntityLoader() works fine.

Is it possible to write an custom entity resolver that tries to call the 
libxml2 default entity resolver first, falling back on custom code when that 
fails to load the external entity? When an external entity cannot be loaded I 
get a warning message on stdout, but it looks like no Exception is triggered. 
I also have no idea what the default entity resolver looks like or where it 
is defined in libxml2 of libxml2mod

Maybe it would be better to have the custom entity resolver work with a 
specific uri scheme only, letting the default entity resolver handle the 
others?

Regards,
Thijs

-- 
Fingertips __ www.fngtps.com __ +31.(0)20.4896540

From bkc@murkworks.com  Thu Oct 16 12:21:30 2003
Return-Path: <bkc@murkworks.com>
Delivered-To: xslt@gnome.org
Received: from anvil.murkworks.com (anvil.murkworks.com [128.153.43.1])
	by mail.gnome.org (Postfix) with ESMTP id 672C718D78
	for <xslt@gnome.org>; Thu, 16 Oct 2003 12:21:30 -0400 (EDT)
Received: from coal.murkworks.com (coal.murkworks.com [128.153.43.3])
	by anvil.murkworks.com (8.9.1/8.9.1) with ESMTP id MAA22520
	for <xslt@gnome.org>; Thu, 16 Oct 2003 12:21:27 -0400 (EDT)
Received: from GIMPELSTIMER/SpoolDir by coal.murkworks.com (Mercury 1.44);
    16 Oct 03 12:17:57 -0400
Received: from SpoolDir by GIMPELSTIMER (Mercury 1.44); 16 Oct 03 12:17:51 -0400
From: "Brad Clements" <bkc@murkworks.com>
Organization: MurkWorks, Incorporated.
To: xslt@gnome.org
Date: Thu, 16 Oct 2003 12:17:45 -0400
MIME-Version: 1.0
Subject: Re: [xslt] document() source
Message-ID: <3F8E8D4D.17211.F40CE34@localhost>
Priority: normal
In-reply-to: <20031016105353.H16905@redhat.com>
References: <200310161610.42687.thijs@fngtps.com>; from thijs@fngtps.com on Thu, Oct 16, 2003 at 04:10:42PM +0200
X-mailer: Pegasus Mail for Windows (v4.20 beta 8)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
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: bkc@murkworks.com
List-Help: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On 16 Oct 2003 at 10:53, Daniel Veillard wrote:

>   Right, it's still basically C code, not python, you have to catch the
> errors, then generate an exception from there might work.
> 

I noticed that if my resolver generates an exception, the built-in resolver tries to handle 
the URL.

I think it would be better if the exception was "passed up" to the original calling function, 
rather than masking it in the resolver and "dropping it".

I'm not sure if this is possible given the current architecture. I'm using xslt.

I think it might be cleaner to say.. the resolver returns a readable() object or a string 
object on success. None when the default resolver should be used, and anything else 
is an exception. And, if the resolver raises an exception, it should be passed up.

currently I think only a readable (file) object is accepted, which is then read() back into 
a DOM object. Interestingly, my resolver has a string and has to use StringIO to make it 
a readable file-like object ;-)

If someone says it's possible to propoge exceptions up, I'll submit a patch. I just 
couldn't tell if libxml could be told "hey, stop, we're dead, don't create a new exception 
there's one pending". I think that'll have to be handled in the external python wrapper, 
not libxslt or libxml C code.



-- 
Brad Clements,                bkc@murkworks.com   (315)268-1000
http://www.murkworks.com                          (315)268-9812 Fax
http://www.wecanstopspam.org/                   AOL-IM: BKClements


From k_isdale@tpg.com.au  Fri Oct 17 21:36:26 2003
Return-Path: <k_isdale@tpg.com.au>
Delivered-To: xslt@gnome.org
Received: from mail1.tpgi.com.au (mail.tpgi.com.au [203.12.160.57])
	by mail.gnome.org (Postfix) with ESMTP id 2F3B3183B9
	for <xslt@gnome.org>; Fri, 17 Oct 2003 21:36:25 -0400 (EDT)
Received: from crevasse.isdale.tpg.com.au (203-219-14-18-qld.tpgi.com.au [203.219.14.18])
	(authenticated (0 bits))
	by mail1.tpgi.com.au (8.11.6/8.11.6) with ESMTP id h9I1ac829140
	for <xslt@gnome.org>; Sat, 18 Oct 2003 11:36:39 +1000
From: Keith Isdale <k_isdale@tpg.com.au>
To: xslt@gnome.org
Subject: Re:[xslt] debugger callbacks
Date: Sat, 18 Oct 2003 11:42:00 +1000
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310181142.00453.k_isdale@tpg.com.au>
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Sorry I'm not a Pascal person and could provide an implementation in the time 
I had availalble. Try discussing Pascal on the xml/xslt bindings list. 

 Kasimier Buchcik <kbuchcik@4commerce.de> wrote:
> Keith Isdale wrote:
> > Have you set xslDebugStatus to something other than XSLT_DEBUG_NONE, 
see=20
>> <libxslt/xsltutils.h>.  You may find you can get the information that 
you=20
>> want using xsldbg :-).=20

>No I did not set xslDebugStatus. Does this variable need to be set to=20
>something? I learned that is it declared in "deprecated.c", but I cannot=20

umm no thats not right. .xslDebugStatus is declared in <libxslt/xsltutils.h> 
and defined in libxslt/libxslt/xsltutils.c See
http://cvs.gnome.org/bonsai/cvsblame.cgi?file=libxslt%2Flibxslt/xsltutils.c&rev=&root=/cvs/gnome
	and 
http://cvs.gnome.org/bonsai/cvsblame.cgi?file=libxslt%2Flibxslt/xsltutils.h&rev=&root=/cvs/gnome

You had me worried for a moment deprecated.c sounds like code that will be 
removed next major release.

>set any variables, since I'm using Delphi 6 with the Pascal bindings to=20
> access the libxslt library.

>Could you implement a function that sets this variable?

You can always submit a patch to xsltutils.c/xsltutils.h and see what happens. 
: trivial implementation for xsltutils,.h
	void xsltSetDebuggerStatus(int value);
	int xsltGetDebuggerStatus();

: trivial implementation for xsltutils.c
	void xsltSetDebuggerStatus(int value)
	{
		xslDebugStatus. = value;
	}

	int xsltGetDebuggerStatus()
	{
		return xslDebugStatus. 
	}

Don't put the implementation in a header file as one day someone may want a 
properly mulitthreaded XSLT debugger and libxslt may be able to be changed to 
meat that requirement: for a non Binary Compatable  future release of 
libxslt.

-- 
Keith  Isdale
http://sourceforge.net.projects/xsldbg  |   xsldbg helping understand 
stylesheets
http://xsldbg.sourceforge.net
 


From bob@decoy.wox.org  Sun Oct 19 23:42:37 2003
Return-Path: <bob@decoy.wox.org>
Delivered-To: xslt@gnome.org
Received: from decoy.wox.org (206.180.133.7.adsl.hal-pc.org [206.180.133.7])
	by mail.gnome.org (Postfix) with ESMTP id 7FB7F1885C
	for <xslt@gnome.org>; Sun, 19 Oct 2003 23:42:37 -0400 (EDT)
Received: from quux.opus.geek (bluesocket.utdallas.edu [129.110.39.12])
	by decoy.wox.org (Postfix) with ESMTP id 8A72627407
	for <xslt@gnome.org>; Sun, 19 Oct 2003 22:42:51 -0500 (CDT)
Received: by quux.opus.geek (Postfix, from userid 1000)
	id D7BEF482BF; Sun, 19 Oct 2003 22:40:33 -0500 (CDT)
Date: Sun, 19 Oct 2003 22:40:33 -0500
From: Graham Wilson <bob@decoy.wox.org>
To: xslt@gnome.org
Message-ID: <20031020034033.GA3272@quux.opus.geek>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw"
Content-Disposition: inline
X-GPG-Fingerprint: A0A7 AE54 665D 6446 F2D9  81FF 8B94 031D 7F75 635F
X-GPG-Key: http://decoy.wox.org/~bob/public.asc
User-Agent: Mutt/1.5.4i
Subject: [xslt] linking of libexslt
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

--wac7ysb48OaltWcw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Daniel,

It seems that if libxslt is not installed on the system when the
configure script is run, libexslt (and libxsltbreakpoint) are not linked
at all against libxslt. This causes undefined symbols in the resulting
libexslt.

Also, there is code in libexslt's Makefile.am (although it is commented
out) which links libexslt against the recently-built libxslt, instead of
the system libxslt. Why is this commented out? Isn't this the right way
to do it?

--=20
gram

--wac7ysb48OaltWcw
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: http://decoy.wox.org/~bob/public.asc

iQEVAwUBP5NZMS6fnYH5E4SWAQInYwf/Rz+XDMhXA+s5iTF/k2OwfO02DjA0HZiN
hugXQTNBkJH1N/5lK438RqXqZnhYgiB2Px/OJtQk3a3LTbnB7HcEmckkyxr/mauD
7oHtsnWSi4LDUDXbPg8muymme3kpLlh7RoTB0W4GSWNijIiram5YE4vvrD5kNsAa
2CSu63A56/a4/Dveen6+24ea7z0s/IW9RU/gMhesNc9BeI/Fabz+I+vDB/8X5Txu
ii27+6QFlR+jCs0FLZPm8NoovXT+eDnJjnpM2qsH0xv70JwWgqs5tUU1k7O2qNir
G5wAM3NQEIGb/OiX9BbHkeKp4tpXWO1j6HywTPsasKCzOfLGV/p2fQ==
=zGfb
-----END PGP SIGNATURE-----

--wac7ysb48OaltWcw--

From veillard@redhat.com  Mon Oct 20 02:43:28 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 31C4418145
	for <xslt@gnome.org>; Mon, 20 Oct 2003 02:43:28 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9K6hir13492
	for xslt@gnome.org; Mon, 20 Oct 2003 02:43:44 -0400
Date: Mon, 20 Oct 2003 02:43:44 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: [xslt] linking of libexslt
Message-ID: <20031020024344.L16905@redhat.com>
References: <20031020034033.GA3272@quux.opus.geek>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20031020034033.GA3272@quux.opus.geek>; from bob@decoy.wox.org on Sun, Oct 19, 2003 at 10:40:33PM -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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Sun, Oct 19, 2003 at 10:40:33PM -0500, Graham Wilson wrote:
> Hi Daniel,
> 
> It seems that if libxslt is not installed on the system when the
> configure script is run, libexslt (and libxsltbreakpoint) are not linked
> at all against libxslt. This causes undefined symbols in the resulting
> libexslt.

  Hum, possible.

> Also, there is code in libexslt's Makefile.am (although it is commented
> out) which links libexslt against the recently-built libxslt, instead of
> the system libxslt. Why is this commented out? Isn't this the right way
> to do it?

  Because dependancies between "being built" libraries is a problem in
practice. It is very likely that I did so to ensure that the common case
I can test and debug and must have working do indeed work.
  I takes patches about configure/Makefile and shared libraries but with
a lot of caution, because usually I get patches which work for the platform
or the use case for which the person was interested in but tend to break
othert setups. It is extremely hard to assess that there is no regression
in configure/Makefile 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 bz@datenkueche.com  Tue Oct 21 11:08:43 2003
Return-Path: <bz@datenkueche.com>
Delivered-To: xslt@gnome.org
Received: from datenkueche.com (unknown [213.133.101.202])
	by mail.gnome.org (Postfix) with SMTP id 3F2A1180EC
	for <xslt@gnome.org>; Tue, 21 Oct 2003 11:08:42 -0400 (EDT)
Received: (qmail 30802 invoked from network); 21 Oct 2003 15:08:57 -0000
Received: from localhost (127.0.0.1)
  by 0 with SMTP; 21 Oct 2003 15:08:57 -0000
Received: from 212.186.108.243 ( [212.186.108.243])
	as user bz@datenkueche.com by webmail.datenkueche.com with HTTP;
	Tue, 21 Oct 2003 17:08:57 +0200
Message-ID: <1066748937.3f954c0930d87@webmail.datenkueche.com>
Date: Tue, 21 Oct 2003 17:08:57 +0200
From: Bernhard Zwischenbrugger <bz@datenkueche.com>
To: "xslt@gnome.org" <xslt@gnome.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.1
X-Originating-IP: 212.186.108.243
Subject: [xslt] Working with lots of XML files
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi all

I have an index.xml that points to about 300 xml Files.

index.xml looks like:
<all>
<item file="/somewhere/file1.xml"/>
<item file="/somewhere/file2.xml"/>

....

<item file="/somewhere/file300.xml"/>
</all>
------------
file1.xml looks like:
<all>
<position num="1" price="100"/>
<position num="2" price="300"/>
...
<position num="1000" price="30"/>
---------------


Now I want to build the sum of all prices.

The stylesheet is easy made:

<xsl:for-each select="/all/item">
<xsl:apply-templates select="exsl:node-set(document(@file))" mode="makesum"/>
</xsl:for-each>

<xsl:template match="*" mode="makesum">
...
make sum
..
</xsl:template>

-----------------

The problem I have, is that xsltproc at the moment needs about 200MB Ram to 
process 
this and the list of XML Files will grow maybe up to 10000 in the next
years.

----
My question:

Isn't it possible to load an XML file using the document() function and
than free the memory again after processing the file?
Is this not possible because of the xSLT Spezification or could
this be optimized with an improved libxslt implementation?
Or with an opimized stylesheet?

I have to make some decisions now, that will effect the scaleability
of my software in some year.

It would be nice to get some hints on this.

Bernhard Zwischenbrugger
http://datenkueche.com

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/


From bruce.miller@nist.gov  Tue Oct 21 11:31:02 2003
Return-Path: <bruce.miller@nist.gov>
Delivered-To: xslt@gnome.org
Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205])
	by mail.gnome.org (Postfix) with ESMTP id E7113180EC
	for <xslt@gnome.org>; Tue, 21 Oct 2003 11:31:01 -0400 (EDT)
Received: from nist.gov ([67.21.63.3]) by mta11.adelphia.net
          (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP
          id <20031021153121.HBPU1451.mta11.adelphia.net@nist.gov>
          for <xslt@gnome.org>; Tue, 21 Oct 2003 11:31:21 -0400
Message-ID: <3F955145.2090903@nist.gov>
Date: Tue, 21 Oct 2003 11:31:17 -0400
From: Bruce Miller <bruce.miller@nist.gov>
Organization: NIST
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: xslt@gnome.org
Subject: Re: [xslt] Working with lots of XML files
References: <1066748937.3f954c0930d87@webmail.datenkueche.com>
In-Reply-To: <1066748937.3f954c0930d87@webmail.datenkueche.com>
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Bernhard Zwischenbrugger wrote:
[..]
> The stylesheet is easy made:
> 
> <xsl:for-each select="/all/item">
> <xsl:apply-templates select="exsl:node-set(document(@file))" mode="makesum"/>
> </xsl:for-each>
> 
> <xsl:template match="*" mode="makesum">
> ....
> make sum
> ...
> </xsl:template>
> 
> -----------------
> 
> The problem I have, is that xsltproc at the moment needs about 200MB Ram to 
> process 
> this and the list of XML Files will grow maybe up to 10000 in the next
> years.

I've been getting in the habit of using a hybrid of xslt + DOM manipulation
(whatever binding you like; Python, Perl's XML::LibXML), whenver the XSL
would get too `nasty'.   Here you're xsl is simple enough, but ...

Anyway, have you considered computing the sum in some other language?
Loop over the files, for each file:
  read it in, compute partial sum, then the doc gets freed.
It would be essentially as simple as your stylesheet, providing it
fits into your `pipeline'...



-- 
bruce.miller@nist.gov
http://math.nist.gov/~BMiller/


From JPocock@transoft.com  Wed Oct 22 03:57:40 2003
Return-Path: <JPocock@transoft.com>
Delivered-To: xslt@gnome.org
Received: from transoft.com (mail.transoft.com [193.119.52.66])
	by mail.gnome.org (Postfix) with ESMTP id 38FB218139
	for <xslt@gnome.org>; Wed, 22 Oct 2003 03:57:40 -0400 (EDT)
Received: by tsfire.transoft.com id <117132>; Wed, 22 Oct 2003 09:01:09 +0100
Message-Id: <03Oct22.090109bst.117132@tsfire.transoft.com>
From: John Pocock <JPocock@transoft.com>
To: xslt@gnome.org
Date:  Wed, 22 Oct 2003 08:18:12 +0100
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [xslt] [NOVICE] Differences processing Stylesheet from memory vs from fi
 le
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

I have just started using libxslt & am having some problems working out the difference between creating DOms in memory and parsing the XML from files.

I wrote this code

char *applyStyle(xmlDocPtr style, xmlDocPtr doc) {
  char *out;
  int len;
  xmlDocPtr tmp;
  xmlDocPtr htmlDoc;
  xmlSubstituteEntitiesDefault(1);
  xmlLoadExtDtdDefaultValue = 1;
  it = xsltParseStylesheetDoc(style);
  htmlDoc = xsltApplyStylesheet(it,doc,NULL);
  if (it != NULL && htmlDoc != NULL) {
    res = xsltSaveResultToString(&out,&len,htmlDoc,it);
    return out;
  } else {
    return NULL;
  }
}

Both 'style & 'doc' are created as in-memory DOMs,  & I have checked them for correctness by saving to file & examining the files. I cannot get the result I expect - in this code, 'it' always ends up as NULL.

If I change the code to save & re-parse the same DOMs

char *applyStyle(xmlDocPtr style, xmlDocPtr doc) {
  char *out;
  int len;
  int res;
  xsltStylesheetPtr it = NULL;
  xmlDocPtr tmp;
  xmlDocPtr htmlDoc;
  xmlSubstituteEntitiesDefault(1);
  xmlLoadExtDtdDefaultValue = 1;
  xmlSaveFormatFile("c:/temp/doc.xml",doc,1);
  tmp = xmlParseFile("c:/temp/doc.xml");
  xmlSaveFormatFile("c:/temp/style.xsl",style,1);
  it = xsltParseStylesheetFile("c:/temp/style.xsl");
  htmlDoc = xsltApplyStylesheet(it,tmp,NULL);
  if (it != NULL && htmlDoc != NULL) {
    res = xsltSaveResultToString(&out,&len,htmlDoc,it);
    return out;
  } else {
    return NULL;
  }
}

Everything works as expected.

Can anyone explain the difference for me, please.

Thanks in advance,

John N Pocock
===========

From abc@executive-solutions.com  Tue Oct 21 23:52:19 2003
Return-Path: <abc@executive-solutions.com>
Delivered-To: xslt@gnome.org
Received: from dt11.executive-solutions.com (dt11.tlgonline.com [64.239.86.38])
	by mail.gnome.org (Postfix) with ESMTP id E9878180F0
	for <xslt@gnome.org>; Tue, 21 Oct 2003 23:52:18 -0400 (EDT)
Received: from dt11.executive-solutions.com (root@localhost)
	by dt11.executive-solutions.com (8.11.6/8.11.6) with SMTP id h9M3qWv03949
	for <xslt@gnome.org>; Tue, 21 Oct 2003 23:52:32 -0400
Received: from localhost.localdomain (ts2-a84.Omsk.dial.rol.ru [194.186.135.84])
	by dt11.executive-solutions.com (8.11.6/8.11.6) with ESMTP id h9M3qUr03942
	for <xslt@gnome.org>; Tue, 21 Oct 2003 23:52:31 -0400
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (Postfix) with SMTP id E8FE377C47
	for <xslt@gnome.org>; Wed, 22 Oct 2003 10:52:26 +0700 (OMSST)
Date: Wed, 22 Oct 2003 10:52:26 +0700
From: Alex Sergeyev <abc@executive-solutions.com>
To: xslt@gnome.org
Message-Id: <20031022105226.3f122492.abc@executive-solutions.com>
X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i586-alt-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: [xslt] exslt strings bug
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hello,

I found, that exslt-strings-split and exslt-strings-tokenize don't work correctly with the entities in argument.... Just few examples based on libxslt-1.0.33/tests/exslt/strings files

tokenize.2.xsl
	You can try these:
	str:tokenize('This is &amp; strange behavior', ' ')
        str:tokenize('This is &amp; strange; behavior', ' ')
	str:tokenize('This is &amp;strange; behavior', ' ')

split.1.xsl
	just one to be sure:
	str:split('data &amp;math str;') doesn't work correctly


That's it.

Alex.


From veillard@redhat.com  Wed Oct 22 04:57:55 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id A02E318A95
	for <xslt@gnome.org>; Wed, 22 Oct 2003 04:57:55 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9M8wBI03812;
	Wed, 22 Oct 2003 04:58:11 -0400
Date: Wed, 22 Oct 2003 04:58:11 -0400
From: Daniel Veillard <veillard@redhat.com>
To: abc@executive-solutions.com
Cc: xslt@gnome.org
Subject: Re: [xslt] exslt strings bug
Message-ID: <20031022045811.I17879@redhat.com>
References: <20031022105226.3f122492.abc@executive-solutions.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: <20031022105226.3f122492.abc@executive-solutions.com>; from abc@executive-solutions.com on Wed, Oct 22, 2003 at 10:52:26AM +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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wed, Oct 22, 2003 at 10:52:26AM +0700, Alex Sergeyev wrote:
> Hello,
> 
> I found, that exslt-strings-split and exslt-strings-tokenize don't work correctly with the entities in argument.... Just few examples based on libxslt-1.0.33/tests/exslt/strings files
> 
> tokenize.2.xsl
> 	You can try these:
> 	str:tokenize('This is &amp; strange behavior', ' ')
>         str:tokenize('This is &amp; strange; behavior', ' ')
> 	str:tokenize('This is &amp;strange; behavior', ' ')
> 
> split.1.xsl
> 	just one to be sure:
> 	str:split('data &amp;math str;') doesn't work correctly

  Please bugzilla the problem:
     http://xmlsoft.org/XSLT/bugs.html

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 Oct 22 04:57:01 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 69CBC18A95
	for <xslt@gnome.org>; Wed, 22 Oct 2003 04:57:01 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9M8vIA03692
	for xslt@gnome.org; Wed, 22 Oct 2003 04:57:18 -0400
Date: Wed, 22 Oct 2003 04:57:18 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: [xslt] [NOVICE] Differences processing Stylesheet from memory vs from fi le
Message-ID: <20031022045718.H17879@redhat.com>
References: <03Oct22.090109bst.117132@tsfire.transoft.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: <03Oct22.090109bst.117132@tsfire.transoft.com>; from JPocock@transoft.com on Wed, Oct 22, 2003 at 08:18:12AM +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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wed, Oct 22, 2003 at 08:18:12AM +0100, John Pocock wrote:
> I have just started using libxslt & am having some problems working out the difference between creating DOms in memory and parsing the XML from files.
[...]
> Both 'style & 'doc' are created as in-memory DOMs,  & I have checked them for correctness by saving to file & examining the files. I cannot get the result I expect - in this code, 'it' always ends up as NULL.
> 
> If I change the code to save & re-parse the same DOMs
[...]
> Everything works as expected.
> 
> Can anyone explain the difference for me, please.

  This means you have made errors when building the DOM, it doesn't
affect serialization but XSLT processing fails. You should have errors
raised somewhere, check them and use a debugger to trace down where
this happens. That's not something we can do for you...

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 bz@datenkueche.com  Wed Oct 22 05:01:49 2003
Return-Path: <bz@datenkueche.com>
Delivered-To: xslt@gnome.org
Received: from datenkueche.com (unknown [213.133.101.202])
	by mail.gnome.org (Postfix) with SMTP id B96201813C
	for <xslt@gnome.org>; Wed, 22 Oct 2003 05:01:48 -0400 (EDT)
Received: (qmail 17802 invoked from network); 22 Oct 2003 09:02:00 -0000
Received: from localhost (127.0.0.1)
  by 0 with SMTP; 22 Oct 2003 09:02:00 -0000
Received: from 212.186.108.243 ( [212.186.108.243])
	as user bz@datenkueche.com by webmail.datenkueche.com with HTTP;
	Wed, 22 Oct 2003 11:02:00 +0200
Message-ID: <1066813320.3f96478861e22@webmail.datenkueche.com>
Date: Wed, 22 Oct 2003 11:02:00 +0200
From: Bernhard Zwischenbrugger <bz@datenkueche.com>
To: "xslt@gnome.org" <xslt@gnome.org>
References: <1062948210.3f5b4d72315aa@webmail.datenkueche.com> <20031021130022.B17879@redhat.com>
In-Reply-To: <20031021130022.B17879@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.1
X-Originating-IP: 212.186.108.243
Subject: [xslt] xmlsoft.org up again
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi 

>   seems xmlsoft.org is down, which is a bit unfortunate considering
> 2.6.0 release was done today, any idea of what's going on and how long it
> is
> gonna take to recover ?
> 

The Server 
http://xmlsoft.org 
http://datenkueche.com

was down for about 12 hours because of a broken CPU FAN. 


Bernhard Zwischenbrugger
http://datenkueche.com



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/


From pj@walter-graphtek.com  Wed Oct 22 05:16:40 2003
Return-Path: <pj@walter-graphtek.com>
Delivered-To: xslt@gnome.org
Received: from jessenlenz.com (mail.jessenlenz.com [212.79.192.34])
	by mail.gnome.org (Postfix) with ESMTP id A3951180DA
	for <xslt@gnome.org>; Wed, 22 Oct 2003 05:16:40 -0400 (EDT)
Received: from SOFTDEV8 (217.0.70.67) by jessenlenz.com with ESMTP (Eudora
 Internet Mail Server 3.1.4); Wed, 22 Oct 2003 11:13:29 +0200
From: "Peter Jacobi" <pj@walter-graphtek.com>
To: Bernhard Zwischenbrugger <bz@datenkueche.com>
Date: Wed, 22 Oct 2003 11:17:50 +0200
MIME-Version: 1.0
Subject: Re: [xslt] xmlsoft.org up again
Cc: "xslt@gnome.org" <xslt@gnome.org>
Message-ID: <3F96675E.355.B9FFED@localhost>
Priority: normal
In-reply-to: <1066813320.3f96478861e22@webmail.datenkueche.com>
References: <20031021130022.B17879@redhat.com>
X-mailer: Pegasus Mail for Windows (v4.02)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Bernhard wrote:

> was down for about 12 hours because of a broken CPU FAN. 

Isn't this rather 20th century? 
Current fashion is blown up capicitors ;-)

Peter Jacobi




From johan30@easynet.be  Wed Oct 22 05:21:46 2003
Return-Path: <johan30@easynet.be>
Delivered-To: xslt@gnome.org
Received: from smtp3.mail.be.easynet.net (bigglesworth.mail.be.easynet.net [212.100.160.67])
	by mail.gnome.org (Postfix) with ESMTP id A67C1182B2
	for <xslt@gnome.org>; Wed, 22 Oct 2003 05:21:46 -0400 (EDT)
Received: from sweety.office.be.easynet.net ([212.100.163.138])
	by smtp3.mail.be.easynet.net with esmtp (Exim 4.22)
	id 1ACFBr-0004z8-5L; Wed, 22 Oct 2003 11:22:03 +0200
From: johan <johan30@easynet.be>
To: xslt@gnome.org, python-list@python.org
Date: Wed, 22 Oct 2003 11:22:02 +0200
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310221122.02487.johan30@easynet.be>
Subject: [xslt] initlibxslt with python2.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
X-Reply-To: johan30@easynet.be
List-Help: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi,

I try to install CMFOODoument under zope, who use, libxml2, libxslt and their 
python bindings. (python 2.1) When I import libxslt, I receive error : 
 import libxslt
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: dynamic module does not define init function (initlibxslt)

I use libxslt-1.0.33, libxml2-2.6.0.tar.gz, and libxml2-2.6.0

Anybody knows what I do wrong ?

Greetings,
Johan

From veillard@redhat.com  Wed Oct 22 05:33:23 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 229C418189
	for <xslt@gnome.org>; Wed, 22 Oct 2003 05:33:23 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9M9Xdl17278;
	Wed, 22 Oct 2003 05:33:39 -0400
Date: Wed, 22 Oct 2003 05:33:39 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Cc: python-list@python.org
Subject: Re: [xslt] initlibxslt with python2.1
Message-ID: <20031022053339.K17879@redhat.com>
References: <200310221122.02487.johan30@easynet.be>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <200310221122.02487.johan30@easynet.be>; from johan30@easynet.be on Wed, Oct 22, 2003 at 11:22:02AM +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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wed, Oct 22, 2003 at 11:22:02AM +0200, johan wrote:
> Hi,
> 
> I try to install CMFOODoument under zope, who use, libxml2, libxslt and their 
> python bindings. (python 2.1) When I import libxslt, I receive error : 
>  import libxslt
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
> ImportError: dynamic module does not define init function (initlibxslt)
> 
> I use libxslt-1.0.33, libxml2-2.6.0.tar.gz, and libxml2-2.6.0
> 
> Anybody knows what I do wrong ?

  either it was miscompiled or you have a rogue libxsltmod module
somewhere which is taking over libxslt-python own module in the 
paths looked at by python.
   libxslt-python has been tested without troubles for all the 
versions of python from 1.5 to 2.2

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  Wed Oct 22 05:41:52 2003
Return-Path: <kbuchcik@4commerce.de>
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 C7E1718298
	for <xslt@gnome.org>; Wed, 22 Oct 2003 05:41:51 -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 1ACFVH-0002gA-00
	for xslt@gnome.org; Wed, 22 Oct 2003 11:42:07 +0200
From: Kasimier Buchcik <kbuchcik@4commerce.de>
To: <xslt@gnome.org>
X-Priority: 3
Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Wed, 22 Oct 2003 11:39:05 +0200
Received: from 4commerce.de (10.1.72.2 [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id VJHJYG89; Wed, 22 Oct 2003 11:39:05 +0200
Message-ID: <3F9650D3.60306@4commerce.de>
Date: Wed, 22 Oct 2003 11:41:39 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
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] set/get functions for xslDebugStatus
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi,

Could the following get/set functions to set/get the xslDebugStatus=20
variable be added to xsltutils? In order to manipulate them from pascal,=20
functions are needed (well, one can set variables but not without doing=20
some dirty hacking).

Thanks,

Kasimier Buchcik

Index: xsltutils.c
=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
RCS file: /cvs/gnome/libxslt/libxslt/xsltutils.c,v
retrieving revision 1.77
diff -r1.77 xsltutils.c
1734a1735,1757
 >  * xsltSetDebuggerStatus:
 >  * @value : the value to be set
 >  *
 >  * This function sets the value of xslDebugStatus.
 >  */
 > void
 > xsltSetDebuggerStatus(int value)
 > {
 >     xslDebugStatus =3D value;=09
 > }
 >
 > /**
 >  * xsltGetDebuggerStatus:
 >  *
 >  * This function returns the value of xslDebugStatus.
 >  */
 > int
 > xsltGetDebuggerStatus(void)
 > {
 >     return(xslDebugStatus);=09
 > }
 >
 > /**


Index: xsltutils.h
=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
RCS file: /cvs/gnome/libxslt/libxslt/xsltutils.h,v
retrieving revision 1.37
diff -r1.37 xsltutils.h
231a232,235
 > XSLTPUBFUN void XSLTCALL
 > =09=09xsltSetDebuggerStatus=09=09(int value);
 > XSLTPUBFUN int XSLTCALL
 > =09=09xsltGetDebuggerStatus=09=09(void);


From johan30@easynet.be  Wed Oct 22 05:51:43 2003
Return-Path: <johan30@easynet.be>
Delivered-To: xslt@gnome.org
Received: from smtp3.mail.be.easynet.net (bigglesworth.mail.be.easynet.net [212.100.160.67])
	by mail.gnome.org (Postfix) with ESMTP id 827D718219
	for <xslt@gnome.org>; Wed, 22 Oct 2003 05:51:43 -0400 (EDT)
Received: from sweety.office.be.easynet.net ([212.100.163.138])
	by smtp3.mail.be.easynet.net with esmtp (Exim 4.22)
	id 1ACFeq-0006kR-ET
	for xslt@gnome.org; Wed, 22 Oct 2003 11:52:00 +0200
From: johan <johan30@easynet.be>
To: xslt@gnome.org
Subject: Re: [xslt] initlibxslt with python2.1
Date: Wed, 22 Oct 2003 11:51:59 +0200
User-Agent: KMail/1.5
References: <200310221122.02487.johan30@easynet.be> <20031022053339.K17879@redhat.com>
In-Reply-To: <20031022053339.K17879@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310221151.59743.johan30@easynet.be>
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: johan30@easynet.be
List-Help: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wednesday 22 October 2003 11:33, Daniel Veillard wrote:
> On Wed, Oct 22, 2003 at 11:22:02AM +0200, johan wrote:
> > Hi,
> >
> > I try to install CMFOODoument under zope, who use, libxml2, libxslt and
> > their python bindings. (python 2.1) When I import libxslt, I receive
> > error : import libxslt
> > Traceback (most recent call last):
> >   File "<stdin>", line 1, in ?
> > ImportError: dynamic module does not define init function (initlibxslt)
> >
> > I use libxslt-1.0.33, libxml2-2.6.0.tar.gz, and libxml2-2.6.0
> >
> > Anybody knows what I do wrong ?
>
>   either it was miscompiled or you have a rogue libxsltmod module
> somewhere which is taking over libxslt-python own module in the
> paths looked at by python.
>    libxslt-python has been tested without troubles for all the
> versions of python from 1.5 to 2.2
>
> Daniel
thx for the answer : in my description I made an error : I use libxslt-1.0.33, 
libxml2-2.6.0 and libxml2-python-2.6.0. Apparently I didnt compile 
libxslt-python , since I didnt find the source. Perhaps this is the problem ?
Greetings,
Johan

From veillard@redhat.com  Wed Oct 22 05:55:08 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 62A2018219
	for <xslt@gnome.org>; Wed, 22 Oct 2003 05:55:07 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9M9tNo25669
	for xslt@gnome.org; Wed, 22 Oct 2003 05:55:23 -0400
Date: Wed, 22 Oct 2003 05:55:23 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: [xslt] set/get functions for xslDebugStatus
Message-ID: <20031022055523.O17879@redhat.com>
References: <3F9650D3.60306@4commerce.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3F9650D3.60306@4commerce.de>; from kbuchcik@4commerce.de on Wed, Oct 22, 2003 at 11:41: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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wed, Oct 22, 2003 at 11:41:39AM +0200, Kasimier Buchcik wrote:
> Hi,
> 
> Could the following get/set functions to set/get the xslDebugStatus 
> variable be added to xsltutils? In order to manipulate them from pascal, 
> functions are needed (well, one can set variables but not without doing 
> some dirty hacking).

  okay, but send me a contextual patch (diff -c or diff -p) and preferably
as an attachment,

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 Oct 22 05:58:50 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 55BEE18A7B
	for <xslt@gnome.org>; Wed, 22 Oct 2003 05:58:50 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9M9x6S27406
	for xslt@gnome.org; Wed, 22 Oct 2003 05:59:06 -0400
Date: Wed, 22 Oct 2003 05:59:06 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: [xslt] initlibxslt with python2.1
Message-ID: <20031022055906.P17879@redhat.com>
References: <200310221122.02487.johan30@easynet.be> <20031022053339.K17879@redhat.com> <200310221151.59743.johan30@easynet.be>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <200310221151.59743.johan30@easynet.be>; from johan30@easynet.be on Wed, Oct 22, 2003 at 11:51:59AM +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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wed, Oct 22, 2003 at 11:51:59AM +0200, johan wrote:
> thx for the answer : in my description I made an error : I use libxslt-1.0.33, 
> libxml2-2.6.0 and libxml2-python-2.6.0. Apparently I didnt compile 
> libxslt-python , since I didnt find the source. Perhaps this is the problem ?

  well, there is no libxslt-python source release. it is included in
libxml2-python . Make sure you have both libxml2 and libxslt installed *before*
compiling libxml2-python.
  It is simpler/faster/safer to use precompiled versions anyway, 

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  Wed Oct 22 06:21:38 2003
Return-Path: <kbuchcik@4commerce.de>
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 2F75218AC1
	for <xslt@gnome.org>; Wed, 22 Oct 2003 06:21:38 -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 1ACG7m-0003cQ-00
	for xslt@gnome.org; Wed, 22 Oct 2003 12:21:54 +0200
From: Kasimier Buchcik <kbuchcik@4commerce.de>
To: <xslt@gnome.org>
X-Priority: 3
Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Wed, 22 Oct 2003 12:15:46 +0200
Received: from 4commerce.de (10.1.72.2 [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id VJHJYG9V; Wed, 22 Oct 2003 12:15:45 +0200
Message-ID: <3F96596B.7020001@4commerce.de>
Date: Wed, 22 Oct 2003 12:18:19 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
X-Accept-Language: en-us, en
References: <3F9650D3.60306@4commerce.de> <20031022055523.O17879@redhat.com>
In-Reply-To: <20031022055523.O17879@redhat.com>
X-eMessageService: eMission.SMTPServer
Subject: "Re: [xslt] set/get functions for xslDebugStatus"
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="_PART_1sbua0tgp75sp60y"
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

This is a multipart message in MIME format

--_PART_1sbua0tgp75sp60y
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Daniel Veillard wrote:

> On Wed, Oct 22, 2003 at 11:41:39AM +0200, Kasimier Buchcik wrote:
>>Could the following get/set functions to set/get the xslDebugStatus=20
>>variable be added to xsltutils? In order to manipulate them from pascal,=20
>>functions are needed (well, one can set variables but not without doing=20
>>some dirty hacking).
>=20
>   okay, but send me a contextual patch (diff -c or diff -p) and preferably
> as an attachment,

Done.

Thanks,

Kasimier Buchcik


--_PART_1sbua0tgp75sp60y
Content-Type: text/plain; name="xsltutils_h.diff"
Content-Transfer-Encoding: Quoted-Printable
Content-Disposition: attachment; filename="xsltutils_h.diff"

Index: libxslt/xsltutils.h
=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
RCS file: /cvs/gnome/libxslt/libxslt/xsltutils.h,v
retrieving revision 1.37
diff -c -r1.37 xsltutils.h
*** xsltutils.h=0927 Aug 2003 10:08:03 -0000=091.37
--- xsltutils.h=0922 Oct 2003 10:06:11 -0000
***************
*** 229,234 ****
--- 229,238 ----
  typedef int (*xsltAddCallCallback) (xsltTemplatePtr templ, xmlNodePtr sour=
ce);
  typedef void (*xsltDropCallCallback) (void);
 =20
+ XSLTPUBFUN void XSLTCALL
+ =09=09xsltSetDebuggerStatus=09=09(int value);
+ XSLTPUBFUN int XSLTCALL
+ =09=09xsltGetDebuggerStatus=09=09(void);
  XSLTPUBFUN int XSLTCALL=09=09
  =09=09xsltSetDebuggerCallbacks=09(int no, void *block);
  XSLTPUBFUN int XSLTCALL=09

--_PART_1sbua0tgp75sp60y
Content-Type: text/plain; name="xsltutils_c.diff"
Content-Transfer-Encoding: Quoted-Printable
Content-Disposition: attachment; filename="xsltutils_c.diff"

Index: libxslt/xsltutils.c
=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
RCS file: /cvs/gnome/libxslt/libxslt/xsltutils.c,v
retrieving revision 1.77
diff -c -r1.77 xsltutils.c
*** xsltutils.c=093 Aug 2003 08:00:05 -0000=091.77
--- xsltutils.c=0922 Oct 2003 10:11:59 -0000
***************
*** 1732,1737 ****
--- 1732,1760 ----
  int xslDebugStatus;
 =20
  /**
+  * xsltSetDebuggerStatus:
+  * @value : the value to be set
+  *=20
+  * This function sets the value of xslDebugStatus.
+  */
+ void
+ xsltSetDebuggerStatus(int value)
+ {
+     xslDebugStatus =3D value;=09
+ }
+=20
+ /**
+  * xsltGetDebuggerStatus:=20
+  *=20
+  * This function returns the value of xslDebugStatus.
+  */
+ int
+ xsltGetDebuggerStatus(void)
+ {
+     return(xslDebugStatus);=09
+ }
+=20
+ /**
   * xsltSetDebuggerCallbacks:
   * @no : number of callbacks
   * @block : the block of callbacks

--_PART_1sbua0tgp75sp60y--


From veillard@redhat.com  Wed Oct 22 07:10:13 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id C9B6318A37
	for <xslt@gnome.org>; Wed, 22 Oct 2003 07:10:12 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9MBAT222475
	for xslt@gnome.org; Wed, 22 Oct 2003 07:10:29 -0400
Date: Wed, 22 Oct 2003 07:10:29 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: "Re: [xslt] set/get functions for xslDebugStatus"
Message-ID: <20031022071029.B4507@redhat.com>
References: <3F9650D3.60306@4commerce.de> <20031022055523.O17879@redhat.com> <3F96596B.7020001@4commerce.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3F96596B.7020001@4commerce.de>; from kbuchcik@4commerce.de on Wed, Oct 22, 2003 at 12:18: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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wed, Oct 22, 2003 at 12:18:19PM +0200, Kasimier Buchcik wrote:
> Hi,
> 
> Daniel Veillard wrote:
> 
> > On Wed, Oct 22, 2003 at 11:41:39AM +0200, Kasimier Buchcik wrote:
> >>Could the following get/set functions to set/get the xslDebugStatus 
> >>variable be added to xsltutils? In order to manipulate them from pascal, 
> >>functions are needed (well, one can set variables but not without doing 
> >>some dirty hacking).
> > 
> >   okay, but send me a contextual patch (diff -c or diff -p) and preferably
> > as an attachment,
> 
> Done.

  okay, apllied and commited, I just modified the xsltGetDebuggerStatus
comment to have a Returns line

  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 wellnhofer@aevum.de  Wed Oct 22 12:53:11 2003
Return-Path: <wellnhofer@aevum.de>
Delivered-To: xslt@gnome.org
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187])
	by mail.gnome.org (Postfix) with ESMTP id AE128180F3
	for <xslt@gnome.org>; Wed, 22 Oct 2003 12:53:10 -0400 (EDT)
Received: from [212.227.126.162] (helo=mrelayng.kundenserver.de)
	by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
	id 1ACMEh-0007Za-00
	for xslt@gnome.org; Wed, 22 Oct 2003 18:53:27 +0200
Received: from [80.128.25.188] (helo=aevum.de)
	by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1)
	id 1ACMEh-0002JJ-00
	for xslt@gnome.org; Wed, 22 Oct 2003 18:53:27 +0200
Message-ID: <3F96B606.2000505@aevum.de>
Date: Wed, 22 Oct 2003 18:53:26 +0200
From: Nick Wellnhofer <wellnhofer@aevum.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031020
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: xslt@gnome.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: [xslt] Strange interaction between <xsl:text> and whitespace in XML output
 mode
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>



Given the following stylesheet


<?xml version=3D"1.0" encoding=3D"iso-8859-1"?>

<xsl:stylesheet version=3D"1.0"=20
xmlns:xsl=3D"http://www.w3.org/1999/XSL/Transform">
<xsl:output encoding=3D"iso-8859-1" indent=3D"yes"=20
doctype-public=3D"-//W3C//DTD XHTML 1.0 Transitional//EN"=20
doctype-system=3D"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd=
"/>

<xsl:template match=3D"/">

<html xmlns=3D"http://www.w3.org/1999/xhtml" xml:lang=3D"en" lang=3D"en">=


<head>
<title>Test</title>
</head>

<body>
<table>
<tr>
   <td>1</td>
   <td>2</td>
   <td>3</td>
</tr>
<tr>
   <xsl:text> </xsl:text>
   <td>4</td>
   <td>5</td>
   <td>6</td>
</tr>
</table>
</body>

</html>

</xsl:template>

</xsl:stylesheet>


and a dummy XML document with an empty root node, I get the following res=
ult


<?xml version=3D"1.0" encoding=3D"iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"=20
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns=3D"http://www.w3.org/1999/xhtml" xml:lang=3D"en" lang=3D"en">=

   <head>
     <meta http-equiv=3D"Content-Type" content=3D"text/html;=20
charset=3Diso-8859-1" />
     <title>Test</title>
   </head>
   <body>
     <table>
       <tr>
         <td>1</td>
         <td>2</td>
         <td>3</td>
       </tr>
       <tr> <td>4</td><td>5</td><td>6</td></tr>
     </table>
   </body>
</html>


The <xsl:text> inside the second <tr> seems to disable the indented=20
formatting. Apparently all whitespace is stripped inside elements that=20
contain <xsl:text>.

This only happens in XML output mode. In HTML output mode (just use a=20
<html>-element without attributes and adjust the doctype) the result is:


<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-885=
9-1">
<title>Test</title>
</head>
<body><table>
<tr>
<td>1</td>
<td>2</td>
<td>3</td>
</tr>
<tr> <td>4</td>
<td>5</td>
<td>6</td>
</tr>
</table></body>
</html>


Is this the expected behaviour? If yes, almost all elements in an XHTML=20
result document will appear on one line which is still correct but=20
completely unreadable.

I'm not on the list, please CC me.


Nick Wellnhofer


--=20
aevum gmbh
leopoldstr. 87
80802 m=FCnchen
germany

fon: +4989 38380653
fax: +4989 38799384
wellnhofer@aevum.de
http://aevum.de/


From veillard@redhat.com  Wed Oct 22 13:22:59 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id E6817189D4
	for <xslt@gnome.org>; Wed, 22 Oct 2003 13:22:58 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9MHNET28821;
	Wed, 22 Oct 2003 13:23:14 -0400
Date: Wed, 22 Oct 2003 13:23:14 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Cc: wellnhofer@aevum.de
Subject: Re: [xslt] Strange interaction between <xsl:text> and whitespace in XML output mode
Message-ID: <20031022132314.G4507@redhat.com>
References: <3F96B606.2000505@aevum.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3F96B606.2000505@aevum.de>; from wellnhofer@aevum.de on Wed, Oct 22, 2003 at 06:53:26PM +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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wed, Oct 22, 2003 at 06:53:26PM +0200, Nick Wellnhofer wrote:
> <xsl:output encoding="iso-8859-1" indent="yes" 

you're indenting, well asking for it I don't see the problem in the 
output.

> Is this the expected behaviour? If yes, almost all elements in an XHTML 
> result document will appear on one line which is still correct but 
> completely unreadable.
blank nodes in input and in stylehseet are NOT handled the same way.
HTML serialization rules turn indent in just new line, see the archives
for explanations.
Please check first the XSLT spec, this is expected behaviour.

> I'm not on the list, please CC me.

  See http://xmlsoft.org/XSLT/bugs.html especially the first
links about the XSLt language.

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 Oct 22 18:41:47 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 350D718AB3
	for <xslt@gnome.org>; Wed, 22 Oct 2003 18:41:46 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9MMg0G27027;
	Wed, 22 Oct 2003 18:42:00 -0400
Date: Wed, 22 Oct 2003 18:41:59 -0400
From: Daniel Veillard <veillard@redhat.com>
To: Nick Wellnhofer <wellnhofer@aevum.de>
Cc: xslt@gnome.org
Subject: Re: [xslt] Strange interaction between <xsl:text> and whitespace in XML output mode
Message-ID: <20031022184159.I4507@redhat.com>
References: <3F96B606.2000505@aevum.de> <20031022132314.G4507@redhat.com> <3F96CDEE.9030900@aevum.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <3F96CDEE.9030900@aevum.de>; from wellnhofer@aevum.de on Wed, Oct 22, 2003 at 08:35:26PM +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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Wed, Oct 22, 2003 at 08:35:26PM +0200, Nick Wellnhofer wrote:
> My problem is that indenting is disabled if I use <xsl:text>. Is there a 
> specific reason?

  The XML serializer notices the text node at the same level as
the elements, concludes that the parent element content model
might be mixed-content, and as a result disable indenting
for this subtree.

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  Thu Oct 23 05:46:36 2003
Return-Path: <kbuchcik@4commerce.de>
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 0122C181D9
	for <xslt@gnome.org>; Thu, 23 Oct 2003 05:46:35 -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 1ACc3Q-0001Lk-00
	for xslt@gnome.org; Thu, 23 Oct 2003 11:46:52 +0200
From: Kasimier Buchcik <kbuchcik@4commerce.de>
To: <xslt@gnome.org>
X-Priority: 3
Received: from emission [10.254.2.2] by kisone [10.254.2.2] with SMTP eMission ESMTPServer; Thu, 23 Oct 2003 11:41:18 +0200
Received: from 4commerce.de (10.1.72.2 [10.1.72.2]) by kisone.kisnet.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id VJHJYHD8; Thu, 23 Oct 2003 11:41:18 +0200
Message-ID: <3F97A2D1.8010105@4commerce.de>
Date: Thu, 23 Oct 2003 11:43:45 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi,

I know this was asked many times before, but it seems that I still=20
cannot manage the problem; linking libxslt I get the following errors:

numbers.obj : error LNK2001: unresolved external symbol _xmlCharInRange
pattern.obj : error LNK2001: unresolved external symbol _xmlCharInRange

I added xmlCharInRange to the win32/libxml2.def.src file and the linker=20
is still unhappy. Any hints about what is still missing?

Used modules:
libxml2 2.6.0 (from cvs) & libxslt 1.0.33 (from cvs)

Kasimier


From bob@decoy.wox.org  Thu Oct 23 11:54:00 2003
Return-Path: <bob@decoy.wox.org>
Delivered-To: xslt@gnome.org
Received: from decoy.wox.org (206.180.133.7.adsl.hal-pc.org [206.180.133.7])
	by mail.gnome.org (Postfix) with ESMTP id 4864518527
	for <xslt@gnome.org>; Thu, 23 Oct 2003 11:54:00 -0400 (EDT)
Received: from quux.opus.geek (dyna039116.utdallas.edu [129.110.39.116])
	by decoy.wox.org (Postfix) with ESMTP id E57B8277DC
	for <xslt@gnome.org>; Thu, 23 Oct 2003 10:54:13 -0500 (CDT)
Received: by quux.opus.geek (Postfix, from userid 1000)
	id B081C746F7; Thu, 23 Oct 2003 10:54:12 -0500 (CDT)
Date: Thu, 23 Oct 2003 10:54:12 -0500
From: Graham Wilson <bob@decoy.wox.org>
To: xslt@gnome.org
Subject: Re: [xslt] linking of libexslt
Message-ID: <20031023155412.GA12721@quux.opus.geek>
Mail-Followup-To: xslt@gnome.org
References: <20031020034033.GA3272@quux.opus.geek> <20031020024344.L16905@redhat.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="5I6of5zJg18YgZEa"
Content-Disposition: inline
In-Reply-To: <20031020024344.L16905@redhat.com>
X-GPG-Fingerprint: A0A7 AE54 665D 6446 F2D9  81FF 8B94 031D 7F75 635F
X-GPG-Key: http://decoy.wox.org/~bob/public.asc
User-Agent: Mutt/1.5.4i
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

--5I6of5zJg18YgZEa
Content-Type: multipart/mixed; boundary="DocE+STaALJfprDB"
Content-Disposition: inline


--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 20, 2003 at 02:43:44AM -0400, Daniel Veillard wrote:
> > Also, there is code in libexslt's Makefile.am (although it is commented
> > out) which links libexslt against the recently-built libxslt, instead of
> > the system libxslt. Why is this commented out? Isn't this the right way
> > to do it?
>=20
>   Because dependancies between "being built" libraries is a problem in
> practice. It is very likely that I did so to ensure that the common case
> I can test and debug and must have working do indeed work.
>   I takes patches about configure/Makefile and shared libraries but with
> a lot of caution, because usually I get patches which work for the platfo=
rm
> or the use case for which the person was interested in but tend to break
> othert setups. It is extremely hard to assess that there is no regression
> in configure/Makefile patches.

I have applied the attached patch to the Debian libxslt package, and it
sucessfully compiles on 11 different (Linux) architectures.

--=20
gram

--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="undef.diff"
Content-Transfer-Encoding: quoted-printable

Index: configure.in
=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
--- configure.in	(revision 25)
+++ configure.in	(working copy)
@@ -386,22 +386,6 @@
 AC_SUBST(CPPFLAGS)
 AC_SUBST(LDFLAGS)
=20
-#
-# Some fun with prelinking :-(
-# try to check if there is already an installed shared lib of the same lev=
el
-#
-INSTALLED_XSLT_LIB=3D""
-if test -d $prefix
-then
-    shared_xslt_lib=3D"$prefix/lib/libxslt.so.$LIBXSLT_MAJOR_VERSION"
-    shared_xslt_la=3D"$prefix/lib/libxslt.la"
-    if test -f $shared_xslt_lib -a -f $shared_xslt_la
-    then
-	INSTALLED_XSLT_LIB=3D"-L$libdir -lxslt"
-    fi
-fi
-AC_SUBST(INSTALLED_XSLT_LIB)
-
 dnl
 dnl In build tree I use a static version with memory debug enabled
 dnl
Index: libexslt/Makefile.am
=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
--- libexslt/Makefile.am	(revision 25)
+++ libexslt/Makefile.am	(working copy)
@@ -25,10 +25,8 @@
 	libexslt.h			\
 	dynamic.c
=20
-# The following DOES NOT WORK reliably. Sorry no prelinking to uninstalled
-# yet libraries.
-# libexslt_la_LIBADD =3D $(top_builddir)/libxslt/libxslt.la $(EXTRA_LIBS)
-libexslt_la_LIBADD =3D $(INSTALLED_XSLT_LIB) $(EXTRA_LIBS)
+# The following DOES NOT WORK reliably.
+libexslt_la_LIBADD =3D $(top_builddir)/libxslt/libxslt.la $(EXTRA_LIBS)
 libexslt_la_LDFLAGS =3D -version-info @LIBEXSLT_VERSION_INFO@
=20
 man_MANS =3D libexslt.3
Index: breakpoint/Makefile.am
=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
--- breakpoint/Makefile.am	(revision 25)
+++ breakpoint/Makefile.am	(working copy)
@@ -5,7 +5,7 @@
 libxsltbreakpoint_la_SOURCES =3D 	\
 	deprecated.c
=20
-libxsltbreakpoint_la_LIBADD =3D $(INSTALLED_XSLT_LIB)  $(EXTRA_LIBS)
+libxsltbreakpoint_la_LIBADD =3D $(top_builddir)/libxslt/libxslt.la $(EXTRA=
_LIBS)
 libxsltbreakpoint_la_LDFLAGS =3D -version-info @LIBXSLTBREAK_VERSION_INFO@
=20
 clean:

--DocE+STaALJfprDB--

--5I6of5zJg18YgZEa
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: http://decoy.wox.org/~bob/public.asc

iQEVAwUBP5f5pC6fnYH5E4SWAQKRewf9GOS/5VKbFdhf+rn4ciPtcGBn5eB8GC3p
GzOevYL5/OKuSAWeKOkarrAB8KnA0cSQaIK8dN5E5fwgueF7uFKvUiXZ+Hf3V2F+
YWPZcnfGxDcT5SESl7uPQrtXxL5Hs/li+UqIBXi4HNLXUx3S5mHjUSULHID4XCN2
68zv9p6LBqVm+rqBnGbFbY3Fxbei5rjTOEKA2vt2iid3S/KfLcM4u3TZxrnTK+iy
MpQBm3exQPHgA/VgWvr9TP6SLUdXmvvO58tGOwJi2V8OO8b0ZLzEpY2uHAULbiLs
aV+Vd3e+BqNA6Ku8SAcegAbtJYt8VHAc7l0maTu8inIniT+XqxeA+g==
=Kj9J
-----END PGP SIGNATURE-----

--5I6of5zJg18YgZEa--

From veillard@redhat.com  Thu Oct 23 12:44:47 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 1539518C19
	for <xslt@gnome.org>; Thu, 23 Oct 2003 12:44:46 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9NGj1x32471
	for xslt@gnome.org; Thu, 23 Oct 2003 12:45:01 -0400
Date: Thu, 23 Oct 2003 12:45:01 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: [xslt] linking of libexslt
Message-ID: <20031023124501.U4507@redhat.com>
References: <20031020034033.GA3272@quux.opus.geek> <20031020024344.L16905@redhat.com> <20031023155412.GA12721@quux.opus.geek>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20031023155412.GA12721@quux.opus.geek>; from bob@decoy.wox.org on Thu, Oct 23, 2003 at 10:54:12AM -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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Thu, Oct 23, 2003 at 10:54:12AM -0500, Graham Wilson wrote:
> On Mon, Oct 20, 2003 at 02:43:44AM -0400, Daniel Veillard wrote:
> > > Also, there is code in libexslt's Makefile.am (although it is commented
> > > out) which links libexslt against the recently-built libxslt, instead of
> > > the system libxslt. Why is this commented out? Isn't this the right way
> > > to do it?
> > 
> >   Because dependancies between "being built" libraries is a problem in
> > practice. It is very likely that I did so to ensure that the common case
> > I can test and debug and must have working do indeed work.
> >   I takes patches about configure/Makefile and shared libraries but with
> > a lot of caution, because usually I get patches which work for the platform
> > or the use case for which the person was interested in but tend to break
> > othert setups. It is extremely hard to assess that there is no regression
> > in configure/Makefile patches.
> 
> I have applied the attached patch to the Debian libxslt package, and it
> sucessfully compiles on 11 different (Linux) architectures.

  the patch failed with breakpoint/Makefile.am in CVS where 
libxsltbreakpoint_la_LIBADD is defined as empty.
  Now the fact that it builds on a number of arches but on a similar setup
does not imply that it will build for example within an RPM build root
where prelinking is activated and where the build root is not the
install root. I think this is the answer to your initial question
  "Why is this commented out? Isn't this the right way to do it?"
  If you have a build root, the $prefix can be
    /var/tmp/libxslt-1.0.34-root/usr/and the prelinking  should still
be done against /usr/libxml/libxml2... 
  I did that patch to cope with this kind of setups I think. I'm afraid
your patch just removes it but doesn't test that this still works. And if
the result is that the package don't build out of the box on Red Hat
buildsystem, well I will have to "fix" it before any release. So I feel
quite uneasy applying your patch blindly, I will need to check it out
on various setups first making sure what I tried to handle in the first
place is not gonna come back after your removed 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 veillard@redhat.com  Thu Oct 23 18:52:26 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 0BDDB18107
	for <xslt@gnome.org>; Thu, 23 Oct 2003 18:52:26 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9NMqgA21476
	for xslt@gnome.org; Thu, 23 Oct 2003 18:52:42 -0400
Date: Thu, 23 Oct 2003 18:52:42 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: [xslt] linking of libexslt
Message-ID: <20031023185242.W4507@redhat.com>
References: <20031020034033.GA3272@quux.opus.geek> <20031020024344.L16905@redhat.com> <20031023155412.GA12721@quux.opus.geek> <20031023124501.U4507@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: <20031023124501.U4507@redhat.com>; from veillard@redhat.com on Thu, Oct 23, 2003 at 12:45:01PM -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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Thu, Oct 23, 2003 at 12:45:01PM -0400, Daniel Veillard wrote:
> On Thu, Oct 23, 2003 at 10:54:12AM -0500, Graham Wilson wrote:
> > On Mon, Oct 20, 2003 at 02:43:44AM -0400, Daniel Veillard wrote:
> > > > Also, there is code in libexslt's Makefile.am (although it is commented
> > > > out) which links libexslt against the recently-built libxslt, instead of
> > > > the system libxslt. Why is this commented out? Isn't this the right way
> > > > to do it?
> > > 
> > >   Because dependancies between "being built" libraries is a problem in
> > > practice. It is very likely that I did so to ensure that the common case
> > > I can test and debug and must have working do indeed work.
> > >   I takes patches about configure/Makefile and shared libraries but with
> > > a lot of caution, because usually I get patches which work for the platform
> > > or the use case for which the person was interested in but tend to break
> > > othert setups. It is extremely hard to assess that there is no regression
> > > in configure/Makefile patches.
> > 
> > I have applied the attached patch to the Debian libxslt package, and it
> > sucessfully compiles on 11 different (Linux) architectures.
> 
>   the patch failed with breakpoint/Makefile.am in CVS where 
> libxsltbreakpoint_la_LIBADD is defined as empty.
>   Now the fact that it builds on a number of arches but on a similar setup
> does not imply that it will build for example within an RPM build root
> where prelinking is activated and where the build root is not the
> install root. I think this is the answer to your initial question
>   "Why is this commented out? Isn't this the right way to do it?"
>   If you have a build root, the $prefix can be
>     /var/tmp/libxslt-1.0.34-root/usr/and the prelinking  should still
> be done against /usr/libxml/libxml2... 
>   I did that patch to cope with this kind of setups I think. I'm afraid
> your patch just removes it but doesn't test that this still works. And if
> the result is that the package don't build out of the box on Red Hat
> buildsystem, well I will have to "fix" it before any release. So I feel
> quite uneasy applying your patch blindly, I will need to check it out
> on various setups first making sure what I tried to handle in the first
> place is not gonna come back after your removed it !

  Okay, I managed to get sucessful rpm builds too with that change (minus
the libxsltbreakpoint_la_LIBADD), I still can't remember why I had to go though
the tortuous exercise of the INSTALLED_XSLT_LIB trick. Well it may come and
bite me later but so far the patch looks okay, so applied and commited !

  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 bob@decoy.wox.org  Thu Oct 23 20:01:51 2003
Return-Path: <bob@decoy.wox.org>
Delivered-To: xslt@gnome.org
Received: from decoy.wox.org (206.180.133.7.adsl.hal-pc.org [206.180.133.7])
	by mail.gnome.org (Postfix) with ESMTP id 4FC7C181E6
	for <xslt@gnome.org>; Thu, 23 Oct 2003 20:01:51 -0400 (EDT)
Received: from quux.opus.geek (bluesocket.utdallas.edu [129.110.39.12])
	by decoy.wox.org (Postfix) with ESMTP id 3F845277DC
	for <xslt@gnome.org>; Thu, 23 Oct 2003 19:02:04 -0500 (CDT)
Received: by quux.opus.geek (Postfix, from userid 1000)
	id 1483A746F2; Thu, 23 Oct 2003 19:02:01 -0500 (CDT)
Date: Thu, 23 Oct 2003 19:02:01 -0500
From: Graham Wilson <bob@decoy.wox.org>
To: xslt@gnome.org
Subject: Re: [xslt] linking of libexslt
Message-ID: <20031024000201.GA16332@quux.opus.geek>
Mail-Followup-To: xslt@gnome.org
References: <20031020034033.GA3272@quux.opus.geek> <20031020024344.L16905@redhat.com> <20031023155412.GA12721@quux.opus.geek> <20031023124501.U4507@redhat.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3"
Content-Disposition: inline
In-Reply-To: <20031023124501.U4507@redhat.com>
X-GPG-Fingerprint: A0A7 AE54 665D 6446 F2D9  81FF 8B94 031D 7F75 635F
X-GPG-Key: http://decoy.wox.org/~bob/public.asc
User-Agent: Mutt/1.5.4i
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 23, 2003 at 12:45:01PM -0400, Daniel Veillard wrote:
> On Thu, Oct 23, 2003 at 10:54:12AM -0500, Graham Wilson wrote:
> > I have applied the attached patch to the Debian libxslt package, and it
> > sucessfully compiles on 11 different (Linux) architectures.
>=20
>   the patch failed with breakpoint/Makefile.am in CVS where=20
> libxsltbreakpoint_la_LIBADD is defined as empty.

Is libxsltbreakpoint not supposed to be linked against libxslt?

>   Now the fact that it builds on a number of arches but on a similar setup
> does not imply that it will build for example within an RPM build root
> where prelinking is activated and where the build root is not the
> install root. I think this is the answer to your initial question
>   "Why is this commented out? Isn't this the right way to do it?"
>   If you have a build root, the $prefix can be
>     /var/tmp/libxslt-1.0.34-root/usr/and the prelinking  should still
> be done against /usr/libxml/libxml2...=20

Hmm... Debian packages are built in a similar way. The files are
installed into a temporary directory, and then are copied into the
package files.=20

Maybe this is why the patch worked alright. Anyways, thanks for testing
and applying it.

--=20
gram

--r5Pyd7+fXNt84Ff3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: http://decoy.wox.org/~bob/public.asc

iQEVAwUBP5hr+S6fnYH5E4SWAQLrYAgAivibwdEFleDY2sd1y1xDk9DBpAIdeHwn
qb24axM4sYUSxG8DCToNAPb6K+lcNWAA+mze7vGj3WwKrJli+N/Qswl2H5YFNaJu
vy9y9/6vZZdRwx2wd3D/FVoPrxdi0uAVcxeQVY8y0dXa37ClrZIlbTJDdp6fRFtv
DrExEFrCOrtsgpkASz0kaRJrVaDBZM0RVCx7NtCOjOzj/CWJ9AE+HOKqt/yWcX7L
ydy0vEuFKXp6e6uhppoFRLbb6NB+OZxg+83tA8Zcx6LoaPJhDqChlBDldGdevflR
Tgl9Ycc8q+FbilA2NXOmqhrmrYMa41WRCPYE+dlBqm1dtFBO9Kr6Pg==
=Yapw
-----END PGP SIGNATURE-----

--r5Pyd7+fXNt84Ff3--

From veillard@redhat.com  Fri Oct 24 05:23:48 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 0D527181F6
	for <xslt@gnome.org>; Fri, 24 Oct 2003 05:23:48 -0400 (EDT)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9O9O5E21011
	for xslt@gnome.org; Fri, 24 Oct 2003 05:24:05 -0400
Date: Fri, 24 Oct 2003 05:24:05 -0400
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: [xslt] linking of libexslt
Message-ID: <20031024052404.Z4507@redhat.com>
References: <20031020034033.GA3272@quux.opus.geek> <20031020024344.L16905@redhat.com> <20031023155412.GA12721@quux.opus.geek> <20031023124501.U4507@redhat.com> <20031024000201.GA16332@quux.opus.geek>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20031024000201.GA16332@quux.opus.geek>; from bob@decoy.wox.org on Thu, Oct 23, 2003 at 07:02:01PM -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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Thu, Oct 23, 2003 at 07:02:01PM -0500, Graham Wilson wrote:
> On Thu, Oct 23, 2003 at 12:45:01PM -0400, Daniel Veillard wrote:
> >   the patch failed with breakpoint/Makefile.am in CVS where 
> > libxsltbreakpoint_la_LIBADD is defined as empty.
> 
> Is libxsltbreakpoint not supposed to be linked against libxslt?

  This is a deprecated library, it's there only for pure ABI compat,
it will actually disapear in the next big update, maybe next release.

> >   Now the fact that it builds on a number of arches but on a similar setup
> > does not imply that it will build for example within an RPM build root
> > where prelinking is activated and where the build root is not the
> > install root. I think this is the answer to your initial question
> >   "Why is this commented out? Isn't this the right way to do it?"
> >   If you have a build root, the $prefix can be
> >     /var/tmp/libxslt-1.0.34-root/usr/and the prelinking  should still
> > be done against /usr/libxml/libxml2... 
> 
> Hmm... Debian packages are built in a similar way. The files are
> installed into a temporary directory, and then are copied into the
> package files. 

  Okay, good to know. Well then I can't remember what kind of troubles I
faced forcing me to do this...

> Maybe this is why the patch worked alright. Anyways, thanks for testing
> and applying it.

  No problem, I'm just cautious about everything related to the build,
teh effect of changes at the code level are relatively easy to check and
test, but for the build it's a shoot in the dark.

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 wellnhofer@aevum.de  Wed Oct 22 14:35:17 2003
Return-Path: <wellnhofer@aevum.de>
Delivered-To: xslt@gnome.org
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.189])
	by mail.gnome.org (Postfix) with ESMTP id 87277181DD
	for <xslt@gnome.org>; Wed, 22 Oct 2003 14:35:17 -0400 (EDT)
Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de)
	by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
	id 1ACNpQ-0003Km-00; Wed, 22 Oct 2003 20:35:28 +0200
Received: from [80.128.25.188] (helo=aevum.de)
	by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1)
	id 1ACNpP-0005l2-00; Wed, 22 Oct 2003 20:35:28 +0200
Message-ID: <3F96CDEE.9030900@aevum.de>
Date: Wed, 22 Oct 2003 20:35:26 +0200
From: Nick Wellnhofer <wellnhofer@aevum.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031020
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: veillard@redhat.com
Cc: xslt@gnome.org
Subject: Re: [xslt] Strange interaction between <xsl:text> and whitespace
 in XML output mode
References: <3F96B606.2000505@aevum.de> <20031022132314.G4507@redhat.com>
In-Reply-To: <20031022132314.G4507@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>


Daniel Veillard wrote:
> On Wed, Oct 22, 2003 at 06:53:26PM +0200, Nick Wellnhofer wrote:
>=20
>><xsl:output encoding=3D"iso-8859-1" indent=3D"yes"=20
>=20
>=20
> you're indenting, well asking for it I don't see the problem in the=20
> output.

I know the output is correct as per the XSLT spec.

My problem is that indenting is disabled if I use <xsl:text>. Is there a =

specific reason?

Nick



--=20
aevum gmbh
leopoldstr. 87
80802 m=FCnchen
germany

fon: +4989 38380653
fax: +4989 38799384
wellnhofer@aevum.de
http://aevum.de/


From justin.fletcher@ntlworld.com  Sun Oct 26 13:51:41 2003
Return-Path: <justin.fletcher@ntlworld.com>
Delivered-To: xslt@gnome.org
Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41])
	by mail.gnome.org (Postfix) with ESMTP id 09B1418465
	for <xslt@gnome.org>; Sun, 26 Oct 2003 13:51:41 -0500 (EST)
Received: from buttercup.gerph.org ([217.137.22.57])
          by mta01-svc.ntlworld.com
          (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP
          id <20031026185157.JXSH12291.mta01-svc.ntlworld.com@buttercup.gerph.org>
          for <xslt@gnome.org>; Sun, 26 Oct 2003 18:51:57 +0000
Received: from zeus (zeus.gerph.org [192.168.0.50])
	by buttercup.gerph.org (Postfix) with SMTP id 33EBCF5637
	for <xslt@gnome.org>; Sun, 26 Oct 2003 18:51:52 +0000 (GMT)
Date: Sun, 26 Oct 2003 18:42:27 GMT
From: Justin Fletcher <justin.fletcher@ntlworld.com>
To: xslt@gnome.org
Message-ID: <a9d791474c.Justin@gerph.movspclr.co.uk>
X-Organization: MOVSPCLR
User-Agent: Messenger-Pro/2.59beta (Newsbase/0.68) (RISC-OS/4.37) POPstar/2.03
X-Comment: A hollow voice whispers diaxos
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Posting-Agent: RISC OS Newsbase 0.68
Subject: [xslt] libxslt 1.0.33 + libxml2 2.6.0 'IS_BLANK' 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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hiya,

I'm building libxslt 1.0.33 against libxml2 2.6.0. I get a fatal error from
the compiler whilst compiling libxslt/xslt.c :

"c.xslt", line 66: Error: differing redefinition of #define macro IS_BLANK

xslt.c has the macro declared :

#define IS_BLANK(c) (((c) == 0x20) || ((c) == 0x09) || ((c) == 0xA) ||	\
                     ((c) == 0x0D))

However, xslt.c also includes libxml/parserInternals.h which has the
definition :

#define IS_BLANK(c)  xmlIsBlankQ(c)


I'm not sure what the behaviour of GCC is on such redefinitions, but the
Norcroft compiler (which is used for my RISC OS builds) treats a differing
redefinition as a fatal error. Such use must be #undef'd before the new
definition can be used.

Is this actually a mistake that I've made, or is this redefinition not a
problem for GCC ?

-- 
Gerph {djf0-.3w6e2w2.226,6q6w2q2,2.3,2m4}
URL: http://www.movspclr.co.uk/
... Eyes to the heavens, screaming at the sky;
    Trying to send you messages, but choking on goodbye.

From igor@zlatkovic.com  Sun Oct 26 15:23:17 2003
Return-Path: <igor@zlatkovic.com>
Delivered-To: xslt@gnome.org
Received: from mail.zlatkovic.com (spell.zlatkovic.com [62.75.159.112])
	by mail.gnome.org (Postfix) with ESMTP id 5CCAA1818B
	for <xslt@gnome.org>; Sun, 26 Oct 2003 15:23:17 -0500 (EST)
Received: from raven (p5080FB34.dip.t-dialin.net [80.128.251.52])
	(authenticated bits=0)
	by mail.zlatkovic.com (8.12.8/8.12.8) with ESMTP id h9QKNWt6020877
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <xslt@gnome.org>; Sun, 26 Oct 2003 21:23:34 +0100
Message-ID: <000801c39bff$0ad40a20$352ffea9@raven>
From: "Igor Zlatkovic" <igor@zlatkovic.com>
To: <xslt@gnome.org>
References: <a9d791474c.Justin@gerph.movspclr.co.uk>
Subject: Re: [xslt] libxslt 1.0.33 + libxml2 2.6.0 'IS_BLANK' problem
Date: Sun, 26 Oct 2003 21:23:37 +0100
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

> Hiya,
>
> I'm building libxslt 1.0.33 against libxml2 2.6.0. I get a fatal error
from
> the compiler whilst compiling libxslt/xslt.c :
>
> "c.xslt", line 66: Error: differing redefinition of #define macro IS_BLANK
>
> xslt.c has the macro declared :
>
> #define IS_BLANK(c) (((c) == 0x20) || ((c) == 0x09) || ((c) == 0xA) || \
>                      ((c) == 0x0D))
>
> However, xslt.c also includes libxml/parserInternals.h which has the
> definition :
>
> #define IS_BLANK(c)  xmlIsBlankQ(c)
>
>
> I'm not sure what the behaviour of GCC is on such redefinitions, but the
> Norcroft compiler (which is used for my RISC OS builds) treats a differing
> redefinition as a fatal error. Such use must be #undef'd before the new
> definition can be used.
>
> Is this actually a mistake that I've made, or is this redefinition not a
> problem for GCC ?

Probably not. I know that MS compiler issues a warning on that one and
continues.

However, perhaps this should be handled. Either xmlsec or xsldbg has the
same somewhere in the code, I cannot remember which it was.

I suggest that IS_BLANK from libxml be used everywhere. If there are no
objections, I'll commit what I can.

Ciao,
Igor


From wbrack@mmm.com.hk  Sun Oct 26 19:50:39 2003
Return-Path: <wbrack@mmm.com.hk>
Delivered-To: xslt@gnome.org
Received: from delightful.com.hk (adsl-63-204-84-206.dsl.sktn01.pacbell.net [63.204.84.206])
	by mail.gnome.org (Postfix) with ESMTP id DAFE7182F1
	for <xslt@gnome.org>; Sun, 26 Oct 2003 19:50:37 -0500 (EST)
Received: from delightful.com.hk (localhost [127.0.0.1])
	by delightful.com.hk (8.12.9/8.12.9) with SMTP id h9R0osVq026513
	for <xslt@gnome.org>; Sun, 26 Oct 2003 16:50:55 -0800
Received: from 219.78.248.18
        (SquirrelMail authenticated user wbrack)
        by www.delightful.com.hk with HTTP;
        Mon, 27 Oct 2003 08:50:55 +0800 (HKT)
Message-ID: <3068.219.78.248.18.1067215855.squirrel@www.delightful.com.hk>
In-Reply-To: <000801c39bff$0ad40a20$352ffea9@raven>
References: <a9d791474c.Justin@gerph.movspclr.co.uk>
    <000801c39bff$0ad40a20$352ffea9@raven>
Date: Mon, 27 Oct 2003 08:50:55 +0800 (HKT)
Subject: Re: [xslt] libxslt 1.0.33 + libxml2 2.6.0 'IS_BLANK' problem
From: "William M. Brack" <wbrack@mmm.com.hk>
To: xslt@gnome.org
User-Agent: SquirrelMail/1.4.1
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Igor Zlatkovic said:
>> Hiya,
>>
>> I'm building libxslt 1.0.33 against libxml2 2.6.0. I get a fatal
>> error
> from
>> the compiler whilst compiling libxslt/xslt.c :
>>
>> "c.xslt", line 66: Error: differing redefinition of #define macro
>> IS_BLANK
>>
>> xslt.c has the macro declared :
>>
>> #define IS_BLANK(c) (((c) == 0x20) || ((c) == 0x09) || ((c) ==
>> 0xA) || \
>>                      ((c) == 0x0D))
>>
>> However, xslt.c also includes libxml/parserInternals.h which has
>> the
>> definition :
>>
>> #define IS_BLANK(c)  xmlIsBlankQ(c)
>>
>>
>> I'm not sure what the behaviour of GCC is on such redefinitions,
>> but the
>> Norcroft compiler (which is used for my RISC OS builds) treats a
>> differing
>> redefinition as a fatal error. Such use must be #undef'd before
>> the new
>> definition can be used.
>>
>> Is this actually a mistake that I've made, or is this redefinition
>> not a
>> problem for GCC ?
>
> Probably not. I know that MS compiler issues a warning on that one
> and
> continues.
>
> However, perhaps this should be handled. Either xmlsec or xsldbg has
> the
> same somewhere in the code, I cannot remember which it was.
>
> I suggest that IS_BLANK from libxml be used everywhere. If there are
> no
> objections, I'll commit what I can.
>
> Ciao,
> Igor

First, with regard to GCC, this "redefinition" only results in a
warning.  Second, there is a problem with using the definition from
parserInternals.h.  This problem comes from changes in version 2.6.0
of libxml2, where all of the IS_XXXX macros have been changed (for
better performance) to use the new range routines.  Eventually
similar enhancements will be made to libxslt, but there is some risk
to ABI compatibility (since there must be a hard dependency on
linking to libxml2-2.6.0 or greater).  I believe that currently the
dependency is only for 2.5.10.

So, the "proper" fix is to do as Igor suggests, and just remove the
definition from xslt.c, but in order to maintain ABI compatibility,
for now we should just #undef it.  I'll do that now, and commit it
to CVS.

Sorry for the problem - if I knew it would break any compilation I
would have fixed it previously.

Regards,

Bill

From alex@shelter.nu  Fri Oct 31 06:30:34 2003
Return-Path: <alex@shelter.nu>
Delivered-To: xslt@gnome.org
Received: from vvask02.itweb.no (unknown [213.236.233.199])
	by mail.gnome.org (Postfix) with ESMTP id 21C8D186EF
	for <xslt@gnome.org>; Fri, 31 Oct 2003 06:30:34 -0500 (EST)
Received: from shelter.nu ([213.236.233.200]) by vvask02 with InterScan Messaging Security Suite; Fri, 31 Oct 2003 12:44:19 +0100
Received: from shelter [203.51.32.41] by shelter.nu with ESMTP
  (SMTPD32-8.03) id A8742620040; Fri, 31 Oct 2003 12:33:08 +0100
To: xslt@gnome.org
From: Alexander Johannesen <alex@shelter.nu>
Organization: shelter.nu
Content-Type: text/plain; format=flowed; charset=iso-8859-15
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Date: Fri, 31 Oct 2003 22:32:45 +1100
Message-ID: <oprxwnovy8epv7f3@mail.shelter.nu>
User-Agent: Opera7.20/Win32 M2 build 3124
Subject: [xslt] JavaScript support in 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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Hi,

Searched high and low (Google, to be exact) for information on how or
if libxslt has got support for JavaScript, but found some messages
indicating yes and some indicating no. With the Sablotron parser there
were builds that had JacaScript 1.5 (Mozilla) compiled in, and I
could use that to transform and fiddle with my data as part of the
transformation. Needless to say, as my main project uses quite a bit
of JavaScript for things not really meant to be done in XSLT, I'm
wondering if it is supported or if it will be? And if, how?


Thanks and kind regards,

Alexander
-- 
___________________ ______________________ _____________________________
                    |                      |
http://shelter.nu/ | alex at shelter . nu | http://shelter.nu/xsiteable/
___________________|______________________|_____________________________


From veillard@redhat.com  Fri Oct 31 06:55:00 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 3D17018861
	for <xslt@gnome.org>; Fri, 31 Oct 2003 06:55:00 -0500 (EST)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9VBtIs16144
	for xslt@gnome.org; Fri, 31 Oct 2003 06:55:18 -0500
Date: Fri, 31 Oct 2003 06:55:18 -0500
From: Daniel Veillard <veillard@redhat.com>
To: xslt@gnome.org
Subject: Re: [xslt] JavaScript support in libxslt?
Message-ID: <20031031065518.H25702@redhat.com>
References: <oprxwnovy8epv7f3@mail.shelter.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <oprxwnovy8epv7f3@mail.shelter.nu>; from alex@shelter.nu on Fri, Oct 31, 2003 at 10:32:45PM +1100
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Fri, Oct 31, 2003 at 10:32:45PM +1100, Alexander Johannesen wrote:
> Hi,
> 
> Searched high and low (Google, to be exact) for information on how or
> if libxslt has got support for JavaScript, but found some messages
> indicating yes and some indicating no. With the Sablotron parser there
> were builds that had JacaScript 1.5 (Mozilla) compiled in, and I
> could use that to transform and fiddle with my data as part of the
> transformation. Needless to say, as my main project uses quite a bit
> of JavaScript for things not really meant to be done in XSLT, I'm
> wondering if it is supported or if it will be? And if, how?

  Not supported. There is support to write extension functions and
elements in Python, but not in JavaScript. The problem is mostly:
   - technical: adding a hard dependancy on mozilla or javascript package
     is ruled out, using dynamic loading, if portable, then why not.
   - philosophical: as you experienced, as soon as you mix the XSLT
     language and another one it's not portable anymore, it really
     depends how it is done, and so far I'm not too convinced by any
     attempt like xsl:script, using extension functions and elements
     on the other hand is relatively clean.

 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 alex@shelter.nu  Fri Oct 31 15:11:07 2003
Return-Path: <alex@shelter.nu>
Delivered-To: xslt@gnome.org
Received: from vvask02.itweb.no (unknown [213.236.233.199])
	by mail.gnome.org (Postfix) with ESMTP id 7AC1D18279
	for <xslt@gnome.org>; Fri, 31 Oct 2003 15:11:06 -0500 (EST)
Received: from shelter.nu ([213.236.233.200]) by vvask02 with InterScan Messaging Security Suite; Fri, 31 Oct 2003 21:24:52 +0100
Received: from shelter [203.51.32.41] by shelter.nu with ESMTP
  (SMTPD32-8.03) id A2732A00072; Fri, 31 Oct 2003 21:13:39 +0100
To: xslt@gnome.org
Subject: Re: [xslt] JavaScript support in libxslt?
References: <oprxwnovy8epv7f3@mail.shelter.nu> <20031031065518.H25702@redhat.com>
Message-ID: <oprxxbr6rcepv7f3@mail.shelter.nu>
From: Alexander Johannesen <alex@shelter.nu>
Organization: shelter.nu
Content-Type: text/plain; format=flowed; charset=iso-8859-15
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Date: Sat, 01 Nov 2003 07:13:08 +1100
In-Reply-To: <20031031065518.H25702@redhat.com>
User-Agent: Opera7.20/Win32 M2 build 3124
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

Thanks for the swift reply, Daniel,

Daniel Veillard <veillard@redhat.com> wrote:
>    - technical: adding a hard dependancy on mozilla or javascript 
>      package is ruled out, using dynamic loading, if portable, then
>      why not.

So it is not supported, and no one is planning such a thing. The thing
is that since PHP now comes with LibXML istead of Sablotron, and all
those applicatons can't be used for PHP 5.0, unless re-compiled for
the Sablotron parser. Just a hassle for us who don't distribute PHP
with our applications; we can't reply on people simply installing PHP
themselves cleanly anymore.

>    - philosophical: as you experienced, as soon as you mix the XSLT
>      language and another one it's not portable anymore, it really
>      depends how it is done, and so far I'm not too convinced by any
>      attempt like xsl:script, using extension functions and elements
>      on the other hand is relatively clean.

Oh, there are many ways of doing things, of course, but having JS as
part of the transformation in xsl:script is sometimes a godsent when
you're dealing with rapid development and prototyping, and of course
re-distribution of applications; it dramatically cuts down on install
and configure problems, for one. And, as you already have support for
Python, why not a more general link-in to support others? Sablotron
has iconv and js1.5 support across several platforms, so it can be done.

Anyways, thanks for the reply.


Alexander
-- 
___________________ ______________________ _____________________________
                    |                      |
http://shelter.nu/ | alex at shelter . nu | http://shelter.nu/xsiteable/
___________________|______________________|_____________________________


From veillard@redhat.com  Fri Oct 31 18:11:19 2003
Return-Path: <veillard@redhat.com>
Delivered-To: xslt@gnome.org
Received: from devserv.devel.redhat.com (pix-525-pool.redhat.com [66.187.233.200])
	by mail.gnome.org (Postfix) with ESMTP id 963BE181ED
	for <xslt@gnome.org>; Fri, 31 Oct 2003 18:11:19 -0500 (EST)
Received: (from veillard@localhost)
	by devserv.devel.redhat.com (8.11.6/8.11.0) id h9VNBZW02770;
	Fri, 31 Oct 2003 18:11:35 -0500
Date: Fri, 31 Oct 2003 18:11:35 -0500
From: Daniel Veillard <veillard@redhat.com>
To: alex@shelter.nu
Cc: xslt@gnome.org
Subject: Re: [xslt] JavaScript support in libxslt?
Message-ID: <20031031181135.C1428@redhat.com>
References: <oprxwnovy8epv7f3@mail.shelter.nu> <20031031065518.H25702@redhat.com> <oprxxbr6rcepv7f3@mail.shelter.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <oprxxbr6rcepv7f3@mail.shelter.nu>; from alex@shelter.nu on Sat, Nov 01, 2003 at 07:13:08AM +1100
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: <mailto:xslt-request@gnome.org?subject=help>
List-Post: <mailto:xslt@gnome.org>
List-Subscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=subscribe>
List-Id: The Gnome XSLT library mailing-list <xslt.gnome.org>
List-Unsubscribe: <http://mail.gnome.org/mailman/listinfo/xslt>,
	<mailto:xslt-request@gnome.org?subject=unsubscribe>
List-Archive: <http://mail.gnome.org/archives/xslt/>

On Sat, Nov 01, 2003 at 07:13:08AM +1100, Alexander Johannesen wrote:
> Thanks for the swift reply, Daniel,
> 
> Daniel Veillard <veillard@redhat.com> wrote:
> >    - technical: adding a hard dependancy on mozilla or javascript 
> >      package is ruled out, using dynamic loading, if portable, then
> >      why not.
> 
> So it is not supported, and no one is planning such a thing. The thing
> is that since PHP now comes with LibXML istead of Sablotron, and all
> those applicatons can't be used for PHP 5.0, unless re-compiled for
> the Sablotron parser. Just a hassle for us who don't distribute PHP
> with our applications; we can't reply on people simply installing PHP
> themselves cleanly anymore.

  Well I did look into this a bit some time ago, and at the time decided
it was more of a hassle than a gain. Maybe from a PHP perspective things
are different.

> >    - philosophical: as you experienced, as soon as you mix the XSLT
> >      language and another one it's not portable anymore, it really
> >      depends how it is done, and so far I'm not too convinced by any
> >      attempt like xsl:script, using extension functions and elements
> >      on the other hand is relatively clean.
> 
> Oh, there are many ways of doing things, of course, but having JS as
> part of the transformation in xsl:script is sometimes a godsent when
> you're dealing with rapid development and prototyping, and of course

Well xsl:script never got blessed as part of the standard, precisely because
it was really bad in term of interoperability. Implementing extension functions
is far cleaner. If you trade long-term maintainance and conformance to
the spec for rapid prototyping, that's fine, but you know that that part
of the trade-off will bite you in the future, don't be too surprised or
angry when this happen. xsl:script only shortly made it into the 1.1 working
draft and died quite fast, it's not present in 2.0, you'd better not rely
on this.

> re-distribution of applications; it dramatically cuts down on install
> and configure problems, for one. And, as you already have support for
> Python, why not a more general link-in to support others? Sablotron
> has iconv and js1.5 support across several platforms, so it can be done.

  I have cross platform support for iconv when present. For Python 
the support comes from the python bindings, not from the library itself
it's very different from adding a hard requirement from libxml2 or libxslt
to python, there is none, there is just another brick which provides
libxslt support from python. If you want to provide one for Javascript
in that way this is fine by me, 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/