Altova Mailing List: xsl-list

Re: [xsl] removing a specific namespace declaration - 11/8/2009 1:32:00 AM

At 2009-11-07 16:42 -0800, tom a wrote:
>I'm trying to remove what I believe to be an unused namespace 
>declaration from the output.

Unused namespace declarations are supposed to be benign to processing 
applications.  Why is it you want to remove it?

>eg:
>
>Source:
>
>
>
>Becomes:
>
>
>
>ie, the foo namespace is removed in the transformation.
>
>I've seen many posts on removing all namespaces, but can't figure 
>out how to remove a specific namespace.

In XSLT one neither removes all namespaces nor removes specific namespaces.

In XSLT and in XQuery one is always creating result trees from 
scratch using the information found in source trees.

To achieve what you want you need to reconstitute the elements and 
inhibit the copying of the foo namespace, rather than copying the 
elements, because copying an element has the effect of copying all 
attached namespace nodes.

I hope the example below helps.

. . . . . . . . . Ken

T:\ftemp>type toma.xml



T:\ftemp>call xslt toma.xml toma.xsl

T:\ftemp>type toma.xsl




   
     
     
     
   



   



T:\ftemp>

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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] removing a specific namespace declaration - 11/8/2009 12:43:00 AM

I'm trying to remove what I believe to be an unused namespace declaration from the output. eg:

Source:



Becomes:



ie, the foo namespace is removed in the transformation.

I've seen many posts on removing all namespaces, but can't figure out how to remove a specific namespace.

Any thoughts are greatly appreciated.



      

--~------------------------------------------------------------------
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] is there a way to output XML with invalid qnames? - 11/7/2009 10:20:00 AM

> Before I give myself a headache trying to figure it out, I 
> was wondering if anyone could suggest a better approach I 
> should look into.

I would suggest outputting valid XML, and then post-processing it with
non-XML software (e.g. sed/Perl) to generate non-XML output.

Regards,

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


--~------------------------------------------------------------------
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] fo:basic-link - 11/7/2009 3:55:00 AM

At 2009-11-06 19:33 -0800, Mark Wilson wrote:
>I am using FOP and it built the PDF files with internal and external 
>basic links without  using the URI wrapper.

The  syntax is only for external links not 
internal links.  Internal link anchors are simple name tokens.

Note that  is for any external reference, such as 
the src=  attribute in , in background-image=, 
and in a number of other lesser-used attributes.

Many stylesheet writers forget to use  syntax for src=.

>I got my syntax [without the URI(...)] from an online tutorial. 
>However, I recognize that the proper syntax should be used, and have 
>altered my code accordingly.

Most vendors support the incorrect syntax but I agree with you that 
isn't a reason it should be used.

>The "s.pdf#block1" experiment did not work. I will take my question 
>to an Adobe PDF list, assuming I can find one.

I look forward to hearing of your progress in finding how to do this.

. . . . . . . . . . . Ken

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: 
--~--

Re: [xsl] fo:basic-link - 11/7/2009 3:34:00 AM

Hi Ken,
As always, I am amazed at your prompt at pointed help.
I am using FOP and it built the PDF files with internal and external basic 
links without  using the URI wrapper. I got my syntax [without the URI(...)] 
from an online tutorial. However, I recognize that the proper syntax should 
be used, and have altered my code accordingly.

The "s.pdf#block1" experiment did not work. I will take my question to an 
Adobe PDF list, assuming I can find one.
Thanks,
Mark 



--~------------------------------------------------------------------
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] fo:basic-link - 11/7/2009 2:47:00 AM

At 2009-11-06 18:26 -0800, Mark Wilson wrote:
>I have been reviewing  and have learned how to use 
>the external- and internal- destination properties. Two test code 
>fragments are listed below. Is there a way to make
>    
>take me directly to
>    block1
>
>within the s.pdf document rather than just opening the "s.pdf" document?
>If so, how would I change
>    
>to do that?

First of all, the syntax should be:

   external-destination='url("----uri-here----")'

... but that isn't the answer to your question.

The semantics of now to resolve external URI specifications are 
outside of the XSL-FO specification.  Section 7.23.6 reads:

   "How the destination (sub-)resource is used and/or displayed is
    application and implementation-dependent. In typical browsing
    applications, the destination resource is displayed in the
    browser positioned so that some rendered portion resulting from
    the processing of some part of the specific destination
    sub-resource indicated by the fragment identifier is in view."

Therefore it is up to (a) the vendor's software creating the output 
from your XSL-FO and (b) the software that is engaged by the reader 
that is reading your published XSL-FO to you.  If you are publishing 
to PDF then this would be (a) the vendor of the XSL-FO to PDF 
creation tool and (b) the platform (probably the browser) that is 
engaged when clicking on a link, and I suppose, the reader engaged by 
the browser to catch the link that was clicked.

I would experiment with:

   external-destination='url("s.pdf#block1")'

.... but I don't know of any browser/reader that supports such a 
syntax but perhaps your platform combination described above supports 
that (it has been many years since I've tried).

I hope this helps.  I would appreciate anyone on the list who knows 
of a more reliable syntax to relate their own experiences, but I'm 
not sure we'll hear from anyone.

. . . . . . . . . . . Ken

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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] fo:basic-link - 11/7/2009 2:27:00 AM

Hi all,
I have been reviewing  and have learned how to use the 
external- and internal- destination properties. Two test code fragments are 
listed below. Is there a way to make
    
take me directly to
    block1

within the s.pdf document rather than just opening the "s.pdf" document?
If so, how would I change
    
to do that?

Thanks,
Mark

Listing fragment 1: set Id

     
             block1
     
     
     
          
      
      
   

Listing Fragment 2: make link

        
                
                      
               
        
        
               
        
 



--~------------------------------------------------------------------
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] is there a way to output XML with invalid qnames? - 11/7/2009 2:09:00 AM

At 2009-11-06 16:57 -0800, Jessica Britton wrote:
>I'm trying to format XML files so that I can display them as 
>examples in a wiki. I'd like the element names in the examples to 
>link to other wiki pages, so I'm trying to figure out the best way 
>to take source like this:
>
>
>     value
>
>
>
>And get output like this:
>
><[ns:elementName1|page 1]>
>     <[ns:elementName2|page 2]>value
>

This was an interesting challenge!  Especially coming up with 
monotonically increasing page number references for unique element 
names across the instance.

>Of course, "[ns:elementName|page]" isn't a valid qname so just 
>trying to rename the elements in an XML to XML transform doesn't work.
>...
>Before I give myself a headache trying to figure it out, I was 
>wondering if anyone could suggest a better approach I should look into.

I think the example below suits your needs, though I'm making 
guesses.  As a more extensive test I ran the stylesheet through 
itself in order to have a larger test.  This isn't a very rigourous 
test, and I haven't checked nearly all the edge cases but it should 
do a lot for you as it stands and may meet your needs.

I hope this helps.

. . . . . . . . . . . Ken


T:\ftemp>type jessica.xml

     value


T:\ftemp>call xslt jessica.xml xml2wiki.xsl
<[ns:elementName1|page 1] xmlns:ns="urn:X-Jessica">
     <[ns:elementName2|page 2]>value

T:\ftemp>type xml2wiki.xsl








   
   <[
   |page 
   
   
   
   
   ]
   
   
     
     :
     
   
   
   
     
     
     "
   
   
     
       
       >
       
       </
       
       >
     
     
       
       />
     
   



   <!--
   
   -->



   <?
   
   ?>



   
   
     
       
       &lt;
       
         
       
     
     
       
     
   




T:\ftemp>call xslt xml2wiki.xsl xml2wiki.xsl
<[xsl:stylesheet|page 1] 
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">

<[xsl:output|page 2] method="text"/>

<[xsl:key|page 3] name="names" match="*" use="name(.)"/>

<[xsl:template|page 4] match="*">
   
   <[xsl:text|page 5]><[
   <[xsl:value-of|page 6] select="name(.)"/>|page <[xsl:text|page 5]/>
   
   <[xsl:variable|page 7] name="first" select="key('names',name(.))[1]"/>
   
   <[xsl:value-of|page 6] 
select="count(                         ($first/preceding::* | 
$first/ancestor::*)                         [generate-id(.)= 
                 generate-id(key('names',name(.))[1])]) + 1"/>
   <[xsl:text|page 5]>]
   
   <[xsl:for-each|page 8] 
select="namespace::*[not(.=../../namespace::*) 
and                                       name(.)!='xml']">
     <[xsl:value-of|page 6] select="concat(' ','xmlns')"/>
     <[xsl:if|page 9] test="name(.)">:<[xsl:value-of|page 6] 
select="name(.)"/>
     <[xsl:value-of|page 6] select="concat('="',.,'"')"/>
   
   
   <[xsl:for-each|page 8] select="@*">
     <[xsl:value-of|page 6] select="concat(' ',name(.),'="')"/>
     <[xsl:call-template|page 10] name="do-text"/>
     <[xsl:text|page 5]>"
   
   <[xsl:choose|page 11]>
     <[xsl:when|page 12] test="node()">
       
       <[xsl:text|page 5]>>
       <[xsl:apply-templates|page 13] select="node()"/>
       <[xsl:text|page 5]></
       <[xsl:value-of|page 6] select="name(.)"/>
       <[xsl:text|page 5]>>
     
     <[xsl:otherwise|page 14]>
       
       <[xsl:text|page 5]>/>
     
   


<[xsl:template|page 4] match="comment()">
   <[xsl:text|page 5]><!--
   <[xsl:value-of|page 6] select="."/>
   <[xsl:text|page 5]>-->


<[xsl:template|page 4] match="processing-instruction()">
   <[xsl:text|page 5]><?
   <[xsl:value-of|page 6] select="concat(name(.),' ',.)"/>
   <[xsl:text|page 5]>?>


<[xsl:template|page 4] match="text()" name="do-text">
   <[xsl:param|page 15] name="rest" select="."/>
   <[xsl:choose|page 11]>
     <[xsl:when|page 12] test="contains($rest,'<')">
       <[xsl:value-of|page 6] select="substring-before($rest,'<')"/>
       <[xsl:text|page 5]><
       <[xsl:call-template|page 10] name="do-text">
         <[xsl:with-param|page 16] name="rest" 
select="substring-after($rest,'<')"/>
       
     
     <[xsl:otherwise|page 14]>
       <[xsl:value-of|page 6] select="$rest"/>
     
   



T:\ftemp>rem



--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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] is there a way to output XML with invalid qnames? - 11/7/2009 12:59:00 AM

I'm trying to format XML files so that I can display them as examples in a wiki. I'd like the element names in the examples to link to other wiki pages, so I'm trying to figure out the best way to take source like this:


    value



And get output like this:

<[ns:elementName1|page 1]>
    <[ns:elementName2|page 2]>value


Of course, "[ns:elementName|page]" isn't a valid qname so just trying to rename the elements in an XML to XML transform doesn't work. 

I've messed around a bit trying to output HTML that looks the way I want it to look, including indentation, eg:


      
      
      
            <></>



That works fine for simple inline elements, but it I'm not sure how to deal with nodes with children.

Before I give myself a headache trying to figure it out, I was wondering if anyone could suggest a better approach I should look into.

            
    



--~------------------------------------------------------------------
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] The benefits of exact selection - 11/6/2009 4:43:00 PM

On Fri, Nov 6, 2009 at 4:51 PM, Jesper Tverskov  wrote:
> I would like to know about real life cases where removing not
> necessary wildcard matching improved the transformation speed?

I have experienced to specify exact paths instead of XPath wildcards,
to speed up XPath processing time significantly, when size of XML tree
was quite large, and large number of XML documents were processed in a
batch. In my use case, both these constraints were present.

-- 
Regards,
Mukul Gandhi

--~------------------------------------------------------------------
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] SOAP extension compatible with AltovaXML - 11/6/2009 4:18:00 PM

[[ it seems that one never found its way to the list, sorry
   if posted twice... ]]

Fabre Lambeau wrote:

  Hi,

> Has anyone come across (or implemented) a SOAP or http-send
> extension for XSLT 2.0 that would work with the AltovaXML
> processor?

  None that I am aware of.  My first advice would be to see if
you can switch to Saxon 9.

  If you cannot, the implementation (in Java) of the EXPath HTTP
Client is (I think) quite properly decoupled between what's Saxon
specific and the rest (if I remember well, the Apache HTTP Client
stuff is not that well entirely isolated in its own layer.)

  For what I've seen on the AltovaXML doc, it supports calling
Java methods, so if you're really interested, you should be able
to replace the Saxon layer of EXPath HTTP Client (mostly dealing
with parsing the http:request element and serializing the
http:response element.)  They do not say how they pass XDM nodes
to Java though (they only document how atomic types are mapped to
Java types.)

  If you're interested, please join the EXPath mailing list
 to ask for more information.

  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] The benefits of exact selection - 11/6/2009 4:07:00 PM


is not same as 

you can`t compare this two XPath`s alone from XML - it is same as
compare "soft with warm" :)

can bet your students high esimate comparing push and pool scheme for
XSLT (also known as data-driven and template-driven models)


2009/11/6 Michael Kay :
>>
>> Using Saxon PE from inside Oxygen, I transformed 20 times for each.
>> Here is the average time as reported by Oxygen:
>>
>> 1) Exact selection: 4.1s
>> 2) Wildcard selection: 5.0s
>>
>> That is a difference. But it is also fair to say that for
>> most transformations, on a small dataset, it will be
>> impossible to measure a difference of any importance.
>>
>
> Does your transformation time include document parsing/building time? For a
> small task like this, the parsing time will completely swamp the
> transformation time. If the parsing time is 4.0s, then your figure shows the
> transformation time is different by a factor of 10.
>
> Regards,
>
> Michael Kay
> http://www.saxonica.com/
> http://twitter.com/michaelhkay
>
>
> --~------------------------------------------------------------------
> 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] Adding a clickable URL to XSL - 11/6/2009 2:47:00 PM

Ah, like an image. Thanks!



----- Original Message ----
From: Martin Honnen 
To: xsl-list@lists.mulberrytech.com
Sent: Fri, November 6, 2009 9:30:00 AM
Subject: Re: [xsl] Adding a clickable URL to XSL

Anonymous Anonymous wrote:
> How do I make just the URL element below appear as a clickable link? The ... represents omitted HTML formatting.

>         

          
            
              
            
          
-- 
    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] Adding a clickable URL to XSL - 11/6/2009 2:30:00 PM

Anonymous Anonymous wrote:
> How do I make just the URL element below appear as a clickable link? The ... represents omitted HTML formatting.

>         

           
             
               
             
           
-- 

	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] Adding a clickable URL to XSL - 11/6/2009 2:28:00 PM

How do I make just the URL element below appear as a clickable link? The ... represents omitted HTML formatting.

Thanks,
XML newbie

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 





...


    

...
        
        
        
    








      

--~------------------------------------------------------------------
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] Trouble digesting grouping - 11/6/2009 2:05:00 PM

Flanders, Charles E (US SSA) wrote:
> I'm struggling with a grouping problem. I've had some success with simpler structures, but this one has me stumped. This is an XML to XML transform.
> 
> I need to eliminate the parent  completely, output the  intact, but grab the  elements, create a single , then a  wrapper element for each . Then output the structures interspersed with the tables. I can't seem to separate the tables and figures. What I'm ending up with is a single  with all the , then the tables. 

This stylesheet



   

   
     
       
     
   

   
     
   

   
     
       
         
           
             
             <xsl:apply-templates select="current-group()"/>
           </figure>
         </xsl:when>
         <xsl:otherwise>
           <xsl:apply-templates select="current-group()"/>
         </xsl:otherwise>
       </xsl:choose>
     </xsl:for-each-group>
   </xsl:template>

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

</xsl:stylesheet>


when applied to

<install>
    <proc>
      <step1>
         <para></para>
</step1>
</proc>
<para>
<table>
          All the table stuff
    </table>
    <graphic/>
    <graphic/>
    <graphic/>
    <table>
         All the table stuff
    </table>
    <graphic/>
    <graphic/>
    <graphic/>
</para>
</install>

outputs

<install>

      <step1>
         <para/>
    </step1>

    <table>
          All the table stuff
    </table>
    <figure>
       <title/>
       <subfig>
          <graphic/>
       </subfig>
       <subfig>
          <graphic/>
       </subfig>
       <subfig>
          <graphic/>
       </subfig>
    </figure>
    <table>
         All the table stuff
    </table>
    <figure>
       <title/>
       <subfig>
          <graphic/>
       </subfig>
       <subfig>
          <graphic/>
       </subfig>
       <subfig>
          <graphic/>
       </subfig>
    </figure>
</install>
-- 

	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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] Trouble digesting grouping - 11/6/2009 1:42:00 PM</h1>
<pre>I'm struggling with a grouping problem. I've had some success with simpler structures, but this one has me stumped. This is an XML to XML transform.

I need to eliminate the parent <para > completely, output the <table> intact, but grab the <graphic> elements, create a single <figure>, then a <subfig> wrapper element for each <graphic>. Then output the structures interspersed with the tables. I can't seem to separate the tables and figures. What I'm ending up with is a single <figure> with all the <subfig>, then the tables. 


<install>
   <proc>
     <step1>
        <para></para>
</step1>
</proc>
<para>
<table>
         All the table stuff
   </table>
   <graphic>
   <graphic>
   <graphic>
   <table>
        All the table stuff
   </table>
   <graphic>
   <graphic>
   <graphic>
</para>
</install>

Output that I desire:

<install>
   <step1>
     <para></para>
   <step1>
   <table>
      All the table stuff
   </table>
   <figure><title/>
     <subfig><graphic></subfig>
     <subfig><graphic></subfig>
      <subfig><graphic></subfig>
   </figure>
   <table>
      All the table stuff
   </table>
   <figure><title/>
     <subfig><graphic></subfig>
     <subfig><graphic></subfig>
      <subfig><graphic></subfig>
   </figure>
</install>

Output that I'm getting (and I've tried defining the group in various ways, this is my last iteration).

<install>
   <step1>
      <para></para>
   </step1>
<figure><title/>
   <subfig><graphic/></subfig>
   <subfig><graphic/></subfig>
   <subfig><graphic/></subfig>
   <subfig><graphic/></subfig>
   <subfig><graphic/></subfig>
   <subfig><graphic/></subfig>
</figure>
<table></table>
<table></table>
</install>

My current templates: (Wendell, my apologies for just not getting this). Using  XSLT 2.0.



<install>
   <xsl:apply-templates select="descendant::step1"/>
   <xsl:if test="child::proc/following-sibling::para/(child::table|graphic)">
      <xsl:apply-templates select="child::proc/following-sibling::para/child::table | child::para" mode="install"/>
   </xsl:if>
</install>

   <xsl:template match="table" mode="install">
     <table>
     <xsl:apply-templates/>
     </table>
   </xsl:template>
   
   <xsl:template match="install/para" mode="install">
     <figure>
   <xsl:for-each-group select="*" group-starting-with="graphic">
     <xsl:for-each select="current-group()[self::graphic]">
        <subfig>
           <xsl:copy-of select="."/>
        </subfig>
     </xsl:for-each>
   </xsl:for-each-group>
        </figure>    
   </xsl:template>

Charles Flanders


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] The benefits of exact selection - 11/6/2009 11:46:00 AM</h1>
<pre>> 
> Using Saxon PE from inside Oxygen, I transformed 20 times for each.
> Here is the average time as reported by Oxygen:
> 
> 1) Exact selection: 4.1s
> 2) Wildcard selection: 5.0s
> 
> That is a difference. But it is also fair to say that for 
> most transformations, on a small dataset, it will be 
> impossible to measure a difference of any importance.
> 

Does your transformation time include document parsing/building time? For a
small task like this, the parsing time will completely swamp the
transformation time. If the parsing time is 4.0s, then your figure shows the
transformation time is different by a factor of 10.

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] The benefits of exact selection - 11/6/2009 11:38:00 AM</h1>
<pre>> 1) Exact selection: 4.1s
> 2) Wildcard selection: 5.0s
> 
> That is a difference. But it is also fair to say that for most
> transformations, on a small dataset, it will be impossible to measure
> a difference of any importance.

Well, the difference may not seem like much in the context of a single
tranformation but think about it in terms of a production system needing
to execute many transformations per second.

I've got a system which is running an average of 191 transformations
per second, and increasing the run-time by 22% in that situation would
be catastrophic for me.


Jim

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] The benefits of exact selection - 11/6/2009 11:22:00 AM</h1>
<pre>Hi list

We always hear that we should select as exactly as possible, and that
wildcards are inefficient. It makes sense.

But I'm tired of just telling it to my students so I set out to
construct a little transformation test that can demonstrate it in the
classroom.

I ended up with a million lines subdivided into 1050 children, each
having 140 children, each having 3 children. In what I believe is the
last element in document order, I might be wrong, I added a lonely
attribute with some value.

The two alternative select expressions are as follows:

1)
<xsl:value-of select="/document/colors[1050]/color[140]/dec/@num"/>
and
2)
<xsl:value-of select="//@num"/>

Using Saxon PE from inside Oxygen, I transformed 20 times for each.
Here is the average time as reported by Oxygen:

1) Exact selection: 4.1s
2) Wildcard selection: 5.0s

That is a difference. But it is also fair to say that for most
transformations, on a small dataset, it will be impossible to measure
a difference of any importance.

I would like to know about real life cases where removing not
necessary wildcard matching improved the transformation speed?

Cheers
Jesper Tverskov

http://www.xmlkurser.dk
http://www.xmlplease.com

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] decimal vs double value spaces - 11/6/2009 7:14:00 AM</h1>
<pre>On Thu, Nov 5, 2009 at 10:23 PM, C. M. Sperberg-McQueen
<cmsmcq@blackmesatech.com> wrote:
>
> As far as I can tell (but I am not a numerical analyst), every
> number expressible with a finite sequence of binary digits
> can also be expressed with a finite sequence of decimal digits
> (ten being divisible by two), so every number in the value
> space of xs:double also makes an appearance in the value
> space of xs:decimal. (Recall though that for simplicity XSD
> treats all primitive value spaces as disjoint, so a sentence
> like "The value space of xs:double is a subset of the value
> space of xs:decimal" would provoke howls of pain from some
> quarters.)
>

I hope I'm taking this not too far off from this list's topic, but
one should see the point "some quarters" are trying to uphold.
While it is not debatable that the set of real numbers represented
by xs:double is a subset of those represented by xs:decimal, a
distinction must be made w.r.t. their respective value spaces
which happen to be part of different *data type* definitions. In
XML, data typing is associated with representation issues
such as facets; in programming languages distinctions are
being made by different (arithmetic) operations being applicable,
or by conversions, etc.

-W

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] decimal vs double value spaces - 11/5/2009 10:37:00 PM</h1>
<pre>> Some numbers are in the decimal space but not in the double space.
> For example, the decimal value space includes the value 0.1 (one
> tenth), because that number can be represented using a finite
> number of decimal digits. The double value space does not include
> that number, because in binary notation the representation of that
> number is a repeating fraction.

But there's a bit more nuance to it than that. 

First, xsd:double (aka an IEEE 754 "double" or "binary64") has
distinct limits, with an approximate range of +/- 1.8 E 308 (base
10). So if you want to express a number larger than that positive or
smaller than that negative, you're out of luck. (Note that you
probably don't: 1.8 E 308 exceeds the estimate of the number of sub-
atomic particles in the universe by perhaps two hundred orders of
magnitude.)

Also a binary64 has the property of the gaps between representable
numbers being unequal -- they get larger as the numbers get further
from zero. There is actually an interesting formula for calculating
the space between representable numbers, but I don't remember it.

See
http://en.wikipedia.org/wiki/Double_precision_floating-point_format.

The point of the post is, in part, to say that if you want precision,
use xsd:decimal. If you need a (*very*) wide range of values and can
live without some precision, use xsd:double.[1]

Any more about this should probably be taken off-list, as it isn't
really that XSL-specific. (But it is interesting. :-)

Note
----
[1] This is precisely why the TEI data.decimal macro was defined as
    "xsd:decimal | xsd:double".

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] decimal vs double value spaces - 11/5/2009 9:24:00 PM</h1>
<pre>On 5 Nov 2009, at 04:28 , Justin Johansson wrote:

> Would someone kindly enlighten me as to the difference in
> the value spaces of xs:decimal's and xs:double's.

The xs:decimal value space contains every number expressible
in decimal notation using a finite number of digits.

The xs:double value space contains every number expressible
using a binary mantissa + exponent representation as
specified by IEEE 754.

Some numbers are in the decimal space but not in the double
space. For example, the decimal value space includes the
value 0.1 (one tenth), because that number can be represented
using a finite number of decimal digits.  The double value
space does not include that number, because in binary
notation the representation of that number is a repeating
fraction.

Some numbers are in neither space, e.g. the fraction 1/3,
which requires an infinitely repeating fraction both in
decimal and in binary.  And of course neither value space
contains any irrational numbers.

As far as I can tell (but I am not a numerical analyst), every
number expressible with a finite sequence of binary digits
can also be expressed with a finite sequence of decimal digits
(ten being divisible by two), so every number in the value
space of xs:double also makes an appearance in the value
space of xs:decimal. (Recall though that for simplicity XSD
treats all primitive value spaces as disjoint, so a sentence
like "The value space of xs:double is a subset of the value
space of xs:decimal" would provoke howls of pain from some
quarters.)

>
> I understand that the former doesn't lexically accept exponent
> notation (E+02 e.g.) but note that some (possibly unfinished/
> possibly naive) Java XPath engines internally represent xs:decimal and
> xs:double as Java doubles thereby reducing the (internal) distinction
> to nought.

I guess they are counting on the difference between the two
value spaces not to make much difference to their users.

Sometimes it doesn't; an implementor might well decide that
finishing the support for the sibling axes (or some other
feature) was more urgent than figuring out how to shift to
BigDecimal so that xs:decimal is supported properly.

If they think the implementation is conforming, though, I
think they are naive.

HTH

-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com
* http://cmsmcq.com/mib
* http://balisage.net
****************************************************************





--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] How to code with relative context: "if the next node - 11/5/2009 6:02:00 PM</h1>
<pre>Ben Stover wrote:
> I would like to copy something to the target XML doc context (!) depending from the value of a node on the same level.
> 
> It should all look similar to the following pseudo code:
> 
> ...assume we are on level/inside <aaa><bbb><ccc>
> <xs:if <ddd>...</ddd> contains a non-whitespace value then>
>   <mytext>yes value found<mytext>
> <xs:else>
>   <myothertext>no value found</myothertext>
> </xs:if>
> ...
> </ccc>...</bbb>....</aaa>
> 
> How can I code this with XSLT ?
> 
> Again: If possible the condition should be context dependent. I don't want to code
> the full XPath  /aaa/bbb/ccc/ddd in the "if" clause.
> Instead the XPath expression should be relative to the current position

Well if you have
   <xsl:template match="ccc">
or maybe
   <xsl:template match="aaa/bbb/ccc">
then in that template you can certainly use
     <xsl:choose>
       <xsl:when test="ddd[normalizes-space()]">
         <mytext>yes value found<mytext>
       </xsl:when>
       <xsl:otherwise>
         <myothertext>no value found</myothertext>
       </xsl:otherwise>
     </xsl:choose>

-- 

	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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] How to code with relative context: "if the next node - 11/5/2009 5:57:00 PM</h1>
<pre>I would like to copy something to the target XML doc context (!) depending from the value of a node on the same level.

It should all look similar to the following pseudo code:

...assume we are on level/inside <aaa><bbb><ccc>
<xs:if <ddd>...</ddd> contains a non-whitespace value then>
  <mytext>yes value found<mytext>
<xs:else>
  <myothertext>no value found</myothertext>
</xs:if>
...
</ccc>...</bbb>....</aaa>

How can I code this with XSLT ?

Again: If possible the condition should be context dependent. I don't want to code
the full XPath  /aaa/bbb/ccc/ddd in the "if" clause.
Instead the XPath expression should be relative to the current position

Thank you 
Ben






--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/5/2009 4:53:00 PM</h1>
<pre>Jesper,

At 04:34 AM 11/5/2009, you wrote:
>The above is of cause only one type of dataset, but it shows to me
>that xsl:key can make a big difference and that fine tuning a
>template's match attribute can make a big difference.
>
>But it must all be done carefully, and it is necessary to analyze the
>dataset to find the best approach, and to test different approaches in
>order to find the best one (fast).

This thread is fascinating and informative: thanks for instigating it.

But I hasten to add that your findings are relevant to Saxon and may 
not (probably will not) be the same for other processors. There, use 
of key() may make less or (in many cases) even more of a difference.

This doesn't make the findings useless: on the contrary. But it does 
suggest, once again, that it is easy to overgeneralize when it comes 
to optimization. I can't count the times I have talked with students 
(usually fairly advanced ones) about contortions in their code, 
rationalized on the basis of optimization, which actually offered no 
effective advantages in practice. :-)

Cheers,
Wendell


======================================================================
Wendell Piez                            mailto:wapiez@mulberrytech.com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/5/2009 4:46:00 PM</h1>
<pre>To complete the picture, I followed MK's advice and went to XMark - An
XML Benchmark Project, http://www.xml-benchmark.org/downloads.html,
and downloaded the ready-made-document of a 100 MB to see xsl:key at
work on a more realistic dataset.

To make transformations from inside Oxygen it was necessary to set
-Xmx256m up to -Xmx700m in oxygen.bat.

I used the following stylesheet:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
    <!-- List the names of persons and the number of items they bought.
            (joins person, closed_auction) -->
    <xsl:output indent="yes"/>

       <xsl:template match="/">
           <items>
        <xsl:for-each select="/site/people/person">
            <xsl:variable name="a"
                select="/site/closed_auctions/closed_auction[buyer/@person =
                current()/@id]"/>
            <item person="{name}"><xsl:value-of select="count($a)"/></item>
        </xsl:for-each>
           </items>
       </xsl:template>
</xsl:stylesheet>

Saxon Home Edtion: 1. test: 876.9s, 2.test: 911.1s
Enterprise Edition: 1. test: 13.2s, 2. test: 13.0s both using
Optimization level 10.
Enterprise Edition: 3. test: 549.5s, 4. test: 556.5s using
Optimization level 1 and 5!

In Saxon's documentation we can read: "currently all values other than
0 results in full optimization but this is likely to change in
future." I don't understand why optimization level 1 and 5 are not as
good as 10 considering the documentation,  and I don't understand why
someone would want less than full optimization?

I then used the stylesheet below using xsl:key:

Saxon Home Edition: 1. test: 12.8s, 2. test: 13.1
That is: xsl:key in Home Edition is as good as the build in
optimization level 10 in Enterprise Edition making xsl:key not
necessary in EE in most situations.

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
    <!-- List the names of persons and the number of items they bought.
            (joins person, closed_auction) -->
    <xsl:output indent="yes"/>
    <xsl:key name="k" match="/site/closed_auctions/closed_auction"
use="buyer/@person"/>

       <xsl:template match="/">
           <items>
        <xsl:for-each select="/site/people/person">
            <xsl:variable name="a"
                select="key('k', @id)"/>
            <item person="{name}"><xsl:value-of select="count($a)"/></item>
        </xsl:for-each>
           </items>
       </xsl:template>
</xsl:stylesheet>

Cheers,
Jesper Tverskov
http://www.xmlplease.com

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] how to exclude namespaces from copy-of - 11/5/2009 3:53:00 PM</h1>
<pre>Thank you. That makes sense. I took your advice and created this template
    <xsl:template match="*" mode="fragment">
        <xsl:element name="{local-name()}">
            <xsl:value-of select="." />
            <xsl:apply-templates select="*" mode="fragment" />
        </xsl:element>
    </xsl:template>

Now from another template that processes the atom feed item I call it 
like this:
            <xsl:when test="@type='xhtml' or @type = 
'application/xhtml+xml'">
                <fragment>
                        <xsl:apply-templates mode="fragment" 
select="xhtml:div" />  
                </fragment>
            </xsl:when>
           <xsl:when test="@type='html' or @type = 'text/html'">
                <xsl:value-of select="." />
            </xsl:when>
            <xsl:otherwise>
                <xsl:value-of select="normalize-space()" />
            </xsl:otherwise>

IT works well now!


Michael Kay wrote:
> Although xsl:copy-of in XSLT 2.0 can exclude unused namespaces
> (copy-namespaces="no"), it can't remove declarations of namespaces that are
> actually in use. You don't actually want to make a copy of the data, you
> want to transform it by changing the names of the elements. Remember that
> the difference between <rss/> and <rss xmlns="xyz"/> is not just a namespace
> declaration - the two elements have different names. So you need to do a
> "renaming identity transform" along the lines
>
> <xsl:template match="*">
>   <xsl:element name="{local-name()}">
>     <xsl:apply-templates select="*"/>
>   </xsl:element>
> </xsl:template>
>
> Regards,
>
> Michael Kay
> http://www.saxonica.com/
> http://twitter.com/michaelhkay  
>
>   
>> -----Original Message-----
>> From: cert21 [mailto:cert21@ptd.net] 
>> Sent: 05 November 2009 15:13
>> To: xsl-list@lists.mulberrytech.com
>> Subject: [xsl] how to exclude namespaces from copy-of
>>
>> Hello!
>>
>> I am trying to parse the atom feed using the xsl template.
>>
>> The item in the feed contains this element: (example) <div 
>> xmlns="http://www.w3.org/1999/xhtml" 
>> xmlns:dc="http://purl.org/dc/elements/1.1/" 
>> xmlns:thr="http://purl.org/syndication/thread/1.0">
>> <p>
>> October and November are busy months for Amazon Web 
>> Services!</p> </div>
>>
>> I want to copy the div with all its child elements, so I use 
>> copy-of The problem is that I don't want the 
>> xmlns="http://www.w3.org/1999/xhtml"
>> or xmlns:dc or any other extra data in the div attribute
>>
>> I just want the result to be
>> <div>
>> <p>
>> October and November are busy months for Amazon Web 
>> Services!</p> </div>
>>
>> How can I do this?
>>
>> Thank you.
>>
>>     
>


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] how to exclude namespaces from copy-of - 11/5/2009 3:27:00 PM</h1>
<pre>Although xsl:copy-of in XSLT 2.0 can exclude unused namespaces
(copy-namespaces="no"), it can't remove declarations of namespaces that are
actually in use. You don't actually want to make a copy of the data, you
want to transform it by changing the names of the elements. Remember that
the difference between <rss/> and <rss xmlns="xyz"/> is not just a namespace
declaration - the two elements have different names. So you need to do a
"renaming identity transform" along the lines

<xsl:template match="*">
  <xsl:element name="{local-name()}">
    <xsl:apply-templates select="*"/>
  </xsl:element>
</xsl:template>

Regards,

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

> -----Original Message-----
> From: cert21 [mailto:cert21@ptd.net] 
> Sent: 05 November 2009 15:13
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] how to exclude namespaces from copy-of
> 
> Hello!
> 
> I am trying to parse the atom feed using the xsl template.
> 
> The item in the feed contains this element: (example) <div 
> xmlns="http://www.w3.org/1999/xhtml" 
> xmlns:dc="http://purl.org/dc/elements/1.1/" 
> xmlns:thr="http://purl.org/syndication/thread/1.0">
> <p>
> October and November are busy months for Amazon Web 
> Services!</p> </div>
> 
> I want to copy the div with all its child elements, so I use 
> copy-of The problem is that I don't want the 
> xmlns="http://www.w3.org/1999/xhtml"
> or xmlns:dc or any other extra data in the div attribute
> 
> I just want the result to be
> <div>
> <p>
> October and November are busy months for Amazon Web 
> Services!</p> </div>
> 
> How can I do this?
> 
> Thank you.
> 
> --~------------------------------------------------------------------
> 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
> 


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] how to exclude namespaces from copy-of - 11/5/2009 3:13:00 PM</h1>
<pre>Hello!

I am trying to parse the atom feed using the xsl template.

The item in the feed contains this element: (example)
<div xmlns="http://www.w3.org/1999/xhtml" 
xmlns:dc="http://purl.org/dc/elements/1.1/" 
xmlns:thr="http://purl.org/syndication/thread/1.0">
<p>
October and November are busy months for Amazon Web Services!</p>
</div>

I want to copy the div with all its child elements, so I use copy-of
The problem is that I don't want the xmlns="http://www.w3.org/1999/xhtml"
or xmlns:dc or any other extra data in the div attribute

I just want the result to be
<div>
<p>
October and November are busy months for Amazon Web Services!</p>
</div>

How can I do this?

Thank you.

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] decimal vs double value spaces - 11/5/2009 11:49:00 AM</h1>
<pre>The value space of xs:double is fully defined in the spec, based on IEEE
specifications.

The value space of xs:decimal isn't fully defined, in that limits on the
number of digits are implementation-defined. However, every value in the
xs:decimal value space is a multiples of 10^-n where n is
implementation-defined, and so long as you're within the expected number of
digits, decimal arithmetic should be exact, whereas double arithmetic in
general will involve rounding on input and output (that is, conversion from
string->double and from double->string).

> but note that some (possibly 
> unfinished/ possibly naive) Java XPath engines internally 
> represent xs:decimal and xs:double as Java doubles 

Representing xs:decimal using Java doubles will give completely
non-conformant results which I don't think can be justified by any appeal to
the implementation-defined limits on precision.

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] decimal vs double value spaces - 11/5/2009 11:29:00 AM</h1>
<pre>Would someone kindly enlighten me as to the difference in
the value spaces of xs:decimal's and xs:double's.

I understand that the former doesn't lexically accept exponent
notation (E+02 e.g.) but note that some (possibly unfinished/
possibly naive) Java XPath engines internally represent xs:decimal and
xs:double as Java doubles thereby reducing the (internal) distinction
to nought.

Thanks for all help,

Justin


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/5/2009 9:35:00 AM</h1>
<pre>I think I got MK's idea wrong in the stylesheet I presented in my last
mail, but it is now corrected at the end of this mail, and it works as
I said.

To wrap it all up, I have made two datasets, one with only two
distinct values of 3000 and the other with 2992 distinct values of
3000. These two datasets are only about duplicate values. The test is
only an indication of how xsl:key can be useful with this type of
dataset.

Since optimization in Saxon EE isn't useful for duplicates, I have
only made this test with Saxon HE (Home Edition), formerly known as
Saxon B for "basics".

far-from-distinct-values.xml
2 distinct out of 3000
1) no key: 13.1s
2) using key: 0.1
3) also key in match: 5.4s

almost-distinct-values.xml
2992 distinct out of 3000
4) no key: 3.6s
5) using key: 3.6
6) also key in match: 0.1s

MK has explained why 2 works better than 3 and why 6 works better than 5.

The above is of cause only one type of dataset, but it shows to me
that xsl:key can make a big difference and that fine tuning a
template's match attribute can make a big difference.

But it must all be done carefully, and it is necessary to analyze the
dataset to find the best approach, and to test different approaches in
order to find the best one (fast).

Here is the corrected example of using xsl:key in the match attribute:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
    <xsl:key name="item-content" match="item" use="."/>

    <xsl:template match="item[. is key('item-content', current())[1]]">
        <xsl:copy>
            <xsl:apply-templates select="@*|node()"/>
        </xsl:copy>
    </xsl:template>

    <xsl:template match="item">
        <xsl:copy>
            <!-- add attribute and skip content -->
            <xsl:attribute name="refid" select="key('item-content', .)[1]/@id"/>
            <xsl:apply-templates select="@*"/>
        </xsl:copy>
    </xsl:template>

    <xsl:template match="@*|node()">
        <xsl:copy>
            <xsl:apply-templates select="@*|node()"/>
        </xsl:copy>
    </xsl:template>

</xsl:stylesheet>

cheers,
Jesper

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] Benefits of using xsl:key - 11/4/2009 9:19:00 PM</h1>
<pre>> 
> That the optimization option in Saxon EE often makes it not 
> necessary to use xsl:key 

Correct.

> but that in many situations you can 
> obtain even greater performance by fine tuning the match 
> attribute by hand using xsl:key?

I'd say "some situations". Particularly those situations where keys are
being used for Muenchian grouping, duplicates elimination etc. Even better
is to rewrite such applications to use xsl:for-each-group or
distinct-values().

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/4/2009 8:20:00 PM</h1>
<pre>Have I understood the last example right:

That the optimization option in Saxon EE often makes it not necessary
to use xsl:key but that in many situations you can obtain even greater
performance by fine tuning the match attribute by hand using xsl:key?

Cheers,
Jesper

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/4/2009 7:55:00 PM</h1>
<pre>MK  wrote:
> I would suggest one template match="x[.
> is key('k', current())[1]]" to match the first duplicate, and another
> match="x" with lower priority to match the remaining duplicates.

It works!

I changed XSLT stylesheet using xsl:key to this:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
    <xsl:key name="value-content" match="value" use="."/>

    <xsl:template match="value[. is key('value-content', current())[1]]">
        <xsl:copy>
            <!-- add attribute and skip content -->
            <xsl:attribute name="refid" select="key('value-content',
.)[1]/@id"/>
            <xsl:apply-templates select="@*"/>
        </xsl:copy>
    </xsl:template>

    <xsl:template match="@*|node()">
        <xsl:copy>
            <xsl:apply-templates select="@*|node()"/>
        </xsl:copy>
    </xsl:template>

</xsl:stylesheet>

Transformation using xsl:key is now back at 0.1s!!!

Cheers,
Jesper

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] Benefits of using xsl:key - 11/4/2009 7:36:00 PM</h1>
<pre>> 
> I have now made a new input file. I transformed the original 
> input fil to a new input file making all the id attribute 
> values unique, and also all the content unique. I then hand 
> edited the new file for 15 of the elements, making the 
> content the same for some other element.
> 
> The transformation with Saxon HE, PE and EE  without using 
> xsl:key is now much faster, 4.5s, but, as a big surprise (to 
> me), the use of xsl:key has no influence on the 
> transformation speed still being 4.5s, and also the 
> optimization option in EE has no effect!

I thought I explained why that should be expected. Your match pattern
match="x[.=preceding::x]" is intrinsically very inefficient, but by chance
it was performing OK because the distance between duplicates was always
small. You have now increased the distance between duplicates, so the match
pattern becomes more expensive, and gives quadratic performance with
document size. 
> 
> I'm a little confused. My conclusion is that xsl:key can make 
> a transformation faster in some situations. It very much 
> depends on data.
> 

Using keys will only speed things up if you use them in a place where the
performance is critical. You now have very few duplicates, so you are not
executing the body of the template very often, so speeding it up gives very
little benefit. Instead you need to speed up the match pattern, which you
can do by rewriting it to use key(): I would suggest one template match="x[.
is key('k', current())[1]]" to match the first duplicate, and another
match="x" with lower priority to match the remaining duplicates.

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/4/2009 7:23:00 PM</h1>
<pre>I have made a more realistic input file, but it leads to new results
reminding me of my first statement: It is difficult to create a test
example showing that xsl:key can speed up the transformation.

In the original example, three elements were copied and pasted over
and over again to create a file of 3000 lines. This gave an input file
with only two elements having different content. The speed difference
in usig xsl:key or not was close to 1:100. (10s/0.1s).

I have now made a new input file. I transformed the original input fil
to a new input file making all the id attribute values unique, and
also all the content unique. I then hand edited the new file for 15 of
the elements, making the content the same for some other element.

The transformation with Saxon HE, PE and EE  without using xsl:key is
now much faster, 4.5s, but, as a big surprise (to me), the use of
xsl:key has no influence on the transformation speed still being 4.5s,
and also the optimization option in EE has no effect!

I'm a little confused. My conclusion is that xsl:key can make a
transformation faster in some situations. It very much depends on
data.

Question: What is the rule of thumb for data sets where the use of
xsl:key is likely to make a big difference?

Cheers,
Jesper

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Condition problem - 11/4/2009 6:09:00 PM</h1>
<pre>On 4 Nov 2009, at 03:29 , Michael Kay wrote:
> ... First some comments:
>>
>> 	<xsl:when test="matches(.,'-') or matches(.,'-')">
>
> Why repeat the condition?

Actually, the two literals being tests are different characters
(here, and elsewhere in the code where there appear at first
glance to be duplicate tests):  hyphen and en-dash.

It looks to me as if in cutting down the problem you omitted
some crucial control structures; I guess your full code contains
one or more for-each constructs to iterate.

Without the code in front of us it's hard to be sure, but from
the sample output you give, my guess is that when generating
the refid attribute your full code first looks for ranges
and supplies the items in the range, and then handles all of
the cr children that are not either the start or the end of
a range.  And (again, judging from your sample input and
output), you want the items mentioned in the refid attribute
to be listed in the order in which they appear (explicitly or
implicitly) in the cr elements in the document.

My first advice would be: replace the contents of

   <xsl:attribute name="refid">
    ...
   </xsl:attribute>

with a call to apply-templates, using a new mode:

   <xsl:attribute name="refid">
     <xsl:apply-templates mode="supply-refid-target-values"  
select="cr"/>
   </xsl:attribute>

Then write three templates to handle the three kinds of cr
elements you have:

   (1) a cr element followed by a hyphen or an en-dash; it
       begins a range, so find the end of the range and emit
       the appropriate bibNN tokens, separated by blanks
   (2) a cr element preceded by a hyphen or an en-dash;
       it ends a range, so it has been handled by the
       first template, and should do nothing
   (3) any other cr element (followed by comma or nothing);
       it isn't a range, so just emit its bibNN token and
       a trailing blank

I hope this helps.

Michael Sperberg-McQueen


-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com
* http://cmsmcq.com/mib
* http://balisage.net
****************************************************************





--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] good Open source IDE Tool for XSL - 11/4/2009 5:36:00 PM</h1>
<pre>On 3 Nov 2009, at 05:20 , Syd Bauman wrote:

>> I am Looking for good Open source IDE Tool for XSL Development.
>> Please suggest me some good tool.
>
> ...
> C. Michael Sperberg-McQueen of Black Mesa technologies gave a talk on
> open source tools for XML development in late summer or early  
> fall. ...


The slides for that talk, given at the XML Summer School in Oxford
organized by Eleven Informatics, are on the Web at

   http://www.blackmesatech.com/2009/09/flossxml

The boundary between XML editors with some useful additional
tools and XML / XSLT IDEs appears fuzzy to me (like a lot of
other category boundaries in this area), so the categorization
of products into groups should not be taken too seriously.

The discussion thread here has mentioned several additional
products not included in my lists; I'll have to add some new
entries ...	

-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com
* http://cmsmcq.com/mib
* http://balisage.net
****************************************************************





--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] good Open source IDE Tool for XSL - 11/4/2009 5:23:00 PM</h1>
<pre>Syd,

Back in the day, Tony Graham had an Emacs mode for XSLT 1.0, xslide. 
Your search engine will show you more. Tony, are you on this channel?

(Not that I want to lure you away from oXygen, which is worth every 
penny and then some in my experience.)

Cheers,
Wendell

At 11:42 AM 11/4/2009, you wrote:
>It would take a lot to make me switch from oXygen. (It took a lot,
>including the steep academic discount, to get me to use it in the
>first place -- I generally prefer open source applications.) But if
>anyone is interested in writing a powerful Emacs mode for XSLT, I'd
>be interested in joining forces. (Like I have time for that?) The
>most important feature to me is completion, and oXygen does a really
>good job of it (completion w/o requiring use of the mouse for element
>names, attribute names, attribute values, variable names, template
>names, xml:id= values, XPath components, and maybe more). But the
>good news is that's probably not too hard to duplicate in Emacs.



======================================================================
Wendell Piez                            mailto:wapiez@mulberrytech.com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] good Open source IDE Tool for XSL - 11/4/2009 4:50:00 PM</h1>
<pre>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Syd Bauman wrote:

> BMi> The Eclipse XSL Developer Tools, part of the WST, aren't bad either -  
> BMi> particularly if you are using Eclipse for any other work.
> 
> Don't know anything about them. But I'm not likely to even try
> anything that lists support for schema languages but not RELAX NG.

My student Martin Schmied developed RELAX NG support for Eclipse
recently. But it will take some time to undergo Eclipse process before
being added into Web Tools Project plugin.

http://wiki.eclipse.org/WTP/RelaxNG/Proposal

> also huge plusses. But it's the completion I couldn't live without.
> :-)

Yep, it is hard to beat oXygen in completion.

- --
- ------------------------------------------------------------------
  Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
- ------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
- ------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
- ------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrxsKUACgkQzwmSw7n0dR6CjQCguwCcVjL/glxy7WhNWsSnzDBi
AOIAn3VtindgeLg4Wvx7gNsSIMUtewej
=GD4A
-----END PGP SIGNATURE-----

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] good Open source IDE Tool for XSL - 11/4/2009 4:43:00 PM</h1>
<pre>I'm glad this question was asked. Although it's off the beaten path
of "how do I accomplish such-and-such", I've learned a bit I didn't
know in an area that's interesting (to me, at least :-)


BMi> The Eclipse XSL Developer Tools, part of the WST, aren't bad either -  
BMi> particularly if you are using Eclipse for any other work.

Don't know anything about them. But I'm not likely to even try
anything that lists support for schema languages but not RELAX NG.


VCh> How could people forget to mention Marrowsoft Xselerator?

As this is a Windows-only product, I have never seen it, and probably
will never use it no matter how good it is. But you never know ...


BMa> I personally use kate and I'm very happy with it ;-)

I had never heard of kate, as I mostly use GNU/Linux without a
windowing system. But at quick glance it looks like it may be a very
reasonable solution for an XML aware editing environment. It may not
be powerful enough to satisfy Anil Kumar Veeramalli's use case, but
looks like it is certainly worth a try.


It would take a lot to make me switch from oXygen. (It took a lot,
including the steep academic discount, to get me to use it in the
first place -- I generally prefer open source applications.) But if
anyone is interested in writing a powerful Emacs mode for XSLT, I'd
be interested in joining forces. (Like I have time for that?) The
most important feature to me is completion, and oXygen does a really
good job of it (completion w/o requiring use of the mouse for element
names, attribute names, attribute values, variable names, template
names, xml:id= values, XPath components, and maybe more). But the
good news is that's probably not too hard to duplicate in Emacs.

Yes, a good XSLT IDE should also let you run the XSLT with one or two
keystrokes, and let you see the output of the run in the app of your
choice; and having built-in XSLT documentation and XSLT debugger are
also huge plusses. But it's the completion I couldn't live without.
:-)

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] How to concatenate/merge two independent XSLT stylesheets - 11/4/2009 1:52:00 PM</h1>
<pre>There are much more efficient ways of creating a pipeline than using "|" on
the command line, but presumably they are ruled out too.

There's no foolproof way of doing this without manually checking for
conflicting names of templates, global variables, keys etc. If you've been
very disciplined then these will all be in namespaces, and it will all be
much easier, but unless you are a very faithful disciple of Ken Holman then
this is unlikely to be the case.

You should change one of the stylesheets (or preferably both) to use named
modes on all template rules and calls of apply-templates.

Then finally you can stitch them together with

<xsl:template match="/">
  <xsl:variable name="temp">
    <xsl:apply-templates select="." mode="phase1"/>
  </xsl:variable>
  <xsl:apply-templates select="$temp" mode="phase2"/>
</xsl:template>

Alternatively, if you don't mind a product-specific solution, use
saxon:next-in-chain on the xsl:output element.

Regards,

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

> 
> I have two independent XSLT style sheets which work fine when 
> they are executed in two steps:
> 
> mydoc1.xml-->mysheet1.xsl-->mydoc2.xml-->mysheet2.xsl-->mydoc3.xml
> 
> However I would like to avoid the intermediate step (and the 
> creation of mydoc2.xml).
> Is there a way to concatenate the two XSLT stylesheets resp. 
> use the output of the first stylesheet templates as input of 
> second stylesheet templates?
> 
> Due to other requirements a piping with the well known pipe 
> symbol (|) on the console is NOT allowed. The two stylesheets 
> MUST be merged together somehow into ONE physical stylesheet file.
> 
> How can I do this?
> 
> Ben
> 
> 
> 
> 
> 
> 
> --~------------------------------------------------------------------
> 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
> 


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] How to concatenate/merge two independent XSLT stylesheets - 11/4/2009 1:27:00 PM</h1>
<pre>Ben Stover wrote:
> I have two independent XSLT style sheets which work fine when they are executed 
> in two steps:
> 
> mydoc1.xml-->mysheet1.xsl-->mydoc2.xml-->mysheet2.xsl-->mydoc3.xml
> 
> However I would like to avoid the intermediate step (and the creation of mydoc2.xml).
> Is there a way to concatenate the two XSLT stylesheets resp. use the output of
> the first stylesheet templates as input of second stylesheet templates?

Saxon has an extension attribute for xsl:output:
http://www.saxonica.com/documentation/extensions/output-extras/next-in-chain.html
so you could use

   <xsl:stylesheet
     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
     xmlns:saxon="http://saxon.sf.net/"
     exclude-result-prefixes="saxon"
     version="2.0">

     <xsl:import href="mysheet1.xsl"/>

     <xsl:output
       saxon:next-in-chain="mysheet2.xsl"/>


   </xsl:stylesheet>

-- 

	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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] How to concatenate/merge two independent XSLT stylesheets - 11/4/2009 1:22:00 PM</h1>
<pre>2009/11/4 Ben Stover <bxstover@yahoo.co.uk>:
> I have two independent XSLT style sheets which work fine when they are executed
> in two steps:
>
> mydoc1.xml-->mysheet1.xsl-->mydoc2.xml-->mysheet2.xsl-->mydoc3.xml
>
> However I would like to avoid the intermediate step (and the creation of mydoc2.xml).
> Is there a way to concatenate the two XSLT stylesheets resp. use the output of
> the first stylesheet templates as input of second stylesheet templates?
>
> Due to other requirements a piping with the well known pipe symbol (|) on the console
> is NOT allowed. The two stylesheets MUST be merged together somehow into ONE physical
> stylesheet file.
>
> How can I do this?

In the simplest scenario its just case of creating a "mysheet3.xsl"
that imports the other 2 :

<xsl:import href="mysheet1.xsl"/>
<xsl:import href="mysheet2.xsl"/>

<xsl:variable name="pass1">
  <xsl:for-each select="doc('mydoc1.xml')">
    <xsl:apply-templates/>
  </xsl:for-each>
<xsl:variable>

<xsl:template match="/">
  <xsl:apply-templates select="$pass1/*"/>
</xsl:template>

However this will only go smoothly if the elements in mydoc1.xml and
the intermediate "mydoc2" are different... if some are the same to
avoid the first pass templates confictling with the second pass (and
vice versa) then you'll need to use modes.


-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] How to concatenate/merge two independent XSLT stylesheets - 11/4/2009 1:19:00 PM</h1>
<pre>At 2009-11-04 14:12 +0100, Ben Stover wrote:
>I have two independent XSLT style sheets which work fine when they 
>are executed
>in two steps:
>
>mydoc1.xml-->mysheet1.xsl-->mydoc2.xml-->mysheet2.xsl-->mydoc3.xml
>
>However I would like to avoid the intermediate step (and the 
>creation of mydoc2.xml).
>Is there a way to concatenate the two XSLT stylesheets resp. use the output of
>the first stylesheet templates as input of second stylesheet templates?
>
>Due to other requirements a piping with the well known pipe symbol 
>(|) on the console
>is NOT allowed. The two stylesheets MUST be merged together somehow 
>into ONE physical
>stylesheet file.
>
>How can I do this?

You can use modes and, in XSLT 2.0, temporary trees, though it will 
require you to modify the stylesheets and not use them untouched as 
they exist now.  You don't have to use named modes for both steps ... 
you can use the default unnamed mode for one of the two steps.

The pattern would be along the lines of:

   <xsl:variable name="intermediate">
     <xsl:apply-templates mode="step1"/>
   </xsl:variable>
   <xsl:apply-templates select="$intermediate"/>

or ....

   <xsl:variable name="intermediate">
     <xsl:apply-templates/>
   </xsl:variable>
   <xsl:apply-templates select="$intermediate" mode="step2"/>

... where each stylesheet's template matches are all in the same mode.

Namespace-qualifying your top-level constructs may help too, to avoid 
overriding declarations.

If you have to do this with XSLT 1 then you'll need to use a 
vendor-supported extension to act on the node set of the result tree fragment.

I hope this helps.

. . . . . . . . . . . . . Ken

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] How to concatenate/merge two independent XSLT stylesheets into - 11/4/2009 1:13:00 PM</h1>
<pre>I have two independent XSLT style sheets which work fine when they are executed 
in two steps:

mydoc1.xml-->mysheet1.xsl-->mydoc2.xml-->mysheet2.xsl-->mydoc3.xml

However I would like to avoid the intermediate step (and the creation of mydoc2.xml).
Is there a way to concatenate the two XSLT stylesheets resp. use the output of
the first stylesheet templates as input of second stylesheet templates?

Due to other requirements a piping with the well known pipe symbol (|) on the console
is NOT allowed. The two stylesheets MUST be merged together somehow into ONE physical
stylesheet file.

How can I do this?

Ben






--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] SOAP extension compatible with AltovaXML - 11/4/2009 11:06:00 AM</h1>
<pre>Fabre Lambeau wrote:

  Hi,

> Has anyone come across (or implemented) a SOAP or http-send
> extension for XSLT 2.0 that would work with the AltovaXML
> processor?

  None that I am aware of.  My first advice would be to see if
you can switch to Saxon 9.

  If you cannot, the implementation (in Java) of the EXPath HTTP
Client is (I think) quite properly decoupled between what's Saxon
specific and the rest (if I remember well, the Apache HTTP Client
stuff is not that well entirely isolated in its own layer.)

  For what I've seen on the AltovaXML doc, it supports calling
Java methods, so if you're really interrested, you should be able
to replace the Saxon layer of EXPath HTTP Client (mostly dealing
with parsing the http:request element and serializing the
http:response element.)  They do not say how they pass XDM nodes
to Java though (they only document how atomic types are mapped to
Java types.)

  If you're interested, please join the EXPath mailing list
<http://www.expath.org/lists.html> to ask for more information.

  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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] Condition problem - 11/4/2009 10:30:00 AM</h1>
<pre>> I am having the following input:

Let's concentrate on the 4th line of input. (It would have made life easier
if you had cut the problem down further)
> 
Input
> 
> <cross-ref>[<cr refid="MEP_L_bib17">17</cr>-<cr
refid="MEP_L_bib29">29</cr>,
   <cr refid="MEP_L_bib43">43</cr>,<cr
refid="MEP_L_bib44">44</cr>]</cross-ref>
> 
> Actual output:
> 
> <ce:cross-refs refid="bib43 bib44 bib27 bib28
bib29">[27–29,43,44]</ce:cross-refs>
> 
> Required output:
> 
> <ce:cross-refs refid="bib27 bib28 bib29 bib43
bib44">[27–29,43,44]</ce:cross-refs>
> 
> 
> This the code I have tried.

As Andrew points out, this clearly isn't your code - you've introduced bugs
when cutting it down, and it's difficult to disentangle those bugs from your
original bugs. I'm afraid I really can't see how you expect to get the "27
28 29" sequence from your "17-29" input, or how you actually got it but in
the wrong place. Perhaps your input was actually "27" rather than "17" (Oh
this is fun, thank you for giving us so much pleasure by adding such twists
to the problem.) First some comments:
> 
> 	<xsl:when test="matches(.,'-') or matches(.,'-')">

Why repeat the condition?
> 				<xsl:if 
> test="cr[following-sibling::node()[1]!='-'][preceding-sibling:
> :node()[1]!='-'][following-sibling::node()[1]!='-'][preceding-
> sibling::node()[1]!='-']">

Why repeat the conditions?
> 					<xsl:value-of
> select="cr[following-sibling::node()[1]!='-'][preceding-siblin
> g::node()[1]!='-'][following-sibling::node()[1]!='-'][precedin
> g-sibling::node()[1]!='-'][following::text()[contains(current(
> ),'-')]]/substring-after(@refid,'MEP_L_')"/>

(a) Why repeat the conditions?

(b) The use of following-text() rather than following-text()[1] looks
questionable

(c) The use of current() rather than "." looks questionable

I strongly suspect, though I haven't tested the hypothesis because it would
involve fixing your other bugs first, that when you write

<xsl:if test="cr/@refid[contains(., 'bib')] and
cr[following-sibling::node()[1]='-']">

or similar constructs in other places, you are assuming that the two
conditions must apply to the same cr child. That is, you should have written

test="cr[contains(@refid, 'bib') and following-sibling::node()[1]='-']">

Similarly, I suspect that when, having tested this condition, you write
something like

<xsl:variable name="starth"
select="cr[following-sibling::node()[1]='-']/substring-after(@refid,'MEP_L_b
ib')"/>

you might be imagining that this will inevitably select the same cr element
that satisfied the condition in the <xsl:if>

In fact, the more I look at your code, the more I find it incomprehensible
that anything like this ever worked. You don't seem to be handling the case
where there are multiple ranges in your input at all, and yet you claim to
be handling some such cases correctly.

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Condition problem - 11/4/2009 10:13:00 AM</h1>
<pre>2009/11/4 Michael Kay <mike@saxonica.com>:
>> >
>> > I am having the following input:
>> >
>> > <cross-ref>[<cr refid="MEP_L_bib32">32</cr>-<cr
>> > refid="MEP_L_bib35">35</cr>]</cross-ref>
>> >
>> > <cross-ref>[<cr refid="MEP_L_bib23">23</cr>-<cr
>>
>>
>> That's not well-formed...
>
> It's well-formed if you add a wrapper element. Strange, but well-formed.
>

I guess you are making a point about rootless trees and the possibly
odd requirement there must be single root element?  (as opposed to
pointing out the obvious to me)





-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] Condition problem - 11/4/2009 10:04:00 AM</h1>
<pre>> >
> > I am having the following input:
> >
> > <cross-ref>[<cr refid="MEP_L_bib32">32</cr>-<cr 
> > refid="MEP_L_bib35">35</cr>]</cross-ref>
> >
> > <cross-ref>[<cr refid="MEP_L_bib23">23</cr>-<cr
> 
> 
> That's not well-formed...

It's well-formed if you add a wrapper element. Strange, but well-formed.

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Condition problem - 11/4/2009 9:31:00 AM</h1>
<pre>2009/11/4 Ganesh Babu N <nbabuganesh@gmail.com>:
> Dear All,
>
> I am having the following input:
>
> <cross-ref>[<cr refid="MEP_L_bib32">32</cr>–<cr
> refid="MEP_L_bib35">35</cr>]</cross-ref>
>
> <cross-ref>[<cr refid="MEP_L_bib23">23</cr>–<cr


That's not well-formed...


> This the code I have tried.
>
> <xsl:template match="cross-ref">
>        <xsl:when test="matches(.,'-') or matches(.,'–')">


Where is xsl:choose?  Surely you get an exception with that...
<rant>You've been on this list for a long time now, you know how to
form a question so why repeatedly post rubbish?</rant>



-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] Condition problem - 11/4/2009 8:37:00 AM</h1>
<pre>Dear All,

I am having the following input:

<cross-ref>[<cr refid="MEP_L_bib32">32</cr>–<cr
refid="MEP_L_bib35">35</cr>]</cross-ref>

<cross-ref>[<cr refid="MEP_L_bib23">23</cr>–<cr
refid="MEP_L_bib25">25</cr>,<cr refid="MEP_L_bib32">32</cr>–<cr
refid="MEP_L_bib34">34</cr>,<cr refid="MEP_L_bib55">55</cr>–<cr
refid="MEP_L_bib57">57</cr>]</cross-ref>

<cross-ref>[<cr refid="MEP_L_bib23">23</cr>,<cr
refid="MEP_L_bib31">31</cr>,<cr refid="MEP_L_bib33">33</cr>,<cr
refid="MEP_L_bib36">36</cr>,<cr refid="MEP_L_bib45">45</cr>–<cr
refid="MEP_L_bib47">47</cr>]</cross-ref>

<cross-ref>[<cr refid="MEP_L_bib17">17</cr>–<cr
refid="MEP_L_bib29">29</cr>,<cr refid="MEP_L_bib43">43</cr>,<cr
refid="MEP_L_bib44">44</cr>]</cross-ref>

<cross-ref>[<cr refid="MEP_L_bib23">23</cr>,<cr
refid="MEP_L_bib24">24</cr>,<cr refid="MEP_L_bib29">29</cr>–<cr
refid="MEP_L_bib31">31</cr>,<cr refid="MEP_L_bib33">33</cr>,<cr
refid="MEP_L_bib46">46</cr>]</cross-ref>


This the code I have tried.

<xsl:template match="cross-ref">
	<xsl:when test="matches(.,'-') or matches(.,'–')">
		<ce:cross-refs>
			<xsl:attribute name="refid">
				<xsl:if test="cr/@refid[contains(., 'bib')] and
cr[following-sibling::node()[1]='-']">
					<xsl:variable name="starth"
select="cr[following-sibling::node()[1]='-']/substring-after(@refid,'MEP_L_bib')"/>
					<xsl:variable name="endh"
select="cr[preceding-sibling::node()[1]='-']/substring-after(@refid,'MEP_L_bib')"/>
					<xsl:for-each select="1 to count($starth)">
						<xsl:variable name="tv" select="."/>
						<xsl:if test="$tv != 1">
							<xsl:text> </xsl:text>
						</xsl:if>
						<xsl:value-of select="for $i in xs:integer($starth[$tv]) to
xs:integer($endh[$tv]) return concat('bib', $i)"/>
					</xsl:for-each>
				</xsl:if>
				<xsl:if test="cr[following-sibling::node()[1]!='–'][preceding-sibling::node()[1]!='–'][following-sibling::node()[1]!='-'][preceding-sibling::node()[1]!='-']">
					<xsl:value-of
select="cr[following-sibling::node()[1]!='–'][preceding-sibling::node()[1]!='–'][following-sibling::node()[1]!='-'][preceding-sibling::node()[1]!='-'][following::text()[contains(current(),'–')]]/substring-after(@refid,'MEP_L_')"/>
					<xsl:text> </xsl:text>
				</xsl:if>
		        	<xsl:if test="cr/@refid[contains(., 'bib')] and
cr[following-sibling::node()[1]='–']">
				<xsl:variable name="startn"
select="cr[following-sibling::node()[1]='–']/substring-after(@refid,'MEP_L_bib')"/>
				<xsl:variable name="endn"
select="cr[preceding-sibling::node()[1]='–']/substring-after(@refid,'MEP_L_bib')"/>
				<xsl:for-each select="1 to count($startn)">
					<xsl:variable name="tv" select="."/>
					<xsl:if test="$tv != 1">
						<xsl:text> </xsl:text>
					</xsl:if>
					<xsl:value-of select="for $i in xs:integer($startn[$tv]) to
xs:integer($endn[$tv]) return concat('bib', $i)"/>
				</xsl:for-each>
			</xsl:if>
		</xsl:attribute>
		<xsl:apply-templates/>
	</ce:cross-refs>
</xsl:template>

With the above code i am getting the following output:

<ce:cross-refs refid="bib32 bib33 bib34 bib35">[32–35]</ce:cross-refs>
<ce:cross-refs refid="bib23 bib24 bib25 bib32 bib33 bib34 bib55 bib56
bib57">[23–25,32–34,55–57]</ce:cross-refs>
<ce:cross-refs refid="bib23 bib31 bib33 bib36 bib45 bib46
bib47">[23,31,33,36,45–47]</ce:cross-refs>
<ce:cross-refs refid="bib43 bib44 bib27 bib28
bib29">[27–29,43,44]</ce:cross-refs>
<ce:cross-refs refid="bib23 bib24 bib33 bib46 bib29 bib30
bib31">[23,24,29–31,33,46]</ce:cross-refs>

Required output is as follows:

<ce:cross-refs refid="bib32 bib33 bib34 bib35">[32–35]</ce:cross-refs>
<ce:cross-refs refid="bib23 bib24 bib25 bib32 bib33 bib34 bib55 bib56
bib57">[23–25,32–34,55–57]</ce:cross-refs>
<ce:cross-refs refid="bib23 bib31 bib33 bib36 bib45 bib46
bib47">[23,31,33,36,45–47]</ce:cross-refs>
<ce:cross-refs refid="bib27 bib28 bib29 bib43
bib44">[27–29,43,44]</ce:cross-refs>
<ce:cross-refs refid="bib23 bib24 bib29 bib30 bib31 bib33 bib46
">[23,24,29–31,33,46]</ce:cross-refs>

Refer the last 3 lines of all the XML content.

In line 3: non-range numbers are present on left side of range pair
In line 4: non-range numbers are present on right side of range pair
In line 5: non-range numbers are present on either side of range pair

When there are non-range numbers all the non-ranges numbers are pulled
to the beginning by the current XSL code. We cannot use tokenize
because the numbers are not consistent. you may get year number in
place of number. only ID value is consistent.

I am unable to maintain the order which the present in the input XML.
Please suggest how to achieve this.

Regards,
Ganesh

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/4/2009 8:22:00 AM</h1>
<pre>Michael Kay wrote:
> The exact way in which you created this file is probably very important. If
> you did it by naive copy-and-paste, then it's likely that the duplicate
> values in the file are very close to each other and that the distance
> between duplicates is consistently small.

I just pasted the three lines four times, then those lines 10 times,
then those lines 10 times, etc. The data set is admittedly only good
enough to demonstrate in a classroom that xsl:key can be useful, but
it is not fair to use this "dummy" data set to test optimization of an
XSLT processor.

Cheers,
Jesper Tverskov

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] Benefits of using xsl:key - 11/3/2009 10:28:00 PM</h1>
<pre>> By modifying the simple example by Michael Müller-Hillebrand:
> 
> Input.xml
> 
> <Doc>
>     <value oid="f37">some text</value>
>     <value oid="f61">some text</value>
>     <value oid="f042">some other text</value> </Doc>
> 
> Copy and pasting so we have 3000 lines.

The exact way in which you created this file is probably very important. If
you did it by naive copy-and-paste, then it's likely that the duplicate
values in the file are very close to each other and that the distance
between duplicates is consistently small.

This means that the pattern match="value[.=preceding::value]" is not nearly
as expensive to evaluate as one might expect: it doesn't involve a search
back to the beginning of the file, only to the nearest duplicate value. I
was initially surprised that introducing keys to this example made so much
difference, given that you left this match pattern unchanged; but the
explanation for this would lie in the predictable data distribution.

By contrast, this code

>             <xsl:attribute name="xrefid"
> select="preceding::value[.=current()][last()]/@oid"/>

is looking for the first (i.e. most distant) duplicate, which will in
general be a long search.

I suspect that with most real-life data, evaluating the pattern would be
much more expensive than it is with this synthetic data, and therefore
introducing the key would have less impact.

>I have a feeling that optimization in EE is not for "preceding axis"
problems, but for "standard" transformations of huge input files?

Saxon-EE has many optimizations, but won't optimize this particular
construct. The reason is that the sequence to which the predicate is applied
(preceding::value) is only searched once; it's not worth building an index
to support a search that is only done once. 

I'm always on the look-out for new optimization opportunities (though they
have to occur in constructs that are frequent enough to justify the extra
complexity). I think it would be potentially possible to extend the indexing
optimization to this case by recognizing that one can rewrite
preceding::value[X=Y] as //value[X=Y][.<<current()], which would then be
rewritten to use an index. In fact, I suspect that rewriting preceding::X as
//X[.<<current()] might well be a worthwhile rewrite even without the
indexing, as it would take advantage of the automatic indexing of //X which
occurs even with Saxon-HE: though it needs care because the "natural" order
of the results is different.

It's worth noting that your rewrite of

select="preceding::value[.=current()][last()]/@oid"

by

select="key('value-content', .)[1]"

works only because you know (from the semantics of the match pattern for the
template) that the context item cannot be the first in its key-group.

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] generating unique ids - 11/3/2009 7:59:00 PM</h1>
<pre>Can u paste the XsLT stylesheet you have or atleast the code where you
think there is trouble?
You must understand why keys are used and how generate id is used.
they are meant to be for two different reasons
So send us a  bit of your code.
remember the XSLT Mailing List Guidelines: Try and give as much info
as possible to get as much help as possible.
Vasu

2009/11/3 a kusa <akusa8@gmail.com>:
> Hi
>
> I am using generate-id() function to generate unique ids through out
> my document. But I am having a problem here.
>
> My output looks like this:
> <root>
>
> <step1 id="idstep_2_566">
>
> .....
> <step1>
> <step1 id="idstep_2_566">
>
>
>
> </step1>
>
> </root>
>
> Now in  my xslt for template 'step1' I have a generate-id() function.
> But for some reason it generates the same id for 'step1' elements.
> How do I prevent it from generating the same id that was generated for
> the previous step1 node? Do I have to use <xsl:key>?
>
> Any tips or suggestions will be helpful.
>
> Thanks.
>
> --~------------------------------------------------------------------
> 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
>
>



-- 
Vasu Chakkera
Numerical Algorithms Group Ltd.
Oxford
www.vasucv.com

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] generating unique ids - 11/3/2009 6:47:00 PM</h1>
<pre>a kusa wrote:

> I am using generate-id() function to generate unique ids through out
> my document. But I am having a problem here.
> 
> My output looks like this:
> <root>
> 
> <step1 id="idstep_2_566">
> 
> .....
> <step1>
> <step1 id="idstep_2_566">
> 
> 
> 
> </step1>
> 
> </root>
> 
> Now in  my xslt for template 'step1' I have a generate-id() function.
> But for some reason it generates the same id for 'step1' elements.
> How do I prevent it from generating the same id that was generated for
> the previous step1 node? Do I have to use <xsl:key>?

generate-id() will give a unique id for the context node. If that is the 
same both times your template is processed then you will get the same id.
So generate-id() is useful if you have e.g.

<list>
   <foo>...</foo>
   <foo>...</foo>
   <foo>...</foo>
</list>

in your input and then write a template for 'foo' elements in the stylesheet
   <xsl:template match="foo">
     <li id="{generate-id()}">
       <xsl:apply-templates/>
     </li>
   </xsl:template>


-- 

	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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] SOAP extension compatible with AltovaXML - 11/3/2009 6:43:00 PM</h1>
<pre>Hi,

Has anyone come across (or implemented) a SOAP or http-send extension
for XSLT 2.0 that would work with the AltovaXML processor?

-- 
Fabre Lambeau

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] generating unique ids - 11/3/2009 6:36:00 PM</h1>
<pre>Hi

I am using generate-id() function to generate unique ids through out
my document. But I am having a problem here.

My output looks like this:
<root>

<step1 id="idstep_2_566">

.....
<step1>
<step1 id="idstep_2_566">



</step1>

</root>

Now in  my xslt for template 'step1' I have a generate-id() function.
But for some reason it generates the same id for 'step1' elements.
How do I prevent it from generating the same id that was generated for
the previous step1 node? Do I have to use <xsl:key>?

Any tips or suggestions will be helpful.

Thanks.

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] batch processing using saxon 9 - 11/3/2009 6:31:00 PM</h1>
<pre>Hi

Thanks fot all your replies! I had somehow overlooked this option:-(

On Tue, Nov 3, 2009 at 8:29 AM, Martin Honnen <Martin.Honnen@gmx.de> wrote:
> a kusa wrote:
>
>> How do you batch process files in saxon 9 using the command line? I
>> have an input directory with xml files and I want to be able to batch
>> process them. I cannot find the option for saxon 9 command line.
>
> Provide an input directory with -s and an output directory with -o:
>
> java -jar SomePath/saxon9he.jar -s:inputDirectory -o:outputDirectory
> -xsl:sheet.xsl
>
> --
>
>        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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
>
>

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/3/2009 4:31:00 PM</h1>
<pre>I have tried to do the same test with the new SAXON HE, PE og EE from
inside Oxygen, and with AltovaXML from inside XMLSpy.

The preceding axis is really stressing the XSLT processor!

For Saxon inside Oxygen, it is interesting that with an xml input file
of only 3000 lines (2000 KB), the optimization option in EE is slower
that using xsl:key in HE, PE and EE, being really fast. I have a
feeling that optimization in EE is not for "preceding axis" problems,
but for "standard" transformations of huge input files?

When I tried to make a longer input file of only 10,000 lines,
transformation is still fast in Oxygen when using xsl:key with any of
the three versions, but without xsl:key transformation seems to be
"looping" for ever, and that is also the case when EE is tested in
optimized mode.

XMLSpy using AltovaXML freezes already when I attempted to transform
the file with only 3000 lines! So I didn't manage to test if xsl:key
could speed things up in XMLSpy.

Cheers,
Jesper

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] batch processing using saxon 9 - 11/3/2009 2:30:00 PM</h1>
<pre>a kusa wrote:

> How do you batch process files in saxon 9 using the command line? I
> have an input directory with xml files and I want to be able to batch
> process them. I cannot find the option for saxon 9 command line.

Provide an input directory with -s and an output directory with -o:

java -jar SomePath/saxon9he.jar -s:inputDirectory -o:outputDirectory 
-xsl:sheet.xsl

-- 

	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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] batch processing using saxon 9 - 11/3/2009 2:28:00 PM</h1>
<pre>> How do you batch process files in saxon 9 using the command line? I
> have an input directory with xml files and I want to be able to batch
> process them. I cannot find the option for saxon 9 command line.


http://www.saxonica.com/documentation/using-xsl/commandline.html


-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] batch processing using saxon 9 - 11/3/2009 2:24:00 PM</h1>
<pre>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Why not making a batch script invoking saxon yourself?
Regards,
Bruno
a kusa wrote:
> Hi
> 
> How do you batch process files in saxon 9 using the command line? I
> have an input directory with xml files and I want to be able to batch
> process them. I cannot find the option for saxon 9 command line.
> 
> Thanks in advance.
> 
> --~------------------------------------------------------------------
> 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
> 
> 

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

iEYEARECAAYFAkrwPT8ACgkQaOubDsBUvbvRFgCgqRG8bAh3yqgEWlV+1q1LLrX9
+gEAn3GO3aeOdgSmCyOsBwaW/e8b2Sac
=YGMt
-----END PGP SIGNATURE-----

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] batch processing using saxon 9 - 11/3/2009 2:23:00 PM</h1>
<pre>Hi

How do you batch process files in saxon 9 using the command line? I
have an input directory with xml files and I want to be able to batch
process them. I cannot find the option for saxon 9 command line.

Thanks in advance.

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] good Open source IDE Tool for XSL - 11/3/2009 2:23:00 PM</h1>
<pre>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I personally use kate and I'm very happy with it ;-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrwPPcACgkQaOubDsBUvbuvDQCfd3NY96O0epwmJ6C3HHUgBuft
FjUAoO6XcCrWT+64scK60Zb/JT4Ft+Qo
=BMFd
-----END PGP SIGNATURE-----

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] Stylesheet compilation with saxon - 11/3/2009 2:20:00 PM</h1>
<pre>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

What are the advantages of compiling a stylesheet with saxon?
I'm searching several ways to fast the xsl transformation process; is a
compiled stylesheet faster than a non-compiled one?
Best regards,
Bruno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrwPFUACgkQaOubDsBUvbv0XgCfVj07itb2v0/ok0japmmSfkPi
cjoAn128ZPkAWDLSq4ErxDrYchi/M97F
=TUYf
-----END PGP SIGNATURE-----

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] xsl:result-document usage - 11/3/2009 2:17:00 PM</h1>
<pre>Thank you!

On Tue, Nov 3, 2009 at 3:12 AM, Andrew Welch <andrew.j.welch@gmail.com> wrote:
> 2009/11/2 a kusa <akusa8@gmail.com>:
>> Hi
>>
>> I am not very clear with the xsl:result-document usage in xslt 2.0.
>> Basically, here is what I want to do.
>>
>> I have an xml file to which I apply my trasnformation style sheet. In
>> my transformation, I calculate what the document number for this input
>> file must be. Now when I run the transformation my  output file must
>> be {document number}.xml.
>>
>> Can I achieve this through xsl:result-document?
>
> yep:
>
> <xsl:template match="/">
>  <xsl:result-document href="{$filename}">
>  ....
>
>
> --
> Andrew Welch
> http://andrewjwelch.com
> Kernow: http://kernowforsaxon.sf.net/
>
> --~------------------------------------------------------------------
> 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
>
>

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] good Open source IDE Tool for XSL - 11/3/2009 2:13:00 PM</h1>
<pre>---------- Forwarded message ----------
From: Vasu Chakkera <vasucv@gmail.com>
Date: 2009/11/3
Subject: Re: [xsl] good Open source IDE Tool for XSL
To: xsl-list@lists.mulberrytech.com


How could people forget to mention Marrowsoft Xselerator?

Home page (SF): http://sourceforge.net/projects/xselerator

Help forum: http://sourceforge.net/forum/forum.php?forum_id=745152

Downloads: http://sourceforge.net/project/showfiles.php?group_id=207860

Enjoy!

Vasu


2009/11/3 Anil Kumar Veeramalli <anil.v@frescoinformatics.com>
>
> Hi,
>
> I am Looking for good  Open source IDE Tool for XSL Development. Please suggest me some good tool.
>
> Thanks,
> Anil
>
>
>
>
> --~------------------------------------------------------------------
> 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
>



--
Vasu Chakkera
Numerical Algorithms Group Ltd.
Oxford
www.vasucv.com




--
Vasu Chakkera
Numerical Algorithms Group Ltd.
Oxford
www.vasucv.com

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] good Open source IDE Tool for XSL - 11/3/2009 12:24:00 PM</h1>
<pre>On 3 Nov 2009, at 12:20, Syd Bauman wrote:

>> I am Looking for good Open source IDE Tool for XSL Development.
>> Please suggest me some good tool.
>
> AFAIK, Emacs is not exactly set up as an XSLT IDE yet, but many of us
> would appreciate it if someone would get on the ball and write one
> up.
>
> Last I saw JEdit was quite reasonable and usable. Netbeans and
> Treebeard supposedly have some built-in IDE-like features, but I've
> never even seen them, let alone used either. All of these should be
> available on Sourceforge.
>
> Although it has the tremendous moral disadvantage of being
> proprietary, I use SyncRO Soft's <oXygen> for 98% of my XSLT editing,
> anyway. (I use Emacs/psgml, Emacs/nxml, oXygen, and occasionally
> JEdit, BBEdit, or a specialized editor for other XML writing tasks;
> but for XSLT, it's almost always oXygen.)

The Eclipse XSL Developer Tools, part of the WST, aren't bad either -  
particularly if you are using Eclipse for any other work.

>
> C. Michael Sperberg-McQueen of Black Mesa technologies gave a talk on
> open source tools for XML development in late summer or early fall. I
> know he covered XML editing, but I don't know if he covered
> specialized XSLT IDEs. info@blackmesa.com.
>
> --~------------------------------------------------------------------
> 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
>

-- 
Bill Michell
billmichell@gmail.com





--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] good Open source IDE Tool for XSL - 11/3/2009 12:21:00 PM</h1>
<pre>> I am Looking for good Open source IDE Tool for XSL Development.
> Please suggest me some good tool.

AFAIK, Emacs is not exactly set up as an XSLT IDE yet, but many of us
would appreciate it if someone would get on the ball and write one
up.

Last I saw JEdit was quite reasonable and usable. Netbeans and
Treebeard supposedly have some built-in IDE-like features, but I've
never even seen them, let alone used either. All of these should be
available on Sourceforge.

Although it has the tremendous moral disadvantage of being
proprietary, I use SyncRO Soft's <oXygen> for 98% of my XSLT editing,
anyway. (I use Emacs/psgml, Emacs/nxml, oXygen, and occasionally
JEdit, BBEdit, or a specialized editor for other XML writing tasks;
but for XSLT, it's almost always oXygen.)

C. Michael Sperberg-McQueen of Black Mesa technologies gave a talk on
open source tools for XML development in late summer or early fall. I
know he covered XML editing, but I don't know if he covered
specialized XSLT IDEs. info@blackmesa.com.

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/3/2009 11:20:00 AM</h1>
<pre>The example works convincingly!

By modifying the simple example by Michael MÃ¼ller-Hillebrand:

Input.xml

<Doc>
    <value oid="f37">some text</value>
    <value oid="f61">some text</value>
    <value oid="f042">some other text</value>
</Doc>

Copy and pasting so we have 3000 lines.

And modifying his stylesheet to:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="2.0">
    <xsl:output indent="yes"/>

    <xsl:template match="value[.=preceding::value]">
        <xsl:copy>
            <!-- add attribute and skip content -->
            <xsl:apply-templates select="@*"/>
            <xsl:attribute name="xrefid"
select="preceding::value[.=current()][last()]/@oid"/>
        </xsl:copy>
    </xsl:template>

    <xsl:template match="@*|node()">
        <xsl:copy>
            <xsl:apply-templates select="@*|node()"/>
        </xsl:copy>
    </xsl:template>

</xsl:stylesheet>

Transformation with an old Saxon-B9 from inside Oxygen takes around 10s.

After using xsl:key and the following stylesheet:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0">
    <xsl:output indent="yes"/>
    <xsl:key name="value-content" match="value" use="."/>

    <xsl:template match="value[.=preceding::value]">
        <xsl:variable name="first" select="key('value-content', .)[1]"/>
        <xsl:copy>
            <xsl:choose>
                <xsl:when test=". is $first">
                    <!-- pass through content -->
                    <xsl:apply-templates select="@*"/>
                    <xsl:apply-templates/>
                </xsl:when>
                <xsl:otherwise>
                    <!-- add attribute and skip content -->
                    <xsl:attribute name="xrefid" select="$first/@oid"/>
                    <xsl:apply-templates select="@*"/>
                </xsl:otherwise>
            </xsl:choose>
        </xsl:copy>
    </xsl:template>

    <xsl:template match="@*|node()">
        <xsl:copy>
            <xsl:apply-templates select="@*|node()"/>
        </xsl:copy>
    </xsl:template>

</xsl:stylesheet>

Transformation takes 0.1s, or is 100 times faster!

It turned out to be easy to construct an example after all. Thanks for
the help. Next I will test the nice example provided by MK.

Cheers,
Jesper

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Break functionality  in XSL - 11/3/2009 10:12:00 AM</h1>
<pre>Thanks a lot Martin.
-Anil
Martin Honnen wrote:
>  
> You can define a key on the ROW elements:
>    <xsl:key name="k1" match="ROW" use="COLUMN[@NAME = 'JOBCODE']"/>
> then key('k1', 'P10') gives you a node-set of the ROW elements with 
> that key value, then you can sort that by the date in descending order 
> and only take the description of the first ROW:
>
> <xsl:stylesheet
>   xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>   xmlns:data="http://example.com/2009/data"
>   exclude-result-prefixes="data"
>   version="1.0">
>
>   <xsl:param name="jobcode" select="'P10'"/>
>
>   <xsl:key name="k1" match="ROW" use="COLUMN[@NAME = 'JOBCODE']"/>
>
>   <xsl:output method="text"/>
>
>   <data:data xmlns="">
>     <month key="Jan" value="01"/>
>     <month key="Feb" value="02"/>
>     <month key="Mar" value="03"/>
>     <month key="Apr" value="04"/>
>     <month key="May" value="05"/>
>     <month key="Jun" value="06"/>
>     <month key="Jul" value="07"/>
>     <month key="Aug" value="08"/>
>     <month key="Sep" value="09"/>
>     <month key="Oct" value="10"/>
>     <month key="Nov" value="11"/>
>     <month key="Dec" value="12"/>
>   </data:data>
>
>   <xsl:template match="/">
>     <xsl:for-each select="key('k1', $jobcode)">
>       <xsl:sort select="concat(
>         substring(COLUMN[@NAME = 'EFFDT'], 8, 4),
>         '-',
>         document('')/xsl:stylesheet/data:data/month[@key = 
> substring(COLUMN[@NAME = 'EFFDT'], 4, 3)]/@value,
>         '-',
>         substring(COLUMN[@NAME = 'EFFDT'], 1, 2))"
>         order="descending"/>
>       <xsl:if test="position() = 1">
>         <xsl:value-of select="COLUMN[@NAME = 'DESCR']"/>
>       </xsl:if>
>     </xsl:for-each>
>   </xsl:template>
>
> </xsl:stylesheet>
>
>
> The only problem is dealing with that date format, you can't sort on 
> that directly, you need to extract the components and bring them into 
> a yyyy-mm-dd format that can be sorted as a string. The stylesheet 
> above does that.
>
>
>



--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] Benefits of using xsl:key - 11/3/2009 9:31:00 AM</h1>
<pre>> 
> We often hear that the use of xsl:key can speed up a 
> transformation many times. But XSLT processors seem so 
> optimized for speed, anyway, these days, that I have found it 
> difficult to construct a test input file and a test XSLT 
> stylesheet demonstrating the dramatic wonders of using xsl:key.
> 
> How big should the input document be?
> How complicated the hierarchy, etc?
> 

Try this query, which is Q8 from the XQuery XMark benchmark translated into
XSLT.

<result xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xsl:version="2.0">
<!-- Q8.  List the names of persons and the number of items they bought.
          (joins person, closed_auction) -->

  <xsl:for-each select="/site/people/person">
    <xsl:variable name="a" 
       select="/site/closed_auctions/closed_auction[buyer/@person =
current()/@id]"/>
    <item person="{name}"><xsl:value-of select="count($a)"/></item>  
  </xsl:for-each>
  
</result>  

Run it against different sizes of database from the XMark benchmark. Observe
how with Saxon-HE the performance increases quadradically with database
size, while with Saxon-EE the increase is linear. That's because Saxon-EE
creates a key automatically. Then show how you can achieve the same effect
with Saxon-HE by hand-optimizing using xsl:key: introduce

<xsl:key name="k" match="/site/closed_auctions/closed_auction"
use="buyer/@person"/>

and change the variable initializer to

select="key('k', @id)"

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/3/2009 9:22:00 AM</h1>
<pre>Hi Jesper,

Am 03.11.2009 um 08:55 schrieb Jesper Tverskov:

> We often hear that the use of xsl:key can speed up a transformation
> many times. But XSLT processors seem so optimized for speed, anyway,
> these days, that I have found it difficult to construct a test input
> file and a test XSLT stylesheet demonstrating the dramatic wonders of
> using xsl:key.
>
> How big should the input document be?
> How complicated the hierarchy, etc?
>
> I would like to impress my students with a nice little transformation
> example, instead of just telling them that there can be huge benefits.

about a year ago I had such a situation. With test documents all went  
fine, but the customer used XML files of about 20 MBytes and they  
waited. They complained about it only after months and I was really  
ashamed.

The task was to remove duplicate content from an XML file, to ease the  
translation process. All duplicate elements should be left in the  
result file, but empty and with an extra attribute @xrefid which would  
allow to revert the process after translation.

The input was essentially a list, the original with a lot more  
attributes and of course thousands of entries:

<?xml version="1.0" encoding="UTF-8"?>
<Doc>
  <value oid="f37">some text</value>
  <value oid="f61">some text</value>
  <value oid="f042">some other text</value>
</Doc>

The desired result was:

<?xml version="1.0" encoding="UTF-8"?>
<Doc>
  <value oid="f37">some text</value>
  <value oid="f61" xrefid="f37" />
  <value oid="f042">some other text</value>
</Doc>

My first take was (I know I should have known better):

<xsl:template match="value[.=preceding::value]">
  <xsl:copy>
   <!-- add attribute and skip content -->
   <xsl:apply-templates select="@*"/>
   <xsl:attribute name="xrefid" select="preceding::value[.=current()] 
[last()]/@oid"/>
  </xsl:copy>
</xsl:template>

<xsl:template match="value">
  <xsl:copy>
   <xsl:apply-templates select="@*|node()"/>
  </xsl:copy>
</xsl:template>


This was really bad with large files, because for every value a look- 
up of all preceding values had to be made. So I changed it to

<xsl:key name="value-content" match="value" use="."/>

<xsl:template match="value">
  <xsl:variable name="first" select="key('value-content', .)[1]"/>
  <xsl:copy>
   <xsl:choose>
    <xsl:when test=". is $first">
     <!-- pass through content -->
     <xsl:apply-templates select="@*"/>
     <xsl:apply-templates/>
    </xsl:when>
    <xsl:otherwise>
      <!-- add attribute and skip content -->
      <xsl:attribute name="xrefid" select="$first/@oid"/>
      <xsl:apply-templates select="@*"/>
    </xsl:otherwise>
   </xsl:choose>
  </xsl:copy>
</xsl:template>

Now the solution worked like a breeze with really large files.

HTH,

- Michael

PS: Examples have been edited and not tested.

--
_______________________________________________________________
Michael Müller-Hillebrand: Dokumentations-Technologie
Adobe Certified Expert, FrameMaker
Lösungen und Training, FrameScript, XML/XSL, Unicode
Blog: http://cap-studio.de/ - Tel. +49 (9131) 28747






--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/3/2009 9:21:00 AM</h1>
<pre>2009/11/3 Jesper Tverskov <jesper.tverskov@gmail.com>:
> On Tue, Nov 3, 2009 at 9:03 AM, David Carlisle <davidc@nag.co.uk> wrote:
>>However a typical
>> muenchian grouping example can easily be orders of magnitude faster and
>> so measurable on really quite small documents as you are avoiding
>> an order  n^2 along the sibling axis looking for duplicates.
>
> What about XSLT 2.0 then, where we use xsl:for-each-group?
>
> A set of XSLT 2.0 test files demonstrating a dramatic difference would
> really be much appreciated?

Create a large index file along the lines of:

<entry id="nnn1" value="vvv1"/>
<entry id="nnn2" value="vvv2"/>

then in another stylesheet do multiple lookups into that file:

$entry-doc//entry[@id eq $id]/@value

then use a key instead:

<xsl:key name="entry-by-id" match="entry" use="@id"/>

with

key('entry-by-id', $id, $entry-doc)/@value

Provided the processor doesn't optimize // (such as the paid-for
version of Saxon) then you should see a measurable difference between
the former and the latter.


-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] xsl:result-document usage - 11/3/2009 9:13:00 AM</h1>
<pre>2009/11/2 a kusa <akusa8@gmail.com>:
> Hi
>
> I am not very clear with the xsl:result-document usage in xslt 2.0.
> Basically, here is what I want to do.
>
> I have an xml file to which I apply my trasnformation style sheet. In
> my transformation, I calculate what the document number for this input
> file must be. Now when I run the transformation my  output file must
> be {document number}.xml.
>
> Can I achieve this through xsl:result-document?

yep:

<xsl:template match="/">
  <xsl:result-document href="{$filename}">
  ....


-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/3/2009 9:01:00 AM</h1>
<pre>On Tue, Nov 3, 2009 at 9:03 AM, David Carlisle <davidc@nag.co.uk> wrote:
>However a typical
> muenchian grouping example can easily be orders of magnitude faster and
> so measurable on really quite small documents as you are avoiding
> an order Â n^2 along the sibling axis looking for duplicates.

What about XSLT 2.0 then, where we use xsl:for-each-group?

A set of XSLT 2.0 test files demonstrating a dramatic difference would
really be much appreciated?

Jesper

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Benefits of using xsl:key - 11/3/2009 8:04:00 AM</h1>
<pre>> How big should the input document be?
> How complicated the hierarchy, etc?

It depends on the processor. Saxon for example will recognise certain
xpath expressions and index them automatcally, and if it does that while
compiling the stylesheet then it makes no difference at all how big or
complicated the input is as the "hint" to the processor to index the
construct isn't needed so doesn't have much effect. However a typical
muenchian grouping example can easily be orders of magnitude faster and
so measurable on really quite small documents as you are avoiding 
an order  n^2 along the sibling axis looking for duplicates.

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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] Benefits of using xsl:key - 11/3/2009 7:56:00 AM</h1>
<pre>Hi list

We often hear that the use of xsl:key can speed up a transformation
many times. But XSLT processors seem so optimized for speed, anyway,
these days, that I have found it difficult to construct a test input
file and a test XSLT stylesheet demonstrating the dramatic wonders of
using xsl:key.

How big should the input document be?
How complicated the hierarchy, etc?

I would like to impress my students with a nice little transformation
example, instead of just telling them that there can be huge benefits.

Cheers,
Jesper Tverskov

http://www.xmlkurser.dk
http://www.xmlplease.com

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] good Open source IDE Tool for XSL - 11/3/2009 6:48:00 AM</h1>
<pre>Hi,

I am Looking for good  Open source IDE Tool for XSL Development. Please 
suggest me some good tool.

Thanks,
Anil




--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] xsl:result-document usage - 11/3/2009 3:48:00 AM</h1>
<pre>On Tue, Nov 3, 2009 at 3:29 AM, a kusa <akusa8@gmail.com> wrote:
> Now when I run the transformation my Â output file must
> be {document number}.xml.
>
> Can I achieve this through xsl:result-document?

I think so. If I remember correctly, you might have to specify value
of href attribute of xsl:result-document instruction as follows,
href="{$document-number}.xml".


-- 
Regards,
Mukul Gandhi

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] XSLT key() function document argument - 11/3/2009 1:54:00 AM</h1>
<pre>Excellent, that helps a lot. Thank you, sir.

G. Ken Holman wrote:
> At 2009-11-02 17:16 -0800, Bill French wrote:
>> I have a stylesheet that initializes some keys based on content in 
>> the input document. Then, the stylesheet applies templates to a node 
>> set variable whose contents come from an external file. For awhile I 
>> was very confused, because the keys weren't accessible from the 
>> templates that were being applied in the different context.
>>
>> <xsl:key name="c" match="rm:content" use="string(@name)"/>
>> <xsl:key name="l" match="rm:label" use="string(@name)"/>
>> <xsl:variable name="orig-context" select="/"/>
>>
>> ...
>>
>> <xsl:variable name="wf">
>>     <xsl:copy-of select="document($wf-filepath)"></xsl:copy-of>
>> </xsl:variable>
> 
> I find it interesting you are using <xsl:copy-of/> ... why not just 
> point to the document root node rather than occupying the memory by 
> creating an entire copy of the document:
> 
>    <xsl:variable name="wf" select="document($wf-filepath)"/>
> 
>> <xsl:template match="/rm:contentList">
>>     <xsl:apply-templates select="$wf"/>
>> </xsl:template>
>>
>> <xsl:template match="rm:insert[@label]">
>>     <xsl:apply-templates select="key('l', @label, $orig-context)"/>
>> </xsl:template>
>>
>> The variable $wf contains the rm:insert elements that are matched by 
>> the final template.
>>
>> Now the question is -- is there a way to reference the "original" 
>> context, i.e., the document that processor originally encounters as 
>> the input tree? I've stored the document in the variable 
>> $orig-context, but this doesn't seem like an efficient or 
>> particularly elegant solution.
> 
> That is exactly how I would do it, with a global:
> 
>    <xsl:variable name="orig-context" select="/"/>
> 
> ... and there is nothing inefficient at all about this since it is 
> only storing a single node ... just like in my suggested modification 
> for $wf above.
> 
>> Is there some special syntax to access the original context from a 
>> context created when applying templates to a node set variable?
> 
> Nothing special about applying templates to a node set variable ... 
> keeping the original context in a variable is entirely acceptable and 
> quite common.
> 
> And, with my modification for $wf above you don't have a node set 
> variable, you are just pushing another document through the template 
> rules without incurring the overhead of creating the complete copy in 
> a node set variable.
> 
> Remember that document() returns a document node (formerly called a 
> root node) after reading the XML document into memory ... so the 
> document is in memory somewhere, it just isn't *also* in a variable 
> through your use of <xsl:copy/>.
> 
> I've often used a global variable storing the root node for precisely 
> the purpose you've described.  Not at all inefficient, nor wasteful, 
> nor inelegant in my opinion.
> 
> I hope this helps.
> 
> . . . . . . . . . Ken
> 
> --
> Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
> Interested in other classes?  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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
> 
> 

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] XSLT key() function document argument - 11/3/2009 1:28:00 AM</h1>
<pre>At 2009-11-02 17:16 -0800, Bill French wrote:
>I have a stylesheet that initializes some keys based on content in 
>the input document. Then, the stylesheet applies templates to a node 
>set variable whose contents come from an external file. For awhile I 
>was very confused, because the keys weren't accessible from the 
>templates that were being applied in the different context.
>
><xsl:key name="c" match="rm:content" use="string(@name)"/>
><xsl:key name="l" match="rm:label" use="string(@name)"/>
><xsl:variable name="orig-context" select="/"/>
>
>...
>
><xsl:variable name="wf">
>     <xsl:copy-of select="document($wf-filepath)"></xsl:copy-of>
></xsl:variable>

I find it interesting you are using <xsl:copy-of/> ... why not just 
point to the document root node rather than occupying the memory by 
creating an entire copy of the document:

   <xsl:variable name="wf" select="document($wf-filepath)"/>

><xsl:template match="/rm:contentList">
>     <xsl:apply-templates select="$wf"/>
></xsl:template>
>
><xsl:template match="rm:insert[@label]">
>     <xsl:apply-templates select="key('l', @label, $orig-context)"/>
></xsl:template>
>
>The variable $wf contains the rm:insert elements that are matched by 
>the final template.
>
>Now the question is -- is there a way to reference the "original" 
>context, i.e., the document that processor originally encounters as 
>the input tree? I've stored the document in the variable 
>$orig-context, but this doesn't seem like an efficient or 
>particularly elegant solution.

That is exactly how I would do it, with a global:

   <xsl:variable name="orig-context" select="/"/>

... and there is nothing inefficient at all about this since it is 
only storing a single node ... just like in my suggested modification 
for $wf above.

>Is there some special syntax to access the original context from a 
>context created when applying templates to a node set variable?

Nothing special about applying templates to a node set variable ... 
keeping the original context in a variable is entirely acceptable and 
quite common.

And, with my modification for $wf above you don't have a node set 
variable, you are just pushing another document through the template 
rules without incurring the overhead of creating the complete copy in 
a node set variable.

Remember that document() returns a document node (formerly called a 
root node) after reading the XML document into memory ... so the 
document is in memory somewhere, it just isn't *also* in a variable 
through your use of <xsl:copy/>.

I've often used a global variable storing the root node for precisely 
the purpose you've described.  Not at all inefficient, nor wasteful, 
nor inelegant in my opinion.

I hope this helps.

. . . . . . . . . Ken

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] XSLT key() function document argument - 11/3/2009 1:17:00 AM</h1>
<pre>Hi all,

I have a stylesheet that initializes some keys based on content in the 
input document. Then, the stylesheet applies templates to a node set 
variable whose contents come from an external file. For awhile I was 
very confused, because the keys weren't accessible from the templates 
that were being applied in the different context.

<xsl:key name="c" match="rm:content" use="string(@name)"/>
<xsl:key name="l" match="rm:label" use="string(@name)"/>
<xsl:variable name="orig-context" select="/"/>

...

<xsl:variable name="wf">
     <xsl:copy-of select="document($wf-filepath)"></xsl:copy-of>
</xsl:variable>

<xsl:template match="/rm:contentList">
     <xsl:apply-templates select="$wf"/>
</xsl:template>

<xsl:template match="rm:insert[@label]">
     <xsl:apply-templates select="key('l', @label, $orig-context)"/>
</xsl:template>

The variable $wf contains the rm:insert elements that are matched by the 
final template.

Now the question is -- is there a way to reference the "original" 
context, i.e., the document that processor originally encounters as the 
input tree? I've stored the document in the variable $orig-context, but 
this doesn't seem like an efficient or particularly elegant solution. Is 
there some special syntax to access the original context from a context 
created when applying templates to a node set variable?

Many thanks,

--Bill

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] xsl:result-document usage - 11/2/2009 10:00:00 PM</h1>
<pre>Hi

I am not very clear with the xsl:result-document usage in xslt 2.0.
Basically, here is what I want to do.

I have an xml file to which I apply my trasnformation style sheet. In
my transformation, I calculate what the document number for this input
file must be. Now when I run the transformation my  output file must
be {document number}.xml.

Can I achieve this through xsl:result-document?
:

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Question about variable assignment based on run-time value - 11/2/2009 8:32:00 PM</h1>
<pre><xsl:variable name="label-nodes"
  select="rm:label[not(parent::shared) or $page-type = tokenize(@pages,
  '\s*,\s*')]"/>

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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] Question about variable assignment based on run-time value - 11/2/2009 8:30:00 PM</h1>
<pre>> I'm trying to capture a sequence of nodes in a variable. The 
> catch is that the nodes I capture can vary based on the 
> local-name() of the element matched by the template.
> 
> I've got:
> 
> <xsl:variable name="label-nodes">
>      <xsl:choose>
>          <xsl:when test="local-name() = 'shared'">
>              <xsl:value-of select="rm:label[$page-type = 
> tokenize(@pages, '\s*,\s*')]"/>
>          </xsl:when>
>          <xsl:otherwise>
>              <xsl:value-of select="rm:label"/>
>          </xsl:otherwise>
>      </xsl:choose>
> </xsl:variable>
> 
> Instead, I want the sequence of rm:label elements selected by 
> the XPath expression in the xsl:value-of instruction's select 
> attribute. But how do I select a sequence?

Well, the minimum change is:

> <xsl:variable name="label-nodes">
>      <xsl:choose>
>          <xsl:when test="local-name() = 'shared'">
>              <xsl:sequence select="rm:label[$page-type = tokenize(@pages,
'\s*,\s*')]"/>
>          </xsl:when>
>          <xsl:otherwise>
>              <xsl:sequence select="rm:label"/>
>          </xsl:otherwise>
>      </xsl:choose>
> </xsl:variable>

But I think I would write

<xsl:variable name="label-nodes"
  select="rm:label[local-name(current()) ne 'shared' or $page-type =
tokenize(@pages, '\s*,\s*')]"/>

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Question about variable assignment based on run-time value - 11/2/2009 8:11:00 PM</h1>
<pre>Apologies -- I should have specified that I'm using XSLT 2.0.

Bill French wrote:
> Hi all,
> 
> I'm trying to capture a sequence of nodes in a variable. The catch is 
> that the nodes I capture can vary based on the local-name() of the 
> element matched by the template.
> 
> I've got:
> 
> <xsl:variable name="label-nodes">
>      <xsl:choose>
>          <xsl:when test="local-name() = 'shared'">
>              <xsl:value-of select="rm:label[$page-type = 
> tokenize(@pages, '\s*,\s*')]"/>
>          </xsl:when>
>          <xsl:otherwise>
>              <xsl:value-of select="rm:label"/>
>          </xsl:otherwise>
>      </xsl:choose>
> </xsl:variable>
> 
> Instead, I want the sequence of rm:label elements selected by the XPath 
> expression in the xsl:value-of instruction's select attribute. But how 
> do I select a sequence?
> 
> Many thanks in advance,
> 
> --Bill
> 
> --~------------------------------------------------------------------
> 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
> --~--
> 
> 

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] Question about variable assignment based on run-time value - 11/2/2009 7:48:00 PM</h1>
<pre>Hi all,

I'm trying to capture a sequence of nodes in a variable. The catch is 
that the nodes I capture can vary based on the local-name() of the 
element matched by the template.

I've got:

<xsl:variable name="label-nodes">
     <xsl:choose>
         <xsl:when test="local-name() = 'shared'">
             <xsl:value-of select="rm:label[$page-type = 
tokenize(@pages, '\s*,\s*')]"/>
         </xsl:when>
         <xsl:otherwise>
             <xsl:value-of select="rm:label"/>
         </xsl:otherwise>
     </xsl:choose>
</xsl:variable>

Instead, I want the sequence of rm:label elements selected by the XPath 
expression in the xsl:value-of instruction's select attribute. But how 
do I select a sequence?

Many thanks in advance,

--Bill

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Break functionality  in XSL - 11/2/2009 5:02:00 PM</h1>
<pre>Anil Kumar Veeramalli wrote:

> this is my sample xml file.
> <TABLE NAME="PS_JOBCODE_TBL">
> <ROWS>
> <ROW>
> <COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
> <COLUMN NAME="JOBCODE"><![CDATA[P10]]></COLUMN>
> <COLUMN NAME="EFFDT"><![CDATA[01-Jan-1996 00:00:00]]></COLUMN>
> <COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
> <COLUMN NAME="DESCR"><![CDATA[yyyyyyyyyyyyyyy]]></COLUMN>
> </ROW>
> <ROW>
> <COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
> <COLUMN NAME="JOBCODE"><![CDATA[B64]]></COLUMN>
> <COLUMN NAME="EFFDT"><![CDATA[01-Jan-1900 00:00:00]]></COLUMN>
> <COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
> <COLUMN NAME="DESCR"><![CDATA[CONSTR SUPR]]></COLUMN>
> </ROW>
> <ROW>
> <COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
> <COLUMN NAME="JOBCODE"><![CDATA[B64]]></COLUMN>
> <COLUMN NAME="EFFDT"><![CDATA[01-Jun-1966 00:00:00]]></COLUMN>
> <COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
> <COLUMN NAME="DESCR"><![CDATA[CONSTR SUPR]]></COLUMN>
> </ROW>
> <ROW>
> <COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
> <COLUMN NAME="JOBCODE"><![CDATA[P10]]></COLUMN>
> <COLUMN NAME="EFFDT"><![CDATA[16-Jul-1991 00:00:00]]></COLUMN>
> <COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
> <COLUMN NAME="DESCR"><![CDATA[CABLE SPLICERS]]></COLUMN>
> </ROW>
> <ROW>
> <COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
> <COLUMN NAME="JOBCODE"><![CDATA[P10]]></COLUMN>
> <COLUMN NAME="EFFDT"><![CDATA[16-Jul-1994 00:00:00]]></COLUMN>
> <COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
> <COLUMN NAME="DESCR"><![CDATA[XXXXXXXXXXX]]></COLUMN>
> </ROW>
> </ROWS>
> </TABLE>
> 
> I need to find out the DESCR. based on JobCode
> 
> *Input :  *Jobcode like P10
> *Process: *find out the all the nodes with  Jobcode  *P10*  and find the 
> latest Effective date (EFFDT) and display corresponding DESCR
> *output: *DESCR with latest Effective date.

You can define a key on the ROW elements:
    <xsl:key name="k1" match="ROW" use="COLUMN[@NAME = 'JOBCODE']"/>
then key('k1', 'P10') gives you a node-set of the ROW elements with that 
key value, then you can sort that by the date in descending order and 
only take the description of the first ROW:

<xsl:stylesheet
   xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
   xmlns:data="http://example.com/2009/data"
   exclude-result-prefixes="data"
   version="1.0">

   <xsl:param name="jobcode" select="'P10'"/>

   <xsl:key name="k1" match="ROW" use="COLUMN[@NAME = 'JOBCODE']"/>

   <xsl:output method="text"/>

   <data:data xmlns="">
     <month key="Jan" value="01"/>
     <month key="Feb" value="02"/>
     <month key="Mar" value="03"/>
     <month key="Apr" value="04"/>
     <month key="May" value="05"/>
     <month key="Jun" value="06"/>
     <month key="Jul" value="07"/>
     <month key="Aug" value="08"/>
     <month key="Sep" value="09"/>
     <month key="Oct" value="10"/>
     <month key="Nov" value="11"/>
     <month key="Dec" value="12"/>
   </data:data>

   <xsl:template match="/">
     <xsl:for-each select="key('k1', $jobcode)">
       <xsl:sort select="concat(
         substring(COLUMN[@NAME = 'EFFDT'], 8, 4),
         '-',
         document('')/xsl:stylesheet/data:data/month[@key = 
substring(COLUMN[@NAME = 'EFFDT'], 4, 3)]/@value,
         '-',
         substring(COLUMN[@NAME = 'EFFDT'], 1, 2))"
         order="descending"/>
       <xsl:if test="position() = 1">
         <xsl:value-of select="COLUMN[@NAME = 'DESCR']"/>
       </xsl:if>
     </xsl:for-each>
   </xsl:template>

</xsl:stylesheet>


The only problem is dealing with that date format, you can't sort on 
that directly, you need to extract the components and bring them into a 
yyyy-mm-dd format that can be sorted as a string. The stylesheet above 
does that.



-- 

	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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] Break functionality  in XSL - 11/2/2009 4:39:00 PM</h1>
<pre>Hi martin,

this is my sample xml file.
<TABLE NAME="PS_JOBCODE_TBL">
<ROWS>
<ROW>
<COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
<COLUMN NAME="JOBCODE"><![CDATA[P10]]></COLUMN>
<COLUMN NAME="EFFDT"><![CDATA[01-Jan-1996 00:00:00]]></COLUMN>
<COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
<COLUMN NAME="DESCR"><![CDATA[yyyyyyyyyyyyyyy]]></COLUMN>
</ROW>
<ROW>
<COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
<COLUMN NAME="JOBCODE"><![CDATA[B64]]></COLUMN>
<COLUMN NAME="EFFDT"><![CDATA[01-Jan-1900 00:00:00]]></COLUMN>
<COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
<COLUMN NAME="DESCR"><![CDATA[CONSTR SUPR]]></COLUMN>
</ROW>
<ROW>
<COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
<COLUMN NAME="JOBCODE"><![CDATA[B64]]></COLUMN>
<COLUMN NAME="EFFDT"><![CDATA[01-Jun-1966 00:00:00]]></COLUMN>
<COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
<COLUMN NAME="DESCR"><![CDATA[CONSTR SUPR]]></COLUMN>
</ROW>
<ROW>
<COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
<COLUMN NAME="JOBCODE"><![CDATA[P10]]></COLUMN>
<COLUMN NAME="EFFDT"><![CDATA[16-Jul-1991 00:00:00]]></COLUMN>
<COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
<COLUMN NAME="DESCR"><![CDATA[CABLE SPLICERS]]></COLUMN>
</ROW>
<ROW>
<COLUMN NAME="SETID"><![CDATA[COMMN]]></COLUMN>
<COLUMN NAME="JOBCODE"><![CDATA[P10]]></COLUMN>
<COLUMN NAME="EFFDT"><![CDATA[16-Jul-1994 00:00:00]]></COLUMN>
<COLUMN NAME="EFF_STATUS"><![CDATA[A]]></COLUMN>
<COLUMN NAME="DESCR"><![CDATA[XXXXXXXXXXX]]></COLUMN>
</ROW>
</ROWS>
</TABLE>

I need to find out the DESCR. based on JobCode

*Input :  *Jobcode like P10
*Process: *find out the all the nodes with  Jobcode  *P10*  and find the 
latest Effective date (EFFDT) and display corresponding DESCR
*output: *DESCR with latest Effective date.

Please suggest me on best of way of doing this.

Thanks,
Anil






--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Break functionality  in XSL - 11/2/2009 2:38:00 PM</h1>
<pre>Anil Kumar Veeramalli wrote:
> in my xml file, I have some duplicate records, so I want to consider 
> only first records. other duplicate records simply want to ignore. That 
> is the reason I need break functionality.

Then use Muenchian grouping, that way you can process only the first 
item of each group of items with the same key value:
http://www.jenitennison.com/xslt/grouping/muenchian.xml

If you need more concrete help then show us a sample of the XML input 
you have and the corresponding transformation result you want to create, 
then we can show you an XSLT way of doing that, without talking about 
loops or breaking out of loops.


-- 

	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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Break functionality  in XSL - 11/2/2009 2:33:00 PM</h1>
<pre>in my xml file, I have some duplicate records, so I want to consider 
only first records. other duplicate records simply want to ignore. That 
is the reason I need break functionality.

Thanks,
Anil
 
>
> There is no xsl:break and xsl:for-each is not a loop. You might simply 
> want to put your condition into a predicate in the select attribute e.g.
>
> <xsl:for-each
> select="TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS'][. 
> = 'A']">
>
>



--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Break functionality  in XSL - 11/2/2009 2:27:00 PM</h1>
<pre>Anil Kumar Veeramalli wrote:

> I am using XSL1.0 version. I am looking for Break functionally in 
> for-loop, I didn't find correct documentation on that.
> 
> <xsl:for-each select="employees">
>   <xsl:for-each select="employee">
>   <xsl:if test="@NAME='STATUS'">
>       <xsl:variable name="status" select="."/>               
> <xsl:for-each 
> select="TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS']"> 
> 
>                   <xsl:value-of variable="test" select=".'">
>                      <xsl:if test="$test='A'">
>                         </xsl:if>
> ///want to come back from loop once a condition is satisfied and don't 
> want to loop again.
> 
>       </xsl:for-each>
> 
>   </xsl:if>
> 
>   </xsl:for-each>
> </xsl:for-each>
> </xsl:template>
> 
> Approaches I tried:
> 1) some were I read that we need to use <xsl:break>, but its not working.

There is no xsl:break and xsl:for-each is not a loop. You might simply 
want to put your condition into a predicate in the select attribute e.g.

<xsl:for-each
select="TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS'][. 
= 'A']">


-- 

	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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] Break functionality  in XSL - 11/2/2009 2:21:00 PM</h1>
<pre>Hi,

I am using XSL1.0 version. I am looking for Break functionally in 
for-loop, I didn't find correct documentation on that.

<xsl:for-each select="employees">
   <xsl:for-each select="employee">
   <xsl:if test="@NAME='STATUS'">
       <xsl:variable name="status" select="."/>      
          <xsl:for-each 
select="TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS']"> 

                   <xsl:value-of variable="test" select=".'">
                      <xsl:if test="$test='A'">
                         </xsl:if>
///want to come back from loop once a condition is satisfied and don't 
want to loop again.
 
       </xsl:for-each>

   </xsl:if>

   </xsl:for-each>
</xsl:for-each>
</xsl:template>

Approaches I tried:
1) some were I read that we need to use <xsl:break>, but its not working.


Thanks,
Anil


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Backward Navigation Problem - 11/2/2009 11:42:00 AM</h1>
<pre>Thanks, Andrew for the clarification.

In this particular problem, since the context node was an element,
therefore ancestor:: axis would certainly have only element nodes. So
ancestor::node() will work for this particular example. You rightly
explained this :)

But I thought, explicitly specifying the kind of nodes (say, with ..,
* or element()) once must search on an XPath axis is a good design
principle with XSLT programs.

On Mon, Nov 2, 2009 at 4:42 PM, Andrew Welch <andrew.j.welch@gmail.com> wrote:
> <pedant>
>
> I agree that in general using node() when really you mean element() is
> a poor choice, however on the ancestor axis it's probably not going to
> make that much difference.... In the vast majority of cases the only
> type of nodes that exist on the ancestor axis are elements (and the
> single document node).
>
> </pedant>


-- 
Regards,
Mukul Gandhi

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Backward Navigation Problem - 11/2/2009 11:13:00 AM</h1>
<pre>Hi,

>> ancestor::node()/TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN
>
> frankly I think, accessing the TABLE element using ancestor::node()
> looks a POOR choice to me.
>
> a node() test generally returns true for all XPath data model nodes,
> therefore I think ancestor::node() was not a good choice.

<pedant>

I agree that in general using node() when really you mean element() is
a poor choice, however on the ancestor axis it's probably not going to
make that much difference.... In the vast majority of cases the only
type of nodes that exist on the ancestor axis are elements (and the
single document node).

</pedant>

:)


-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Backward Navigation Problem - 11/2/2009 11:03:00 AM</h1>
<pre>Thanks Mukul. I will try that way.


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Backward Navigation Problem - 11/2/2009 11:00:00 AM</h1>
<pre>On Mon, Nov 2, 2009 at 4:23 PM, Anil Kumar Veeramalli
<anil.v@frescoinformatics.com> > Thanks MK. finally I was able to do
with
> ancestor::node()/TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN

frankly I think, accessing the TABLE element using ancestor::node()
looks a POOR choice to me.

a node() test generally returns true for all XPath data model nodes,
therefore I think ancestor::node() was not a good choice.

I suggest, you should use the expression which Mike suggested or can
use what I wrote.


-- 
Regards,
Mukul Gandhi

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Backward Navigation Problem - 11/2/2009 10:53:00 AM</h1>
<pre>Thanks MK. finally I was able to do with 
ancestor::node()/TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN


Thanks,
Anil


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>RE: [xsl] Backward Navigation Problem - 11/2/2009 10:19:00 AM</h1>
<pre>> 
> looks like
> TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='ST
> ATUS']" is not working.
> 
> Approaches I followed.
> 1)  
> ../TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME=
> 'STATUS']"
> 2)
> parent::node()/TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/C
> OLUMN[@NAME='DESCR']
> 

I would write it as a rooted path: /root/TABLE/.....

Your first try doesn't work because TABLE is not a child of the context node
(an employee element).

Your second try doesn't work because TABLE is not a child of the parent of
the context node (an employees element).

Regards,

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


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Backward Navigation Problem - 11/2/2009 10:11:00 AM</h1>
<pre>Hi Anil,
  if you are doing, <xsl:for-each select="employee">

then to reach to the TABLE node, you need to do as following:
../../TABLE

it seems, you are having trouble determining the context node.

On Mon, Nov 2, 2009 at 3:00 PM, Anil Kumar Veeramalli
<anil.v@frescoinformatics.com> wrote:
> Hi,
>
> My sample XML file lok lilke this
> <root>
> <employees>
> Â <employee hireDate="04/23/1999">
> Â  <COLUMN NAME="LAST">Hilllfrist</COLUMN> Â  Â  <COLUMN
> NAME="STATUS"><![CDATA[A]]></COLUMN>
> Â </employee>
> Â <employee hireDate="05/23/1999">
> Â  <COLUMN NAME="LAST">raj</COLUMN> Â  Â  <COLUMN
> NAME="STATUS"><![CDATA[T]]></COLUMN>
> Â </employee>
> </employees>
> <TABLE NAME="XLATTABLE_EMPL_STATUS">
> <ROWS>
> <ROW>
> <COLUMN NAME="STATUS"><![CDATA[T]]></COLUMN>
> <COLUMN NAME="DESCR"><![CDATA[Terminated]]></COLUMN>
> </ROW>
> <ROW>
> <COLUMN NAME="STATUS"><![CDATA[A]]></COLUMN>
> <COLUMN NAME="DESCR"><![CDATA[Active]]></COLUMN>
> </ROW>
> <ROW>
> </TABLE >
> </root>
>
> I need to Iterate all the Status values Â and need to fetch the description
> from XLATTABLE_EMPL_STATUS.
>
> Example if the status is A, it has to be displayed as Active, if its T , it
> has to be displayed as Terminated.
>
> My xsl code is as below.
>
> xsl:template match="root">
> Â <xsl:for-each select="employees">
> Â  <xsl:for-each select="employee">
> Â  <xsl:if test="@NAME='STATUS'">
> Â  Â  Â  <xsl:variable name="status" select="."/> Â  Â  Â  Â  Â  Â  Â  Â  <xsl:for-each
> select="TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS']">
> Â  Â  Â  Â  Â  Â  Â  <xsl:value-of
> select="TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='DESCR']"
> Â  Â  Â  </xsl:for-each>
>
> Â  </xsl:if>
>
> Â  </xsl:for-each>
> </xsl:for-each>
> </xsl:template>
>
> looks like
> TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS']" is not
> working.
>
> Approaches I followed.
> 1) Â ../TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS']"
> 2)
> parent::node()/TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='DESCR']
>
> Please suggest me on this.
>
>
> Thanks,
> Anil


-- 
Regards,
Mukul Gandhi

--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] Backward Navigation Problem - 11/2/2009 9:31:00 AM</h1>
<pre>Hi,

My sample XML file lok lilke this
<root>
<employees>
  <employee hireDate="04/23/1999">
    <COLUMN NAME="LAST">Hilllfrist</COLUMN>  
    <COLUMN NAME="STATUS"><![CDATA[A]]></COLUMN>
  </employee>
  <employee hireDate="05/23/1999">
    <COLUMN NAME="LAST">raj</COLUMN>  
    <COLUMN NAME="STATUS"><![CDATA[T]]></COLUMN>
  </employee>
</employees>
<TABLE NAME="XLATTABLE_EMPL_STATUS">
<ROWS>
<ROW>
<COLUMN NAME="STATUS"><![CDATA[T]]></COLUMN>
<COLUMN NAME="DESCR"><![CDATA[Terminated]]></COLUMN>
</ROW>
<ROW>
<COLUMN NAME="STATUS"><![CDATA[A]]></COLUMN>
<COLUMN NAME="DESCR"><![CDATA[Active]]></COLUMN>
</ROW>
<ROW>
</TABLE >
</root>

I need to Iterate all the Status values  and need to fetch the 
description from XLATTABLE_EMPL_STATUS.

Example if the status is A, it has to be displayed as Active, if its T , 
it has to be displayed as Terminated.

My xsl code is as below.

xsl:template match="root">
  <xsl:for-each select="employees">
    <xsl:for-each select="employee">
    <xsl:if test="@NAME='STATUS'">
        <xsl:variable name="status" select="."/>        
   
        <xsl:for-each 
select="TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS']">
                <xsl:value-of 
select="TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='DESCR']"
        </xsl:for-each>

    </xsl:if>

    </xsl:for-each>
</xsl:for-each>
</xsl:template>

looks like 
TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS']" is 
not working.

Approaches I followed.
1)  ../TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='STATUS']"
2) 
parent::node()/TABLE[@NAME='XLATTABLE_EMPL_STATUS']/ROWS/ROW/COLUMN[@NAME='DESCR']

Please suggest me on this.


Thanks,
Anil





 


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>[xsl] XSL-List Guidelines - 11/1/2009 3:30:00 PM</h1>
<pre>This information is posted to the XSL-List (and the XSL-List Digest)
at intervals under the subject line "XSL-List guidelines".

INTRODUCTION TO XSL-LIST

XSL-List hosts discussion of XSL itself, XSL applications and implementation, and XSL user questions. XSL-List is open to everyone, users and developers, experts and novices alike. There is no restriction to what may be posted on the XSL-List provided it is related to XSL, which is considered to include XSLT (versions 1 and 2), XPath (versions 1 and 2) and XSL Formatting Objects (FO).

XSL-List is not a W3C mailing list, and has no affiliation with W3C (or any official standing with any standards organization). However, XSL-List was established with the encouragement of members of the W3C XSL Working Group, and members of the Working Group are among the subscribers to the list.

Only subscribers can post to XSL-List, but since the goal is to increase the level of XSL knowledge, XSL-List is being archived for everybody to view. The topics being discussed on the XSL-List change as new ideas arise or existing problems are dealt with, but the archive contains all of the ideas and solutions that have been discussed on the list.

XSL-List is provided by Mulberry Technologies, Inc., as a service to the XSL user community. Mulberry is an XML and SGML consultancy specializing in applications that have a text design, processing, interchange, or display component. For more information about Mulberry Technologies, Inc. see http://www.mulberrytech.com 


SUBSCRIBING TO THE XSL-LIST

To subscribe to the list, fill out the form at http://www.mulberrytech.com/xsl/xsl-list/subscribe-unsubscribe.html.


DAILY DIGEST

Daily digests -- copies of a whole days XSL-List messages sent as one email message -- are available. Not only is it a single email message containing all of that day's XSL-List messages, it is also half the size, on average, of the individual messages since it doesn't include the overhead of the mail headers from each message.

To unsubscribe from the list and subscribe to the digest, use the form at http://www.mulberrytech.com/xsl/xsl-list/subscribe-unsubscribe.html.


POSTING GUIDELINES

Only subscribers can post to XSL-List, and only from the exact address they used when they subscribed.

There is no restriction on what may be posted to the XSL-List provided it is related to XSL. Items concerning XML but without a direct connection to XSL should be posted to a XML-related list instead of to the XSL-List. Items related to DSSSL should be posted to the DSSSList.

Do not begin your subject line with "help" or "subscribe" since the list software will bounce the message because it looks like is an administrative request.

It is best to start a new message for a new thread. Do not start a new thread by replying to an unrelated message and just changing the subject line, since the header of your message will contain references to the previous message and your new message will appear in the archive as one of the replies to the original message.

Both subscribers to the full list (xsl-list@lists.mulberrytech.com) and subscribers to the digest (xsl-list-digest@lists.mulberrytech.com) should post their messages to xsl- list@lists.mulberrytech.com; the messages will be received by both subscribers to the list and subscribers to the digest.


BEFORE YOU POST ... DO YOUR HOMEWORK
 - Check that your question isn't already answered in the XSL FAQ at http://www.dpawson.co.uk/.
 - Check that your question isn't already answered in the XSL-List archives at http://www.biglist.com/lists/xsl-list/archives/.
 - If you are asking for help with XSL code, determine which version of the language you are using (plus extensions, if any), and confirm that your XSL processor supports that version and/or extension. (If you are unsure of your processor, this can be determined by using the stylesheet at http://www.mulberrytech.com/xsl/xsl-list/processor-version.xsl on any input, including the stylesheet itself: see http://www.mulberrytech.com/xsl/xsl-list/processor-version.html for more information.) An XSLT 1.0 engine will not process stylesheets written in XSLT 2.0!


IN YOUR POSTING ...

Name the XSL processor, processor version, and version of the language you are using. This information is frequently necessary to diagnose a problem exactly, and always helps respondents give good advice.

If you are replying to a post, trim the quoted message to just the parts to which you are replying.

In addition to following simple rules of net etiquette and common sense, you will improve the chances that you will receive prompt and helpful responses by:
 - Asking questions specific enough that answers are possible. Describe what you are trying to do, how you approached it, what happened, and why you don't like the result you got. Don't simply say "it gave me an error": paste in the error message (someone else can probably make sense of it).
  -  Illustrating your question with a demonstration of the problem. Well-composed questions frequently include a small XML sample, an XSLT stylesheet, the results received, and the result that was desired - all in miniature, to make it comprehensible to readers new to your problem. (It is also not uncommon to discover what a problem actually is in the process of reducing it to an illustrative version.)


USE INFORMATIVE SUBJECT LINES

When posting to the XSL-List, do not use uninformative subject lines like "Urgent", "Question", or "Newbie HELP!!!", which don't say anything about what your problem is. Instead, use a meaningful subject line that will make sense to the people whose help you are trying to get. It may even get a response from people who normally shy away from "beginner" questions.

Informative subject lines make the XSL-List archive more useful since people with the same problem will more easily find the relevant threads.


DO NOT CROSS-POST

Cross-posting to the XSL-List and to another list, even XML-Dev or the DSSSList, is generally counter-productive. No list's archive will contain the complete thread; cross-posts from non-subscribers continuing the thread will bounce; and XSL-List subscribers who are not also on the other list will only see half the thread, as will those on the other list who are not also reading XSL- List. Subscribers to both lists may see two copies of the message, annoying them as well.


REPLIES GO TO THE LIST

The reply address of XSL-List messages (and of digests) is xsl-list@lists.mulberrytech.com so REPLIES GO TO THE LIST BY DEFAULT. If you want to reply to just the author of a post, you should change the "To:" field in your reply.


USE SHORT QUOTES OF PREVIOUS MESSAGES IN REPLIES

Please do not quote entire messages just to add a few lines at the beginning or end. Instead, quote the parts to which you are directly replying or quote enough to establish the context.

Everybody on the list has already received the message that you are quoting, and anyone searching the archive will find your message and the previous message listed under the same thread.

Subscribers to the XSL-List will just ignore most of the quoted messages and move to the next post, but subscribers to the XSL-List Digest will mostly have to page past the quoted messages to reach the next material in which they are interested in reading.


POSTINGS MUST BE IN PLAIN TEXT ONLY

Postings to XSL-List must be in plain text only. The XSL-List does not allow 
HTML postings because many users cannot display them appropriately, and because 
they are unnecessarily large. 


POSTINGS MAY NOT BE IN BASE 64

Postings to XSL-List may not be in Base 64 because it makes a mess of both the digest and the archive. 


ATTACHMENTS ARE BANNED

Since Mulberry's mailing lists have in the past been unwittingly used for spreading viruses in e-mail attachments, all e-mail attachments are banned from the XSL-List.

XSL stylesheets are XML files, and XML files are text files, so this does not affect the majority of posts to the list since you can include the files' text in the body of your message. If you need to refer to a binary file such as a PDF file, you should put the file on a Web site or FTP site and include the file's URL in your XSL-List post.

If you do include an attachment in your XSL-List post -- even a HTML attachment -- your message will bounce.


YOUR POST WILL BE PERMANENTLY ARCHIVED

Because it is a public resource created by and for the entire XSL
community, we do not edit XSL-List. Therefore, it is responsibility of
list subscribers not to post anything to the list that they do not want
publicly available, possibly for a very long time.

Postings in the list archives will be complete, including: all contents, examples, sample data, code or code fragments, and email header and footer contents. An automated process will obscure the domain portion of email addresses (the part after the @ sign).in the headers and footers of postings, but no guarnantee is made that this process will be completely successfull. Other than this, all postings will be archived in public as received.

Further, we at Mulberry could not, even if we wanted to, edit all of the 
archives of XSL-List. Several third-parties have created unofficial archives of 
XSL-List, often without asking, or even informing, Mulberry. Postings to XSL-List 
will be included in an unknown and ever-changing variety of web publications. If 
you don't want your questions/comments/answers in public view don't post them to 
XSL-List. 


THIRD-PARTY ARCHIVES OF XSL-LIST

Third parties are welcome to create searchable or reference archives of XSL-List
provided they adhere to the following guidelines: 
 - the material is clearly labelled as being from XSL-List, with 
   an acknowledgement of Mulberry's role as provider of XSL-List
 - there is a navigable pointer to the official list page at
   http://www.mulberrytech.com/xsl/xsl-list/ either on every posting 
   or associated with the user interface such that it is visible with 
   the postings
 - list postings are unedited
 - either the entire archive of the list is provided or there is a 
   clearly stated method for selecting the subset of the list that is provided

Mulberry does not provide these third parties with help to create these archives, does not endorse particular third party archives, and has no control over the ways in which they present the material in their systems.

People or organizations that publish the contents of XSL-List without following 
the guidelines above are being very antisocial. Please bookmark either 
the official XSL-List archive or one provided by a service that plays nicely 
in the community and shun those who do not give credit where credit it due.


UNSUBSCRIBING FROM THE XSL-LIST

To unsubscribe from XSL-List, use the form at http://www.mulberrytech.com/xsl/xsl-list/subscribe-unsubscribe.html.


UNSUBSCRIBING FROM THE XSL-LIST DIGEST

To unsubscribe from the XSL-List digest, use the form at http://www.mulberrytech.com/xsl/xsl-list/subscribe-unsubscribe.html.


IF YOU STOP GETTING XSL-LIST MESSAGES

If you stop receiving XSL-List message, you may have been removed because mail to you was bouncing. You are not being picked on, and you can just rejoin the list.


ARCHIVE

XSL-List messages are archived at http://www.biglist.com/lists/xsl-list/archives/.


REPORTING BUGS IN SOFTWARE

Bugs in software should firstly be reported to its author rather than to the XSL List. Questions regarding how to work around bugs are welcome, but the list does not function as a bug-tracking system for any software.


XSL FAQ AND OTHER INFORMATION ON XSL

Dave Pawson's XSL FAQ is at http://www.dpawson.co.uk/.

The W3C information on XSL is at http://www.w3.org/Style/XSL.

An excellent source of information about XSL is the XSL page of Robin Cover's SGML/XML Web Page at http://www.oasis-open.org/cover/xsl.html.

Mulberry's XSLT 1.0 and XPath 1.0 Quick Reference is at http://www.mulberrytech.com/quickref/.


DSSSLIST -- THE DSSSL USERS' MAILING LIST

Mulberry Technologies, Inc., also provides the DSSSList -- the DSSSL Users' Mailing List. For subscription information and the DSSSList archive, see http://www.mulberrytech.com/dsssl/dssslist.


CONTACT

If you have any questions or problems, please contact xsl-list-owner@lists.mulberrytech.com.


ADMINISTRATIVE COMMUNICATIONS

The list administrator will reply to emailed questions relating to the mechanics and administration of XSL-List and to help new users learn to use the list. However, the administrator will not take the time to navigate mazes of any sort in order to do so. If the list owner's messages are rejected by a user's anti-spam system the list owner will not pursue the matter. Similarly, if list-related notices to a subscriber are rejected as spam the subscriber will be unsubscribed. 



CHANGE History

==============
May 5, 2009 - btu. 

  10. Added paragraph clarifying that all content will be archived in 
      public, including text, examples, code, and email headers and 
      footers including names.

==============
February 1, 2008 - btu. 

  9. Policy on third-party archives added. 

  8. Policy banning attachments and postings in Base 64 clarified. 

==============
September 1, 2007 - btu. 

  7. Administrative communication policy clarified.  


==============
October 1, 2005 - btu. 

  6. Mulberry Technologies' relationship to XSL-List clarified. We 
     do the work. We pay the bills. Organizations who post unauthorized 
     copies of the archive without acknowledging Mulberry's contribution 
     are not playing nicely in the community. 

==============
March 2, 2005 - btu. 

  4. Users are asked to identify the version of XSLT and XPath
     they are using for questions that are specific to one version

  5. Clarifying the policy on editing the list archive (we don't edit
     it). 

==============
March 30, 2004 - btu. 

  1. All references to subscribing and unsubscribing have been
     updated to reflect changes in the list management system.

  2. Pointers to the XSL and XPath specification were removed. There
     are now so many specifications and draft specifications relevant
     to XSL that it is more practical to simply point to W3C's XSL
     page. 

  3. A few typographical errors were corrected.


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Different behaviour for the first item in a    - 11/1/2009 7:31:00 AM</h1>
<pre>Ken,
Checked all 378 pages - Perfect!
Thanks to you and Martin for your help.

Mark 


--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Different behaviour for the first item in a for-each-group - 11/1/2009 2:47:00 AM</h1>
<pre>At 2009-10-31 19:31 -0700, Mark Wilson wrote:
>That seems to be it. I checked 28 of the 200+ pages and all was OK.
>
>Sorry I did not make it clear from the start. Also, somewhere along 
>the line an un-needed for-each crept in.

Then you don't need $group-position ... in what I see in your bit 
below it is totally redundant.

>            <xsl:variable name="group-position" select="position()"/>
>                <fo:table-row>
>                    <xsl:if test="position()=1 and $group-position=1">

It was there to get the first of the current-group() in the first of 
the groups, so if you aren't walking through the groups then you 
don't need it.  You are acting on only the first member of each 
group, thus I gather you are doing it for de-duping and not for 
classical grouping.

>By the way, you have helped with this very same function three times 
>now over the past year. For the record, here is the actual correct template.

You might want to review taking out $group-position because it isn't 
doing anything for you.

I'm glad things have worked out for you.  And a Happy Hallowe'en to 
you and yours!

. . . . . . . Ken


--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Different behaviour for the first item in a   - 11/1/2009 2:32:00 AM</h1>
<pre>Hi Ken,
That seems to be it. I checked 28 of the 200+ pages and all was OK.

Sorry I did not make it clear from the start. Also, somewhere along the line 
an un-needed for-each crept in.

By the way, you have helped with this very same function three times now 
over the past year. For the record, here is the actual correct template.

Thanks again.
Happy Halloween!
Mark

xsl:template name="format-article">
        <xsl:for-each-group select="../Article" group-by="Title">
            <xsl:sort select="Title"/>
            <xsl:sort select="Year"/>
            <xsl:sort select="IssueNumber" data-type="number"/>
            <xsl:sort select="Page"/>
            <xsl:variable name="group-position" select="position()"/>
                <fo:table-row>
                    <xsl:if test="position()=1 and $group-position=1">
                        <!--then at the very first of the sorted 
population-->
                        <xsl:attribute 
name="keep-with-previous">always</xsl:attribute>
                    </xsl:if>
                    <!-- And all the others in a non-"keeping" row -->
                    <fo:table-cell>
                        <fo:block>
                            <xsl:choose>
                                <xsl:when test="parent::Item">
                                    <xsl:call-template name="article0"/>
                                </xsl:when>
                                <xsl:when test="parent::Level1">
                                    <xsl:call-template name="article1"/>
                                </xsl:when>
                                <xsl:when test="parent::Level2">
                                    <xsl:call-template name="article2"/>
                                </xsl:when>
                                <xsl:when test="parent::Level3">
                                    <xsl:call-template name="article3"/>
                                </xsl:when>
                            </xsl:choose>
                            <fo:block xsl:use-attribute-sets="citation">
                                <fo:wrapper xsl:use-attribute-sets="title">
                                    <!--for a given title-->
                                    <xsl:apply-templates select="Title"/>
                                </fo:wrapper>
                                <xsl:apply-templates select="Person"/>
                                <!--and for each citation-->
                                <xsl:apply-templates 
select="current-group()" mode="format"/>
                            </fo:block>
                        </fo:block>
                    </fo:table-cell>
                </fo:table-row>
        </xsl:for-each-group>
    </xsl:template>
 



--~------------------------------------------------------------------
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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Different behaviour for the first item in a for-each-group - 11/1/2009 1:57:00 AM</h1>
<pre>At 2009-10-31 15:51 -0700, Mark Wilson wrote:
>I was not careful in the way I described this problem. Each group 
>consists of a single title with one or more citations. What I must 
>have said is that I wanted to set the Title in each group to "keep". 
>What I *should* have said was, I want to set the only the first 
>group to "keep". For the input data at the end of this email, that 
>would be the title "Further observations".

Is it a co-incidence that it is alphabetically the first and 
positioned as first?  I'm assuming because of your use of <xsl:sort> 
that the alphabetical order is important in the determination of first.

>All the rest would not be marked "keep".

Then I would have worded your request "the first of the sorted 
population" not "the first of the group".

>Clearly, I do not want (from listing 1):
>                    <xsl:if test="position()=1">
>                        <xsl:attribute 
> name="keep-with-previous">always</xsl:attribute>
>                    </xsl:if>

It wasn't clear to me because you were grouping articles and asked 
for the first of the group.  I believe Martin interpreted it the same way.

I now understand you were grouping the population of articles and 
need a keep on the first of the sorted population.

>However, I do not know XPath well. How do I select only the first 
>group for marking and let the other groups pass without marking them?

   <xsl:for-each-group select="...population...">
     <xsl:sort .../>
     <xsl:sort .../>
     <xsl:sort .../>
     <xsl:variable name="group-position" select="position()"/>
     <xsl:for-each select="current-group()">
        <fo:table-row>
           <xsl:if test="position()=1 and $group-position=1">
              <!--then at the very first of the sorted population-->
              <xsl:attribute name="keep-with-previous">.....

I hope this helps.

. . . . . . . . . . . . . Ken


--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com>
--~--</pre>
</article>
<article>
<h1>Re: [xsl] Different behaviour for the first item in a  for-each-group - 10/31/2009 10:52:00 PM</h1>
<pre>Hi Ken,
I was not careful in the way I described this problem. Each group consists 
of a single title with one or more citations. What I must have said is that 
I wanted to set the Title in each group to "keep". What I *should* have said 
was, I want to set the only the first group to "keep". For the input data at 
the end of this email, that would be the title "Further observations". All 
the rest would not be marked "keep".

Clearly, I do not want (from listing 1):
                    <xsl:if test="position()=1">
                        <xsl:attribute 
name="keep-with-previous">always</xsl:attribute>
                    </xsl:if>
However, I do not know XPath well. How do I select only the first group for 
marking and let the other groups pass without marking them?

All help appreciated.
Mark

Listing 1:
<xsl:template name="format-article">
        <xsl:for-each-group select="../Article" group-by="Title">
            <xsl:sort select="Title"/>
            <xsl:sort select="Year"/>
            <xsl:sort select="IssueNumber" data-type="number"/>
            <xsl:sort select="Page"/>
            <xsl:for-each select="current-group()">
                <fo:table-row>
                    <!-- Put the first group in a keeping row-->
                    <xsl:if test="position()=1">
                        <xsl:attribute 
name="keep-with-previous">always</xsl:attribute>
                    </xsl:if>
                    <!-- And all the other groups in a non-"keeping" row -->
                    <fo:table-cell>
                        <fo:block>
                            <xsl:choose>
                                <xsl:when test="parent::Item">
                                    <xsl:call-template name="article0"/>
                                </xsl:when>
                                <xsl:when test="parent::Level1">
                                    <xsl:call-template name="article1"/>
                                </xsl:when>
                                <xsl:when test="parent::Level2">
                                    <xsl:call-template name="article2"/>
                                </xsl:when>
                                <xsl:when test="parent::Level3">
                                    <xsl:call-template name="article3"/>
                                </xsl:when>
                            </xsl:choose>
                            <fo:block xsl:use-attribute-sets="citation">
                                <fo:wrapper xsl:use-attribute-sets="title">
                                    <!--for a given title-->
                                    <xsl:apply-templates select="Title"/>
                                </fo:wrapper>
                                <xsl:apply-templates select="Person"/>
                                <!--and for each citation-->
                                <xsl:apply-templates 
select="current-group()" mode="format"/>
                            </fo:block>
                        </fo:block>
                    </fo:table-cell>
                </fo:table-row>
            </xsl:for-each>
        </xsl:for-each-group>
    </xsl:template>

Input data:
<Item>
     <Article>
        <Title>Further observations
        Mar/Apr
        1999
        34
        2
    
    
        Letters to the editor
        Nov/Dec
        2001
        27
        6
    
    
        Philatelic news and views
        Sep/Oct
        2001
        35
        5
    
    
        Philatelic news and views
        Sep/Oct
        2002
        11
        5
    
    
        Philatelic news and views
        Nov/Dec
        2002
        28
        6
    
    
        Philatelic news and views
        Jan/Feb
        2003
        24
        1
    
    
        Philatelic news and views
        Nov/Dec
        2006
        18
        6
    
 



--~------------------------------------------------------------------
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] Setting a foreign attribute - 10/31/2009 9:50:00 PM
Hi Ken
Worked again.

I think I only have one problem left (Cell too large to fit on a single 
page). I'll look at that, but the rest of the "keep" problem seems solved: 
pages seem to be ending correctly, but I have almost 200 of them to check 
first.
Thanks,
Mark
 



--~------------------------------------------------------------------
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] Setting a foreign attribute - 10/31/2009 9:24:00 PM
At 2009-10-31 14:15 -0700, Mark Wilson wrote:
>FOP does not like this fragment and calls  a 
>foreign attribute.

Right ... xsl:use-attribute-sets= is recognized by XSLT processors 
and you are putting that attribute into an XSL-FO file which doesn't 
recognize it because it isn't part of the FO vocabulary so FO 
processors rightfully complain.

>                    
>                         
>                                
>                                    article0
>                                
>                                
>                                    article1
>                                
>                                
>                                    article2
>                                
>                                
>                                    article3
>                                
>                            
>
>                                    .....
>                        
>
>Is there a way to set  similar to my 
>unacceptable construction, or do I have to create all six attributes 
>for each ?

The latter.  You've overlooked what is happening where in the 
process.  xsl:use-attribute-sets= is acted on during the building of 
the result tree and isn't recognized when placed directly in the result tree.

If you change:

   
     ...
   

to:

   
     ...
   

Then you can use  in order to add 
all of the attributes, but it means that everywhere where you have:

   
     ...

you will need to have:

   
     
     ...

But there are features of xsl:use-attribute-sets= that might mean you 
can't just do that everywhere.

I hope this helps.

. . . . . . . . . . Ken

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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] Setting a foreign attribute - 10/31/2009 9:16:00 PM
Hi all,
FOP does not like this fragment and calls  a foreign 
attribute.

                    
                         
                                
                                    article0
                                
                                
                                    article1
                                
                                
                                    article2
                                
                                
                                    article3
                                
                            

                                    .....
                        

Is there a way to set  similar to my unacceptable 
construction, or do I have to create all six attributes for each ?

Thanks,
Mark 



--~------------------------------------------------------------------
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] copy attributes, except some - 10/31/2009 9:16:00 PM
Hi Wendell,

Not all problems can be presented simply.  This one had quite a few 
parameters, including the fact that it was not a single thing but a 
recurring pattern with growing overhead.  It took some time but it works 
out ok, thanks to everyone who contributed.

Has it is a relatively fundamental XML/XSL pattern I just also submit 
that it may be worth giving it a second thought in case, at some point 
in the evolution of XSLT, there is a way to work out a simpler 
solution.  Comparing nodes and comparing node values are quite well 
taken care of, but comparing node names, in a namespace safe way is a 
little trickier.  It is settled for me now and it may have been useful 
for others, so maybe it is fine. I may not be a good judge for the 
relevancy of a more obvious solution, anymore. Maybe better documenting 
it in the reference manuals could be enough.

In any case, thank you again.

Cheers,
ac




> AC,
>
> At 09:02 PM 10/29/2009, you wrote:
>> Hi Wendell,
>>
>> True. The thing that still bothers me with this is that since nodes 
>> and content are compared, a variable like $excepted-attributes has to 
>> be defined for every attribute group, for every tree/subtree that may 
>> get copied which is getting to be quite an overhead here.
>
> Yes, certainly. My suggestion is clean only if the variable can be 
> declared at the top -- that is, if @name1 attributes are always to be 
> excluded. Even then, there are situations where it will be problematic.
>
> This is the problem with posting fragments of problems to the list. As 
> we have noted before (in this thread and elsewhere), without a 
> complete problem spec, we can't really provide a solution. For 
> example, a parameterized approach, in which $exclude-attributes would 
> be passed through templates (using a tunnel parameter) and modified 
> where necessary, might be another thing worth trying.
>
> On the other hand, sometimes our waving flashlights in the dark will 
> lead to an accidental insight which is at least as good, or better, 
> than a solution. If that's the case here, we should call it a success.
>
> Cheers,
> Wendell
>
>
>
> ======================================================================
> Wendell Piez                            mailto:wapiez@mulberrytech.com
> Mulberry Technologies, Inc.                http://www.mulberrytech.com
> 17 West Jefferson Street                    Direct Phone: 301/315-9635
> Suite 207                                          Phone: 301/315-9631
> Rockville, MD  20850                                 Fax: 301/315-8285
> ----------------------------------------------------------------------
>   Mulberry Technologies: A Consultancy Specializing in SGML and XML
> ======================================================================
>
>
> --~------------------------------------------------------------------
> 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] Different behaviour for the first item in a  for-each-group - 10/31/2009 6:48:00 PM
Hi Ken,
As always, sweet!

I am working my way through the "keep" problem we discussed yesterday and I 
think your hint below will let me simplify all of my templates, not just 
this one. I was worried about all the duplication I was putting in. Better 
to keep it clean now than to re-factor later!

Thanks,
Mark

 



--~------------------------------------------------------------------
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] Different behaviour for the first item in a for-each-group - 10/31/2009 6:40:00 PM
At 2009-10-31 11:10 -0700, Mark Wilson wrote:
>I have a working template that I need to modify. At the moment, as 
>it iterates through the for-each-group, every group (Title) is 
>treated identically. I need to provide a different behavior The 
>first group will be wrapped by a row/cell with the "keep "property, 
>all others in a non-"keep" property row/cell.  The current template 
>is in Listing 1, my attempt to modify it in listing 2. Before I 
>bollix everything up, would someone look it over and tell me if I 
>have done it right or if there is a better way?

There are better approaches to what you've done that I think will 
help.  Your listing 2 is characterized by a lot of duplication that I 
think is not necessary.

>Listing 2:
>
>        
>            
>            
>            
>            
>            
>            
>                
>                    

The above test will always be true because you are testing that the 
group exists (in that the first member of the group exists) which is 
going to be true because you just created the group.

>               

The above attribute appears to be the only difference in the 
behaviour, and that correlates with your description above, so there 
is a better way to address this requirement by only selectively 
adding the attribute:

    
        
            
            
            
            
            
            
              
                 
                  always
                 
                 
                   
                     
                       
                     
                     
                     
                   
                 
              
            
            ...

I hope this helps!

. . . . . . . . . . . . Ken


--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: 
--~--


Re: [xsl] Different behaviour for the first item in a for-each-group - 10/31/2009 6:38:00 PM
Hi Martin,
Thanks. Yes, position() is what I want.
Mark

 


--~------------------------------------------------------------------
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] Different behaviour for the first item in a for-each-group - 10/31/2009 6:32:00 PM
Mark Wilson wrote:

> I have a working template that I need to modify. At the moment, as it 
> iterates through the for-each-group, every group (Title) is treated 
> identically. I need to provide a different behavior The first group will 
> be wrapped by a row/cell with the "keep "property, all others in a 
> non-"keep" property row/cell.  The current template is in Listing 1, my 
> attempt to modify it in listing 2. Before I bollix everything up, would 
> someone look it over and tell me if I have done it right or if there is 
> a better way?

> 
>        
>            
>            
>            
>            
>            
>            
>                
>                    
>                        
>                        
>                            
>                                          xsl:use-attribute-sets="title">
>                                    
>                                
>                                
>                                
>                                 select="current-group()" mode="format"/>
>                            
>                        
>                            
>                    
>                    
>                        
>                            
>                                
>                                
>                                     xsl:use-attribute-sets="title">
>                                         select="Title"/>
>                                    
>                                    
>                                     select="current-group()" mode="format"/>
>                                
>                            
>                            
>                    
>                
>            
>        
>    

Inside of the for-each-group position() will give you the "number" of 
the group being processed thus if you want to treat the first group 
differently then I think you want


        
            
            
            
            


                
                    
                        
                        
                            
                                         
                                    
                                
                                
                                
                                
                            
                        
                            
                    
                    
                        
                            
                                
                                
                                    
                                        
                                    
                                    
                                    
                                
                            
                            
                    
                

        
    

-- 

	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] Different behaviour for the first item in a for-each-group - 10/31/2009 6:11:00 PM
Hi all,
I have a working template that I need to modify. At the moment, as it 
iterates through the for-each-group, every group (Title) is treated 
identically. I need to provide a different behavior The first group will be 
wrapped by a row/cell with the "keep "property, all others in a non-"keep" 
property row/cell.  The current template is in Listing 1, my attempt to 
modify it in listing 2. Before I bollix everything up, would someone look it 
over and tell me if I have done it right or if there is a better way?

Listing 1.
 
        
            
            
            
            
                        
                
                
                    
                
                
                
                
            
        
    

Listing 2:
 
        
            
            
            
            
            
            
                
                    
                        
                        
                            
                                         
                                    
                                
                                
                                
                                
                            
                        
                            
                    
                    
                        
                            
                                
                                
                                    
                                        
                                    
                                    
                                    
                                
                            
                            
                    
                
            
        
    
 



--~------------------------------------------------------------------
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] Widows and orphans in XSL-FO - 10/31/2009 1:50:00 AM
Hi Ken,
That is close, but  any of the red elements (including the top level ones) 
may be followed by a back element before one of the lower level red levels 
is encountered.

I think, though, you have given me the general idea. I work on it for 
awhile.

Thanks,
Mark

--------------------------------------------------
From: "G. Ken Holman" 
Sent: Friday, October 30, 2009 5:57 PM
To: 
Subject: Re: [xsl] Widows and orphans in XSL-FO

> At 2009-10-30 17:44 -0700, Mark Wilson wrote:
>>Sorry my original post was not clear enough. I have a short output PDF 
>>file that may show better what I mean, but I cannot send it to the list. A 
>>longer copy is on the web at:
>>
>>http://www.knihtisk.org/library/specialist/pdf/a.pdf
>
> That helps a lot.
>
>>Page 1 ends with "Kvapilová, Hana"
>>
>>In a perfect world, it would have ended with the line above it, "New 
>>issues: Czech Republic. Jan/Feb 1996 p.23." which is an  element 
>>and Kvapilová, Hana" ( a  element), would have been pushed to the 
>>next page.
>>
>>The rule I want to enforce is:
>>"A page may only end with one or more renditions of  elements." 
>>(Visually: a page may only end with a black rendition, never a red 
>>rendition).
>>
>>The bottom of page 3 shows how pages should end. There, a list of 
>> elements extends from the bottom of page 3 to the top of page 4
>>
>>I did get a lead on "blind tables" with my Google search and am attempting 
>>to see if that will work for me. The "keep-" properties seems more in line 
>>with my needs than the "break-" properties, but I am not sure.
>
> How about for your top-level entries (e.g. "Actors") you don't use a keep.
>
> Then for their first-level children (i.e. starting with "-") and 
> second-level grandchildren (i.e. starting with "- - ") use 
> keep-with-next.within-column="always".
>
> Then for the black lines, use keep-with-previous.within-column="always". 
> This handles the two lines of the "Velehrad" entry.
>
> That way you'll get no page breaks between your red and black lines.  Nor 
> will you get a break between *adjacent* red lines.  If you don't want a 
> break before "Strahovaska Madona" then add 
> keep-with-previous.within-column="always" to the "- - " grandchildren.
>
> Page breaks should put first-level children at the top of the column, 
> except between the first child of a top-level entry.
>
> I think that will get you real close and perhaps meet all of your 
> requirements as I understand them.
>
> I hope this helps.
>
> . . . . . . . . . . . . . Ken
>
> --
> Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
> Interested in other classes?  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-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] Widows and orphans in XSL-FO - 10/31/2009 12:58:00 AM
At 2009-10-30 17:44 -0700, Mark Wilson wrote:
>Sorry my original post was not clear enough. I 
>have a short output PDF file that may show 
>better what I mean, but I cannot send it to the 
>list. A longer copy is on the web at:
>
>http://www.knihtisk.org/library/specialist/pdf/a.pdf

That helps a lot.

>Page 1 ends with "Kvapilová, Hana"
>
>In a perfect world, it would have ended with the 
>line above it, "New issues: Czech Republic. 
>Jan/Feb 1996 p.23." which is an  
>element and Kvapilová, Hana" ( a  
>element), would have been pushed to the next page.
>
>The rule I want to enforce is:
>"A page may only end with one or more renditions 
>of  elements." (Visually: a page may 
>only end with a black rendition, never a red rendition).
>
>The bottom of page 3 shows how pages should end. 
>There, a list of  elements extends from 
>the bottom of page 3 to the top of page 4
>
>I did get a lead on "blind tables" with my 
>Google search and am attempting to see if that 
>will work for me. The "keep-" properties seems 
>more in line with my needs than the "break-" properties, but I am not sure.

How about for your top-level entries (e.g. "Actors") you don't use a keep.

Then for their first-level children (i.e. 
starting with "-") and second-level grandchildren 
(i.e. starting with "- - ") use keep-with-next.within-column="always".

Then for the black lines, use 
keep-with-previous.within-column="always".  This 
handles the two lines of the "Velehrad" entry.

That way you'll get no page breaks between your 
red and black lines.  Nor will you get a break 
between *adjacent* red lines.  If you don't want 
a break before "Strahovaska Madona" then add 
keep-with-previous.within-column="always" to the "- - " grandchildren.

Page breaks should put first-level children at 
the top of the column, except between the first child of a top-level entry.

I think that will get you real close and perhaps 
meet all of your requirements as I understand them.

I hope this helps.

. . . . . . . . . . . . . Ken

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: 
--~--


Re: [xsl] Widows and orphans in XSL-FO - 10/31/2009 12:45:00 AM
Hi Ken,
Sorry my original post was not clear enough. I have a short output PDF file 
that may show better what I mean, but I cannot send it to the list. A longer 
copy is on the web at:

 http://www.knihtisk.org/library/specialist/pdf/a.pdf

Page 1 ends with "Kvapilová, Hana"

In a perfect world, it would have ended with the line above it, "New issues: 
Czech Republic. Jan/Feb 1996 p.23." which is an  element and 
Kvapilová, Hana" ( a  element), would have been pushed to the next 
page.

The rule I want to enforce is:
"A page may only end with one or more renditions of  elements." 
(Visually: a page may only end with a black rendition, never a red 
rendition).

The bottom of page 3 shows how pages should end. There, a list of  
elements extends from the bottom of page 3 to the top of page 4

I did get a lead on "blind tables" with my Google search and am attempting 
to see if that will work for me. The "keep-" properties seems more in line 
with my needs than the "break-" properties, but I am not sure.
Mark 



--~------------------------------------------------------------------
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] Widows and orphans in XSL-FO - 10/30/2009 11:52:00 PM
At 2009-10-30 15:33 -0700, Mark Wilson wrote:
>I looked at that function and am not sure if it would be useful or 
>not. However, a Google search on it did lead me to within-page. The 
>article warned that FOP (which I am using) did not support this, but 
>found me a free download of XEP.
>When I tried to run my stylesheet, XEP failed on the current-time() 
>function from XSLT. I could get along without that, but then it 
>failed on the base-uri(/) function,

You are not obliged to use the XSLT processor in XEP ... just use any 
XSLT 2.0 processor (I have great success with Saxon) to produce your 
XSL-FO from your XML, and then pass the raw XSL-FO to XEP for formatting.

>which is necessary, so that XEP seems dead unless there is a way to 
>get XEP to recognize these functions. I'll look around for an XEP list.

http://xep.xattic.com/lists/xep-support/
mailto:xep-support-request@renderx.com?body=subscribe

>Thanks again, even though my problem is still unresolved.

Your original post wasn't clear enough for me to understand, even 
with your bit at the bottom of the message.

>>On Fri, Oct 30 2009 18:19:34 +0000, mark@knihtisk.org wrote:
>>>I am compiling a journal index. The output is generated via XSLT and
>>>XSL-FO. I have been looking for a way to deal with widows and orphans
>>>in XSL-FO, but all of the information I have found seems to be focused
>>>on breaks *within* an rather than *between*
>>>differents. My problem is that I only want to end a page if
>>>the processor has started rendering (or has completed rendering), a
>>>specific ,

That to me sounds like a keep constraint, which correlates with your 
own discovery of the "within-page":

   keep.together.within-column="always"

... is what I tell my XSL-FO students to use.  If you have only one 
column then you get the page behaviour you need, and if you have more 
than one column then you don't get a column break in the middle.

Note that you should not do:

   keep.together="always"

... because that sets the property at the line level as well.

I hope this helps.

. . . . . . . . . . Ken

p.s. for readers: one seat remains open for Monday's XSLT/XQuery 
class in DC ... more room available for the XSL-FO class starting on the 9th:

   http://www.CraneSoftwrights.com/index.html#Crane200910IAD



--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  http://www.CraneSoftwrights.com/f/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/f/
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/f/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: 
--~--


Re: [xsl] Widows and orphans in XSL-FO - 10/30/2009 10:33:00 PM
Hi Tony,
I looked at that function and am not sure if it would be useful or not. 
However, a Google search on it did lead me to within-page. The article 
warned that FOP (which I am using) did not support this, but found me a free 
download of XEP.
When I tried to run my stylesheet, XEP failed on the current-time() function 
from XSLT. I could get along without that, but then it failed on the 
base-uri(/) function, which is necessary, so that XEP seems dead unless 
there is a way to get XEP to recognize these functions. I'll look around for 
an XEP list.

Thanks again, even though my problem is still unresolved.
Mark

--------------------------------------------------
From: "Tony Graham" 
Sent: Friday, October 30, 2009 12:38 PM
To: 
Subject: Re: [xsl] Widows and orphans in XSL-FO

> On Fri, Oct 30 2009 18:19:34 +0000, mark@knihtisk.org wrote:
>> I am compiling a journal index. The output is generated via XSLT and
>> XSL-FO. I have been looking for a way to deal with widows and orphans
>> in XSL-FO, but all of the information I have found seems to be focused
>> on breaks *within* an rather than *between*
>> differents. My problem is that I only want to end a page if
>> the processor has started rendering (or has completed rendering), a
>> specific , one containing the content from an 
>> element.  Is there a mechanism for forcing a page to end with, or
>> within, a specific type?
>
> Have you looked at break-after [1], specifically, break-after="page"?
>
> Regards,
>
>
> Tony Graham                         Tony.Graham@MenteithConsulting.com
> Director                                  W3C XSL FO SG Invited Expert
> Menteith Consulting Ltd                               XML Guild member
> XML, XSL and XSLT consulting, programming and training
> Registered Office: 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
> Registered in Ireland - No. 428599   http://www.menteithconsulting.com
>  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
> xmlroff XSL Formatter                               http://xmlroff.org
> xslide Emacs mode                  http://www.menteith.com/wiki/xslide
> Unicode: A Primer                               urn:isbn:0-7645-4625-2
>
> [1] http://www.w3.org/TR/xsl11/#break-after
>
> --~------------------------------------------------------------------
> 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] Widows and orphans in XSL-FO - 10/30/2009 6:20:00 PM
Hello all,
I am compiling a journal index. The output is generated via XSLT and XSL-FO. 
I have been looking for a way to deal with widows and orphans in XSL-FO, but 
all of the information I have found seems to be focused on breaks *within* 
an rather than *between* differents. My problem is that 
I only want to end a page if the processor has started rendering (or has 
completed rendering), a specific , one containing the content from 
an  element.  Is there a mechanism for forcing a page to end with, 
or within, a specific type?

The index itself may be seen at 
http://www.knihtisk.org/library/specialist/index.htm.

Thanks,
Mark

Pictures explain better than words. As you might imagine, the actual XSL-FO 
style sheet is quite complex. Thus, rather than supplying the style sheet 
itself, the seven possible problem configurations are shown below. Each of 
the five elements is rendered in its own :

 page 1
 page 2

 page 1
 page 2

 page 1
 page 1
    page 2

 page 1
 page 1
 page 2

 page 1
 page 1
 page 1
    page 2

 page 1
 page 1
 page 1
 Page 2

 page 1
 page 1
 page 1
 page 1
    page 2



 



--~------------------------------------------------------------------
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] axis specifier issue - 10/30/2009 5:21:00 PM
a kusa wrote:
> What I want is that any  element that is below  and before
> to be pushed under .

With XSLT 2.0 you can achieve that as follows:



   
     
       
     
   

   
     
       
     
   

   
     
       
     
   



-- 

	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: 
--~--


Re: [xsl] axis specifier issue - 10/30/2009 3:42:00 PM
What I want is that any  element that is below  and before
to be pushed under .



On 10/29/09, David Carlisle  wrote:
>
> You are ot giving us many clues as to what criterion you are trying to
> encode which decides which notes to move, but note the
> preeeeceding-sibling axis selcts all preceding siblings, perhaps you
> just want the closest, so that's
>
> preceding-sibling::*[1]
> or, if you just want the closest sibling if it is a note,
> preceding-sibling*[1][self::note]
>
> 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] copy attributes, except some - 10/30/2009 1:41:00 PM
AC,

At 09:02 PM 10/29/2009, you wrote:
>Hi Wendell,
>
>True. The thing that still bothers me with this is that since nodes 
>and content are compared, a variable like $excepted-attributes has 
>to be defined for every attribute group, for every tree/subtree that 
>may get copied which is getting to be quite an overhead here.

Yes, certainly. My suggestion is clean only if the variable can be 
declared at the top -- that is, if @name1 attributes are always to be 
excluded. Even then, there are situations where it will be problematic.

This is the problem with posting fragments of problems to the list. 
As we have noted before (in this thread and elsewhere), without a 
complete problem spec, we can't really provide a solution. For 
example, a parameterized approach, in which $exclude-attributes would 
be passed through templates (using a tunnel parameter) and modified 
where necessary, might be another thing worth trying.

On the other hand, sometimes our waving flashlights in the dark will 
lead to an accidental insight which is at least as good, or better, 
than a solution. If that's the case here, we should call it a success.

Cheers,
Wendell



======================================================================
Wendell Piez                            mailto:wapiez@mulberrytech.com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


--~------------------------------------------------------------------
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] [ANN] XML Prague 2010 Call for Participation (CFP) - 10/30/2009 12:45:00 PM
XML Prague 2010 Call for Papers

XML Prague 2010 is now welcoming submissions for presentations on the
following topics:

   * XML lifecycle (diffing, merging, change tracking, etc.)
   * Efficiency and performance in XML (verbosity, processing, overuse)
   * Hypermedia in XML (SMIL, SVG animations)
   * Spatial data and XML (WGS84, microformats)
   * XML all the time (XRX, XQuery web applications)

All proposals will be submitted for review by a peer review panel made
up of the XML Prague Organizing Committee. Submissions will be chosen
based on interest, applicability, technical merit, and technical
correctness.

Accepted Papers will be included inside the published conference proceedings.

Authors should strive to contain original material and belong in the
topics previously listed. Submissions which can be construed as
product or service descriptions (adverts) will probably be deemed
inappropriate. Other approaches such as using case studies are welcome
but must be clearly related to conference topics.

Selected presenters must submit an full paper (on time) and give their
presentation and answer questions in English, as well as follow the
XML Prague 2010 conference guidelines.
Important Dates:

   * December 21st - End of CFP (extended abstract or full paper)
   * January 6th - Notification of acceptance/rejection of paper to authors
   * January 22nd - Final paper

How to Submit:

All submissions must be done using the conference management system
available at

https://cmt.research.microsoft.com/XML2010/

If you have never used this system before for other conferences, you
will have to sign-up first and create new account for yourself.

After logging onto conference management system you will be able to
submit your paper and edit this submission before deadline. You can
also review the status of your paper as well as review comments from
review process.

You may submit an abstract or a full paper. We recommend to provide as
much information as possible to give the reviewers the best chance to
judge your submission.
Submission Guidelines:

All submissions must be in English and paper should not exceed 15
pages in length. Papers for review can be submitted in any common
format. However, we remind people that if your paper is accepted that
we will be asking for the final version to be submitted in DocBook XML
format.

If you have any question regarding submission process please contact
Jirka Kosek at jirka.kosek@xmlprague.cz.

on behalf,
XML Prague Committee

-------------------------
Jim Fuller
http://www.xmlprague.cz



-- 
cheers, Jim

-------------------------
XML Prague
http://www.xmlprague.cz

--~------------------------------------------------------------------
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] [ANN] XML Prague 2010 and registration is now open - 10/30/2009 10:43:00 AM
[ANN] XML Prague 2010, March 13th & 14th ' Temporal XML'

XML Prague is a conference on XML for developers, markup geeks,
information managers,
and students, in its 5th year. To obtain more information or register
please visit the website

http://www.xmlprague.cz

----------------------------------------
Important Dates
----------------------------------------

* Oct 2009 - Topics Announced, Registration Opens

* Oct 2009 - Call for Papers

* March 13th & 14th 2010 - XML Prague Conference

A separate email will go out today with CFP details.

----------------------------------------
Topics
----------------------------------------

XML Prague 2010 will focus on core and emerging XML technologies with
this year's
special focus given on temporal aspects of XML.

Â  Â * XML Lifecycle (diffing, merging, change tracking, etc.)

Â  Â * Efficiency and performance in XML (verbosity, processing, overuse)

Â  Â * Hypermedia in XML (SMIL, SVG animations)

Â  Â * Spatial data and XML (WGS84, microformats)

Â  Â * XML all the time (XRX, XQuery web applications)

Special panel discussion: Editing XML (open to sponsors)

If you have any questions please email us at info@xmlprague.cz.

----------------------------------------
Pricing
----------------------------------------

* Conference Pass (25 EUR, 30 EUR on site):*
- Access to all XML Prague 2009 conference sessions (13 - 14 March).
- Coffee and light refreshments during coffee-breaks (4 times).
- A copy of conference proceedings.

* Full Pass (60 EUR):*
- All included in the Conference package,
- plus two lunches (13 - 14 March) and the social dinner (13 March).

*Social Dinner (20 EUR)*
- the social dinner (13 March) for accompanying person.

----------------------------------------
Location
----------------------------------------

The conference is held in Prague, Czech Republic.

Â Lesser Town Campus of Charles University
Â MalostranskÃ© nÃ¡mÄ›stÃ 25, Prague, Czech Republic


----------------------------------------
How to Participate
----------------------------------------

If you are planning to attend the conference and would be
interested in participating, please review the available options.

Â * Poster: Submit a 'poster' submission which if we have time may
also mean giving a 5 minute Lightening Talk.

Â * Workshops: As we have limited resources please contact
us early to discuss the possibility of holding a workshop.

Submit your ideas to ideas@xmlprague.cz

----------------------------------------
XML Prague 2009 Organizing Committee
----------------------------------------

Petr Cimprich, Unity Mobile
TomÃ¡Å¡ Kaiser, University of West Bohemia, Pilsen
Jaroslav NeÅ¡etÅ™il, Charles University, Prague
James Fuller, http://www.webcomposite.com
Jirka Kosek, xmlguru.cz & University of Economics, Prague
Mohamed Zergaoui, Innovimax
Pavel Kroh, Independent Consultant
Martin Å½Ã¡k
Vit Janota

----------------------------------------

Hope to see everyone there.

XML Prague Committee

-------------------------
Jim Fuller
XML Prague 2010
http://www.xmlprague.cz

--~------------------------------------------------------------------
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] Lookup kind of Functionality with XSL - 10/30/2009 9:40:00 AM
> 
> I have a requirement like this.
> 
> 
>     Herbert three
>     Johnny
>     
>     
>   
> 
> another piece of XML is
> 
> 
> 
> 
> 
> 
> 
> while reading STATUS (status A), I need to look up the 
> corresponding Description ('Active').

Assuming that the  element is bound to variable $emp, and the
 element to variable $table, and that there is a  start tag
carelessly omitted from the sample XML, you want

$table/ROW[COLUMN[@name='DESCR'][.=$emp/COLUMN[@name='STATUS']]/COLUMN[@NAME
='DESCR']

As I suggested in a response to a previous post, this would all become a lot
easier if you first transform this verbose representation of your data into
something cleaner, like


  
  ...


so the logic would become

$statusCodes/status[@code=$emp/status]/@description

Regards,

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


--~------------------------------------------------------------------
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] Lookup kind of Functionality with XSL - 10/30/2009 8:57:00 AM
you can use the XSLT 'document' function to achieve this (ref,
http://www.w3.org/TR/xslt#document).

On Fri, Oct 30, 2009 at 2:20 PM, Anil Kumar Veeramalli
 wrote:
> Hi,
>
> I have a requirement like this.
>
> 
> Â  Herbert three
> Â  Johnny
> Â  
> Â  
> Â 
>
> another piece of XML is
> 
> 
> 
> 
> 
>
>
> while reading STATUS (status A), I need to look up the corresponding
> Description ('Active').
>
> I will have to use only XSL 1.0 version, javascript and XALAN (if required)
>
> how can I achieve this in XSL.
>
> Thanks,
> Anil



-- 
Regards,
Mukul Gandhi

--~------------------------------------------------------------------
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] Lookup kind of Functionality with XSL - 10/30/2009 8:51:00 AM
Hi,

I have a requirement like this.


    Herbert three
    Johnny
    
    
  

another piece of XML is







while reading STATUS (status A), I need to look up the corresponding 
Description ('Active').

I will have to use only XSL 1.0 version, javascript and XALAN (if required)

how can I achieve this in XSL.

Thanks,
Anil



--~------------------------------------------------------------------
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] copy attributes, except some - 10/30/2009 1:03:00 AM
Hi Wendell,

True. The thing that still bothers me with this is that since nodes and 
content are compared, a variable like $excepted-attributes has to be 
defined for every attribute group, for every tree/subtree that may get 
copied which is getting to be quite an overhead here.  The situation is 
more or less the same for the attribute() approach. Comparing attribute 
names is really what I require but is trickier in a namespace safe way.

Consequently, by first declaring a variable with a "dummy" set of 
attributes to exclude, like
    
I can now declare:
    
and later use:
    
on as many trees as I need, bringing the variable overhead down to two 
per excepted attribute set, independently of the number of tree/subtree 
that need copying, which is a lot in this case.

Also note that the example here copies attributes from the context node 
which implies, especially with many trees/subtrees and many excluded 
attributes that you would want to use a lot of  elements to set those context nodes.  
With an attribute name-based approach one can also spare most of these 
context setting instructions, just simply using the tree variable 
reference once, per tree. Again, it seems, quite a saving in a setting 
with many trees/subtrees.

The solution still does not seem perfectly elegant, especially as it is 
a little twisted, but it seems like the best possible, and it works.

Mind you, in a context where elements can have dynamic attribute sets 
from a wide potential range, from multiple namespaces, which I think 
should be casual with XML, it may be interesting to consider how this 
could be made more elegant.

It works for now and I thank you, and everyone who contributed, for the 
insight.

Cheers,
ac


> ac,
>
> At 02:37 AM 10/29/2009, you wrote:
>> Hi,
>>
>> Sorry for noise again, but David did provide a possibly better option 
>> as in:
>> 
>
> Also (syntax errors aside), if you wanted to drive this from the top:
>
> 
>
> ... and then ...
>
> 
>
> Cheers,
> Wendell
>
>
> ======================================================================
> Wendell Piez                            mailto:wapiez@mulberrytech.com
> Mulberry Technologies, Inc.                http://www.mulberrytech.com
> 17 West Jefferson Street                    Direct Phone: 301/315-9635
> Suite 207                                          Phone: 301/315-9631
> Rockville, MD  20850                                 Fax: 301/315-8285
> ----------------------------------------------------------------------
>   Mulberry Technologies: A Consultancy Specializing in SGML and XML
> ======================================================================
>
>
> --~------------------------------------------------------------------
> 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] axis specifier issue - 10/29/2009 11:30:00 PM
You are ot giving us many clues as to what criterion you are trying to
encode which decides which notes to move, but note the
preeeeceding-sibling axis selcts all preceding siblings, perhaps you
just want the closest, so that's

preceding-sibling::*[1]
or, if you just want the closest sibling if it is a note,
preceding-sibling*[1][self::note]

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] axis specifier issue - 10/29/2009 10:31:00 PM
Hi:

I have an input file like this:


this is a sample note
sample desc
note at the end of desc 
      
           sample text
      


Now I want to transform this so that the  note at the end
of desc  comes right under .

So:


this is a sample note
sample desc
      
note at the end of desc 
           sample text
      


But when I use preceding-sibling, it pulls this is a sample note
into  as well.

Can anybody help me here?

Thanks in advance.

--~------------------------------------------------------------------
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] reading a text file and putting out an xml file using xslt - 10/29/2009 10:27:00 PM
Thanks! I will take a look at the documentation again.

On 10/29/09, David Carlisle  wrote:
>
> > Can you please tell me what I am doing wrong here?
>
> > > a directory with all the xml files and images.
>
> I think you'll find saxon's directory input feature applies teh
> stylesheet to all the files in teh directory, so you'll get xml parse
> errors on the images.
>
> Instead of doing that you can use the collection() function and just select the xml
> files with  a URL ending with directory-name/?select=*.xml
> see the saxon documentation.
>
> 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] copy attributes, except some - 10/29/2009 9:51:00 PM
ac,

At 02:37 AM 10/29/2009, you wrote:
>Hi,
>
>Sorry for noise again, but David did provide a possibly better option as in:
>

Also (syntax errors aside), if you wanted to drive this from the top:



... and then ...



Cheers,
Wendell


======================================================================
Wendell Piez                            mailto:wapiez@mulberrytech.com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


--~------------------------------------------------------------------
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: Re: [xsl] Create word elements from a string - 10/29/2009 9:51:00 PM
Larry,

At 02:58 AM 10/29/2009, you wrote:
>Thanks for the help. I was able to get something working in XSL 1.0
>using what you all provided. Although I think it's time to switch to
>2.0 with tokenize!
>
>I did run into a problem with:
>
>
>
>The test always returns true even when I only have one word in the
>text. I don't particularly understand why, but when I change it to
>this, everything works fine:
>
>
>
>Why does it return true when normalize-space is not there? I would
>think with only one word, there wouldn't be any spaces.

Single words can, of course, be preceded or followed by spaces, and 
remain single words. Could this have been the case?

normalize-space() will strip leading and trailing whitespace, as well 
as collapsing runs of spaces within a string.

Cheers,
Wendell



======================================================================
Wendell Piez                            mailto:wapiez@mulberrytech.com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


--~------------------------------------------------------------------
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] [ANN] Altova announces v2010 of the MissionKit tool suite - 10/29/2009 9:09:00 PM
Altova is pleased to announce general availability version 2010 of its
MissionKit XML, database, and UML tools. v2010 is our MOST WANTED
release and includes over 70 new customer-requested features. Just a few
of these include: 

* Support for WSDL 2.0, JSON, and SysML technologies
* New stylesheet design paradigm with advanced support for electronic
form design
* Enhanced XBRL functionality
* Database schema comparison
* And much more 

More info and screenshots are available at
 

Download a fully functional free trial at
 

Best regards,
Liz

Liz Andrews
Technical Marketing Manager
Altova, Inc.
www.altova.com


This e-mail and any attachments are intended only for the person/entity
to which they are addressed and may contain confidential and/or
privileged material. If you received this in error, please notify the
sender and delete the message.



--~------------------------------------------------------------------
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] reading a text file and putting out an xml file using xslt - 10/29/2009 5:37:00 PM
> Can you please tell me what I am doing wrong here?

> > a directory with all the xml files and images.

I think you'll find saxon's directory input feature applies teh
stylesheet to all the files in teh directory, so you'll get xml parse
errors on the images.

Instead of doing that you can use the collection() function and just select the xml
files with  a URL ending with directory-name/?select=*.xml
see the saxon documentation.

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] reading a text file and putting out an xml file using xslt - 10/29/2009 5:33:00 PM
> 
> Can someone please let me know if I am doing something wrong here?

This isn't an XSLT problem, it's an XML problem. Saxon is telling you quite
clearly that the error comes from the XML parser.

> > SXXP0003: Error reported by XML parser: Content is not allowed in
prolog.
> > While processing bk1-im1.tif: Run-time errors were reported

It looks as if the XML parser is trying to parse the content of bk1-im1.tif
as XML and failing. Perhaps that's because you have an entity reference
&im1; somewhere in your source - that's not allowed with unparsed entities.
However, I can only speculate.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 
> 
> On Wed, Oct 28, 2009 at 2:23 PM, a kusa  wrote:
> > Thank you. This worked.
> >
> > But I have anther problem. I am applying a transformation 
> style sheets 
> > to another set of xml files to generate another xml output.
> > These files have images as entities in beginning:
> >
> >  >  > Facsimile//EN' >  
> >  ]>
> >


--~------------------------------------------------------------------
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] reading a text file and putting out an xml file using xslt - 10/29/2009 5:26:00 PM
Can someone please let me know if I am doing something wrong here?

On Wed, Oct 28, 2009 at 2:23 PM, a kusa  wrote:
> Thank you. This worked.
>
> But I have anther problem. I am applying a transformation style sheets
> to another set of xml files to generate another xml output.
> These files have images as entities in beginning:
>
>  
> 
> 
> ]>
>
> I am using saxon9 to run this in a batch mode. So my source points to
> a directory with all the xml files and images.
> java net.sf.saxon.Transform -s:c:\sampleset -xsl:test.xsl -o:c:\output
>
> But I get this error on running it in batch mode.
>
> SXXP0003: Error reported by XML parser: Content is not allowed in prolog.
> While processing bk1-im1.tif: Run-time errors were reported
>
> Can you please tell me what I am doing wrong here?
>
>
> On Wed, Oct 28, 2009 at 10:40 AM, Michael Kay  wrote:
>>
>>> Thank you. I have saxon9 downloaded. But I am not sure how to
>>> run a transformation on the command line for a text input.
>>> Any help?
>>>
>>
>> Typically
>>
>> java net.sf.saxon.Transform -xsl:stylesheet.xsl -it:main
>>
>> or you might want to supply the name of the unparsed text file as a
>> parameter:
>>
>> java net.sf.saxon.Transform -xsl:stylesheet.xsl -it:main input=text.xml
>>
>> with
>>
>> 
>>
>> and
>>
>> select="unparsed-text($input)"
>>
>> Regards,
>>
>> Michael Kay
>> http://www.saxonica.com/
>> http://twitter.com/michaelhkay
>>
>>
>> --~------------------------------------------------------------------
>> 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] nodes() before and after a string delimiter - 10/29/2009 11:30:00 AM
Martin,

Thanks for the quick reply and solution. This is definitely one for the toolbox.

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries

-----Original Message-----
From: Martin Honnen [mailto:Martin.Honnen@gmx.de] 
Sent: Wednesday, October 28, 2009 2:53 PM
To: xsl-list@lists.mulberrytech.com
Subject: Re: [xsl] nodes() before and after a string delimiter

Mario Madunic wrote:
> I have the following element (I'm using Saxon9 and XSLT2)
> 
> Crazing â€“ Hairline cracking of the resin, giving it an opaque, frosty appearance.
> 
> I need to break it into two halves like the following based on the â€“ (space en dash space) and only the first  â€“ (space en dash space).
> 
> 
>    Crazing
>    Hairline cracking of the resin, giving it an opaque, frosty appearance.
> 

This stylesheet



   

   
     
       
     
   

   
     
       
       
       
         
           
           
             
             
           
         
         
           
         
       
     
   



does that but I have not tested against anything but your input sample.
-- 

	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: 
--~--


--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.


--~------------------------------------------------------------------
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] nodes() before and after a string delimiter - 10/29/2009 11:29:00 AM
Michael,

Thank you very much.

This is a simple and elegant solution. I did not know that I could use substring-before and after in such a way. Guess I was stuck on the 'string' part of the function name.

Once again thanks.

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries

-----Original Message-----
From: Michael Kay [mailto:mike@saxonica.com] 
Sent: Wednesday, October 28, 2009 4:57 PM
To: xsl-list@lists.mulberrytech.com
Subject: RE: [xsl] nodes() before and after a string delimiter

First find the text node containing the dash:



Create a  element containing all nodes preceding this text node, plus
the part of the text node before the dash:


   
   


Create a  element containing everything that follows the dash:


    
   


Regards,

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

> -----Original Message-----
> From: Mario Madunic [mailto:Mario_Madunic@newflyer.com] 
> Sent: 28 October 2009 19:25
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] nodes() before and after a string delimiter
> 
> I have the following element (I'm using Saxon9 and XSLT2)
> 
> Crazing - Hairline cracking of the resin, giving it an 
> opaque, frosty appearance.
> 
> I need to break it into two halves like the following based 
> on the - (space en dash space) and only the first  - (space 
> en dash space).
> 
> 
>    Crazing
>    Hairline cracking of the resin, giving it an 
> opaque, frosty appearance. 
> 
> I'm used to breaking strings on delimiters and not worrying 
> about any inline elements, but his time the inline elements matter. 
> Is this a for-each-group solution? Break it into two 
> for-each-groups and in the first test for a 
> following-sibling[. = '-'] and the second test for the 
> following-sibling[. = '-']. 
> 
> No need to apply templates at this point a copy-of will suffice.
> 
> Any insight would be appreciated.
> 
> Thanks
> 
> Marijan (Mario) Madunic
> Publishing Specialist
> New Flyer Industries
> 
> --------------------------------------------------------------------
> Please consider the environment before printing this e-mail.
> 
> CONFIDENTIALITY STATEMENT: This communication (and  any and 
> all information or material transmitted with this 
> communication) is confidential, may be privileged and is 
> intended only for the use of the intended recipient. If you 
> are not the intended recipient, any review, retransmission, 
> circulation, distribution, reproduction, conversion to hard 
> copy, copying or other use of this communication, information 
> or material is strictly prohibited and may be illegal. If you 
> received this communication in error or if it is forwarded to 
> you without the express authorization of New Flyer, please 
> notify us immediately by telephone or by return email and 
> permanently delete the communication, information and 
> material from any computer, disk drive, diskette or other 
> storage device or media. Thank you.
> 
> 
> --~------------------------------------------------------------------
> 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: 
--~--


--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.


--~------------------------------------------------------------------
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] convert String to date format and sort - 10/29/2009 9:42:00 AM
Hi,

1) my current date format is 28-Oct-1987(dd-mmm-yyyy), want to convert it yyyy-mm-dd format.
2) sort the dates

XML code:

John


John


John


xslt 
code to sort by date:


 
 
 




sorting this way is good approach or do we have any better approach.



Thanks,
Anil



--~------------------------------------------------------------------
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] attribute based sorting - 10/29/2009 9:16:00 AM
> 
>  
> 28-Oct-1987
> 
> date format will be in DD-MMM-DDDD, what is the good approach 
> to sort this kind of dates.
> 

This seems to be a classic case where you should be using a pipeline
architecture: a series of transformations. First transform your data to
"clean" XML, that is, to

1987-10-27

and then the real processing all becomes much easier. The advantage of
splitting the transformation into phases is that the "clean-up" phase is
reusable, and independent of the subsequent processing you want to perform.

Regards,

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


--~------------------------------------------------------------------
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: Re: [xsl] Create word elements from a string - 10/29/2009 8:45:00 AM
On Thu, Oct 29, 2009 at 12:28 PM, Larry Hayashi  wrote:
> I did run into a problem with:
>
> 
>
> The test always returns true even when I only have one word in the
> text. I don't particularly understand why, but when I change it to
> this, everything works fine:
>
> 

Did you run this modified syntax, with the same input you specified
earlier (i.e, Jill ran up the hill.)?
If your input was this (i.e, text node within  as mentioned
above), then I think normalize-space is not needed.

> Why does it return true when normalize-space is not there? I would
> think with only one word, there wouldn't be any spaces.

If you can post the input with which, you ran your stylesheet it would
be helpful to find an answer to your question. It would also be
helpful, if you mention the XSLT engine you are using.



-- 
Regards,
Mukul Gandhi

--~------------------------------------------------------------------
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] Is a XSLT 2 to 1 transform possible? - 10/29/2009 8:40:00 AM
Ok, thanks :)

2009/10/29 Michael Kay :
>> Out of curiosity, could a XSLT 1.0 stylesheet be used to
>> convert a XSLT 2.0 stylesheet to an equivalent XSLT 1.0 stylesheet?
>>
>
> XSLT 1.0 is Turing-complete so the theoretical answer is yes. (With a
> proviso that you would need to call out to extensions to handle a few things
> like unparsed-text() and xsl:result-document).
>
> The practical answer, given the number of man-years that I imagine are
> available to you, is no. Can you imagine what a regular expression engine
> would look like written in XSLT 1.0 code?
>
> Regards,
>
> Michael Kay
> http://www.saxonica.com/
> http://twitter.com/michaelhkay
>
>
> --~------------------------------------------------------------------
> 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] attribute based sorting - 10/29/2009 8:38:00 AM
Thanks a lot  Michael. Its working as expected..
I have another question, its an extension to that.

 
28-Oct-1987

date format will be in DD-MMM-DDDD, what is the good approach to sort this kind of dates.


Thanks,
Anil

Michael Kay wrote:
> 
>
> Regards,
>
> Michael Kay
> http://www.saxonica.com/
> http://twitter.com/michaelhkay  
>
>   
>> -----Original Message-----
>> From: Anil Kumar Veeramalli [mailto:anil.v@frescoinformatics.com] 
>> Sent: 29 October 2009 06:33
>> To: xsl-list@lists.mulberrytech.com
>> Subject: [xsl] attribute based sorting 
>>
>> Hi,
>>
>> I wanted to sort based on salary. please suggest me on 
>> this.can you give me some sample code.
>> my sample xml file look like this
>> 
>>     95000
>>   
>> with multiple employees.
>>
>> I want to sort based on Salary attribute. instead of > name="salary">95000 this , 1000 
>> with this I am able to sort it out  like this > select="salary" *data-type="number"*/>
>>
>>
>> Please please help out on this.
>>
>> Thanks,
>> Anil
>>
>>
>> --~------------------------------------------------------------------
>> 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-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] Is a XSLT 2 to 1 transform possible? - 10/29/2009 8:36:00 AM
> Out of curiosity, could a XSLT 1.0 stylesheet be used to 
> convert a XSLT 2.0 stylesheet to an equivalent XSLT 1.0 stylesheet?
> 

XSLT 1.0 is Turing-complete so the theoretical answer is yes. (With a
proviso that you would need to call out to extensions to handle a few things
like unparsed-text() and xsl:result-document).

The practical answer, given the number of man-years that I imagine are
available to you, is no. Can you imagine what a regular expression engine
would look like written in XSLT 1.0 code?

Regards,

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


--~------------------------------------------------------------------
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] attribute based sorting - 10/29/2009 8:30:00 AM


Regards,

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

> -----Original Message-----
> From: Anil Kumar Veeramalli [mailto:anil.v@frescoinformatics.com] 
> Sent: 29 October 2009 06:33
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] attribute based sorting 
> 
> Hi,
> 
> I wanted to sort based on salary. please suggest me on 
> this.can you give me some sample code.
> my sample xml file look like this
> 
>     95000
>   
> with multiple employees.
> 
> I want to sort based on Salary attribute. instead of  name="salary">95000 this , 1000 
> with this I am able to sort it out  like this  select="salary" *data-type="number"*/>
> 
> 
> Please please help out on this.
> 
> Thanks,
> Anil
> 
> 
> --~------------------------------------------------------------------
> 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] attribute based sorting - 10/29/2009 8:28:00 AM
I am using 

Please help me out this problem.

Thanks,
Anil
Anil Kumar Veeramalli wrote:
> Let me explain my problem
>
> My XML format will look like this.
>    95000  NAME="NAME">ANIL 
>    92000  NAME="NAME">Kumar .....
>
> I wanted to sort this based on SALARY.
>
> Approaches I tried
> 1)               select="COLUMN/SALARY" data-type="number"/>
>                test="@NAME='SALARY'">
>      
> with this I am not able to sort
>
> with the above code, sort is not happening.
>
>
> Thanks,
> Anil
>
>
> Michael Müller-Hillebrand wrote:
>> Am 29.10.2009 um 09:00 schrieb Anil Kumar Veeramalli:
>>
>>> thanks Michael,
>>>
>>> I tried that option too,......its not working.
>>
>> Anil, apparently you gave us not enough information. "not working" is 
>> not useful. What is your input, how does your XSL look like so far 
>> (all stripped down to the absolute minimum), what is the expected 
>> output, what output do you get.
>>
>> As mentioned previously, preparing such a test case for many users 
>> (myself included) solves the problem.
>>
>> Best regards,
>>
>> - Michael
>>
>>
>> -- 
>> _______________________________________________________________
>> Michael Müller-Hillebrand: Dokumentations-Technologie
>> Adobe Certified Expert, FrameMaker
>> Lösungen und Training, FrameScript, XML/XSL, Unicode
>> Blog: http://cap-studio.de/ - Tel. +49 (9131) 28747
>>
>>
>>
>>
>>
>>
>> --~------------------------------------------------------------------
>> 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-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] Is a XSLT 2 to 1 transform possible? - 10/29/2009 8:26:00 AM
Out of curiosity, could a XSLT 1.0 stylesheet be used to convert a
XSLT 2.0 stylesheet to an equivalent XSLT 1.0 stylesheet?

-Jostein

--~------------------------------------------------------------------
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] attribute based sorting - 10/29/2009 8:14:00 AM
Let me explain my problem

My XML format will look like this.
   95000 ANIL 
   92000 Kumar .....

I wanted to sort this based on SALARY.

Approaches I tried
1)       
        
        
             
                  
        
      
with this I am not able to sort

with the above code, sort is not happening.


Thanks,
Anil


Michael Müller-Hillebrand wrote:
> Am 29.10.2009 um 09:00 schrieb Anil Kumar Veeramalli:
>
>> thanks Michael,
>>
>> I tried that option too,......its not working.
>
> Anil, apparently you gave us not enough information. "not working" is 
> not useful. What is your input, how does your XSL look like so far 
> (all stripped down to the absolute minimum), what is the expected 
> output, what output do you get.
>
> As mentioned previously, preparing such a test case for many users 
> (myself included) solves the problem.
>
> Best regards,
>
> - Michael
>
>
> -- 
> _______________________________________________________________
> Michael Müller-Hillebrand: Dokumentations-Technologie
> Adobe Certified Expert, FrameMaker
> Lösungen und Training, FrameScript, XML/XSL, Unicode
> Blog: http://cap-studio.de/ - Tel. +49 (9131) 28747
>
>
>
>
>
>
> --~------------------------------------------------------------------
> 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] attribute based sorting - 10/29/2009 8:07:00 AM
Am 29.10.2009 um 09:00 schrieb Anil Kumar Veeramalli:

> thanks Michael,
>
> I tried that option too,......its not working.

Anil, apparently you gave us not enough information. "not working" is  
not useful. What is your input, how does your XSL look like so far  
(all stripped down to the absolute minimum), what is the expected  
output, what output do you get.

As mentioned previously, preparing such a test case for many users  
(myself included) solves the problem.

Best regards,

- Michael


--
_______________________________________________________________
Michael Müller-Hillebrand: Dokumentations-Technologie
Adobe Certified Expert, FrameMaker
Lösungen und Training, FrameScript, XML/XSL, Unicode
Blog: http://cap-studio.de/ - Tel. +49 (9131) 28747






--~------------------------------------------------------------------
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] attribute based sorting - 10/29/2009 8:01:00 AM
thanks Michael,

I tried that option too,......its not working.

Thanks,
Anil

if the XML format is
Michael Müller-Hillebrand wrote:
> Am 29.10.2009 um 07:33 schrieb Anil Kumar Veeramalli:
>
>> I wanted to sort based on salary. please suggest me on this.can you 
>> give me some sample code.
>> my sample xml file look like this 
>>   95000
>> 
>> with multiple employees.
>>
>> I want to sort based on Salary attribute. instead of > name="salary">95000 this , 1000 with this I 
>> am able to sort it out  like this
>> 
>
> I assume you process  maybe in a xsl:for-each loop. The try:
>
> 
>
> - Michael
>
> -- 
> _______________________________________________________________
> Michael Müller-Hillebrand: Dokumentations-Technologie
> Adobe Certified Expert, FrameMaker
> Lösungen und Training, FrameScript, XML/XSL, Unicode
> Blog: http://cap-studio.de/ - Tel. +49 (9131) 28747
>
>
>
>
>
>
> --~------------------------------------------------------------------
> 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] attribute based sorting - 10/29/2009 7:58:00 AM
Am 29.10.2009 um 07:33 schrieb Anil Kumar Veeramalli:

> I wanted to sort based on salary. please suggest me on this.can you  
> give me some sample code.
> my sample xml file look like this 
>   95000
> 
> with multiple employees.
>
> I want to sort based on Salary attribute. instead of  name="salary">95000 this , 1000 with this  
> I am able to sort it out  like this
> 

I assume you process  maybe in a xsl:for-each loop. The try:



- Michael

--
_______________________________________________________________
Michael Müller-Hillebrand: Dokumentations-Technologie
Adobe Certified Expert, FrameMaker
Lösungen und Training, FrameScript, XML/XSL, Unicode
Blog: http://cap-studio.de/ - Tel. +49 (9131) 28747






--~------------------------------------------------------------------
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: Re: [xsl] Create word elements from a string - 10/29/2009 6:59:00 AM
Thanks for the help. I was able to get something working in XSL 1.0
using what you all provided. Although I think it's time to switch to
2.0 with tokenize!

I did run into a problem with:



The test always returns true even when I only have one word in the
text. I don't particularly understand why, but when I change it to
this, everything works fine:



Why does it return true when normalize-space is not there? I would
think with only one word, there wouldn't be any spaces.

Larry

--~------------------------------------------------------------------
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] copy attributes, except some - 10/29/2009 6:38:00 AM
Hi,

Sorry for noise again, but David did provide a possibly better option as in:


Thanks,
ac




Hi,

In XSLT 2.0, assuming that the $excepted-attributes variable is not used
anywhere else, and apart from also using an attribute-set in defining
the $excepted-attributes variable value xx element, is there a better
way to copy all attributes except some specific ones, in a namespace
safe way, rather than:



Thank you,
ac



--~------------------------------------------------------------------
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] attribute based sorting - 10/29/2009 6:34:00 AM
Hi,

I wanted to sort based on salary. please suggest me on this.can you give 
me some sample code.
my sample xml file look like this 

    95000
  
with multiple employees.

I want to sort based on Salary attribute. instead of 95000 this , 1000 with this I am 
able to sort it out  like this



Please please help out on this.

Thanks,
Anil


--~------------------------------------------------------------------
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] mailing list - 10/29/2009 6:30:00 AM
mailing list


--~------------------------------------------------------------------
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] copy attributes, except some - 10/29/2009 6:06:00 AM
Hi,

In XSLT 2.0, assuming that the $excepted-attributes variable is not used 
anywhere else, and apart from also using an attribute-set in defining 
the $excepted-attributes variable value xx element, is there a better 
way to copy all attributes except some specific ones, in a namespace 
safe way, rather than:



Thank you,
ac


--~------------------------------------------------------------------
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] Create word elements from a string - 10/29/2009 4:41:00 AM
Here's another 1.0 stylesheet (Dimitre, gave you one):


				
    				
				
    
       
	   
	      
	   
       
   

   
      	
	  
	    
	       
		  
	       
	       
		   
	       
	    
	    
	       
		   
	       
	    
	  
    



This stylesheet implements tokenizing algorithm from scratch (and also
with a limitation, that tokenizing delimiter can be a single ' '
character). If you can use XSLT 2.0, you might prefer Ken's solution,
as XPath 2.0 has native tokenizing function. XPath 2.0 tokenizing
function allows you to, use say a regular expression specifier '\s+'
as a tokenizing delimiter.

On Thu, Oct 29, 2009 at 2:14 AM, Larry Hayashi  wrote:
> Is there a function in XSLT 1.1 that will extract words from a string?
> I'd like to be able to take Jill ran up the hill. and get
> the following:
>
> 
> Â Jill
> Â ran
> Â up
> Â the
> Â hill.
> 
>
> Thanks,
> Larry



-- 
Regards,
Mukul Gandhi

--~------------------------------------------------------------------
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] nodes() before and after a string delimiter - 10/28/2009 9:58:00 PM
First find the text node containing the dash:



Create a  element containing all nodes preceding this text node, plus
the part of the text node before the dash:


   
   


Create a  element containing everything that follows the dash:


    
   


Regards,

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

> -----Original Message-----
> From: Mario Madunic [mailto:Mario_Madunic@newflyer.com] 
> Sent: 28 October 2009 19:25
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] nodes() before and after a string delimiter
> 
> I have the following element (I'm using Saxon9 and XSLT2)
> 
> Crazing - Hairline cracking of the resin, giving it an 
> opaque, frosty appearance.
> 
> I need to break it into two halves like the following based 
> on the - (space en dash space) and only the first  - (space 
> en dash space).
> 
> 
>    Crazing
>    Hairline cracking of the resin, giving it an 
> opaque, frosty appearance. 
> 
> I'm used to breaking strings on delimiters and not worrying 
> about any inline elements, but his time the inline elements matter. 
> Is this a for-each-group solution? Break it into two 
> for-each-groups and in the first test for a 
> following-sibling[. = '-'] and the second test for the 
> following-sibling[. = '-']. 
> 
> No need to apply templates at this point a copy-of will suffice.
> 
> Any insight would be appreciated.
> 
> Thanks
> 
> Marijan (Mario) Madunic
> Publishing Specialist
> New Flyer Industries
> 
> --------------------------------------------------------------------
> Please consider the environment before printing this e-mail.
> 
> CONFIDENTIALITY STATEMENT: This communication (and  any and 
> all information or material transmitted with this 
> communication) is confidential, may be privileged and is 
> intended only for the use of the intended recipient. If you 
> are not the intended recipient, any review, retransmission, 
> circulation, distribution, reproduction, conversion to hard 
> copy, copying or other use of this communication, information 
> or material is strictly prohibited and may be illegal. If you 
> received this communication in error or if it is forwarded to 
> you without the express authorization of New Flyer, please 
> notify us immediately by telephone or by return email and 
> permanently delete the communication, information and 
> material from any computer, disk drive, diskette or other 
> storage device or media. Thank you.
> 
> 
> --~------------------------------------------------------------------
> 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] Create word elements from a string - 10/28/2009 9:11:00 PM
You can use the str-split-to-words template of FXSL 1,x

Here is an example of using it:




   

   

    
      
        
          
          
        
      

      
    

    
      
    




When applied on the following XML document:

Use FXSL to do this

the result is:

1 Use
2 FXSL
3 to
4 do
5 this


-- 
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play




On Wed, Oct 28, 2009 at 1:44 PM, Larry Hayashi  wrote:
> Is there a function in XSLT 1.1 that will extract words from a string?
> I'd like to be able to take Jill ran up the hill. and get
> the following:
>
> 
> Â Jill
> Â ran
> Â up
> Â the
> Â hill.
> 
>
> Thanks,
> Larry
>
> --~------------------------------------------------------------------
> 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] Create word elements from a string - 10/28/2009 8:52:00 PM
At 2009-10-28 13:44 -0700, Larry Hayashi wrote:
>Is there a function in XSLT 1.1

XSLT 1.1 was formally abandoned in August 2001 and should not be used 
... read the notice in the status section of this document:

   http://www.w3.org/TR/2001/WD-xslt11-20010824/

>that will extract words from a string?
>I'd like to be able to take Jill ran up the hill. and get
>the following:
>
>
>   Jill
>   ran
>   up
>   the
>   hill.
>

In XSLT 2.0 you can use tokenize().

I hope this helps.

. . . . . . . . . . . Ken

T:\ftemp>type larry.xsl






   
     
       
         
       
     
   




T:\ftemp>xslt2 larry.xsl larry.xsl con


    Jill
    ran
    up
    the
    hill.

T:\ftemp>

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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] Create word elements from a string - 10/28/2009 8:45:00 PM
Is there a function in XSLT 1.1 that will extract words from a string?
I'd like to be able to take Jill ran up the hill. and get
the following:


  Jill
  ran
  up
  the
  hill.


Thanks,
Larry

--~------------------------------------------------------------------
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] nodes() before and after a string delimiter - 10/28/2009 7:53:00 PM
Mario Madunic wrote:
> I have the following element (I'm using Saxon9 and XSLT2)
> 
> Crazing â€“ Hairline cracking of the resin, giving it an opaque, frosty appearance.
> 
> I need to break it into two halves like the following based on the â€“ (space en dash space) and only the first  â€“ (space en dash space).
> 
> 
>    Crazing
>    Hairline cracking of the resin, giving it an opaque, frosty appearance.
> 

This stylesheet



   

   
     
       
     
   

   
     
       
       
       
         
           
           
             
             
           
         
         
           
         
       
     
   



does that but I have not tested against anything but your input sample.
-- 

	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] nodes() before and after a string delimiter - 10/28/2009 7:25:00 PM
I have the following element (I'm using Saxon9 and XSLT2)

Crazing â€“ Hairline cracking of the resin, giving it an opaque, frosty appearance.

I need to break it into two halves like the following based on the â€“ (space en dash space) and only the first  â€“ (space en dash space).


   Crazing
   Hairline cracking of the resin, giving it an opaque, frosty appearance.


Iâ€™m used to breaking strings on delimiters and not worrying about any inline elements, but his time the inline elements matter. 
Is this a for-each-group solution? Break it into two for-each-groups and in the first test for a following-sibling[. = 'â€“'] and the second test for the following-sibling[. = 'â€“']. 

No need to apply templates at this point a copy-of will suffice.

Any insight would be appreciated.

Thanks

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries

--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.


--~------------------------------------------------------------------
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] reading a text file and putting out an xml file using xslt - 10/28/2009 7:24:00 PM
Thank you. This worked.

But I have anther problem. I am applying a transformation style sheets
to another set of xml files to generate another xml output.
These files have images as entities in beginning:




]>

I am using saxon9 to run this in a batch mode. So my source points to
a directory with all the xml files and images.
java net.sf.saxon.Transform -s:c:\sampleset -xsl:test.xsl -o:c:\output

But I get this error on running it in batch mode.

SXXP0003: Error reported by XML parser: Content is not allowed in prolog.
While processing bk1-im1.tif: Run-time errors were reported

Can you please tell me what I am doing wrong here?


On Wed, Oct 28, 2009 at 10:40 AM, Michael Kay  wrote:
>
>> Thank you. I have saxon9 downloaded. But I am not sure how to
>> run a transformation on the command line for a text input.
>> Any help?
>>
>
> Typically
>
> java net.sf.saxon.Transform -xsl:stylesheet.xsl -it:main
>
> or you might want to supply the name of the unparsed text file as a
> parameter:
>
> java net.sf.saxon.Transform -xsl:stylesheet.xsl -it:main input=text.xml
>
> with
>
> 
>
> and
>
> select="unparsed-text($input)"
>
> Regards,
>
> Michael Kay
> http://www.saxonica.com/
> http://twitter.com/michaelhkay
>
>
> --~------------------------------------------------------------------
> 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] reading a text file and putting out an xml file using xslt - 10/28/2009 3:41:00 PM
> Thank you. I have saxon9 downloaded. But I am not sure how to 
> run a transformation on the command line for a text input.
> Any help?
> 

Typically

java net.sf.saxon.Transform -xsl:stylesheet.xsl -it:main

or you might want to supply the name of the unparsed text file as a
parameter:

java net.sf.saxon.Transform -xsl:stylesheet.xsl -it:main input=text.xml

with



and

select="unparsed-text($input)"

Regards,

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


--~------------------------------------------------------------------
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] reading a text file and putting out an xml file using xslt - 10/28/2009 3:13:00 PM
Thank you. I have saxon9 downloaded. But I am not sure how to run a
transformation on the command line for a text input.
Any help?

On Wed, Oct 28, 2009 at 9:30 AM, Martin Honnen  wrote:
> a kusa wrote:
>
>> I have an input file which is a text file. My output should be an XML
>> file that conforms to a schema that I already have.
>>
>> How do I do this in XSLT2.0? Can I use unparsed-text() function? Are
>> there any examples that I can look at for this?
>
> An XSLT 2.0 processor should allow you to start processing with a named
> template so in your stylesheet you would write a named template e.g.
>  
>    
>    
>  
> then you would instruct the XSLT processor to start with template named
> "main" (e.g. option -it:main in Saxon or /n main with Altova I think).
>
>
>
> --
>
>        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] reading a text file and putting out an xml file using xslt - 10/28/2009 2:30:00 PM
a kusa wrote:

> I have an input file which is a text file. My output should be an XML
> file that conforms to a schema that I already have.
> 
> How do I do this in XSLT2.0? Can I use unparsed-text() function? Are
> there any examples that I can look at for this?

An XSLT 2.0 processor should allow you to start processing with a named 
template so in your stylesheet you would write a named template e.g.
   
     
     
   
then you would instruct the XSLT processor to start with template named 
"main" (e.g. option -it:main in Saxon or /n main with Altova I think).



-- 

	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] reading a text file and putting out an xml file using xslt 2.0 - 10/28/2009 2:26:00 PM
Hi

I have an input file which is a text file. My output should be an XML
file that conforms to a schema that I already have.

How do I do this in XSLT2.0? Can I use unparsed-text() function? Are
there any examples that I can look at for this?

Thanks in advance

--~------------------------------------------------------------------
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] Saxon9, XMLSpy2009, and result-document href= - 10/28/2009 1:30:00 PM
I often make solutions that work in both AltovaXML and Saxon.

In the following example I load a file as unpassed text, and need to
get hold of the filename. To make a solution that works both in Saxon
and AltovaXML, I do this:








It is line three that is important. I do this:
(\\|/)')[last()
to make it work both in Saxon and AltovaXML.

Hope it can be of some help.

Cheers,

Jesper Tverskov
http://www.xmlplease.com

--~------------------------------------------------------------------
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] Saxon9, XMLSpy2009, and result-document href= - 10/28/2009 1:18:00 PM
Is it possible to pass a param in that defines which environment you are using, so as to define whether or not "file:///" or "" to use?

Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries

-----Original Message-----
From: Raymond Lillibridge [mailto:RLillibridge@municode.com] 
Sent: Wednesday, October 28, 2009 7:08 AM
To: 'xsl-list@lists.mulberrytech.com'
Subject: [xsl] Saxon9, XMLSpy2009, and result-document href=

All,

While developing my XSLT 2.0 transformation files using XMLSpy 2009, I was able to save output to the result-document @href value of "C:/folder/file.xml" but when using Saxon9 this doesn't work.  Saxon9 seemed to only work if I used "file:////C:/folder/file.xml" instead (Which doesn't work with XMLSpy).  

This creates a development problem.  My current solution is to change XMLSpy to use Saxon9 for it's translations, but I can't assume all developers will be using it for their development and transformations.  Is there a method of writing our XSLT transformations such that they will work properly using either Saxon9 or XMLSpy2009?  Any insight on this difference in their functionality is appreciated.


Cheers,
----------------------------------
Raymond Lillibridge
   Systems Analyst
rlillibridge@municode.com
800-262-2633
850-576-3171 x248

"It's what you read when you don't have to that determines what you will be when you can't help it."
--Oscar Wilde


--~------------------------------------------------------------------
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: 
--~--


--------------------------------------------------------------------
Please consider the environment before printing this e-mail.

CONFIDENTIALITY STATEMENT: This communication (and  any and all information or material transmitted with this communication) is confidential, may be privileged and is intended only for the use of the intended recipient. If you are not the intended recipient, any review, retransmission, circulation, distribution, reproduction, conversion to hard copy, copying or other use of this communication, information or material is strictly prohibited and may be illegal. If you received this communication in error or if it is forwarded to you without the express authorization of New Flyer, please notify us immediately by telephone or by return email and permanently delete the communication, information and material from any computer, disk drive, diskette or other storage device or media. Thank you.


--~------------------------------------------------------------------
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] Saxon9, XMLSpy2009, and result-document href= - 10/28/2009 12:17:00 PM
> 
> While developing my XSLT 2.0 transformation files using 
> XMLSpy 2009, I was able to save output to the result-document 
> @href value of "C:/folder/file.xml" but when using Saxon9 
> this doesn't work.  Saxon9 seemed to only work if I used 
> "file:////C:/folder/file.xml" instead (Which doesn't work 
> with XMLSpy).  
> 

The specification states that it must be a URI. Many products accept Windows
filenames in places where the W3C specs mandate a URI, but in general, Saxon
doesn't.

It should be file:///C:/folder/file.xml or possibly file:/C:/folder/file.xml
- but I'm not surprised you got away with ////, the specs for the file: URI
scheme are pretty fuzzy.

You might find that the most portable solution is to use a relative URI
(e.g. file.xml). This is interpreted relative to the base Output URI, which
will generally be the destination of the primary output of the
transformation.

Regards,

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


--~------------------------------------------------------------------
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] Saxon9, XMLSpy2009, and result-document href= - 10/28/2009 12:11:00 PM
try oxygenxml - oxygenxml.com

Joan Crawford  - "I, Joan Crawford, I believe in the dollar.
Everything I earn, I spend." -
http://www.brainyquote.com/quotes/authors/j/joan_crawford.html


On Wed, Oct 28, 2009 at 3:08 PM, Raymond Lillibridge
 wrote:
> All,
>
> While developing my XSLT 2.0 transformation files using XMLSpy 2009, I was able to save output to the result-document @href value of "C:/folder/file.xml" but when using Saxon9 this doesn't work. Â Saxon9 seemed to only work if I used "file:////C:/folder/file.xml" instead (Which doesn't work with XMLSpy).
>
> This creates a development problem. Â My current solution is to change XMLSpy to use Saxon9 for it's translations, but I can't assume all developers will be using it for their development and transformations. Â Is there a method of writing our XSLT transformations such that they will work properly using either Saxon9 or XMLSpy2009? Â Any insight on this difference in their functionality is appreciated.
>
>
> Cheers,
> ----------------------------------
> Raymond Lillibridge
> Â Â  Systems Analyst
> rlillibridge@municode.com
> 800-262-2633
> 850-576-3171 x248
>
> "It's what you read when you don't have to that determines what you will be when you can't help it."
> --Oscar Wilde
>
>
> --~------------------------------------------------------------------
> 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] Saxon9, XMLSpy2009, and result-document href= - 10/28/2009 12:09:00 PM
All,

While developing my XSLT 2.0 transformation files using XMLSpy 2009, I was able to save output to the result-document @href value of "C:/folder/file.xml" but when using Saxon9 this doesn't work.  Saxon9 seemed to only work if I used "file:////C:/folder/file.xml" instead (Which doesn't work with XMLSpy).  

This creates a development problem.  My current solution is to change XMLSpy to use Saxon9 for it's translations, but I can't assume all developers will be using it for their development and transformations.  Is there a method of writing our XSLT transformations such that they will work properly using either Saxon9 or XMLSpy2009?  Any insight on this difference in their functionality is appreciated.


Cheers,
----------------------------------
Raymond Lillibridge
   Systems Analyst
rlillibridge@municode.com
800-262-2633
850-576-3171 x248

"It's what you read when you don't have to that determines what you will be when you can't help it."
--Oscar Wilde


--~------------------------------------------------------------------
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] FOP flow question - 10/28/2009 11:50:00 AM
Mark,

I also noticed you have no  in your table. You may also be
having problems with the renderer handling your LinoType font. Try using a
generic font such as Helvetica and see if that helps.

Below is some code that should work although you need to get the indents
sorted on the before and after regions.


	
		
			
			
			
		
	
	
		
			
				
				
					
						
							Hello in
the header table!
						
					
				
			
		
		
			
				
				
				
					
						
							

						
						
							
	

							
						
					
				
			
		
		
			Hello in the body.
		
		
	



William Charlton
The yMonda team
yMonda Limited
w: www.ymonda.net


-----Original Message-----
From: mark bordelon [mailto:markcbordelon@yahoo.com] 
Sent: 26 October 2009 17:36
To: xsl-list@lists.mulberrytech.com
Subject: [xsl] FOP flow question

Dear Members,

After a break from fop frustration, I have reduced my fop transform to the
simplest as I build it up, studying from ww3schools ftp xslt tutorial.
Unfortuantely, even here I am having mixed success that someone here might
be able to help with. I will eventually learn all this at a class I am
taking with Ken, but need this working before then, unfortunately. Any help
much appreciated!

1) (region-bfore) I am getting errors about having two flow tags. When I
change the first to static-content, nothing appears at all in this region.
How can you put text into two regions of the same page-sequence?

2) (region-after) The "denominator" of the page footer does not display. I
have looked through the documentation and cannot figure what is wrong.











	
	
	


			

						
 



				


Page  of 




...content...






	



      

--~------------------------------------------------------------------
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] FOP transform region issue - 10/28/2009 11:32:00 AM
Mark,

You must have columns specified for tables in XSL-FO or the table will not
render.



	  


William Charlton
The yMonda team
yMonda Limited
w: www.ymonda.net

-----Original Message-----
From: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com] 
Sent: 27 October 2009 17:43
To: xsl-list@lists.mulberrytech.com
Subject: Re: [xsl] FOP transform region issue

At 2009-10-27 10:28 -0700, mark bordelon wrote:
>OK, following instructions,
>I have only one flow for the body and static-content for the before-region.
>
>Structure looks like this:

I removed the XSLT and just edited a raw XSL-FO file so as to be able 
to test the pertinent issues without the XSLT getting in the way.  I 
also had to flesh out the table and the body to get some text.  I was 
left with this:

   
    
     
      
      
     
    

    

     
       
      
        
          
            Hello in the header table!
          
        
      
     
     
      
        Hello in the body.
      
      
    
   

When I run the above through four XSL-FO processors (including FOP), 
I get both the header and the body showing.  I am also using FOP 0.95 
and I get these messages:

t:\ftemp>xslfo-pdf-fop mark.fo mark.pdf -v
FOP Version 0.95
Oct 27, 2009 1:37:03 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'LinotypeSyntax,normal,400' not found. Substituting 
with 'any,normal,400'.
Oct 27, 2009 1:37:03 PM 
org.apache.fop.layoutmgr.table.TableLayoutManager getNextKnuthElements
INFO: table-layout="fixed" and width="auto", but auto-layout not 
supported => assuming width="100%"

t:\ftemp>

>But the bad news is the static-content for the before-region does not
appear

I am seeing the static content, so I'm not sure how to mimic the 
problems you are experiencing.

Perhaps someone on the list with FOP experience can recognize the 
differences in behaviours.

. . . . . . . . . . . . . . Ken

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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-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] start-indent - 10/27/2009 9:09:00 PM
My error.
Shortly after I hit the send button, I realized that I was missing the 
point. Simply putting the "right" value (as opposed to useless values) in 
the fo:block did the trick.
Thanks for your answer.
Mark

--------------------------------------------------
From: "G. Ken Holman" 
Sent: Tuesday, October 27, 2009 1:58 PM
To: 
Subject: Re: [xsl] start-indent

> At 2009-10-27 13:09 -0700, Mark Wilson wrote:
>>Hi all,
>>I know I can do this:
>>
>>
>>but is it possible to make something like this work?
>>
>>........
>>
>>
>>So that the wrapper stuff is indented within the block.
>
> Can you describe your requirement in more detail?  Your  is 
> going to add those block-oriented properties to any block content inside, 
> but if you only have inline characters inside, then you won't see any 
> effect.
>
>>If so, how?
>
> If you are expecting to write:
>
>   abcdef ghijkl
>
> ... then what would you have wanted to see?
>
> . . . . . . . . . Ken
>
>
> --
> Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
> Interested in other classes?  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-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] start-indent - 10/27/2009 8:59:00 PM
At 2009-10-27 13:09 -0700, Mark Wilson wrote:
>Hi all,
>I know I can do this:
>
>
>but is it possible to make something like this work?
>
>........
>
>
>So that the wrapper stuff is indented within the block.

Can you describe your requirement in more detail?  Your  
is going to add those block-oriented properties to any block content 
inside, but if you only have inline characters inside, then you won't 
see any effect.

>If so, how?

If you are expecting to write:

   abcdef ghijkl

... then what would you have wanted to see?

. . . . . . . . . Ken


--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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] start-indent - 10/27/2009 8:10:00 PM
Hi all,
I know I can do this:


but is it possible to make something like this work?

........


So that the wrapper stuff is indented within the block.
If so, how?
Thanks
Mark
 


--~------------------------------------------------------------------
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] XSL-FO group by problem - 10/27/2009 7:08:00 PM
Martin and Ken,
So obvious, but I just did not see it.
Thanks
Mark
--------------------------------------------------
From: "Martin Honnen" 
Sent: Tuesday, October 27, 2009 11:08 AM
To: 
Subject: Re: [xsl] XSL-FO group by problem

> Mark Wilson wrote:
>
>>         
>>            
>>                
>>
>> 
>>                    > mode="do"/>
>
> I think you want to move the above xsl:apply-templates outside of the 
> xsl:for-each to ensure it is only done once for each group but not for 
> each Item in each group.
>
>>                   
>>
>>                
>>            
>>        
>
>
>
> -- 
>
> 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] string search - 10/27/2009 6:52:00 PM
Thank you for your responses. I am sorry to have come in such a rush :-) Things (especially the specification give to me) have changed a bit since my post and are much clearer now. It seems that it will not be as difficult as it seemed at the beginning. Nevertheless, I will try to post results and examples after I finish.

Pavel ©kopík



-----Original Message-----
From: Andrew Welch [mailto:andrew.j.welch@gmail.com] 
Sent: Tuesday, October 27, 2009 6:40 PM
To: xsl-list@lists.mulberrytech.com
Subject: Re: [xsl] string search


That's fine... if you spec out the problem more fully with a complete set of possible inputs and required out, and the xslt processer and version you are using, then you should get a solution.

2009/10/27 Skopik Pavel :
> Hello,
>
> I have come across an issue related to string search which seems to be 
> much advanced then just testing its occurence or positon.
>
> My XML source has a node, which contains list of organizations and 
> their roles. First comes the role, second the name of the subject. The 
> subject and its role may be surounded by other text. What I need to do 
> is to extract the name of the subject which comes after the name of 
> the role.
>
> Source text:
> Text text text. Approves: Ministry of whatever. Text Text.
>
> Desired result:
> Ministry of whatever
>
> Of course there can be punctuation characters around the name of the 
> subject, spaces etc.
>
> Do you think it is feasable even to try do something like this or just 
> leave it off and try to solve this situation with different 
> technology? (I am inclined to the second option, but would like to 
> hear you opinion).
>
> Best regards,
>
> Pavel ©kopík
>
>
>
>
>
> __________ Informace od ESET NOD32 Antivirus, verze databaze 4548 
> (20091027) __________
>
> Tuto zpravu proveril ESET NOD32 Antivirus.
>
> http://www.eset.cz
>
>
> --~------------------------------------------------------------------
> 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: 
> --~--
>
>



-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
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: 
--~--

 

__________ Informace od ESET NOD32 Antivirus, verze databaze 4548 (20091027) __________

Tuto zpravu proveril ESET NOD32 Antivirus.

http://www.eset.cz
 
 

__________ Informace od ESET NOD32 Antivirus, verze databaze 4549 (20091027) __________

Tuto zpravu proveril ESET NOD32 Antivirus.

http://www.eset.cz
 

--~------------------------------------------------------------------
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] XSL-FO group by problem - 10/27/2009 6:10:00 PM
At 2009-10-27 11:00 -0700, Mark Wilson wrote:
>In an XSLT-FO style sheet, I have created groups similar to the one 
>shown at the end of this email.

Fine.

>I have one template for formatting the  and another 
>for formatting the remaining data. The  is always 
>identical in a group, but the remaining information differs. I want 
>a single copy of the  and one copy each of all of the 
>remaining information from each as indicated in the output 
>below (I can format everything, that's not my problem, I just can't 
>get the single copy of the ).

What you are missing is that your current node at the beginning of 
 is at the first member of the group selected.

>Output:
>4: New issues: Czech Republic, May/Jun 1993, p. 22; Letters to the 
>editor, Mar/Apr 2002, p. 27; Joint issues, Nov/Dec 2002, p.18.
>
>My style sheet code is:
>         

At this point,  will give you 
"4" because your current node is the first  of the group of 
 elements.

In the classroom I tell students to read the instruction as if it were written:

               
>                
>
>

You put the processing of the catalogue number before the 
, not inside.

>                    

Move that line up before the 

>                   
>
>                
>            
>        

I hope this helps.

. . . . . . . . . . . . . . Ken


--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: 
--~--


Re: [xsl] XSL-FO group by problem - 10/27/2009 6:09:00 PM
Mark Wilson wrote:

>         
>            
>                
> 
> 
>                    

I think you want to move the above xsl:apply-templates outside of the 
xsl:for-each to ensure it is only done once for each group but not for 
each Item in each group.

>                   
> 
>                
>            
>        



-- 

	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] XSL-FO group by problem - 10/27/2009 6:01:00 PM
Hello all,
In an XSLT-FO style sheet, I have created groups similar to the one shown at 
the end of this email.
I have one template for formatting the  and another for 
formatting the remaining data. The  is always identical in a 
group, but the remaining information differs. I want a single copy of the 
 and one copy each of all of the remaining information from 
each as indicated in the output below (I can format everything, that's 
not my problem, I just can't get the single copy of the ).

Thanks,
Mark

Output:
4: New issues: Czech Republic, May/Jun 1993, p. 22; Letters to the editor, 
Mar/Apr 2002, p. 27; Joint issues, Nov/Dec 2002, p.18.

My style sheet code is:
         
            
                


                    
                   

                
            
        

Example of a group:

      4
      New issues: Czech Republic
      May/Jun
      1993
      22

 
     4
     Letters to the editor
     Mar/Apr
     2002
     27


     4
     Joint issues
     Nov/Dec
     2002
     18
 



--~------------------------------------------------------------------
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] string search - 10/27/2009 5:51:00 PM
It's probably feasible to do this in XSLT 2.0 using regular expressions,
assuming you can specify the problem more precisely - or develop the regular
expressions incrementally by trial and error over a range of source files
that are representative of the whole collection you need to process.

(If you can't specify the problem more precisely, then a different
technology isn't going to help.)

Doing it with XSLT 1.0 is likely to be more difficult. 

Regards,

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

> -----Original Message-----
> From: Skopik Pavel [mailto:Pavel.Skopik@aipsafe.cz] 
> Sent: 27 October 2009 17:33
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] string search
> 
> Hello,
>  
> I have come across an issue related to string search which 
> seems to be much advanced then just testing its occurence or positon.
>  
> My XML source has a node, which contains list of 
> organizations and their roles. First comes the role, second 
> the name of the subject. The subject and its role may be 
> surounded by other text. What I need to do is to extract the 
> name of the subject which comes after the name of the role. 
>  
> Source text:
> Text text text. Approves: Ministry of whatever. Text Text.
>  
> Desired result:
> Ministry of whatever
>  
> Of course there can be punctuation characters around the name 
> of the subject, spaces etc.
>  
> Do you think it is feasable even to try do something like 
> this or just leave it off and try to solve this situation 
> with different technology? (I am inclined to the second 
> option, but would like to hear you opinion).
>  
> Best regards,
>  
> Pavel ©kopík
> 
> 
> 
>  
> 
> __________ Informace od ESET NOD32 Antivirus, verze databaze 
> 4548 (20091027) __________
> 
> Tuto zpravu proveril ESET NOD32 Antivirus.
> 
> http://www.eset.cz
>  
> 
> --~------------------------------------------------------------------
> 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] FOP transform region issue - 10/27/2009 5:43:00 PM
At 2009-10-27 10:28 -0700, mark bordelon wrote:
>OK, following instructions,
>I have only one flow for the body and static-content for the before-region.
>
>Structure looks like this:

I removed the XSLT and just edited a raw XSL-FO file so as to be able 
to test the pertinent issues without the XSLT getting in the way.  I 
also had to flesh out the table and the body to get some text.  I was 
left with this:

   
    
     
      
      
     
    

    

     
       
      
        
          
            Hello in the header table!
          
        
      
     
     
      
        Hello in the body.
      
      
    
   

When I run the above through four XSL-FO processors (including FOP), 
I get both the header and the body showing.  I am also using FOP 0.95 
and I get these messages:

t:\ftemp>xslfo-pdf-fop mark.fo mark.pdf -v
FOP Version 0.95
Oct 27, 2009 1:37:03 PM org.apache.fop.fonts.FontInfo notifyFontReplacement
WARNING: Font 'LinotypeSyntax,normal,400' not found. Substituting 
with 'any,normal,400'.
Oct 27, 2009 1:37:03 PM 
org.apache.fop.layoutmgr.table.TableLayoutManager getNextKnuthElements
INFO: table-layout="fixed" and width="auto", but auto-layout not 
supported => assuming width="100%"

t:\ftemp>

>But the bad news is the static-content for the before-region does not appear

I am seeing the static content, so I'm not sure how to mimic the 
problems you are experiencing.

Perhaps someone on the list with FOP experience can recognize the 
differences in behaviours.

. . . . . . . . . . . . . . Ken

--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: 
--~--


Re: [xsl] string search - 10/27/2009 5:40:00 PM
That's fine... if you spec out the problem more fully with a complete
set of possible inputs and required out, and the xslt processer and
version you are using, then you should get a solution.

2009/10/27 Skopik Pavel :
> Hello,
>
> I have come across an issue related to string search which seems to be much advanced then just testing its occurence or positon.
>
> My XML source has a node, which contains list of organizations and their roles. First comes the role, second the name of the subject. The subject and its role may be surounded by other text. What I need to do is to extract the name of the subject which comes after the name of the role.
>
> Source text:
> Text text text. Approves: Ministry of whatever. Text Text.
>
> Desired result:
> Ministry of whatever
>
> Of course there can be punctuation characters around the name of the subject, spaces etc.
>
> Do you think it is feasable even to try do something like this or just leave it off and try to solve this situation with different technology? (I am inclined to the second option, but would like to hear you opinion).
>
> Best regards,
>
> Pavel ©kopík
>
>
>
>
>
> __________ Informace od ESET NOD32 Antivirus, verze databaze 4548 (20091027) __________
>
> Tuto zpravu proveril ESET NOD32 Antivirus.
>
> http://www.eset.cz
>
>
> --~------------------------------------------------------------------
> 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: 
> --~--
>
>



-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
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] string search - 10/27/2009 5:39:00 PM
With the given (sketchy) specification it would be difficult with
*any* technology. How is the end of the "name of the subject" defined?
How many roles are there? Is it guaranteed that no role name occurs in
the "Text text text" preceding the actual role? Is matching to be done
heeding case? Etc., etc.
-W

2009/10/27 Skopik Pavel 
>
> Hello,
>
> I have come across an issue related to string search which seems to be much advanced then just testing its occurence or positon.
>
> My XML source has a node, which contains list of organizations and their roles. First comes the role, second the name of the subject. The subject and its role may be surounded by other text. What I need to do is to extract the name of the subject which comes after the name of the role.
>
> Source text:
> Text text text. Approves: Ministry of whatever. Text Text.
>
> Desired result:
> Ministry of whatever
>
> Of course there can be punctuation characters around the name of the subject, spaces etc.
>
> Do you think it is feasable even to try do something like this or just leave it off and try to solve this situation with different technology? (I am inclined to the second option, but would like to hear you opinion).
>
> Best regards,
>
> Pavel ©kopík
>
>
>
>
>
> __________ Informace od ESET NOD32 Antivirus, verze databaze 4548 (20091027) __________
>
> Tuto zpravu proveril ESET NOD32 Antivirus.
>
> http://www.eset.cz
>
>
> --~------------------------------------------------------------------
> 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] string search - 10/27/2009 5:34:00 PM
Hello,
 
I have come across an issue related to string search which seems to be much advanced then just testing its occurence or positon.
 
My XML source has a node, which contains list of organizations and their roles. First comes the role, second the name of the subject. The subject and its role may be surounded by other text. What I need to do is to extract the name of the subject which comes after the name of the role. 
 
Source text:
Text text text. Approves: Ministry of whatever. Text Text.
 
Desired result:
Ministry of whatever
 
Of course there can be punctuation characters around the name of the subject, spaces etc.
 
Do you think it is feasable even to try do something like this or just leave it off and try to solve this situation with different technology? (I am inclined to the second option, but would like to hear you opinion).
 
Best regards,
 
Pavel ©kopík



 

__________ Informace od ESET NOD32 Antivirus, verze databaze 4548 (20091027) __________

Tuto zpravu proveril ESET NOD32 Antivirus.

http://www.eset.cz
 

--~------------------------------------------------------------------
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] FOP transform region issue - 10/27/2009 5:29:00 PM
OK, following instructions,
I have only one flow for the body and static-content for the before-region.

Structure looks like this:





  
   
    
     
     
    
   
   
   
   
     
     
     
    
    
     
     
     
   
  

 

 
(For simplicity's sake, I removed the after-region. since this is a one-page page-sequence, the page count is not necessary.)

Oddly enough, I checked to make sure that=A0all regions=A0still transform perfectly in SPY (I am using the built-in XSLT engine to perform XSLT part, and the FOP-0.95 for the FO).
But the bad news is the static-content for the before-region does not appear in the java transformation even though the body transforms fine.=20

I get these log messages:
using the=A0org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser as SAX2 Parser
building formatting object tree
setting up fonts
Parsing of document complete, stopping renderer
Initial heap size: 76700Kb
Current heap size: 76700Kb
Total memory used: 0Kb
Memory use is indicative; no GC was performed
These figures should not be used comparatively
Total time used: 10ms
Pages rendered: 0


      

--~------------------------------------------------------------------
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] Can an XSLT document invoke arbitrary extension functions? - 10/26/2009 10:44:00 PM
Hi,

I scanned the slides cited and I actually found nothing to disagree 
with (though it's not my area of expertise). The author is clearly 
talking about XSLT being used for things it wasn't primarily intended 
for by developers who are in over their heads and haven't come to 
terms with what XSLT or XSLT engines can do. If this makes it a 
security hazard in that application context, that's not really about 
XSLT but about the way it's being used.

As I see it, that kind of problem actually goes with the territory of 
its being a powerful and capable technology, not something always to 
be avoided on principle.

I agree that the particular example of a Xalan extension supposedly 
being used to execute arbitrary code is over the top; but the 
argument being made in the slides doesn't actually depend on this example.

Cheers,
Wendell

At 04:40 PM 10/26/2009, Roger wrote:
>Hi Folks,
>
>Below is an XSLT transform that - supposedly - opens a DOS command 
>prompt. I saw the XSLT transform in this [1] briefing (slide 132). I 
>ran it. It doesn't work; it just produces an error....


======================================================================
Wendell Piez                            mailto:wapiez@mulberrytech.com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


--~------------------------------------------------------------------
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] Can an XSLT document invoke arbitrary extension functions? - 10/26/2009 9:43:00 PM
An XSLT transformation is just a program execution.

Allowing unknown programs to run on a box is a security issue of *that
box*, not a security issue of the programming language, in which the
program is written.


-- 
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play





On Mon, Oct 26, 2009 at 1:40 PM, Costello, Roger L.  wrote:
>
> Hi Folks,
>
> Below is an XSLT transform that - supposedly - opens a DOS command prompt. I saw the XSLT transform in this [1] briefing (slide 132). I ran it. It doesn't work; it just produces an error.
>
> The briefing seems to suggest that XSLT is riddled with security leaks, as any XSLT transform can invoke pretty much any arbitrary function (apparently including, as the below XSLT transform shows, any arbitrary Windows function).
>
> Questions:
>
> 1. Should the below XSLT Transform work? (i.e. is there simply a minor bug in it, that when fixed, would make it operate as desired?)
>
> 2. Is there any control over the set of extension functions provided by XSLT processors?
>
> 3. How do you respond to the briefing's suggestions that XSLT is riddled with security leaks? (I realize this is a broad question; any thoughts you have would be appreciated)
>
>
> 
>  Â  Â  Â  Â  Â  Â  Â  Â xmlns:rt="http://xml.apache.org/xalan/java/java.lang.Runtime"
> Â  Â  Â  Â  Â  Â  Â  Â xmlns:ob="http://xml.apache.org/xalan/java/java.lang.Object"
> Â  Â  Â  Â  Â  Â  Â  Â extension-element-prefixes="rt ob"
> Â  Â  Â  Â  Â  Â  Â  Â version="1.0">
>
>
> Â  Â 
> Â  Â  Â  Â 
> Â  Â  Â  Â  Â  Â  Â  Â  Â  select="rt:exec($runTimeObject, 'c:\Windows\system32\cmd.exe')"/>
> Â  Â  Â  Â 
> Â  Â  Â  Â 
> Â  Â 
>
> 
>
>
> /Roger
>
>
> [1] https://www.isecpartners.com/files/iSEC_HILL_AttackingXMLSecurity_bh07.pdf
> --~------------------------------------------------------------------
> 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] Can an XSLT document invoke arbitrary extension functions? - 10/26/2009 9:08:00 PM
Costello, Roger L. wrote:

  Hi,

> The briefing seems to suggest that XSLT is riddled with security
> leaks, as any XSLT transform can invoke pretty much any
> arbitrary function (apparently including, as the below XSLT
> transform shows, any arbitrary Windows function).

  A processor can provide such extension functions, sure.  But
well, the same way you can do pretty weird things in Java or any
other programming languages.  This is not a security hole, this is
a feature you can use or not.  Of course, if you plan to execute a
program coming from the wild wild world, you have to very carefully
disable those features on your processor.

  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] Can an XSLT document invoke arbitrary extension functions? - 10/26/2009 8:59:00 PM
> 
> The briefing seems to suggest that XSLT is riddled with 
> security leaks, as any XSLT transform can invoke pretty much 
> any arbitrary function (apparently including, as the below 
> XSLT transform shows, any arbitrary Windows function). 
> 
> Questions:
> 
> 1. Should the below XSLT Transform work? (i.e. is there 
> simply a minor bug in it, that when fixed, would make it 
> operate as desired?)
> 
> 2. Is there any control over the set of extension functions 
> provided by XSLT processors?
> 
> 3. How do you respond to the briefing's suggestions that XSLT 
> is riddled with security leaks? (I realize this is a broad 
> question; any thoughts you have would be appreciated)
> 

1. The set of extension functions provided by a processors is defined by
that processor, not by the language specification. So the answer to (1)
depends on which processor you are using.

2. Ditto. Saxon has always had an option to disable all extension functions,
for this reason. The latest release of Saxon goes beyond this, by allowing
you to restrict the processor to use only extension functions that have been
pre-registered with the processor: so provided you trust the application
that invokes the processor, you don't need to trust the stylesheet.

3. It's rather emotive language, but there is certainly an issue here that
implementors and users need to be aware of. In the early days of XSLT the
W3C ran a service to run user-uploaded transformations using James Clark's
xt processor, which at the time had no way to disable extension functions,
and I demonstrated that it was possible to use this to obtain a full listing
of the server filestore. (I could equally have read or deleted files if I
had been so inclined). For a short time before I spotted it, Software AG
were doing the same thing. So it's right to draw attention to the risk.

Also of course, XSLT is Turing-complete, so it is eminently capable of
denial-of-service attacks. The bottom line is that a stylesheet is a
program, and if you really care about security then you shouldn't run
untrusted programs, whatever language they are written in.

Regards,

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


--~------------------------------------------------------------------
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] Can an XSLT document invoke arbitrary extension functions? - 10/26/2009 8:54:00 PM
At 2009-10-26 16:40 -0400, Costello, Roger L. wrote:
>Below is an XSLT transform that - supposedly - opens a DOS command 
>prompt. I saw the XSLT transform in this [1] briefing (slide 132). I 
>ran it. It doesn't work; it just produces an error.

Right, because you haven't asked the XSLT processor if it supports 
the "getRuntime()" function in the given namespace.  If you try 
invoking a function that does not exist, the specification states it 
is an error:

   http://www.w3.org/TR/1999/REC-xslt-19991116#section-Extension-Functions
   "If such an extension function occurs in an expression and the extension
    function is actually called, the XSLT processor must signal an error."

The way you check is with the function-available() function:

   http://www.w3.org/TR/1999/REC-xslt-19991116#function-function-available

>1. Should the below XSLT Transform work? (i.e. is there simply a 
>minor bug in it, that when fixed, would make it operate as desired?)

The semantics of extension functions are up to the definition and how 
it is supported by the processor.  It looks like a processor that 
supports what you have would work, but how many processors support it?

>2. Is there any control over the set of extension functions provided 
>by XSLT processors?

"control"?  An XSLT processor has a set of extension functions or it 
doesn't.  If the processor offers at invocation time the ability to 
turn on or off functions, then I suppose one could then "control" 
what extension functions are available in an environment invoked for 
arbitrary stylesheets.

>3. How do you respond to the briefing's suggestions that XSLT is 
>riddled with security leaks? (I realize this is a broad question; 
>any thoughts you have would be appreciated)

There is *nothing* that I know of in the standard XSLT specification 
that gives an outside program control.  What any particular processor 
offers to stylesheets by way of extensions is up to the processor and 
is outside the definition of the specification.

So, I would say that XSLT has zero security issues but XSLT 
processors (like any other application) may have their own problems 
if they implement anything beyond the standard definition.

I think it is unfair to criticize the specification as unsafe when 
safe implementations of the specification can be written.  A 
processor is not required to support any extension at all.  I would 
think processor writers could offer a "safe mode" if this was a 
concern for their users.

I hope this helps.

. . . . . . . . . . Ken


--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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] Can an XSLT document invoke arbitrary extension functions? - 10/26/2009 8:41:00 PM
Hi Folks,

Below is an XSLT transform that - supposedly - opens a DOS command prompt. I saw the XSLT transform in this [1] briefing (slide 132). I ran it. It doesn't work; it just produces an error.

The briefing seems to suggest that XSLT is riddled with security leaks, as any XSLT transform can invoke pretty much any arbitrary function (apparently including, as the below XSLT transform shows, any arbitrary Windows function). 

Questions:

1. Should the below XSLT Transform work? (i.e. is there simply a minor bug in it, that when fixed, would make it operate as desired?)

2. Is there any control over the set of extension functions provided by XSLT processors?

3. How do you respond to the briefing's suggestions that XSLT is riddled with security leaks? (I realize this is a broad question; any thoughts you have would be appreciated)






    
        
        
        
        
    




/Roger


[1] https://www.isecpartners.com/files/iSEC_HILL_AttackingXMLSecurity_bh07.pdf
--~------------------------------------------------------------------
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] FOP flow question - 10/26/2009 8:18:00 PM
At 2009-10-26 10:36 -0700, mark bordelon wrote:
>I will eventually learn all this at a class I am taking with Ken, 
>but need this working before then, unfortunately.

Yes, all of this is covered in the classroom.

Note to others:  there are still seats remaining for both the 
XSLT/XQuery class next week and the XSL-FO class the following week 
... please see here for details:

   http://www.CraneSoftwrights.com/index.html#Crane200910IAD

>1) (region-bfore) I am getting errors about having two flow tags.

Indeed.  In XSL-FO 1.0 only one flow is allowed (any number are 
allowed in 1.1, but you only need one).

>When I change the first to static-content, nothing appears at all in 
>this region.

That surprises me.  From your stylesheet I would have expected the 
content to show, but to be in conflict with the body content on the page.

>How can you put text into two regions of the same page-sequence?

You use multiple  elements, one for 
each of the perimeter regions you need content in, and then one 
 that triggers the pagination.

>2) (region-after) The "denominator" of the page footer does not 
>display. I have looked through the documentation and cannot figure 
>what is wrong.

I'm unfamiliar with the use of "denominator" in publishing, and I 
don't see the word in your stylesheet fragment.

But I do note that your body-region doesn't have any margin to 
accommodate the after-region ... only the before and left margins are 
specified for the body-region.  Your body-region should have a bottom 
margin at least the size of the extent of the page's after-region.

An error is not generated in the case of the overlap of regions, 
because there are some strategies where the overlap is very useful, 
as illustrated in the free UN Layout Key stylesheets for UBL on our 
web site:  the background is painted with XSL-FO and the foreground 
is overlaid on top with more XSL-FO.

I hope this helps.

. . . . . . . . . . . Ken

>
>
>xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
>xmlns:fo="http://www.w3.org/1999/XSL/Format" exclude-result-prefixes="fo">
>indent="yes"/>
>
>
>
>
>
>page-height="11in" margin-top="0.5in" margin-bottom=".5in" 
>margin-left="0.5in" margin-right="1in">
>         
>         
>         
>
>
>
>
>
>
>
>
>
>
>
>text-align="right">
>Page  of 
>
>
>
>
>...content...
>
>
>
>
>
>
>
>


--
Upcoming:  hands-on XSLT, XQuery and XSL-FO Washington DC Nov 2009
Interested in other classes?  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: 
--~--


Re: [xsl] "Concatenate two element values as an attribute value". ( - 10/26/2009 6:27:00 PM
David Galligani wrote:

>>                            > href="{/webenmr/calculation/webinfo/@workingdir}/{@filename}"> ...
>>                                                        
> and
>>   > href="{ancestor::calculation/webinfo/@workingdir}/{@filename}">...
>>   
> 
> Output a correct href , even in if there's a :
> 
> between the two  and  tags I get an empty page :)

The output of your XSLT stylesheet should be an HTML document and HTML 
documents, at least when rendered in the browser window, do not have 
pages. You only get pages or empty pages when you print an HTML 
document. Do you use any print stylesheet that could have CSS settings 
enforcing a page break?

How does the resulting HTML markup look exactly?

Generally when you develop an XSLT stylesheet to produce a HTML document 
I wouldn't start with rendering that result directly in the browser, 
rather I would look at the serialized transformation result in a file 
and inspect the HTML markup created in a editor or at least in console 
window.

-- 

	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] FOP flow question - 10/26/2009 5:37:00 PM
Dear Members,

After a break from fop frustration, I have reduced my fop transform to the simplest as I build it up, studying from ww3schools ftp xslt tutorial. Unfortuantely, even here I am having mixed success that someone here might be able to help with. I will eventually learn all this at a class I am taking with Ken, but need this working before then, unfortunately. Any help much appreciated!

1) (region-bfore) I am getting errors about having two flow tags. When I change the first to static-content, nothing appears at all in this region.
How can you put text into two regions of the same page-sequence?

2) (region-after) The "denominator" of the page footer does not display. I have looked through the documentation and cannot figure what is wrong.











	
	
	


			

						
 



				


Page  of 




...content...






	



      

--~------------------------------------------------------------------
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] "Concatenate two element values as an attribute value". ( - 10/26/2009 2:27:00 PM
> Michael , surely you'r right ... I've been told to learn 
> xml/xsl and to complete a job in a week , so It's not easy a 
> task  , and probably I missed a lot of concept ...

You should have refused the task. Very few people are capable of learning a
new language under such time pressure. I certainly wouldn't attempt it.

Regards,

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


--~------------------------------------------------------------------
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] "Concatenate two element values as an attribute value". ( was - 10/26/2009 2:02:00 PM
First of all many thx to everybody ...
I apologize if I posted a non-correct mail to the list .
With your hints , it "almost" works :)

>
>                             href="{/webenmr/calculation/webinfo/@workingdir}/{@filename}"> ...
>                             
>                            
and
>    href="{ancestor::calculation/webinfo/@workingdir}/{@filename}">...
>   

Output a correct href , even in if there's a :

between the two  and  tags I get an empty page :)
> I think you're having problems because you haven't understood the concept of
> the context node/item, or the details of when and how it changes.

Michael , surely you'r right ... I've been told to learn xml/xsl and to 
complete a job in a week ,
so It's not easy a task  , and probably I missed a lot of concept ...


Thx again

D.



--~------------------------------------------------------------------
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] Variables - 10/26/2009 11:54:00 AM
You will improve the chances that you will receive prompt and helpful 
responses on XSL-List by:

   - asking specific enough questions that answers are possible. Describe
     what you are trying to do, how you approached it, what happened, and
     why you don't like the result you got

     In your case, select one question (you mention "several problems")
     and focus on it. Ask any other questions separately.

   - supplying small samples of files that illustrate your question or
     problem. For example, an XML file, an XSLT stylesheet, the result
     you got, and the result you want - all in miniature (and remembering
     that everything posted to XSL-List is archived in public)

     Create the smallest possible XML document and smallest possible
     XSLT that shows how you are trying to create the hyperlink. Leave
     out anything that is not related to this small issue.

   - describing the topic of your question concisely in the subject line
     Good subject lines - those that describe the subject matter of your
     message - not only increase the chances that you will receive answers
     to questions or responses to comments, they also make your message
     and any replies to it accessible in the list archives.

     In this case, you might want to describe your question as:
     "Concatenate two element values as an attribute value".


Instructions on subscribing to XSL-List are available at 
http://www.mulberrytech.com/xsl/xsl-list/index.html
and the XSL-List archives are at 
http://www.biglist.com/lists/xsl-list/archives/

-- Tommie



>Hi all ,
>I' m a complete newbie in xml/xsl , and I'm having several problems .
>I have the following xml :
>
>
>
>
>
>end_count="5" loop_count="3" timestep="0.005" n_thread="20" />
>
>protein.psf
>CA2.psf
>axis_new_501.psf
>axis_new_502.psf
>axis_new_503.psf
>
>
>par_axis_3.pro
>ca.par
>
>
>protein.pdb
>ca.pdb
>axis_xyzo_3_501.pdb
>axis_xyzo_3_502.pdb
>axis_xyzo_3_503.pdb
>
>
>    
>     tensors.tbl
>    
>    
>     calbindin_NOE.tbl
>     metalcenter.tbl
>    
>   
>   
>    calbindin_ACO.tbl
>   
>   t2="-175.5" fmed="20" scale="5.0" />
>   t2="-5601.7" fmed="20" scale="0.25" />
>   t2="-923.3" fmed="20" scale="1.25" />
>   t2="0.143" fmed="20" scale="1.0" />
>   t2="4.552" fmed="20" scale="0.05" />
>   t2="0.750" fmed="20" scale="0.25" />
>   
>    
>    
>   
>   
>    
>     
>    
>   
>   
>  
>  
>   
>    filename="ite_1_d_input_9_pdb_sa1_1.pdb">
>A2="-166.871736148801" class="pcsce"
>total_energy="89.1003471455398" />
>
>filename="ite_1_d_input_9_pdb_sa1_2.pdb">
>A2="-159.967740084884" class="pcsce"
>total_energy="188.041801829022" />
>
>filename="ite_1_d_input_9_pdb_sa1_3.pdb">
>A2="-175.784774140119" class="pcsce"
>total_energy="90.7929905009074" />
>
>[...]
>
>and the xsl  ( which probably will be infested with errors :) ):
>
>
>xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
>
>
>    
>        
>
>
>ENMRWEBUI
>
>
>
>
>
>
>        
>            
>                
>                
>                
>                 
>                    
>                     select="webenmr/calculation/output/iteration">
>                        
>                     
>                            
>
>                         
>            
>                        
>                             
>                                
>                                
>                             
>                          
>                                        
>                                
>                                    
>                                
>                              
>                                
>                                  
>                                
>                                    
>                              
>                                    
>                             
>                                    
>                             
>                                    
>                              
>                                    
>                                  
>                                
>                                
>                               [...]
>
>I want to concatenate the "workingdir" and "filename" values in an 
>hyperlink , something like File
>but atm nothing seems to work .
>I'm sure it' s a silly thing , but I have already lost 2 days trying 
>to achieve it , and I was wondering if someone could help me .
>Many thx in advance .
>
>David
>
>P.S.: I hope you can understand my english ...
>
>
>--~------------------------------------------------------------------
>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: 
>--~--


-- 

======================================================================
B. Tommie Usdin                        mailto:btusdin@mulberrytech.com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                           Phone: 301/315-9631
Suite 207                                    Direct Line: 301/315-9634
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in XML and SGML
======================================================================

--~------------------------------------------------------------------
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] Variables - 10/26/2009 11:49:00 AM
David Galligani wrote:

> 
> 
> 

>  
>   
>     filename="ite_1_d_input_9_pdb_sa1_1.pdb">

>                                    
>                             
>                                
>                                Iteration
>                            
>                                
>                          
>                            
File 
>                                  
>                                    
>                                    
>                                
XPCS Tensor A1 
> Energy PCS A2 Class Total 
>Energy
  select="@energy_pcs"/>   select="@total_energy"/>
File 
>                                                                      
> 

> I want to concatenate the "workingdir" and "filename" values in an 
> hyperlink , something like File
> but atm nothing seems to work .

Does
                            
                              
                            

give you what you want?

-- 

	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: 
--~--


RE: [xsl] Variables - 10/26/2009 11:47:00 AM
Firstly, xsl:if doesn't change the context node, so this

    
        
            

should probably be something like this:

    
        
            

Assuming the context node is a pdb_info, you can output your hyperlink like
this:

    ...

I think you're having problems because you haven't understood the concept of
the context node/item, or the details of when and how it changes. Also: try
to take advantage of apply-templates and template rules, rather than
wrapping everying in deeply-nested for-each loops.

Regards,

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

 

> -----Original Message-----
> From: David Galligani [mailto:galligani@cerm.unifi.it] 
> Sent: 26 October 2009 11:29
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] Variables 
> 
> Hi all ,
> I' m a complete newbie in xml/xsl , and I'm having several problems .
> I have the following xml :
> 
> 
> 
> 
> 
>  end_count="5" loop_count="3" timestep="0.005" n_thread="20" 
> />  protein.psf
> CA2.psf
> axis_new_501.psf
> axis_new_502.psf
> axis_new_503.psf
> 
> 
> par_axis_3.pro
> ca.par
> 
> 
> protein.pdb
> ca.pdb
> axis_xyzo_3_501.pdb
> axis_xyzo_3_502.pdb
> axis_xyzo_3_503.pdb
> 
> 
>     
>      tensors.tbl
>     
>     
>      calbindin_NOE.tbl
>      metalcenter.tbl
>     
>    
>    
>     calbindin_ACO.tbl
>    
>     t2="-175.5" fmed="20" scale="5.0" />
>     t2="-5601.7" fmed="20" scale="0.25" />
>     t2="-923.3" fmed="20" scale="1.25" />
>     t2="0.143" fmed="20" scale="1.0" />
>     t2="4.552" fmed="20" scale="0.05" />
>     t2="0.750" fmed="20" scale="0.25" />
>    
>     
>     
>    
>    
>     
>      
>     
>    
>    
>   
>   
>    
>      filename="ite_1_d_input_9_pdb_sa1_1.pdb">
>  A2="-166.871736148801" class="pcsce"
> total_energy="89.1003471455398" />
> 
>  filename="ite_1_d_input_9_pdb_sa1_2.pdb">
>  A2="-159.967740084884" class="pcsce"
> total_energy="188.041801829022" />
> 
>  filename="ite_1_d_input_9_pdb_sa1_3.pdb">
>  A2="-175.784774140119" class="pcsce"
> total_energy="90.7929905009074" />
> 
> [...]
> 
> and the xsl  ( which probably will be infested with errors :) ):
> 
> 
>  xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> 
> 
>     
>         
> 
>  ENMRWEBUI
> 
> 
> 
> 
> 
> 
>         
>             
>                 
>                 
>                 
>                  
>                     
>                       select="webenmr/calculation/output/iteration">
>                         
>                       
>                             
> 
>                          
>              
>                         
>                              
>                                 
>                                 
>                              
>                            
>                                         
>                                 
>                                     
>                                 
>                                
>                                 
>                                    
>                                 
>                                     
>                                
>                                     
>                               
>                                     
>                               
>                                     
>                                
>                                     
>                                    
>                                 
>                                 
>                                [...]
> 
> I want to concatenate the "workingdir" and "filename" values 
> in an hyperlink , something like  href='workingdir/filename'>File
> but atm nothing seems to work .
> I'm sure it' s a silly thing , but I have already lost 2 days 
> trying to achieve it , and I was wondering if someone could help me .
> Many thx in advance .
> 
> David
> 
> P.S.: I hope you can understand my english ...
> 
> 
> --~------------------------------------------------------------------
> 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: 
--~--

Iteration
>                             
>                                 
>                            
>                             
File 
>                                    
>                                     
>                                     
>                                 
XPCS Tensor A1 
> Energy PCS A2 Class Total Energy
 select="@A1"/>   select="@energy_pcs"/>  select="@A2"/>  select="@class"/>   select="@total_energy"/>