[xsl] File URI / EXPath / Saxon - 11/21/2009 12:24:00 AM

Hey list,

in my XSLT, I'm passing an absolute URI of the file which I want
EXPath to create for me as a parameter.

Using getRealPath() in Java gives backslashes on Windows, so I replace
them with forward ones and this is the value I pass:
file:///C:/Users/Martynas/WebRoot/odf2epub/build/web/epub/test.epub

But then running the stylesheet gives errors:

net.sf.saxon.trans.XPathException: Invalid URI:
file:///C:\Users\Martynas\WebRoot\odf2epub\build\web\epub\test.epub
        at org.expath.saxon.Zip.fileFromURI(Zip.java:261)
        at org.expath.saxon.Zip.analyseHref(Zip.java:239)
        at org.expath.saxon.Zip.zipFile(Zip.java:305)

And the file path is shown with backslashes again. Backslashes are not
allowed in URIs as far as I know, but the parameter value is without
them.
Any ideas on what's going wrong? I'm running Saxon on Windows.

Martynas

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

RE: [xsl] How to include ' in the argument of function - 11/20/2009 11:48:00 PM

The least confusing way to do this is to use variables:

'

then 

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay  

> -----Original Message-----
> From: Mak, Lucas Wing Kau [mailto:makw@mail.lib.msu.edu] 
> Sent: 20 November 2009 21:46
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] How to include ' in the argument of 
>  function
> 
> I am trying to replace the apostrophe (') with a space by the 
>  function but oXygen gave me an error message 
> ("unmatched quote in expression") when I put ' in the 
> second argument. How can I resolve that?
> 
> Thanks,
> 
> Lucas
> 
> --~------------------------------------------------------------------
> XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
> or e-mail: 
> --~--
> 


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

Re: [xsl] How to include ' in the argument of function - 11/20/2009 9:53:00 PM

At 2009-11-20 16:46 -0500, Mak, Lucas Wing Kau wrote:
>I am trying to replace the apostrophe (') with a space by the 
> function but oXygen gave me an error message ("unmatched 
>quote in expression") when I put ' in the second argument. How 
>can I resolve that?

You aren't showing your current code for volunteers to analyze where 
you are going wrong.

You have to distinguish attribute delimiters from string delimiters.

For example, this should work just fine:

   select='translate($old,"'","")'

... because I'm using single quotes as my attribute delimiter and 
double quotes for my string delimiters.  That choice of string 
delimiter allows me to embed an apostrophe in the string, which I do 
with the entity reference.

Remember that entity substitution happens long before the syntax 
analysis of the function call, so if you had:

   select="translate($old,''','')"

... then you would get an error because that is *no* different from:

   select="translate($old,''','')"

I hope this helps.

. . . . . . . . . Ken

--
Vote for your XML training:   http://www.CraneSoftwrights.com/s/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/s/
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview:  http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/s/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

[xsl] How to include ' in the argument of function - 11/20/2009 9:47:00 PM

I am trying to replace the apostrophe (') with a space by the  function but oXygen gave me an error message ("unmatched quote in expression") when I put ' in the second argument. How can I resolve that?

Thanks,

Lucas

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

Re: [xsl] XSLT for XSL-FO internal-destination - 11/20/2009 7:15:00 PM

David,

I'm still not quite clear about how to connect the id from the href to the id at the heading of each page. Just to clarify, here is a simplified stylesheet (test.xsl), XML table of contents page (text.xml), and two XHTML source files (file_one.htm and file_two.htm). I'm calling the text.xml file that points to the file_one.htm and file_two.htm source files.

For the purposes of this example, I've moved all the files into the same directory, but is the purpose of the translate function merely to remove special characters the directory path in order to create an id? If so, perhaps it's not necessary in this latest example:

--------------------
test.xsl
--------------------


 


   
	  

    
    
        	
        	
        	
        	
        	
    
    
            
    
	
    	     
                
                   
                 
            
              
                   
                        
                         
                                      
                            
                              
                            

                        
                         
                   
              
   




    
		 
    



   
      
              
                 
                  
              
              
      
    




--------------------
test.xml (acts as a table of contents in online help)
--------------------




    
    


--------------------
file_one.htm
--------------------


    
        
    
    
        Link example: Link to file two.  
    
 

--------------------
file_two.htm
--------------------


    
        
    
    
        Text in file two. 
    
 

Thanks,

Rob


--- On Fri, 11/20/09, David Carlisle  wrote:

> From: David Carlisle 
> Subject: Re: [xsl] XSLT for XSL-FO internal-destination
> To: xsl-list@lists.mulberrytech.com
> Cc: xsl-list@lists.mulberrytech.com
> Date: Friday, November 20, 2009, 8:48 AM
> 
> 
> well you're leaving me to guess a lot about your uinput
> structure, but
> I'd guess that 
> 
>                
>    
> 
>            
>          select="//TocEntry">
>            
>            
> 
>                
>            
>   
> 
> 
> just puts in a single id (with possibly empty value) at the
> top of teh
> document
> you want an id for each file inclusion so perhaps
> 
> 
> 
> 
>            
>          select="//TocEntry">
>                
>                
>       
>            
>            
> 
>                
>            
>   
> David
> 
> ________________________________________________________________________
> The Numerical Algorithms Group Ltd is a company registered
> in England
> and Wales with company number 1249803. The registered
> office is:
> Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United
> Kingdom.
> 
> This e-mail has been scanned for all viruses by Star. The
> service is
> powered by MessageLabs. 
> ________________________________________________________________________
> 
> --~------------------------------------------------------------------
> XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
> or e-mail: 
> --~--
> 
> 


      

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

Re: [xsl] Decoding %-escaped chars in URI - 11/20/2009 5:58:00 PM

James A. Robinson wrote:

> At when point when I was playing around with making a useful
> library for URI manipulation per RFC 398, I put the following
> together, don't know if it might be useful to the original
> poster.

  Thanks.  If I am right, that does decode only unreserved chars.
But as the target of the decoded string is a human, I really want
to decode everything.  Actually I ended up with something very
similar (but simpler as it decodes everything encoded).

  Thanks!

-- 
Florent Georges
http://www.fgeorges.org/

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

Re: [xsl] Decoding %-escaped chars in URI - 11/20/2009 5:52:00 PM

> As a matter of interest, what's the use case?
> 
> I think the only reasons it's not there are (a) absence of a use case, and
> (b) difficulty in the detail of specifying it: what do you do for example
> with percent signs that aren't followed by two hex digits.

I think people I've talked to about this generally have in mind the equiv
of perl's URI::Escape, with the ability to either encode or decode ASCII.
Additional functionality, e.g., taking a Unicode character above the
128 range and turning it into encoded UTF-8 would be icing on the cake.

Personally, I'd have loved some basic functionality to deal with URI
escaped data at the XSLT layer, we've had several cases where data was
being over-enthusiastically encoded, e.g., apache re-encoding something
that was already encoded and Tomcat only performing one level of decoding.

Naturally the correct fix is down at the level where the mistake is
being introduced, but having the *ability* to unencode it at the XSLT
layer would have been useful.

At when point when I was playing around with making a useful library
for URI manipulation per RFC 398, I put the following together, don't
know if it might be useful to the original poster.

...

  
  
    
    
   
  
    
    

    

    
      
        
      
      
        
          
            
            
            
              
                
                
              
              
                
              
            
          
          
            
            
          
          
            
          
        
      
      
        
        
      
      
        
      
    
  

  
  
    

    
    
      
        
      
      
        
      
      
        
      
    
  
...


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
James A. Robinson                       jim.robinson@stanford.edu
Stanford University HighWire Press      http://highwire.stanford.edu/
+1 650 7237294 (Work)                   +1 650 7259335 (Fax)

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

Re: [xsl] Decoding %-escaped chars in URI - 11/20/2009 5:42:00 PM

Michael Kay wrote:

> No there's no such function.

  That's sad, but at least I'm reassured about my spec searching
skills ;-)

> As a matter of interest, what's the use case?

  I am writing a WebDAV client in XSLT, using the EXPath HTTP
client.  In the result, the paths are encoded (for instance if you
ask the list of resources in a collection, aka the files in a
directory).  See (in particular the example in 8.3.1):

    http://tools.ietf.org/html/rfc4918#section-8.3

  So to display the resource name to a human, I should decode it
first.

> (b) difficulty in the detail of specifying it: what do you do
> for example with percent signs that aren't followed by two hex
> digits.

  Yes.  I've just written such a function in plain XSLT, and I
generate an error in that case.  If I am right (but I did not
check) the input is not a valid lexical URI if this is the case
(for instance "http://.../a%2").

  Regards,

-- 
Florent Georges
http://www.fgeorges.org/

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

RE: [xsl] Decoding %-escaped chars in URI - 11/20/2009 4:49:00 PM

No there's no such function.

As a matter of interest, what's the use case?

I think the only reasons it's not there are (a) absence of a use case, and
(b) difficulty in the detail of specifying it: what do you do for example
with percent signs that aren't followed by two hex digits.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay  

> -----Original Message-----
> From: Florent Georges [mailto:lists@fgeorges.org] 
> Sent: 20 November 2009 16:35
> To: XSL Mulberry list
> Subject: [xsl] Decoding %-escaped chars in URI
> 
>   Hi,
> 
>   I guess I simply missed it, but I need a function to 
> unescape %-escaped characters in a URI (that is, the opposite 
> of the function fn:encode-for-uri) and I didn't find it in 
> the standard library.
> 
>   Did I miss it, or is it missing from the standard library 
> (and if it is, why is it so?)
> 
>   Regards,
> 
> --
> Florent Georges
> http://www.fgeorges.org/
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>       
> 
> 
> --~------------------------------------------------------------------
> XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
> or e-mail: 
> --~--
> 


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

[xsl] Decoding %-escaped chars in URI - 11/20/2009 4:35:00 PM

Hi,

  I guess I simply missed it, but I need a function to unescape
%-escaped characters in a URI (that is, the opposite of the
function fn:encode-for-uri) and I didn't find it in the standard
library.

  Did I miss it, or is it missing from the standard library (and
if it is, why is it so?)

  Regards,

-- 
Florent Georges
http://www.fgeorges.org/






















      


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

RE: [xsl] Having elements defined only once with XSLT - 11/20/2009 11:16:00 AM

Hi,

Thank you for your help and good tip. I'm using the XSLT 2.0, and you
are right, temporary tree seems to be a very reasonable suggestion. 

Janne

> Janne Luoma wrote:
> 
> > Now my XSLT script process the Source XML-file so that some of the
> > elements ('objectA', 'objectB'. 'objectC') may be resulted in the
> > beginning of the result file (or may not, based on the XSLT rules).
> That
> > XSLT script part + rules works fine!
> >
> > But in case that element ('objectB' in my sample) is defined already
> in
> > the beginning of the result file and then the same used later in the
> > document, this element should be referenced by href (not generated
> the
> > full information again!). (In cases where element is not defined in
> the
> > beginning, it should be reported fully, this works fine!). So my
> > question is: How to know which objects / elements have been
> > handled/defined already in the output, so that I could use href in
> those
> > cases?
> 
> Do you use XSLT 2.0 or 1.0?
> With 2.0 you could easily transform in a first step into a temporary
> tree stored in a variable and then on the second step check the
> temporary tree in the variable.
> With 1.0 you would need to make use of an extension function like
> exsl:node-set to do this with one transformation.
> 
> 
> --
> 
> 	Martin Honnen
> 	http://msmvps.com/blogs/martin_honnen/
> 
> --~------------------------------------------------------------------
> XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
> or e-mail: 
> --~--


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

Re: [xsl] Having elements defined only once with XSLT - 11/20/2009 11:02:00 AM

Janne Luoma wrote:

> Now my XSLT script process the Source XML-file so that some of the
> elements ('objectA', 'objectB'. 'objectC') may be resulted in the
> beginning of the result file (or may not, based on the XSLT rules). That
> XSLT script part + rules works fine! 
> 
> But in case that element ('objectB' in my sample) is defined already in
> the beginning of the result file and then the same used later in the
> document, this element should be referenced by href (not generated the
> full information again!). (In cases where element is not defined in the
> beginning, it should be reported fully, this works fine!). So my
> question is: How to know which objects / elements have been
> handled/defined already in the output, so that I could use href in those
> cases? 

Do you use XSLT 2.0 or 1.0?
With 2.0 you could easily transform in a first step into a temporary 
tree stored in a variable and then on the second step check the 
temporary tree in the variable.
With 1.0 you would need to make use of an extension function like 
exsl:node-set to do this with one transformation.


-- 

	Martin Honnen
	http://msmvps.com/blogs/martin_honnen/

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

[xsl] Having elements defined only once with XSLT - 11/20/2009 9:38:00 AM

Hi,

I'm stuck with following XSLT processing problem:

Source XML
==========

            
            	Jack
            


            
	            Jim
            


            
           	 John
            



Now my XSLT script process the Source XML-file so that some of the
elements ('objectA', 'objectB'. 'objectC') may be resulted in the
beginning of the result file (or may not, based on the XSLT rules). That
XSLT script part + rules works fine! 

But in case that element ('objectB' in my sample) is defined already in
the beginning of the result file and then the same used later in the
document, this element should be referenced by href (not generated the
full information again!). (In cases where element is not defined in the
beginning, it should be reported fully, this works fine!). So my
question is: How to know which objects / elements have been
handled/defined already in the output, so that I could use href in those
cases? 


Expected output:
================


             
  		   Jim
	  







	
		 
			   Jack
		  
	
           
	
		 
	 		   John
		  
	



Thanks in advance

Janne

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

Re: [xsl] XSLT for XSL-FO internal-destination - 11/20/2009 8:49:00 AM

well you're leaving me to guess a lot about your uinput structure, but
I'd guess that 

                   

        			
        				
                			  


just puts in a single id (with possibly empty value) at the top of teh
document
you want an id for each file inclusion so perhaps




        			
                                      
        				
                			  
David

________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
--~--

Re: [xsl] for-each tokenize() and context problem - 11/20/2009 3:29:00 AM

Sorry I haven't read your use case in detail. But from XSLT language
perspective, it's probably better to declare the variable you used, as
following:

  ...

XSLT 2.0 allows us to specify the type of a variable like, as
xs:string* above which brings the advantages to strong typing, as we
have been discussing in other threads lately.

I think, if we declare a variable as following:

  ...

The contents of the variable are the output of some sequence
instruction(s), probably, let's say which (the sequence instructions)
produce data of some XDM type.

Depending on where the variable, l_GetPartNumber is used after
declaration, the variable will be coerced to the type required by the
evaluation in a given context (I don't mean though the XSLT language
term, context :)) which is probably expensive for XSLT processor to
do, and also probably not a good program design.

So in a nutshell, I would recommend to declare the types of variables
(or whatever XSLT 2 instructions allow us to specify types, like also
for e.g, ) whereever we can know
before compilation of the stylesheets, what the types of data should
be.

On Thu, Nov 19, 2009 at 10:57 PM, Mario Madunic
 wrote:
> I have the following variable,
>
> 
> Â 
> Â  Â 
> Â  Â 
> Â  Â  Â 
> Â  Â 
> Â 
> 
>
> 
>
> It is all within a

Altova Mailing List: xsl-list

[xsl] File URI / EXPath / Saxon - 11/21/2009 12:24:00 AM

RE: [xsl] How to include ' in the argument of function - 11/20/2009 11:48:00 PM

Re: [xsl] How to include ' in the argument of function - 11/20/2009 9:53:00 PM

[xsl] How to include ' in the argument of function - 11/20/2009 9:47:00 PM

Re: [xsl] XSLT for XSL-FO internal-destination - 11/20/2009 7:15:00 PM

Re: [xsl] Decoding %-escaped chars in URI - 11/20/2009 5:58:00 PM

Re: [xsl] Decoding %-escaped chars in URI - 11/20/2009 5:52:00 PM

Re: [xsl] Decoding %-escaped chars in URI - 11/20/2009 5:42:00 PM

RE: [xsl] Decoding %-escaped chars in URI - 11/20/2009 4:49:00 PM

[xsl] Decoding %-escaped chars in URI - 11/20/2009 4:35:00 PM

RE: [xsl] Having elements defined only once with XSLT - 11/20/2009 11:16:00 AM

Re: [xsl] Having elements defined only once with XSLT - 11/20/2009 11:02:00 AM

[xsl] Having elements defined only once with XSLT - 11/20/2009 9:38:00 AM

Re: [xsl] XSLT for XSL-FO internal-destination - 11/20/2009 8:49:00 AM

Re: [xsl] for-each tokenize() and context problem - 11/20/2009 3:29:00 AM

Re: [xsl] XSLT for XSL-FO internal-destination - 11/20/2009 2:29:00 AM

Re: [xsl] Benefits of xsd-types in XSLT - 11/19/2009 7:12:00 PM

RE: [xsl] for-each tokenize() and context problem - 11/19/2009 6:39:00 PM

Re: [xsl] for-each tokenize() and context problem - 11/19/2009 6:23:00 PM

RE: [xsl] for-each tokenize() and context problem - 11/19/2009 6:19:00 PM

Re: [xsl] for-each tokenize() and context problem - 11/19/2009 5:34:00 PM

[xsl] for-each tokenize() and context problem - 11/19/2009 5:28:00 PM

Re: [xsl] Key functionality in XSL - 11/19/2009 4:59:00 PM

Re: [xsl] Date compare in XSL - 11/19/2009 4:54:00 PM

[xsl] Date compare in XSL - 11/19/2009 4:44:00 PM

[xsl] [Announce] Poll for hands-on XML training offerings in Europe - 11/19/2009 4:13:00 PM

Re: [xsl] Benefits of xsd-types in XSLT - 11/19/2009 3:53:00 PM

Re: [xsl] Benefits of xsd-types in XSLT - 11/19/2009 3:21:00 PM

Re: [xsl] Key functionality in XSL - 11/19/2009 10:03:00 AM

Re: [xsl] Key functionality in XSL - 11/19/2009 9:43:00 AM

Re: [xsl] Benefits of xsd-types in XSLT - 11/19/2009 8:35:00 AM

[xsl] Key functionality in XSL - 11/19/2009 7:41:00 AM

Re: [xsl] Benefits of xsd-types in XSLT - 11/19/2009 2:24:00 AM

Re: [xsl] generating a url to another drive on the local host - 11/19/2009 12:58:00 AM

Re: [xsl] same prefix, different namespaces (URIs) - 11/19/2009 12:34:00 AM

RE: [xsl] Benefits of xsd-types in XSLT - 11/18/2009 10:41:00 PM

RE: [xsl] generating a url to another drive on the local host - 11/18/2009 10:31:00 PM

[xsl] generating a url to another drive on the local host - 11/18/2009 10:18:00 PM

Re: [xsl] Benefits of xsd-types in XSLT - 11/18/2009 8:18:00 PM

[xsl] Benefits of xsd-types in XSLT - 11/18/2009 4:33:00 PM

Re: [xsl] same prefix, different namespaces (URIs) - 11/18/2009 3:52:00 PM

Re: [xsl] same prefix, different namespaces (URIs) - 11/18/2009 3:24:00 PM

[xsl] same prefix, different namespaces (URIs) - 11/18/2009 3:04:00 PM

Re: [xsl] Break functionality in XSL - 11/18/2009 2:24:00 PM

Re: [xsl] Break functionality in XSL - 11/18/2009 1:46:00 PM

Re: [xsl] Why is copy-namespaces="no" required? - 11/18/2009 1:22:00 PM

Re: [xsl] Why is copy-namespaces="no" required? - 11/18/2009 12:54:00 PM

Re: [xsl] Why is copy-namespaces="no" required? - 11/18/2009 12:37:00 PM

[xsl] Why is copy-namespaces="no" required? - 11/18/2009 12:25:00 PM

[xsl] instance a template from xsl:for-each-group - 11/17/2009 8:30:00 PM

Re: [xsl] measuring performance of XSLT stylesheet - 11/17/2009 5:51:00 PM

Re: [xsl] multiple elements to use for grouping - 11/17/2009 1:02:00 PM

Re: [xsl] measuring performance of XSLT stylesheet - 11/16/2009 8:24:00 PM

Re: [xsl] Merging two XML files - 11/16/2009 8:20:00 PM

[xsl] Merging two XML files - 11/16/2009 7:42:00 PM

RE: [xsl] measuring performance of XSLT stylesheet - 11/16/2009 7:35:00 PM

Re: [xsl] measuring performance of XSLT stylesheet - 11/16/2009 6:57:00 PM

Re: [xsl] reversing dictionary in xml - 11/16/2009 6:16:00 PM

Re: [xsl] reversing dictionary in xml - 11/16/2009 6:14:00 PM

Re: [xsl] measuring performance of XSLT stylesheet - 11/16/2009 5:13:00 PM

[xsl] measuring performance of XSLT stylesheet - 11/16/2009 5:11:00 PM

Re: [xsl] reversing dictionary in xml - 11/16/2009 5:06:00 PM

Re: [xsl] Does XSLT contain an easy means of determining if a string - 11/16/2009 1:52:00 PM

RE: [xsl] Display numeric string of the form 01W or 02Y - 11/16/2009 1:46:00 PM

[xsl] reversing dictionary in xml - 11/16/2009 1:32:00 PM

Re: [xsl] Happy Birthday! - 11/16/2009 11:34:00 AM

RE: [xsl] Happy Birthday! - 11/16/2009 11:24:00 AM

[xsl] Happy Birthday! - 11/16/2009 11:16:00 AM

RE: [xsl] Display numeric string of the form 01W or 02Y - 11/16/2009 9:27:00 AM

RE: [xsl] Does XSLT contain an easy means of determining if a string - 11/16/2009 9:24:00 AM

Re: [xsl] Does XSLT contain an easy means of determining if a string - 11/16/2009 6:34:00 AM

Re: [xsl] Does XSLT contain an easy means of determining if a string - 11/16/2009 5:46:00 AM

Re: [xsl] Does XSLT contain an easy means of determining if a string - 11/16/2009 5:44:00 AM

Re: [xsl] Does XSLT contain an easy means of determining if a string - 11/16/2009 5:41:00 AM

[xsl] Does XSLT contain an easy means of determining if a string - 11/16/2009 5:35:00 AM

RE: [xsl] Extra spaces - 11/16/2009 12:20:00 AM

RE: [xsl] Display numeric string of the form 01W or 02Y - 11/16/2009 12:18:00 AM

RE: [xsl] axis test for namespace nodes - 11/16/2009 12:17:00 AM

[xsl] axis test for namespace nodes - 11/15/2009 10:50:00 PM