xmlxslt-devel

Re: Help on XSLT template logic! (Prasanna Kumar)

[Geert J. <Gee...@Da...>]

This ought to do it...

Grtz,
Geert

Prasanna Kumar schreef:
> 
> Hi Josten,
> Thanks for the Reply.
> This solves my problem. But one addition to it. I don't know the depth the
> <TEXTELEMENT> can grow upto. Is there anyway by which we can render towards
> the leaf in a loop.
> 
> Thanks
> Prasanna Kumar
> 
> ----- Original Message -----
> From: "Geert Josten" <Gee...@Da...>
> To: "Prasanna Kumar" <agp...@ho...>
> Cc: <xml...@li...>
> Sent: Friday, February 07, 2003 2:26 PM
> Subject: Re: Help on XSLT template logic! (Prasanna Kumar)
> 
> > Hi there,
> >
> > How about something like:
> >
> > <xsl:stylesheet ...>
> >
> > <xsl:template match="COLUMNHEADER">
> >   <table>
> >     <tr>
> >       <xsl:apply-templates select="TEXTELEMENT" />
> >     </tr>
> >     <tr>
> >       <xsl:apply-templates select="*/TEXTELEMENT" />
> >     </tr>
> >     <tr>
> >       <xsl:apply-templates select="*/*/TEXTELEMENT" />
> >     </tr>
> >   </table>
> > </xsl:template>
> >
> > <xsl:template match="TEXTELEMENT">
> >       <td><xsl:value-of select="@DISPLAYNAME" /></td>
> > </xsl:template>
> >
> > </xsl:stylesheet>
> >
> > > Message: 1
> > > From: "Prasanna Kumar" <agp...@ho...>
> > > To: <XML...@ja...>,
> > >         <xer...@xm...>,
> > >         <xml...@li...>,
> > >         <xml...@li...>
> > > Subject: Help on XSLT template logic!
> > > Date: Thu, 6 Feb 2003 18:26:54 +0530
> > >
> > > Hi All,
> > >
> > > I have the Following XML :
> > >
> > > <COLUMNHEADER>
> > >                 <TEXTELEMENT DISPLAYNAME="T1">
> > >                                    <TEXTELEMENT DISPLAYNAME="T11">
> > >                                                             <TEXTELEMENT
> > > DISPLAYNAME="T21"/>
> > >                                                            <TEXTELEMENT
> > > DISPLAYNAME="T22"/>
> > >                                   </TEXTELEMENT>
> > >                                  <TEXTELEMENT DISPLAYNAME="T12">
> > >                                                             <TEXTELEMENT
> > > DISPLAYNAME="T23"/>
> > >                                  </TEXTELEMENT>
> > >               </TEXTELEMENT>
> > >               <TEXTELEMENT DISPLAYNAME="T2">
> > >                                  <TEXTELEMENT DISPLAYNAME="T13">
> > >                                                            <TEXTELEMENT
> > > DISPLAYNAME="T24"/>
> > >                                                            <TEXTELEMENT
> > > DISPLAYNAME="T25"/>
> > >                                   </TEXTELEMENT>
> > >                                 <TEXTELEMENT DISPLAYNAME="T14">
> > >                                                         <TEXTELEMENT
> > > DISPLAYNAME="T26"/>
> > >                                </TEXTELEMENT>
> > >                 </TEXTELEMENT>
> > > </COLUMNHEADER>
> > >
> > > And I require the following HTML output:
> > >
> > >  <table>
> > >   <tr>
> > >    <td>T1</td>
> > >    <td>T2</td>
> > >   </tr>
> > >   <tr>
> > >    <td>T11</td>
> > >    <td>T12</td>
> > >    <td>T13</td>
> > >    <td>T14</td>
> > >   </tr>
> > >   <tr>
> > >    <td>T21</td>
> > >    <td>T22</td>
> > >    <td>T23</td>
> > >    <td>T24</td>
> > >    <td>T25</td>
> > >    <td>T26</td>
> > >   </tr>
> > >
> > > My requirement is to loop through the elements recursively, from top
> level
> > > to the leaf node level and render them,
> > >
> > > how can I achieve this using xsl. what should be my template logic?
> > >
> > > Thanks in Advance,
> > >
> > > Prasanna Kumar
> >

Re: Help on XSLT template logic! (Prasanna Kumar)

[Prasanna K. <agp...@ho...>]

Hi Josten,
Thanks for the Reply.
This solves my problem. But one addition to it. I don't know the depth the
<TEXTELEMENT> can grow upto. Is there anyway by which we can render towards
the leaf in a loop.

Thanks
Prasanna Kumar



----- Original Message -----
From: "Geert Josten" <Gee...@Da...>
To: "Prasanna Kumar" <agp...@ho...>
Cc: <xml...@li...>
Sent: Friday, February 07, 2003 2:26 PM
Subject: Re: Help on XSLT template logic! (Prasanna Kumar)


> Hi there,
>
> How about something like:
>
> <xsl:stylesheet ...>
>
> <xsl:template match="COLUMNHEADER">
>   <table>
>     <tr>
>       <xsl:apply-templates select="TEXTELEMENT" />
>     </tr>
>     <tr>
>       <xsl:apply-templates select="*/TEXTELEMENT" />
>     </tr>
>     <tr>
>       <xsl:apply-templates select="*/*/TEXTELEMENT" />
>     </tr>
>   </table>
> </xsl:template>
>
> <xsl:template match="TEXTELEMENT">
>       <td><xsl:value-of select="@DISPLAYNAME" /></td>
> </xsl:template>
>
> </xsl:stylesheet>
>
> > Message: 1
> > From: "Prasanna Kumar" <agp...@ho...>
> > To: <XML...@ja...>,
> >         <xer...@xm...>,
> >         <xml...@li...>,
> >         <xml...@li...>
> > Subject: Help on XSLT template logic!
> > Date: Thu, 6 Feb 2003 18:26:54 +0530
> >
> > Hi All,
> >
> > I have the Following XML :
> >
> > <COLUMNHEADER>
> >                 <TEXTELEMENT DISPLAYNAME="T1">
> >                                    <TEXTELEMENT DISPLAYNAME="T11">
> >                                                             <TEXTELEMENT
> > DISPLAYNAME="T21"/>
> >                                                            <TEXTELEMENT
> > DISPLAYNAME="T22"/>
> >                                   </TEXTELEMENT>
> >                                  <TEXTELEMENT DISPLAYNAME="T12">
> >                                                             <TEXTELEMENT
> > DISPLAYNAME="T23"/>
> >                                  </TEXTELEMENT>
> >               </TEXTELEMENT>
> >               <TEXTELEMENT DISPLAYNAME="T2">
> >                                  <TEXTELEMENT DISPLAYNAME="T13">
> >                                                            <TEXTELEMENT
> > DISPLAYNAME="T24"/>
> >                                                            <TEXTELEMENT
> > DISPLAYNAME="T25"/>
> >                                   </TEXTELEMENT>
> >                                 <TEXTELEMENT DISPLAYNAME="T14">
> >                                                         <TEXTELEMENT
> > DISPLAYNAME="T26"/>
> >                                </TEXTELEMENT>
> >                 </TEXTELEMENT>
> > </COLUMNHEADER>
> >
> > And I require the following HTML output:
> >
> >  <table>
> >   <tr>
> >    <td>T1</td>
> >    <td>T2</td>
> >   </tr>
> >   <tr>
> >    <td>T11</td>
> >    <td>T12</td>
> >    <td>T13</td>
> >    <td>T14</td>
> >   </tr>
> >   <tr>
> >    <td>T21</td>
> >    <td>T22</td>
> >    <td>T23</td>
> >    <td>T24</td>
> >    <td>T25</td>
> >    <td>T26</td>
> >   </tr>
> >
> > My requirement is to loop through the elements recursively, from top
level
> > to the leaf node level and render them,
> >
> > how can I achieve this using xsl. what should be my template logic?
> >
> > Thanks in Advance,
> >
> > Prasanna Kumar
>

Re: Help on XSLT template logic! (Prasanna Kumar)

[Geert J. <Gee...@Da...>]

Hi there,

How about something like:

<xsl:stylesheet ...>

<xsl:template match="COLUMNHEADER">
  <table>
    <tr>
      <xsl:apply-templates select="TEXTELEMENT" />
    </tr>
    <tr>
      <xsl:apply-templates select="*/TEXTELEMENT" />
    </tr>
    <tr>
      <xsl:apply-templates select="*/*/TEXTELEMENT" />
    </tr>
  </table>
</xsl:template>

<xsl:template match="TEXTELEMENT">
      <td><xsl:value-of select="@DISPLAYNAME" /></td>
</xsl:template>

</xsl:stylesheet>

> Message: 1
> From: "Prasanna Kumar" <agp...@ho...>
> To: <XML...@ja...>,
>         <xer...@xm...>,
>         <xml...@li...>,
>         <xml...@li...>
> Subject: Help on XSLT template logic!
> Date: Thu, 6 Feb 2003 18:26:54 +0530
> 
> Hi All,
> 
> I have the Following XML :
> 
> <COLUMNHEADER>
>                 <TEXTELEMENT DISPLAYNAME="T1">
>                                    <TEXTELEMENT DISPLAYNAME="T11">
>                                                             <TEXTELEMENT
> DISPLAYNAME="T21"/>
>                                                            <TEXTELEMENT
> DISPLAYNAME="T22"/>
>                                   </TEXTELEMENT>
>                                  <TEXTELEMENT DISPLAYNAME="T12">
>                                                             <TEXTELEMENT
> DISPLAYNAME="T23"/>
>                                  </TEXTELEMENT>
>               </TEXTELEMENT>
>               <TEXTELEMENT DISPLAYNAME="T2">
>                                  <TEXTELEMENT DISPLAYNAME="T13">
>                                                            <TEXTELEMENT
> DISPLAYNAME="T24"/>
>                                                            <TEXTELEMENT
> DISPLAYNAME="T25"/>
>                                   </TEXTELEMENT>
>                                 <TEXTELEMENT DISPLAYNAME="T14">
>                                                         <TEXTELEMENT
> DISPLAYNAME="T26"/>
>                                </TEXTELEMENT>
>                 </TEXTELEMENT>
> </COLUMNHEADER>
> 
> And I require the following HTML output:
> 
>  <table>
>   <tr>
>    <td>T1</td>
>    <td>T2</td>
>   </tr>
>   <tr>
>    <td>T11</td>
>    <td>T12</td>
>    <td>T13</td>
>    <td>T14</td>
>   </tr>
>   <tr>
>    <td>T21</td>
>    <td>T22</td>
>    <td>T23</td>
>    <td>T24</td>
>    <td>T25</td>
>    <td>T26</td>
>   </tr>
> 
> My requirement is to loop through the elements recursively, from top level
> to the leaf node level and render them,
> 
> how can I achieve this using xsl. what should be my template logic?
> 
> Thanks in Advance,
> 
> Prasanna Kumar

Help on XSLT template logic!

[Prasanna K. <agp...@ho...>]

Hi All,

I have the Following XML :

<COLUMNHEADER>
                <TEXTELEMENT DISPLAYNAME="T1">
                                   <TEXTELEMENT DISPLAYNAME="T11">
                                                            <TEXTELEMENT
DISPLAYNAME="T21"/>
                                                           <TEXTELEMENT
DISPLAYNAME="T22"/>
                                  </TEXTELEMENT>
                                 <TEXTELEMENT DISPLAYNAME="T12">
                                                            <TEXTELEMENT
DISPLAYNAME="T23"/>
                                 </TEXTELEMENT>
              </TEXTELEMENT>
              <TEXTELEMENT DISPLAYNAME="T2">
                                 <TEXTELEMENT DISPLAYNAME="T13">
                                                           <TEXTELEMENT
DISPLAYNAME="T24"/>
                                                           <TEXTELEMENT
DISPLAYNAME="T25"/>
                                  </TEXTELEMENT>
                                <TEXTELEMENT DISPLAYNAME="T14">
                                                        <TEXTELEMENT
DISPLAYNAME="T26"/>
                               </TEXTELEMENT>
                </TEXTELEMENT>
</COLUMNHEADER>


And I require the following HTML output:

 <table>
  <tr>
   <td>T1</td>
   <td>T2</td>
  </tr>
  <tr>
   <td>T11</td>
   <td>T12</td>
   <td>T13</td>
   <td>T14</td>
  </tr>
  <tr>
   <td>T21</td>
   <td>T22</td>
   <td>T23</td>
   <td>T24</td>
   <td>T25</td>
   <td>T26</td>
  </tr>

My requirement is to loop through the elements recursively, from top level
to the leaf node level and render them,

how can I achieve this using xsl. what should be my template logic?

Thanks in Advance,

Prasanna Kumar

Re: [XML::XSLT] Re: List ending

[Geert J. <Gee...@Da...>]

You can add me as administrator as well. The traffic is low, but whenever someone comes by with a general XSL question it is welcome here and I'll be there to answer it...

Grtz,
Geert

PS: I have been working on an XSL parser in the language MetaMorphosis. Maybe I can use the experience to speed up this Perl version :) (If I find the time somehow)

Jonathan Stowe schreef:
> 
> On 12 Jul 2002, Mark A. Hershberger wrote:
> 
> >
> > They say that SourceForge is where projects go to die and it
> > looks like this one is dead.  At the very least, there is too
> > much spam for me to deal with on a weekly basis (compared with
> > the traffic on the list) to justify continuing the mailing list
> > (in my mind).
> >
> 
> Tell me about it, I administer a number of lists where the majority of
> traffic is (bounced) spam.
> 
> However I don't think that the project is entirely dead - I still think
> there is a need for a pure Perl XSLT processor and I know that there are
> some people using out in the wild.  I have had some recent offers of
> development help and I am planning to write an article on the efficacy of
> the XML::XSLT approach against using an external xslt C library sometime
> this summer - unfortunately my development time is rather thinly spread at
> the moment, I am intending to make a new release to CPAN before the
> autumn however as there are a number of new changes in the CVS which
> people will find useful.  Not dead just pining for the Fjords.
> 
> > So, as of today, I will be discontinuing the xmlxslt-discuss and
> > xmlxslt-devel mailing lists.  If you would like to see the lists
> > continue, you may volunteer to act as the list administrator and
> > I'll hand you control.
> >
> 
> I think that the xmlxslt-devel list should stay - I'm quite happy to take
> over as administrator, the other one I have no feelings about, if anyone
> else has any feelings shout up and I will administer that as well.
> 
> /J\
> --
> Jonathan Stowe                      |
> <http://www.gellyfish.com>          |      This space for rent
>                                     |
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Xmlxslt-discuss mailing list
> Xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlxslt-discuss

Re: List ending

[Jonathan S. <gel...@ge...>]

On 12 Jul 2002, Mark A. Hershberger wrote:

>
> They say that SourceForge is where projects go to die and it
> looks like this one is dead.  At the very least, there is too
> much spam for me to deal with on a weekly basis (compared with
> the traffic on the list) to justify continuing the mailing list
> (in my mind).
>

Tell me about it, I administer a number of lists where the majority of
traffic is (bounced) spam.

However I don't think that the project is entirely dead - I still think
there is a need for a pure Perl XSLT processor and I know that there are
some people using out in the wild.  I have had some recent offers of
development help and I am planning to write an article on the efficacy of
the XML::XSLT approach against using an external xslt C library sometime
this summer - unfortunately my development time is rather thinly spread at
the moment, I am intending to make a new release to CPAN before the
autumn however as there are a number of new changes in the CVS which
people will find useful.  Not dead just pining for the Fjords.

> So, as of today, I will be discontinuing the xmlxslt-discuss and
> xmlxslt-devel mailing lists.  If you would like to see the lists
> continue, you may volunteer to act as the list administrator and
> I'll hand you control.
>

I think that the xmlxslt-devel list should stay - I'm quite happy to take
over as administrator, the other one I have no feelings about, if anyone
else has any feelings shout up and I will administer that as well.

/J\
-- 
Jonathan Stowe                      |
<http://www.gellyfish.com>          |      This space for rent
                                    |

List ending

[<ma...@ev...>]

They say that SourceForge is where projects go to die and it
looks like this one is dead.  At the very least, there is too
much spam for me to deal with on a weekly basis (compared with
the traffic on the list) to justify continuing the mailing list
(in my mind).

So, as of today, I will be discontinuing the xmlxslt-discuss and
xmlxslt-devel mailing lists.  If you would like to see the lists
continue, you may volunteer to act as the list administrator and
I'll hand you control.

Mark.

-- 
Find inner peace and ten thousand around you shall be saved.
		     -- St. Seraphim of Sarov

New release of XML::XSLT

[Jonathan S. <gel...@ge...>]

I have made a new release XML::XSLT to both Sourceforge and CPAN - I have
arbitrarily given it a version number of 0.40.  I have also given it a CVS
tag of 'VERSION-040' if you need to get the release version from CVS.

Whilst it fixes some reported bugs and addresses some feature requests it
should probably be considered an interim release.

In the short term I think some more work needs to be done on the tests as
Devel::Cover reports the existing tests only giving just over 50% coverage
- adding tests for unimplemented XSLT features and having them skipped
might be a good idea and a spur to development :)

Have fun with it :)

/J\
-- 
Jonathan Stowe                      |
<http://www.gellyfish.com>          |      This space for rent
                                    |

[Fwd: Re: XML::XSLT]

[Bron G. <br...@br...>]

-------- Original Message --------
Subject: Re: XML::XSLT
Date: Sun, 16 Dec 2001 19:41:24 +0000 (GMT)
From: Jonathan Stowe <jn...@ge...>
To: Bron Gondwana <br...@br...>



On Thu, 13 Dec 2001, Bron Gondwana wrote:
> Jonathan Stowe said:
> > Hi,
> > I have sent you a patch for XML::XSLT by E-Mail
> > this morning, but looking at the sourceforge
> > there appears to be a number of unapplied patches
> > outstanding.  Do you need any help with an extra
> > developer with (at least a little) spare time - I
> > would like to see the module move forward as I
> > intend to use it for a forthcoming project.
>
> Yes please.
>
> I'd love to release a new copy unto the world (with said patches applied),
> but I haven't had time to look at it for ages (over a year now).  If you'd
> like to take over maintaining, I'd love that too!
>

OK, I have got what could be a 0.34 release ready - I have added all the
outstanding patches and improved the _if() code - I have also added some
more tests.  Now if you could make me a developer on the sourceforge I
will update this stuff to CVS and make a new upload to CPAN :)

The updated code is at
http://petunia.gellyfish.com/modules/XML-XSLT-0.34.tar.gz

Have fun ...

/J\

Johnathan Stowe to take over XML::XSLT development

[Bron G. <br...@br...>]

Since I have no time to work on XML::XSLT (as evidenced by the lack of a 
release for over a year!), I am handing over to Johnathan Stowe 
(gellyfish on Sourceforge), email <jn...@ge...>.

I have createded an admin account for him on Sourceforge, and will be 
handing over responsibility for the CPAN module as well.

Regards,

Bron ( one very slack project admin! )

Re: patch xsl:output

[<dai...@eu...>]

Hi!

No, I believe it is not on. At least, I didn't receive a notification as far as 
I can remember. 

Thanks for the patch! I'll dive into XML::XSLT within two weeks or so and will 
put in the patch if I can! 

Greets, 
Geert 

> 
> > Today's Topics: 
> > 
> >    1. patch to get xsl:output doctype stuff working (Frank Tobin) 
> > 
> > --__--__-- 
> > 
> > Message: 1 
> > Date: Mon, 5 Mar 2001 11:23:37 -0600 (CST) 
> > From: Frank Tobin <ft...@ui...> 
> > To: <xml...@li...> 
> > Subject: patch to get xsl:output doctype stuff working 
> > 
> > Note: please CC me any responses, as I am not on this list. 
> > 
> > I don't know if you guys have automatic notification setup for the Patches 
> > Tracker on SourceForge, so I thought I'd just mail here to let you know 
> > that I uploaded a patch that makes it so that xsl:output doctype stuff 
> > works. 
> > 
> > Patch is #406057, available at 
> > https://sourceforge.net/tracker/index.php? 
> func=detail&aid=406057&group_id=6054&atid=306054 
> > 
> > -- 
> > Frank Tobin http://www.uiuc.edu/~ftobin/ 
> > 
> > 
> 
Quoting xml...@li...:

> Send Xmlxslt-devel mailing list submissions to
> 	xml...@li...
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.sourceforge.net/lists/listinfo/xmlxslt-devel
> or, via email, send a message with subject or body 'help' to
> 	xml...@li...
> 
> You can reach the person managing the list at
> 	xml...@li...
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xmlxslt-devel digest..."
> 
> 
> Today's Topics:
> 
>    1. patch to get xsl:output doctype stuff working (Frank Tobin)
> 
> --__--__--
> 
> Message: 1
> Date: Mon, 5 Mar 2001 11:23:37 -0600 (CST)
> From: Frank Tobin <ft...@ui...>
> To: <xml...@li...>
> Subject: patch to get xsl:output doctype stuff working
> 
> Note: please CC me any responses, as I am not on this list.
> 
> I don't know if you guys have automatic notification setup for the Patches
> Tracker on SourceForge, so I thought I'd just mail here to let you know
> that I uploaded a patch that makes it so that xsl:output doctype stuff
> works.
> 
> Patch is #406057, available at
> https://sourceforge.net/tracker/index.php?
func=detail&aid=406057&group_id=6054&atid=306054
> 
> -- 
> Frank Tobin		http://www.uiuc.edu/~ftobin/
> 
> 
> 
> 
> --__--__--
> 
> _______________________________________________
> Xmlxslt-devel mailing list
> Xml...@li...
> http://lists.sourceforge.net/lists/listinfo/xmlxslt-devel
> 
> 
> End of Xmlxslt-devel Digest
> 
> 
> 

Re: patch xsl:output

[<dai...@eu...>]

No, I believe it is not on. At least, I didn't receive a notification as far as 
I can remember.

Thanks for the patch! I'll dive into XML::XSLT within two weeks again, and put 
the patch in if I can!

Greets,
Geert

> Today's Topics:
> 
>    1. patch to get xsl:output doctype stuff working (Frank Tobin)
> 
> --__--__--
> 
> Message: 1
> Date: Mon, 5 Mar 2001 11:23:37 -0600 (CST)
> From: Frank Tobin <ft...@ui...>
> To: <xml...@li...>
> Subject: patch to get xsl:output doctype stuff working
> 
> Note: please CC me any responses, as I am not on this list.
> 
> I don't know if you guys have automatic notification setup for the Patches
> Tracker on SourceForge, so I thought I'd just mail here to let you know
> that I uploaded a patch that makes it so that xsl:output doctype stuff
> works.
> 
> Patch is #406057, available at
> https://sourceforge.net/tracker/index.php?
func=detail&aid=406057&group_id=6054&atid=306054
> 
> -- 
> Frank Tobin		http://www.uiuc.edu/~ftobin/
> 
> 

patch to get xsl:output doctype stuff working

[Frank T. <ft...@ui...>]

Note: please CC me any responses, as I am not on this list.

I don't know if you guys have automatic notification setup for the Patches
Tracker on SourceForge, so I thought I'd just mail here to let you know
that I uploaded a patch that makes it so that xsl:output doctype stuff
works.

Patch is #406057, available at
https://sourceforge.net/tracker/index.php?func=detail&aid=406057&group_id=6054&atid=306054

-- 
Frank Tobin		http://www.uiuc.edu/~ftobin/

Re: Xmlxslt-devel: Patch for <xsl:output>

[<dai...@eu...>]

Thanks for submitting the patch...
About public and system that doesn't work: I believe that xml::dom didn't 
support altering the doctype-nodes, that is why support is still not properly 
implemented, I guess...

Greets,
Geert

Quoting xml...@li...:

> Send Xmlxslt-devel mailing list submissions to
> 	xml...@li...
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.sourceforge.net/lists/listinfo/xmlxslt-devel
> or, via email, send a message with subject or body 'help' to
> 	xml...@li...
> 
> You can reach the person managing the list at
> 	xml...@li...
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xmlxslt-devel digest..."
> 
> 
> Today's Topics:
> 
>    1. XML::XSLT omit-xml-declaration and doctype's (Frank Tobin)
> 
> --__--__--
> 
> Message: 1
> Date: Fri, 23 Feb 2001 07:24:27 -0600 (CST)
> From: Frank Tobin <ft...@ui...>
> To: <xml...@li...>, <ma...@ev...>
> Subject: XML::XSLT omit-xml-declaration and doctype's
> 
> XML::XSLT 0.32 has a bug where it faults if <xsl:output> is used, but the
> attribute omit-xml-declaration is not defined.  I've traced the bug, and
> the patch at the end of this message will fix this problem.
> 
> In another bug I've found, <xsl:output> does not seem to support
> doctype-public or doctype-system yet; I see the code for it, but it just
> doesn't seem to go through.
> 
> I noticed that the last two versions of XSLT aren't on SourceForge; is
> there a reason for this?
> 
> I'll put this patch in the patch submission page for the project, too.
> 
> Index: lib/XML/XSLT.pm
> ===================================================================
> RCS file: /cvsroot/xmlxslt/XML-XSLT/lib/XML/XSLT.pm,v
> retrieving revision 1.4
> diff -u -r1.4 XSLT.pm
> --- lib/XML/XSLT.pm	2001/01/23 04:03:02	1.4
> +++ lib/XML/XSLT.pm	2001/02/23 13:23:09
> @@ -555,8 +555,7 @@
>      $self->{METHOD} = $method->getNodeValue if defined $method;
> 
>      my $omit = $attribs->getNamedItem('omit-xml-declaration');
> -    $self->{OMIT_XML_DECL} = defined $omit->getNodeValue ?
> -      $omit->getNodeValue : 'no';
> +    $self->{OMIT_XML_DECL} = $omit ? $omit->getNodeValue : 'no';
> 
>      if ($self->{OMIT_XML_DECL} ne 'yes' && $self->{OMIT_XML_DECL} ne
> 'no') {
>        $self->warn(qq{Wrong value for attribute "omit-xml-declaration"
> in\n\t} .
> 
> 
> -- 
> Frank Tobin		http://www.uiuc.edu/~ftobin/
> 
> 
> 
> 
> 
> 
> 
> --__--__--
> 
> _______________________________________________
> Xmlxslt-devel mailing list
> Xml...@li...
> http://lists.sourceforge.net/lists/listinfo/xmlxslt-devel
> 
> 
> End of Xmlxslt-devel Digest
> 
> 
> 

XML::XSLT omit-xml-declaration and doctype's

[Frank T. <ft...@ui...>]

XML::XSLT 0.32 has a bug where it faults if <xsl:output> is used, but the
attribute omit-xml-declaration is not defined.  I've traced the bug, and
the patch at the end of this message will fix this problem.

In another bug I've found, <xsl:output> does not seem to support
doctype-public or doctype-system yet; I see the code for it, but it just
doesn't seem to go through.

I noticed that the last two versions of XSLT aren't on SourceForge; is
there a reason for this?

I'll put this patch in the patch submission page for the project, too.

Index: lib/XML/XSLT.pm
===================================================================
RCS file: /cvsroot/xmlxslt/XML-XSLT/lib/XML/XSLT.pm,v
retrieving revision 1.4
diff -u -r1.4 XSLT.pm
--- lib/XML/XSLT.pm	2001/01/23 04:03:02	1.4
+++ lib/XML/XSLT.pm	2001/02/23 13:23:09
@@ -555,8 +555,7 @@
     $self->{METHOD} = $method->getNodeValue if defined $method;

     my $omit = $attribs->getNamedItem('omit-xml-declaration');
-    $self->{OMIT_XML_DECL} = defined $omit->getNodeValue ?
-      $omit->getNodeValue : 'no';
+    $self->{OMIT_XML_DECL} = $omit ? $omit->getNodeValue : 'no';

     if ($self->{OMIT_XML_DECL} ne 'yes' && $self->{OMIT_XML_DECL} ne
'no') {
       $self->warn(qq{Wrong value for attribute "omit-xml-declaration"
in\n\t} .


-- 
Frank Tobin		http://www.uiuc.edu/~ftobin/

FW: [XML::XSLT] getting XML declaration and DOCTYPE to work

[Vincent L. <vin...@an...>]

-----Original Message-----
From: dai...@eu... [mailto:dai...@eu...]
Sent: Thursday, February 08, 2001 9:13 AM
To: Vincent Loach
Cc: xml...@li...
Subject: Re: [XML::XSLT] getting XML declaration and DOCTYPE to work



Although I was the one that wrote the initial versions, I cannot help with
the 
function serve. (Who wrote that one!!??)

Forward this message to xml...@li..., maybe one of
the 
current developers has time to look into your problem.

I can at least tell this. The last version I delivered didn't support the 
<xsl:output> tag...


Greets,
Geert


Quoting Vincent Loach <vin...@an...>:

> 
> A note about my recent experiences with XML::XSLT.
> 
> Ananova wants to run arbitrary translations on XML documents, but unlike
> most XSL users she wants to transform XML from one format to another (i.e.
> two different DTDs with a common subset of conceptual items). She also
wants
> 'non-programmers' to do the transformations, so XSL seemed a good choice.
A
> programmer (me) will write a high level mechanism to process the
> transformations. Ananova prefers to do this kind of thing in Perl.
> 
> Here are some very noddy test documents (yes, I know they produce invalid
> XML):
> 
> p.xml:
> 	<?xml version="1.0" encoding="UTF-8"?>
> 	<test><p>test para</p></test>
> 
> x.xsl:
> 	<?xml version="1.0" ?>
> 	<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> version="1.0">
> 	<xsl:output method="xml" omit-xml-declaration="no"
> doctype-system="http://content.ananova.com/dtd/story.dtd" />
> 	<xsl:template match="/">
> 	<story>
> 	<xsl:value-of select="/test/p"/>
> 	</story>
> 	</xsl:template>
> 	</xsl:stylesheet>
> 
> If we run that using a Xalan XSLT mechanism:
> 	java org.apache.xalan.xslt.Process -in p.xml -xsl x.xsl -out ./test
> 
> we get:
> 	<?xml version="1.0" encoding="UTF-8"?>
> 	<!DOCTYPE story SYSTEM "http://content.ananova.com/dtd/story.dtd">
> 	<story>test para</story>
> 
> which is reasonable.
> 
> 
> I then write a simple Perl program (txslt.pl):
> 	use XML::XSLT;
> 
> 	$xsl = shift( @ARGV );
> 	$xmlfile = shift( @ARGV );
> 
> 	my $xslt = XML::XSLT->new( $xsl );
> 
> 	$xslt->transform( $xmlfile );
> 	print $xslt->toString;
> 
> 	$xslt->dispose();
> 
> to test things out. This produces:
> 
> 	<story>
> 	test para
> 	</story>
> 
> with no XML header or DOCTYPE declaration, which is a problem for Ananova.
> 
> 
> Eventually, I work out that if txslt.pl uses:
> 
> 	print $xslt->serve( $xmlfile, xml_declaration => 1, http_headers =>
> 0 );
> 
> Then I can get:
> 
> 	<?xml version="1.0" encoding="UTF-8"?>
> 
> 	<story>
> 	test para
> 	</story>
> 
> which still does not have a DOCTYPE.
> 
> I looked at the examples, mailing list archive and tried various things
> (using CDATA), and I *could* get a DOCTYPE out, as long as I didn't mind
if
> being "&lt;!DOCTYPE", which still meant post-processing the output.
> 
> I looked at the source code and noticed that a deprecated subroutine
> "print_output" seemed to do something similar to what I wanted. I could
not
> see what looked like equivalent code in "serve" though.
> 
> So, eventually, I hacked around with the "serve" subroutine to create
> something like what I want. This will work for Ananova, but I haven't
really
> considered the overall effects of this on *other* types (i.e. HTML) of
> processing. Here's my hacked version:
> 
> sub serve {
>   my $self = shift;
>   my $class = ref $self || croak "Not a method call";
>   my %args = $self->__parse_args(@_);
>   my $ret;
>   my $extra;
> 
>   $args{http_headers}    = 1 unless defined $args{http_headers};
>   $args{xml_declaration} = 1 unless defined $args{xml_declaration};
>   $args{xml_version}     = "1.0" unless defined $args{xml_version};
>   $args{doctype}         = "SYSTEM" unless defined $args{doctype};
>   $args{clean}           = 0 unless defined $args{clean};
> 
>   $ret = $self->transform($args{Source})->toString;
> 
>   if($args{clean}) {
>     eval {require HTML::Clean};
> 
>     if($@) {
>       CORE::warn("Not passing through HTML::Clean -- install the module");
>     } else {
>       my $hold = HTML::Clean->new(\$ret);
>       $hold->strip;
>       $ret = ${$hold->data};
>     }
>   }
> 
>   if($args{xml_declaration}) {
>     $extra = '<?xml version="' . $args{xml_version} . '"
> encoding="UTF-8"?>'.
>       "\n";
>   }
> 
>   if($args{http_headers}) {
>     $extra = "Content-Type: " . $self->media_type . "\n" .
>       "Content-Length: " . length($ret) . "\n\n";
>   }
> 
>   if ( $self->{METHOD} eq 'xml' ) {
>     if ($self->{DOCTYPE_SYSTEM}) {
>       my $root_name =
>
$self->{RESULT_DOCUMENT}->getElementsByTagName('*',0)->item(0)->getTagName;
>       if ($self->{DOCTYPE_PUBLIC}) {
>     $extra .= qq{<!DOCTYPE $root_name PUBLIC "} . $self->{DOCTYPE_PUBLIC}
.
>       qq{" "} . $self->{DOCTYPE_SYSTEM} . qq{">\n};
>       } else {
>     $extra .= qq{<!DOCTYPE $root_name SYSTEM "} . $self->{DOCTYPE_SYSTEM}
.
> qq{">\n};
>       }
>     }
>   }
> 
>   return $extra . $ret;
> }
> 
> (I can't quite see what $args{doctype} really achieves in the above).
> 
> So now I get:
> 
> 	<?xml version="1.0" encoding="UTF-8"?>
> 	<!DOCTYPE story SYSTEM "http://content.ananova.com/dtd/story.dtd">
> 
> 	<story>
> 	test para
> 	</story>
> 
> which Ananova likes.
> 
> I don't know if anyone is interested in the above, but I need to write it
up
> anyway to add to notes here to explain why the local version of XML::XSLT
> has been modified.
> 
> The only thing bothering me now is that I may have missed something really
> obvious and worked around the houses, when all I needed to know was one
> extra option to pass in somewhere. I'm sure someone will let me know :-)
> 
> Vincent Loach
> Programmer
> 
> Direct Line:	+44 (0)113 367 4513
> Switchboard:	+44 (0)845 121 6060
> Fax:		+44 (0)845 121 5060
> Mobile:			+44 (0)7977 171135
> Email:		vin...@an...
> 
> http://www.ananova.com
> 
> Ananova Ltd
> Marshall Mill
> Marshall Street
> Leeds LS11 9YJ
> 
> Registered Office:
> St James Court
> Great Park Road
> Almondsbury Park
> Bradley Stoke
> Bristol BS32 4QJ
> Registered in England No.2858918
> 
> The information transmitted is intended only for the person or entity to
> which it is addressed
> and may contain confidential and/or privileged material.  Any review,
> retransmission, 
> dissemination or other use of, or taking of any action in reliance upon,
> this information by
> persons or entities other than the intended recipient is prohibited.  If
you
> receive this in
> error, please contact the sender and delete the material from any
computer.
> 
> 
> _______________________________________________
> Xmlxslt-discuss mailing list
> Xml...@li...
> http://lists.sourceforge.net/lists/listinfo/xmlxslt-discuss
> 
> 
> 

Re: [XML::XSLT] Re: XML::XPath

[Geert J. <Gee...@Da...>]

> # Yes, a resulting node-set is incompatible... I was only thinking that far
> # most xpath-expressions are used to select a value with xsl:value-of. That
> # function always returns one of the simplest variable types, string or
> # number... In those cases the result of XPath is just the value.
> 
>   yes, but you have to parse the file twice - once for DOM and once for
>   XPath - perhaps we can forget DOM and use XPath DOMish API only...
> 
>   Pavel

The latter idea is a nice consideration, but requires that the full length of XSLT.pm has to be rewritten. It will definitely mean a gain in speed, without doubt, unless the stripped down version of the DOM-tree that the XPath-module uses has too little support to manipulate trees for transformation purposes; that is not what XPath was meant for...

About the first: yes, the xml has to be parsed twice, but reading in the XML is not the bottleneck! :) The real bottleneck is the 'speed' of DOM-function. The other bottleneck is memory-usage, but that can only be solved by incorporating memory-swapping techniques. And doing that in Perl?? Hmmm.... :P

Geert

Re: XML::XPath

[Pavel N. <bi...@at...>]

On Fri, Jan 05, 2001 at 10:46:14AM +0100, Geert Josten wrote:
# Yes, a resulting node-set is incompatible... I was only thinking that far
# most xpath-expressions are used to select a value with xsl:value-of. That
# function always returns one of the simplest variable types, string or
# number... In those cases the result of XPath is just the value.

  yes, but you have to parse the file twice - once for DOM and once for
  XPath - perhaps we can forget DOM and use XPath DOMish API only...

  Pavel

Re: XML::XPath

[Geert J. <Gee...@Da...>]

Yes, a resulting node-set is incompatible... I was only thinking that far most xpath-expressions are used to select a value with xsl:value-of. That function always returns one of the simplest variable types, string or number... In those cases the result of XPath is just the value.

Oh, I forgot that XPath is also used for xsl:variable, one can store the resulting node-set in a variable. Maybe it is possible to manipulate the resulting tree so that becomes a DOM-tree. If the structures resemble each other enough, it might even be done relatively quick.

Other alternative: parse the XPath expression and construct a block of perl-code to retrieve the set, saving as much variable usage as possible and saving many function-calls as well. Though the parsing itself may cancel the gain of speed...

Greets,
Geert


Pavel Nejedly wrote:
> 
> On Fri, Jan 05, 2001 at 09:39:44AM +0100, Geert Josten wrote:
> # I am convinced that XML::XPath can be used very easily for getting node-set
> # selections (xsl:value-of etc.). Anyone comment on this? Anyone interested?
> 
>   Hmmm... But it's incompatible with XML::DOM (or is it?)
>   But I agree that XML::XPath would help us...
> 
>   Pavel

XML::XPath

[Geert J. <Gee...@Da...>]

Hi all,

I am convinced that XML::XPath can be used very easily for getting node-set selections (xsl:value-of etc.). Anyone comment on this? Anyone interested?

Greets,
Geert

Re: not a HASH (a short patch)

[Geert J. <Gee...@Da...>]

Hi,

Comment out line 503, by putting a # before 'local', that will help..
(cannot try myself, but since I placed the code there myself, I'm pretty convinced that will fix your problem.)

Greets,
Geert

>    2. BUG: Not a HASH reference? (Janus Liebregts)
> 
> --__--__--
> 
> Message: 2
> Date: Thu, 04 Jan 2001 17:47:29 +0100
> From: Janus Liebregts <ja...@li...>
> To: xml...@li...
> Subject: BUG: Not a HASH reference?
> 
> Hi,
> 
> Strugling with XML XSLT and PERL, I used the 0.24 version of XML::XSLT
> 
> everytime my script fails with this error:
> 
> Not a HASH reference at /usr/lib/perl5/site_perl/XML/XSLT.pm line 492
> 
> using this script:
> 
> use XML::XSLT;
> $xslfile = "$ENV{DOCUMENT_ROOT}/de.xsl";
> my $parser = XML::XSLT->new ($xslfile, "FILE", warnings => "Active");
> $parser->transform_document ("$ENV{DOCUMENT_ROOT}/Bewoners/links.xml",
> "FILE");
> $parser->print_result("$ENV{DOCUMENT_ROOT}/Bewoners/linksnew.xml");
> $parser->dispose ();
> 
> regards,
> janus

BUG: Not a HASH reference?

[Janus L. <ja...@li...>]

Hi,

Strugling with XML XSLT and PERL, I used the 0.24 version of XML::XSLT

everytime my script fails with this error:

Not a HASH reference at /usr/lib/perl5/site_perl/XML/XSLT.pm line 492

using this script:

use XML::XSLT;
$xslfile = "$ENV{DOCUMENT_ROOT}/de.xsl";
my $parser = XML::XSLT->new ($xslfile, "FILE", warnings => "Active");
$parser->transform_document ("$ENV{DOCUMENT_ROOT}/Bewoners/links.xml",
"FILE");
$parser->print_result("$ENV{DOCUMENT_ROOT}/Bewoners/linksnew.xml");
$parser->dispose ();

regards,
janus

Re: Is this list alive?

[Geert J. <Gee...@Da...>]

Hi,

About this specific list, I'm not sure, but there is also the list
xml...@li.... See xmlxslt.sourceforge.net for the archives.

The project is not dead, but me and the other developers have either a lot to do or have migrated most activity to different projects like experimenting with the XML::XPath module.

I at least am available to answer any of your questions and I might be able to pick up developing again...

Greets,
Geert


> Today's Topics:
> 
>    1. is this list alive? (Zack Brown)
> 
> --__--__--
> 
> Message: 1
> Date: Tue, 2 Jan 2001 20:03:44 -0800 (PST)
> From: Zack Brown <zb...@li...>
> To: xml...@li...
> Subject: is this list alive?
> 
> Hi,
> 
> I've just started using XSL::XSLT, but when I went to look over the list
> archives, the most recent post seems to be from September. Is the list
> alive? Is the project maintained? Is there a different module that folks
> have migrated to?
> 
> Thanks,
> Zack
> 
> --
> Zack Brown, Linuxcare, Inc.
> tel: 1-415-354-4878x284, fax: 1-415-701-7457
> zb...@li..., http://www.linuxcare.com/
> Linuxcare. Support for the revolution.
> 
> --__--__--
> 
> _______________________________________________
> Xmlxslt-devel mailing list
> Xml...@li...
> http://lists.sourceforge.net/mailman/listinfo/xmlxslt-devel
> 
> End of Xmlxslt-devel Digest

is this list alive?

[Zack B. <zb...@li...>]

Hi,

I've just started using XSL::XSLT, but when I went to look over the list
archives, the most recent post seems to be from September. Is the list
alive? Is the project maintained? Is there a different module that folks
have migrated to?

Thanks,
Zack

-- 
Zack Brown, Linuxcare, Inc.
tel: 1-415-354-4878x284, fax: 1-415-701-7457
zb...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [eugene@snailgem.org: [XML::XSLT] XML::XSLT homepage]

[Pavel N. <bi...@at...>]

On Sun, Sep 24, 2000 at 03:13:49PM -0500, Mike808 wrote:
# I don't think it is the stylesheet. Netscape is rendering the <H#>
# tags in the Comic Sans font.

  by default?
  ok, I can set hx to be Times or anything you like :)

# Is what you're hosting what you checked out from the repository?

  yes, with the fixes applied. 

# I'd very much like to see Egon's example content restored, since I 
# think that was a major part of what was missing (as well as prior
# releases).
# The most glaring problem was that there is no download
# available from the site. It probably ought to point them to the
# Sourceforge download area rather than retain the older content.

  That's exactly what I did! :
  * download link goes into sourceforge download area
  * previous releases are located in 
    ftp://xmlxslt.sourceforge.net/pub/xmlxslt/historical
  * examples will go to
    http://xmlsxslt.souceforge.net/examples

# Also, there's some webalyzer statistics that can be viewed, but I
# can't seem to get cron working on the new host. Haven't had time
# to look into it yet.

  And do we need it? Isn't SourceForge statistics enough?

# And I think either Marc or Bron worked
# out a trick with the web pages being in the CVS repository and
# being extracted automatically.

  I know - I've seen it in CVS repository. I suppose it's working,
  but if it's not I can copy it manually on shell1.

  Pavel