Subject: Re: [xsl] Meunchen Grouping - How to combine two specific 'unique' group types? From: David Carlisle <davidc@xxxxxxxxx> Date: Tue, 8 May 2007 17:47:18 +0100 |
You want to ensure that NOTSET and Exam end up using the same key, there are several ways of doing that, it doesn't matter which one you use as long as you do the same thing both where the key is defiend and where it is called. One way: change <xsl:key name="schedule-by-assessmentType" match="activeSchedule" use="assessmentType"/> to <xsl:key name="schedule-by-assessmentType" match="activeSchedule" use="translate(assessmentType,'NOSET','mxam')"/> and <xsl:apply-templates select="//activeSchedule[generate-id(.) = generate-id(key('schedule-by-assessmentType', assessmentType)[1])]"/> to <xsl:apply-templates select="//activeSchedule[generate-id(.) = generate-id(key('schedule-by-assessmentType', translate(assessmentType,'NOSET','mxam'))[1])]"/> The translate probably garbles for all your exam types but it doesn't matter what value it generates as long as its unique in all cases except that NOTSET and Exam both translate to mxam. 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. ________________________________________________________________________
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Meunchen Grouping - How to co, Karlmarx Rajangam | Thread | [xsl] Continued Table Headers [fo:m, Horace Burke |
Re: [xsl] recursive xsl replace, Joelle Tegwen | Date | Re: [xsl] [HS] Documentation for Ge, Florent Georges |
Month |