You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(34) |
Aug
(21) |
Sep
(8) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(8) |
Feb
(3) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2003 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
(6) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2004 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
From: <aiq...@gm...> - 2005-12-14 18:13:48
|
亲爱的爱情BBS会员: 您好! 您好久没有光顾“爱情BBS”了, 您最近是不是很忙,千万注意保重身体。爱情BBS成为中国最好的爱情社区,少不了您的支持。 爱情BBS 新开设: *免费性教育电影片* 观看 *两性健康* 性交技巧* 等栏目 地址: http://www.aiqingbbs.com 感谢您继续支持我们! 此为系统发送,请勿直接回复! 爱情BBS 2005.12.15 |
From: Eckenrode, G. <c-G...@td...> - 2005-07-15 11:33:50
|
Mark, Thanks ! I did a quick ppm search and install for XML-XSLT and found nothing. But, I will try other means too. I appreciate your getting back to me. George -----Original Message----- From: Mark A. Hershberger To: Eckenrode, George; Jonathan Stowe Cc: XML-XSLT Devel Sent: 7/14/2005 3:47 PM Subject: XML::XSLT Thanks for your interest in XML::XSLT. However, I am no longer involved in the project. Try emailing Jonathan Stowe -- I know he's worked on it more recently than me. Also, if it is possible, you might look into XML::LibXSLT. I'm sorry I couldn't be of more direct assistance. >First, let me say that I am really at the end of my rope and that is the >only reason why I am attempting to ask you for a little help. > >I am using PERL and XML::XSLT and have two questions: > >1. I can set two variables equal to two values but cannot seem to do >internal computation ( <xsl:value-of select="$gross + $payoff)"/> both >variables can be displayed with their correct values but the above comes up >with blank in the output. Is this available to be done ? > >2. Inside a choose and when can I do anything with a value of an element in >the TEST compare ? I cannot seem to get that working either. > >HONESTLY, I appreciate that this is a work in progress etc. but I have >searched EVERYWHERE trying to get these things to work without any success. > > >Thanks. > >George > > > |
From: Mark A. H. <ma...@ev...> - 2005-07-14 19:50:09
|
Thanks for your interest in XML::XSLT. However, I am no longer involved in the project. Try emailing Jonathan Stowe -- I know he's worked on it more recently than me. Also, if it is possible, you might look into XML::LibXSLT. I'm sorry I couldn't be of more direct assistance. >First, let me say that I am really at the end of my rope and that is the >only reason why I am attempting to ask you for a little help. > >I am using PERL and XML::XSLT and have two questions: > >1. I can set two variables equal to two values but cannot seem to do >internal computation ( <xsl:value-of select="$gross + $payoff)"/> both >variables can be displayed with their correct values but the above comes up >with blank in the output. Is this available to be done ? > >2. Inside a choose and when can I do anything with a value of an element in >the TEST compare ? I cannot seem to get that working either. > >HONESTLY, I appreciate that this is a work in progress etc. but I have >searched EVERYWHERE trying to get these things to work without any success. > > >Thanks. > >George > > > |
From: Carter T. <cth...@ou...> - 2005-01-05 17:59:25
|
> -----Original Message----- > From: Jonathan Stowe [mailto:jn...@ge...]=20 >=20 > On Wed, 2004-12-29 at 21:43, Carter Thompson wrote: > > Hi All, > >=20 > > I need some pointers on either how to get the XML::XSLT=20 > module to work=20 > > or finding another module to take its place. The problem=20 > is with the=20 > > named attributes, instead of generating an html file with=20 > the correct=20 > > contents in each cell I'm getting data from the "comment"=20 > field in all=20 > > of the cells. I'm guessing that XML::XSLT isn't quite ready, right? > >=20 >=20 > The trouble with XML::XSLT is that doesn't handle quite a lot=20 > of the XPath expressions that it should do. >=20 > Assuming that the output you are expecting is something like:=20 > <html><body> <h2>Patches</h2> <table border=3D"1"> <tr=20 > bgcolor=3D"#CECECE"> <th align=3D"left">Patch</th> <th=20 > align=3D"left">Bug</th> <th align=3D"left">Version</th> </tr>=20 > <tr> <td>patch-5.tar.gz</td> <td>13933</td> <td>3.1.1</td>=20 > </tr> </table> </body></html> >=20 > (which is the output from libxslt), I will add this a test=20 > case for the module so it can get fixed at some point .... Jonathan, Thanks very much. Adding the above as a test case would be appreciated. If you need additional information please don't hesitate to ask. =20 Cheers, Carter. |
From: Jonathan S. <jn...@ge...> - 2005-01-05 09:05:56
|
On Wed, 2004-12-29 at 21:43, Carter Thompson wrote: > Hi All, > > I need some pointers on either how to get the XML::XSLT module to work > or finding another module to take its place. The problem is with the > named attributes, instead of generating an html file with the correct > contents in each cell I'm getting data from the "comment" field in all > of the cells. I'm guessing that XML::XSLT isn't quite ready, right? > The trouble with XML::XSLT is that doesn't handle quite a lot of the XPath expressions that it should do. Assuming that the output you are expecting is something like: <html><body> <h2>Patches</h2> <table border="1"> <tr bgcolor="#CECECE"> <th align="left">Patch</th> <th align="left">Bug</th> <th align="left">Version</th> </tr> <tr> <td>patch-5.tar.gz</td> <td>13933</td> <td>3.1.1</td> </tr> </table> </body></html> (which is the output from libxslt), I will add this a test case for the module so it can get fixed at some point .... /J\ -- This e-mail is sponsored by http://www.integration-house.com/ |
From: Jonathan S. <jn...@ge...> - 2004-06-03 15:37:01
|
On Fri, 2004-05-28 at 05:09, Geoff Capper wrote: > Hi all, > > First thanks for creating and maintaining XML:XSLT, it's great! My > apologies if posting attachments is frowned upon, please let me know the > correct procedures. > Well as you will have seen it will cause some delay to your message reaching the list, this compounded by the fact that I had forgotten the list admin password. Ideally we would get changes as a patch to the latest version of the file from the CVS (or just made and committed to the CVS .) > I have altered the module to implement the name() and local-name() > functions, though the name() implementation doesn't support a node-set > yet, the local-name() does, and it doesn't break any of your tests. > SOunds good - but do you have a test to support it :-) Seriously, thanks for this I am always happy to have functionality supported. > My question is related to the following (it may be that I lack enough > knowledge of XSLT and that my mistake is therefore in this rather than > the implementation of the function.): > > If I have xml such as: > > <structure> > <nucleus> > <protons>1</protons> > <neutrons>0</neutrons> > </nucleus> > </structure> > > and an xsl template: > > <xsl:template match="structure"> > <xsl:value-of select="local-name(nucleus/*[0])"/> > </xsl:template> > > it returns "neutrons" wheras if my template says: > > <xsl:value-of select="local-name(nucleus/*)"/> > > it will return "protons" > > Is this an error in my understanding of xslt or just the way I have > implemented the function? Shouldn't /* and /*[0] both refer to the first > child in this context (the xpath spec says just act on the first child > for this function) > I think this should be the other way round, I think the unqualified * will return the last value and the qualified should return the first (or whichever index it has). Usually the way I sort this out is try it with some other xslt processor or two to see what they do - if I get a minute I'll try xsltproc and sabcmd, though this is unlikely before next week. > Also, if these additions are in accordance with the specs and useful, > are they in the right place? Should any changes be made to add them to > the module? > As I say, ideally we would get them as a patch and with tests that can be placed in the t/ directory of the distribution - you will probably find some example xml, xslt and result in the NIST test suite. Alternatively I could make you a developer on the project and you could commit the changes to CVS yourself - of course you will still have to make the tests :-) Mail me off-list with your sourceforge id if you want to sign-up. Thanks again for the work. /J\ |
From: Jonathan S. <jn...@ge...> - 2004-06-02 07:47:22
|
On Tue, 2004-06-01 at 19:49, John Bywater wrote: > Hey Gellyfish! > > > > Thanks for picking the patch up. > > > > I was just curious about when the code changes may appear on > > CPAN. What do you think might happen? I had to change the patch to use UNIVERSAL::isa($args{Source},'XML::DOM::Document') instead of the object method as it would fail when the $args{Source} wasn't blessed. I had already fixed the $_ - [0] things previously so that didn't apply. It is unlikely I am able to do a release to CPAN for a while as I am rather busy with work. There are a number of other things that need to go in and/or be fixed before, Anyway thanks again for the patch. If you feel that you have the time I would be quite happy for you to become a developer on the project. /J\ |
From: Geoff C. <geo...@oz...> - 2004-05-28 04:09:08
|
Hi all, First thanks for creating and maintaining XML:XSLT, it's great! My apologies if posting attachments is frowned upon, please let me know the correct procedures. I have altered the module to implement the name() and local-name() functions, though the name() implementation doesn't support a node-set yet, the local-name() does, and it doesn't break any of your tests. My question is related to the following (it may be that I lack enough knowledge of XSLT and that my mistake is therefore in this rather than the implementation of the function.): If I have xml such as: <structure> <nucleus> <protons>1</protons> <neutrons>0</neutrons> </nucleus> </structure> and an xsl template: <xsl:template match="structure"> <xsl:value-of select="local-name(nucleus/*[0])"/> </xsl:template> it returns "neutrons" wheras if my template says: <xsl:value-of select="local-name(nucleus/*)"/> it will return "protons" Is this an error in my understanding of xslt or just the way I have implemented the function? Shouldn't /* and /*[0] both refer to the first child in this context (the xpath spec says just act on the first child for this function) Also, if these additions are in accordance with the specs and useful, are they in the right place? Should any changes be made to add them to the module? Cheers, Geoff |
From: Jonathan S. <jn...@ge...> - 2004-04-22 08:12:02
|
On Wed, 2004-04-21 at 21:30, per...@ro... wrote: > Hello, I am interested in perhaps using the perl module to generate > html from xml data and xsl stylesheets. > > I have a large xml file that is accessed by an xsl stylesheet that > performs multiple iterations to render a complex html page on the fly. > I am using msxml and it is working quite well. > > For making static pages (where ALL of the data is stored in the html > page - and there is no longer a link to the xsl or xml files), I have > used Saxon which is VERY slow. > > Could your module be capable of creating a static html page from the > xml and xsl files? > Sure, XML::XSLT would do this for most XSLT stylesheets, however if you are finding Saxon slow it is likely you are going to find this module even slower - particularly on large xml files - as it is written entirely in Perl. If you are looking for a Perl module that is likely to be quicker than Saxon you might want to to look at XML::LibXSLT which in some benchmarks I have seen does seem to be a lot quicker. /J\ |
From: <per...@ro...> - 2004-04-21 20:41:16
|
Hello, I am interested in perhaps using the perl module to generate html from xml data and xsl stylesheets. I have a large xml file that is accessed by an xsl stylesheet that performs multiple iterations to render a complex html page on the fly. I am using msxml and it is working quite well. For making static pages (where ALL of the data is stored in the html page - and there is no longer a link to the xsl or xml files), I have used Saxon which is VERY slow. Could your module be capable of creating a static html page from the xml and xsl files? Any help would be appreciated. Regards, Perrik 1 |
From: Bernhard W. <ber...@we...> - 2004-03-25 15:24:43
|
<html><style>p {margin: 0px}</style><body bgcolor='#ffffff' style='font-size:9pt; font-family:Verdana; font-family: Verdana' ><P>Hello Jonathan,</P><P>it will make no difference if I put the declaration of the $xslt variable within the for() loop. Unfortunately I have to process a lot of documents with different xsl files. I've tried as workaround the following code:</P><P>my $xslt = XML::XSLT->new ($xslurl, warnings => 1);<BR>for($i=0; $i<200; $i++) {<BR> $xslt->open_xsl($xslurl);<BR> $xslt->transform($xmlurl);<BR> print $xslt->toString;<BR>}<BR>$xslt->dispose();</P><P>But here I will get the error</P><P>Can't call method "getTagName" on an undefined value at C:/PERL/site/lib/XML/XSLT.pm line 869.</P><P>As I see </P><P>$template->getParentNode->getTagName</P><P>within __cache_templates will fail.</P><P>Thank you very much in advance for your help.</P><P>Best regards</P><P>Bernhard</P><P> </P><P><A href="mailto:gellyfish! @gellyfish.com">gel...@ge...</A> schrieb am 25.03.04 15:02:46:<BR>> The only thing I can think of is that you might want to move the lexical<BR>> declaration of the $xslt variable within your for() loop as this may<BR>> force the destruction of the xobjects. It might however be that we need<BR>> to dispose() of some of the XML::DOM xobjects that are created within<BR>> XML::XSLT. I'll check it out.<BR>> <BR>> /J<BR></P><br><br><table cellpadding="0" cellspacing="0" border="0"><tr><td bgcolor="#000000"><img src="http://img.web.de/p.gif" width="1" height="1" border="0" alt="" /></td></tr><tr><td style="font-family:verdana; font-size:12px; line-height:17px;">Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Beagle.A-J! <br>Kostenfrei fuer FreeMail Nutzer. <A HREF="http://f.web.de/?mc=021158"><B>http://f.web.de/?mc=021158</B></A> </td></tr></table></body></html> |
From: Jonathan S. <gel...@ge...> - 2004-03-25 14:02:41
|
On Wed, 2004-03-24 at 08:19, Bernhard Weininger wrote: > Hi ..., > > very nice tool, but is it possible that there is a memory leak? If I > run the example below the perl process will grow and grow ... > > Or is there something wrong with my code? The only thing I can think of is that you might want to move the lexical declaration of the $xslt variable within your for() loop as this may force the destruction of the objects. It might however be that we need to dispose() of some of the XML::DOM objects that are created within XML::XSLT. I'll check it out. /J\ > > Best regards, > > Bernhard > > > > ================================================================ > > use strict; > use XML::XSLT; > > my $xsl = "D:/transfer/XSL_BUG/HTML.xsl"; > my $xmlfile = "D:/transfer/XSL_BUG/attributes.xml"; > > my $xslurl = makeURL($xsl); > my $xmlurl = makeURL($xmlfile); > > my $i; > my $xslt; > for($i=0; $i<200; $i++) { > $xslt = XML::XSLT->new ($xslurl, warnings => 1); > > $xslt->transform ($xmlurl); > print $xslt->toString; > > > $xslt->dispose(); > } > > 0; > > > sub makeURL { > my $string = shift; > > ! ; if( $string =~ m|^file\://|i ) { return $string; } # if > already URL format > $string =~ s|\\|\/|g; # replace \\ > $string =~ s/\:/\|/o; # replace : > return "FILE://".$string; # add file:// > } > > > > ... and the winner is... WEB.DE FreeMail! - Deutschlands beste E-Mail > ist zum 39. Mal Testsieger (PC Praxis 03/04) > http://f.web.de/?mc=021191 |
From: Bernhard W. <ber...@we...> - 2004-03-24 08:19:41
|
<html><style>p {margin: 0px}</style><body bgcolor='#ffffff' style='font-size:9pt; font-family:Verdana; font-family: Verdana' ><P>Hi ...,</P><P>very nice tool, but is it possible that there is a memory leak? If I run the example below the perl process will grow and grow ...</P><P>Or is there something wrong with my code?</P><P>Best regards,</P><P>Bernhard</P><P> </P><P>================================================================</P><P>use strict;<BR>use XML::XSLT;</P><P>my $xsl = "D:/transfer/XSL_BUG/HTML.xsl";<BR>my $xmlfile = "D:/transfer/XSL_BUG/attributes.xml";</P><P>my $xslurl = makeURL($xsl);<BR>my $xmlurl = makeURL($xmlfile);</P><P>my $i;<BR>my $xslt;<BR>for($i=0; $i<200; $i++) {<BR>$xslt = XML::XSLT->new ($xslurl, warnings => 1);</P><P>$xslt->transform ($xmlurl);<BR>print $xslt->toString;</P><P><BR>$xslt->dispose();<BR>}</P><P>0;</P><P><BR>sub makeURL {<BR> my $string = shift;</P><P>  ! ; if( $string =~ m|^file\://|i ) { return $string; } # if already URL format<BR> $string =~ s|\\|\/|g; # replace \\<BR> $string =~ s/\:/\|/o; # replace :<BR> return "<A href='file://".$string'>FILE://".$string</A>; # add file://<BR>}</P><br><table cellpadding="0" cellspacing="0" border="0"><tr><td bgcolor="#000000"><img src="http://img.web.de/p.gif" width="1" height="1" border="0" alt="" /></td></tr><tr><td style="font-family:verdana; font-size:12px; line-height:17px;">... and the winner is... WEB.DE FreeMail! - Deutschlands beste E-Mail<br>ist zum 39. Mal Testsieger (PC Praxis 03/04) <A HREF="http://f.web.de/?mc=021191"><B>http://f.web.de/?mc=021191</B></A></td></tr></tabl! e></body></html> |
From: Jonathan S. <jn...@ge...> - 2004-02-20 09:39:12
|
Well you wait for ages and all of a sudden two come along at once. This is a further interim release containing a number of bug fixes. * Top level and external variables weren't propagating down * Attribute sets can now inherit properly * use-attribute-sets now work in xsl:copy * fixed select for "comment()" "processing-instruction()" etc Again feel free to send any comments, patches flames etc ... /J\ |
From: Jonathan S. <jn...@ge...> - 2004-02-16 13:37:16
|
XML::XSLT is not dead just rather sluggish. I have made a release today to CPAN and sourceforge of 0.47 of the module. This contains a number of bug fixes, most importantly with respect to the handling of variables and includes a few more tests. Please feel free to direct any bug reports, patches, offers of help or flames toward me. /J\ |
From: Geert J. <Geert.Josten@Daidalos.nl> - 2003-07-04 08:02:36
|
> > > > Charles F. Goldfarb and Paul Prescod, authors of the forthcoming > > > > Fifth Edition of The XML Handbook (Prentice Hall, 2003) would like > > > > the CD-ROM that accompanies the book to include your free software: > > > > > > > > XML::XSLT > > > > > > This is fine however what is the timetable for getting the module onto the > CD? I am intending to make a new release of the module to CPAN within the > next week and it would be nice if you could use the most up to date > version there is available and obviously it wants to be the same as > released version rather than from the CVS. > > Also does the book include any examples using XML::XSLT? If so it might be > worth your while getting a final technical review of those parts from one > of the developers. > > /J\ Hi Jonathan, I don't think there are examples of XML::XSLT in particular in the book. The book is accompanied by a CD-bundle with a large set of all kinds of XML-related tools and parsers. I'v seen 3rd and 4th edition, but never saw much of tool-specific examples in there, I think... But let's see what the editor(s) of the handbook have to say about it... :-) Grtz, Geert |
From: Jonathan S. <gel...@ge...> - 2003-07-03 15:56:44
|
On Wed, 2 Jul 2003, Geert Josten wrote: > Egon Willighagen schreef: > > > > On Wednesday 02 July 2003 14:44, Andrew D. Goldfarb Managing Editor The XML > > Handbook +1(415 wrote: > > > Charles F. Goldfarb and Paul Prescod, authors of the forthcoming > > > Fifth Edition of The XML Handbook (Prentice Hall, 2003) would like > > > the CD-ROM that accompanies the book to include your free software: > > > > > > XML::XSLT > > > This is fine however what is the timetable for getting the module onto the CD? I am intending to make a new release of the module to CPAN within the next week and it would be nice if you could use the most up to date version there is available and obviously it wants to be the same as released version rather than from the CVS. Also does the book include any examples using XML::XSLT? If so it might be worth your while getting a final technical review of those parts from one of the developers. /J\ -- Jonathan Stowe | <http://www.gellyfish.com> | This space for rent | |
From: Geert J. <Geert.Josten@Daidalos.nl> - 2003-07-02 13:06:53
|
You have my permission as well, though main development has been transferred to the Project Admins as mentioned on the following page: http://sourceforge.net/projects/xmlxslt/ It would be nice if I could receive a copy of the book as well. You may send it to the same address as below. Sincerely, Geert Josten Egon Willighagen schreef: > > On Wednesday 02 July 2003 14:44, Andrew D. Goldfarb Managing Editor The XML > Handbook +1(415 wrote: > > Charles F. Goldfarb and Paul Prescod, authors of the forthcoming > > Fifth Edition of The XML Handbook (Prentice Hall, 2003) would like > > the CD-ROM that accompanies the book to include your free software: > > > > XML::XSLT > > > > If you agree, please reply to me with this message attached, thereby > > indicating that you grant permission to include the documentation > > and executable code for the software in the book "The XML Handbook, > > Fifth Edition" to be published by Prentice Hall, Inc., and that you > > grant Prentice Hall non-exclusive worldwide distribution rights. > > I hereby grant permission to distribute XML::XSLT. > Note that there are other authors who need to give permission too. > > > Replying now would be best, but if that isn't possible, please don't > > delay past July 18 to avoid missing the due date for including > > software on the CD-ROM. Other than your approval, no other effort is > > required of you, as we can download the free software from the > > Internet. > > > > If you are not the appropriate person to consider this request, I > > would be grateful if you would direct this message to that person and > > notify me so that I can update our records. Any additional questions > > can be directed to Andrew Goldfarb at an...@xm.... > > > > Thank you in advance. > > I would like to receive a copy of the book. It can be send to: > > E.L.Willighagen > wijnkersstraat 53 > NL-6679 CR Oosterhout (Nijmegen) > The Netherlands > > kind regards, > > Egon Willighagen |
From: Jonathan S. <gel...@ge...> - 2003-06-26 16:34:35
|
On Wed, 25 Jun 2003, Mark A. Hershberger wrote: > Jonathan Stowe <gel...@ge...> writes: > > > The module passes all the tests it has now. However I would like to get > > some feedback as to whether it is sensible to make a release right now. > > I think a new release makes a ton of sense. It'll show up on CPAN > and show that the project is still alive. > > Also, may I suggest using the test suite that libxslt uses? It seems > fairly complete and would be a good benchmark. > Well, I have started to roll in some of the NIST test suite - I haven't put it all in as the high proportion of skipped tests might be embarassing. I'll take a look at the libxslt tests to see if there are any which might be simply implemented. /J\ -- Jonathan Stowe | <http://www.gellyfish.com> | This space for rent | |
From: Geert J. <Geert.Josten@Daidalos.nl> - 2003-06-26 07:35:07
|
Hi Mark, Interesting note: do you really think it is possible to parse an XSL-sheet using streaming models? I have thought it over often (I have worked with the streaming language Omnimark), but discarded it as impossible. Grtz, Geert > Message: 2 > To: xml...@li... > Subject: Re: New release ? > From: ma...@ev... (Mark A. Hershberger) > Date: Wed, 25 Jun 2003 11:51:18 -0500 > > Jonathan Stowe <gel...@ge...> writes: > > > The module passes all the tests it has now. However I would like to get > > some feedback as to whether it is sensible to make a release right now. > > I think a new release makes a ton of sense. It'll show up on CPAN > and show that the project is still alive. > > Also, may I suggest using the test suite that libxslt uses? It seems > fairly complete and would be a good benchmark. > > Finally, have you given any thought to using XML::SAX? That way, if > a pure-perl parser is needed, one is available, or if a faster > version is available, it is used. > > Mark. |
From: <ma...@ev...> - 2003-06-25 16:51:47
|
Jonathan Stowe <gel...@ge...> writes: > The module passes all the tests it has now. However I would like to get > some feedback as to whether it is sensible to make a release right now. I think a new release makes a ton of sense. It'll show up on CPAN and show that the project is still alive. Also, may I suggest using the test suite that libxslt uses? It seems fairly complete and would be a good benchmark. Finally, have you given any thought to using XML::SAX? That way, if a pure-perl parser is needed, one is available, or if a faster version is available, it is used. Mark. -- As long as you have mystery you have health; when you destroy mystery you create morbidity. -- G.K. Chesterson |
From: Geert J. <Geert.Josten@Daidalos.nl> - 2003-06-25 07:40:10
|
Hi all, I'm delighted to see that at least two die-hards are still working with this module! I don't think I have time to dive into the sources, mainly because they have changed too much for me to recognize them any longer and I don't have the time to read them through again. Though, I am working a lot with XSL(T) currently and have worked on multiple (obscure ;) implementations of XSL parsers; if it is of any help, I can assist with test work. I would really like it if this module would reach a more or less up-to-date status again. Grtz, Geert |
From: Jonathan S. <gel...@ge...> - 2003-06-24 21:30:09
|
I have put quite a lot of code into the CVS since I made the last release of the module. Unless I here otherwise I propose to make a release to CPAN in the next few weeks. A release might at the least provoke some patches :-) The module passes all the tests it has now. However I would like to get some feedback as to whether it is sensible to make a release right now. Looking forward to see some feedback. /J\ -- Jonathan Stowe | <http://www.gellyfish.com> | This space for rent | |
From: Jonathan S. <jn...@ge...> - 2003-06-24 16:13:20
|
On Tue, 24 Jun 2003, Iain Tatch wrote: > On Tuesday, June 24, 2003, 2:13:50 PM, Jonathan Stowe wrote: > > >> Pure Perl XSLT was unsupported and incomplete last I heard. > >> > > JS> Oi! Less of the unsupported matey. All patches welcome. > > [ .. offlist reply .. ] > > Hmmm that's a point. > > Just (finally) started taking a look at XML::XSLT to try to get it moved > along a little bit. My first step is to get it to successfully process > some stylesheets that I'm currently transforming via Xalan (C++ not Java). > Much of this is probably going to revolve around getting xsl:variable > more fully implemented, but the first snag I hit was > > line 704: Well its more like line 771 in the CVS version :-) > if ($match && $name) { > $self->warn(qq{defining a template with both a "name" and a "match" attribute is not allowed!}); > > Is this the case according to the XSL specs? As far as I can make out from > http://www.w3.org/TR/xslt section 5.3 it's perfectly permissable to have > both. Ditto with the DTD from the same URI (yuk I *hate* DTDs!) but if I'm > reading it correctly: > > <!ATTLIST xsl:template > match %pattern; #IMPLIED > name %qname; #IMPLIED > priority %priority; #IMPLIED > mode %qname; #IMPLIED > %space-att; > > > I think that you are correct the spec actually says: If an xsl:template element has a name attribute, it may, but need not, also have a match attribute. I think probably this might need a little work on conflict resolution but I can't see any reason for it not to go in. On closer inspection of the spec I think that this bit might need fixing to comply with: The match attribute is required unless the xsl:template element has a name attribute as well. However I am going to go with: --- XSLT.pm 18 Feb 2002 09:05:14 -0000 1.19 +++ XSLT.pm 24 Jun 2003 16:01:34 -0000 @@ -765,22 +765,10 @@ foreach my $template (reverse $self->templates()) { if ($template->getParentNode->getTagName =~ /^([\w\.\-]+\:){0,1}(stylesheet|transform|include)/) { - my $match = $template->getAttribute ('match'); - my $name = $template->getAttribute ('name'); - if ($match && $name) { - $self->warn(qq{defining a template with both a "name" and a "match" attribute is not allowed!}); - push (@{$self->{TEMPLATE_MATCH}}, ""); - push (@{$self->{TEMPLATE_NAME}}, ""); - } elsif ($match) { - push (@{$self->{TEMPLATE_MATCH}}, $match); - push (@{$self->{TEMPLATE_NAME}}, ""); - } elsif ($name) { - push (@{$self->{TEMPLATE_MATCH}}, ""); - push (@{$self->{TEMPLATE_NAME}}, $name); - } else { - push (@{$self->{TEMPLATE_MATCH}}, ""); - push (@{$self->{TEMPLATE_NAME}}, ""); - } + my $match = $template->getAttribute ('match') || ''; + my $name = $template->getAttribute ('name') || ''; + push (@{$self->{TEMPLATE_MATCH}}, $match); + push (@{$self->{TEMPLATE_NAME}}, $name); } } } for the time being. I'll look at the mandatory match later. This passes all the current tests and I'll add a test for this specifically in a bit. It's a good thing I ran a 'make test' as it generates a whole slew of Subroutine XML::DOM::Text::print redefined at /home/gellyfish/develop/xmlxslt/XML-XSLT/blib/lib/XML/XSLT.pm line 1109 with the perl 5.8.0 and XML::DOM 1.42 ... /J\ |
From: Prasanna K. <agp...@ho...> - 2003-02-07 12:32:00
|
Thanks Josten, This is really Cool! ----- Original Message ----- From: "Geert Josten" <Geert.Josten@Daidalos.nl> To: "Prasanna Kumar" <agp...@ho...> Cc: <xml...@li...> Sent: Friday, February 07, 2003 5:39 PM Subject: Re: Help on XSLT template logic! (Prasanna Kumar) > 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" <Geert.Josten@Daidalos.nl> > > 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 > > > ---------------------------------------------------------------------------- ---- > <?xml version='1.0' encoding='ISO-8859-1'?> > <xsl:stylesheet version="1.0" > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> > > <xsl:output method="html" /> > > <xsl:template match="COLUMNHEADER"> > <table> > <!-- recursive solution --> > <xsl:call-template name="printrow"> > <xsl:with-param name="elements" select="TEXTELEMENT" /> > </xsl:call-template> > <!-- non-recursive solution --> > <!--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 name="printrow"> > <xsl:param name="elements" /> > <xsl:if test="$elements"> > <tr> > <xsl:apply-templates select="$elements" /> > </tr> > <xsl:call-template name="printrow"> > <xsl:with-param name="elements" select="$elements/TEXTELEMENT" /> > </xsl:call-template> > </xsl:if> > </xsl:template> > > <xsl:template match="TEXTELEMENT"> > <td><xsl:value-of select="@DISPLAYNAME" /></td> > </xsl:template> > > </xsl:stylesheet> > ---------------------------------------------------------------------------- ---- > <?xml version='1.0' encoding='ISO-8859-1'?> > <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> > |