Re: [xsl] Fwd:[xsl] REMOVE FROM MAILING LIST

Subject: Re: [xsl] Fwd:[xsl] REMOVE FROM MAILING LIST
From: Robert C Corsaro <rcorsaro@xxxxxxxxxxx>
Date: Thu, 31 May 2007 13:34:12 -0400
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I say that anyone sending such messages to the list should be removed
immediately.  We don't need that type of rudeness here.

Mulberry Technologies List Owner wrote:
> Please send all administrative messages about XSL-List to the list
> owner, not to the list. There is no reason that all the subscribers to
> the list need to see administrative questions such as this.
> 
> If anyone else on the list would like to be removed from the list, or
> has any other administrative requests, please send them to me at
> <xsl-list-owner@xxxxxxxxxxxxxxxxxxxxxx>.
> 
> Thank you.
> 
> -- Tommie
> 
> 
>> Hi,
>>    I'd like to be removed from the list too. Earlier I received a mail
>> saying that mails sent to my email id were getting returned back. I
>> want to assure you that the mails are indeed coming to my mailbox and
>> I don't want them to come no longer. I would appreciate if you could
>> unsubscribe me from the list.
>>
>> Regards,
>> V.Omprakash
>>
>>
>>
>>
>>  Wrote---
>> I've gone through the removal process and it does not work I get an =
>> email back stating that I am not a member of this list and yet it =
>> persists in sending me these emails.
>>
>> Please remove my address from the list.
>>
>>
>> -------------------------------------------------------------------------=
>>
>> -------------------
>> Le pr=E9sent courriel et toutes les pi=E8ces jointes peuvent contenir
>> de =
>> l'information priv=E9e, exclusive, privil=E9gi=E9e ou confidentielle, =
>> sujette au droit d'auteur s'adressant uniquement au destinataire. Toute =
>> utilisation, copie ou distribution non autoris=E9e du contenu de ce =
>> courriel est strictement interdite. Si vous n'=EAtes pas le
>> destinataire =
>> de ce message et que vous l'avez re=E7u par erreur, veuillez le =
>> supprimer et en informer imm=E9diatement l'exp=E9diteur.=20
>>
>> This e-mail communication, including all attachments, may contain =
>> private, proprietary, privileged and/or confidential information and =
>> subject to copyright. It is intended only for the person to whom it is =
>> addressed. Any unauthorized use, copying or distribution of the
>> contents =
>> of this e-mail is strictly prohibited. Please delete this e-mail and =
>> notify the sender immediately, if you are not the intended recipient, =
>> and have received it in error.=20
>>
>> -----Message d'origine-----
>> De=A0: xsl-list-digest-help@xxxxxxxxxxxxxxxxxxxxxx =
>> [mailto:xsl-list-digest-help@xxxxxxxxxxxxxxxxxxxxxx]=20
>> Envoy=E9=A0: May 29, 2007 1:10 AM
>> =C0=A0: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> Objet=A0: xsl-list Digest 29 May 2007 05:10:00 -0000 Issue 1151
>>
>> xsl-list Digest 29 May 2007 05:10:00 -0000 Issue 1151
>>
>> Topics (messages 36920 through 36933):
>>
>> call-template error
>>     36920 by: Vaduvoiu Tiberiu
>>     36923 by: Michael Kay
>>     36928 by: Dimitre Novatchev
>>     36929 by: M. David Peterson
>>
>> Batch processing
>>     36921 by: J. S. Rawat
>>     36924 by: Michael Kay
>>
>> Re: XSLT and XML in the same document
>>     36922 by: Julian Reschke
>>     36926 by: M. David Peterson
>>     36927 by: Julian Reschke
>>     36930 by: Andrew Welch
>>     36931 by: M. David Peterson
>>     36932 by: M. David Peterson
>>     36933 by: M. David Peterson
>>
>> Re: Entities Conversion
>>     36925 by: Tony Graham
>>
>> Administrivia:
>>
>> To subscribe to the digest, e-mail:
>>     <xsl-list-digest-subscribe@xxxxxxxxxxxxxxxxxxxxxx>
>>
>> To unsubscribe from the digest, e-mail:
>>     <xsl-list-digest-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx>
>>
>> To post to the list, e-mail:
>>     <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
>>
>>
>> ----------------------------------------------------------------------
>> Date: Mon, 28 May 2007 03:24:13 -0700 (PDT)
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: Vaduvoiu Tiberiu <vaduvoiutibi@xxxxxxxxx>
>> Subject: call-template error
>> Message-ID: <442391.9734.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>
>> On my site I have a couple of categories/menus. Each time you're in a =
>> category it loads a different template(content)
>> I have a parameter $menu which has the value of the name of the menu
>> you =
>> are at on the site. So until now I had something like this:
>>
>> <xsl:if test=3D"$menu=3D sport">
>> <xsl:call-template name=3D"toolbox_sport"></xsl:call-template>
>> </xsl:if>
>> <xsl:if test=3D"$menu=3D 'news">
>> <xsl:call-template name=3D"toolbox_news"></xsl:call-template>
>> </xsl:if>
>> <xsl:if test=3D"$menu=3D recent">
>> <xsl:call-template name=3D"toolbox_recent"></xsl:call-template>
>> </xsl:if>
>> <xsl:if test=3D"$menu=3D test">
>> <xsl:call-template name=3D"toolbox_test"></xsl:call-template>
>> </xsl:if>
>>
>> like this, it works. But then I though of making it more simple like =
>> this:
>>
>> <xsl:call-template name=3D"toolbox_$menu"></xsl:call-template> so =
>> basically it should only loads the template of the selected menu. Thing =
>> is it doesn't work..I get java.util.EmptyStackException:
>>
>> I also tried creating a variable
>> <xsl:variable name=3D"tool">toolbox_<xsl:value-of =
>> select=3D"$menu"/></xsl:variable>
>> and then calling the template with the name=3D"$tool"..also doesn't =
>> work. So why doesn't he load it?? 10x
>>
>>       =20
>> _________________________________________________________________________=
>>
>> ___________Take the Internet to Go: Yahoo!Go puts the Internet in your =
>> pocket: mail, news, photos & more.=20
>> http://mobile.yahoo.com/go?refer=3D1GNXIC
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 13:01:13  0100
>> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
>> From: "Michael Kay" <mike@xxxxxxxxxxxx>
>> Subject: RE: [xsl] call-template error
>> Message-ID: <00ad01c7a11f$e37a4e10$6401a8c0@turtle>
>>
>> The name of a template being called must be a fixed string, just as
>> when =
>> you
>> call a function or method in languages like C or Java. Variables can =
>> only be
>> used in XPath expressions, and the name attribute of call-template is =
>> not an
>> XPath expression.
>>
>> You can often achieve a dynamic call by using apply-templates to some
>> suitable node.
>>
>> Michael Kay
>> http://www.saxonica.com/=20
>>
>>>  -----Original Message-----
>>>  From: Vaduvoiu Tiberiu [mailto:vaduvoiutibi@xxxxxxxxx]=20
>>>  Sent: 28 May 2007 11:24
>>>  To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>>>  Subject: [xsl] call-template error
>>> =20
>>>  On my site I have a couple of categories/menus. Each time=20
>>>  you're in a category it loads a different template(content) I=20
>>>  have a parameter $menu which has the value of the name of the=20
>>>  menu you are at on the site. So until now I had something like this:
>>> =20
>>>  <xsl:if test=3D"$menu=3D sport">
>>>  <xsl:call-template name=3D"toolbox_sport"></xsl:call-template>
>>>  </xsl:if>
>>>  <xsl:if test=3D"$menu=3D 'news">
>>>  <xsl:call-template name=3D"toolbox_news"></xsl:call-template>
>>>  </xsl:if>
>>>  <xsl:if test=3D"$menu=3D recent">
>>>  <xsl:call-template name=3D"toolbox_recent"></xsl:call-template>
>>>  </xsl:if>
>>>  <xsl:if test=3D"$menu=3D test">
>>>  <xsl:call-template name=3D"toolbox_test"></xsl:call-template>
>>>  </xsl:if>
>>> =20
>>>  like this, it works. But then I though of making it more=20
>>>  simple like this:
>>> =20
>>>  <xsl:call-template name=3D"toolbox_$menu"></xsl:call-template>=20
>>>  so basically it should only loads the template of the=20
>>>  selected menu. Thing is it doesn't work..I get=20
>>>  java.util.EmptyStackException:
>>> =20
>>>  I also tried creating a variable
>>>  <xsl:variable name=3D"tool">toolbox_<xsl:value-of=20
>>>  select=3D"$menu"/></xsl:variable> and then calling the template=20
>>>  with the name=3D"$tool"..also doesn't work. So why doesn't he=20
>>>  load it?? 10x
>>> =20
>>> =20
>>>        =20
>>>  ______________________________________________________________
>>>  ______________________Take the Internet to Go: Yahoo!Go puts=20
>>>  the Internet in your pocket: mail, news, photos & more.=20
>>>  http://mobile.yahoo.com/go?refer=3D1GNXIC
>>> =20
>>> =20
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 08:17:48 -0700
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: "Dimitre Novatchev" <dnovatchev@xxxxxxxxx>
>> Subject: Re: [xsl] call-template error
>> Message-ID: =
>> <1563432b0705280817m554ca9a6hfae9d7bed2803ccf@xxxxxxxxxxxxxx>
>>
>> In addition to the explanation of Dr. Kay, see:
>>
>>        http://fxsl:sf.net
>>
>> --=20
>> Cheers,
>> Dimitre Novatchev
>> ---------------------------------------
>> Truly great madness cannot be achieved without significant intelligence.
>> ---------------------------------------
>> To invent, you need a good imagination and a pile of junk
>> -------------------------------------
>> You've achieved success in your field when you don't know whether what
>> you're doing is work or play
>>
>> On 5/28/07, Vaduvoiu Tiberiu <vaduvoiutibi@xxxxxxxxx> wrote:
>>>  On my site I have a couple of categories/menus. Each time you're in a =
>> category it loads a different template(content)
>>>  I have a parameter $menu which has the value of the name of the menu =
>> you are at on the site. So until now I had something like this:
>>>
>>>  <xsl:if test=3D"$menu=3D sport">
>>>  <xsl:call-template name=3D"toolbox_sport"></xsl:call-template>
>>>  </xsl:if>
>>>  <xsl:if test=3D"$menu=3D 'news">
>>>  <xsl:call-template name=3D"toolbox_news"></xsl:call-template>
>>>  </xsl:if>
>>>  <xsl:if test=3D"$menu=3D recent">
>>>  <xsl:call-template name=3D"toolbox_recent"></xsl:call-template>
>>>  </xsl:if>
>>>  <xsl:if test=3D"$menu=3D test">
>>>  <xsl:call-template name=3D"toolbox_test"></xsl:call-template>
>>>  </xsl:if>
>>>
>>>  like this, it works. But then I though of making it more simple like =
>> this:
>>>
>>>  <xsl:call-template name=3D"toolbox_$menu"></xsl:call-template> so =
>> basically it should only loads the template of the selected menu. Thing =
>> is it doesn't work..I get java.util.EmptyStackException:
>>>
>>>  I also tried creating a variable
>>>  <xsl:variable name=3D"tool">toolbox_<xsl:value-of =
>> select=3D"$menu"/></xsl:variable>
>>>  and then calling the template with the name=3D"$tool"..also doesn't =
>> work. So why doesn't he load it?? 10x
>>>
>>>
>>>
>>>  =
>> _________________________________________________________________________=
>>
>> ___________Take the Internet to Go: Yahoo!Go puts the Internet in your =
>> pocket: mail, news, photos & more.
>>>  http://mobile.yahoo.com/go?refer=3D1GNXIC
>>>
>>>
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 10:05:13 -0600
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: "M. David Peterson" <m.david@xxxxxxxxxxxxx>
>> Subject: Re: [xsl] call-template error
>> Message-ID: <op.ts1oazfqgb2xtc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>
>> On Mon, 28 May 2007 09:17:48 -0600, Dimitre Novatchev =20
>> <dnovatchev@xxxxxxxxx> wrote:
>>
>>>  http://fxsl:sf.net
>>
>> And if that doesn't work, try http://fxsl.sf.net/ ;-)
>>
>> --=20
>> /M:D
>>
>> M. David Peterson
>> http://mdavid.name | http://www.oreillynet.com/pub/au/2354 | =20
>> http://dev.aol.com/blog/3155
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 16:08:08  0530
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: "J. S. Rawat" <jrawat@xxxxxxxxxxxxxx>
>> Subject: Batch processing
>> Message-Id: <4.3.1.20070528155300.01a334a0@localhost>
>>
>> Dear lists-
>> There are a list of files listed in XYZ.XML. Is there a way by which I =
>> can=20
>> process these files by XSLT by saxon. Basically I want a batch =
>> processing.=20
>> I want to put files into server alongwith XYZ.xml and need to pass one=20
>> commandline to process all the XML. I am just confused with =
>> collection().
>>
>> XYZ.XML
>> <dir>
>> <xmlFile>input.xml</xmlFile>
>> <xmlFile>input_meta.xml</xmlFile>
>> <xmlFile>sample.xml</xmlFile>
>> <xmlFile>x.xml</xmlFile>
>> </dir>
>>
>> thanks
>> ..JSR
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 13:03:30  0100
>> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
>> From: "Michael Kay" <mike@xxxxxxxxxxxx>
>> Subject: RE: [xsl] Batch processing
>> Message-ID: <00ae01c7a120$35952260$6401a8c0@turtle>
>>
>> You don't need the collection() function for this, you can do it with
>> document(). With <dir> as your current node, do
>>
>> <xsl:apply-templates select=3D"document(xmlFile)" mode=3D"m"/>
>>
>> and it will cause each of these input documents to be processed.
>>
>> Michael Kay
>> http://www.saxonica.com/=20
>>
>>>  -----Original Message-----
>>>  From: J. S. Rawat [mailto:jrawat@xxxxxxxxxxxxxx]=20
>>>  Sent: 28 May 2007 11:38
>>  > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>>>  Subject: [xsl] Batch processing
>>> =20
>>>  Dear lists-
>>>  There are a list of files listed in XYZ.XML. Is there a way=20
>>>  by which I can process these files by XSLT by saxon.=20
>>>  Basically I want a batch processing.=20
>>  > I want to put files into server alongwith XYZ.xml and need to=20
>>>  pass one commandline to process all the XML. I am just=20
>>>  confused with collection().
>>> =20
>>>  XYZ.XML
>>>  <dir>
>>>  <xmlFile>input.xml</xmlFile>
>>>  <xmlFile>input_meta.xml</xmlFile>
>>>  <xmlFile>sample.xml</xmlFile>
>>>  <xmlFile>x.xml</xmlFile>
>>>  </dir>
>>> =20
>>>  thanks
>>>  ..JSR
>>> =20
>>> =20
>>> =20
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 13:11:06  0200
>> To:  xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: Julian Reschke <julian.reschke@xxxxxx>
>> Subject: Re: [xsl] XSLT and XML in the same document
>> Message-ID: <465AB8CA.9050106@xxxxxx>
>>
>> David Carlisle wrote:
>>>>  functionality via msxsl:node-set()[2].  Kind of a pain to work =
>> between the =20
>>>>  two of them inside of the same transformation file, but a simple =
>> check =20
>>> =20
>>>  you can probably just use msxsl:script to define exslt:node set can't
>>>  you,and then just use the exslt version in the actual code.
>>>  I don't think I've tried that though (but I may have done, hard to
>>>  remember:-)
>>
>> I just tried, and the first hurdle is that I can't define a function=20
>> called "node-set" in JScript (it's not a legal identifier). But=20
>> otherwise a cool idea :-)
>>
>> Microsoft: please give us exslt:node-set in IE. Please.
>>
>> Best regards, Julian
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 08:45:25 -0600
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: "M. David Peterson" <m.david@xxxxxxxxxxxxx>
>> Subject: Re: [xsl] XSLT and XML in the same document
>> Message-ID: <op.ts1klzjugb2xtc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>
>> On Mon, 28 May 2007 05:11:06 -0600, Julian Reschke =
>> <julian.reschke@xxxxxx> =20
>> wrote:
>>
>>>  Microsoft: please give us exslt:node-set in IE. Please.
>>
>> An interesting point in time to be asking MSFT for "favors."  via a =20
>> comment from Mike Champion (formerly of MSFT XML Team, now a part of
>> the =
>> =20
>> WS-* team; He's the one that lobbied for and obtained support for XSLT
>> =20
>> 2.0, so it's fair to assume that his advice on how to get MSFT's =
>> attention =20
>> in this space is quite sound)
>>
>> @http://www.oreillynet.com/xml/blog/2007/05/xml_silverlight_and.html#comm=
>>
>> ent-590145
>>
>> "I think Aaron is asking about what *subset* of the .NET XML features =20
>> should be ported to the Silverlight environment :-)
>>
>> But to get their attention for whatever subset or superset features
>> you  =
>>
>> think is appropriate, it would be best to be more explicit about the =
>> types =20
>> of applications you would build for the Silverlight platform and why =
>> some =20
>> specific XML feature would be necessary to make it work well."
>>
>> My own wish-list is in the body of the same linked post from above,
>> and  =
>>
>> while full support for XSLT 2.0 inside of Silverlight would be *GREAT*, =
>> I =20
>> don't think it's something we should get our hopes up too high about,
>> as =
>> =20
>> small and fast is of primary concern.  Instead, I believe that if the =20
>> community were to put their heads together and come up with a =
>> reasoanable =20
>> subset of EXSLT functions (potentially using the support provided by
>> Fx  =
>>
>> 3.0 as a foundation to begin working from?), we could probably get the
>> =20
>> right folks attention at MSFT to at very least consider providing =
>> support.
>>
>> In the mean time, something to consider: The Mono project provides an =20
>> implementation of System.Xml.Xsl licensed under the MIT license.  The =
>> MSFT =20
>> XML MVP's have support for EXSLT inside of their BSD-licensed Mvp.Xml =20
>> library.  Silverlight provides support for XmlReader and XmlWriter,
>> and  =
>>
>> Silverlight itself is a full fledged CLR, or in other words, their is =
>> full =20
>> support for CIL, which means their is full support for the C#, VB.NET, =
>> and =20
>> any other CLR compliant language (F# is the latest entry I have seen
>> in  =
>>
>> the "hey, look what Silverlight can do" language support-fest.)  And
>> to  =
>>
>> put the cherry on top of all of this, Silverlight is supported on not =
>> just =20
>> IE, but on Firefox (Windows, Mac) and (soon) Opera (Windows, Mac),
>> with  =
>>
>> the Mono project folks developing support as part of their Moonlight =20
>> project[1] which is suggested will be complete by the end of this year.
>>
>> In short: An opportunity now exists to both get MSFT's attention and =
>> have =20
>> a reasonable chance of gaining at least some level of support for
>> EXSLT  =
>>
>> inside of Silverlight and as such have that same support provided =20
>> cross-browser/cross-platform, as well as taking the bull by the horns =
>> and =20
>> building that support by using existing code that already provides =
>> *FULL* =20
>> support for XSLT 1.0/EXSLT, or in other words, developing support =20
>> ourselves that could then be used inside of any Silverlight-based =
>> project =20
>> would be pretty straight forward.  Gaining direct support would =
>> obviously =20
>> be quite a bit better, but creating a community-based project would at
>> =20
>> very least ensure that support is available, while at the same time act =
>> as =20
>> a good way to flesh out what portions of the EXSLT spec make sense =
>> inside =20
>> of the browser space and which of those do not.
>>
>> I've started a project on CodePlex called SilverLiteXSLT =20
>> (http://www.codeplex.com/silverlitexslt < Haven't published it yet, so =
>> you =20
>> probably won't see anything if you visit this link.) Please contact me
>> =20
>> off-list if you have interest in being a part of this.
>>
>> NOTE: The Atomictalk project is specifically focused at providing the =20
>> ability to build out cross-breed web applications, using pre-defined =20
>> modules in XHTML, Silverlight, Flash, etc... so I will be using this is =
>> as =20
>> the foundation for SilverLiteXSLT in regards to finding the most =
>> practical =20
>> feature-set using a hands-on, pragramatic approach.  Will be OOF for
>> the =
>> =20
>> rest of the morning, but when I come back I plan to spend some time =20
>> finishing out getting this project setup and the code from the various
>> =20
>> projects checked-in to begin the "mashup" process.  < This is going to =
>> be =20
>> fun! :D  Anyone want to join me?  Let me know :)
>>
>> [1] http://mono-project.com/Moonlight
>>
>> --=20
>> /M:D
>>
>> M. David Peterson
>> http://mdavid.name | http://www.oreillynet.com/pub/au/2354 | =20
>> http://dev.aol.com/blog/3155
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 17:12:21  0200
>> To:  xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: Julian Reschke <julian.reschke@xxxxxx>
>> Subject: Re: [xsl] XSLT and XML in the same document
>> Message-ID: <465AF155.8000400@xxxxxx>
>>
>> M. David Peterson wrote:
>>>  On Mon, 28 May 2007 05:11:06 -0600, Julian Reschke=20
>>>  <julian.reschke@xxxxxx> wrote:
>>> =20
>>>>  Microsoft: please give us exslt:node-set in IE. Please.
>>> =20
>>>  An interesting point in time to be asking MSFT for "favors."  via a=20
>>>  comment from Mike Champion (formerly of MSFT XML Team, now a part of =
>> the=20
>>>  WS-* team; He's the one that lobbied for and obtained support for
>>> XSLT =
>>
>>>  2.0, so it's fair to assume that his advice on how to get MSFT's=20
>>>  attention in this space is quite sound)
>>> =20
>>>  =
>> @http://www.oreillynet.com/xml/blog/2007/05/xml_silverlight_and.html#comm=
>>
>> ent-590145=20
>>>  ...
>>
>> David, that's all very interesting, but what *I* am looking for is
>> more=20
>> power in client side XSLT -- in this case, this means MSXML-inside-IE,=20
>> no .NET, no Silverlight.
>>
>> Best regards, Julian
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 18:27:11  0100
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: "Andrew Welch" <andrew.j.welch@xxxxxxxxx>
>> Subject: Re: [xsl] XSLT and XML in the same document
>> Message-ID: =
>> <74a894af0705281027s585f23b5lc1948c4d33aa6b7c@xxxxxxxxxxxxxx>
>>
>> On 5/28/07, Julian Reschke <julian.reschke@xxxxxx> wrote:
>>>  David Carlisle wrote:
>>>  >> functionality via msxsl:node-set()[2].  Kind of a pain to work =
>> between the
>>>  >> two of them inside of the same transformation file, but a simple =
>> check
>>>  >
>>>  > you can probably just use msxsl:script to define exslt:node set =
>> can't
>>>  > you,and then just use the exslt version in the actual code.
>>>  > I don't think I've tried that though (but I may have done, hard to
>>>  > remember:-)
>>>
>>>  I just tried, and the first hurdle is that I can't define a function
>>  > called "node-set" in JScript (it's not a legal identifier). But
>>>  otherwise a cool idea :-)
>>>
>>>  Microsoft: please give us exslt:node-set in IE. Please.
>>
>> There's msxsl:node-set().... used in combination with
>> function-available() and exslt:node-set() that should be sufficient
>> for what you need (if a bit of a pain)?
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 11:27:09 -0600
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: "M. David Peterson" <m.david@xxxxxxxxxxxxx>
>> Subject: Re: [xsl] XSLT and XML in the same document
>> Message-ID: <op.ts1r3j0jgb2xtc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>
>> On Mon, 28 May 2007 09:12:21 -0600, Julian Reschke =
>> <julian.reschke@xxxxxx> =20
>> wrote:
>>
>>>  but what *I* am looking for is more power in client side XSLT
>>
>> Silverlight is a client-side browser technology.  As such, this *is* =20
>> client-side XSLT that I am referring to.
>>
>> --=20
>> /M:D
>>
>> M. David Peterson
>> http://mdavid.name | http://www.oreillynet.com/pub/au/2354 | =20
>> http://dev.aol.com/blog/3155
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 23:04:29 -0600
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: "M. David Peterson" <m.david@xxxxxxxxxxxxx>
>> Subject: Re: [xsl] XSLT and XML in the same document
>> Message-ID: <op.ts2odrmrgb2xtc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>
>> On Mon, 28 May 2007 08:45:25 -0600, M. David Peterson =20
>> <m.david@xxxxxxxxxxxxx> wrote:
>>
>>>  Will be OOF for the rest of the morning, but when I come back I plan =
>> to =20
>>>  spend some time finishing out getting this project setup and the
>>> code  =
>>
>>>  from the various projects checked-in to begin
>>
>> This is now setup and the intitial code base from both Mono =20
>> (System.Xml.XPath, System.Xml.Xsl, Mono.Xml, Mono.XPath) and the
>> Mvp.Xml =
>> =20
>> project (Mvp.Xml.Exslt, Mvp.Xml.Common) checked in.  This has to be =20
>> completely rebuilt on top of XmlReader/XmlWriter so while the code is
>> in =
>> =20
>> place, it's going to take some work to get it to compile.  Still, it's
>> =20
>> worth the effort.
>>
>> If you have any desire what-so-ever to get involved, please let me know.
>>
>> http://www.codeplex.com/silverlitexslt
>>
>> --=20
>> /M:D
>>
>> M. David Peterson
>> http://mdavid.name | http://www.oreillynet.com/pub/au/2354 | =20
>> http://dev.aol.com/blog/3155
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 23:08:25 -0600
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: "M. David Peterson" <m.david@xxxxxxxxxxxxx>
>> Subject: Re: [xsl] XSLT and XML in the same document
>> Message-ID: <op.ts2okb0ngb2xtc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>
>> On Mon, 28 May 2007 23:04:29 -0600, M. David Peterson  =3D
>>
>> <m.david@xxxxxxxxxxxxx> wrote:
>>
>>>  If you have any desire what-so-ever to get involved, please let me =
>> kno=3D
>> w.
>>
>> BTW... If you want to browse through the source, you can do so via  =3D
>>
>> http://www.codeplex.com/silverlitexslt/SourceControl/DirectoryView.aspx?=3D=
>>
>>
>> SourcePath=3D3D%24%2fsilverlitexslt%2fSilverlitEXSLT&changeSetId=3D3D3840=
>>
>>
>>
>> -- =3D
>>
>> /M:D
>>
>> M. David Peterson
>> http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |  =3D
>>
>> http://dev.aol.com/blog/3155
>>
>> ------------------------------
>>
>> Date: Mon, 28 May 2007 13:25:18  0100
>> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> From: Tony Graham <Tony.Graham@xxxxxxxxxxxxxxxxxxxxxx>
>> Subject: Re: [xsl] Entities Conversion
>> Message-ID: <87tztx6spd.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>
>> On Sat, May 26 2007 23:39:12  0100, Abel Braaksma wrote:
>>>  J. S. Rawat wrote:
>> ...
>>>>  DESIRED OUTPUT
>>>>  l n q s
>>>
>>>  there's a way to get this in XSLT 2.0 using character-sets, but it is
>>>  usually not the way to go as you will invalidate your xml.
>>
>> ...unless your output includes (or is included as an external general
>> parsed entity in a document that includes) the DOCTYPE declaration for
>> a DTD that defines those entities.
>>
>> It's generally not necessary to turn the characters back into entity
>> references since your XML parser will turn them back into characters
>> again anyway when you come to parse your XML.
>>
>> About the only use that I can see for turning the characters back into
>> entities is if you both need to eyeball the XML and it would make more
>> sense to you if you saw named entity references rather than numeric
>> references.
>>
>> If you want to, your stylesheet can import a set of XSLT 2.0 character
>> maps for the ISO entity sets that can be downloaded from
>> http://www.w3.org/2003/entities/iso8879doc/overview.html.
>>
>> While DTDs sometimes map multiple different ISO entities to
>> the same numeric entity reference, these character maps can only
>> convert a character back to a single entity reference.  If you use
>> these character maps, you might particularly look at the mappings to
>> 'rsquor' and 'rdquor' in the ISOpub mapping since you may want 'rsquo'
>> and 'rdquo' instead.
>>
>> Regards,
>>
>> Tony Graham.
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Tony.Graham@xxxxxxxxxxxxxxxxxxxxxx   http://www.menteithconsulting.com
>>
>> Menteith Consulting Ltd             Registered in Ireland - No. 428599
>> Registered Office: 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
>> ----------------------------------------------------------------------
>> Menteith Consulting -- Understanding markup
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> ------------------------------
>>
>> End of xsl-list Digest
>> ***********************************
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGXwcUkAu83kdgE3MRAlQMAJ9oss9tlzOlndauZsgM7wtQ7W1I8gCeP0+v
LNsSDnySnNQ3TOk/iiYhY8I=
=WxT3
-----END PGP SIGNATURE-----

Current Thread