When I attempt to use xsltproc here are the results; compilation error: file input.xsl line 25 element template xsltCompilePattern : failed to compile '@*[local-name()='name']' The result using xalan is what I had hoped for: My Car Models: Rabbit Tundra Mini The Manufacturers: Volkswagen Toyota Bavarian Motor Works If I change the input xml doc so that name is an element instead of an attribute and change my xsl doc to select for this, that works. So, instead of this; I have this; xsltproc will select the names of the models and manufacturers correctly. Does libxslt implement this functionality different than Xalan (if so can someone tell me the proper usage) or is this a bug? The release of xsltproc I am using: Using libxml 20426, libxslt 10022 and libexslt 713 xsltproc was compiled against libxml 20426, libxslt 10022 and libexslt 713 libxslt 10022 was compiled against libxml 20426 libexslt 713 was compiled against libxml 20426 Thanks for your help, Susan Cline --------------------------------- Do you Yahoo!? HotJobs - Search new jobs daily now --0-999316785-1036451987=:35506 Content-Type: text/html; charset=us-ascii

Hello,

I'm attempting to use the local-name() function to match attributes with the same name in different namespaces in an xml document. The pattern I am attempting to use succeeds using the Xalan processor, but using xsltproc it gives me an error.

Here is the xml doc:

<?xml version="1.0" encoding="UTF-8"?>
<car:cars xmlns:car="http://www.example.com/xmlns/car"
          xmlns:m="http://www.example.com/xmlns/manufacturer">
<car:models>
    <car:model car:name="Rabbit" m:id="VW" car:year="1984" />
    <car:model car:name="Tundra" m:id="TY" car:year="2000" />
    <car:model car:name="Mini" m:id="BM" car:year="2003" />
</car:models>
<m:manufacturers>
    <m:manufacturer m:id="VW" m:name="Volkswagen" m:country="Germany" />
    <m:manufacturer m:id="TY" m:name="Toyota" m:country="Japan" />
    <m:manufacturer m:id="BM" m:name="Bavarian Motor Works" m:country="Germany"/>
</m:manufacturers>
</car:cars>

Here is the xsl doc:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:car="http://www.example.com/xmlns/car"
xmlns:manu="http://www.example.com/xmlns/manufacturer">

<xsl:output method="text" encoding="UTF-8" />
<xsl:strip-space elements="*" />

<xsl:template match="/">
<xsl:apply-templates />
</xsl:template>

<xsl:template match="car:models">
    <xsl:text>My Car Models:
</xsl:text>
    <xsl:apply-templates select="car:model/@car:name"></xsl:apply-templates>
    <xsl:text>
</xsl:text>
</xsl:template>

<xsl:template match="manu:manufacturers">
<xsl:text>The Manufacturers:
</xsl:text>
<xsl:apply-templates select="manu:manufacturer/@manu:name"></xsl:apply-templ
ates>
</xsl:template>

<xsl:template match="@*[local-name()='name']">
<xsl:value-of select="." />
<xsl:text>
</xsl:text>
</xsl:template>

</xsl:stylesheet>

When I attempt to use xsltproc here are the results;

compilation error: file input.xsl line 25 element template

xsltCompilePattern : failed to compile '@*[local-name()='name']'

The result using xalan is what I had hoped for:

My Car Models:
Rabbit
Tundra
Mini

The Manufacturers:
Volkswagen
Toyota
Bavarian Motor Works

If I change the input xml doc so that name is an element instead of an attribute and change my xsl doc to select for this, that works. So, instead of this;

<xsl:template match="@*[local-name()='name']">

I have this;

<xsl:template match="*[local-name()='name']">

xsltproc will select the names of the models and manufacturers correctly.

Does libxslt implement this functionality different than Xalan (if so can someone tell me the proper usage) or is this a bug?

The release of xsltproc I am using:

Using libxml 20426, libxslt 10022 and libexslt 713
xsltproc was compiled against libxml 20426, libxslt 10022 and libexslt 713
libxslt 10022 was compiled against libxml 20426
libexslt 713 was compiled against libxml 20426

Thanks for your help,

Susan Cline

Do you Yahoo!?
HotJobs - Search new jobs daily now --0-999316785-1036451987=:35506-- From home4slc@yahoo.com Mon Nov 4 19:06:16 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from web14410.mail.yahoo.com (web14410.mail.yahoo.com [216.136.173.221]) by mail.gnome.org (Postfix) with SMTP id 99710180E9 for ; Mon, 4 Nov 2002 19:06:15 -0500 (EST) Message-ID: <20021105000614.7063.qmail@web14410.mail.yahoo.com> Received: from [32.97.110.142] by web14410.mail.yahoo.com via HTTP; Mon, 04 Nov 2002 16:06:14 PST Date: Mon, 4 Nov 2002 16:06:14 -0800 (PST) From: Susan Cline To: xslt@gnome.org Cc: home4slc@yahoo.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-475318687-1036454774=:7021" Subject: [xslt] cdata-section-elements not working correctly? Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: --0-475318687-1036454774=:7021 Content-Type: text/plain; charset=us-ascii Hi, I've tried using cdata-section-elements in the way I believe it is intended to be used but I don't think I am getting the correct results. XML doc: X < Y XSL:

Result using xsltproc: X < Y Result using saxon: Result using Xalan: I believe the correct way to output the second element is to contain CDATA as is done using saxon and xalan. Is this a bug? Thanks, Susan Cline --------------------------------- Do you Yahoo!? HotJobs - Search new jobs daily now --0-475318687-1036454774=:7021 Content-Type: text/html; charset=us-ascii

Hi,

I've tried using cdata-section-elements in the way I believe it is intended to be used but I don't think I am getting the correct results.

XML doc:

<?xml version="1.0" encoding="utf-8"?>
<operators>
<compare><![CDATA[X < Y]]></compare>
<compare>X < Y</compare>
</operators>

XSL:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:output cdata-section-elements="compare" />

<xsl:template match="/">
<xsl:copy-of select="." />
</xsl:template>
</xsl:stylesheet>

Result using xsltproc:

<?xml version="1.0"?>
<operators>
<compare><![CDATA[X < Y]]></compare>
<compare>X < Y</compare>
</operators>

Result using saxon:

<?xml version="1.0" encoding="utf-8"?><operators>
<compare><![CDATA[X < Y]]></compare>
<compare><![CDATA[X < Y]]></compare>
</operators>

Result using Xalan:

<?xml version="1.0" encoding="UTF-8"?>
<operators>
<compare><![CDATA[X < Y]]></compare>
<compare><![CDATA[X < Y]]></compare>
</operators>

I believe the correct way to output the second <compare> element is to contain CDATA as is done using saxon and xalan.

Is this a bug?

Thanks,

Susan Cline

Do you Yahoo!?
HotJobs - Search new jobs daily now --0-475318687-1036454774=:7021-- From home4slc@yahoo.com Thu Nov 7 13:14:08 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from web14401.mail.yahoo.com (web14401.mail.yahoo.com [216.136.174.58]) by mail.gnome.org (Postfix) with SMTP id 26722184F9 for ; Thu, 7 Nov 2002 13:14:08 -0500 (EST) Message-ID: <20021107181407.10998.qmail@web14401.mail.yahoo.com> Received: from [63.205.172.122] by web14401.mail.yahoo.com via HTTP; Thu, 07 Nov 2002 10:14:07 PST Date: Thu, 7 Nov 2002 10:14:07 -0800 (PST) From: Susan Cline To: xslt@gnome.org Cc: home4slc@yahoo.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-3993272-1036692847=:7547" Subject: [xslt] CDATA-section-elements? Is this a 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: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: --0-3993272-1036692847=:7547 Content-Type: text/plain; charset=us-ascii Hi, I posted the below message earlier this week. Does anyone know if this is a bug? Thanks, Susan ***************************************************************** Hi, I've tried using cdata-section-elements in the way I believe it is intended to be used but I don't think I am getting the correct results. XML doc: X < Y XSL:

Result using xsltproc: X < Y Result using saxon: Result using Xalan: I believe the correct way to output the second element is to contain CDATA as is done using saxon and xalan. Is this a bug? Thanks, Susan Cline --------------------------------- Do you Yahoo!? U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD --0-3993272-1036692847=:7547 Content-Type: text/html; charset=us-ascii

Hi,

I posted the below message earlier this week. Does anyone know if this is a bug?

Thanks,

Susan *****************************************************************

Hi,

I've tried using cdata-section-elements in the way I believe it is intended to be used but I don't think I am getting the correct results.

XML doc:

<?xml version="1.0" encoding="utf-8"?>
<operators>
<compare><![CDATA[X < Y]]></compare>
<compare>X < Y</compare>
</operators>

XSL:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:output cdata-section-elements="compare" />

<xsl:template match="/">
<xsl:copy-of select="." />
</xsl:template>
</xsl:stylesheet>

Result using xsltproc:

<?xml version="1.0"?>
<operators>
<compare><![CDATA[X < Y]]></compare>
<compare>X < Y</compare>
</operators>

Result using saxon:

<?xml version="1.0" encoding="utf-8"?><operators>
<compare><![CDATA[X < Y]]></compare>
<compare><![CDATA[X < Y]]></compare>
</operators>

Result using Xalan:

<?xml version="1.0" encoding="UTF-8"?>
<operators>
<compare><![CDATA[X < Y]]></compare>
<compare><![CDATA[X < Y]]></compare>
</operators>

I believe the correct way to output the second <compare> element is to contain CDATA as is done using saxon and xalan.

Is this a bug?

Thanks,

Susan Cline

Do you Yahoo!?
U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD --0-3993272-1036692847=:7547-- From home4slc@yahoo.com Thu Nov 7 13:16:11 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from web14401.mail.yahoo.com (web14401.mail.yahoo.com [216.136.174.58]) by mail.gnome.org (Postfix) with SMTP id 9971418660 for ; Thu, 7 Nov 2002 13:16:10 -0500 (EST) Message-ID: <20021107181610.11356.qmail@web14401.mail.yahoo.com> Received: from [63.205.172.122] by web14401.mail.yahoo.com via HTTP; Thu, 07 Nov 2002 10:16:10 PST Date: Thu, 7 Nov 2002 10:16:10 -0800 (PST) From: Susan Cline To: xslt@gnome.org Cc: home4slc@yahoo.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1072373250-1036692970=:7547" Subject: [xslt] local-name() and attributes Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: --0-1072373250-1036692970=:7547 Content-Type: text/plain; charset=us-ascii Hi, I haven't heard from anyone - can anyone comment on if this is a bug or not? Thanks, Susan ********************************* Hello, I'm attempting to use the local-name() function to match attributes with the same name in different namespaces in an xml document. The pattern I am attempting to use succeeds using the Xalan processor, but using xsltproc it gives me an error. Here is the xml doc: Here is the xsl doc:

My Car Models:

The Manufacturers:

When I attempt to use xsltproc here are the results; compilation error: file input.xsl line 25 element template xsltCompilePattern : failed to compile '@*[local-name()='name']' The result using xalan is what I had hoped for: My Car Models: Rabbit Tundra Mini The Manufacturers: Volkswagen Toyota Bavarian Motor Works If I change the input xml doc so that name is an element instead of an attribute and change my xsl doc to select for this, that works. So, instead of this; I have this; xsltproc will select the names of the models and manufacturers correctly. Does libxslt implement this functionality different than Xalan (if so can someone tell me the proper usage) or is this a bug? The release of xsltproc I am using: Using libxml 20426, libxslt 10022 and libexslt 713 xsltproc was compiled against libxml 20426, libxslt 10022 and libexslt 713 libxslt 10022 was compiled against libxml 20426 libexslt 713 was compiled against libxml 20426 Thanks for your help, Susan Cline --------------------------------- Do you Yahoo!? U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD --0-1072373250-1036692970=:7547 Content-Type: text/html; charset=us-ascii

Hi,

I haven't heard from anyone - can anyone comment on if this is a bug or not?

Thanks,

Susan *********************************

Hello,

Here is the xml doc:

Here is the xsl doc:

<xsl:output method="text" encoding="UTF-8" />
<xsl:strip-space elements="*" />

<xsl:template match="/">
<xsl:apply-templates />
</xsl:template>

<xsl:template match="car:models">
    <xsl:text>My Car Models:
</xsl:text>
    <xsl:apply-templates select="car:model/@car:name"></xsl:apply-templates>
    <xsl:text>
</xsl:text>
</xsl:template>

<xsl:template match="manu:manufacturers">
<xsl:text>The Manufacturers:
</xsl:text>
<xsl:apply-templates select="manu:manufacturer/@manu:name"></xsl:apply-templ
ates>
</xsl:template>

<xsl:template match="@*[local-name()='name']">
<xsl:value-of select="." />
<xsl:text>
</xsl:text>
</xsl:template>

</xsl:stylesheet>

When I attempt to use xsltproc here are the results;

compilation error: file input.xsl line 25 element template

xsltCompilePattern : failed to compile '@*[local-name()='name']'

The result using xalan is what I had hoped for:

My Car Models:
Rabbit
Tundra
Mini

The Manufacturers:
Volkswagen
Toyota
Bavarian Motor Works

If I change the input xml doc so that name is an element instead of an attribute and change my xsl doc to select for this, that works. So, instead of this;

<xsl:template match="@*[local-name()='name']">

I have this;

<xsl:template match="*[local-name()='name']">

xsltproc will select the names of the models and manufacturers correctly.

Does libxslt implement this functionality different than Xalan (if so can someone tell me the proper usage) or is this a bug?

The release of xsltproc I am using:

Thanks for your help,

Susan Cline

Do you Yahoo!?
U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD --0-1072373250-1036692970=:7547-- From veillard@redhat.com Thu Nov 7 13:16:15 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 9F3E318660 for ; Thu, 7 Nov 2002 13:16:15 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id gA7IGFC02956; Thu, 7 Nov 2002 13:16:15 -0500 Date: Thu, 7 Nov 2002 13:16:15 -0500 From: Daniel Veillard To: xslt@gnome.org Cc: home4slc@yahoo.com Subject: Re: [xslt] CDATA-section-elements? Is this a bug? Message-ID: <20021107131615.I2472@redhat.com> References: <20021107181407.10998.qmail@web14401.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021107181407.10998.qmail@web14401.mail.yahoo.com>; from home4slc@yahoo.com on Thu, Nov 07, 2002 at 10:14:07AM -0800 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Nov 07, 2002 at 10:14:07AM -0800, Susan Cline wrote: > > Hi, > > I posted the below message earlier this week. Does anyone know if this is a bug? yes that looks a bug in the recursive copy which didn't checked for the cdata-element, please bugzilla 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 Nov 7 15:17:03 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id EE827182CC for ; Thu, 7 Nov 2002 15:17:02 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id gA7KH2o05157; Thu, 7 Nov 2002 15:17:02 -0500 Date: Thu, 7 Nov 2002 15:17:02 -0500 From: Daniel Veillard To: xslt@gnome.org Cc: home4slc@yahoo.com Subject: Re: [xslt] local-name() and attributes Message-ID: <20021107151702.J2472@redhat.com> References: <20021107181610.11356.qmail@web14401.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021107181610.11356.qmail@web14401.mail.yahoo.com>; from home4slc@yahoo.com on Thu, Nov 07, 2002 at 10:16:10AM -0800 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Thu, Nov 07, 2002 at 10:16:10AM -0800, Susan Cline wrote: > When I attempt to use xsltproc here are the results; > > compilation error: file input.xsl line 25 element template > > xsltCompilePattern : failed to compile '@*[local-name()='name']' yep, it seems another bug this time on the XPath analyser ... 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 Nov 7 17:51:01 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id E30AB18249 for ; Thu, 7 Nov 2002 17:51:00 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id gA7Mp0r19319; Thu, 7 Nov 2002 17:51:00 -0500 Date: Thu, 7 Nov 2002 17:51:00 -0500 From: Daniel Veillard To: xslt@gnome.org Cc: "Vakoc, Mark" Message-ID: <20021107175100.K2472@redhat.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: [xslt] speedup for node document order Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline It was a couple of months ago IIRC: I don't remember if it was Mark or someone else who had troubles with the cost associated to sorting large nodeset in XPath. Ideally an node counter could do this but there is no such thing in the existing structure ... except I realized I usually keep line numbers from the input on element nodes, and that could be used to at least help the sort in most cases. The following patch does this it doesn't break the regression tests (one need to recompile libxml, then libxslt and make sure the parser generate the line numbers like xsltproc does with xmlLineNumbersDefault(1); ). Whoever was having the problem, if you're still around I would like comment on this patch, 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/ --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="merge.patch" Index: xpath.c =================================================================== RCS file: /cvs/gnome/gnome-xml/xpath.c,v retrieving revision 1.206 diff -c -r1.206 xpath.c *** xpath.c 22 Oct 2002 17:35:33 -0000 1.206 --- xpath.c 7 Nov 2002 22:44:39 -0000 *************** *** 1368,1373 **** --- 1368,1388 ---- return(-1); /* + * Speedup using line numbers if availble. + */ + if ((node1->type == XML_ELEMENT_NODE) && + (node2->type == XML_ELEMENT_NODE) && + (0 != (int) node1->content) && (0 != (int) node2->content)) { + int l1, l2; + l1 = (int) node1->content; + l2 = (int) node2->content; + if (l1 < l2) + return(1); + if (l1 > l2) + return(-1); + } + + /* * compute depth to root */ for (depth2 = 0, cur = node2;cur->parent != NULL;cur = cur->parent) { --cWoXeonUoKmBZSoM-- From Mark_Vakoc@jdedwards.com Thu Nov 7 19:58:40 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from ns1.jdedwards.com (ns1.jdedwards.com [199.166.248.147]) by mail.gnome.org (Postfix) with ESMTP id DB321182DD for ; Thu, 7 Nov 2002 19:58:39 -0500 (EST) Received: from denvscans3.jdedwards.com ([10.0.14.77]) by ns1.jdedwards.com (8.9.1/8.9.1) with SMTP id RAA14069 for ; Thu, 7 Nov 2002 17:58:39 -0700 (MST) Received: from 10.0.14.51 by denvscans3.jdedwards.com (InterScan E-Mail VirusWall NT); Thu, 07 Nov 2002 17:59:07 -0700 Received: by cormails11.jdedwards.com with Internet Mail Service (5.5.2653.19) id <3YKRKRCH>; Thu, 7 Nov 2002 18:00:31 -0700 Message-ID: <09B3671D58690A4193A7F8F15F416B23103312@denmails3.jdedwards.com> From: "Vakoc, Mark" To: "'xslt@gnome.org'" Date: Thu, 7 Nov 2002 17:59:02 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [xslt] RE: speedup for node document order Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > It was a couple of months ago IIRC: > I don't remember if it was Mark or someone else who had troubles Hmmm... Many people will say I have troubles, but this isn't one of 'em! From paul@localdomain.net Fri Nov 8 01:23:49 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by mail.gnome.org (Postfix) with ESMTP id A08A0191C0 for ; Fri, 8 Nov 2002 01:22:34 -0500 (EST) Received: from sdn-ap-015tnnashp0215.dialsprint.net ([63.190.208.215] helo=localhost.localdomain.net) by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18A2XJ-00069S-00 for xslt@gnome.org; Thu, 07 Nov 2002 22:22:33 -0800 Received: by localhost.localdomain.net (Postfix, from userid 500) id 354D0352CD; Fri, 8 Nov 2002 01:22:34 -0500 (EST) Date: Fri, 8 Nov 2002 01:22:34 -0500 From: Paul Tremblay To: Daniel Veillard Message-ID: <20021108012234.G29413@localhost.localdomain> Mail-Followup-To: Daniel Veillard Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.21i Subject: [xslt] xsltproc changes unicode to nonsense Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: In my stlesheet, I have: I then put this character in my xslt stylesheet: This should be a no break space. However, xsltproc translates this to a upper case A with a hat over it. If I change the output method line to: then xsltproc leaves the entity alone. If I run my stylesheet with xalan, and use html as the output method, the gets translated to Is there anything I can do? I need html as my output method because I am using
, which is not recogized in html. Thanks Paul -- ************************ *Paul Tremblay * *phthenry@earthlink.net* ************************ From morus@tanto-xipolis.de Fri Nov 8 03:33:57 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.tanto-xipolis.de (h-213.61.178.42.host.de.colt.net [213.61.178.42]) by mail.gnome.org (Postfix) with ESMTP id 2A2EE18116 for ; Fri, 8 Nov 2002 03:33:57 -0500 (EST) Received: from morus.xipolis.net (unknown [10.0.1.4]) by mail.tanto-xipolis.de (Postfix on SuSE Linux 7.3 (i386)) with ESMTP id 464CC19B795 for ; Fri, 8 Nov 2002 09:33:56 +0100 (CET) Received: (from morus@localhost) by morus.xipolis.net (8.11.6/8.11.6/SuSE Linux 0.5) id gA88YlS20337; Fri, 8 Nov 2002 09:34:47 +0100 From: Morus Walter MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15819.30503.1844.228243@morus.xipolis.net> Date: Fri, 8 Nov 2002 09:34:47 +0100 To: xslt@gnome.org Subject: Re: [xslt] xsltproc changes unicode to nonsense In-Reply-To: <20021108012234.G29413@localhost.localdomain> References: <20021108012234.G29413@localhost.localdomain> X-Mailer: VM 6.95 under 21.4 (patch 4) "Artificial Intelligence" XEmacs Lucid Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Paul Tremblay writes: > In my stlesheet, I have: > > > > I then put this character in my xslt stylesheet: > > > > This should be a no break space. > > However, xsltproc translates this to a upper case A with a hat over it. > If I change the output method line to: > No. It outputs a nonbreaking space in utf8 which is (in latin1) a upper case A with a hat over, followed by nonbreaking space. The latter is a bit hard to see but it's there. Provide an apropriate output encoding (such as ASCII or iso-8859-1) to get ' ' or a literate non breaking space. > > > then xsltproc leaves the entity alone. This is in deed a bit strange, but AFAIK any xslt processer is free to choose the way it outputs characters. So xsltproc might output a utf8 nonbreaking space as well, but it does not have to. HTH Morus From paul@localdomain.net Fri Nov 8 18:06:06 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mail.gnome.org (Postfix) with ESMTP id 452D7180E1 for ; Fri, 8 Nov 2002 18:06:06 -0500 (EST) Received: from sdn-ap-020tnnashp0294.dialsprint.net ([63.191.73.40] helo=localhost.localdomain.net) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18AICS-0000EC-00 for xslt@gnome.org; Fri, 08 Nov 2002 15:06:05 -0800 Received: by localhost.localdomain.net (Postfix, from userid 500) id 20F3E352CD; Fri, 8 Nov 2002 18:06:05 -0500 (EST) Date: Fri, 8 Nov 2002 18:06:05 -0500 From: Paul Tremblay To: xslt@gnome.org Subject: Re: [xslt] xsltproc changes unicode to nonsense Message-ID: <20021108180605.H29413@localhost.localdomain> Mail-Followup-To: xslt@gnome.org References: <20021108012234.G29413@localhost.localdomain> <15819.30503.1844.228243@morus.xipolis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15819.30503.1844.228243@morus.xipolis.net> User-Agent: Mutt/1.3.21i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Nov 08, 2002 at 09:34:47AM +0100, Morus Walter wrote: > Paul Tremblay writes: > > In my stlesheet, I have: > > > > > > > > I then put this character in my xslt stylesheet: > > > > > > > > This should be a no break space. > > > > However, xsltproc translates this to a upper case A with a hat over it. > > If I change the output method line to: > > > No. It outputs a nonbreaking space in utf8 which is (in latin1) > a upper case A with a hat over, followed by nonbreaking space. > The latter is a bit hard to see but it's there. > Wow. I'm really confused. What does the A with the hat over it have to do with a non-breaking space? I thought I could pick any unicode character, and a browser would have to represent it. I understand that not all browsers can handle every single unicode character, but I thought that if a browser couldn't handle a character, it would output a "?". I guess I don't understand utf8. I thought that utf8 *was* unicode. That is, it was a way to represent all of unicode with just 8-bit numbers. (Now that I think of it, even 8-bit should be wrong, since not all computers agree on the upper 128 in character set.) Do you know any good sites that explain this? > Provide an apropriate output encoding (such as ASCII or iso-8859-1) > to get ' ' or a literate non breaking space. I'll have to try this. One thing that really annoys me is that I have a linux box, and I always get webpages full of "??" because the webpages assumed everone uses the same encoding scheme. I thought utf8 was a way to ensure this wouldn't happen. But I guess I have a thing or two to learn! Paul -- ************************ *Paul Tremblay * *phthenry@earthlink.net* ************************ From tmoog@polhode.com Fri Nov 8 22:37:07 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mail.gnome.org (Postfix) with ESMTP id 9E0301826A for ; Fri, 8 Nov 2002 22:37:07 -0500 (EST) Received: from polhode3 ([12.250.133.27]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20021109033707.SGYL3205.sccrmhc03.attbi.com@polhode3> for ; Sat, 9 Nov 2002 03:37:07 +0000 Date: Fri, 8 Nov 2002 21:34:55 -0600 (Central Standard Time) From: Tom Moog To: "xslt@gnome.org" Subject: Re: [xslt] xsltproc changes unicode to nonsense In-Reply-To: <20021108180605.H29413@localhost.localdomain> Message-ID: X-X-Sender: tmoog@imap.enteract.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: The A with the hat is the printable part of a two byte utf-8 sequence for (namely octal 302 240). On Fri, 8 Nov 2002, Paul Tremblay wrote: > On Fri, Nov 08, 2002 at 09:34:47AM +0100, Morus Walter wrote: > > Paul Tremblay writes: > > > In my stlesheet, I have: > > > > > > > > > > > > I then put this character in my xslt stylesheet: > > > > > > > > > > > > This should be a no break space. > > > > > > However, xsltproc translates this to a upper case A with a hat over it. > > > If I change the output method line to: > > > > > No. It outputs a nonbreaking space in utf8 which is (in latin1) > > a upper case A with a hat over, followed by nonbreaking space. > > The latter is a bit hard to see but it's there. > > > > Wow. I'm really confused. What does the A with the hat over it have to > do with a non-breaking space? > > I thought I could pick any unicode character, and a browser would have > to represent it. I understand that not all browsers can handle every > single unicode character, but I thought that if a browser couldn't > handle a character, it would output a "?". > > I guess I don't understand utf8. I thought that utf8 *was* unicode. That > is, it was a way to represent all of unicode with just 8-bit numbers. > (Now that I think of it, even 8-bit should be wrong, since not all > computers agree on the upper 128 in character set.) > > Do you know any good sites that explain this? > > > > Provide an apropriate output encoding (such as ASCII or iso-8859-1) > > to get ' ' or a literate non breaking space. > > I'll have to try this. One thing that really annoys me is that I have a > linux box, and I always get webpages full of "??" because the webpages > assumed everone uses the same encoding scheme. I thought utf8 was a way > to ensure this wouldn't happen. But I guess I have a thing or two to > learn! > > Paul > > -- > > ************************ > *Paul Tremblay * > *phthenry@earthlink.net* > ************************ > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt > From paul@localdomain.net Sun Nov 10 03:16:24 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mail.gnome.org (Postfix) with ESMTP id F3859181A1 for ; Sun, 10 Nov 2002 03:16:23 -0500 (EST) Received: from sdn-ap-007tnnashp0231.dialsprint.net ([63.189.192.231] helo=localhost.localdomain.net) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18AnGY-0000vR-00 for xslt@gnome.org; Sun, 10 Nov 2002 00:16:22 -0800 Received: by localhost.localdomain.net (Postfix, from userid 500) id 1D5F6352CD; Sun, 10 Nov 2002 03:16:17 -0500 (EST) Date: Sun, 10 Nov 2002 03:16:17 -0500 From: Paul Tremblay To: xslt@gnome.org Subject: Re: [xslt] xsltproc changes unicode to nonsense Message-ID: <20021110031616.A4017@localhost.localdomain> Mail-Followup-To: xslt@gnome.org References: <20021108012234.G29413@localhost.localdomain> <15819.30503.1844.228243@morus.xipolis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15819.30503.1844.228243@morus.xipolis.net> User-Agent: Mutt/1.3.21i Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Fri, Nov 08, 2002 at 09:34:47AM +0100, Morus Walter wrote: > Provide an apropriate output encoding (such as ASCII or iso-8859-1) > to get ' ' or a literate non breaking space. Thanks. This works really nice. Encoding is just a bit clearer in my head. Paul -- ************************ *Paul Tremblay * *phthenry@earthlink.net* ************************ From Gerhard.Dieringer@nexgo.de Sun Nov 10 11:14:06 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from mx01.nexgo.de (mx01.nexgo.de [151.189.8.96]) by mail.gnome.org (Postfix) with ESMTP id 4895B18207 for ; Sun, 10 Nov 2002 11:14:06 -0500 (EST) Received: from dialin-145-254-195-156.arcor-ip.net (dialin-145-254-195-156.arcor-ip.net [145.254.195.156]) by mx01.nexgo.de (Postfix) with ESMTP id E0B6B3C0B1 for ; Sun, 10 Nov 2002 17:14:04 +0100 (CET) From: Gerhard Dieringer To: xslt@gnome.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0 (Preview Release) Date: 10 Nov 2002 17:11:45 +0100 Message-Id: <1036944706.3442.6.camel@lise> Mime-Version: 1.0 Subject: [xslt] namespace URI for child elements Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi I have the following question: the following stylesheet: --------------------------------------------------------

-------------------------------------------------------- gives with the following input file: -------------------------------------------------------- -------------------------------------------------------- the output: -------------------------------------------------------- data=hello data=world -------------------------------------------------------- Is there a way to avoid the (not needed) namespace-URIs in and and get the result -------------------------------------------------------- data=hello data=world -------------------------------------------------------- ------- Gerhard From morus@tanto-xipolis.de Mon Nov 11 03:12:31 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.tanto-xipolis.de (h-213.61.178.42.host.de.colt.net [213.61.178.42]) by mail.gnome.org (Postfix) with ESMTP id D493C180FC for ; Mon, 11 Nov 2002 03:12:30 -0500 (EST) Received: from morus.xipolis.net (unknown [10.0.1.4]) by mail.tanto-xipolis.de (Postfix on SuSE Linux 7.3 (i386)) with ESMTP id BCE3E19B793; Mon, 11 Nov 2002 09:12:29 +0100 (CET) Received: (from morus@localhost) by morus.xipolis.net (8.11.6/8.11.6/SuSE Linux 0.5) id gAB8DQJ01554; Mon, 11 Nov 2002 09:13:26 +0100 From: Morus Walter MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15823.26277.972257.109861@morus.xipolis.net> Date: Mon, 11 Nov 2002 09:13:25 +0100 To: xslt@gnome.org Subject: Re: [xslt] xsltproc changes unicode to nonsense Cc: phthenry@earthlink.net In-Reply-To: <20021108180605.H29413@localhost.localdomain> References: <20021108012234.G29413@localhost.localdomain> <15819.30503.1844.228243@morus.xipolis.net> <20021108180605.H29413@localhost.localdomain> X-Mailer: VM 6.95 under 21.4 (patch 4) "Artificial Intelligence" XEmacs Lucid Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Paul Tremblay writes: > On Fri, Nov 08, 2002 at 09:34:47AM +0100, Morus Walter wrote: > > Paul Tremblay writes: > > > In my stlesheet, I have: > > > > > > > > > > > > I then put this character in my xslt stylesheet: > > > > > > > > > > > > This should be a no break space. > > > > > > However, xsltproc translates this to a upper case A with a hat over it. > > > If I change the output method line to: > > > > > No. It outputs a nonbreaking space in utf8 which is (in latin1) > > a upper case A with a hat over, followed by nonbreaking space. > > The latter is a bit hard to see but it's there. > > > > Wow. I'm really confused. What does the A with the hat over it have to > do with a non-breaking space? > > I thought I could pick any unicode character, and a browser would have > to represent it. I understand that not all browsers can handle every > single unicode character, but I thought that if a browser couldn't > handle a character, it would output a "?". > > I guess I don't understand utf8. I thought that utf8 *was* unicode. That > is, it was a way to represent all of unicode with just 8-bit numbers. > (Now that I think of it, even 8-bit should be wrong, since not all > computers agree on the upper 128 in character set.) > No. Unicode is a convention, how to map characters to numbers. E.g. #160 is nonbreaking space. #65 is a 'A'. UTF8 is a convention, how to store these numbers into a file. So unicode and UTF8 are connected but not the same. UTF8 doesn't simply store the number, it encodes the number into variable length byte codes (number 0-127 take one byte, 128-2048 two bytes and so on). Now when you do this with #160 you get two bytes (xC2 and xA0) and when you *interprete* these characters as latin1 you get the characters named above (of course this is a misinterpretion, since you intended these bytes to be utf8). So this is what you see in a latin1 console window or in a latin1 expecting browser. If you have this in a browser, you might switch the encoding to utf8 and the browser will display your non breaking space (in mozilla this is 'view' -> 'character coding'). So in your case, part of the problem might be, that you have to tell the browser that it's getting utf8. You should always consider that any program just sees some bytes (containing numbers) and interpretes them before they get charaters and readable text. And when there are different ways how to interprete something, you will see different results. > Do you know any good sites that explain this? > Hava a look at http://www.cl.cam.ac.uk/~mgk25/unicode.html (UTF-8 and Unicode FAQ for Unix/Linux) http://czyborra.com/ (Unicode in the Unix Environment) On linux you might also have a look at the utf8 man page though this is very technical. > > > Provide an apropriate output encoding (such as ASCII or iso-8859-1) > > to get ' ' or a literate non breaking space. > > I'll have to try this. One thing that really annoys me is that I have a > linux box, and I always get webpages full of "??" because the webpages > assumed everone uses the same encoding scheme. I thought utf8 was a way > to ensure this wouldn't happen. But I guess I have a thing or two to > learn! > Well, one source of the ?-problem with linux/unix browsers is that windows user tend to use a special windows encoding and claim it's latin1. See http://www.cs.tut.fi/~jkorpela/www/windows-chars.html Linux/unix users are usually out of danger of creating these errors, since the windows encodings aren't used under linux/unix. The second source is insufficent encoding declaration. If you send latin1 and the browser "thinks" it's utf8 or visa verce, you should not be suprised, if things don't work as expected. The most secure way not get into trouble is to use ascii and decimal character references ({). Specifying the right encoding should work also of course. HTH Morus From pj@walter-graphtek.com Mon Nov 11 04:07:17 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from jessenlenz.com (mail.jessenlenz.com [212.79.192.34]) by mail.gnome.org (Postfix) with ESMTP id A2D0B181CC for ; Mon, 11 Nov 2002 04:07:16 -0500 (EST) Received: from SOFTDEV8 (217.227.30.128) by jessenlenz.com with ESMTP (Eudora Internet Mail Server 3.1.3); Mon, 11 Nov 2002 12:08:22 +0100 From: "Peter Jacobi" To: Paul Tremblay , xslt@gnome.org Date: Mon, 11 Nov 2002 10:12:36 +0100 MIME-Version: 1.0 Subject: Re: [xslt] xsltproc changes unicode to nonsense Message-ID: <3DCF8294.25025.4BE6CA@localhost> Priority: normal In-reply-to: <20021108180605.H29413@localhost.localdomain> References: <15819.30503.1844.228243@morus.xipolis.net> 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: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi Paul, I stumbled across this thread during my coffee break, and can give a hint, which possibly resolves your problems (as an alternative to the solution). > I thought I could pick any unicode character, and a browser would have > to represent it. I understand that not all browsers can handle every > single unicode character, but I thought that if a browser couldn't > handle a character, it would output a "?". The problem is to tell the browser, that the HTML document is encoded in UTF-8, especially when opening documents as files (in contrast to to HTTP): This you can achieve by putting a meta tag in the header: Regards, Peter Jacobi From cbozeman@hiwaay.net Mon Nov 11 09:01:28 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.hiwaay.net (fly.hiwaay.net [216.180.54.1]) by mail.gnome.org (Postfix) with ESMTP id 93ADE1844D for ; Mon, 11 Nov 2002 09:01:28 -0500 (EST) Received: from tnt6-216-180-4-60.dialup.HiWAAY.net (tnt6-216-180-4-60.dialup.HiWAAY.net [216.180.4.60]) by mail.hiwaay.net (8.12.5/8.12.5) with ESMTP id gABE1LnO014930 for ; Mon, 11 Nov 2002 08:01:22 -0600 (CST) Subject: Re: [xslt] namespace URI for child elements From: Charles Bozeman To: xslt@gnome.org In-Reply-To: <1036944706.3442.6.camel@lise> References: <1036944706.3442.6.camel@lise> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 11 Nov 2002 08:01:38 -0600 Message-Id: <1037023300.1487.5.camel@localhost.localdomain> Mime-Version: 1.0 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: add the following attribute to your stylesheet element: exclude-result-prefixes="in out" On Sun, 2002-11-10 at 10:11, Gerhard Dieringer wrote: > > > Hi > > I have the following question: > > the following stylesheet: > -------------------------------------------------------- > > > xmlns:in="input" > xmlns:out="output" > version='1.0'> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------- > gives with the following input file: > -------------------------------------------------------- > > > > > > -------------------------------------------------------- > the output: > -------------------------------------------------------- > > > > data=hello > data=world > > -------------------------------------------------------- > Is there a way to avoid the (not needed) namespace-URIs in > and > and get the result > -------------------------------------------------------- > > > > data=hello > data=world > > -------------------------------------------------------- > > > ------- > Gerhard > > > _______________________________________________ > xslt mailing list, project page http://xmlsoft.org/XSLT/ > xslt@gnome.org > http://mail.gnome.org/mailman/listinfo/xslt > From rothwell@holly-springs.nc.us Mon Nov 11 10:35:17 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from ns.holly-springs.nc.us (unknown [207.198.61.36]) by mail.gnome.org (Postfix) with ESMTP id DC0F9184A0 for ; Mon, 11 Nov 2002 10:35:16 -0500 (EST) Received: from holly-springs.nc.us (gwe.abanes.org [216.54.200.242]) (authenticated) by ns.holly-springs.nc.us (8.11.6/8.11.2) with ESMTP id gABFZG904134 for ; Mon, 11 Nov 2002 10:35:16 -0500 Message-ID: <3DCFCE2E.1070008@holly-springs.nc.us> Date: Mon, 11 Nov 2002 10:35:10 -0500 From: Michael Rothwell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: xslt@gnome.org X-Enigmail-Version: 0.65.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [xslt] extra "" at top of output Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: I'm using libXSLT to transform XML into HTML. It looks like libXSLT is putting an extra "" at the top of the document, and an "" at the bottom, like this: [...] It does this regardless of whether I have "" in the source file or not. I'm using the HTML parser to load HTML and trandform it, so it's not exactly XML input. From rothwell@holly-springs.nc.us Mon Nov 11 10:37:08 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from ns.holly-springs.nc.us (unknown [207.198.61.36]) by mail.gnome.org (Postfix) with ESMTP id 53C8C184A0 for ; Mon, 11 Nov 2002 10:37:08 -0500 (EST) Received: from holly-springs.nc.us (gwe.abanes.org [216.54.200.242]) (authenticated) by ns.holly-springs.nc.us (8.11.6/8.11.2) with ESMTP id gABFb7904152 for ; Mon, 11 Nov 2002 10:37:07 -0500 Message-ID: <3DCFCE9D.80803@holly-springs.nc.us> Date: Mon, 11 Nov 2002 10:37:01 -0500 From: Michael Rothwell User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: xslt@gnome.org Subject: Re: [xslt] xsltproc changes unicode to nonsense References: <20021108012234.G29413@localhost.localdomain> <15819.30503.1844.228243@morus.xipolis.net> X-Enigmail-Version: 0.65.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Morus Walter wrote: > Paul Tremblay writes: > >>In my stlesheet, I have: >> >> >> >>I then put this character in my xslt stylesheet: >> >> Have your HTML output include this: From Jre@scanlaser.nl Tue Nov 12 13:16:14 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.scanlaser.com (unknown [213.201.144.249]) by mail.gnome.org (Postfix) with ESMTP id B072F1813A for ; Tue, 12 Nov 2002 13:16:14 -0500 (EST) To: xslt@gnome.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: Jre@scanlaser.nl Date: Tue, 12 Nov 2002 18:16:12 +0000 X-MIMETrack: Serialize by Router on Eureka/slbv(Release 5.0.10 |March 22, 2002) at 11/12/2002 07:16:14 PM, Serialize complete at 11/12/2002 07:16:14 PM Content-Type: text/plain; charset="us-ascii" Subject: [xslt] using key() function with key name in a variable Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: I'm using the key() function (via xsltproc) and supplying the key name in a variable. This works if the variable contains a string (such as) However, if the variable contains an RTF, such as keyname1 keyname2 then using key( $k, ... ) gives the error runtime error: file gbs_log_show_all.xsl line 187 element variable key() : invalid arg expecting a string but key( string($k), ... ) works ok. I've tried the same thing in saxon, mozilla and msxml and they all seem to work when $k contains the RTF (without needing the string() function). Looking at the xslt rec, it doesn't seem to say much about the first parameter to key() other than that it's a string and a QName. Didn't find anything in the archives and I don't remember seeing anything like this on xslt-list, so I don't know whether to report this as a bug or not, but it seems to act differently to several other xslt processors. I'm using xsltproc -V Using libxml 20421, libxslt 10017 and libexslt 708 xsltproc was compiled against libxml 20421, libxslt 10017 and libexslt 708 libxslt 10017 was compiled against libxml 20421 libexslt 708 was compiled against libxml 20421 regards, John Escott. From veillard@redhat.com Tue Nov 12 13:31:16 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 9DEDE1813A for ; Tue, 12 Nov 2002 13:31:16 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id gACIVGQ31764 for xslt@gnome.org; Tue, 12 Nov 2002 13:31:16 -0500 Date: Tue, 12 Nov 2002 13:31:16 -0500 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] using key() function with key name in a variable Message-ID: <20021112133116.I28903@redhat.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="0ntfKIWw70PvrIHh" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from Jre@scanlaser.nl on Tue, Nov 12, 2002 at 06:16:12PM +0000 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Nov 12, 2002 at 06:16:12PM +0000, Jre@scanlaser.nl wrote: > gives the error > runtime error: file gbs_log_show_all.xsl line 187 element variable > key() : invalid arg expecting a string > but > key( string($k), ... ) > works ok. Okay, > I've tried the same thing in saxon, mozilla and msxml and they all seem to > work when $k contains the RTF (without needing the string() function). > Looking at the xslt rec, it doesn't seem to say much about the first > parameter to key() other than that it's a string and a QName. Hum, > Didn't find anything in the archives and I don't remember seeing anything > like this on xslt-list, so I don't know whether to report this as a bug or > not, but it seems to act differently to several other xslt processors. Seems very easy to fix to follow the common behaviour, so it's probably not worth starting a standard reading contest over xsl-list :-) Patch enclosed, untested since you didn't provided a full example. 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/ --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="key.patch" Index: libxslt/functions.c =================================================================== RCS file: /cvs/gnome/libxslt/libxslt/functions.c,v retrieving revision 1.42 diff -c -r1.42 functions.c *** libxslt/functions.c 15 Oct 2002 16:06:47 -0000 1.42 --- libxslt/functions.c 12 Nov 2002 18:30:00 -0000 *************** *** 270,275 **** --- 270,276 ---- return; } + xmlXPathStringFunction(ctxt, 1); obj2 = valuePop(ctxt); if ((obj2 == NULL) || (ctxt->value == NULL) || (ctxt->value->type != XPATH_STRING)) { --0ntfKIWw70PvrIHh-- From Jre@scanlaser.nl Wed Nov 13 14:10:37 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.scanlaser.com (unknown [213.201.144.249]) by mail.gnome.org (Postfix) with ESMTP id 7040818380 for ; Wed, 13 Nov 2002 14:10:37 -0500 (EST) To: xslt@gnome.org Subject: Re: [xslt] using key() function with key name in a variable MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: Jre@scanlaser.nl Date: Wed, 13 Nov 2002 19:10:33 +0000 X-MIMETrack: Serialize by Router on Eureka/slbv(Release 5.0.10 |March 22, 2002) at 11/13/2002 08:10:37 PM, Serialize complete at 11/13/2002 08:10:37 PM Content-Type: text/plain; charset="us-ascii" Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: > Seems very easy to fix to follow the common behaviour, so it's probably not > worth starting a standard reading contest over xsl-list :-) > Patch enclosed, untested since you didn't provided a full example. Thanks very much -- I can confirm it works. Sorry about the lack of an example, but maybe better late than never: source doc: -------------------- stylesheet: -------------------

k1 k2

output: ----------------------- one33 two15 Thanks again, John Escott. From Yves.Forkl@gmx.net Wed Nov 13 13:44:03 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from mail.gmx.net (sproxy.gmx.de [213.165.64.20]) by mail.gnome.org (Postfix) with SMTP id 0AFAF18A91 for ; Wed, 13 Nov 2002 13:44:03 -0500 (EST) Received: (qmail 26414 invoked by uid 0); 13 Nov 2002 18:43:39 -0000 Received: from dialin-145-254-229-237.arcor-ip.net (HELO gmx.net) (145.254.229.237) by mail.gmx.net (mp004-rz3) with SMTP; 13 Nov 2002 18:43:39 -0000 Message-ID: <3DD29E01.39B2AED9@gmx.net> Date: Wed, 13 Nov 2002 19:46:25 +0100 From: Yves Forkl X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: de,fr,en MIME-Version: 1.0 To: xslt@gnome.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [xslt] xsltproc: --stringparam under Cygwin? Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: xsltproc's option stringparam doesn't seem to work in the current release (as of 2002-11-10) of precompiled libs and binaries for Cygwin. The version of xsltproc included claims to be: $ xsltproc --version Using libxml 20417, libxslt 10010 and libexslt 703 xsltproc was compiled against libxml 20413, libxslt 10010 and libexslt 703 libxslt 10010 was compiled against libxml 20413 libexslt 703 was compiled against libxml 20413 (I tried it under Windows with another version, "xsltproc compiled against libxml 20426, libxslt 10022 and libexslt 713": the problem does not appear there.) Here is the error I get: $ xsltproc --stringparam myparam mystring stylesheet.xsl input.xml warning: failed to load external entity "myparam" cannot parse myparam In contrast, it works fine if I use the param option instead and quote the string appropriately: $ xsltproc --param myparam "'myvalue'" stylesheet.xsl input.xml However, I think I depend on the stringparam option because I want to pass a variable as a parameter, running xsltproc from a bash shell script, like this: xsltproc --stringparam myparam "$mystring" stylesheet.xsl in.xml > out.xml I tried to enclose the content of the variable with "' and '" and use --param instead, which worked in some cases. But when I want to pass a path to a file to my stylesheet, I get in trouble: - either I don't quote the path, then it is considered a node identifier evaluating to NULL - or I quote it, so it is a string; but later, when xsltproc applies the stylesheet (which is trying to read from that file), it concatenates the current directory (as base URI, I suppose) and the apostrophe-quoted contents of $mystring, complaining: warning: failed to load external entity "/current/dir/'/path/given/in/mystring'" Do I need to use another technique (like XInclude) to pass path names or is there a chance for me to get the stringparam option working? If so, is there a newer version of xsltproc for Cygwin around or would I have to compile it myself? From which versions of the libxml2 and libxslt libraries? Yves From veillard@redhat.com Thu Nov 14 04:16:36 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 5A28B1819F for ; Thu, 14 Nov 2002 04:16:28 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id gAE9GRP16627; Thu, 14 Nov 2002 04:16:27 -0500 Date: Thu, 14 Nov 2002 04:16:26 -0500 From: Daniel Veillard To: Yves.Forkl@gmx.net Cc: xslt@gnome.org Subject: Re: [xslt] xsltproc: --stringparam under Cygwin? Message-ID: <20021114041626.S28903@redhat.com> References: <3DD29E01.39B2AED9@gmx.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: <3DD29E01.39B2AED9@gmx.net>; from Yves.Forkl@gmx.net on Wed, Nov 13, 2002 at 07:46:25PM +0100 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wed, Nov 13, 2002 at 07:46:25PM +0100, Yves Forkl wrote: > xsltproc's option stringparam doesn't seem to work in the current > release (as of 2002-11-10) of precompiled libs and binaries for > Cygwin. The version of xsltproc included claims to be: > > $ xsltproc --version > Using libxml 20417, libxslt 10010 and libexslt 703 > xsltproc was compiled against libxml 20413, libxslt 10010 and libexslt > 703 > libxslt 10010 was compiled against libxml 20413 > libexslt 703 was compiled against libxml 20413 Looks 1/ old 2/ bad (the library used an the one the application was compiled again do not match) > (I tried it under Windows with another version, "xsltproc compiled > against libxml 20426, libxslt 10022 and libexslt 713": the problem > does not appear there.) Simply upgrade then ! 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 Nov 14 04:32:42 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 8B3A918361 for ; Thu, 14 Nov 2002 04:32:42 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id gAE9Wgq19512 for xslt@gnome.org; Thu, 14 Nov 2002 04:32:42 -0500 Date: Thu, 14 Nov 2002 04:32:42 -0500 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] using key() function with key name in a variable Message-ID: <20021114043242.T28903@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from Jre@scanlaser.nl on Wed, Nov 13, 2002 at 07:10:33PM +0000 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: On Wed, Nov 13, 2002 at 07:10:33PM +0000, Jre@scanlaser.nl wrote: > > Seems very easy to fix to follow the common behaviour, so it's > probably not > > worth starting a standard reading contest over xsl-list :-) > > Patch enclosed, untested since you didn't provided a full example. > > Thanks very much -- I can confirm it works. Sorry about the lack of an > example, but maybe better late than never: okay, added to the regression tests: paphio:~/XSLT/tests/general -> xsltproc bug-98.xsl ../docs/bug-98.xml one33 two15 paphio:~/XSLT/tests/general -> 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 peb@mppmu.mpg.de Thu Nov 14 09:17:20 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from iwsrz5.mppmu.mpg.de (iwsrz5.mppmu.mpg.de [134.107.2.78]) by mail.gnome.org (Postfix) with ESMTP id CA5B61811F for ; Thu, 14 Nov 2002 09:17:19 -0500 (EST) Received: from pcl321.mppmu.mpg.de (pcl321.mppmu.mpg.de [134.107.3.54]) by iwsrz5.mppmu.mpg.de (Postfix) with ESMTP id C78E33256 for ; Thu, 14 Nov 2002 15:17:18 +0100 (NFT) Received: from pcl321.mppmu.mpg.de (localhost [127.0.0.1]) by pcl321.mppmu.mpg.de (8.12.2/8.12.2) with ESMTP id gAEEHIHJ009172 for ; Thu, 14 Nov 2002 15:17:18 +0100 Received: from localhost (peb@localhost) by pcl321.mppmu.mpg.de (8.12.2/8.12.2/Submit) with ESMTP id gAEEHIDX009169 for ; Thu, 14 Nov 2002 15:17:18 +0100 X-Authentication-Warning: pcl321.mppmu.mpg.de: peb owned process doing -bs Date: Thu, 14 Nov 2002 15:17:17 +0100 (CET) From: Peter Breitenlohner To: xslt@gnome.org Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1803957763-402569313-1037283437=:32738" Subject: [xslt] libxslt-1.0.22 -- libxstl.4, libexslt.4 manpages => man3 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1803957763-402569313-1037283437=:32738 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I really think these manpages ought to be in section 3 (not 4) as per the attached patch. Why: ? 1. They describe library functions => section 3 2. the libxml(3) manpage is in section 3 3. the libxml, libxslt, and libexslt manpages refer (in 'SEE ALSO') to libxslt(3) and libexslt(3) 4. the libxslt manpage even internally ('.TH') claims to belong to section 3! regards Peter Breitenlohner --1803957763-402569313-1037283437=:32738 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="libxslt-1.0.22-changes" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="libxslt-1.0.22-changes" CUZpcnN0IGRvIHRoaXM6DQoJCW12IC12IGxpYnhzbHQvbGlieHNsdC40IGxp YnhzbHQvbGlieHNsdC4zDQoJCW12IC12IGxpYmV4c2x0L2xpYmV4c2x0LjQg bGliZXhzbHQvbGliZXhzbHQuMw0KCWFuZCB0aGVuIGFwcGx5IHRoaXMgcGF0 Y2gNCg0KCVBldGVyIEJyZWl0ZW5sb2huZXIgPHBlYkBtcHBtdS5tcGcuZGU+ DQoNCmRpZmYgLXVyIGxpYnhzbHQtMS4wLjIyLm9yaWcvbGliZXhzbHQvTWFr ZWZpbGUuYW0gbGlieHNsdC0xLjAuMjIvbGliZXhzbHQvTWFrZWZpbGUuYW0N Ci0tLSBsaWJ4c2x0LTEuMC4yMi5vcmlnL2xpYmV4c2x0L01ha2VmaWxlLmFt CTIwMDItMDUtMzEgMDQ6NTU6MTMuMDAwMDAwMDAwICswMjAwDQorKysgbGli eHNsdC0xLjAuMjIvbGliZXhzbHQvTWFrZWZpbGUuYW0JMjAwMi0xMS0xNCAx MToyNzoyOS4wMDAwMDAwMDAgKzAxMDANCkBAIC0zMCw2ICszMCw2IEBADQog bGliZXhzbHRfbGFfTElCQUREID0gJChJTlNUQUxMRURfWFNMVF9MSUIpICQo RVhUUkFfTElCUykNCiBsaWJleHNsdF9sYV9MREZMQUdTID0gLXZlcnNpb24t aW5mbyBATElCRVhTTFRfVkVSU0lPTl9JTkZPQA0KIA0KLW1hbl9NQU5TID0g bGliZXhzbHQuNA0KK21hbl9NQU5TID0gbGliZXhzbHQuMw0KIA0KIEVYVFJB X0RJU1QgPSAkKG1hbl9NQU5TKQ0KZGlmZiAtdXIgbGlieHNsdC0xLjAuMjIu b3JpZy9saWJleHNsdC9saWJleHNsdC4zIGxpYnhzbHQtMS4wLjIyL2xpYmV4 c2x0L2xpYmV4c2x0LjMNCi0tLSBsaWJ4c2x0LTEuMC4yMi5vcmlnL2xpYmV4 c2x0L2xpYmV4c2x0LjMJMjAwMi0wNS0yMiAwNDo1NToyMS4wMDAwMDAwMDAg KzAyMDANCisrKyBsaWJ4c2x0LTEuMC4yMi9saWJleHNsdC9saWJleHNsdC4z CTIwMDItMTEtMTQgMTE6Mjk6MDQuMDAwMDAwMDAwICswMTAwDQpAQCAtMSw0 ICsxLDQgQEANCi0uVEggbGliZXhzbHQgNCAiMTUgTWF5IDIwMDIiDQorLlRI IGxpYmV4c2x0IDMgIjE1IE1heSAyMDAyIg0KIC5TSCBOQU1FDQogbGliZXhz bHQgXC0gZXh0ZW5zaW9uIGxpYnJhcnkgZm9yIFhTTFQNCiAuU0ggREVTQ1JJ UFRJT04NCmRpZmYgLXVyIGxpYnhzbHQtMS4wLjIyLm9yaWcvbGlieHNsdC9N YWtlZmlsZS5hbSBsaWJ4c2x0LTEuMC4yMi9saWJ4c2x0L01ha2VmaWxlLmFt DQotLS0gbGlieHNsdC0xLjAuMjIub3JpZy9saWJ4c2x0L01ha2VmaWxlLmFt CTIwMDItMTAtMTEgMDQ6NTU6MTUuMDAwMDAwMDAwICswMjAwDQorKysgbGli eHNsdC0xLjAuMjIvbGlieHNsdC9NYWtlZmlsZS5hbQkyMDAyLTExLTE0IDEx OjI1OjI1LjAwMDAwMDAwMCArMDEwMA0KQEAgLTUxLDcgKzUxLDcgQEANCiBs aWJ4c2x0X2xhX0xJQkFERCA9ICQoRVhUUkFfTElCUykNCiBsaWJ4c2x0X2xh X0xERkxBR1MgPSAtdmVyc2lvbi1pbmZvIEBMSUJYU0xUX1ZFUlNJT05fSU5G T0ANCiANCi1tYW5fTUFOUyA9IGxpYnhzbHQuNA0KK21hbl9NQU5TID0gbGli eHNsdC4zDQogDQogRVhUUkFfRElTVCA9ICQobWFuX01BTlMpDQogDQo= --1803957763-402569313-1037283437=:32738-- From igor@stud.fh-frankfurt.de Thu Nov 14 14:06:20 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from mailout08.sul.t-online.com (mailout08.sul.t-online.com [194.25.134.20]) by mail.gnome.org (Postfix) with ESMTP id B99DE187A4; Thu, 14 Nov 2002 14:06:19 -0500 (EST) Received: from fwd07.sul.t-online.de by mailout08.sul.t-online.com with smtp id 18CPJg-0005kn-05; Thu, 14 Nov 2002 20:06:16 +0100 Received: from spell.home.loc (510057364475-0001@[217.226.105.12]) by fmrl07.sul.t-online.com with esmtp id 18CPJU-0IssFMC; Thu, 14 Nov 2002 20:06:04 +0100 Received: from 192.168.9.72 (ident=unknown) by spell.home.loc with smtp (MasqMail 0.1.16) id 18CPJl-2Co-00; Thu, 14 Nov 2002 20:06:21 +0100 Message-ID: <003701c28c11$268aabb0$4809a8c0@raven> From: Igor Zlatkovic To: , References: <002201c28bf3$73b2d9d0$4809a8c0@raven> Date: Thu, 14 Nov 2002 20:08:00 +0100 Organization: UAS Frankfurt 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 X-Sender: 510057364475-0001@t-dialin.net Subject: [xslt] Re: [xml] Mingw Lives 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: Igor Zlatkovic List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hi there, Okay, its done. Both libxml and libxslt have native support for Mingw, along with MSVC. Both libraries behave as described in the previous post. Builds are binary compatible to each other, means Mingw-libxslt will happily link to MSVC-libxml and vice-versa, at least dynamically. I have a small dependency problem. :-) When using mingw, typing 'make' will rebuild the whole world no matter what, if anything, has been modified since the last build. MS nmake does not have this symptom, while it has the same dependences in the makefile. This I have no time to track now, so I left it for the better days. :-) Ciao Igor ----- Original Message ----- From: "Igor Zlatkovic" To: Sent: Thursday, November 14, 2002 4:35 PM Subject: [xml] Mingw Lives > Hi there, > > In oder to end the problem at least where I can, I have now integrated mingw > into the JScript-based build. > > The JScript configure accepts a new option "compiler" which can be either > "msvc" or "mingw". The default is "msvc". So, the MSVC user would do a > > C:\> cscript configure.js [...] > C:\> nmake > > to build libxml and friends. Mingw user would do a > > C:\> cscript configure.js compiler=mingw [...] > C:\> make > > and end up with the same result (shared library, static library, xmllint and > test tools). The whole process does not require MSYS or any other posix > layer. > > Note that configuration with compiler=mingw requires GNU make afterwards, > where configuration with compiler=msvc requires Microsoft NMAKE. This is > normal, as the users of the one compiler do not necessarily have the make > tool that belongs to the other. > > Modification requires changes to win32/Makefile.mingw, which is now very > similar to win32/Makefile.msvc. I hope that's okay with you, Elisabeth? > > I'll commit this later today. If everything goes well, libxslt will get the > same. > > Ciao > Igor From veillard@redhat.com Sun Nov 17 13:08:48 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 83727181BA for ; Sun, 17 Nov 2002 13:08:48 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id gAHI8mk07239 for xslt@gnome.org; Sun, 17 Nov 2002 13:08:48 -0500 Date: Sun, 17 Nov 2002 13:08:48 -0500 From: Daniel Veillard To: xslt@gnome.org Message-ID: <20021117130848.G28903@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: [xslt] Release of libxslt-1.0.23 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Yes, time for the Monthly Release: ftp://xmlsoft.org/ and Gnome FTP mirrors http://xmlsoft.org/XSLT/ A number of bug fixes (upgrade of libxml2 to 2.4.27 is recommended for XSLT processing), Windows updates and doc improvements: * Windows build cleanup (Igor) * Unix build and RPM packaging cleanup * Improvement of the python bindings: extension functions and activating EXSLT * various bug fixes: number formatting, portability for bounded string functions, CData nodes, key(), @*[...] patterns * Documentation improvements (John Fleck) * added libxslt.m4 (Thomas Schraitle) Enjoy, 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 m.scheibler@xebec.de Mon Nov 18 04:54:40 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from mx0.xebec.de (xebec.rgbg.r-kom.net [212.77.162.199]) by mail.gnome.org (Postfix) with ESMTP id 2FD8D18164 for ; Mon, 18 Nov 2002 04:54:40 -0500 (EST) Received: from integrator ([192.168.1.11]) by mx0.xebec.de with smtp (Exim 3.35 #2) id 18Dic3-0005Lj-00 for xslt@gnome.org; Mon, 18 Nov 2002 10:54:39 +0100 Message-ID: <001301c28ee8$851555c0$0b01a8c0@intranet.xebec.de> From: "Michael Scheibler" To: Date: Mon, 18 Nov 2002 10:54:43 +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.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [xslt] document() function doesn't work - my fault? Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Hello, my code looks like this: The corresponding document looks like this: ... The error in my httpd error log is this: compilation error: file unknown-000143413712 element variable xsl:variable : could not compile select expression 'document('de.xml')/bundle@language' What did I do wrong? I thought that's the way it should work!! Is it possible, that it just can't find my file? Michael Scheibler From ke@suse.de Mon Nov 18 04:55:01 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by mail.gnome.org (Postfix) with ESMTP id 1A2F118164 for ; Mon, 18 Nov 2002 04:55:00 -0500 (EST) Received: from Hermes.suse.de (Charybdis.suse.de [213.95.15.201]) by Cantor.suse.de (Postfix) with ESMTP id 621111439D for ; Mon, 18 Nov 2002 10:54:59 +0100 (MET) X-Authentication-Warning: frechet.suse.de: ke set sender to ke@suse.de using -f To: xslt@gnome.org Subject: Re: [xslt] Release of libxslt-1.0.23 References: <20021117130848.G28903@redhat.com> From: Karl Eichwalder Date: Mon, 18 Nov 2002 10:54:58 +0100 In-Reply-To: <20021117130848.G28903@redhat.com> (Daniel Veillard's message of "Sun, 17 Nov 2002 13:08:48 -0500") Message-ID: Lines: 35 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.3.50 (i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org List-Help: List-Post: List-Subscribe: , List-Id: The Gnome XSLT library mailing-list List-Unsubscribe: , List-Archive: Daniel Veillard writes: > Yes, time for the Monthly Release: > ftp://xmlsoft.org/ and Gnome FTP mirrors > http://xmlsoft.org/XSLT/ > > A number of bug fixes (upgrade of libxml2 to 2.4.27 is recommended for > XSLT processing), It won't compile with 2.4.23; thus please make use of this patch: 2002-11-18 Karl Eichwalder * configure.in: Set LIBXML_REQUIRED_VERSION to 2.4.27. diff -u /usr/src/ke/libxslt/BUILD/libxslt-1.0.23/configure.in.\~1\~ /usr/src/ke/libxslt/BUILD/libxslt-1.0.23/configure.in --- /usr/src/ke/libxslt/BUILD/libxslt-1.0.23/configure.in.~1~ 2002-11-17 18:11:01.000000000 +0100 +++ /usr/src/ke/libxslt/BUILD/libxslt-1.0.23/configure.in 2002-11-18 10:52:27.000000000 +0100 @@ -11,7 +11,7 @@ LIBEXSLT_MAJOR_VERSION=0 LIBEXSLT_MINOR_VERSION=7 LIBEXSLT_MICRO_VERSION=14 -LIBXML_REQUIRED_VERSION=2.4.23 +LIBXML_REQUIRED_VERSION=2.4.27 LIBXSLT_VERSION=$LIBXSLT_MAJOR_VERSION.$LIBXSLT_MINOR_VERSION.$LIBXSLT_MICRO_VERSION Diff finished at Mon Nov 18 10:52:41 -- Linux frechet 2.4.19-4GB #1 Thu Nov 14 11:46:51 UTC 2002 i686 unknown 10:53am up 2 days, 19:11, 7 users, load average: 0.20, 0.49, 0.48 work : ke@suse.de Karl Eichwalder home : keichwa@gmx.net From veillard@redhat.com Mon Nov 18 05:10:41 2002 Return-Path: Delivered-To: xslt@gnome.org Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by mail.gnome.org (Postfix) with ESMTP id 104A518968 for ; Mon, 18 Nov 2002 05:10:41 -0500 (EST) Received: (from veillard@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) id gAIAAbH16663 for xslt@gnome.org; Mon, 18 Nov 2002 05:10:37 -0500 Date: Mon, 18 Nov 2002 05:10:37 -0500 From: Daniel Veillard To: xslt@gnome.org Subject: Re: [xslt] Release of libxslt-1.0.23 Message-ID: <20021118051037.J28903@redhat.com> References: <20021117130848.G28903@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: ; from ke@suse.de on Mon, Nov 18, 2002 at 10:54:58AM +0100 Sender: xslt-admin@gnome.org Errors-To: xslt-admin@gnome.org X-BeenThere: xslt@gnome.org X-Loop: xslt@gnome.org X-Mailman-Version: 2.0.12 Precedence: bulk Reply-To: xslt@gnome.org X-Reply-To: veillard@redhat.com List-Help: List-Post: