http://www.altova.com/ Altova accelerates application development and data management projects with software and solutions that enhance productivity and maximize results. As an innovative, customer-focused company and the creator of XMLSpy and other leading XML, data administration, UML, and Web services tools, Altova is the choice of over 3 million clients worldwide, including virtually every Fortune 500 company. With customers ranging from vast development teams in the world’s largest organizations to progressive one-person shops, Altova’s line of software applications fulfills a broad spectrum of business needs. Altova is an active member of the World Wide Web Consortium (W3C) and Object Management Group (OMG) and is committed to delivering standards-based platform-independent solutions that are powerful, affordable, and easy to use. Altova was founded in 1992 and has headquarters in Beverly, Massachusetts and Vienna, Austria. en-us Copyright © 2005, 2006, 2007 Altova GmbH. All rights reserved. Altova, XMLSpy, MapForce, StyleVision, SemanticWorks, SchemaAgent, UModel, DiffDog, and Authentic are trademarks and/or registered trademarks of Altova GmbH in the United States and/or other countries. The names of and reference to other companies and products mentioned herein may be the trademarks of their respective owners. Tue, 03 Jun 2008 10:00:00 EDT Tue, 03 Jun 2008 10:00:00 EDT Authentic RSS Editor, visit www.altova.com for details pr@altova.com webmaster@altova.com http://www.altova.com/images/logos/altova_right_120.gif http://www.altova.com/ 120 24 Altova Logo Hi. I am currently trying to transform the xml as shown below. It requires me to essentially find the distinct list of all people who have the same set of meeting dates and times, and then group them by those that have the same dates and times together. i.e. a single invitee is never split over multiple appointment groups - if they have all days the same and one extra, then they become a new group. <Appointments> <Appointment Date="2011-01-01" TimeOfDay="06:00:00" AppointmentType="Meeting"> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> </Appointment> <Appointment Date="2011-01-02" TimeOfDay="06:00:00" AppointmentType="Meeting"> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> <Invitee Firstname="Gordon" Surname="Jones"/> </Appointment> <Appointment Date="2011-01-03" TimeOfDay="06:00:00" AppointmentType="Meeting"> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> <Invitee Firstname="Gordon" Surname="Jones"/> </Appointment> <Appointment Date="2011-01-02" TimeOfDay="06:00:00" AppointmentType="PhoneHookup"> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> </Appointment> </Appointments> Into: <MeetingPlan> <Appointments TimeOfDay="06:00:00" AppointmentType="Meeting"> <Dates> <MeetingDate date="2011-01-01"/> <MeetingDate date="2011-01-02"/> <MeetingDate date="2011-01-03"/> </Dates> <Invitees> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> </Invitees> </Appointments> <Appointments TimeOfDay="06:00:00" AppointmentType="Meeting"> <Dates> <MeetingDate date="2011-01-02"/> <MeetingDate date="2011-01-03"/> </Dates> <Invitees> <Invitee Firstname="Gordon" Surname="Jones"/> </Invitees> </Appointments> <Appointments TimeOfDay="06:00:00" AppointmentType="PhoneHookup"> <Dates> <MeetingDate date="2011-01-02"/> </Dates> <Invitees> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> </Invitees> </Appointments> </MeetingPlan> I've had some success thus far. The following transform: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:xd="http://www.oxygenxml.com/ns/doc/xsl" exclude-result-prefixes="xd xs fn" version="2.0"> <xd:doc scope="stylesheet"> <xd:desc> <xd:p><xd:b>Created on:</xd:b> Feb 1, 2 amarendy</xd:p> <xd:p><xd:b>Author:</xd:b>Anthony Marendy</xd:p> </xd:desc> </xd:doc> <xsl:template match="//Appointments"> <MeetingPlan> <xsl:for-each-group select="//Invitee" group-by="../@AppointmentType"> <xsl:variable name="currentAppointmentType" select="current-grouping-key()"/> <xsl:for-each-group select="current-group()" group-by="../@TimeOfDay"> <xsl:variable name="currentTimeOfDay" select="current-grouping-key()"/> <xsl:variable name="appointmentsWithSameTypeAndTime" select="current-group()"/> <xsl:for-each-group select="$appointmentsWithSameTypeAndTime" group-by="@Surname"> <xsl:variable name="currentSurname" select="current-grouping-key()"/> <xsl:for-each-group select="current-group()" group-by="@Firstname"> <xsl:variable name="currentFirstname" select="current-grouping-key()"/> <!-- Get the list of appointments that the current invitee has. --> <xsl:variable name="inviteeAppointments" select="for $d in current-group()/.. return $d"/> <xsl:if test="(count($inviteeAppointments) > 0)"> <Appointments TimeOfDay="{$currentTimeOfDay}" AppointmentType="{$currentAppointmentType}"> <Dates> <xsl:for-each select="$inviteeAppointments"> <MeetingDate date="{./@Date}"/> </xsl:for-each> </Dates> <Invitees> <!-- Now loop through and find all invitees that have the same combination of appointments --> <xsl:for-each-group select="$appointmentsWithSameTypeAndTime" group-by="@Surname"> <xsl:variable name="loopSurname" select="current-grouping-key()"/> <xsl:for-each-group select="current-group()" group-by="@Firstname"> <xsl:variable name="loopFirstname" select="current-grouping-key()"/> <xsl:variable name="entriesForCurrentInvitee" select="current-group()"/> <xsl:variable name="loopAppointments" select="for $d in $entriesForCurrentInvitee/.. return $d"/> <xsl:if test="fn:deep-equal($loopAppointments, $inviteeAppointments)"> <Invitee Firstname="{$loopFirstname}" Surname="{$loopSurname}"/> </xsl:if> </xsl:for-each-group> </xsl:for-each-group> </Invitees> </Appointments> </xsl:if> </xsl:for-each-group> </xsl:for-each-group> </xsl:for-each-group> </xsl:for-each-group> </MeetingPlan> </xsl:template> <xsl:template match="@*|node()"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> </xsl:stylesheet> Produces the following output: <?xml version="1.0" encoding="UTF-8"?> <MeetingPlan> <Appointments TimeOfDay="06:00:00" AppointmentType="Meeting"> <Dates> <MeetingDate date="2011-01-01"/> <MeetingDate date="2011-01-02"/> <MeetingDate date="2011-01-03"/> </Dates> <Invitees> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> </Invitees> </Appointments> <Appointments TimeOfDay="06:00:00" AppointmentType="Meeting"> <Dates> <MeetingDate date="2011-01-01"/> <MeetingDate date="2011-01-02"/> <MeetingDate date="2011-01-03"/> </Dates> <Invitees> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> </Invitees> </Appointments> <Appointments TimeOfDay="06:00:00" AppointmentType="Meeting"> <Dates> <MeetingDate date="2011-01-02"/> <MeetingDate date="2011-01-03"/> </Dates> <Invitees> <Invitee Firstname="Gordon" Surname="Jones"/> </Invitees> </Appointments> <Appointments TimeOfDay="06:00:00" AppointmentType="PhoneHookup"> <Dates> <MeetingDate date="2011-01-02"/> </Dates> <Invitees> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> </Invitees> </Appointments> <Appointments TimeOfDay="06:00:00" AppointmentType="PhoneHookup"> <Dates> <MeetingDate date="2011-01-02"/> </Dates> <Invitees> <Invitee Firstname="Martha" Surname="Jones"/> <Invitee Firstname="Louis" Surname="Jones"/> </Invitees> </Appointments> </MeetingPlan> The way the transform works is that it works its way down find a particular appointment type and time, then it determines the list of dates for that appointment. It then loops through all of the appointments of that type and time to find any that have the same set of dates. You can see that the output the problem is that the output is duplicated. The reason is that that there are multiple appointments in the same set, and each of these will match in the second lookup. Firstly, I just can't help but feeling I'm going about this the wrong way, so suggestions to other approaches would be appreciated. Alternately, can anyone suggest how I could remove these duplicates? I have thought about passing the result through a second stylesheet - which I could live with, but would prefer a different solution. Thanks, Anthony. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324681.html > What's the issue there? > > It should really have have a return type of item()*, and the param > should really be called 'node-list' rather than 'context': > > <xsl:function name="f:apply-templates" as="item()*"> > <xsl:param name="node-list" as="node()*"/> > <xsl:apply-templates select="$node-list/> > </xsl:function> > > anything else? > One possible issue is that people may want the results to correspond to the sequence order of the argument. This could be "assured" if you use: <xsl:for-each select="$node-list"> <xsl:apply-templates select="."/> </xsl:for-each> However, if you use this apply() function in: /a/b/f:apply() the results will be deduplicated and sorted in document order. If new nodes are created, their order will be unpredictable (implementation-dependent). It is still OK to use such a function within an XPath expression if order and deduplication don't matter, though. Cheers, Dimitre On Sun, Feb 12, 2012 at 8:30 AM, Andrew Welch <andrew.j.welch@gmail.com> wrote: > Hi Dimitre, > > On 12 February 2012 15:48, Dimitre Novatchev <dnovatchev@gmail.com> wrote: >> On Sun, Feb 12, 2012 at 5:24 AM, Andrew Welch <andrew.j.welch@gmail.com> wrote: >>> If you needed to call apply-templates using a function call (say as >>> part of an xpath) any reason why this wouldn't be fine: >>> >>> <xsl:function name="f:apply-templates" as="node()*"> >>>    <xsl:param name="context" as="node()*"/> >>>    <xsl:apply-templates select="$context"/> >>> </xsl:function> >>> >>> with: >>> >>> <xsl:sequence select="f:apply-templates(child::node())"/> >>> >>> (ignoring modes and params etc) >>> >>> Seems ok to me... >> >> Except when you use it as the second operand of the / operator. > > What's the issue there? > > It should really have have a return type of item()*, and the param > should really be called 'node-list' rather than 'context': > > <xsl:function name="f:apply-templates" as="item()*"> >   <xsl:param name="node-list" as="node()*"/> >   <xsl:apply-templates select="$node-list/> > </xsl:function> > > anything else? > > -- > Andrew Welch > http://andrewjwelch.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> > --~-- > -- 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 ------------------------------------- To avoid situations in which you might make mistakes may be the biggest mistake of all ------------------------------------ Quality means doing it right when no one is looking. ------------------------------------- You've achieved success in your field when you don't know whether what you're doing is work or play ------------------------------------- Facts do not cease to exist because they are ignored. ------------------------------------- I finally figured out the only reason to be alive is to enjoy it. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324680.html > You appear to propose the FXSL's  f:apply() function that was > published more than seven years ago. :) Ha ok... I was just watching Evan Lenz's talk at xmlprague where he mentioned an issue with xslt was the lack of the ability to call apply-templates as a function. -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324679.html Andrew, You appear to propose the FXSL's f:apply() function that was published more than seven years ago. :) Cheers, Dimitre On Sun, Feb 12, 2012 at 5:24 AM, Andrew Welch <andrew.j.welch@gmail.com> wrote: > If you needed to call apply-templates using a function call (say as > part of an xpath) any reason why this wouldn't be fine: > > <xsl:function name="f:apply-templates" as="node()*"> >    <xsl:param name="context" as="node()*"/> >    <xsl:apply-templates select="$context"/> > </xsl:function> > > with: > > <xsl:sequence select="f:apply-templates(child::node())"/> > > (ignoring modes and params etc) > > Seems ok to me... > > > -- > Andrew Welch > http://andrewjwelch.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> > --~-- > -- 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 ------------------------------------- To avoid situations in which you might make mistakes may be the biggest mistake of all ------------------------------------ Quality means doing it right when no one is looking. ------------------------------------- You've achieved success in your field when you don't know whether what you're doing is work or play ------------------------------------- Facts do not cease to exist because they are ignored. ------------------------------------- I finally figured out the only reason to be alive is to enjoy it. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324677.html Hi Dimitre, On 12 February 2012 15:48, Dimitre Novatchev <dnovatchev@gmail.com> wrote: > On Sun, Feb 12, 2012 at 5:24 AM, Andrew Welch <andrew.j.welch@gmail.com> wrote: >> If you needed to call apply-templates using a function call (say as >> part of an xpath) any reason why this wouldn't be fine: >> >> <xsl:function name="f:apply-templates" as="node()*"> >>    <xsl:param name="context" as="node()*"/> >>    <xsl:apply-templates select="$context"/> >> </xsl:function> >> >> with: >> >> <xsl:sequence select="f:apply-templates(child::node())"/> >> >> (ignoring modes and params etc) >> >> Seems ok to me... > > Except when you use it as the second operand of the / operator. What's the issue there? It should really have have a return type of item()*, and the param should really be called 'node-list' rather than 'context': <xsl:function name="f:apply-templates" as="item()*"> <xsl:param name="node-list" as="node()*"/> <xsl:apply-templates select="$node-list/> </xsl:function> anything else? -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324678.html On Sun, Feb 12, 2012 at 5:24 AM, Andrew Welch <andrew.j.welch@gmail.com> wrote: > If you needed to call apply-templates using a function call (say as > part of an xpath) any reason why this wouldn't be fine: > > <xsl:function name="f:apply-templates" as="node()*"> >    <xsl:param name="context" as="node()*"/> >    <xsl:apply-templates select="$context"/> > </xsl:function> > > with: > > <xsl:sequence select="f:apply-templates(child::node())"/> > > (ignoring modes and params etc) > > Seems ok to me... Except when you use it as the second operand of the / operator. > > > -- > Andrew Welch > http://andrewjwelch.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> > --~-- > -- 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 ------------------------------------- To avoid situations in which you might make mistakes may be the biggest mistake of all ------------------------------------ Quality means doing it right when no one is looking. ------------------------------------- You've achieved success in your field when you don't know whether what you're doing is work or play ------------------------------------- Facts do not cease to exist because they are ignored. ------------------------------------- I finally figured out the only reason to be alive is to enjoy it. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324676.html If you needed to call apply-templates using a function call (say as part of an xpath) any reason why this wouldn't be fine: <xsl:function name="f:apply-templates" as="node()*"> <xsl:param name="context" as="node()*"/> <xsl:apply-templates select="$context"/> </xsl:function> with: <xsl:sequence select="f:apply-templates(child::node())"/> (ignoring modes and params etc) Seems ok to me... -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324675.html On 11/02/2012 19:58, Wolfgang Laun wrote: > which Chrome refuses to accept as correct javascript, and I think it is right. Chrome would have accepted had you served it with the correct mime type (application/xhtml+xml) If you serve it as text/html then chrome (and other browsers) expects to get html not xml. Saxon would have generated an html form of the output had you used xsl:output method="html". David -- google plus: https:/profiles.google.com/d.p.carlisle --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324674.html Wolfgang Laun wrote: > <xsl:stylesheet version="2.0" > xmlns:xsl="http://www.w3.org/1999/XSL/Transform" > xmlns:xs="http://www.w3.org/2001/XMLSchema" > xmlns="http://www.w3.org/1999/xhtml"> > > <xsl:output method = "html" cdata-section-elements="script" encoding = > "UTF-8" indent = "yes"/> > > <xsl:template match="/"> > <html> > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> > <head> > <script type="text/javascript"><![CDATA[ > function restore(){ > if( 1< 10 ) alert("x"); // something else in reality. > } > ]]></script> > <title>X</title> > </head> > <body> > </body> > </html> > </xsl:template> > </xsl:stylesheet> > > However, the output from Saxon 9 (latest) contains > if( 1&lt; 10 ) alert("x"); > which Chrome refuses to accept as correct javascript, and I think it is right. > > Omitting cdata-section-elements="script" doesn't alter anything, of course. For text/html, consider to create HTML 4 or HTML5 with no namespaces with output method "html", then the XSLT processor will serialize inline script correctly for browsers with their tag soup text/html parsers or with their recent move to HTML5 parsers. You currently have output method "html" which is intended for HTML 4 and text/html with HTML elements being in no namespace, yet your result elements are in the XHTML namespace, so the serialization rules that the output method "html" mandates are not applied to your result elements. There is also in XSLT 2.0 an output method "xhtml" aimed at outputting XHTML 1.0 as text/html but I don't think it is helpful with inline script. If you really want to create XHTML but want it to be served as text/html then I agree with Andrew that using external script files is the right approach to avoid all these problems with incompatibilites between SGML or tag soup HTML parsing rules and XML serialization syntax. -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324673.html >    <script type="text/javascript"><![CDATA[ > Any ideas? By far the easiest and best long term approach is to use an external js file. -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324671.html This is the essential part of what I have (after some research): <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/1999/xhtml"> <xsl:output method = "html" cdata-section-elements="script" encoding = "UTF-8" indent = "yes"/> <xsl:template match="/"> <html> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <head> <script type="text/javascript"><![CDATA[ function restore(){ if( 1 < 10 ) alert("x"); // something else in reality. } ]]></script> <title>X</title> </head> <body> </body> </html> </xsl:template> </xsl:stylesheet> However, the output from Saxon 9 (latest) contains if( 1 &lt; 10 ) alert("x"); which Chrome refuses to accept as correct javascript, and I think it is right. Omitting cdata-section-elements="script" doesn't alter anything, of course. Any ideas? Wolfgang --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324670.html On Sat, Feb 11, 2012 at 04:22:47PM +0100, Wolfgang Laun scripsit: > My XSLT generates a HTML document containing (almost) nothing except > <h*> and <table>. I wrote it as a template reflecting the <html> > structure, with called templates pulling in the data from the XML > source. It is within these called templates that the various <table> > elements (of differing structure) are generated. > > An new requirement demands that all the various <table> elements are > to be wrapped with another <table> (with a single <tr>) for layout > purposes, adding one <td> with uniform contents to the <td> containing > the original table. > > I cannot insert two different template calls producing the outer > table's introduction and completion, respectively: they each would > contain unbalanced data. Supposing you are using XSLT2, this seems like a textbook example of when to use xsl:next-match; the higher priority "outer" match creates the wrapper, the normal-priority "inner" match creates the table. Generally, I suspect this is a case where making the table creators callable named templates might not be what you want; it compels you to manage the logic of which table to create when. If you could do that via source document template matches, a whole lot of the headache vanishes into the XSLT processor's domain. -- Graydon -- Graydon Saunders graydon@epiphyte.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324669.html On 11 February 2012 16:59, Andrew Welch <andrew.j.welch@gmail.com> wrote: >> An new requirement demands that all the various <table> elements are >> to be wrapped with another <table> (with a single <tr>) for layout >> purposes, adding one <td> with uniform contents to the <td> containing >> the original table. > > It's hard to give a decent answer with an actual example, but 2 options are: > > - modify the transform to just output the wrapper code This would be the added layout table for enclosing the actual table and the new additions - but how would the original tables be added? <table class="wrapper"> <tr> <td><table class="original table, one of many different tables"><tr>...</table></td> <td><div class="new stuff, same for all"/></td> </tr> </table> > > - use 'micro-pipelining' to post-process the result to wrap the <table>s OK, I understand. But I'd have to identify the "original" tables or XPath-pick them carefully because a <table> might crop up as an element within an "original" table. Thanks Wolfgang > -- > Andrew Welch > http://andrewjwelch.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> > --~-- > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324668.html > An new requirement demands that all the various <table> elements are > to be wrapped with another <table> (with a single <tr>) for layout > purposes, adding one <td> with uniform contents to the <td> containing > the original table. It's hard to give a decent answer with an actual example, but 2 options are: - modify the transform to just output the wrapper code - use 'micro-pipelining' to post-process the result to wrap the <table>s -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324667.html Hello Roelof, Roelof Wobben wrote: > <xsl:template match="dagboek/entry" > > <h3> > <xsl:value-of select="titel" /> > </h3> > <xsl:apply-templates select="dagboek/entry[nieuwe-pagina = 'yes']" mode="pagegroup" /> > <xsl:apply-templates select="tekst" /> > </div> > </xsl:template> In this template, the context node is a <entry> element, therefore 'apply-templates select="dagboek/entry[...' does not select anything: there is no /data/dagboek/entry/dagboek/entry in your input XML. I'm not sure what you want to achieve with this apply-templates, either, since it is located between the code for 'titel' and 'tekst'. Just guessing, a better place for this apply-templates would be in the 'data' template. Also, you may want to use either 'yes' or 'Yes' (like in your XML data). Markus --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324666.html My XSLT generates a HTML document containing (almost) nothing except <h*> and <table>. I wrote it as a template reflecting the <html> structure, with called templates pulling in the data from the XML source. It is within these called templates that the various <table> elements (of differing structure) are generated. An new requirement demands that all the various <table> elements are to be wrapped with another <table> (with a single <tr>) for layout purposes, adding one <td> with uniform contents to the <td> containing the original table. I cannot insert two different template calls producing the outer table's introduction and completion, respectively: they each would contain unbalanced data. I know it can be done by adding the new HTML stuff to all the called templates, which isn't nice as it duplicates code, in many different places. If I had realized this new requirement earlier - would there be a good solution while still retaining the "pull" structure? How do I handle the generation of different tables from within a single "wrapper" table template? One big <choose> driven by a parameter seems to be the only option. (Something like a "function reference" for callable templates would enable me to write what I'd consider a "clean" program structure.) I wouldn't be surprised if there is there anything I've overlooked. Regards Wolfgang --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324665.html >I'm genuinely surprised that Microsoft has dropped the ball on this. They put in a massive effort when they introduced .NET which was after their browser played a pioneering role in the genenis of XSL. Not affording their .NET library XSLT2 is tantermount to sabotaging the progress of XML related development. It just doesn't make sense and is pretty lame IMO. I don't know any detail of what went on inside Microsoft other than a few rumours that leaked out, but I do know a little bit about the process, or lack of it, that results in product development decisions inside large companies. There will always be champions (perhaps in this case even a Champion...) advocating investing in a particular technology; there will be others with competing proposals, and there will be managers who aren't intimately acquainted with the technical detail who end up having to make the decisions. There will also be customers pushing for one course of action or another, and some of those customers will have clout and others won't: not necessarily because of pure revenue considerations, but perhaps because keeping them "on side" is important for unrelated reasons. In making these decisions, the biggest problem is that so much of this kind of software is free, which means that the value the customers get from a product doesn't flow back into investment in that product. When the champions for developing a particular piece of software can't put together a business case based on the direct revenue from that product, the arguments for and against become very woolly and subjective. XSLT has always been a technology that some people love and others hate. The language has deep beauty but superficial ugliness, so this range of reactions is not surprising. No doubt this polarisation of views exists within Microsoft as much as anywhere else; and no doubt the negative views will have been amplified by those advocating other investments that were competing for the same budget, such as XQuery and Linq. Perhaps some of these voices were even arguing that Microsoft could safely leave this area to third parties. So you shouldn't be surprised. These decisions are complex, there is a lot of emotion involved, and very little hard data about the impact of deciding one way or another. Probably at least half the product development decisions made in a big company turn out to be wrong, so expecting a big company to make the decision you consider right is naive. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324664.html On 11 February 2012 02:44, Wendell Piez <wapiez@mulberrytech.com> wrote: > > I think much of this is true, yet don't forget that XML and XSLT are still > healthy (very healthy as far as I can tell) in the space for which they were > originally designed, namely publishing systems. > > Some publishing systems are content to stick with a single channel of > output, such as print or the web. And if you're publishing only to the web, > you can maintain your data in HTML and/or an HTML-facing CMS. > > But other publishers can't do this, or they need to insulate themselves, to > whatever extent possible, from technological changes in target media, and > XML/XSLT allow them to do this. Or they need to find efficiencies and > scalability in data interchange and data longevity that they can only get > through a careful separation of concerns across their workflows, which > XML/XSLT allows them to engineer. > > If there's a significant part of the tech marketplace that doesn't even know > this is going on, what does that say other than that the world is a big > place? > Well this is all very true (when I was working as Australian Army webmaster, it was within DoD "publishing systems" where they used SGML and Adobe Frame Maker back in the day). But the introduction of XML Schema saw the implementation of strong data typing which implies the use of XML for data packets AS WELL AS document publishing. The "insulation" used by publishing houses is at least as important to anyone exchanging data - hence all of us [coders]. Personally, I don't see an argument for XML not to be everywhere (at least where protocol overhead isn't super-critical). If it that was half-true [everywhere], then XSLT 2 processors would be ubiquitous. I'm genuinely surprised that Microsoft has dropped the ball on this. They put in a massive effort when they introduced .NET which was after their browser played a pioneering role in the genenis of XSL. Not affording their .NET library XSLT2 is tantermount to sabotaging the progress of XML related development. It just doesn't make sense and is pretty lame IMO. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324663.html Mark, The publishing industry in general and at large is very loosely organized. Authors interchange data with editors (sadly, not much in XML, yet), editorial groups among themselves and with production, production with various distribution and syndication channels, all the above with contractors and subcontractors for operations including conversion and formatting, and finally everyone wants to get in with the aggregators, indexing services, archives and libraries. I'm sure I haven't thought of everything, but you can see that even here there's going to be quite a bit of room for technology solutions that work across organizational boundaries (like XML), or that help to mediate between them (like XSLT). And this is only the "publishing industry", considered broadly. As Andrew's client list shows, many organizations and companies that aren't "publishers" and don't make money publishing also publish more than many who make their living that way. Part of the reason XML and XSLT work well is that they are very capable with information sets whose structures are loose and only imperfectly specified (or even understood) up front, and very adaptable. This offers advantages in very heterogeneous environments that change rapidly, because it lets you create islands of stability even while your interfaces remain very responsive. Cheers, Wendell On 2/10/2012 1:28 PM, Mark Giffin wrote: > On 2/10/2012 8:44 AM, Wendell Piez wrote: >> >> [...] Or they need to find efficiencies and scalability in data >> interchange and data longevity that they can only get through a >> careful separation of concerns across their workflows, which XML/XSLT >> allows them to engineer. >> > Thanks Wendell for being specific about what XML and XSLT are used for > (publishing makes a lot of sense to me). What kind of data interchange > do you mean here? Passing documents between parts of the same company? > Connecting SQL Server data to Oracle data? Other things? > > Mark -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324662.html On 2/10/2012 8:44 AM, Wendell Piez wrote: > > [...] Or they need to find efficiencies and scalability in data > interchange and data longevity that they can only get through a > careful separation of concerns across their workflows, which XML/XSLT > allows them to engineer. > Thanks Wendell for being specific about what XML and XSLT are used for (publishing makes a lot of sense to me). What kind of data interchange do you mean here? Passing documents between parts of the same company? Connecting SQL Server data to Oracle data? Other things? 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324661.html On 02/09/2012 10:53 PM, Mark Giffin wrote: > Sorry, but forget JSON. What is XSLT mainly being used for these days? XML, JSON... who cares. I like SAX: assuming SAX serializer/deserializer exist, anything can be treated as XML. For example, you can write XSLT stylesheets transforming JSON: all you need is JSON2SAXParser and SAX2JSONSerializer. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324660.html Hi again, On 2/9/2012 6:22 PM, Andrew Welch wrote: >> Where do you use it Mr. Welch? > > Various companies and sectors, including aerospace (BAE), health > (MDConsult), finance (JPMC, Interactive Data), publishing (Elsevier, > Macmillan), telecoms (Vodafone)... it's all pretty much the same work, > just the text nodes are different. FWIW, these all fall into the category of "publishers" in a large sense, since they are publishing even if only in support of other activities. Keep in mind that two of the most important sectors supporting the development of SGML in the 1980s and 1990s were military-industrial, and academic computing (big research libraries and their ancillary activities). What do these have in common? They both need their data to outlive their machines, so they have to avoid proprietary lock-in either to platforms or even (at the further edges) to sets of functional requirements. This is the conceptual foundation of layered systems based on descriptive markup, aka (in its current form) XML/XSLT. For many kinds of work the engineering expense is arguably not worth it (partly because it requires a rare combination of skills to do well). Other kinds of work are more or less impossible or unsustainable without it. 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324658.html Hi, Glossing David again, If you have <xsl:variable name="alpha" select="A | B | C | D"/> Keep in mind this will bind $alpha only to the A,B,C and D children of the context (the root if the variable declaration is global). You can bind to all the A|B|C|D in the document with <xsl:variable name="alpha" select="//A | //B | //C | //D"/> On 2/10/2012 6:42 AM, David Carlisle wrote: >> <xsl:template match="* except $alpha"/> > no that would be a legal xpath but not a pattern > >> or >> <xsl:template match="*[not $alpha]"/> > > no, that's a syntax error so wouldn't run at all <xsl:template match="*[exists(. except $alpha)]"> will work with the declaration of $alpha given above. Of course this will tend to be much less efficient than what David suggests: > easiest is > > <xsl:template match="*"> the complement > > <xsl:template match="A|B|C|D" priority="2"> this one I've had times when I wanted to parameterize match patterns though. 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324659.html On 02/09/2012 06:14 PM, Wendell Piez wrote: > Evan Lenz's work on the "Carrot" syntax for XSLT, which you possibly saw > presented at Balisage, might give an interesting starting point for work my experiment w/ XSLT syntax: http://www.gerixsoft.com/sites/gerixsoft.com/files/json2xml.txt it is implemented using custom SAX parser that generates XSLT "on the fly", so XSLT processor does not need to be modified to accept this new syntax http://www.gerixsoft.com/blog/xslt/sdl-syntax --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324657.html Hi, On 2/9/2012 6:09 PM, Terence Kearns wrote: > Wow. Okay then. I guess it was fun while it lasted. I guess the > conditions aren't there anymore (for open source development of large > projects). > > I guess Apache Cocoon's fate has gone the same way. But Cocoon is still used, and the Cocoon users' list is still active. I'm not arguing with the basic point, nor even with the questioning of Cocoon's development activity (which I don't track).... > Personally, I think the volume of code cutters has increased, and the > percentage of "casual" coders has greatly incresed. XSLT 1.0 probably > couldn't get traction with casual coders who could only think > procedurally and it scared them off - leaving no perceivable demand > for the next XSLT interation from the code cutting masses. So the big > coding houses like IBM, Microsoft and Oracle have lost interest. > Personally, I think that's a shame. That XML is primarily useful as > high-level web service data packets (competing with JSON) is a > misconception. It might be the reality that this is how the market > sees it, but "the market is wrong" Living proof that market forces > don't follow technical superiority. I think much of this is true, yet don't forget that XML and XSLT are still healthy (very healthy as far as I can tell) in the space for which they were originally designed, namely publishing systems. Some publishing systems are content to stick with a single channel of output, such as print or the web. And if you're publishing only to the web, you can maintain your data in HTML and/or an HTML-facing CMS. But other publishers can't do this, or they need to insulate themselves, to whatever extent possible, from technological changes in target media, and XML/XSLT allow them to do this. Or they need to find efficiencies and scalability in data interchange and data longevity that they can only get through a careful separation of concerns across their workflows, which XML/XSLT allows them to engineer. If there's a significant part of the tech marketplace that doesn't even know this is going on, what does that say other than that the world is a big place? 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324654.html The simplified source file you posted was not well formed, also your email contained several xsl:template elements that were not contained in side xsl:stylesheet, please put some effort into running what you are about to post locally, seeing what (if anything) comes out and saying _exactly_ what's wrong with it. If I take the part of your email between <xsl:stylesheet and </xsl:stylesheet> as a stylesheet, fix your input file so it is well formed and run then through as xslt 1 processor I get Yes Article 1 Nekplooimeting 2005-04-01 Yes Article 2 Vlokkentest ? 2005-04-04 which is what I'd expect as you are just applying templates to all "dagboek/entry" elements. 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324653.html Sorry for the missing data. Here a simpliefied xslt with everything needed. <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" omit-xml-declaration="yes" encoding="UTF-8" indent="yes" /> <xsl:template match="/"> <xsl:apply-templates select="data" /> </xsl:template> <xsl:template match="data"> <xsl:apply-templates select="dagboek/entry"/> </xsl:template> </xsl:stylesheet> <xsl:template match="dagboek/entry" > <h3> <xsl:value-of select="titel" /> </h3> <xsl:apply-templates select="dagboek/entry[nieuwe-pagina = 'yes']" mode="pagegroup" /> <xsl:apply-templates select="tekst" /> </div> </xsl:template> <xsl:template match="entry" mode="pagegroup"> <xsl:apply-templates select=". | following-sibling::entry[not(nieuwe-pagina = 'yes') and preceding-sibling::entry[nieuwe-pagina = 'yes'][1] = current()]" /> </xsl:template> </xsl:stylesheet> <xsl:template match="tekst//p[starts-with(., 'FLOAT : ')]" priority="1"> <img class="float-left" src="{$workspace}/images/{substring-after(., 'FLOAT : ')}" /> </xsl:template> <xsl:template match="tekst//*"> <xsl:element name="{name()}"> <xsl:apply-templates select="* | @* | text()"/> </xsl:element> </xsl:template> <xsl:template match="tekst//@*"> <xsl:attribute name="{name(.)}"> <xsl:value-of select="."/> </xsl:attribute> </xsl:template> And here the simpliefied xml : <data> <dagboek> <section id="9" handle="dagboek">Dagboek</section> 41 <entry id="20"> <nieuwe-pagina>Yes</nieuwe-pagina> <tekst mode="formatte""> Article 1 </tekst> <titel handle="nekplooimeting">Nekplooimeting </titel> <datum time="00:00" weekday="5">2005-04-01</datum> </entry> <entry id="21"> <nieuwe-pagina>Yes</nieuwe-pagina> <tekst mode="formatted"> Article 2 </tekst> <titel handle="vlokkentest">Vlokkentest ?</titel> <datum time="19:16" weekday="1">2005-04-04</datum> </entry> </dagboek> </data> What I was expecting was a page where only the first arcticle and the article between the first article and the next article with <nieuwe-pagina = "yes"> is displayed. Now it's schowing both articles where I was expecting to see only the first article. ---------------------------------------- > Date: Fri, 10 Feb 2012 12:40:20 +0000 > From: davidc@nag.co.uk > To: xsl-list@lists.mulberrytech.com > CC: rwobben@hotmail.com > Subject: Re: [xsl] can this idea work ? > > On 10/02/2012 12:29, Roelof Wobben wrote: > > So I thought this xslt 1.0 could do the job : > > > > > > you haven't said what output you expected from the stylesheet or what > output you got, and we can't run the code you posted as it imports files > you have not posted. > > If the imported files are not relevant to your problem make a small > (without all the irrelevant text and elements) input file and a small > complete runnable xsl stylesheet and then say what output you got and > what output you expected/wanted. > > 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324652.html On 10/02/2012 14:17, Michael Kay wrote: > Perhaps the spelling correcter converts.... I think that's the one I use for xsl-list postings ________________________________________________________________________ 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324651.html >XML is still topping json by 18:1 ... although the trendlines are down, that is very common as concepts become mainstream (less people search for them because they already know) More to the point, people choose a more specific search term because the general term returns too much noise. I think this effect makes google trends very unreliable. (In any case, despite being in Prague, I refuse to believe that the top three languages for searches on XSLT are Czech, English, and Danish in that order - especially as most of the searches originate from India. Is there a large expatriate Czech community in Chennai? Perhaps the spelling correcter converts some Czech word for sex into "XSLT"?) Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324650.html On 10/02/2012 12:29, Roelof Wobben wrote: > So I thought this xslt 1.0 could do the job : > > you haven't said what output you expected from the stylesheet or what output you got, and we can't run the code you posted as it imports files you have not posted. If the imported files are not relevant to your problem make a small (without all the irrelevant text and elements) input file and a small complete runnable xsl stylesheet and then say what output you got and what output you expected/wanted. 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324646.html Hello, I have a new idea for my website. On every article which must be placed in a new page I enable a checkbox. So I have this xml : <?xml version="1.0" encoding="utf-8" ?> <data> <params> <today>2012-02-10</today> <current-time>08:58</current-time> <this-year>2012</this-year> <this-month>02</this-month> <this-day>10</this-day> <timezone>+01:00</timezone> <website-name>Tamara Wobben</website-name> <page-title>dagboek</page-title> <root>http://test.tamarawobben.nl</root> <workspace>http://test.tamarawobben.nl/workspace</workspace> <root-page>dagboek</root-page> <current-page>dagboek</current-page> <current-page-id>7</current-page-id> <current-path>/dagboek/2005/04/1/?debug</current-path> <parent-path>/</parent-path> <current-url>http://test.tamarawobben.nl/dagboek/2005/04/1/?debug</current-url> <upload-limit>2097152</upload-limit> <symphony-version>2.2.5</symphony-version> <year>2005</year> <month>04</month> <page>1</page> <cookie-username>xxxxxx</cookie-username> <cookie-pass>xxxxxxx</cookie-pass> <site-mode>live</site-mode> </params> <events /> <dagboek> <section id="9" handle="dagboek">Dagboek</section> <entry id="20"> <nieuwe-pagina>Yes</nieuwe-pagina> <tekst mode="formatted"><p>Alvast bloed laten prikken voor de tripletest. De uitstag is dan binnen als de nekplooimeting wordt gedaan. Sinds kort kan dat in het S.M.T. in Hengelo, dus dat is mooi meegenomen. Nog niet veel mensen weten dat je in mijn buik aan het groeien bent, maar ik had het al wel tegen een vriendin verteld en het leuke was dat ik de week erna een hele stapel broeken te leen kreeg en een stapel Wij jonge ouders. Dus lees ik volop. Heerlijk om in weg te dromen en ik ben benieuwd hoe jij eruit zult zien.</p> 44 45<p>FLOAT : echo.jpg </p> 46 47<p>De hoeveelheid vocht in jouw nek is meer dan gebruikelijk, het is 3,2 mm, met alle gegevens erbij wordt een kansberekening gemaakt voor het Downsyndroom. De uitslag is een kans van 1 op 24. Het lijkt niet veel maar toch. Verslagen verlaten we het ziekenhuis en in de trein wordt het mij teveel. De uitslag en het gezeur over de manier waarop de echo was geregeld werd me teveel en wat me al heel lang niet meer was overkomen gebeurt dan toch, ik zit te huilen in de trein.</p> 48 49<p>Terug op het werk vertel ik mijn collega’s wat er is gezegd en neem dan pauze, even de honden uitlaten. Thuis schrik ik van het bericht op het antwoordapparaat. Mijn gynaecoloog, Dr. Veenstra heeft gebeld, de uitslag van de tripletest is binnen en ze wil me zo snel mogelijk spreken. Uitslag binnen, dat kon toch niet. Ik snap er niets meer van en ga eerst met de honden lopen en moed verzamelen. Dr. Veenstra is er ’s middags niet en ik word doorverbonden met Dr. Gnodde. Hij verontschuldigd zich voor het feit dat ik deze informatie over de telefoon krijg, maar het is heel belangrijk. De uitslag van de tripletest is dat er een kans is van 1 op 30 op een kindje met het Downsyndroom. Echter, samen met de nekplooimeting wordt het een kans van 1 op 3! Als ik de telefoon neerleg is de grond onder mijn voeten weggeslagen. De honden voelen mijn verdriet en zitten dicht bij me. Ik bel jouw papa en spreek met hem af dat ik hem op kom halen zodra ik rustig ben, ik heb behoorlijk zitten huilen aan de telefoon.</p> 50 51<p>Terug op het werk zien mijn collega’s al dat niet goed gaat en ik vertel wat er is. Het werk wordt onder mijn handen weggepakt en ik moet je papa bellen. Hij is er heel snel en we gaan samen naar huis, een voordeel als je in het zelfde gebouw 52werkt.</p> </tekst> <titel handle="nekplooimeting">Nekplooimeting </titel> <datum time="00:00" weekday="5">2005-04-01</datum> </entry> <entry id="21"> <nieuwe-pagina>Yes</nieuwe-pagina> <tekst mode="formatted"><p>Er is veel gesproken over de echo, de vlokkentest en mijn angst hiervoor. Jouw papa en ik hebben besloten om het wel te doen, dan hebben we zekerheid. Ik heb het ziekenhuis gebeld en ik moet morgen naar het MST. Ik zie er als een berg tegenop.</p> 60 </tekst> <titel handle="vlokkentest">Vlokkentest ?</titel> <datum time="19:16" weekday="1">2005-04-04</datum> </entry> </dagboek> </data> So I thought this xslt 1.0 could do the job : <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:import href="../utilities/frontpage-article.xsl"/> <xsl:import href="../utilities/date-time.xsl"/> <xsl:template match="dagboek/entry" > <h3> <xsl:value-of select="titel" /> </h3> <div class="post-inner"> <div class="date-tab"> <span class="month"> <xsl:call-template name="format-date"> <xsl:with-param name="date" select="datum"/> <xsl:with-param name="format" select="'M'"/> </xsl:call-template> </span> <span class="day"> <xsl:call-template name="format-date"> <xsl:with-param name="date" select="datum"/> <xsl:with-param name="format" select="'d'"/> </xsl:call-template> </span> </div> <xsl:apply-templates select="dagboek/entry[nieuwe-pagina = 'yes']" mode="pagegroup" /> <xsl:apply-templates select="tekst" /> </div> </xsl:template> <xsl:template match="entry" mode="pagegroup"> <xsl:apply-templates select=". | following-sibling::entry[not(nieuwe-pagina = 'yes') and preceding-sibling::entry[nieuwe-pagina = 'yes'][1] = current()]" /> </xsl:template> </xsl:stylesheet> But it does not. It still places all the articles on 1 page. Can this idea work or did I made a stupid mistake ? Roelof --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324645.html ihe onwuka wrote: > Suppose the children of the context node are elements named A to Z. > > Then I declare a variable > > <xsl:variable name="alpha" select="A|B|C|D"/> > > Now i want to match on the complement of alpha. > > Can I say > > <xsl:template match="* except $alpha"/> Yes, with XSLT 2.0, not with 1.0. -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324644.html On 10/02/2012 11:31, ihe onwuka wrote: > Suppose the children of the context node are elements named A to Z. > > Then I declare a variable > > <xsl:variable name="alpha" select="A|B|C|D"/> > > Now i want to match on the complement of alpha. > > Can I say it would have been quicker just to try, but... > > <xsl:template match="* except $alpha"/> no that would be a legal xpath but not a pattern > or > <xsl:template match="*[not $alpha]"/> no, that's a syntax error so wouldn't run at all easiest is <xsl:template match="*"> the complement <xsl:template match="A|B|C|D" priority="2"> this one 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324643.html Suppose the children of the context node are elements named A to Z. Then I declare a variable <xsl:variable name="alpha" select="A|B|C|D"/> Now i want to match on the complement of alpha. Can I say <xsl:template match="* except $alpha"/> or <xsl:template match="*[not $alpha]"/> --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324642.html On Thu, 2012-02-09 at 11:14 -0500, Wendell Piez wrote: > Evan Lenz's work on the "Carrot" syntax for XSLT, which you possibly saw > presented at Balisage, might give an interesting starting point for work > on a compiler to write XQuery from XSLT 2.0. (Evan does go the other > way, from XQuery+Carrot into XSLT.) The hard part, I think (as Dr Kay has mentioned) is that XSLT has "match patterns" and XQuery does not. Interpreting XSLT in XQuery directly might be hard as a result. Or at least not very efficient. Preprocessing to convert might work. I remember having a conversation with Jerôme Siméon abuot the idea of making XPath expressions and node tests as first-class objects in XQuery, e.g. so you could pass them to functions as arguments, ask what they matched, etc. As it stands, apply-templates might involve something like (for $pattern in find-candidates($match-patterns, $mode, $here) order by $pattern/@priority return if matches($here, $pattern[1]) then $pattern else () )[1] for each node you try to match. Hmm, well, it's 7am so maybe there's a better way. If Dmitry thought about it for 30ms he'd probably find one. :-) Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324638.html Before the off-topic alarms go off: Quercus is quite mature.and has been demonstrated to run many major PHP packages out of the box. The Pear modules, which have native C components, might have spotty support (at a guess) but with the vast array of Java libraries readily available for everything under the sun (no pun intended), any shortfalls in Pear are easily compensated for. It does hint at a life for XSLT 2.0 and PHP. - michael dykman On Thu, Feb 9, 2012 at 10:36 PM, Terence Kearns <info@terencekearns.com> wrote: > Quercus looks promising. One of the things with PHP is it's huge > library of modules - many of which are included in the default distro. > I'll have to see if there are any important PHP modules which haven't > been imported to Quercus. Having said that, if there is a real need, > an alternative library may exist in Java. > > I am a big fan of the servlet containter architecture, and I vagely > recall resin being an awesome implementation - particularly for speed. > > Quercus might well be the way to go for a casual PHP coder who is > looking to make the move to Java. > > I'm tempted to port my PHP/XML framework ( > http://xao-php.sourceforge.net ) - binding it to the Quercus > implementation (and Saxon). > > I'd heard of something like this before, but had forgotten. The > implementation is probably quite mature by now. > > Cheers. > > > > On 10 February 2012 11:13, Michael Dykman <mdykman@gmail.com> wrote: >> Terence, >> >> Have you looked at Quercus? >> >> http://www.caucho.com/resin-3.0/quercus/ >> >> It's a highly performant PHP implementation implemented as a Java >> servlet.  I have seen benchmarks which suggest that it as fast as >> Enterprise PHP and extending it with Java methods is trivial.  If you >> like PHP (which I don't especially), you still have the opportunity of >> doing XSLT 2.0 in that environment. >> >> On Thu, Feb 9, 2012 at 6:09 PM, Terence Kearns <info@terencekearns.com> wrote: >>> >>> RIP my XML/PHP framework (for which my enthusiasm kinda died due to no >>> real XSLT2 support in PHP's roadmap). >>> >>> ...grateful for Saxon... >>> >>> >>> On 9 February 2012 22:34, Michael Kay <mike@saxonica.com> wrote: >>>> >>>>>> Does anyone know if PHP has it? >>>>> >>>>> Sadly, not yet (except via the Java bridge). No recent news from the LIBX* >>>>> project: http://www.explain.com.au/libx/. Perhaps Steve Ball found something >>>>> else to do with his weekends. I think the days of hobbyist implementations >>>>> of these technologies are past. >>>> >>>> This posting sort of sums it up: >>>> >>>> http://mail.explain.com.au/pipermail/libx/2011-September/000004.html >>>> >>>> I don't think you can write an XSLT 2.0 processor and have an unrelated day >>>> job. Most of the coding for Saxon's XSLT 2.0 processor was done when I was >>>> employed by Software AG full time on standards work, and I was spending >>>> about half my time on the standards and half on Saxon, with the full >>>> encouragement of my employer. I think we can forget about this project >>>> unless it finds a sponsor. >>>> >>>> >>>> Michael Kay >>>> Saxonica >>>> >>>> --~------------------------------------------------------------------ >>>> XSL-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> >>>> --~-- >>>> >>> >>> >>> >>> -- >>> http://TerenceKearns.com PHOTO.VIDEO | ABN 58705023254 | ph 0412 235 575 >>> >>> --~------------------------------------------------------------------ >>> XSL-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> >>> --~-- >>> >> >> >> >> -- >>  - michael dykman >>  - mdykman@gmail.com >> >>  May the Source be with 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> >> --~-- >> > > > > -- > http://TerenceKearns.com PHOTO.VIDEO | ABN 58705023254 | ph 0412 235 575 > > --~------------------------------------------------------------------ > XSL-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> > --~-- > --  - michael dykman  - mdykman@gmail.com  May the Source be with 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324636.html Quercus looks promising. One of the things with PHP is it's huge library of modules - many of which are included in the default distro. I'll have to see if there are any important PHP modules which haven't been imported to Quercus. Having said that, if there is a real need, an alternative library may exist in Java. I am a big fan of the servlet containter architecture, and I vagely recall resin being an awesome implementation - particularly for speed. Quercus might well be the way to go for a casual PHP coder who is looking to make the move to Java. I'm tempted to port my PHP/XML framework ( http://xao-php.sourceforge.net ) - binding it to the Quercus implementation (and Saxon). I'd heard of something like this before, but had forgotten. The implementation is probably quite mature by now. Cheers. On 10 February 2012 11:13, Michael Dykman <mdykman@gmail.com> wrote: > Terence, > > Have you looked at Quercus? > > http://www.caucho.com/resin-3.0/quercus/ > > It's a highly performant PHP implementation implemented as a Java > servlet.  I have seen benchmarks which suggest that it as fast as > Enterprise PHP and extending it with Java methods is trivial.  If you > like PHP (which I don't especially), you still have the opportunity of > doing XSLT 2.0 in that environment. > > On Thu, Feb 9, 2012 at 6:09 PM, Terence Kearns <info@terencekearns.com> wrote: >> >> RIP my XML/PHP framework (for which my enthusiasm kinda died due to no >> real XSLT2 support in PHP's roadmap). >> >> ...grateful for Saxon... >> >> >> On 9 February 2012 22:34, Michael Kay <mike@saxonica.com> wrote: >>> >>>>> Does anyone know if PHP has it? >>>> >>>> Sadly, not yet (except via the Java bridge). No recent news from the LIBX* >>>> project: http://www.explain.com.au/libx/. Perhaps Steve Ball found something >>>> else to do with his weekends. I think the days of hobbyist implementations >>>> of these technologies are past. >>> >>> This posting sort of sums it up: >>> >>> http://mail.explain.com.au/pipermail/libx/2011-September/000004.html >>> >>> I don't think you can write an XSLT 2.0 processor and have an unrelated day >>> job. Most of the coding for Saxon's XSLT 2.0 processor was done when I was >>> employed by Software AG full time on standards work, and I was spending >>> about half my time on the standards and half on Saxon, with the full >>> encouragement of my employer. I think we can forget about this project >>> unless it finds a sponsor. >>> >>> >>> Michael Kay >>> Saxonica >>> >>> --~------------------------------------------------------------------ >>> XSL-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> >>> --~-- >>> >> >> >> >> -- >> http://TerenceKearns.com PHOTO.VIDEO | ABN 58705023254 | ph 0412 235 575 >> >> --~------------------------------------------------------------------ >> XSL-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> >> --~-- >> > > > > -- >  - michael dykman >  - mdykman@gmail.com > >  May the Source be with 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> > --~-- > -- http://TerenceKearns.com PHOTO.VIDEO | ABN 58705023254 | ph 0412 235 575 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324635.html Terence, Have you looked at Quercus? http://www.caucho.com/resin-3.0/quercus/ It's a highly performant PHP implementation implemented as a Java servlet. I have seen benchmarks which suggest that it as fast as Enterprise PHP and extending it with Java methods is trivial. If you like PHP (which I don't especially), you still have the opportunity of doing XSLT 2.0 in that environment. On Thu, Feb 9, 2012 at 6:09 PM, Terence Kearns <info@terencekearns.com> wrote: > > RIP my XML/PHP framework (for which my enthusiasm kinda died due to no > real XSLT2 support in PHP's roadmap). > > ...grateful for Saxon... > > > On 9 February 2012 22:34, Michael Kay <mike@saxonica.com> wrote: >> >>>> Does anyone know if PHP has it? >>> >>> Sadly, not yet (except via the Java bridge). No recent news from the LIBX* >>> project: http://www.explain.com.au/libx/. Perhaps Steve Ball found something >>> else to do with his weekends. I think the days of hobbyist implementations >>> of these technologies are past. >> >> This posting sort of sums it up: >> >> http://mail.explain.com.au/pipermail/libx/2011-September/000004.html >> >> I don't think you can write an XSLT 2.0 processor and have an unrelated day >> job. Most of the coding for Saxon's XSLT 2.0 processor was done when I was >> employed by Software AG full time on standards work, and I was spending >> about half my time on the standards and half on Saxon, with the full >> encouragement of my employer. I think we can forget about this project >> unless it finds a sponsor. >> >> >> Michael Kay >> Saxonica >> >> --~------------------------------------------------------------------ >> XSL-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> >> --~-- >> > > > > -- > http://TerenceKearns.com PHOTO.VIDEO | ABN 58705023254 | ph 0412 235 575 > > --~------------------------------------------------------------------ > XSL-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> > --~-- > --  - michael dykman  - mdykman@gmail.com  May the Source be with 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324634.html Just for fun I tried google trends http://www.google.com/trends/?q=xslt,xquery,xml,json&ctab=0&geo=all&date=all&sort=3 XML is still topping json by 18:1 ... although the trendlines are down, that is very common as concepts become mainstream (less people search for them because they already know) -----Original Message----- From: Michael Kay [mailto:mike@saxonica.com] Sent: Thursday, February 09, 2012 6:37 PM To: xsl-list@lists.mulberrytech.com Subject: Re: [xsl] XSLT 2 processors >What is XSLT mainly being used for these days? Is it shrinking in use or growing? Nobody knows for sure. But I think usage has shifted from the trendy/cool/vocal end of the developer community to the serious corporate backroom space, which probably means it is making less noise but that usage is actually growing substantially. And it's not just for documents, where XML and XSLT are the only game in town; XML is still the workhorse for any data flow that crosses enterprise boundaries, and will remain so for many years if only because once entrenched, things like that don't change easily. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324633.html >What is XSLT mainly being used for these days? Is it shrinking in use or growing? Nobody knows for sure. But I think usage has shifted from the trendy/cool/vocal end of the developer community to the serious corporate backroom space, which probably means it is making less noise but that usage is actually growing substantially. And it's not just for documents, where XML and XSLT are the only game in town; XML is still the workhorse for any data flow that crosses enterprise boundaries, and will remain so for many years if only because once entrenched, things like that don't change easily. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324632.html > Where do you use it Mr. Welch? Various companies and sectors, including aerospace (BAE), health (MDConsult), finance (JPMC, Interactive Data), publishing (Elsevier, Macmillan), telecoms (Vodafone)... it's all pretty much the same work, just the text nodes are different. -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324631.html Wow. Okay then. I guess it was fun while it lasted. I guess the conditions aren't there anymore (for open source development of large projects). I guess Apache Cocoon's fate has gone the same way. Personally, I think the volume of code cutters has increased, and the percentage of "casual" coders has greatly incresed. XSLT 1.0 probably couldn't get traction with casual coders who could only think procedurally and it scared them off - leaving no perceivable demand for the next XSLT interation from the code cutting masses. So the big coding houses like IBM, Microsoft and Oracle have lost interest. Personally, I think that's a shame. That XML is primarily useful as high-level web service data packets (competing with JSON) is a misconception. It might be the reality that this is how the market sees it, but "the market is wrong" :-) Living proof that market forces don't follow technical superiority. Being a casual coder myself, I reckon if I was to return to development, it would have to be Java all the way - just so I could leverage Saxon - and keep my XML pipeline. RIP my XML/PHP framework (for which my enthusiasm kinda died due to no real XSLT2 support in PHP's roadmap). ...grateful for Saxon... On 9 February 2012 22:34, Michael Kay <mike@saxonica.com> wrote: > >>> Does anyone know if PHP has it? >> >> Sadly, not yet (except via the Java bridge). No recent news from the LIBX* >> project: http://www.explain.com.au/libx/. Perhaps Steve Ball found something >> else to do with his weekends. I think the days of hobbyist implementations >> of these technologies are past. > > This posting sort of sums it up: > > http://mail.explain.com.au/pipermail/libx/2011-September/000004.html > > I don't think you can write an XSLT 2.0 processor and have an unrelated day > job. Most of the coding for Saxon's XSLT 2.0 processor was done when I was > employed by Software AG full time on standards work, and I was spending > about half my time on the standards and half on Saxon, with the full > encouragement of my employer. I think we can forget about this project > unless it finds a sponsor. > > > Michael Kay > Saxonica > > --~------------------------------------------------------------------ > XSL-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> > --~-- > -- http://TerenceKearns.com PHOTO.VIDEO | ABN 58705023254 | ph 0412 235 575 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324630.html Sadly, the posting still applies. Implementing an XPath 2.0 + XSLT 2.0 processor is a relatively large engineering project. I always knew that when I started. People who work on HTML 5+CSS3, etc, are doing much smaller projects and hence make (apparent) progress a lot more quickly. Cheers, Steve Ball On 09/02/2012, at 11:34 PM, Michael Kay wrote: > >>> Does anyone know if PHP has it? >> Sadly, not yet (except via the Java bridge). No recent news from the LIBX* project: http://www.explain.com.au/libx/. Perhaps Steve Ball found something else to do with his weekends. I think the days of hobbyist implementations of these technologies are past. > This posting sort of sums it up: > > http://mail.explain.com.au/pipermail/libx/2011-September/000004.html > > I don't think you can write an XSLT 2.0 processor and have an unrelated day job. Most of the coding for Saxon's XSLT 2.0 processor was done when I was employed by Software AG full time on standards work, and I was spending about half my time on the standards and half on Saxon, with the full encouragement of my employer. I think we can forget about this project unless it finds a sponsor. > > Michael Kay > Saxonica > > --~------------------------------------------------------------------ > XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324629.html On 2/9/2012 11:59 AM, Andrew Welch wrote: > Nooooo not xml vs json.... :) There are plenty of opinions in the > various archives if you wanted to go over that old ground. > > > From an XSLT perspective, html5 should be just another output format > (assuming the xml syntax version of html5 is covered by the existing > xml output method) Sorry, but forget JSON. What is XSLT mainly being used for these days? Is it shrinking in use or growing? I notice Michale Kay's list of XSLT2 processors does not include anything from Microsoft, so I assume they are still not going for it: Saxon, Altova, IBM, Intel, MarkLogic, XQSharp. Saxon-CE (client edition) for the browser now in beta. Gestalt still exists but development has ceased. I use XSLT for tech pubs-type documentation systems and find it very useful. Where do you use it Mr. Welch? 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324628.html > What are the strong areas for XML that look like they will remain? Even > Douglas Crockford (main promoter of JSON) says that XML is better for > documents than JSON. What else? XML databases? Nooooo not xml vs json.... :) There are plenty of opinions in the various archives if you wanted to go over that old ground. From an XSLT perspective, html5 should be just another output format (assuming the xml syntax version of html5 is covered by the existing xml output method) -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324627.html On 2/9/2012 10:14 AM, Andrew Welch wrote: >> Maybe all the hobbyists have gotten excited by HTML5/CSS3/JavaScript. "Cool" >> and "new" are the Queen Bee of the hive. > html5 and css3 really are amazing... very, very impressive. Agreed, I generally like what's going on with these. It will be very interesting to see what effect this has on our XML communities. HTML5 makes it easier to use XML like SVG and MathML. But JSON seems to be wiping out XML use in things like Ajax and other web development areas. XHTML has no more official future. What are the strong areas for XML that look like they will remain? Even Douglas Crockford (main promoter of JSON) says that XML is better for documents than JSON. What else? XML databases? 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324626.html > Maybe all the hobbyists have gotten excited by HTML5/CSS3/JavaScript. "Cool" > and "new" are the Queen Bee of the hive. html5 and css3 really are amazing... very, very impressive. -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324625.html A browser game, implemented in XSLT 2.0 (using Saxon CE): http://publishinggeekly.com/wp-content/uploads/2012/02/floodit-xsl/floodit.html ;) -- Gerrit Imsieke Geschäftsführer / Managing Director le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 110, Fax +49 341 355356 510 gerrit.imsieke@le-tex.de, http://www.le-tex.de Registergericht / Commercial Register: Amtsgericht Leipzig Registernummer / Registration Number: HRB 24930 Geschäftsführer: Gerrit Imsieke, Svea Jelonek, Thomas Schmidt, Dr. Reinhard Vöckler --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324624.html On 2/9/2012 4:16 AM, Michael Kay wrote: >> Does anyone know if PHP has it? > Sadly, not yet (except via the Java bridge). No recent news from the > LIBX* project: http://www.explain.com.au/libx/. Perhaps Steve Ball > found something else to do with his weekends. I think the days of > hobbyist implementations of these technologies are past. >> > Michael Kay > Saxonica Maybe all the hobbyists have gotten excited by HTML5/CSS3/JavaScript. "Cool" and "new" are the Queen Bee of the hive. 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324623.html On 09/02/2012 16:14, Wendell Piez wrote: > Liam, > > Evan Lenz's work on the "Carrot" syntax for XSLT, which you possibly > saw presented at Balisage, might give an interesting starting point > for work on a compiler to write XQuery from XSLT 2.0. (Evan does go > the other way, from XQuery+Carrot into XSLT.) > Given an open-source XQuery engine, I suspect an easier approach is to write a front-end that compiles XSLT into the abstract tree representation used by the XQuery processor, augmented with some custom functions to do pattern matching and template despatch, and a few internal code tweaks to handle the cases where XSLT and XQuery behave almost the same but not quite, e.g. handling of duplicate attributes (dynamic error in XQuery, use the last in XSLT). Generating XQuery code that handles that kind of difference is likely to impose a nasty performance penalty. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324622.html Liam, Evan Lenz's work on the "Carrot" syntax for XSLT, which you possibly saw presented at Balisage, might give an interesting starting point for work on a compiler to write XQuery from XSLT 2.0. (Evan does go the other way, from XQuery+Carrot into XSLT.) Would this be, like, totally perverse? On the one hand, bizarre and (in a just world) unnecessary. But on the other, it would as you suggest open up XSLT as an option on a wide range of platforms. An excellent Balisage paper would be on your XSLT -> XQuery compiler implemented in XSLT, which you compiled into XQuery for distribution on XQuery platforms so they could support XSLT. (Subsequent papers would be on optimizing this handstand so it actually worked tolerably well?) Okay I'll stop now. http://balisage.net/Proceedings/vol7/html/Lenz01/BalisageVol7-Lenz01.html Cheers, Wendell On 2/9/2012 8:54 AM, Liam R E Quin wrote: > On Thu, 2012-02-09 at 12:34 +0000, Michael Kay wrote: >> [...] > >> Perhaps Steve Ball >>> found something else to do with his weekends. I think the days of >>> hobbyist implementations of these technologies are past. >> This posting sort of sums it up: >> >> http://mail.explain.com.au/pipermail/libx/2011-September/000004.html > > Large open source projects generally need a community, or someone with a > lot of wisdom and generosity and dedication and focus, or (best) both. > I agree 100%. > > On the other hand, a C (not C++) implementation would bring XSLT 2 a lot > closer to PHP, Python, Perl, JavaScript, etc. Or maybe even a > translation into XQuery, hmmm... -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324621.html On Thu, 2012-02-09 at 12:34 +0000, Michael Kay wrote: > [...] > Perhaps Steve Ball > > found something else to do with his weekends. I think the days of > > hobbyist implementations of these technologies are past. > This posting sort of sums it up: > > http://mail.explain.com.au/pipermail/libx/2011-September/000004.html Large open source projects generally need a community, or someone with a lot of wisdom and generosity and dedication and focus, or (best) both. I agree 100%. On the other hand, a C (not C++) implementation would bring XSLT 2 a lot closer to PHP, Python, Perl, JavaScript, etc. Or maybe even a translation into XQuery, hmmm... Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324620.html > Interesting. How exactly does that work? The best answer is: Try it. The "current statement" marker moves from one subexpression to another when stepping through. Cheers, Dimitre On Thu, Feb 9, 2012 at 5:53 AM, TW <zupftom@googlemail.com> wrote: > 2012/2/9 Dimitre Novatchev <dnovatchev@gmail.com>: >>> I like pure XPath solutions because they are less verbose, but I find >>> "full" XSLT less restricting and easier to debug (especially when I >>> want to check what variable holds what value). >> >> Since about 6 months oXygen has implemented stepping through an XPath >> expression (not sure about setting breakpoints). Thus there should be >> no difference in debugging XPath code and XSLT code with oXygen. >> > > Interesting.  How exactly does that work? > > Thomas 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> > --~-- > -- 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 ------------------------------------- To avoid situations in which you might make mistakes may be the biggest mistake of all ------------------------------------ Quality means doing it right when no one is looking. ------------------------------------- You've achieved success in your field when you don't know whether what you're doing is work or play ------------------------------------- Facts do not cease to exist because they are ignored. ------------------------------------- I finally figured out the only reason to be alive is to enjoy it. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324619.html 2012/2/9 Dimitre Novatchev <dnovatchev@gmail.com>: >> I like pure XPath solutions because they are less verbose, but I find >> "full" XSLT less restricting and easier to debug (especially when I >> want to check what variable holds what value). > > Since about 6 months oXygen has implemented stepping through an XPath > expression (not sure about setting breakpoints). Thus there should be > no difference in debugging XPath code and XSLT code with oXygen. > Interesting. How exactly does that work? Thomas 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324618.html Michael Kay wrote: > On 09/02/2012 11:50, Terence Kearns wrote: >> It seems I like to check in every few years on this list. I haven't >> cut code for years. >> >> So how's support for XSLT2 these days? > Saxon, Altova, IBM, Intel, MarkLogic, XQSharp. It seems XQSharp is now called XmlPrime. Does anyone here know whether Intel's XSLT 2.0 processor got beyond its beta status (http://software.intel.com/en-us/articles/intel-soa-expressway-xslt-20-processor/)? -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324617.html > I like pure XPath solutions because they are less verbose, but I find > "full" XSLT less restricting and easier to debug (especially when I > want to check what variable holds what value). Since about 6 months oXygen has implemented stepping through an XPath expression (not sure about setting breakpoints). Thus there should be no difference in debugging XPath code and XSLT code with oXygen. Cheers, Dimitre Novatchev. On Wed, Feb 8, 2012 at 11:59 PM, TW <zupftom@googlemail.com> wrote: > Hi all, > > in XSLT 2.0, I quite often find that I can do things using either > XPath or XSLT constructs.  For example, in a step-by-step calculation > I define a number of variables, either with <xsl:variable> or XPath > "for $x in y" expressions.  I can use <xsl:choose> or XPath's > if/then/else (single or chained).  Sometimes a goal can be achieved > with either <xsl:for-each>/<xsl:sort> and more complex sort criteria > and return values, or max()/min() and some conditional treatment. > > I like pure XPath solutions because they are less verbose, but I find > "full" XSLT less restricting and easier to debug (especially when I > want to check what variable holds what value).  But how does it look > performance-wise?  Is there a valid rule of thumb what constructs are > cheaper in general?  Do XSLT constructs maybe have an overhead that > XPath ones don't? > > Thomas 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> > --~-- > -- 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 ------------------------------------- To avoid situations in which you might make mistakes may be the biggest mistake of all ------------------------------------ Quality means doing it right when no one is looking. ------------------------------------- You've achieved success in your field when you don't know whether what you're doing is work or play ------------------------------------- Facts do not cease to exist because they are ignored. ------------------------------------- I finally figured out the only reason to be alive is to enjoy it. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324616.html >> Does anyone know if PHP has it? > Sadly, not yet (except via the Java bridge). No recent news from the > LIBX* project: http://www.explain.com.au/libx/. Perhaps Steve Ball > found something else to do with his weekends. I think the days of > hobbyist implementations of these technologies are past. This posting sort of sums it up: http://mail.explain.com.au/pipermail/libx/2011-September/000004.html I don't think you can write an XSLT 2.0 processor and have an unrelated day job. Most of the coding for Saxon's XSLT 2.0 processor was done when I was employed by Software AG full time on standards work, and I was spending about half my time on the standards and half on Saxon, with the full encouragement of my employer. I think we can forget about this project unless it finds a sponsor. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324615.html On 09/02/2012 11:50, Terence Kearns wrote: > It seems I like to check in every few years on this list. I haven't > cut code for years. > > So how's support for XSLT2 these days? Saxon, Altova, IBM, Intel, MarkLogic, XQSharp. Saxon-CE (client edition) for the browser now in beta. Gestalt still exists but development has ceased. > Does anyone know if PHP has it? Sadly, not yet (except via the Java bridge). No recent news from the LIBX* project: http://www.explain.com.au/libx/. Perhaps Steve Ball found something else to do with his weekends. I think the days of hobbyist implementations of these technologies are past. > Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324614.html It seems I like to check in every few years on this list. I haven't cut code for years. So how's support for XSLT2 these days? Does anyone know if PHP has it? Is there a definitive list of XSLT2 processors somewhere? Also, does anyone know what happened to Apache Cocoon? They have been at v3 for years now and only seem to have an alpha release. Looks like it's all just died off... --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324613.html On 09/02/2012 10:22, David Carlisle wrote: > On 09/02/2012 09:54, Clint Redwood wrote: > > I also note that the xpath function "round" doesn't have any > > precision associated with it, so I can't just count the decimal > > places of the shorter value and round the longer to that precision. > > > yes not sure why they didn't add a precision argument. > round-to-half-even does have a precision argument so you could use > that if that rounding is acceptable, or if you want to use round you > can of course scale by a suitable power of 10 to bring the precisions > into play. > A second argument to round() has been added in XPath 3.0. Mind you, since it's in terms of decimal places, it can cause confusion when used with double or float data types - I would recommend only using it with xs:decimal. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324612.html On 09/02/2012 09:54, Clint Redwood wrote: > I also note that the xpath function "round" doesn't have any > precision associated with it, so I can't just count the decimal > places of the shorter value and round the longer to that precision. yes not sure why they didn't add a precision argument. round-to-half-even does have a precision argument so you could use that if that rounding is acceptable, or if you want to use round you can of course scale by a suitable power of 10 to bring the precisions into play. David -- google plus: https:/profiles.google.com/d.p.carlisle ________________________________________________________________________ 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324611.html Thanks to all for your advice. That helps deciding what to use in what situation. Thomas W. 2012/2/9 Andrew Welch <andrew.j.welch@gmail.com>: >> I like pure XPath solutions because they are less verbose, but I find >> "full" XSLT less restricting and easier to debug (especially when I >> want to check what variable holds what value). > > ...and insert additional instructions like xsl:message or comments, or > allow refactorings at certain points like an apply-templates instead > of just getting the value. > > My general guide is use XPath for simple tasks, say an if-then-else, > but when its get past trivial, eg if-then-else-if-then-else, switch to > the longer winded choose/when, as your future self with thank you for > it. > > > -- > Andrew Welch > http://andrewjwelch.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> > --~-- > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324610.html On 09/02/2012 09:21, Clint Redwood wrote: > Hi! > > I've a slightly awkward comparison, where I have two numbers of differing precisions, and I want to regard them as the same if the less preicse is the more precise rounded down to the same precision. > > Examples are: > 17.166666666666668 ~= 17.1666666666667 > and > 8.333333333333334 ~= 8.33333333333333 > > Unfortunately, the precision is not always the same for all the numbers I'm trying to compare. > > I just wondered if anyone on this list had done anything similar, and had a good way of doing it, while I try and figure out a suitable way to do it. > > Yours, > > Clint Redwood. > > Presumably by "precision" you mean the number of decimal digits in the lexical form of the number. That means that trailing zero digits change the result, and since trailing zeroes are ignored for all the system-supplied numeric data types, it means you are outside the range of what the system data types can do. Drafts of XSD 1.1 included a "precision decimal" data type that was intended to meet this need - but it only defined the lexical and value space of the type, not the arithmetic rules for comparing and calculating with these values (which is why it was dropped from the final spec). I think in your position I would represent the values as elements of the form <value precision="12">17.16666667</value>, and then write your own function library with operations for comparing and calculating on these values. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324609.html > I like pure XPath solutions because they are less verbose, but I find > "full" XSLT less restricting and easier to debug (especially when I > want to check what variable holds what value). ...and insert additional instructions like xsl:message or comments, or allow refactorings at certain points like an apply-templates instead of just getting the value. My general guide is use XPath for simple tasks, say an if-then-else, but when its get past trivial, eg if-then-else-if-then-else, switch to the longer winded choose/when, as your future self with thank you for it. -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324608.html With performance questions, it always depends on the processor. In Saxon 6, like most other XSLT 1.0 processors I have seen, the XSLT and XPath engines were very separate; the boundary between the two languages was very evident in the internal engine, both compile time and run-time. With this architecture, there might well be performance differences between equivalent XSLT and XPath constructs. In Saxon 9, XSLT and XPath code compile to a single integrated expression tree, which is optimized and executed as a whole without concern for which parts originated as XSLT and which as XPath. So, for example, an XPath "if-then-else" will typically generate exactly the same code as an XSLT xsl:choose. The code generated by the xsl:for-each instruction is exactly the same as the code for the "/" operator in the case where the rhs has an atomic type. So you can safely make your coding decisions on what reads well, rather than what performs well. Of course, other XSLT 2.0 processors may differ. If you want to improve both the readability and the performance of your code, as well as improving ease of debugging, the single best thing you can do is to declare the types of your variables and parameters as precisely as possible. Michael Kay Saxonica On 09/02/2012 07:59, TW wrote: > Hi all, > > in XSLT 2.0, I quite often find that I can do things using either > XPath or XSLT constructs. For example, in a step-by-step calculation > I define a number of variables, either with<xsl:variable> or XPath > "for $x in y" expressions. I can use<xsl:choose> or XPath's > if/then/else (single or chained). Sometimes a goal can be achieved > with either<xsl:for-each>/<xsl:sort> and more complex sort criteria > and return values, or max()/min() and some conditional treatment. > > I like pure XPath solutions because they are less verbose, but I find > "full" XSLT less restricting and easier to debug (especially when I > want to check what variable holds what value). But how does it look > performance-wise? Is there a valid rule of thumb what constructs are > cheaper in general? Do XSLT constructs maybe have an overhead that > XPath ones don't? > > Thomas 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> > --~-- > > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324607.html Hi David, I'm comparing data loaded into a system with the values extracted from that system. Not all the numbers are the same precision, but it would seem that the system is rounding slightly less than XSL treats as double precision. I'm already casting the two values to xs:double to carry out the comparison, but that is still regarding the values as different. The comparision I'd like to make ideally is "Is the value A the same as B if A is rounded to the same precision that B is stated.". I've considered comparing as float, but I think that may not really have sufficient precision. I also note that the xpath function "round" doesn't have any precision associated with it, so I can't just count the decimal places of the shorter value and round the longer to that precision. Yours, Clint. -----Original message----- To: xsl-list@lists.mulberrytech.com; CC: Clint Redwood <clint@screwtape.co.uk>; From: David Carlisle <davidc@nag.co.uk> Sent: Thu 09-02-2012 09:40 Subject: Re: [xsl] Comparing numbers with different precisions > On 09/02/2012 09:24, Clint Redwood wrote: > > Hi! > > > > I've a slightly awkward comparison, where I have two numbers of > > differing precisions, and I want to regard them as the same if the > > less preicse is the more precise rounded down to the same precision. > > > > Examples are: 17.166666666666668 ~= 17.1666666666667 and > > 8.333333333333334 ~= 8.33333333333333 > > > > Unfortunately, the precision is not always the same for all the > > numbers I'm trying to compare. > > > > I just wondered if anyone on this list had done anything similar, and > > had a good way of doing it, while I try and figure out a suitable way > > to do it. > > > > Yours, > > > > Clint Redwood. > > How big are your precisions? in particular do you want xpath to treat > then as doubles (which will mean that anything after 16 or so places > will be lost anyway) and you can just use double precision numeric > functions such as round to deal with the rounding, or do you need > arbitrary precision decimals or (equivalently srings0 and expect to do > teh rounding "by hand". > > 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> > --~-- > > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324606.html On 09/02/2012 09:24, Clint Redwood wrote: > Hi! > > I've a slightly awkward comparison, where I have two numbers of > differing precisions, and I want to regard them as the same if the > less preicse is the more precise rounded down to the same precision. > > Examples are: 17.166666666666668 ~= 17.1666666666667 and > 8.333333333333334 ~= 8.33333333333333 > > Unfortunately, the precision is not always the same for all the > numbers I'm trying to compare. > > I just wondered if anyone on this list had done anything similar, and > had a good way of doing it, while I try and figure out a suitable way > to do it. > > Yours, > > Clint Redwood. How big are your precisions? in particular do you want xpath to treat then as doubles (which will mean that anything after 16 or so places will be lost anyway) and you can just use double precision numeric functions such as round to deal with the rounding, or do you need arbitrary precision decimals or (equivalently srings0 and expect to do teh rounding "by hand". 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324605.html On 09/02/2012 07:59, TW wrote: > Do XSLT constructs maybe have an overhead that XPath ones don't? Michael KnowsTheseThings, but I'll hazard an answer anyway. if you look at Xquery syntax which is basically just an xpath-like syntax for parts of XSLT, and the fact that saxon (at least) compiles xquery and xslt (and xpath) down to the same internal representation, I would expect that there is negligible difference in compilation time and literally no difference in run time behaviour when the xpath and xslt are really doing the same thing. 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324604.html Hi! I've a slightly awkward comparison, where I have two numbers of differing precisions, and I want to regard them as the same if the less preicse is the more precise rounded down to the same precision. Examples are: 17.166666666666668 ~= 17.1666666666667 and 8.333333333333334 ~= 8.33333333333333 Unfortunately, the precision is not always the same for all the numbers I'm trying to compare. I just wondered if anyone on this list had done anything similar, and had a good way of doing it, while I try and figure out a suitable way to do it. Yours, Clint Redwood. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324603.html Hi! I've a slightly awkward comparison, where I have two numbers of differing precisions, and I want to regard them as the same if the less preicse is the more precise rounded down to the same precision. Examples are: 17.166666666666668 ~= 17.1666666666667 and 8.333333333333334 ~= 8.33333333333333 Unfortunately, the precision is not always the same for all the numbers I'm trying to compare. I just wondered if anyone on this list had done anything similar, and had a good way of doing it, while I try and figure out a suitable way to do it. Yours, Clint Redwood. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324602.html Hi all, in XSLT 2.0, I quite often find that I can do things using either XPath or XSLT constructs. For example, in a step-by-step calculation I define a number of variables, either with <xsl:variable> or XPath "for $x in y" expressions. I can use <xsl:choose> or XPath's if/then/else (single or chained). Sometimes a goal can be achieved with either <xsl:for-each>/<xsl:sort> and more complex sort criteria and return values, or max()/min() and some conditional treatment. I like pure XPath solutions because they are less verbose, but I find "full" XSLT less restricting and easier to debug (especially when I want to check what variable holds what value). But how does it look performance-wise? Is there a valid rule of thumb what constructs are cheaper in general? Do XSLT constructs maybe have an overhead that XPath ones don't? Thomas 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324601.html As usual, there is always clear and meaningful explanation. Thanks! On Wed, Feb 8, 2012 at 4:58 PM, Michael Kay <mike@saxonica.com> wrote: > You don't have a template rule that matches the document node (/) in mode > navigation-special_paint-selected, so when the recursion reaches the root, > the built-in template for document nodes is invoked. The built-in template > rule applies-templates to its children, so you oscillate infinitely between > the root document node and its element child. The solution is to add a rule > for match="/" that does nothing. > > Michael Kay > Saxonica > > > On 08/02/2012 22:50, Karl Stubsjoen wrote: >> >> This recursion template is failing.  I'm getting the error, too many >> recursions...  I would expect that when I get to the root element it >> would stop recursing.  I guess I need a test for root element. >> Karl.. >> >>     <xsl:template match="*" mode="navigation-special_paint-selected"> >>         <xsl:param name="node-id"/> >>         <xsl:choose> >>             <xsl:when test="generate-id() = $node-id"> >>                 <xsl:attribute name="background">#eee</xsl:attribute> >>             </xsl:when> >>             <xsl:otherwise> >>                 <xsl:apply-templates select="parent::node()" >> mode="navigation-special_paint-selected"> >>                     <xsl:with-param name="node-id" select="$node-id"/> >>                 </xsl:apply-templates> >>             </xsl:otherwise> >>         </xsl:choose> >>     </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> >> --~-- >> >> > > > --~------------------------------------------------------------------ > XSL-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> > --~-- > -- Karl Stubsjoen MeetScoresOnline.com (602) 845-0006 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324600.html On 09/02/2012 00:04, Costello, Roger L. wrote: > So, the definition of f is this sequence: items[1], f(items[position() gt 1] union g(items[1]) > > What name would you call this function? I want something more descriptive than " f " > If I created an object by nailing four pieces of wood together, I would name it according to the purpose of the artefact: why do I think four pieces of wood nailed together in this particular way would be useful to anyone? For example, I might call it a wine rack if it were well suited to that purpose. You've described a function in terms of how you implemented it, but you haven't given us any clues as to what it might be good for, and that's what makes it hard to name. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324599.html Hi Folks, I created a higher-order function. I will refer to the function as: f The argument to f is a sequence of items: f (items) Processing items[1] may produce/generate more items. After outputting the first item, f is applied to the remaining items plus g(item[1]), where g is a function applied to the first item. So, the definition of f is this sequence: items[1], f(items[position() gt 1] union g(items[1]) What name would you call this function? I want something more descriptive than " f " /Roger --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324598.html You don't have a template rule that matches the document node (/) in mode navigation-special_paint-selected, so when the recursion reaches the root, the built-in template for document nodes is invoked. The built-in template rule applies-templates to its children, so you oscillate infinitely between the root document node and its element child. The solution is to add a rule for match="/" that does nothing. Michael Kay Saxonica On 08/02/2012 22:50, Karl Stubsjoen wrote: > This recursion template is failing. I'm getting the error, too many > recursions... I would expect that when I get to the root element it > would stop recursing. I guess I need a test for root element. > Karl.. > > <xsl:template match="*" mode="navigation-special_paint-selected"> > <xsl:param name="node-id"/> > <xsl:choose> > <xsl:when test="generate-id() = $node-id"> > <xsl:attribute name="background">#eee</xsl:attribute> > </xsl:when> > <xsl:otherwise> > <xsl:apply-templates select="parent::node()" > mode="navigation-special_paint-selected"> > <xsl:with-param name="node-id" select="$node-id"/> > </xsl:apply-templates> > </xsl:otherwise> > </xsl:choose> > </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> > --~-- > > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324597.html Hi again, On 2/8/2012 6:05 PM, David Carlisle wrote: >> <xsl:template match="*" mode="navigation-special_paint-selected"> >> <xsl:param name="node-id"/> >> <xsl:choose> >> <xsl:when test="generate-id() = $node-id"> >> <xsl:attribute name="background">#eee</xsl:attribute> >> </xsl:when> >> <xsl:otherwise> >> <xsl:apply-templates select="parent::node()" >> mode="navigation-special_paint-selected"> >> <xsl:with-param name="node-id" select="$node-id"/> >> </xsl:apply-templates> >> </xsl:otherwise> >> </xsl:choose> >> </xsl:template> >> > because you have used parent::node() (which could more simply be written > as ..) rather than parent::* then if it doesn't find the $node-id it > will reach / and then (because your template only matches * not /) it > will apply the default template to / which will apply templates to its > element child, hitting this template again and looping forever. > cahanging the match to "*|/" should fix it. As I thought immediately after hitting "send" ... a slightly neater solution. Or apply-templates select="parent::*", as David also almost says. 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324596.html Karl, Unless you have a template to match the root in this mode, it will apply templates to its children in this mode ... and you will recurse back to the root etc. Try adding <xsl:template match="/" mode="navigation-special_paint-selected"/> Cheers, Wendell On 2/8/2012 5:50 PM, Karl Stubsjoen wrote: > This recursion template is failing. I'm getting the error, too many > recursions... I would expect that when I get to the root element it > would stop recursing. I guess I need a test for root element. > Karl.. > > <xsl:template match="*" mode="navigation-special_paint-selected"> > <xsl:param name="node-id"/> > <xsl:choose> > <xsl:when test="generate-id() = $node-id"> > <xsl:attribute name="background">#eee</xsl:attribute> > </xsl:when> > <xsl:otherwise> > <xsl:apply-templates select="parent::node()" > mode="navigation-special_paint-selected"> > <xsl:with-param name="node-id" select="$node-id"/> > </xsl:apply-templates> > </xsl:otherwise> > </xsl:choose> > </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> > --~-- > > -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324594.html On 08/02/2012 22:50, Karl Stubsjoen wrote: > This recursion template is failing. I'm getting the error, too many > recursions... I would expect that when I get to the root element it > would stop recursing. I guess I need a test for root element. > Karl.. > > <xsl:template match="*" mode="navigation-special_paint-selected"> > <xsl:param name="node-id"/> > <xsl:choose> > <xsl:when test="generate-id() = $node-id"> > <xsl:attribute name="background">#eee</xsl:attribute> > </xsl:when> > <xsl:otherwise> > <xsl:apply-templates select="parent::node()" > mode="navigation-special_paint-selected"> > <xsl:with-param name="node-id" select="$node-id"/> > </xsl:apply-templates> > </xsl:otherwise> > </xsl:choose> > </xsl:template> > because you have used parent::node() (which could more simply be written as ..) rather than parent::* then if it doesn't find the $node-id it will reach / and then (because your template only matches * not /) it will apply the default template to / which will apply templates to its element child, hitting this template again and looping forever. cahanging the match to "*|/" should fix it. David -- google plus: https:/profiles.google.com/d.p.carlisle --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324595.html This recursion template is failing. I'm getting the error, too many recursions... I would expect that when I get to the root element it would stop recursing. I guess I need a test for root element. Karl.. <xsl:template match="*" mode="navigation-special_paint-selected"> <xsl:param name="node-id"/> <xsl:choose> <xsl:when test="generate-id() = $node-id"> <xsl:attribute name="background">#eee</xsl:attribute> </xsl:when> <xsl:otherwise> <xsl:apply-templates select="parent::node()" mode="navigation-special_paint-selected"> <xsl:with-param name="node-id" select="$node-id"/> </xsl:apply-templates> </xsl:otherwise> </xsl:choose> </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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324593.html At 2012-02-09 03:46 +0530, ram wrote: >it doesn't worked for me. Can you send across your code for the >expected result. I need to leave my keyboard for the day, so I won't have the chance to respond to your response to my earlier request for guidance as to the problems you are experiencing. I hope the code below helps ... I don't know if it will. . . . . . . . Ken t:\ftemp>type ram.xsl <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" exclude-result-prefixes="soapenv" version="1.0"> <xsl:template match="node()|@*"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> <xsl:template match="soapenv:Header"> <xsl:copy> <xsl:copy-of select="@*"/> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>abcd</wsse:Username> <wsse:Password>ramkurra</wsse:Password> </wsse:UsernameToken> </wsse:Security> </xsl:copy> </xsl:template> </xsl:stylesheet> t:\ftemp>type ram1.xml <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:con1="http://abc.com/DefService/" > <soapenv:Header> </soapenv:Header> <soapenv:Body> <con1:GetDefinition> <!--Optional:--> <con1:Request><con1:Id/> </con1:Request> </con1:GetDefinition> </soapenv:Body> </soapenv:Envelope> t:\ftemp>call xslt ram1.xml ram.xsl ram1.out t:\ftemp>type ram1.out <?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:con1="http://abc.com/DefService/"> <soapenv:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsse:UsernameToken><wsse:Username>abcd</wsse:Username><wsse:Password>ramkurra</wsse:Password></wsse:UsernameToken></wsse:Security></soapenv:Header> <soapenv:Body> <con1:GetDefinition> <!--Optional:--> <con1:Request><con1:Id/> </con1:Request> </con1:GetDefinition> </soapenv:Body> </soapenv:Envelope> t:\ftemp>type ram2.xml <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:con1="http://abc.com/DefService/" > <s:Header> </s:Header> <s:Body> <con1:GetDefinition> <!--Optional:--> <con1:Request><con1:Id/> </con1:Request> </con1:GetDefinition> </s:Body> </s:Envelope> t:\ftemp>call xslt ram2.xml ram.xsl ram2.out t:\ftemp>type ram2.out <?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:con1="http://abc.com/DefService/"> <s:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><wsse:UsernameToken><wsse:Username>abcd</wsse:Username><wsse:Password>ramkurra</wsse:Password></wsse:UsernameToken></wsse:Security></s:Header> <s:Body> <con1:GetDefinition> <!--Optional:--> <con1:Request><con1:Id/> </con1:Request> </con1:GetDefinition> </s:Body> </s:Envelope> t:\ftemp>rem Done! -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324592.html At 2012-02-09 03:46 +0530, you wrote: >it doesn't worked for me. Where doesn't it work for you? Wendell made the same recommendation as I did regarding the use of <xsl:copy>. Please give me some guidance as to where you need help with the approach we've recommended. . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324591.html If I could clarify Wendell's response a little: XSLT 1.0 in general allows the XSLT processor (or more specifically, the serializer) to use whatever prefixes it wants - though in practice, processors only take advantage of this in edge cases. XSLT 2.0 makes the choice of prefix predictable in the vast majority of cases: for example if you have a literal result element <p:xyz> in the stylesheet, then the prefix p will be used in the output. The reason for this change is two-fold: firstly, XML is designed to be human-readable, and prefixes matter to human readers. Secondly, prefixes can be used in content, for example the infamous xsi:type="my:ownType". This only works if there is a declaration for the prefix "my" in the document, so the XSLT author needs to be able to guarantee that "my" will not be replaced by "your". Michael Kay Saxonica On 08/02/2012 22:01, Wendell Piez wrote: > Ram, > > Maybe you want to use xsl:copy, which may do better for you. Most > processors, when copying an element, will use the same prefix as the > input document uses. > > Or it may not: as Ken says, processors are not obliged to respect > prefixes since a prefix is not properly part of the name, as formally > defined; it is only a (local) binding mechanism. > > If you are answering a requirement from a partner who does not > understand this, you can, in XSLT 2.0, go to considerably more work to > construct elements with namespaces, names and their prefixes generated > dynamically, using XPath functions such as name(), > prefix-from-QName(), and namespace-uri-for-prefix(). An XSLT > stylesheet could generate a new header using whatever prefix the input > uses, whatever it is -- although such a stylesheet will look pretty > mysterious to the uninitiated. > > But this is not trivial to do, and a lot of trouble to go to for > something that matters only because someone thinks it matters. Even > worse, if you are addressing a set of requirements that have never > been articulated, which you have only because someone at some point > might be unhappy about something ... well. That's a difficult problem > to solve. > > Cheers, > Wendell > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324589.html it doesn't worked for me. Can you send across your code for the expected result. --- On Thu, 9/2/12, G. Ken Holman <gkholman@CraneSoftwrights.com> wrote: > From: G. Ken Holman <gkholman@CraneSoftwrights.com> > Subject: Re: [xsl] adding element in with general namespace prefix > To: xsl-list@lists.mulberrytech.com, xsl-list@lists.mulberrytech.com > Date: Thursday, 9 February, 2012, 3:19 AM > At 2012-02-09 03:16 +0530, ram > wrote: > > i completly agree with you, but some time service > provider may not like it when he sees the request, he may > question, why are you keeping different namespace prefix for > same namespace. > >    i wanted to be consistent in the entire > soap request that i am sending > > Then use: > >   <xsl:template match="soapenv:Header"> >     <xsl:copy> >       <xsl:copy-of select="@*"/> >       ..... > > If the input has <s:Header> then your output will be > <s:Header>. > > . . . . . . . . . Ken > > -- > Contact us for world-wide XML consulting and instructor-led > training > Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h > Crane Softwrights Ltd.          >   http://www.CraneSoftwrights.com/s/ > G. Ken Holman            >        mailto:gkholman@CraneSoftwrights.com > Google+ profile: https://plus.google.com/116832879756988317389/about > 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324590.html Ram, Maybe you want to use xsl:copy, which may do better for you. Most processors, when copying an element, will use the same prefix as the input document uses. Or it may not: as Ken says, processors are not obliged to respect prefixes since a prefix is not properly part of the name, as formally defined; it is only a (local) binding mechanism. If you are answering a requirement from a partner who does not understand this, you can, in XSLT 2.0, go to considerably more work to construct elements with namespaces, names and their prefixes generated dynamically, using XPath functions such as name(), prefix-from-QName(), and namespace-uri-for-prefix(). An XSLT stylesheet could generate a new header using whatever prefix the input uses, whatever it is -- although such a stylesheet will look pretty mysterious to the uninitiated. But this is not trivial to do, and a lot of trouble to go to for something that matters only because someone thinks it matters. Even worse, if you are addressing a set of requirements that have never been articulated, which you have only because someone at some point might be unhappy about something ... well. That's a difficult problem to solve. Cheers, Wendell On 2/8/2012 4:46 PM, ram wrote: > i completly agree with you, but some time service provider may not like it when he sees the request, he may question, why are you keeping different namespace prefix for same namespace. > i wanted to be consistent in the entire soap request that i am sending > > --- On Thu, 9/2/12, G. Ken Holman<gkholman@CraneSoftwrights.com> wrote: > >> From: G. Ken Holman<gkholman@CraneSoftwrights.com> >> Subject: Re: [xsl] adding element in with general namespace prefix >> To: xsl-list@lists.mulberrytech.com, xsl-list@lists.mulberrytech.com >> Date: Thursday, 9 February, 2012, 3:11 AM >> A true XML application ignores the >> namespace prefix and relies only >> on the namespace URI associated with the namespace prefix. >> >> Can you explain why it is important to you that the prefix >> be the >> same? It is irrelevant. This request is >> equivalent to an XML-based >> namespace-aware application: >> >> <giraffe:Envelope xmlns:giraffe="http://schemas.xmlsoap.org/soap/envelope/"> >> >> An XML application will still see the above as a SOAP >> envelope. >> >> At 2012-02-09 03:06 +0530, ram wrote: >>> So any idea how to fix >> it. >> >> It isn't broken. >> >> I hope this helps. >> >> . . . . . . . . . . Ken >> >> At 2012-02-09 03:06 +0530, ram wrote: >>> Hi, >>> I have a soap request like the following >>> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >>> xmlns:con1="http://abc.com/DefService/"> >>> >> <soapenv:Header> >>> >>> >> </soapenv:Header> >>> >> <soapenv:Body> >>> >> <con1:GetDefinition> >>> >> >> <!--Optional:--> >>> >> >> <con1:Request><con1:Id/> >>> >> >> </con1:Request> >>> >> </con1:GetDefinition> >>> >> </soapenv:Body> >>> </soapenv:Envelope> >>> >>> I wanted to add ws:security with username credentials to >> the request >>> like the following. >>> >>> >>> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <soapenv:Envelope xmlns:con="http://wellpoint.com/esb/context" >>> xmlns:con1="http://abc.com/DefService/> >>> <soapenv:Header> >>> <wsse:Security >>> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> >>> <wsse:UsernameToken> >>> >> <wsse:Username>abcd</wsse:Username> >>> >> <wsse:Password>ramkurra</wsse:Password> >>> </wsse:UsernameToken> >>> </wsse:Security> >>> </soapenv:Header> >>> <soapenv:Body> >>> <con1:GetDefinition> >>> <con1:Id/> >>> >> </con1:Response> >>> </con1:GetDefinition> >>> </soapenv:Body> >>> </soapenv:Envelope> >>> >>> >>> i tried with the following piece of code >>> >>> <xsl:stylesheet version="1.0" >>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> >>> <xsl:template match="@*|node()"> >>> <xsl:copy> >>> >> <xsl:apply-templates >> select="@*|node()"/> >>> </xsl:copy> >>> >>> </xsl:template> >>> <xsl:template >> match="/*[local-name()='Envelope']/*[local-name()='Header']"> >>> <soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> >>> <wsse:Security >>> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> >>> <wsse:UsernameToken> >>> <wsse:Username> >> abc</wsse:Username> >>> <wsse:Password> >> xya</wsse:Password> >>> </wsse:UsernameToken> >>> </wsse:Security> >>> </soapenv:Header> >>> </xsl:template> >>> </xsl:stylesheet> >>> >>> i get the result as expected, >> but my problem is when client >>> sends the request with different namespace name rather >> than >>> soapenv:Header, like s:Header, the following line of >> code will >>> still put soapenv:Header in the result >>> <soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> >>> >>> I wanted to make this namespace prefix is >> more of generalized >>> manner, which picks from request. >>> So any idea how to fix >> it. >> >> >> -- >> Contact us for world-wide XML consulting and instructor-led >> training >> Free 5-hour video lecture: XSLT/XPath 1.0& 2.0 http://ude.my/uoui9h >> Crane Softwrights Ltd. >> http://www.CraneSoftwrights.com/s/ >> G. Ken Holman >> mailto:gkholman@CraneSoftwrights.com >> Google+ profile: https://plus.google.com/116832879756988317389/about >> 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> > --~-- > > -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324588.html At 2012-02-09 03:16 +0530, ram wrote: >i completly agree with you, but some time service provider may not >like it when he sees the request, he may question, why are you >keeping different namespace prefix for same namespace. > i wanted to be consistent in the entire soap request that i am sending Then use: <xsl:template match="soapenv:Header"> <xsl:copy> <xsl:copy-of select="@*"/> ..... If the input has <s:Header> then your output will be <s:Header>. . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324587.html i completly agree with you, but some time service provider may not like it when he sees the request, he may question, why are you keeping different namespace prefix for same namespace. i wanted to be consistent in the entire soap request that i am sending --- On Thu, 9/2/12, G. Ken Holman <gkholman@CraneSoftwrights.com> wrote: > From: G. Ken Holman <gkholman@CraneSoftwrights.com> > Subject: Re: [xsl] adding element in with general namespace prefix > To: xsl-list@lists.mulberrytech.com, xsl-list@lists.mulberrytech.com > Date: Thursday, 9 February, 2012, 3:11 AM > A true XML application ignores the > namespace prefix and relies only > on the namespace URI associated with the namespace prefix. > > Can you explain why it is important to you that the prefix > be the > same?  It is irrelevant.  This request is > equivalent to an XML-based > namespace-aware application: > >    <giraffe:Envelope xmlns:giraffe="http://schemas.xmlsoap.org/soap/envelope/"> > > An XML application will still see the above as a SOAP > envelope. > > At 2012-02-09 03:06 +0530, ram wrote: > >       So any idea how to fix > it. > > It isn't broken. > > I hope this helps. > > . . . . . . . . . . Ken > > At 2012-02-09 03:06 +0530, ram wrote: > >Hi, > >    I have a soap request like the following > ><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" > >xmlns:con1="http://abc.com/DefService/" > > >      >    <soapenv:Header> > > > >          > </soapenv:Header> > >      >    <soapenv:Body> > >              >    <con1:GetDefinition> > >                >       >    <!--Optional:--> > >                >       >    <con1:Request><con1:Id/> > >                >       >    </con1:Request> > >              >    </con1:GetDefinition> > >      >    </soapenv:Body> > ></soapenv:Envelope> > > > >I wanted to add ws:security with username credentials to > the request > >like the following. > > > > > > > ><?xml version="1.0" encoding="UTF-8"?> > ><soapenv:Envelope xmlns:con="http://wellpoint.com/esb/context" > >xmlns:con1="http://abc.com/DefService/> > ><soapenv:Header> > ><wsse:Security > >xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> > >  <wsse:UsernameToken> > >    > <wsse:Username>abcd</wsse:Username> > >    > <wsse:Password>ramkurra</wsse:Password> > >  </wsse:UsernameToken> > ></wsse:Security> > ></soapenv:Header> > ><soapenv:Body> > >    <con1:GetDefinition> > >         <con1:Id/> > >      >    </con1:Response> > >    </con1:GetDefinition> > ></soapenv:Body> > ></soapenv:Envelope> > > > > > >i tried with the following piece of code > > > ><xsl:stylesheet version="1.0" > >xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> > ><xsl:template match="@*|node()"> > >     <xsl:copy> > >      >    <xsl:apply-templates > select="@*|node()"/> > >    </xsl:copy> > > > ></xsl:template> > ><xsl:template > match="/*[local-name()='Envelope']/*[local-name()='Header']"> > ><soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> > ><wsse:Security > >xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> > ><wsse:UsernameToken> > >    <wsse:Username>      > abc</wsse:Username> > >    <wsse:Password>      > xya</wsse:Password> > ></wsse:UsernameToken> > ></wsse:Security> > ></soapenv:Header> > ></xsl:template> > ></xsl:stylesheet> > > > >     i get the result as expected, > but my problem is when client > > sends the request with different namespace name rather > than > > soapenv:Header, like s:Header, the following line of > code will > > still put soapenv:Header in the result > ><soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> > > > >    I wanted to make this namespace prefix is > more of generalized > > manner, which picks from request. > >       So any idea how to fix > it. > > > -- > Contact us for world-wide XML consulting and instructor-led > training > Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h > Crane Softwrights Ltd.          >   http://www.CraneSoftwrights.com/s/ > G. Ken Holman            >        mailto:gkholman@CraneSoftwrights.com > Google+ profile: https://plus.google.com/116832879756988317389/about > 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324586.html A true XML application ignores the namespace prefix and relies only on the namespace URI associated with the namespace prefix. Can you explain why it is important to you that the prefix be the same? It is irrelevant. This request is equivalent to an XML-based namespace-aware application: <giraffe:Envelope xmlns:giraffe="http://schemas.xmlsoap.org/soap/envelope/"> An XML application will still see the above as a SOAP envelope. At 2012-02-09 03:06 +0530, ram wrote: > So any idea how to fix it. It isn't broken. I hope this helps. . . . . . . . . . . Ken At 2012-02-09 03:06 +0530, ram wrote: >Hi, > I have a soap request like the following ><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >xmlns:con1="http://abc.com/DefService/" > > <soapenv:Header> > > </soapenv:Header> > <soapenv:Body> > <con1:GetDefinition> > <!--Optional:--> > <con1:Request><con1:Id/> > </con1:Request> > </con1:GetDefinition> > </soapenv:Body> ></soapenv:Envelope> > >I wanted to add ws:security with username credentials to the request >like the following. > > > ><?xml version="1.0" encoding="UTF-8"?> ><soapenv:Envelope xmlns:con="http://wellpoint.com/esb/context" >xmlns:con1="http://abc.com/DefService/> ><soapenv:Header> ><wsse:Security >xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> > <wsse:UsernameToken> > <wsse:Username>abcd</wsse:Username> > <wsse:Password>ramkurra</wsse:Password> > </wsse:UsernameToken> ></wsse:Security> ></soapenv:Header> ><soapenv:Body> > <con1:GetDefinition> > <con1:Id/> > </con1:Response> > </con1:GetDefinition> ></soapenv:Body> ></soapenv:Envelope> > > >i tried with the following piece of code > ><xsl:stylesheet version="1.0" >xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> ><xsl:template match="@*|node()"> > <xsl:copy> > <xsl:apply-templates select="@*|node()"/> > </xsl:copy> > ></xsl:template> ><xsl:template match="/*[local-name()='Envelope']/*[local-name()='Header']"> ><soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> ><wsse:Security >xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> ><wsse:UsernameToken> > <wsse:Username> abc</wsse:Username> > <wsse:Password> xya</wsse:Password> ></wsse:UsernameToken> ></wsse:Security> ></soapenv:Header> ></xsl:template> ></xsl:stylesheet> > > i get the result as expected, but my problem is when client > sends the request with different namespace name rather than > soapenv:Header, like s:Header, the following line of code will > still put soapenv:Header in the result ><soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> > > I wanted to make this namespace prefix is more of generalized > manner, which picks from request. > So any idea how to fix it. -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324585.html Hi, I have a soap request like the following <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:con1="http://abc.com/DefService/" > <soapenv:Header> </soapenv:Header> <soapenv:Body> <con1:GetDefinition> <!--Optional:--> <con1:Request><con1:Id/> </con1:Request> </con1:GetDefinition> </soapenv:Body> </soapenv:Envelope> I wanted to add ws:security with username credentials to the request like the following. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:con="http://wellpoint.com/esb/context" xmlns:con1="http://abc.com/DefService/> <soapenv:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>abcd</wsse:Username> <wsse:Password>ramkurra</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> <soapenv:Body> <con1:GetDefinition> <con1:Id/> </con1:Response> </con1:GetDefinition> </soapenv:Body> </soapenv:Envelope> i tried with the following piece of code <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="@*|node()"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> <xsl:template match="/*[local-name()='Envelope']/*[local-name()='Header']"> <soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken> <wsse:Username> abc</wsse:Username> <wsse:Password> xya</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> </xsl:template> </xsl:stylesheet> i get the result as expected, but my problem is when client sends the request with different namespace name rather than soapenv:Header, like s:Header, the following line of code will still put soapenv:Header in the result <soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> I wanted to make this namespace prefix is more of generalized manner, which picks from request. So any idea how to fix it. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324584.html 8<-------------------------------------------------------------------- XSLfast 5.0: Data to Document... Done We are proud to announce the release of XSLfast 5.0 which is now available on our website http://www.xslfast.com/. You can see the brand-new features and enjoy the simplified and improved layout creation process. XSLfast is the leading tool to create layout templates and generate PDF documents. It turns your XML data into forms, invoices, price lists, catalogs, data sheets and much more in an easy way! XSLfast uses open technologies (like XSL-FO, PDF, FOP) that do not lock you into any proprietary tools. We welcome your feedback: in our public forum http://forums.jcatalog.com/forums/forums/show/2.page you can give us your comments, exchange ideas, discuss features or just get in touch with other XSLfast users. The ticket system is publicly available, too: http://jira.jcatalog.com/browse/XSL/. Limited Time Offer: Purchase XSLfast 5.0 till the 29th of February 2012 and save up to 150,00 EUR! New features of XSLfast 5.0: - Improved user interface: New skin and more classic look with improved functions - Improved grouping functions: hinting depending on attached XML file, most reasonable groupings are available from context menu and much more - Completions in Windows editor - Support for FOP 1.0, XEP, XSLformatter, JAVA 1.6, XSLT 2.0, PDF 1.4 and CSV - Massive enhancements for pivot tables - Completely new table wizard: The refined table wizard simplifies and accelerates the layout creation - On-the-fly preview: The preview window shows how your layout really looks - External tools are gone: XSLfast is able to automatically detect everything - Support of multiple monitors: Simplifies and accelerates layout creation - Additional functions: Side floats, more IF-clauses for table columns, support of fo:marker, managed backgrounds, support of DTD external entities, layout comparisons and much more... More features of XSLfast: - Cross media publishing for every XML data - Create forms, invoices, product sheets, catalogs, price lists, ... - Design templates for database publishing, print-on-demand and batch publishing - No XSL-FO or XSLT-programming skills necessary - Use of templates as functions in your XSL code - Different output formats and files (PDF, HTML, XSL-FO) - Compatible with Windows XP, Vista, 7, Mac OS, Linux We invite you to try XSLfast 5.0 by visiting our website http://www.xslfast.com/ and downloading the free trial version. Yours XSLfast Team Europe:   jCatalog Software AG   Lindemannstr. 79   44137 Dortmund   Germany   Tel: +49 231-3967-0   Fax: +49 231-3967-100   Mail: info@xslfast.com USA:   jCatalog Software AG   6818 Balsam Way   Oakland, CA 94611   USA   Tel: + 1 510 595 6800   Fax: + 1 413 487 1814   Mail: info@xslfast.com 8<-------------------------------------------------------------------- --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324583.html At 2012-02-08 09:46 +0000, Florent Georges wrote: >Wendell Piez wrote: > > "XSL", in fact, properly means the combination of XSLT and > > XSL-FO, even if it's also commonly used to mean XSLT without > > XSL-FO. > Even worse... Some people use it to refer to XSLT (like an >"abbreviation" of XSLT, mainly because of the usual extension >.xsl I guess). My students tell me the confusion is because of the choice of the namespace prefix in code they've seen ... I am often asked "Then why isn't it <xslt:value-of>?". Of course the very first examples of XSLT were created when XSLT was chapter 2 of XSL. Well, it still is as a reference, but in the first drafts, before it was split off, all of XSLT was described in the body of chapter 2 of XSL. >Some people use it to refer to XSL-FO, as the XSL >spec actually refers to the XSLT spec, but includes (and is) the >spec body for XSL-FO. And I guess some people use it to refer to >XSL, but I rarely have the opportunity to speak about XSL as a >whole ;-) > > My rule of thumb: always use either XSLT or XSL-FO, and if you >hear XSL, ask for precision. +1 . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324582.html Wendell Piez wrote:   Hi, > "XSL", in fact, properly means the combination of XSLT and > XSL-FO, even if it's also commonly used to mean XSLT without > XSL-FO.   Even worse...  Some people use it to refer to XSLT (like an "abbreviation" of XSLT, mainly because of the usual extension .xsl I guess).  Some people use it to refer to XSL-FO, as the XSL spec actually refers to the XSLT spec, but includes (and is) the spec body for XSL-FO.  And I guess some people use it to refer to XSL, but I rarely have the opportunity to speak about XSL as a whole ;-)   My rule of thumb: always use either XSLT or XSL-FO, and if you hear XSL, ask for precision.   Regards, --  Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324581.html As a contra-point, I exclusively use XQuery not XSLT to generate XSL-FO for publication of PDF. I am probably the 1 in a million who finds it vastly easier to comprehend then XSLT ... but so be it :) -----Original Message----- From: Wendell Piez [mailto:wapiez@mulberrytech.com] Sent: Tuesday, February 07, 2012 2:06 PM To: xsl-list@lists.mulberrytech.com Subject: Re: [xsl] [XSL-FO] Way to include an outside stylesheet? Colin, If your stylesheet has something like this at the top: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" ... then it is XSLT. (Yes, XSLT is used routinely to generate XSL-FO. "XSL", in fact, properly means the combination of XSLT and XSL-FO, even if it's also commonly used to mean XSLT without XSL-FO.) So you have xsl:include, xsl:import, templates and the entire range of XSLT functionalities available. In fact, if you find you are writing lots of xsl:if or xsl:choose instructions, chances are good that you could improve your XSLT quite a bit. In XSLT, conditional processing is often done in other ways, and usually more gracefully. Most of what you learn when you use XSLT to generate other formats (such as HTML) will also apply when using it to make XSL-FO. So, absolutely, yes, go for it. (If you aren't using XSLT, then can you explain how you are generating your XSL-FO?) Cheers, Wendell On 2/7/2012 12:02 PM, Colin DeClue wrote: > Hey Guys, > > So, I'm using xsl-fo (with the Antenna House Formatter) to develop > several reports. Many of them have share a large section of the body. > I was building them up by having lots of if statements for the other > parts of the reports, but that's getting cumbersome. I'd like to have > the body portion in a separate style sheet, and keep the separate > reports in separate style sheets that reference the body portion. I > saw that xslt an<xsl:include> element, but I couldn't find something > for xsl-fo. Does anyone have any suggestions? > > Thanks, > Colin DeClue -- ====================================================================== 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> --~-- --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324579.html I do have that at the top of my stylesheet, but when I tried <xsl:include>, it complained. It looks like I was using the include element incorrectly, however. I'd just assumed when it didn't recognize the include that it just wasn't XSLT. Thanks. The knowledge that I CAN use it should hopefully be enough to get me to use it correctly, this time. On Tue, Feb 7, 2012 at 1:06 PM, Wendell Piez <wapiez@mulberrytech.com> wrote: > Colin, > > If your stylesheet has something like this at the top: > > <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" ... > > then it is XSLT. (Yes, XSLT is used routinely to generate XSL-FO. "XSL", in > fact, properly means the combination of XSLT and XSL-FO, even if it's also > commonly used to mean XSLT without XSL-FO.) > > So you have xsl:include, xsl:import, templates and the entire range of XSLT > functionalities available. > > In fact, if you find you are writing lots of xsl:if or xsl:choose > instructions, chances are good that you could improve your XSLT quite a bit. > In XSLT, conditional processing is often done in other ways, and usually > more gracefully. > > Most of what you learn when you use XSLT to generate other formats (such as > HTML) will also apply when using it to make XSL-FO. > > So, absolutely, yes, go for it. > > (If you aren't using XSLT, then can you explain how you are generating your > XSL-FO?) > > Cheers, > Wendell > > > On 2/7/2012 12:02 PM, Colin DeClue wrote: >> >> Hey Guys, >> >> So, I'm using xsl-fo (with the Antenna House Formatter) to develop >> several reports. Many of them have share a large section of the body. >> I was building them up by having lots of if statements for the other >> parts of the reports, but that's getting cumbersome. I'd like to have >> the body portion in a separate style sheet, and keep the separate >> reports in separate style sheets that reference the body portion. I >> saw that xslt an<xsl:include>  element, but I couldn't find something >> for xsl-fo. Does anyone have any suggestions? >> >> Thanks, >> Colin DeClue > > > > -- > ====================================================================== > 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> > --~-- > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324578.html Colin, If your stylesheet has something like this at the top: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" ... then it is XSLT. (Yes, XSLT is used routinely to generate XSL-FO. "XSL", in fact, properly means the combination of XSLT and XSL-FO, even if it's also commonly used to mean XSLT without XSL-FO.) So you have xsl:include, xsl:import, templates and the entire range of XSLT functionalities available. In fact, if you find you are writing lots of xsl:if or xsl:choose instructions, chances are good that you could improve your XSLT quite a bit. In XSLT, conditional processing is often done in other ways, and usually more gracefully. Most of what you learn when you use XSLT to generate other formats (such as HTML) will also apply when using it to make XSL-FO. So, absolutely, yes, go for it. (If you aren't using XSLT, then can you explain how you are generating your XSL-FO?) Cheers, Wendell On 2/7/2012 12:02 PM, Colin DeClue wrote: > Hey Guys, > > So, I'm using xsl-fo (with the Antenna House Formatter) to develop > several reports. Many of them have share a large section of the body. > I was building them up by having lots of if statements for the other > parts of the reports, but that's getting cumbersome. I'd like to have > the body portion in a separate style sheet, and keep the separate > reports in separate style sheets that reference the body portion. I > saw that xslt an<xsl:include> element, but I couldn't find something > for xsl-fo. Does anyone have any suggestions? > > Thanks, > Colin DeClue -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324577.html Hey Guys, So, I'm using xsl-fo (with the Antenna House Formatter) to develop several reports. Many of them have share a large section of the body. I was building them up by having lots of if statements for the other parts of the reports, but that's getting cumbersome. I'd like to have the body portion in a separate style sheet, and keep the separate reports in separate style sheets that reference the body portion. I saw that xslt an <xsl:include> element, but I couldn't find something for xsl-fo. Does anyone have any suggestions? Thanks, Colin DeClue --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324576.html On 07/02/2012 14:00, ram wrote: > Hi, > I was trying to do xpath like following. > > > <xsl:variable name='abc' select="normalize-space($var1/*[local-name()='source']/text())"/> > > the $var1 contains a node set something like this. > > > <plan> > <sourc>asfasfs</source> > <value>adadf</value> > </plan> > > when i run the above line i am not getting any result. is there anything wrong with the statement. > > It's hard to debug problems when all you know is that the input is "something like this" - solving programming problems requires accurate detail. My guess would be that $var is actually the document node that contains <plan> as a child element, in which case you need to select down an extra level. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324574.html On 7 February 2012 14:00, ram <ram_kurra@yahoo.co.in> wrote: > Hi, >     I was trying to do xpath like following. > > > <xsl:variable name='abc' select="normalize-space($var1/*[local-name()='source']/text())"/> > > the $var1 contains a node set something like this. > > > <plan> >   <sourc>asfasfs</source> >   <value>adadf</value> > </plan> > >    when i run the above line i am not getting any result. is there anything wrong with the statement. Don't forget if you have a variable like this: <xsl:variable name="var1"> <plan> <source> then $var1 returns the document-node containing <plan> element, so to access the <source> element you need either $var1/plan/source, or set the sequence type of the variable to be element(plan), then use $var1/source. -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324575.html I am sorry its typo error. <plan> <source>asfasfs</source> </plan> --- On Tue, 7/2/12, Martin Honnen <Martin.Honnen@gmx.de> wrote: > From: Martin Honnen <Martin.Honnen@gmx.de> > Subject: Re: [xsl] xpath problem > To: xsl-list@lists.mulberrytech.com > Date: Tuesday, 7 February, 2012, 7:33 PM > ram wrote: > > >       I was trying to do xpath > like following. > > > > > > <xsl:variable name='abc' > select="normalize-space($var1/*[local-name()='source']/text())"/> > > > > the $var1 contains a node set something like this. > > > > > > <plan> > >  >    <sourc>asfasfs</source> >        ^^^^^^^    >    ^^^^^^^^^ > That is not even well-formed so please post samples that > allow us to > reproduce the issue. > >  >    <value>adadf</value> > > </plan> > > > >      when i run the above line i am not > getting any result. is there anything wrong with the > statement. > > > > > -- > >     Martin Honnen --- MVP Data Platform > Development >     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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324573.html ram wrote: > I was trying to do xpath like following. > > > <xsl:variable name='abc' select="normalize-space($var1/*[local-name()='source']/text())"/> > > the $var1 contains a node set something like this. > > > <plan> > <sourc>asfasfs</source> ^^^^^^^ ^^^^^^^^^ That is not even well-formed so please post samples that allow us to reproduce the issue. > <value>adadf</value> > </plan> > > when i run the above line i am not getting any result. is there anything wrong with the statement. -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324572.html Hi, I was trying to do xpath like following. <xsl:variable name='abc' select="normalize-space($var1/*[local-name()='source']/text())"/> the $var1 contains a node set something like this. <plan> <sourc>asfasfs</source> <value>adadf</value> </plan> when i run the above line i am not getting any result. is there anything wrong with the statement. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324571.html Nice! Thanks again. Here's to getting rid of old hoariness. Mark On 2/6/2012 12:46 PM, Wendell Piez wrote: > Mark, > > This is cool. > > On 2/6/2012 12:50 PM, Mark Giffin wrote: >> Thanks Wendell, also good to know. In this project I ran out of time and >> couldn't take the time to work out how to use collection(), so I handled >> it elsewise. collection() would have required a ton of refactoring on >> this project. I realized I mainly needed to exclude a couple files, so I >> embedded a little lookup table in the stylesheet that holds a couple >> strings: >> >> <st:exclude> >> <st:file name="filename1.xml"/> >> <st:file name="filename2.xml"/> >> </st:exclude> >> >> Then I made a key to parse it: >> >> <xsl:variable name="excluded-files" >> select="document('')/xsl:stylesheet/st:exclude"/> > > Or you could simply do > > <xsl:variable name="excluded-files" as="element(st:file)+"> > <st:file name="filename1.xml"/> > <st:file name="filename2.xml"/> > ... > </xsl:variable> > > and take it from there. > > (The hoary old XSLT 1.0 trick you used is no longer necessary. :-) > > Then you may not need the key any more either, as > > exists($excluded-files[@name=$this-file]) > > will then tell you what you need to know, probably as fast. > > (Many things can become much simpler under 2.0.) > > Cheers, > Wendell > >> >> <!-- Key to parse $excluded-files. --> >> <xsl:key name="excluded" match="st:file" use="@name"/> >> >> And excluded those files by testing it with key(): >> >> <xsl:when test="exists(key('excluded', $thisfile, $excluded-files))"> >> <!-- do nothing --> >> </xsl:when> >> >> Maybe later I can get cooler with collection(). > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324557.html Mark, This is cool. On 2/6/2012 12:50 PM, Mark Giffin wrote: > Thanks Wendell, also good to know. In this project I ran out of time and > couldn't take the time to work out how to use collection(), so I handled > it elsewise. collection() would have required a ton of refactoring on > this project. I realized I mainly needed to exclude a couple files, so I > embedded a little lookup table in the stylesheet that holds a couple > strings: > > <st:exclude> > <st:file name="filename1.xml"/> > <st:file name="filename2.xml"/> > </st:exclude> > > Then I made a key to parse it: > > <xsl:variable name="excluded-files" > select="document('')/xsl:stylesheet/st:exclude"/> Or you could simply do <xsl:variable name="excluded-files" as="element(st:file)+"> <st:file name="filename1.xml"/> <st:file name="filename2.xml"/> ... </xsl:variable> and take it from there. (The hoary old XSLT 1.0 trick you used is no longer necessary. :-) Then you may not need the key any more either, as exists($excluded-files[@name=$this-file]) will then tell you what you need to know, probably as fast. (Many things can become much simpler under 2.0.) Cheers, Wendell > > <!-- Key to parse $excluded-files. --> > <xsl:key name="excluded" match="st:file" use="@name"/> > > And excluded those files by testing it with key(): > > <xsl:when test="exists(key('excluded', $thisfile, $excluded-files))"> > <!-- do nothing --> > </xsl:when> > > Maybe later I can get cooler with collection(). -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324552.html Thanks Wendell, also good to know. In this project I ran out of time and couldn't take the time to work out how to use collection(), so I handled it elsewise. collection() would have required a ton of refactoring on this project. I realized I mainly needed to exclude a couple files, so I embedded a little lookup table in the stylesheet that holds a couple strings: <st:exclude> <st:file name="filename1.xml"/> <st:file name="filename2.xml"/> </st:exclude> Then I made a key to parse it: <xsl:variable name="excluded-files" select="document('')/xsl:stylesheet/st:exclude"/> <!-- Key to parse $excluded-files. --> <xsl:key name="excluded" match="st:file" use="@name"/> And excluded those files by testing it with key(): <xsl:when test="exists(key('excluded', $thisfile, $excluded-files))"> <!-- do nothing --> </xsl:when> Maybe later I can get cooler with collection(). Mark On 2/6/2012 9:17 AM, Wendell Piez wrote: > Hi Mark, > > In addition to what Ken says, two other things: > > Some processors, Saxon included, will accept a list of documents for > the collection() function from a file. So you only have to contrive a > way of getting the files you are interested in listed in the syntax it > expects. > > (See http://www.saxonica.com/documentation/sourcedocs/collections.xml.) > > Plus, there's also a (rather crude) escape hatch. In addition to > whatever is supported by the local implementation of collection(), > keep in mind that you can get any document's URI using the > document-uri() function, and it's a string, so you can use it to > filter documents. > > So something like > > select="collection('path;on-error=ignore') > [matches(document-uri(.),'content/extra/[^/]+/[^/]+$']" > > Obviously this is likely to quite expensive since every document (or > every XML document) is subject to being retrieved before the ones you > don't want are discarded. But by the same token it is very flexible. > > Cheers, > Wendell > > On 2/5/2012 4:25 PM, Mark Giffin wrote: >> Thanks Ken! This does help, I'll check it out. That info is not in >> Michael Kay's XSLT 2.0 book. I'll blame him. Just kiddin. >> >> Mark >> >> On 2/5/2012 12:56 PM, G. Ken Holman wrote: >>> At 2012-02-05 12:51 -0800, Mark Giffin wrote: >>>> Is there a way to collect a set of files off the file system in XSLT >>>> 2.0, in the same way that Ant lets you define a set of files with >>>> <fileset> like this: >>>> >>>> <fileset dir="${src.dir}" id="all.docs"> >>>> <include name="**/*.xml"/> >>>> <exclude name="**/gui/*.*"/> >>>> <exclude name="tools/**/*.*"/> >>>> <exclude name="content/extra/**/*.*"/> >>>> </fileset> >>>> >>>> Maybe an extension function or something? I've been using a >>>> manually-maintained list of files like this, but it's a a pain: >>>> >>>> <docroot> >>>> <root href="../../../doc_source/system100.xml" /> >>>> <root href="../../../doc_source/content/access/accesscore.xml" /> >>>> <root href="../../../doc_source/content/access/accesstest.xml" /> >>>> <root >>>> href="../../../doc_source/content/access/accesstest_commands.xml" /> >>>> etc. >>>> </docroot> >>> >>> The concept in XSLT2 is the function collection(uri) which returns a >>> set of root nodes of all the XML files addressed by the URI. >>> >>> There is no standard for the URI string, so you have to read your >>> vendor's documentation regarding how to compose the URI for what you >>> want. For example, for Saxon, you would address all the XML files in >>> the current and descendent subdirectories with something along the >>> lines of: >>> >>> collection("./?select="*.xml;recurse=yes;on-error=ignore") >>> >>> I hope this helps. >>> >>> . . . . . . . . . . . Ken > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324546.html Hi, On 2/6/2012 6:07 AM, David Carlisle wrote: > If you chose an output encoding that does not include the characters > (say US-ASCII) then the system will encode the non ascii characters > using numeric references on output. This does exactly what's needed about 98% of the time. Saxon even includes an option (xsl:output/@saxon:character-representation) for controlling whether numeric character references come out in hex or in decimal. 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324545.html Hi, On 2/5/2012 10:37 PM, Graydon wrote: > On Sun, Feb 05, 2012 at 10:30:15PM -0500, Syd Bauman scripsit: >> For years I've used expressoins like >> @*[not(name(.)='xml:id' or name(.)='rend')] >> to ask for all of the attributes *except* xml:id= or rend=. And some >> time ago Jeni recommended essentially the same approach.[1] But I'm >> wondering if that isn't an XPath 1-ish way to do things, and if there >> isn't a nicer way to get the same set when using XSLT 2 (and thus can >> make use of XPath 2). > > @* except (@xml:id,@rend) > > is how that goes in XSLT 2. Yes, and much nicer. Boo to explicit name testing. > (or @*[name(.) != ('xml:id','rend')] if you're preferential toward the > predicate, but the except is the way to go, since that's an actual node > test and keeps you out of the stringy land of names.) Gotcha alert: that should be not(name(.) = ('xml:id','rend')). The != will always be true because every possible value of name(.) (any string at all) is != to either or both 'xml:id' and 'rend'. But the main reason to dislike explicit name testing for this kind of thing is that it isn't namespace-safe, and is thus liable to break at inconvenient times, unlike the implicit name testing provided by path expressions. (If you really must, the XPath 2.0 node-name() function can help.) > The only tricky thing I've so far noticed about 'except' is that it > doesn't always affect the implicit context of position() just how you > would expect without the write-stuff-down-and-stare-at-it step. Yes, you have to keep in mind that it's a set operation, so in both attribute::* except (attribute::xml:id|attribute::rend) attribute::type union attribute::rend @type|@rend the context for evaluating the second operand is the same as the context for the first, that is, we are excluding (or including) particular attribute of the context node, not of its attributes. 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324544.html Hi Mark, In addition to what Ken says, two other things: Some processors, Saxon included, will accept a list of documents for the collection() function from a file. So you only have to contrive a way of getting the files you are interested in listed in the syntax it expects. (See http://www.saxonica.com/documentation/sourcedocs/collections.xml.) Plus, there's also a (rather crude) escape hatch. In addition to whatever is supported by the local implementation of collection(), keep in mind that you can get any document's URI using the document-uri() function, and it's a string, so you can use it to filter documents. So something like select="collection('path;on-error=ignore') [matches(document-uri(.),'content/extra/[^/]+/[^/]+$']" Obviously this is likely to quite expensive since every document (or every XML document) is subject to being retrieved before the ones you don't want are discarded. But by the same token it is very flexible. Cheers, Wendell On 2/5/2012 4:25 PM, Mark Giffin wrote: > Thanks Ken! This does help, I'll check it out. That info is not in > Michael Kay's XSLT 2.0 book. I'll blame him. Just kiddin. > > Mark > > On 2/5/2012 12:56 PM, G. Ken Holman wrote: >> At 2012-02-05 12:51 -0800, Mark Giffin wrote: >>> Is there a way to collect a set of files off the file system in XSLT >>> 2.0, in the same way that Ant lets you define a set of files with >>> <fileset> like this: >>> >>> <fileset dir="${src.dir}" id="all.docs"> >>> <include name="**/*.xml"/> >>> <exclude name="**/gui/*.*"/> >>> <exclude name="tools/**/*.*"/> >>> <exclude name="content/extra/**/*.*"/> >>> </fileset> >>> >>> Maybe an extension function or something? I've been using a >>> manually-maintained list of files like this, but it's a a pain: >>> >>> <docroot> >>> <root href="../../../doc_source/system100.xml" /> >>> <root href="../../../doc_source/content/access/accesscore.xml" /> >>> <root href="../../../doc_source/content/access/accesstest.xml" /> >>> <root >>> href="../../../doc_source/content/access/accesstest_commands.xml" /> >>> etc. >>> </docroot> >> >> The concept in XSLT2 is the function collection(uri) which returns a >> set of root nodes of all the XML files addressed by the URI. >> >> There is no standard for the URI string, so you have to read your >> vendor's documentation regarding how to compose the URI for what you >> want. For example, for Saxon, you would address all the XML files in >> the current and descendent subdirectories with something along the >> lines of: >> >> collection("./?select="*.xml;recurse=yes;on-error=ignore") >> >> I hope this helps. >> >> . . . . . . . . . . . Ken -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324543.html Thanks a lot ! . . . . . . . . . . . . . . . . . . . . . . . . . . Ing. Patrick Szabo XSLT Developer LexisNexis A-1030 Wien, Marxergasse 25 mailto:patrick.szabo@lexisnexis.at Tel.: +43 1 53452 1573 Fax: +43 1 534 52 146 -----Ursprüngliche Nachricht----- Von: David Carlisle [mailto:davidc@nag.co.uk] Gesendet: Montag, 06. Februar 2012 12:08 An: xsl-list@lists.mulberrytech.com Cc: Szabo, Patrick (LNG-VIE) Betreff: Re: [xsl] Entities On 06/02/2012 10:56, Szabo, Patrick (LNG-VIE) wrote: > Hi, > > How can I declare that I do not wan't entities to be resolved ? > I've tried different output methods but that didn't work. > The entities are in hex-format. > In XML terminology numeric character references are not entity references, and XML tools typically provide no way not to resolve them to their characters. The whole point is that the author should be free to use either form and get the same outcome. If you chose an output encoding that does not include the characters (say US-ASCII) then the system will encode the non ascii characters using numeric references on output. David -- google plus: https:/profiles.google.com/d.p.carlisle ________________________________________________________________________ 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324528.html On 06/02/2012 10:56, Szabo, Patrick (LNG-VIE) wrote: > Hi, > > How can I declare that I do not wan't entities to be resolved ? > I've tried different output methods but that didn't work. > The entities are in hex-format. > In XML terminology numeric character references are not entity references, and XML tools typically provide no way not to resolve them to their characters. The whole point is that the author should be free to use either form and get the same outcome. If you chose an output encoding that does not include the characters (say US-ASCII) then the system will encode the non ascii characters using numeric references on output. David -- google plus: https:/profiles.google.com/d.p.carlisle ________________________________________________________________________ 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324527.html Szabo, Patrick (LNG-VIE) wrote: > How can I declare that I do not wan't entities to be resolved ? > I've tried different output methods but that didn't work. > The entities are in hex-format. That sounds as if you are talking about hexadecimal character references, not entities or entity references. In the XSLT data model the XSLT processor operates on there are neither entity references nor character references, the processor simply operates on a tree with text nodes containing Unicode characters. The only way to be able to preserve character references is to mark them up as needed before the XSLT processor works, I think Andrew's LexEx http://andrewjwelch.com/lexev/ does that for you on the Java platform. That way you get nodes you can operate on in XSLT -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324526.html Hi, How can I declare that I do not wan't entities to be resolved ? I've tried different output methods but that didn't work. The entities are in hex-format. Best regards . . . . . . . . . . . . . . . . . . . . . . . . . . Ing. Patrick Szabo XSLT Developer LexisNexis A-1030 Wien, Marxergasse 25 mailto:patrick.szabo@lexisnexis.at Tel.: +43 1 53452 1573 Fax: +43 1 534 52 146 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324524.html Great, thanks! 2012/2/6 Philip Fearon <phil@saxonica.com>: > No, it's not yet possible to process dynamically generated XSLT from > Saxon-CE, but we're hoping to include this for the next release. > > Phil > > On Mon, Feb 6, 2012 at 7:08 AM, TW <zupftom@googlemail.com> wrote: >> Subject line says it:  Can I use Saxon-CE to dynamically generate an >> XSL stylesheet that I then apply to some data?  With in-browser XSLT >> 1.0 I'd load the dynamically generated stylesheet with >> xsltProcessor.importStylesheet().  Is there a comparable mechanism for >> Saxon-CE? >> >> Thomas 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> >> --~-- >> > > --~------------------------------------------------------------------ > XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324523.html No, it's not yet possible to process dynamically generated XSLT from Saxon-CE, but we're hoping to include this for the next release. Phil On Mon, Feb 6, 2012 at 7:08 AM, TW <zupftom@googlemail.com> wrote: > Subject line says it:  Can I use Saxon-CE to dynamically generate an > XSL stylesheet that I then apply to some data?  With in-browser XSLT > 1.0 I'd load the dynamically generated stylesheet with > xsltProcessor.importStylesheet().  Is there a comparable mechanism for > Saxon-CE? > > Thomas 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> > --~-- > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324522.html Subject line says it: Can I use Saxon-CE to dynamically generate an XSL stylesheet that I then apply to some data? With in-browser XSLT 1.0 I'd load the dynamically generated stylesheet with xsltProcessor.importStylesheet(). Is there a comparable mechanism for Saxon-CE? Thomas 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324521.html On Sun, Feb 05, 2012 at 10:30:15PM -0500, Syd Bauman scripsit: > For years I've used expressoins like > @*[not(name(.)='xml:id' or name(.)='rend')] > to ask for all of the attributes *except* xml:id= or rend=. And some > time ago Jeni recommended essentially the same approach.[1] But I'm > wondering if that isn't an XPath 1-ish way to do things, and if there > isn't a nicer way to get the same set when using XSLT 2 (and thus can > make use of XPath 2). @* except (@xml:id,@rend) is how that goes in XSLT 2. (or @*[name(.) != ('xml:id','rend')] if you're preferential toward the predicate, but the except is the way to go, since that's an actual node test and keeps you out of the stringy land of names.) The only tricky thing I've so far noticed about 'except' is that it doesn't always affect the implicit context of position() just how you would expect without the write-stuff-down-and-stare-at-it step. -- Graydon --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324520.html For years I've used expressoins like @*[not(name(.)='xml:id' or name(.)='rend')] to ask for all of the attributes *except* xml:id= or rend=. And some time ago Jeni recommended essentially the same approach.[1] But I'm wondering if that isn't an XPath 1-ish way to do things, and if there isn't a nicer way to get the same set when using XSLT 2 (and thus can make use of XPath 2). Note ---- [1] http://www.dpawson.co.uk/xsl/sect2/N1553.html#d2256e890 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324519.html Thanks Ken! This does help, I'll check it out. That info is not in Michael Kay's XSLT 2.0 book. I'll blame him. Just kiddin. Mark On 2/5/2012 12:56 PM, G. Ken Holman wrote: > At 2012-02-05 12:51 -0800, Mark Giffin wrote: >> Is there a way to collect a set of files off the file system in XSLT >> 2.0, in the same way that Ant lets you define a set of files with >> <fileset> like this: >> >> <fileset dir="${src.dir}" id="all.docs"> >> <include name="**/*.xml"/> >> <exclude name="**/gui/*.*"/> >> <exclude name="tools/**/*.*"/> >> <exclude name="content/extra/**/*.*"/> >> </fileset> >> >> Maybe an extension function or something? I've been using a >> manually-maintained list of files like this, but it's a a pain: >> >> <docroot> >> <root href="../../../doc_source/system100.xml" /> >> <root href="../../../doc_source/content/access/accesscore.xml" /> >> <root href="../../../doc_source/content/access/accesstest.xml" /> >> <root >> href="../../../doc_source/content/access/accesstest_commands.xml" /> >> etc. >> </docroot> > > The concept in XSLT2 is the function collection(uri) which returns a > set of root nodes of all the XML files addressed by the URI. > > There is no standard for the URI string, so you have to read your > vendor's documentation regarding how to compose the URI for what you > want. For example, for Saxon, you would address all the XML files in > the current and descendent subdirectories with something along the > lines of: > > collection("./?select="*.xml;recurse=yes;on-error=ignore") > > I hope this helps. > > . . . . . . . . . . . Ken --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324517.html At 2012-02-05 12:51 -0800, Mark Giffin wrote: >Is there a way to collect a set of files off the file system in XSLT >2.0, in the same way that Ant lets you define a set of files with ><fileset> like this: > ><fileset dir="${src.dir}" id="all.docs"> ><include name="**/*.xml"/> ><exclude name="**/gui/*.*"/> ><exclude name="tools/**/*.*"/> ><exclude name="content/extra/**/*.*"/> ></fileset> > >Maybe an extension function or something? I've been using a >manually-maintained list of files like this, but it's a a pain: > ><docroot> ><root href="../../../doc_source/system100.xml" /> ><root href="../../../doc_source/content/access/accesscore.xml" /> ><root href="../../../doc_source/content/access/accesstest.xml" /> ><root href="../../../doc_source/content/access/accesstest_commands.xml" /> > etc. ></docroot> The concept in XSLT2 is the function collection(uri) which returns a set of root nodes of all the XML files addressed by the URI. There is no standard for the URI string, so you have to read your vendor's documentation regarding how to compose the URI for what you want. For example, for Saxon, you would address all the XML files in the current and descendent subdirectories with something along the lines of: collection("./?select="*.xml;recurse=yes;on-error=ignore") I hope this helps. . . . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324515.html Is there a way to collect a set of files off the file system in XSLT 2.0, in the same way that Ant lets you define a set of files with <fileset> like this: <fileset dir="${src.dir}" id="all.docs"> <include name="**/*.xml"/> <exclude name="**/gui/*.*"/> <exclude name="tools/**/*.*"/> <exclude name="content/extra/**/*.*"/> </fileset> Maybe an extension function or something? I've been using a manually-maintained list of files like this, but it's a a pain: <docroot> <root href="../../../doc_source/system100.xml" /> <root href="../../../doc_source/content/access/accesscore.xml" /> <root href="../../../doc_source/content/access/accesstest.xml" /> <root href="../../../doc_source/content/access/accesstest_commands.xml" /> etc. </docroot> 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324514.html "Szabo, Patrick (LNG-VIE)" wrote:   Hi, > Thanks a lot for your very detailed answer.  > I'll take a look at EXPath and the ressources you've provided.   Because a few people asked in private for the WSDL Compiler, I've updated it, and it's available in the Subversion repository of the open source implementation of the EXPath HTTP Client for Java, in trunk/samples/wsdl-compiler/ [1].   The idea is to transform the WSDL using wsdl-compiler.xsl.  The result of this is a stylesheet defining a function for each Web service's operation.  You can then import this XSLT library in your own stylesheet and use the generated functions, passing them directly the SOAP payload (the content of soap-env:Body).   There are 2 examples (for each there is a WSDL and a test stylesheet, you have to generate the compiled library and name it after the import statement in the test stylesheet).  These example are in the same directory.   If you have any question, the EXPath mailing list is probably a better place than here...   Please keep in mind that it's more a proof-of-concept than an industry quality standards-compliant stylesheet...   Regards, --  Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ [1]http://code.google.com/p/expath-http-client/source/browse/#svn%2Ftrunk%2Fsamples%2Fwsdl-compiler --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324451.html Hi, Thanks a lot for your very detailed answer. I'll take a look at EXPath and the ressources you've provided. Best regards . . . . . . . . . . . . . . . . . . . . . . . . . . Ing. Patrick Szabo XSLT Developer LexisNexis A-1030 Wien, Marxergasse 25 mailto:patrick.szabo@lexisnexis.at Tel.: +43 1 53452 1573 Fax: +43 1 534 52 146 -----Ursprüngliche Nachricht----- Von: Florent Georges [mailto:lists@fgeorges.org] Gesendet: Freitag, 03. Februar 2012 09:58 An: xsl-list@lists.mulberrytech.com Betreff: Re: [xsl] Webservices and XSLT "Szabo, Patrick (LNG-VIE)" wrote: Hi, > I was looking online and found several possibilities to work > with soap and xslt but I can't wrap my head around how this > really works. Well, as with any other client (if we restrict the discussion to synchronous SOAP-over-HTTP Web services), technically you have to send POST requests (with the XML message as the payload) and you get the operation's XML response as the payload of the HTTP response. XSLT is very well suited to construct the XML request and consume the XML response, but you'll need an extension to send HTTP POST requests. The EXPath HTTP Client is implemented for several processor, check your processor to see if it does support it. More infos in the following pages (including an example of consuming a SOAP Web service): http://expath.org/modules/http-client/ http://expath.org/modules/http-client/samples#soap http://expath.org/spec/http-client > In no example online I see where the URL to the wsdl is > configured. If you expect more automated support in XSLT from a WSDL, that's another story. I wrote once a WSDL compiler, that "compiled" a WSDL to a stylesheet defining a function for each Web service operation, hiding all the communication technical details for the user. So the user can just call a function by passing directly the payload, and getting back the response. With the WSDL in the above example, the generated function could be called like: <xsl:stylesheet xmlns:tns="http://www.webservicex.net" ...> <!-- import the library generated from the WSDL --> <xsl:import href="compiled-web-service.xsl"/> <!-- the service operation request --> <xsl:variable name="request"> <wsx:GetWeatherByPlaceName> <wsx:PlaceName>NEW YORK</wsx:PlaceName> </wsx:GetWeatherByPlaceName> </xsl:variable> <!-- invoke the service operation --> <xsl:template name="main"> <xsl:sequence select=" tns:GetWeatherByPlaceName($request)"/> </xsl:template> </xsl:stylesheet> Unfortunately the WSDL compiler was never released, but I can send you a copy if you want... Of course, it relies on the EXPath HTTP Client in order to send HTTP requests under the hood. Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324434.html "Szabo, Patrick (LNG-VIE)" wrote:   Hi, > I was looking online and found several possibilities to work > with soap and xslt but I can't wrap my head around how this > really works.   Well, as with any other client (if we restrict the discussion to synchronous SOAP-over-HTTP Web services), technically you have to send POST requests (with the XML message as the payload) and you get the operation's XML response as the payload of the HTTP response.   XSLT is very well suited to construct the XML request and consume the XML response, but you'll need an extension to send HTTP POST requests.  The EXPath HTTP Client is implemented for several processor, check your processor to see if it does support it.  More infos in the following pages (including an example of consuming a SOAP Web service):     http://expath.org/modules/http-client/     http://expath.org/modules/http-client/samples#soap     http://expath.org/spec/http-client > In no example online I see where the URL to the wsdl is > configured.   If you expect more automated support in XSLT from a WSDL, that's another story.  I wrote once a WSDL compiler, that "compiled" a WSDL to a stylesheet defining a function for each Web service operation, hiding all the communication technical details for the user.  So the user can just call a function by passing directly the payload, and getting back the response.   With the WSDL in the above example, the generated function could be called like:     <xsl:stylesheet xmlns:tns="http://www.webservicex.net" ...>        <!-- import the library generated from the WSDL -->        <xsl:import href="compiled-web-service.xsl"/>        <!-- the service operation request -->        <xsl:variable name="request">           <wsx:GetWeatherByPlaceName>              <wsx:PlaceName>NEW YORK</wsx:PlaceName>           </wsx:GetWeatherByPlaceName>        </xsl:variable>        <!-- invoke the service operation -->        <xsl:template name="main">           <xsl:sequence select="               tns:GetWeatherByPlaceName($request)"/>        </xsl:template>     </xsl:stylesheet>   Unfortunately the WSDL compiler was never released, but I can send you a copy if you want...  Of course, it relies on the EXPath HTTP Client in order to send HTTP requests under the hood.   Regards, --  Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324432.html Hi, I'm using xslt 1.0 and i want to acces a Webservice located here: http://newton.level7.ro/newton/NewtonService/NewtonWebservice?wsdl (You might not have acces to it.) I was looking online and found several possibilities to work with soap and xslt but I can't wrap my head around how this really works. In no example online I see where the URL to the wsdl is configured. What is the easiest, best way to use a function from a Webservice in xslt 1.0 ? Thanks in advance! . . . . . . . . . . . . . . . . . . . . . . . . . . Ing. Patrick Szabo XSLT Developer LexisNexis A-1030 Wien, Marxergasse 25 mailto:patrick.szabo@lexisnexis.at Tel.: +43 1 53452 1573 Fax: +43 1 534 52 146 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324431.html Thanks Ken, I'll have a look at your course materials, I'm definitely a hands on learner and working through examples aids immensely Cheers On Thu, Feb 2, 2012 at 11:22 AM, G. Ken Holman <gkholman@cranesoftwrights.com> wrote: > At 2012-02-02 09:29 -0500, Sean Tiley wrote: >> >> Had some troubles with namespaces which still confuses me greatly but >> its working.. > > > Well done.  Your use of namespaces in your stylesheet is correct. > > >> I had thought that the matching expression  should be something like >> <xsl:template match="/agr:SiebelMessage/agr:Message"), then the >> collection select would just have been <xsl:for-each >> select="collection('file:///c:/tmp/?select=*.xml'/agr:Account"> >> >> No matter what I did I could not get that working, thought I'm sure >> it's posible. > > > Not sure what you are trying to do there ... I think you are conflating > different concepts.  The collection() function returns a set of root nodes, > so you are obliged to find your Account element with a full path from the > root node of each document.  There are no shortcuts available by any concept > of matching part of the XPath address before calling the collection() > function. > > >> Seems I need to read up on namespaces and xslt as there is much I do >> not understand > > > You can read what I have to say about namespaces in my PDF book (pp.29-33) > that I sell off my web site (the entire book can be downloaded for free > preview; I ask that people pay for the book if they decide after previewing > it that they want to keep it; I wish more people would be honest about > that). > > You can hear what I have to say about namespaces at the 54m10s mark of > Module 1 Lesson 1 (Lecture 2) of my XSLT/XPath training video (you do not > need to create an account in order to view the free content) ... simply open > that lecture and drag the slider to the time: > >  http://www.CraneSoftwrights.com/links/udemy-ptux-online.htm > > Five hours of my 24-hour long lecture are made freely available.  The > lecture was recorded over 5 days in August 2008.  The course includes > hands-on exercises and I review all of the answers.  The video is also > available to purchase as a DVD-ROM for sharing (not copying) amongst your > colleagues.  Just yesterday I reduced the cost of watching the remaining 19 > hours of the online video and having access to the exercises.  This is the > 2008 version of the material I still teach when I travel the world > delivering my XSLT, XQuery and XSL-FO classes.  Last week I delivered my > combination XSLT/XQuery class in London England, next month I'm delivering > the same combination class in the eastern US. > > I hope this helps. > > . . . . . . . . . . . Ken > > > > -- > Contact us for world-wide XML consulting and instructor-led training > Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h > Crane Softwrights Ltd.            http://www.CraneSoftwrights.com/s/ > G. Ken Holman                   mailto:gkholman@CraneSoftwrights.com > Google+ profile: https://plus.google.com/116832879756988317389/about > 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> > --~-- > -- Sean Tiley sean.tiley@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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324424.html Hermann, This looks challenging enough that I dare say even the interested may not have the time to dig in. What I'm wondering is, why not XSLT 2.0? This could make a very nice demonstration of XSLT 2.0 in the client using Saxon CE. And the code would probably be about one quarter the length, since you'd have actual sequences to work with, could write functions, etc. Cheers, Wendell On 2/1/2012 10:54 AM, Hermann Stamm-Wilbrandt wrote: >> I am not sure I understand the problem but you seem to do something like >> <xsl:if test="document($nxt)"> >> in there and with MSXML I think you get a fatal transformation error if >> the document you are trying to load (i.e. snake.07.xml) does not exist. >> > Thank for that explanation. > Please have a look at the real problem I described in my previous email. > The first time the index of the cube to rotate decreases (idx="7" for > snake and idx="3" for small.xml) the corresponding cube gets drawn at its > original position and not at the correctly transformed position. > You can see that best when starting with snake.00.xml, and then clicking > next two times (with Non-IE browser because of your explanation). > The first rotation is fine, and the problem in the 2nd is easy to see. > > $ tail -20 snake.xml > <cube x="12" y="0" z="11" c="&b;"/> > <cube x="13" y="0" z="11" c="&d;"/> > <cube x="13" y="0" z="12" c="&b;"/> > <cube x="13" y="0" z="13" c="&d;"/> > <!-- > <rot r="z" x0="1" y0="0" idx="4"/> > <rot r="y" x0="1" z0="2" idx="3"/> > --> > > <rot r="x" y0="0" z0="2" idx="3"/> > <rot r="z" x0="1" y0="0" idx="4"/> > <rot r="Y" x0="1" z0="2" idx="4"/> > <rot r="x" y0="0" z0="3" idx="5"/> > <rot r="X" y0="0" z0="4" idx="8"/> > <rot r="y" x0="3" z0="4" idx="7"/> > > <rot r="Z" x0="5" y0="0" idx="10"/> > <rot r="Z" x0="5" y0="0" idx="10"/> > > </snake> > $ > > Mit besten Gruessen / Best wishes, > > Hermann Stamm-Wilbrandt > Level 3 support for XML Compiler team, Fixpack team lead > WebSphere DataPower SOA Appliances > https://www.ibm.com/developerworks/mydeveloperworks/blogs/HermannSW/ > ---------------------------------------------------------------------- > IBM Deutschland Research& Development GmbH > Vorsitzende des Aufsichtsrats: Martina Koederitz > Geschaeftsfuehrung: Dirk Wittkopp > Sitz der Gesellschaft: Boeblingen > Registergericht: Amtsgericht Stuttgart, HRB 243294 > > > > From: Martin Honnen<Martin.Honnen@gmx.de> > > To: xsl-list@lists.mulberrytech.com, > > Date: 02/01/2012 02:01 PM > > Subject: Re: [xsl] Need debug help xslt+svg > > > > > > > Hermann Stamm-Wilbrandt wrote: > >> The problem I need debug help is step 6 of the animation: >> http://stamm-wilbrandt.de/en/xsl-list/cube/snake.00.xml >> >> Clicking on the link gives you the start. The clicking next 5 times >> gives fine results. When clicking the 6th time you can see the >> problem, one of the cubes is not rotated correctly. > > I am not sure I understand the problem but you seem to do something like > <xsl:if test="document($nxt)"> > in there and with MSXML I think you get a fatal transformation error if > the document you are trying to load (i.e. snake.07.xml) does not exist. > > > > -- > > Martin Honnen --- MVP Data Platform Development > 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> > --~-- > > -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324423.html At 2012-02-02 09:29 -0500, Sean Tiley wrote: >Had some troubles with namespaces which still confuses me greatly but >its working.. Well done. Your use of namespaces in your stylesheet is correct. >I had thought that the matching expression should be something like ><xsl:template match="/agr:SiebelMessage/agr:Message"), then the >collection select would just have been <xsl:for-each >select="collection('file:///c:/tmp/?select=*.xml'/agr:Account"> > >No matter what I did I could not get that working, thought I'm sure >it's posible. Not sure what you are trying to do there ... I think you are conflating different concepts. The collection() function returns a set of root nodes, so you are obliged to find your Account element with a full path from the root node of each document. There are no shortcuts available by any concept of matching part of the XPath address before calling the collection() function. >Seems I need to read up on namespaces and xslt as there is much I do >not understand You can read what I have to say about namespaces in my PDF book (pp.29-33) that I sell off my web site (the entire book can be downloaded for free preview; I ask that people pay for the book if they decide after previewing it that they want to keep it; I wish more people would be honest about that). You can hear what I have to say about namespaces at the 54m10s mark of Module 1 Lesson 1 (Lecture 2) of my XSLT/XPath training video (you do not need to create an account in order to view the free content) ... simply open that lecture and drag the slider to the time: http://www.CraneSoftwrights.com/links/udemy-ptux-online.htm Five hours of my 24-hour long lecture are made freely available. The lecture was recorded over 5 days in August 2008. The course includes hands-on exercises and I review all of the answers. The video is also available to purchase as a DVD-ROM for sharing (not copying) amongst your colleagues. Just yesterday I reduced the cost of watching the remaining 19 hours of the online video and having access to the exercises. This is the 2008 version of the material I still teach when I travel the world delivering my XSLT, XQuery and XSL-FO classes. Last week I delivered my combination XSLT/XQuery class in London England, next month I'm delivering the same combination class in the eastern US. I hope this helps. . . . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324422.html Thank you Michael and David, Setting xsl:output method to xml prevent the <meta> to be output. I keep xhtml ouput for compatibility reason, and this <meta> is actually welcomed ! I was just wondering ... Thanks a lot one more time, Hope to see you both at XML Prague :-) Cheers, Matthieu. Le 02/02/2012 15:13, David Carlisle a écrit : > On 02/02/2012 13:49, Matthieu Ricaud-Dussarget wrote: > >> Just one more question about the output : >> A <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> >> element is added to the <head> element, this is the only residual >> unindented element in the file. I'm not sure why saxon add this ? It >> doesn't seems to depend on the xsl:output settings : even when >> xsl:output is absent I get the <meta> added, with no attribute >> @encoding="UTF-8" on the xsl:output I also get the meta.... >> > > your output is defaulting to xhtml method which does this unless you say > include-content-type="no" on xsl:output" > > or specify the xml output method on xsl:output > > 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> > --~-- > > -- Matthieu Ricaud 05 45 37 08 90 NeoLibris --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324421.html Ok, got it working. Had some troubles with namespaces which still confuses me greatly but its working.. let me explain. The source XML files have the followng structure <SiebelMessage xmlns="http://www.siebel.com/xml/CPC%20FBE%20Outbound%20Internal%20IO"> <Message> <Account Version="1.0.4"> <Value1/> <Value2/> ... </Account> </Message> </SiebelMessage> The stylesheet is as follows <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:agr="http://www.siebel.com/xml/CPC%20FBE%20Outbound%20Internal%20IO"> <xsl:template match="/"> <html> <body> <h2>In file analysis</h2> <table border="1"> <tr> <th>Value1</th> <th>Value2</th> </tr> <xsl:for-each select="collection('file:///c:/tmp/?select=*.xml')/agr:SiebelMessage/agr:Message/agr:Account"> <tr> <td> <xsl:value-of select="agr:Value1"/> </td> <td> <xsl:value-of select="agr:Value2"/> </td> </tr> </xsl:for-each> </table> </body> </html> </xsl:template> </xsl:stylesheet> I had thought that the matching expression should be something like <xsl:template match="/agr:SiebelMessage/agr:Message"), then the collection select would just have been <xsl:for-each select="collection('file:///c:/tmp/?select=*.xml'/agr:Account"> No matter what I did I could not get that working, thought I'm sure it's posible. Seems I need to read up on namespaces and xslt as there is much I do not understand Thanks very much for all the help. Much appreciated Sean On Mon, Jan 30, 2012 at 8:15 AM, Sean Tiley <sean.tiley@gmail.com> wrote: > Thank you Ken, very clear. > > I'll give it a whirl and get back, likely tomorrow. > > Sean Tiley > > On Sun, Jan 29, 2012 at 4:37 PM, G. Ken Holman > <gkholman@cranesoftwrights.com> wrote: >> At 2012-01-29 16:28 -0500, Sean Tiley wrote: >>> >>> Hello, >>> I currently have a template that successfully processes a single xml file. >>> >>> XSLT version 2 >>> Using Saxon-SA 9.1.0.7, >>> >>> >>> I would like to iterate through a folder of XML source documents and >>> create a single output file >> >> >> The XSLT 2 concept you are looking for is "collections".  There are no >> standardized URI strings to represent a collection, but Saxon's URI >> convention is straightforward. >> >> You don't show us your data format, but your example could be modified along >> the lines of: >> >> >>> My template that successfully processes my source file is >>> >>> <?xml version="1.0" encoding="utf-8"?> >>> <xsl:stylesheet version="2.0" >>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> >>> >>> <xsl:template match="Account"> >> >> >> You now want to do the logic at the start of processing, so match="/". >> >> >>> <html> >>>       <body> >>>               <h2>LogEntries</h2> >>>          <table border="1"> >>>            <tr bgcolor="#9acd32"> >>>                 <th>Column1</th> >>>                 <th>Column2</th> >>>            </tr> >> >> >> At this point you now want to walk all XML files and, I assume, process the >> document element named "Account" in each one as a row: >> >>  <xsl:for-each select="collection('./?select=*.xml')/Account"> >> >> >>>            <tr> >>>                 <td> >>>                   <xsl:value-of select="Firstname"/> >>>                 </td> >>>                 <td> >>>                   <xsl:value-of select="Lastname"/> >>>               </td> >>>            </tr> >> >> >>  </xsl:for-each> >> >> >>>          </table> >>>       </body> >>> </html> >>> </xsl:template> >>> >>> </xsl:stylesheet> >>> >>> The output I want is basically a single html file >>> that includes a table with 2 columns >>> >>> Column1                    Column2 >>> Firstname1      Lastname1      (info from file1) >>> Firstname2      Lastname2      (info from file2) >>> Firstname3      Lastname3      (info from file3) >>> >>> >>> etc... >>> >>> Not clear this is possible. >> >> >> It certainly is. >> >> >>> I could code it in Java / C# to iterate >>> the docs but kinda feels like it should be possible with just XSLT >>> Any insight or reading would be appreciated. >> >> >> I hope the above helps.  Check the Saxon documentation for all of the >> features of the URI for collections. >> >> . . . . . . . . . . Ken >> >> -- >> Contact us for world-wide XML consulting and instructor-led training >> Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h >> Crane Softwrights Ltd.            http://www.CraneSoftwrights.com/s/ >> G. Ken Holman                   mailto:gkholman@CraneSoftwrights.com >> Google+ profile: https://plus.google.com/116832879756988317389/about >> 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> >> --~-- >> > > > > -- > Sean Tiley > sean.tiley@gmail.com -- Sean Tiley sean.tiley@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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324417.html On 02/02/2012 13:49, Matthieu Ricaud-Dussarget wrote: > Just one more question about the output : > A <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> > element is added to the <head> element, this is the only residual > unindented element in the file. I'm not sure why saxon add this ? It > doesn't seems to depend on the xsl:output settings : even when > xsl:output is absent I get the <meta> added, with no attribute > @encoding="UTF-8" on the xsl:output I also get the meta.... > your output is defaulting to xhtml method which does this unless you say include-content-type="no" on xsl:output" or specify the xml output method on xsl:output 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324416.html > > Just one more question about the output : > A <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" > /> element is added to the <head> element, this is the only residual > unindented element in the file. I'm not sure why saxon add this ? It > doesn't seems to depend on the xsl:output settings : even when > xsl:output is absent I get the <meta> added, with no attribute > @encoding="UTF-8" on the xsl:output I also get the meta.... > > This line is added by the XHTML output method, which is designed on the assumption that the input isn't XHTML. It can be suppressed using <xsl:output include-content-type="no"/>. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324415.html Hi Michael, thanks for your reply. My apologies for the mail, I actually did not thought about different mail ready system. But fortunately your guessing skills helps :-) ! I had -strip:none to the command line and it does the trick : I get exactly the same indentation result as when commenting the DOCTYPE on the source file ! I'm using Saxon-HE 9.2.1.1J I've just tried with the brand new "Saxon-HE 9.4.0.1J", and it is the same behaviour. I guess -strip:none is not the default option. Thanks a lot anyway, this is what I was looking for :-) !! Just one more question about the output : A <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> element is added to the <head> element, this is the only residual unindented element in the file. I'm not sure why saxon add this ? It doesn't seems to depend on the xsl:output settings : even when xsl:output is absent I get the <meta> added, with no attribute @encoding="UTF-8" on the xsl:output I also get the meta.... Regards, Matthieu Le 02/02/2012 12:09, Michael Kay a écrit : > On 02/02/2012 10:48, Matthieu Ricaud-Dussarget wrote: >> Hi all, >> >> In my project I concatenate multiple xhtml files in one xml files. >> This aggregate file has to be edited by hand, that means indentation >> is important here for convenience. >> >> Before I discovered XML Catalog, I used to delete all DOCTYPE >> declarations within source XHTML file with a perl script (which also >> remplace named entities with UTF-8 ones). This worked fine : the >> concatenated files were indented exactly like the XHTML sources. >> >> But this was a bit dangerous in case I didn't match a special entity >> to replace with perl. And this was not a really good XML practice. >> >> Now that I'm using a local XML Catalog and run my tranformation with >> Saxon in command line with this options : >> -r:org.apache.xml.resolver.tools.CatalogResolver >> -x:org.apache.xml.resolver.tools.ResolvingXMLReader >> -y:org.apache.xml.resolver.tools.ResolvingXMLReader >> > I can't see exactly what's happening here because your mail client and > mine have conspired to ignore the whitespace which was critical to > understanding your message. > > Generally, if you validate against a DTD, then whitespace in elements > whose content model is defined as element-only (for example head and > body) will be treated as ignorable, which means it's liable to be lost > in a copy operation. Perhaps this is what is happening. > > Try the option -strip:none on the command line to prevent this > behaviour. The documentation says this is the default, but I'm not > convinced it is correct: I seem to remember it changing some time ago > in response to a W3C change. > > Michael Kay > Saxonica > > --~------------------------------------------------------------------ > XSL-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> > --~-- > > -- Matthieu Ricaud 05 45 37 08 90 NeoLibris --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324411.html Hi Ganesh, Thanks for you reply. I already set up a local XML catalog wich contains xhtml11.dtd, if not i could even not tranform the input. I'm affraid to set indent to yes on the xsl:output in an production environnement cause I don't want extra blanks to be added between word anywhere. I tested it anyway and I don't get the desired output : - many blank lines are generated (inside div element for example) - only a part of the <head> element is indented as desired, I still get : <link href="my.css" rel="stylesheet" type="text/css" /><script type="text/javascript" src="my.js"></script></head> on the same line. As Michael said, I think it has to do with the DTD model itself. I continue investigate. Thanks, Matthieu Le 02/02/2012 12:06, Ganesh Babu N a écrit : > Dear Matthieu, > > You can achieve this by downloading all the modules of xhtml11.dtd and > place them in local and using catalogs and changing the indent to > "yes" which align your XHTML output in a tree structure. There is not > need to comment the DOCTYPE in the source file. > > Regards, > Ganesh > > > On Thu, Feb 2, 2012 at 4:18 PM, Matthieu Ricaud-Dussarget > <matthieu.ricaud@igs-cp.fr> wrote: >> Hi all, >> >> In my project I concatenate multiple xhtml files in one xml files. This >> aggregate file has to be edited by hand, that means indentation is important >> here for convenience. >> >> Before I discovered XML Catalog, I used to delete all DOCTYPE declarations >> within source XHTML file with a perl script (which also remplace named >> entities with UTF-8 ones). This worked fine : the concatenated files were >> indented exactly like the XHTML sources. >> >> But this was a bit dangerous in case I didn't match a special entity to >> replace with perl. And this was not a really good XML practice. >> >> Now that I'm using a local XML Catalog and run my tranformation with Saxon >> in command line with this options : >> -r:org.apache.xml.resolver.tools.CatalogResolver >> -x:org.apache.xml.resolver.tools.ResolvingXMLReader >> -y:org.apache.xml.resolver.tools.ResolvingXMLReader >> >> Lets go in the probleme, my XSL is a simple identity template : >> >> <xsl:output method="xhtml" indent="no" encoding="UTF-8" >> omit-xml-declaration="no" doctype-public="-//W3C//DTD XHTML 1.1//EN" >> doctype-system="http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"/> >> >> <xsl:template match="* | @* | processing-instruction() | comment()" >> mode="copy"> >> <xsl:copy copy-namespaces="no"> >> <xsl:apply-templates select="node()|@*" mode="copy"/> >> </xsl:copy> >> </xsl:template> >> >> <xsl:template match="/"> >> <xsl:apply-templates mode="copy"/> >> </xsl:template> >> >> this is my XML source : >> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" >> "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> >> <html xmlns="http://www.w3.org/1999/xhtml"> >> <head> >> <title>title</title> >> <link href="my.css" rel="stylesheet" type="text/css" /> >> <script type="text/javascript" src="my.js"></script> >> </head> >> <body> >> <div class="body"> >> <div class="pageTitre_container"> >> <h1> >> <span>Title 1</span> >> </h1> >> <p><span class="big">This</span> is<span class="little">a >> paragraphe</span></p> >> <p><span class="big">This</span> is<span class="little">a >> paragraphe</span></p> >> </div> >> </div> >> <table> >> <caption>This is a table</caption> >> <thead> >> <tr> >> <td>Col 1</td> >> <td>Col 2</td> >> <td>Col 3</td> >> <td>Col 4</td> >> <td>Col 5</td> >> </tr> >> </thead> >> <tbody> >> <tr> >> <td> </td> >> <td colspan="3" rowspan="7"> >> <p class="entitre-en-savoir-">À savoir</p> >> <p class="no"> >> <span class="no-style-override-5">Certains grands magasins proposent des >> comparatifs très complets, prenez le temps de les parcourir. Vous pouvez >> également chercher des infos sur Internet via les sites des fabricants, ou >> sur les forums&#160;: rien ne vaut l’avis d’un consommateur pour se faire >> une idée précise du produit&#160;!</span> >> </p> >> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> <td> </td> >> <td> </td> >> <td> </td> >> </tr> >> </tbody> >> </table> >> </body> >> </html> >> >> Which gives as output : >> >> <?xml version="1.0" encoding="UTF-8"?> >> <!DOCTYPE html >> PUBLIC "-//W3C//DTD XHTML 1.1//EN" >> "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> >> <html xmlns="http://www.w3.org/1999/xhtml"><head><meta >> http-equiv="Content-Type" content="text/html; charset=UTF-8" >> /><title>title</title><link href="my.css" rel="stylesheet" type="text/css" >> /><script type="text/javascript" src="my.js"></script></head><body><div >> class="body"> >> <div class="pageTitre_container"> >> <h1> >> <span>Title 1</span> >> </h1> >> <p><span class="big">This</span> is<span class="little">a >> paragraphe</span></p> >> <p><span class="big">This</span> is<span class="little">a >> paragraphe</span></p> >> </div> >> </div><table><caption>This is a table</caption><thead><tr><td>Col >> 1</td><td>Col 2</td><td>Col 3</td><td>Col 4</td><td>Col >> 5</td></tr></thead><tbody><tr><td> </td><td colspan="3" rowspan="7"> >> <p class="entitre-en-savoir-">À savoir</p> >> <p class="no"> >> <span class="no-style-override-5">Certains grands magasins proposent des >> comparatifs très complets, prenez le temps de les parcourir. Vous pouvez >> également chercher des infos sur Internet via les sites des fabricants, ou >> sur les forums : rien ne vaut l’avis d’un consommateur pour se faire une >> idée précise du produit !</span> >> </p> >> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> >> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> >> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> >> </td><td> </td><td> </td><td> </td></tr></tbody></table></body></html> >> >> If I comment the DOCTYPE in the source I get : >> >> <?xml version="1.0" encoding="UTF-8"?><!--<!DOCTYPE html PUBLIC "-//W3C//DTD >> XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">--> >> <!DOCTYPE html >> PUBLIC "-//W3C//DTD XHTML 1.1//EN" >> "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> >> <html xmlns="http://www.w3.org/1999/xhtml"> >> <head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> >> <title>title</title> >> <link href="my.css" rel="stylesheet" type="text/css" /> >> <script type="text/javascript" src="my.js"></script> >> </head> >> <body> >> <div class="body"> >> <div class="pageTitre_container"> >> <h1> >> <span>Title 1</span> >> </h1> >> <p><span class="big">This</span> is<span class="little">a >> paragraphe</span></p> >> <p><span class="big">This</span> is<span class="little">a >> paragraphe</span></p> >> </div> >> </div> >> <table> >> <caption>This is a table</caption> >> <thead> >> <tr> >> <td>Col 1</td> >> <td>Col 2</td> >> <td>Col 3</td> >> <td>Col 4</td> >> <td>Col 5</td> >> </tr> >> </thead> >> <tbody> >> <tr> >> <td> </td> >> <td colspan="3" rowspan="7"> >> <p class="entitre-en-savoir-">À savoir</p> >> <p class="no"> >> <span class="no-style-override-5">Certains grands magasins proposent des >> comparatifs très complets, prenez le temps de les parcourir. Vous pouvez >> également chercher des infos sur Internet via les sites des fabricants, ou >> sur les forums : rien ne vaut l’avis d’un consommateur pour se faire une >> idée précise du produit !</span> >> </p> >> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> </tr> >> <tr> >> <td> </td> >> <td> </td> >> <td> </td> >> <td> </td> >> <td> </td> >> </tr> >> </tbody> >> </table> >> </body> >> </html> >> >> >> the head element is now indented and the table too, this is what i would >> like... but I don't want to comment the doctype in the source. >> >> Has it something to do with the XHTML DTD model ? Any Idea how to achieve >> what I'd like ? >> >> Thanks, >> >> Matthieu. >> >> >> >> >> >> --~------------------------------------------------------------------ >> XSL-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> > --~-- > > -- Matthieu Ricaud 05 45 37 08 90 NeoLibris --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324410.html On 02/02/2012 10:48, Matthieu Ricaud-Dussarget wrote: > Hi all, > > In my project I concatenate multiple xhtml files in one xml files. > This aggregate file has to be edited by hand, that means indentation > is important here for convenience. > > Before I discovered XML Catalog, I used to delete all DOCTYPE > declarations within source XHTML file with a perl script (which also > remplace named entities with UTF-8 ones). This worked fine : the > concatenated files were indented exactly like the XHTML sources. > > But this was a bit dangerous in case I didn't match a special entity > to replace with perl. And this was not a really good XML practice. > > Now that I'm using a local XML Catalog and run my tranformation with > Saxon in command line with this options : > -r:org.apache.xml.resolver.tools.CatalogResolver > -x:org.apache.xml.resolver.tools.ResolvingXMLReader > -y:org.apache.xml.resolver.tools.ResolvingXMLReader > I can't see exactly what's happening here because your mail client and mine have conspired to ignore the whitespace which was critical to understanding your message. Generally, if you validate against a DTD, then whitespace in elements whose content model is defined as element-only (for example head and body) will be treated as ignorable, which means it's liable to be lost in a copy operation. Perhaps this is what is happening. Try the option -strip:none on the command line to prevent this behaviour. The documentation says this is the default, but I'm not convinced it is correct: I seem to remember it changing some time ago in response to a W3C change. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324409.html Dear Matthieu, You can achieve this by downloading all the modules of xhtml11.dtd and place them in local and using catalogs and changing the indent to "yes" which align your XHTML output in a tree structure. There is not need to comment the DOCTYPE in the source file. Regards, Ganesh On Thu, Feb 2, 2012 at 4:18 PM, Matthieu Ricaud-Dussarget <matthieu.ricaud@igs-cp.fr> wrote: > Hi all, > > In my project I concatenate multiple xhtml files in one xml files. This > aggregate file has to be edited by hand, that means indentation is important > here for convenience. > > Before I discovered XML Catalog, I used to delete all DOCTYPE declarations > within source XHTML file with a perl script (which also remplace named > entities with UTF-8 ones). This worked fine : the concatenated files were > indented exactly like the XHTML sources. > > But this was a bit dangerous in case I didn't match a special entity to > replace with perl. And this was not a really good XML practice. > > Now that I'm using a local XML Catalog and run my tranformation with Saxon > in command line with this options : > -r:org.apache.xml.resolver.tools.CatalogResolver > -x:org.apache.xml.resolver.tools.ResolvingXMLReader > -y:org.apache.xml.resolver.tools.ResolvingXMLReader > > Lets go in the probleme, my XSL is a simple identity template : > > <xsl:output method="xhtml" indent="no" encoding="UTF-8" > omit-xml-declaration="no" doctype-public="-//W3C//DTD XHTML 1.1//EN" > doctype-system="http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"/> > > <xsl:template match="* | @* | processing-instruction() | comment()" > mode="copy"> > <xsl:copy copy-namespaces="no"> > <xsl:apply-templates select="node()|@*" mode="copy"/> > </xsl:copy> > </xsl:template> > > <xsl:template match="/"> > <xsl:apply-templates mode="copy"/> > </xsl:template> > > this is my XML source : > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" > "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml"> > <head> > <title>title</title> > <link href="my.css" rel="stylesheet" type="text/css" /> > <script type="text/javascript" src="my.js"></script> > </head> > <body> > <div class="body"> > <div class="pageTitre_container"> > <h1> > <span>Title 1</span> > </h1> > <p><span class="big">This</span> is <span class="little">a > paragraphe</span></p> > <p><span class="big">This</span> is <span class="little">a > paragraphe</span></p> > </div> > </div> > <table> > <caption>This is a table</caption> > <thead> > <tr> > <td>Col 1</td> > <td>Col 2</td> > <td>Col 3</td> > <td>Col 4</td> > <td>Col 5</td> > </tr> > </thead> > <tbody> > <tr> > <td> </td> > <td colspan="3" rowspan="7"> > <p class="entitre-en-savoir-">À savoir</p> > <p class="no"> > <span class="no-style-override-5">Certains grands magasins proposent des > comparatifs très complets, prenez le temps de les parcourir. Vous pouvez > également chercher des infos sur Internet via les sites des fabricants, ou > sur les forums&#160;: rien ne vaut l’avis d’un consommateur pour se faire > une idée précise du produit&#160;!</span> > </p> > </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > <td> </td> > <td> </td> > <td> </td> > </tr> > </tbody> > </table> > </body> > </html> > > Which gives as output : > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE html >  PUBLIC "-//W3C//DTD XHTML 1.1//EN" > "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml"><head><meta > http-equiv="Content-Type" content="text/html; charset=UTF-8" > /><title>title</title><link href="my.css" rel="stylesheet" type="text/css" > /><script type="text/javascript" src="my.js"></script></head><body><div > class="body"> > <div class="pageTitre_container"> > <h1> > <span>Title 1</span> > </h1> > <p><span class="big">This</span> is <span class="little">a > paragraphe</span></p> > <p><span class="big">This</span> is <span class="little">a > paragraphe</span></p> > </div> > </div><table><caption>This is a table</caption><thead><tr><td>Col > 1</td><td>Col 2</td><td>Col 3</td><td>Col 4</td><td>Col > 5</td></tr></thead><tbody><tr><td> </td><td colspan="3" rowspan="7"> > <p class="entitre-en-savoir-">À savoir</p> > <p class="no"> > <span class="no-style-override-5">Certains grands magasins proposent des > comparatifs très complets, prenez le temps de les parcourir. Vous pouvez > également chercher des infos sur Internet via les sites des fabricants, ou > sur les forums : rien ne vaut l’avis d’un consommateur pour se faire une > idée précise du produit !</span> > </p> > </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> > </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> > </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> > </td><td> </td><td> </td><td> </td></tr></tbody></table></body></html> > > If I comment the DOCTYPE in the source I get : > > <?xml version="1.0" encoding="UTF-8"?><!--<!DOCTYPE html PUBLIC "-//W3C//DTD > XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">--> > <!DOCTYPE html >  PUBLIC "-//W3C//DTD XHTML 1.1//EN" > "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml"> > <head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> > <title>title</title> > <link href="my.css" rel="stylesheet" type="text/css" /> > <script type="text/javascript" src="my.js"></script> > </head> > <body> > <div class="body"> > <div class="pageTitre_container"> > <h1> > <span>Title 1</span> > </h1> > <p><span class="big">This</span> is <span class="little">a > paragraphe</span></p> > <p><span class="big">This</span> is <span class="little">a > paragraphe</span></p> > </div> > </div> > <table> > <caption>This is a table</caption> > <thead> > <tr> > <td>Col 1</td> > <td>Col 2</td> > <td>Col 3</td> > <td>Col 4</td> > <td>Col 5</td> > </tr> > </thead> > <tbody> > <tr> > <td> </td> > <td colspan="3" rowspan="7"> > <p class="entitre-en-savoir-">À savoir</p> > <p class="no"> > <span class="no-style-override-5">Certains grands magasins proposent des > comparatifs très complets, prenez le temps de les parcourir. Vous pouvez > également chercher des infos sur Internet via les sites des fabricants, ou > sur les forums : rien ne vaut l’avis d’un consommateur pour se faire une > idée précise du produit !</span> > </p> > </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > </tr> > <tr> > <td> </td> > <td> </td> > <td> </td> > <td> </td> > <td> </td> > </tr> > </tbody> > </table> > </body> > </html> > > > the head element is now indented and the table too, this is what i would > like... but I don't want to comment the doctype in the source. > > Has it something to do with the XHTML DTD model ? Any Idea how to achieve > what I'd like ? > > Thanks, > > Matthieu. > > > > > > --~------------------------------------------------------------------ > XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324408.html Hi all, In my project I concatenate multiple xhtml files in one xml files. This aggregate file has to be edited by hand, that means indentation is important here for convenience. Before I discovered XML Catalog, I used to delete all DOCTYPE declarations within source XHTML file with a perl script (which also remplace named entities with UTF-8 ones). This worked fine : the concatenated files were indented exactly like the XHTML sources. But this was a bit dangerous in case I didn't match a special entity to replace with perl. And this was not a really good XML practice. Now that I'm using a local XML Catalog and run my tranformation with Saxon in command line with this options : -r:org.apache.xml.resolver.tools.CatalogResolver -x:org.apache.xml.resolver.tools.ResolvingXMLReader -y:org.apache.xml.resolver.tools.ResolvingXMLReader Lets go in the probleme, my XSL is a simple identity template : <xsl:output method="xhtml" indent="no" encoding="UTF-8" omit-xml-declaration="no" doctype-public="-//W3C//DTD XHTML 1.1//EN" doctype-system="http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"/> <xsl:template match="* | @* | processing-instruction() | comment()" mode="copy"> <xsl:copy copy-namespaces="no"> <xsl:apply-templates select="node()|@*" mode="copy"/> </xsl:copy> </xsl:template> <xsl:template match="/"> <xsl:apply-templates mode="copy"/> </xsl:template> this is my XML source : <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>title</title> <link href="my.css" rel="stylesheet" type="text/css" /> <script type="text/javascript" src="my.js"></script> </head> <body> <div class="body"> <div class="pageTitre_container"> <h1> <span>Title 1</span> </h1> <p><span class="big">This</span> is <span class="little">a paragraphe</span></p> <p><span class="big">This</span> is <span class="little">a paragraphe</span></p> </div> </div> <table> <caption>This is a table</caption> <thead> <tr> <td>Col 1</td> <td>Col 2</td> <td>Col 3</td> <td>Col 4</td> <td>Col 5</td> </tr> </thead> <tbody> <tr> <td> </td> <td colspan="3" rowspan="7"> <p class="entitre-en-savoir-">À savoir</p> <p class="no"> <span class="no-style-override-5">Certains grands magasins proposent des comparatifs très complets, prenez le temps de les parcourir. Vous pouvez également chercher des infos sur Internet via les sites des fabricants, ou sur les forums&#160;: rien ne vaut l’avis d’un consommateur pour se faire une idée précise du produit&#160;!</span> </p> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> </tbody> </table> </body> </html> Which gives as output : <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>title</title><link href="my.css" rel="stylesheet" type="text/css" /><script type="text/javascript" src="my.js"></script></head><body><div class="body"> <div class="pageTitre_container"> <h1> <span>Title 1</span> </h1> <p><span class="big">This</span> is <span class="little">a paragraphe</span></p> <p><span class="big">This</span> is <span class="little">a paragraphe</span></p> </div> </div><table><caption>This is a table</caption><thead><tr><td>Col 1</td><td>Col 2</td><td>Col 3</td><td>Col 4</td><td>Col 5</td></tr></thead><tbody><tr><td> </td><td colspan="3" rowspan="7"> <p class="entitre-en-savoir-">À savoir</p> <p class="no"> <span class="no-style-override-5">Certains grands magasins proposent des comparatifs très complets, prenez le temps de les parcourir. Vous pouvez également chercher des infos sur Internet via les sites des fabricants, ou sur les forums : rien ne vaut l’avis d’un consommateur pour se faire une idée précise du produit !</span> </p> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> </td></tr><tr><td> </td><td> </td><td> </td><td> </td><td> </td></tr></tbody></table></body></html> If I comment the DOCTYPE in the source I get : <?xml version="1.0" encoding="UTF-8"?><!--<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">--> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>title</title> <link href="my.css" rel="stylesheet" type="text/css" /> <script type="text/javascript" src="my.js"></script> </head> <body> <div class="body"> <div class="pageTitre_container"> <h1> <span>Title 1</span> </h1> <p><span class="big">This</span> is <span class="little">a paragraphe</span></p> <p><span class="big">This</span> is <span class="little">a paragraphe</span></p> </div> </div> <table> <caption>This is a table</caption> <thead> <tr> <td>Col 1</td> <td>Col 2</td> <td>Col 3</td> <td>Col 4</td> <td>Col 5</td> </tr> </thead> <tbody> <tr> <td> </td> <td colspan="3" rowspan="7"> <p class="entitre-en-savoir-">À savoir</p> <p class="no"> <span class="no-style-override-5">Certains grands magasins proposent des comparatifs très complets, prenez le temps de les parcourir. Vous pouvez également chercher des infos sur Internet via les sites des fabricants, ou sur les forums : rien ne vaut l’avis d’un consommateur pour se faire une idée précise du produit !</span> </p> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> </tbody> </table> </body> </html> the head element is now indented and the table too, this is what i would like... but I don't want to comment the doctype in the source. Has it something to do with the XHTML DTD model ? Any Idea how to achieve what I'd like ? Thanks, Matthieu. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324407.html General Atomics Aeronautical in San Diego CA is looking for a tools developer to help support our IETM development and support the team of writers. We are looking for just about any combination of these skills: - S1000D - DITA - Mil Spec publishing background - Army IADS development - SGML - FOSI - Arbortext customization - Perl, Javascript, Java - XML This is a full time direct position and is located in Poway (outside San Diego). For complete details see https://search9.smartsearchonline.com/asi/jobs/jobdetails.asp?current_page=1&city=&location=&job_type=&emp_status=&direct_jo_num=&country=&k1=IETMS&k2=&k3=&k4=&k5=&k6=&k7=&k8=&salary_min=&co_num=&apply=yes&job_number=11446 or contact me directly at dvint@dvint.com --------------------------------------------------------------------------- Danny Vint Panoramic Photography http://www.dvint.com voice: 619-938-3610 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324401.html 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. If you have difficulties unsubscribing from the list: - make sure you are unsubscribing EXACTLY the email address that is subscribed - if you receive only one message a day from the list be sure to check the box marked "Select for the Digest version of the list" (if you subscribe to the digest and don't check this box the system will try to unsubscribe you from the regular list and fail; it will only unsubscribe you from the digest if you check this box.) 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 and check the box marked "Select for the Digest version of the list". 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/xsl/index.html. The W3C information on XSL is at http://www.w3.org/Style/XSL. Mulberry's Quick References are at http://www.mulberrytech.com/quickref/ and cover XSLT, XPath, and XQuery. 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 ============== December 26, 2011 - btu. 11. Clarified instructions on unsubscribing from the digest version of the list. ============== 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324379.html > I am not sure I understand the problem but you seem to do something like > <xsl:if test="document($nxt)"> > in there and with MSXML I think you get a fatal transformation error if > the document you are trying to load (i.e. snake.07.xml) does not exist. > Thank for that explanation. Please have a look at the real problem I described in my previous email. The first time the index of the cube to rotate decreases (idx="7" for snake and idx="3" for small.xml) the corresponding cube gets drawn at its original position and not at the correctly transformed position. You can see that best when starting with snake.00.xml, and then clicking next two times (with Non-IE browser because of your explanation). The first rotation is fine, and the problem in the 2nd is easy to see. $ tail -20 snake.xml <cube x="12" y="0" z="11" c="&b;"/> <cube x="13" y="0" z="11" c="&d;"/> <cube x="13" y="0" z="12" c="&b;"/> <cube x="13" y="0" z="13" c="&d;"/> <!-- <rot r="z" x0="1" y0="0" idx="4"/> <rot r="y" x0="1" z0="2" idx="3"/> --> <rot r="x" y0="0" z0="2" idx="3"/> <rot r="z" x0="1" y0="0" idx="4"/> <rot r="Y" x0="1" z0="2" idx="4"/> <rot r="x" y0="0" z0="3" idx="5"/> <rot r="X" y0="0" z0="4" idx="8"/> <rot r="y" x0="3" z0="4" idx="7"/> <rot r="Z" x0="5" y0="0" idx="10"/> <rot r="Z" x0="5" y0="0" idx="10"/> </snake> $ Mit besten Gruessen / Best wishes, Hermann Stamm-Wilbrandt Level 3 support for XML Compiler team, Fixpack team lead WebSphere DataPower SOA Appliances https://www.ibm.com/developerworks/mydeveloperworks/blogs/HermannSW/ ---------------------------------------------------------------------- IBM Deutschland Research & Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschaeftsfuehrung: Dirk Wittkopp Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 From: Martin Honnen <Martin.Honnen@gmx.de> To: xsl-list@lists.mulberrytech.com, Date: 02/01/2012 02:01 PM Subject: Re: [xsl] Need debug help xslt+svg Hermann Stamm-Wilbrandt wrote: > The problem I need debug help is step 6 of the animation: > http://stamm-wilbrandt.de/en/xsl-list/cube/snake.00.xml > > Clicking on the link gives you the start. The clicking next 5 times > gives fine results. When clicking the 6th time you can see the > problem, one of the cubes is not rotated correctly. I am not sure I understand the problem but you seem to do something like <xsl:if test="document($nxt)"> in there and with MSXML I think you get a fatal transformation error if the document you are trying to load (i.e. snake.07.xml) does not exist. -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324368.html The way I tackle most regex problems is to break them up. I would do this one by first tokenizing on ';' and then tokenizing each token on ','. We've inherited from the Perl regex tradition the idea that each capturing subexpression (i.e. each occurrence of "(...)" in the source) captures zero or one substrings. It could have been done better (and perhaps with the new fn:analyze-string() in 3.0 which generates a marked-up version of the input string we should have tried), but everyone is scared of doing things that are beyond the scope of existing regex libraries. Personally, having just integrated a modified version of Jakarta into Saxon, I'm less scared of this than I was. But that's the way xsl:analyze-string is defined, and it's defined that way for reasons of compatibility with the Perl regex tradition. Michael Kay Saxonica On 01/02/2012 14:42, Florent Georges wrote: > Hi, > > Let's say I have a string of the form "a:b;c:d;" where there > can be any number of sub-parts of the form "x:y;", that I'd like > to parse using xsl:analyze-string. With the following regex: > > ^(([a-z]):([a-z]);)+$ > > which matches indeed, I cannot use the regex-groups to retrieve > all values. For instance the following: > > <xsl:analyze-string select="'a:b;c:d;'" > regex="^(([a-z]):([a-z]);)+$"> > <xsl:matching-substring> > <group num="0" value="{ regex-group(0) }"/> > <group num="1" value="{ regex-group(1) }"/> > <group num="2" value="{ regex-group(2) }"/> > <group num="3" value="{ regex-group(3) }"/> > <group num="4" value="{ regex-group(4) }"/> > <group num="5" value="{ regex-group(5) }"/> > <group num="6" value="{ regex-group(6) }"/> > <group num="7" value="{ regex-group(7) }"/> > </xsl:matching-substring> > </xsl:analyze-string> > > returns the following: > > <group num="0" value="a:b;c:d;"/> > <group num="1" value="c:d;"/> > <group num="2" value="c"/> > <group num="3" value="d"/> > <group num="4" value=""/> > <group num="5" value=""/> > <group num="6" value=""/> > <group num="7" value=""/> > > when I would have expected the following instead: > > <group num="0" value="a:b;c:d;"/> > <group num="1" value="a:b;"/> > <group num="2" value="a"/> > <group num="3" value="b"/> > <group num="4" value="c:d;"/> > <group num="5" value="c"/> > <group num="6" value="d"/> > <group num="7" value=""/> > > That is, I expected the regex-groups to match the "dynamic" > number of groups, instead of the strict "static" or "lexical" > group numbering from the regex string. I thought that was what > I was used to in Perl and other tools, by I can't recall for > sure, and I didn't find a definitive answer in the spec. > > Are my expectations wrong? If yes why? And if yes, is there > any general solution to this problem? (by "general", I mean not > recursing on the string and using substring on ';' because here > this is a simple delimiter) > > BTW, tested with Saxon HE 9.3.0.5 and 9.4.0.2. > > Regards, > > -- > Florent Georges > http://fgeorges.org/ > http://h2oconsulting.be/ > > --~------------------------------------------------------------------ > XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324367.html Florent Georges wrote: > Let's say I have a string of the form "a:b;c:d;" where there > can be any number of sub-parts of the form "x:y;", that I'd like > to parse using xsl:analyze-string. With the following regex: > > ^(([a-z]):([a-z]);)+$ > > which matches indeed, I cannot use the regex-groups to retrieve > all values. For instance the following: > > <xsl:analyze-string select="'a:b;c:d;'" > regex="^(([a-z]):([a-z]);)+$"> > <xsl:matching-substring> > <group num="0" value="{ regex-group(0) }"/> > <group num="1" value="{ regex-group(1) }"/> > <group num="2" value="{ regex-group(2) }"/> > Are my expectations wrong? If yes why? And if yes, is there > any general solution to this problem? (by "general", I mean not > recursing on the string and using substring on ';' because here > this is a simple delimiter) Shouldn't it suffice to do <xsl:analyze-string select="'a:b;c:d;'" regex="([a-z]):([a-z]);"> <xsl:matching-substring> <!-- now access groups here --> </xsl:matching-substring> </xsl:analyze-string> then matching-substring is "called" for every part of the form "x:y;". -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324366.html   Hi,   Let's say I have a string of the form "a:b;c:d;" where there can be any number of sub-parts of the form "x:y;", that I'd like to parse using xsl:analyze-string.  With the following regex:     ^(([a-z]):([a-z]);)+$ which matches indeed, I cannot use the regex-groups to retrieve all values.  For instance the following:     <xsl:analyze-string select="'a:b;c:d;'"                         regex="^(([a-z]):([a-z]);)+$">        <xsl:matching-substring>           <group num="0" value="{ regex-group(0) }"/>           <group num="1" value="{ regex-group(1) }"/>           <group num="2" value="{ regex-group(2) }"/>           <group num="3" value="{ regex-group(3) }"/>           <group num="4" value="{ regex-group(4) }"/>           <group num="5" value="{ regex-group(5) }"/>           <group num="6" value="{ regex-group(6) }"/>           <group num="7" value="{ regex-group(7) }"/>        </xsl:matching-substring>     </xsl:analyze-string> returns the following:     <group num="0" value="a:b;c:d;"/>     <group num="1" value="c:d;"/>     <group num="2" value="c"/>     <group num="3" value="d"/>     <group num="4" value=""/>     <group num="5" value=""/>     <group num="6" value=""/>     <group num="7" value=""/> when I would have expected the following instead:     <group num="0" value="a:b;c:d;"/>     <group num="1" value="a:b;"/>     <group num="2" value="a"/>     <group num="3" value="b"/>     <group num="4" value="c:d;"/>     <group num="5" value="c"/>     <group num="6" value="d"/>     <group num="7" value=""/>   That is, I expected the regex-groups to match the "dynamic" number of groups, instead of the strict "static" or "lexical" group numbering from the regex string.  I thought that was what I was used to in Perl and other tools, by I can't recall for sure, and I didn't find a definitive answer in the spec.   Are my expectations wrong?  If yes why?  And if yes, is there any general solution to this problem? (by "general", I mean not recursing on the string and using substring on ';' because here this is a simple delimiter)   BTW, tested with Saxon HE 9.3.0.5 and 9.4.0.2.   Regards, --  Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324362.html Hermann Stamm-Wilbrandt wrote: > The problem I need debug help is step 6 of the animation: > http://stamm-wilbrandt.de/en/xsl-list/cube/snake.00.xml > > Clicking on the link gives you the start. The clicking next 5 times > gives fine results. When clicking the 6th time you can see the > problem, one of the cubes is not rotated correctly. I am not sure I understand the problem but you seem to do something like <xsl:if test="document($nxt)"> in there and with MSXML I think you get a fatal transformation error if the document you are trying to load (i.e. snake.07.xml) does not exist. -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324359.html Hello, last year I visited a science museum with my kids. There was an area with different puzzles. I liked the "snake cube" puzzle, 27 wooden cubes hold together by an elastic band (not visible), see this photo: http://stamm-wilbrandt.de/en/xsl-list/cube/111029_140526.jpg The task was to fold the cubes to finally build a 3x3x3 cube. We bought a small version of that puzzle at the museum shop. I was able to solve the puzzle and wanted to do a 3D demonstration of the solution steps. I was really surprised how easy it is to generate graphics in the browser with SVG. I did a handmade 3D view by drawing the little cubes in the right order resulting in removal of all hidden stuff. Of course this was done with XSLT. Although I do not use IE browser I installed IE9 on my home computer just to verify that it really can display SVG. By David Carlisle's exslt-node-set-function blog posting the exslt:node-set() calls work fine even in IE. The problem I need debug help is step 6 of the animation: http://stamm-wilbrandt.de/en/xsl-list/cube/snake.00.xml Clicking on the link gives you the start. The clicking next 5 times gives fine results. When clicking the 6th time you can see the problem, one of the cubes is not rotated correctly. This happens exactly when the cube id of the cube where the rotation should be done decreases for the first time. This is a smaller example for debugging, problem in 2nd step: http://stamm-wilbrandt.de/en/xsl-list/cube/small.00.xml I added xsl:message output to view.xsl and the problem is that the 3rd cube does not get the coordinates which are correctly computed for step 1 as basis for step 2. I have no idea why this happens and appreciate any help. Interestingly IE9 does not do step 2 but reports an XSLT execution error in browser console, but no details on where&why. This is console output for small.01.xml: xsl:message - 1:0/0/0 : id0x000000000261afc0 | 0/0/1 : id0x000000000261b000 | 0/0/2 : id0x000000000261b040 | 1/0/2 : id0x000000000261af80 | xsl:message - 0:1/-1/0 : id0x00000000051dd040 | 1/-1/1 : id0x00000000051dd5c0 | 1/-1/2 : id0x00000000053d8940 | 1/0/2 : id0x00000000053d8a40 | 1/-1/2 is correct coordinate after first rotation for 3rd cube. This is console output for small.02.xml: xsl:message - 2:0/0/0 : id0x000000000bb3b680 | 0/0/1 : id0x000000000bb3b740 | 0/0/2 : id0x000000000bb3b7c0 | 1/0/2 : id0x000000000bb3b540 | xsl:message - 1:1/-1/0 : id0x000000000de03380 | 1/-1/1 : id0x000000000de03480 | 0/0/2 : id0x000000000de03940 | 1/0/2 : id0x000000000de23140 | xsl:message - 0:3/-1/2 : id0x000000000e9fa680 | 2/-1/2 : id0x000000000e9fac40 | 0/0/2 : id0x000000000ea01040 | 1/0/2 : id0x000000000ea01140 | The 3rd cube in middle line is 0/0/2 but should be 1/-1/2 ... All files are available under http://stamm-wilbrandt.de/en/xsl-list/cube ftp> dir 227 Entering Passive Mode (93,90,177,145,163,97). 150 Opening ASCII mode data connection for file list drwxr-xr-x 2 web138 web138 4096 Feb 1 11:09 . drwxr-xr-x 20 web138 web138 4096 Dec 1 10:12 .. -rw-r--r-- 1 web138 web138 178592 Feb 1 11:09 111029_140526.jpg -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 small.00.xml -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 small.01.xml -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 small.02.xml -rw-r--r-- 1 web138 web138 1452 Feb 1 10:47 small.xml -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 snake.00.xml -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 snake.01.xml -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 snake.02.xml -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 snake.03.xml -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 snake.04.xml -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 snake.05.xml -rw-r--r-- 1 web138 web138 88 Feb 1 10:47 snake.06.xml -rw-r--r-- 1 web138 web138 1452 Feb 1 10:47 snake.xml -rw-r--r-- 1 web138 web138 7370 Feb 1 10:47 view.xsl 226 Transfer complete. ftp> Mit besten Gruessen / Best wishes, Hermann Stamm-Wilbrandt Level 3 support for XML Compiler team, Fixpack team lead WebSphere DataPower SOA Appliances https://www.ibm.com/developerworks/mydeveloperworks/blogs/HermannSW/ ---------------------------------------------------------------------- IBM Deutschland Research & Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschaeftsfuehrung: Dirk Wittkopp Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201202/msg1000324357.html As others have said, this can be an intractable problem unless the names really are only in the format FirstName MiddleInitial LastName in your data. You need to bear in mind names like "Michael O'Connell" or "Mary da Silva". You can find some food for thought here: http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ -----Original Message----- From: Michael Kay [mailto:mike@saxonica.com] Sent: 30 January 2012 18:21 To: xsl-list@lists.mulberrytech.com Subject: Re: [xsl] Last name first On 30/01/2012 17:51, Jacob L wrote: > All, > > > I am using<xsl:stylesheet version="2.0" .If in the input XML file, > the text in the<p>has a name such as > > <p> Aaron S. Williams</p> > > and I want the last name to come first, seperated by comma like this > > <p> Williams, Aaron S.</p> > > Is it possible using xslt? It's certainly possible if you can specify precisely what the rules are: for example, what you want to happen to names like Herbert von Karajan or Ralph Vaughan Williams. If all your names are in the simplified American format of John X. Doe then it's fairly easy, but with real names occurring in the real world it's much harder (regardless of what programming language you choose). Michael Kay Saxonica > --~------------------------------------------------------------------ XSL-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> --~-- ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324349.html On 30/01/2012 17:51, Jacob L wrote: > All, > > > I am using<xsl:stylesheet version="2.0" .If in the input XML file, > the text in the<p>has a name such as > > <p> Aaron S. Williams</p> > > and I want the last name to come first, seperated by comma like this > > <p> Williams, Aaron S.</p> > > Is it possible using xslt? It's certainly possible if you can specify precisely what the rules are: for example, what you want to happen to names like Herbert von Karajan or Ralph Vaughan Williams. If all your names are in the simplified American format of John X. Doe then it's fairly easy, but with real names occurring in the real world it's much harder (regardless of what programming language you choose). Michael Kay Saxonica > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324341.html Jacob L wrote: > I am using<xsl:stylesheet version="2.0" .If in the input XML file, > the text in the<p>has a name such as > > <p> Aaron S. Williams</p> > > and I want the last name to come first, seperated by comma like this > > <p> Williams, Aaron S.</p> > > Is it possible using xslt? Look into xsl:analyze-string http://www.w3.org/TR/xslt20/#analyze-string. If you need help with precise code then please first explain in more detail whether you expect "p" elements to solely contain names or whether you want to look for names in some more complex content. -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324340.html All, I am using <xsl:stylesheet version="2.0" .If in the input XML file, the text in the <p>has a name such as <p> Aaron S. Williams </p> and I want the last name to come first, seperated by comma like this <p> Williams, Aaron S. </p> Is it possible using xslt?If yes, could i have the code plz. 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324339.html Thank you Ken, very clear. I'll give it a whirl and get back, likely tomorrow. Sean Tiley On Sun, Jan 29, 2012 at 4:37 PM, G. Ken Holman <gkholman@cranesoftwrights.com> wrote: > At 2012-01-29 16:28 -0500, Sean Tiley wrote: >> >> Hello, >> I currently have a template that successfully processes a single xml file. >> >> XSLT version 2 >> Using Saxon-SA 9.1.0.7, >> >> >> I would like to iterate through a folder of XML source documents and >> create a single output file > > > The XSLT 2 concept you are looking for is "collections".  There are no > standardized URI strings to represent a collection, but Saxon's URI > convention is straightforward. > > You don't show us your data format, but your example could be modified along > the lines of: > > >> My template that successfully processes my source file is >> >> <?xml version="1.0" encoding="utf-8"?> >> <xsl:stylesheet version="2.0" >> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> >> >> <xsl:template match="Account"> > > > You now want to do the logic at the start of processing, so match="/". > > >> <html> >>       <body> >>               <h2>LogEntries</h2> >>          <table border="1"> >>            <tr bgcolor="#9acd32"> >>                 <th>Column1</th> >>                 <th>Column2</th> >>            </tr> > > > At this point you now want to walk all XML files and, I assume, process the > document element named "Account" in each one as a row: > >  <xsl:for-each select="collection('./?select=*.xml')/Account"> > > >>            <tr> >>                 <td> >>                   <xsl:value-of select="Firstname"/> >>                 </td> >>                 <td> >>                   <xsl:value-of select="Lastname"/> >>               </td> >>            </tr> > > >  </xsl:for-each> > > >>          </table> >>       </body> >> </html> >> </xsl:template> >> >> </xsl:stylesheet> >> >> The output I want is basically a single html file >> that includes a table with 2 columns >> >> Column1                    Column2 >> Firstname1      Lastname1      (info from file1) >> Firstname2      Lastname2      (info from file2) >> Firstname3      Lastname3      (info from file3) >> >> >> etc... >> >> Not clear this is possible. > > > It certainly is. > > >> I could code it in Java / C# to iterate >> the docs but kinda feels like it should be possible with just XSLT >> Any insight or reading would be appreciated. > > > I hope the above helps.  Check the Saxon documentation for all of the > features of the URI for collections. > > . . . . . . . . . . Ken > > -- > Contact us for world-wide XML consulting and instructor-led training > Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h > Crane Softwrights Ltd.            http://www.CraneSoftwrights.com/s/ > G. Ken Holman                   mailto:gkholman@CraneSoftwrights.com > Google+ profile: https://plus.google.com/116832879756988317389/about > 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> > --~-- > -- Sean Tiley sean.tiley@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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324330.html At 2012-01-29 16:28 -0500, Sean Tiley wrote: >Hello, >I currently have a template that successfully processes a single xml file. > >XSLT version 2 >Using Saxon-SA 9.1.0.7, > > >I would like to iterate through a folder of XML source documents and >create a single output file The XSLT 2 concept you are looking for is "collections". There are no standardized URI strings to represent a collection, but Saxon's URI convention is straightforward. You don't show us your data format, but your example could be modified along the lines of: >My template that successfully processes my source file is > ><?xml version="1.0" encoding="utf-8"?> ><xsl:stylesheet version="2.0" >xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> > ><xsl:template match="Account"> You now want to do the logic at the start of processing, so match="/". ><html> > <body> > <h2>LogEntries</h2> > <table border="1"> > <tr bgcolor="#9acd32"> > <th>Column1</th> > <th>Column2</th> > </tr> At this point you now want to walk all XML files and, I assume, process the document element named "Account" in each one as a row: <xsl:for-each select="collection('./?select=*.xml')/Account"> > <tr> > <td> > <xsl:value-of select="Firstname"/> > </td> > <td> > <xsl:value-of select="Lastname"/> > </td> > </tr> </xsl:for-each> > </table> > </body> ></html> ></xsl:template> > ></xsl:stylesheet> > >The output I want is basically a single html file >that includes a table with 2 columns > >Column1 Column2 >Firstname1 Lastname1 (info from file1) >Firstname2 Lastname2 (info from file2) >Firstname3 Lastname3 (info from file3) > > >etc... > >Not clear this is possible. It certainly is. >I could code it in Java / C# to iterate >the docs but kinda feels like it should be possible with just XSLT >Any insight or reading would be appreciated. I hope the above helps. Check the Saxon documentation for all of the features of the URI for collections. . . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324321.html Hello, I currently have a template that successfully processes a single xml file. XSLT version 2 Using Saxon-SA 9.1.0.7, I would like to iterate through a folder of XML source documents and create a single output file My template that successfully processes my source file is <?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="Account"> <html> <body> <h2>LogEntries</h2> <table border="1"> <tr bgcolor="#9acd32"> <th>Column1</th> <th>Column2</th> </tr> <tr> <td> <xsl:value-of select="Firstname"/> </td> <td> <xsl:value-of select="Lastname"/> </td> </tr> </table> </body> </html> </xsl:template> </xsl:stylesheet> The output I want is basically a single html file that includes a table with 2 columns Column1 Column2 Firstname1 Lastname1 (info from file1) Firstname2 Lastname2 (info from file2) Firstname3 Lastname3 (info from file3) etc... Not clear this is possible. I could code it in Java / C# to iterate the docs but kinda feels like it should be possible with just XSLT Any insight or reading would be 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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324320.html It seems to me that the OP wants to be provided with a simple but complete working XQuery example, that uses Saxon's maps. He seems to have syntactic difficulties. Or, is the maps feature implemented only in the XSLT processor? Cheers, Dimitre Novatchev. On Sat, Jan 28, 2012 at 11:30 AM, Michael Kay <mike@saxonica.com> wrote: > > On 28/01/2012 16:34, Jakub Maly wrote: >> >> I would like to experiment with map features in Saxon (http://www.saxonica.com/documentation/expressions/xpath30maps.xml), but I am unable to get past query compilation. Maybe I am missing some parameter or I use a wrong namespace, but I just can't find the right answer. This is my query code: >> >> > Unfortunately, maps as implemented in Saxon-PE 9.4 (both XSLT and XQuery) are not documented either in any published W3C working draft, nor in the Saxon documentation. I have remedied this by placing a specification at: > > http://dev.saxonica.com/blog/mike/2012/01/#000188 > > Any resemblance to any spec that might be published by some future W3C working group is entirely serendipitous. > > Michael Kay > Saxonica > > > --~------------------------------------------------------------------ > XSL-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> > --~-- > -- 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 ------------------------------------- To avoid situations in which you might make mistakes may be the biggest mistake of all ------------------------------------ Quality means doing it right when no one is looking. ------------------------------------- You've achieved success in your field when you don't know whether what you're doing is work or play ------------------------------------- Facts do not cease to exist because they are ignored. ------------------------------------- I finally figured out the only reason to be alive is to enjoy it. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324311.html On 28/01/2012 16:34, Jakub Maly wrote: > I would like to experiment with map features in Saxon (http://www.saxonica.com/documentation/expressions/xpath30maps.xml), but I am unable to get past query compilation. Maybe I am missing some parameter or I use a wrong namespace, but I just can't find the right answer. This is my query code: > > Unfortunately, maps as implemented in Saxon-PE 9.4 (both XSLT and XQuery) are not documented either in any published W3C working draft, nor in the Saxon documentation. I have remedied this by placing a specification at: http://dev.saxonica.com/blog/mike/2012/01/#000188 Any resemblance to any spec that might be published by some future W3C working group is entirely serendipitous. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324310.html Jakub Maly wrote: > > I would like to experiment with map features in Saxon (http://www.saxonica.com/documentation/expressions/xpath30maps.xml), but I am unable to get past query compilation. Maybe I am missing some parameter or I use a wrong namespace, but I just can't find the right answer. This is my query code: > > xquery version "3.0"; This is the XSL mailing list, I don't think XQuery is on topic here. There is an XQuery mailing list and Saxon also has its own mailing list where you can ask. -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324308.html I would like to experiment with map features in Saxon (http://www.saxonica.com/documentation/expressions/xpath30maps.xml), but I am unable to get past query compilation. Maybe I am missing some parameter or I use a wrong namespace, but I just can't find the right answer. This is my query code: xquery version "3.0"; (: i have also tried http://www.w3.org/2005/xpath-functions/map, no difference :) import module namespace map = "http://ns.saxonica.com/map"; map:get(map { 1 := 'aaa'}, 1) invoked from command line: "c:\Program Files\Saxonica\SaxonEE9.4N\bin\Query.exe" -s:play.xml -q:play2.xq" -qversion:3.0 The commands ends with error: Cannot locate module for namespace "http://ns.saxonica.com/map" When I leave out the module namespace map declaration, the error is Prefix map has not been declared, so I assume the namespace declaration must be there... ________________________________________ Jakub Malý Ph. D. candidate XML Research Group Department of Software Engineering Faculty of Mathematics and Physics Charles University in Prague, Czech Republic www.jakubmaly.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: <mailto:xsl-list-unsubscribe@lists.mulberrytech.com> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324307.html > //figure/preceding-sibling::*[1][figure] The default axis is "child::", so this should be the same as //figure/preceding-sibling::*[1][child::figure] But you said you want the <figure> that has an immediate preceeding sibling. The path //figure/preceding-sibling::*[1][self::figure] picks up the preceding sibling itself, not the <figure> that has the preceding sibling. Perhaps you want something like //figure[preceding-sibling::*[1][self::figure]] > I wanted to isolate the figure element that has a figure as an > immediate preceding sibling. > > <section role="All_models"> > <title>All models</title> > <figure role="Harness_multi-plug"> > <title>ECU harness multi-plug</title> > <mediaobject> > <imageobject> > <imagedata fileref="78650"/> > </imageobject> > </mediaobject> > </figure> > <figure role="Circuit_diagram"> > <title>System circuit diagram</title> > <mediaobject> > <imageobject> > <imagedata fileref="31544"/> > </imageobject> > </mediaobject> > </figure> > </section> > > I settled on //figure/preceding-sibling::*[1][figure] but it gave back > nothing and would only work when I used the explicit form of the self > axis. > > I settled on //figure/preceding-sibling::*[1][self::figure] > > However if I want the title element immediately preceding figure I > don't need to use the explicit form. This works > > //figure/preceding-sibling::*[1][title] > > So what is going on in this particular case (because I don't > understand the difference), and in general when is explicit self > required. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324300.html ihe onwuka wrote: > I wanted to isolate the figure element that has a figure as an > immediate preceding sibling. > > <section role="All_models"> > <title>All models</title> > <figure role="Harness_multi-plug"> > <title>ECU harness multi-plug</title> > <mediaobject> > <imageobject> > <imagedata fileref="78650"/> > </imageobject> > </mediaobject> > </figure> > <figure role="Circuit_diagram"> > <title>System circuit diagram</title> > <mediaobject> > <imageobject> > <imagedata fileref="31544"/> > </imageobject> > </mediaobject> > </figure> > </section> > > I settled on //figure/preceding-sibling::*[1][figure] but it gave back > nothing and would only work when I used the explicit form of the self > axis. Well [figure] checks wether there is a child element named figure, not whether the element itself is a figure element. > I settled on //figure/preceding-sibling::*[1][self::figure] > > However if I want the title element immediately preceding figure I > don't need to use the explicit form. This works > > //figure/preceding-sibling::*[1][title] > > So what is going on in this particular case (because I don't > understand the difference), and in general when is explicit self > required. The same here, [title] checks whether there is a child element named "title", only in your XML that is the case. -- Martin Honnen --- MVP Data Platform Development 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324299.html I wanted to isolate the figure element that has a figure as an immediate preceding sibling. <section role="All_models"> <title>All models</title> <figure role="Harness_multi-plug"> <title>ECU harness multi-plug</title> <mediaobject> <imageobject> <imagedata fileref="78650"/> </imageobject> </mediaobject> </figure> <figure role="Circuit_diagram"> <title>System circuit diagram</title> <mediaobject> <imageobject> <imagedata fileref="31544"/> </imageobject> </mediaobject> </figure> </section> I settled on //figure/preceding-sibling::*[1][figure] but it gave back nothing and would only work when I used the explicit form of the self axis. I settled on //figure/preceding-sibling::*[1][self::figure] However if I want the title element immediately preceding figure I don't need to use the explicit form. This works //figure/preceding-sibling::*[1][title] So what is going on in this particular case (because I don't understand the difference), and in general when is explicit self required. --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324298.html Am 24.01.2012 23:19, schrieb Jesse Schaaf: > There has to be a simple answer to this one. > I have a block statement as such: > <fo:block>&#x2022; = Utilization Management (UM) </fo:block> > > However the bullet(or &#x2022;) needs to be in a larger font. I know I > can add font-size to the block statement but that would increase the > other text inside the block which I do not want to do. > > I know this is not correct but here is what I am trying to do: > <fo:block><FONT line-height="13pt" font-size="15pt"> &#x2022;</FONT> = > Utilization Management (UM)</fo:block> > > I tried using another block but it forces a line break. I know I can > use a table with two cells however I have to believe there is a simple > tag I can use for this? > > Try fo:inline (http://www.w3schools.com/xslfo/obj_inline.asp) Best regards, Christian --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324288.html There has to be a simple answer to this one. I have a block statement as such: <fo:block>&#x2022; = Utilization Management (UM) </fo:block> However the bullet(or &#x2022;) needs to be in a larger font. I know I can add font-size to the block statement but that would increase the other text inside the block which I do not want to do. I know this is not correct but here is what I am trying to do: <fo:block><FONT line-height="13pt" font-size="15pt"> &#x2022;</FONT> = Utilization Management (UM)</fo:block> I tried using another block but it forces a line break. I know I can use a table with two cells however I have to believe there is a simple tag I can use for this? -- Jesse Schaaf Schaafnet Consulting www.schaafnet.com 952-463-7625 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324287.html Hi Chris, If using XSLT 2.0 (and why not?), you should look up xsl:for-each-group, which as the name implies is designed to support grouping. If you are using XSLT 1.0 and don't have this option, there are several others, all of which share a single characteristic: they are less graceful than xsl:for-each-group. The method you are attempting might be one of them, except for one thing. XPath ($nodesetA != $nodesetB) returns true if any member of $nodesetA is unequal to any member of $nodesetB. You want not(mainGroupCodes = preceding-sibling::*/mainGroupCodes), which returns false as long as the value of mainGroupCodes is equal to the value of any of preceding-sibling::*/mainGroupCodes. There is a subtle but important difference there. Cheers, Wendell On 1/24/2012 10:17 AM, Chris Booth wrote: > Hi, > > I am after a litte bit guidance and help please. > > Using XSL:FO I need to be able to group parts of my data together. > >> From the XML below, I am looking for a way where I loop over Lines/Line and based on the value in LineGroup/GroupCode, if it's the first occurance then display the GroupDescription. > > I am trying all sorts of variations on the below but with no joy- > <xsl:if test="mainGroupCodes != preceding-sibling::*/mainGroupCodes"> > DISPLAY GROUP DESC > </xsl:if> > > REQUIRED OUTPUT: > Main Group One > LINE DATA > LINE DATA > > > Main Group Three > LINE DATA > LINE DATA > > Sub Group 1 > LINE DATA > LINE DATA > > SAMPLE XML: > <Lines Type="Quote"> > <Line Type="Quote"> > <DocumentLine>1.00</DocumentLine> > <LineGroup>14.00</LineGroup> > <LineDisplaySequence>1</LineDisplaySequence> > <mainGroupCodes>1</mainGroupCodes> > <LineGroup> > <GroupId>14.00</GroupId> > <GroupCode>1</GroupCode> > <GroupDescription>Main Group One</GroupDescription> > <FloorGroup>1</FloorGroup> > <CeilingGroup>2</CeilingGroup> > <SubGroupLineValueTotal>8000.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>8000.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>31.00</DocumentLine> > <LineGroup>16.00</LineGroup> > <LineDisplaySequence>10</LineDisplaySequence> > <mainGroupCodes>3</mainGroupCodes> > <LineGroup> > <GroupId>16.00</GroupId> > <GroupCode>3</GroupCode> > <GroupDescription>Main Group Three</GroupDescription> > <FloorGroup>3</FloorGroup> > <CeilingGroup>4</CeilingGroup> > <SubGroupLineValueTotal>518.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>3806.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>2.00</DocumentLine> > <LineGroup>16.00</LineGroup> > <LineDisplaySequence>11</LineDisplaySequence> > <mainGroupCodes>3</mainGroupCodes> > <LineGroup> > <GroupId>16.00</GroupId> > <GroupCode>3</GroupCode> > <GroupDescription>Main Group Three</GroupDescription> > <FloorGroup>3</FloorGroup> > <CeilingGroup>4</CeilingGroup> > <SubGroupLineValueTotal>518.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>3806.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>13.00</DocumentLine> > <LineGroup>19.00</LineGroup> > <LineDisplaySequence>12</LineDisplaySequence> > <mainGroupCodes>4</mainGroupCodes> > <LineGroup> > <GroupId>19.00</GroupId> > <GroupCode>4.1</GroupCode> > <GroupDescription>Sub group 1</GroupDescription> > <FloorGroup>4</FloorGroup> > <CeilingGroup>5</CeilingGroup> > <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>14.00</DocumentLine> > <LineGroup>19.00</LineGroup> > <LineDisplaySequence>13</LineDisplaySequence> > <mainGroupCodes>4</mainGroupCodes> > <LineGroup> > <GroupId>19.00</GroupId> > <GroupCode>4.1</GroupCode> > <GroupDescription>Sub group 1</GroupDescription> > <FloorGroup>4</FloorGroup> > <CeilingGroup>5</CeilingGroup> > <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>15.00</DocumentLine> > <LineGroup>19.00</LineGroup> > <LineDisplaySequence>14</LineDisplaySequence> > <mainGroupCodes>4</mainGroupCodes> > <LineGroup> > <GroupId>19.00</GroupId> > <GroupCode>4.1</GroupCode> > <GroupDescription>Sub group 1</GroupDescription> > <FloorGroup>4</FloorGroup> > <CeilingGroup>5</CeilingGroup> > <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>17.00</DocumentLine> > <LineGroup>19.00</LineGroup> > <LineDisplaySequence>15</LineDisplaySequence> > <mainGroupCodes>4</mainGroupCodes> > <LineGroup> > <GroupId>19.00</GroupId> > <GroupCode>4.1</GroupCode> > <GroupDescription>Sub group 1</GroupDescription> > <FloorGroup>4</FloorGroup> > <CeilingGroup>5</CeilingGroup> > <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>23.00</DocumentLine> > <LineGroup>19.00</LineGroup> > <LineDisplaySequence>16</LineDisplaySequence> > <OriginalOrderLine>0.00</OriginalOrderLine> > <mainGroupCodes>4</mainGroupCodes> > <LineGroup> > <GroupId>19.00</GroupId> > <GroupCode>4.1</GroupCode> > <GroupDescription>Sub group 1</GroupDescription> > <FloorGroup>4</FloorGroup> > <CeilingGroup>5</CeilingGroup> > <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>24.00</DocumentLine> > <LineGroup>20.00</LineGroup> > <LineDisplaySequence>17</LineDisplaySequence> > <mainGroupCodes>4</mainGroupCodes> > <LineGroup> > <GroupId>20.00</GroupId> > <GroupCode>4.2</GroupCode> > <GroupDescription>Subgroup 2</GroupDescription> > <FloorGroup>4</FloorGroup> > <CeilingGroup>5</CeilingGroup> > <SubGroupLineValueTotal>0.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>25.00</DocumentLine> > <LineGroup>20.00</LineGroup> > <LineDisplaySequence>18</LineDisplaySequence> > <mainGroupCodes>4</mainGroupCodes> > <LineGroup> > <GroupId>20.00</GroupId> > <GroupCode>4.2</GroupCode> > <GroupDescription>Subgroup 2</GroupDescription> > <FloorGroup>4</FloorGroup> > <CeilingGroup>5</CeilingGroup> > <SubGroupLineValueTotal>0.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>9.00</DocumentLine> > <LineGroup>21.00</LineGroup> > <LineDisplaySequence>19</LineDisplaySequence> > <mainGroupCodes>4</mainGroupCodes> > <LineGroup> > <GroupId>21.00</GroupId> > <GroupCode>4.3</GroupCode> > <GroupDescription>Sub group 3</GroupDescription> > <FloorGroup>4</FloorGroup> > <CeilingGroup>5</CeilingGroup> > <SubGroupLineValueTotal>500.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>20.00</DocumentLine> > <LineGroup>14.00</LineGroup> > <LineDisplaySequence>2</LineDisplaySequence> > <mainGroupCodes>1</mainGroupCodes> > <LineGroup> > <GroupId>14.00</GroupId> > <GroupCode>1</GroupCode> > <GroupDescription>Main Group One</GroupDescription> > <FloorGroup>1</FloorGroup> > <CeilingGroup>2</CeilingGroup> > <SubGroupLineValueTotal>8000.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>8000.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > <Line Type="Quote"> > <DocumentLine>8.00</DocumentLine> > <LineGroup>18.00</LineGroup> > <LineDisplaySequence>20</LineDisplaySequence> > <mainGroupCodes>4</mainGroupCodes> > <LineGroup> > <GroupId>18.00</GroupId> > <GroupCode>4</GroupCode> > <GroupDescription>Main Group 4</GroupDescription> > <FloorGroup>4</FloorGroup> > <CeilingGroup>5</CeilingGroup> > <SubGroupLineValueTotal>1574.00</SubGroupLineValueTotal> > <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> > </LineGroup> > </Line> > </Lines> -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324286.html Hi, I am after a litte bit guidance and help please. Using XSL:FO I need to be able to group parts of my data together. From the XML below, I am looking for a way where I loop over Lines/Line and based on the value in LineGroup/GroupCode, if it's the first occurance then display the GroupDescription. I am trying all sorts of variations on the below but with no joy- <xsl:if test="mainGroupCodes != preceding-sibling::*/mainGroupCodes"> DISPLAY GROUP DESC </xsl:if> REQUIRED OUTPUT: Main Group One LINE DATA LINE DATA Main Group Three LINE DATA LINE DATA Sub Group 1 LINE DATA LINE DATA SAMPLE XML: <Lines Type="Quote"> <Line Type="Quote"> <DocumentLine>1.00</DocumentLine> <LineGroup>14.00</LineGroup> <LineDisplaySequence>1</LineDisplaySequence> <mainGroupCodes>1</mainGroupCodes> <LineGroup> <GroupId>14.00</GroupId> <GroupCode>1</GroupCode> <GroupDescription>Main Group One</GroupDescription> <FloorGroup>1</FloorGroup> <CeilingGroup>2</CeilingGroup> <SubGroupLineValueTotal>8000.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>8000.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>31.00</DocumentLine> <LineGroup>16.00</LineGroup> <LineDisplaySequence>10</LineDisplaySequence> <mainGroupCodes>3</mainGroupCodes> <LineGroup> <GroupId>16.00</GroupId> <GroupCode>3</GroupCode> <GroupDescription>Main Group Three</GroupDescription> <FloorGroup>3</FloorGroup> <CeilingGroup>4</CeilingGroup> <SubGroupLineValueTotal>518.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>3806.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>2.00</DocumentLine> <LineGroup>16.00</LineGroup> <LineDisplaySequence>11</LineDisplaySequence> <mainGroupCodes>3</mainGroupCodes> <LineGroup> <GroupId>16.00</GroupId> <GroupCode>3</GroupCode> <GroupDescription>Main Group Three</GroupDescription> <FloorGroup>3</FloorGroup> <CeilingGroup>4</CeilingGroup> <SubGroupLineValueTotal>518.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>3806.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>13.00</DocumentLine> <LineGroup>19.00</LineGroup> <LineDisplaySequence>12</LineDisplaySequence> <mainGroupCodes>4</mainGroupCodes> <LineGroup> <GroupId>19.00</GroupId> <GroupCode>4.1</GroupCode> <GroupDescription>Sub group 1</GroupDescription> <FloorGroup>4</FloorGroup> <CeilingGroup>5</CeilingGroup> <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>14.00</DocumentLine> <LineGroup>19.00</LineGroup> <LineDisplaySequence>13</LineDisplaySequence> <mainGroupCodes>4</mainGroupCodes> <LineGroup> <GroupId>19.00</GroupId> <GroupCode>4.1</GroupCode> <GroupDescription>Sub group 1</GroupDescription> <FloorGroup>4</FloorGroup> <CeilingGroup>5</CeilingGroup> <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>15.00</DocumentLine> <LineGroup>19.00</LineGroup> <LineDisplaySequence>14</LineDisplaySequence> <mainGroupCodes>4</mainGroupCodes> <LineGroup> <GroupId>19.00</GroupId> <GroupCode>4.1</GroupCode> <GroupDescription>Sub group 1</GroupDescription> <FloorGroup>4</FloorGroup> <CeilingGroup>5</CeilingGroup> <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>17.00</DocumentLine> <LineGroup>19.00</LineGroup> <LineDisplaySequence>15</LineDisplaySequence> <mainGroupCodes>4</mainGroupCodes> <LineGroup> <GroupId>19.00</GroupId> <GroupCode>4.1</GroupCode> <GroupDescription>Sub group 1</GroupDescription> <FloorGroup>4</FloorGroup> <CeilingGroup>5</CeilingGroup> <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>23.00</DocumentLine> <LineGroup>19.00</LineGroup> <LineDisplaySequence>16</LineDisplaySequence> <OriginalOrderLine>0.00</OriginalOrderLine> <mainGroupCodes>4</mainGroupCodes> <LineGroup> <GroupId>19.00</GroupId> <GroupCode>4.1</GroupCode> <GroupDescription>Sub group 1</GroupDescription> <FloorGroup>4</FloorGroup> <CeilingGroup>5</CeilingGroup> <SubGroupLineValueTotal>4960.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>24.00</DocumentLine> <LineGroup>20.00</LineGroup> <LineDisplaySequence>17</LineDisplaySequence> <mainGroupCodes>4</mainGroupCodes> <LineGroup> <GroupId>20.00</GroupId> <GroupCode>4.2</GroupCode> <GroupDescription>Subgroup 2</GroupDescription> <FloorGroup>4</FloorGroup> <CeilingGroup>5</CeilingGroup> <SubGroupLineValueTotal>0.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>25.00</DocumentLine> <LineGroup>20.00</LineGroup> <LineDisplaySequence>18</LineDisplaySequence> <mainGroupCodes>4</mainGroupCodes> <LineGroup> <GroupId>20.00</GroupId> <GroupCode>4.2</GroupCode> <GroupDescription>Subgroup 2</GroupDescription> <FloorGroup>4</FloorGroup> <CeilingGroup>5</CeilingGroup> <SubGroupLineValueTotal>0.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>9.00</DocumentLine> <LineGroup>21.00</LineGroup> <LineDisplaySequence>19</LineDisplaySequence> <mainGroupCodes>4</mainGroupCodes> <LineGroup> <GroupId>21.00</GroupId> <GroupCode>4.3</GroupCode> <GroupDescription>Sub group 3</GroupDescription> <FloorGroup>4</FloorGroup> <CeilingGroup>5</CeilingGroup> <SubGroupLineValueTotal>500.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>20.00</DocumentLine> <LineGroup>14.00</LineGroup> <LineDisplaySequence>2</LineDisplaySequence> <mainGroupCodes>1</mainGroupCodes> <LineGroup> <GroupId>14.00</GroupId> <GroupCode>1</GroupCode> <GroupDescription>Main Group One</GroupDescription> <FloorGroup>1</FloorGroup> <CeilingGroup>2</CeilingGroup> <SubGroupLineValueTotal>8000.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>8000.00</AllGroupLineValueTotal> </LineGroup> </Line> <Line Type="Quote"> <DocumentLine>8.00</DocumentLine> <LineGroup>18.00</LineGroup> <LineDisplaySequence>20</LineDisplaySequence> <mainGroupCodes>4</mainGroupCodes> <LineGroup> <GroupId>18.00</GroupId> <GroupCode>4</GroupCode> <GroupDescription>Main Group 4</GroupDescription> <FloorGroup>4</FloorGroup> <CeilingGroup>5</CeilingGroup> <SubGroupLineValueTotal>1574.00</SubGroupLineValueTotal> <AllGroupLineValueTotal>7034.00</AllGroupLineValueTotal> </LineGroup> </Line> </Lines> ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324285.html You can use bookmark-tree That works with FOP 1.0 (not sure it was supported earlier) I definitely use that in FOP 1 <fo:bookmark-tree> <fo:bookmark internal-destination="front-page-id"> <fo:bookmark-title> <xsl:text>Front Page Title</xsl:text> </fo:bookmark-title> </fo:bookmark> ...... A bookmark has a title, an internal-destination (make sure the block you point to has a matching id) and a bookmark can have other bookmarks as well (to make a hierarchical tree) There is a way to set the bookmark tree to open with the document, but I need to check what that is exactly if that is important cheers Geert At 02:13 24/01/2012, you wrote: >I am using FOP Apache to generate and publish a pdf from XML and >need to create bookmarks so when you open the pdf in adobe the left >menu will show links to sections in the document. > >I am told that the only way to do this is by using the extension >fox:OUTLINE and fox:label elements. Are there any other options >without using these extensions? > >This really is an effort to become 508 compliant. Basically this is >a Government Standard that says any PDF that is published should be >designed for the hearing impaired and the 508 compliance is a set of >standards to adhere to. One of the requirements is that you have >bookmarks on pdfs over 9 pages. > > >-- >Jesse Schaaf >Schaafnet Consulting >www.schaafnet.com >952-463-7625 > >--~------------------------------------------------------------------ >XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324282.html I am using FOP Apache to generate and publish a pdf from XML and need to create bookmarks so when you open the pdf in adobe the left menu will show links to sections in the document. I am told that the only way to do this is by using the extension fox:OUTLINE and fox:label elements. Are there any other options without using these extensions? This really is an effort to become 508 compliant. Basically this is a Government Standard that says any PDF that is published should be designed for the hearing impaired and the 508 compliance is a set of standards to adhere to. One of the requirements is that you have bookmarks on pdfs over 9 pages. -- Jesse Schaaf Schaafnet Consulting www.schaafnet.com 952-463-7625 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324281.html Hi, On 1/21/2012 2:13 PM, was written: > > <xsl:function as="xs:string" name="d:getMonthName"> > <xsl:param name="monthName"/> > <xsl:variable name="monthNames" > select="('january','february','march','april','may','june','july','august','september','october','november','december')"/> > <xsl:sequence > select="format-number(if (index-of($monthNames,$monthName) castable as xs:integer) > then index-of($monthNames,$monthName) > else 0,'00')" > /> > </xsl:function> A bit of refactoring: select="format-number((index-of($monthNames,$monthName),0)[1],'00')" It works since index-of() returns an empty sequence if the item argument is not included in the sequence argument. 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324279.html In your future postings to XSL-List please provide an informative title or 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. A good way to write a subject line is to write the message first and then form the subject line from the phrase(s) in the text of the message that most clearly identify your topic. In this case, "How to get unique IDs" would have been far better than "how to achieve this ?". -- Tommie Usdin XSL-List Owner On Jan 23, 2012, at 2:26 AM, Roelof Wobben wrote: > > Hello, > > > > For a menu I have to take care that every <menu class> get a unique id. > > I thought this would work : > > > > <xsl:template match="year"> > <ul class="menu" id= "concat ('menu', @value)" > > <li> > <a href="#"> <xsl:value-of select="@value"/> </a> > <ul class="acitem"> > <xsl:apply-templates select="month" /> > </ul> > </li> > </ul> > </xsl:template> > > > But it don't work. > > Do I have to use here <xsl:value-of> or is there a better way ? > > > > Roelof > > > > --~------------------------------------------------------------------ > XSL-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> > --~-- > ====================================================================== 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 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324278.html My apologies, disregard my previous email; it was a mistake. Vojtech > -----Original Message----- > From: vojtech.toman@emc.com [mailto:vojtech.toman@emc.com] > Sent: Monday, January 23, 2012 12:02 PM > To: xsl-list@lists.mulberrytech.com > Subject: RE: [xsl] how to achieve this ? > > :) Ty jsi ale plna dobrych napadu :) > > > -----Original Message----- > > From: Andrew Welch [mailto:andrew.j.welch@gmail.com] > > Sent: Monday, January 23, 2012 11:56 AM > > To: xsl-list@lists.mulberrytech.com > > Subject: Re: [xsl] how to achieve this ? > > > > On 23 January 2012 10:44, Michel Hendriksen <michel.hendriksen@42.nl> > > wrote: > > > Sounds like HTML/javascript problem, is another list. > > > > Yeah it's not for this list... however I've been doing some html5 and > > css3 recently (with jquery) and it's pretty amazing stuff. It's a > > huge leap forward. > > > > To bring it back to XSLT, I'm guessing there will be some new > > serialisation options in 3.0 to accommodate it. > > > > > > > > -- > > Andrew Welch > > http://andrewjwelch.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> > > --~-- > > > > > --~------------------------------------------------------------------ > XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324277.html :) Ty jsi ale plna dobrych napadu :) > -----Original Message----- > From: Andrew Welch [mailto:andrew.j.welch@gmail.com] > Sent: Monday, January 23, 2012 11:56 AM > To: xsl-list@lists.mulberrytech.com > Subject: Re: [xsl] how to achieve this ? > > On 23 January 2012 10:44, Michel Hendriksen <michel.hendriksen@42.nl> > wrote: > > Sounds like HTML/javascript problem, is another list. > > Yeah it's not for this list... however I've been doing some html5 and > css3 recently (with jquery) and it's pretty amazing stuff. It's a > huge leap forward. > > To bring it back to XSLT, I'm guessing there will be some new > serialisation options in 3.0 to accommodate it. > > > > -- > Andrew Welch > http://andrewjwelch.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> > --~-- > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324276.html On 23 January 2012 10:44, Michel Hendriksen <michel.hendriksen@42.nl> wrote: > Sounds like HTML/javascript problem, is another list. Yeah it's not for this list... however I've been doing some html5 and css3 recently (with jquery) and it's pretty amazing stuff. It's a huge leap forward. To bring it back to XSLT, I'm guessing there will be some new serialisation options in 3.0 to accommodate it. -- Andrew Welch http://andrewjwelch.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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324275.html Sounds like HTML/javascript problem, is another list. On 1/23/12, Roelof Wobben <rwobben@hotmail.com> wrote: > > Thanks, > > > > It solved the id problem but the menu still don't work right. > > It still don't work as as accordian menu. See http://test.tamarawobben.nl > > > > Roelof > > > > > > > > > > ---------------------------------------- > From: bbosgoed@bkwi.nl > Date: > Mon, 23 Jan 2012 08:35:36 +0100 > To: xsl-list@lists.mulberrytech.com > > Subject: Re: [xsl] how to achieve this ? > > > Op 23 jan 2012, om 08:26 > heeft Roelof Wobben het volgende geschreven: > > Not knowing how the input > looks like, i would say that: > <ul class="menu" id={concat('menu', > @value)}> > > should do it for you, its a short notation for xsl:value-of > select > > > > For a menu I have to take care that every <menu class> get a > unique id. > > > > I thought this would work : > > > > <xsl:template > match="year"> > > <ul class="menu" id= "concat ('menu', @value)" > > > <li> >> > <a href="#"> <xsl:value-of select="@value"/> </a> > > <ul > class="acitem"> > > <xsl:apply-templates select="month" /> > > </ul> > > > </li> > > </ul> > > </xsl:template> > > > > But it don't work. > > > > Do I > have to use here <xsl:value-of> or is there a better 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> > --~-- > > --~------------------------------------------------------------------ > XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324274.html Thanks, It solved the id problem but the menu still don't work right. It still don't work as as accordian menu. See http://test.tamarawobben.nl Roelof ---------------------------------------- > From: bbosgoed@bkwi.nl > Date: Mon, 23 Jan 2012 08:35:36 +0100 > To: xsl-list@lists.mulberrytech.com > Subject: Re: [xsl] how to achieve this ? > > > Op 23 jan 2012, om 08:26 heeft Roelof Wobben het volgende geschreven: > > Not knowing how the input looks like, i would say that: > <ul class="menu" id={concat('menu', @value)}> > > should do it for you, its a short notation for xsl:value-of select > > > > For a menu I have to take care that every <menu class> get a unique id. > > > > I thought this would work : > > > > <xsl:template match="year"> > > <ul class="menu" id= "concat ('menu', @value)" > > > <li> > > <a href="#"> <xsl:value-of select="@value"/> </a> > > <ul class="acitem"> > > <xsl:apply-templates select="month" /> > > </ul> > > </li> > > </ul> > > </xsl:template> > > > > But it don't work. > > > > Do I have to use here <xsl:value-of> or is there a better 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> > --~-- > --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324273.html Op 23 jan 2012, om 08:26 heeft Roelof Wobben het volgende geschreven: Not knowing how the input looks like, i would say that: <ul class="menu" id={concat('menu', @value)}> should do it for you, its a short notation for xsl:value-of select > For a menu I have to take care that every <menu class> get a unique id. > > I thought this would work : > > <xsl:template match="year"> > <ul class="menu" id= "concat ('menu', @value)" > > <li> > <a href="#"> <xsl:value-of select="@value"/> </a> > <ul class="acitem"> > <xsl:apply-templates select="month" /> > </ul> > </li> > </ul> > </xsl:template> > > But it don't work. > > Do I have to use here <xsl:value-of> or is there a better 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324272.html Hello, For a menu I have to take care that every <menu class> get a unique id. I thought this would work : <xsl:template match="year"> <ul class="menu" id= "concat ('menu', @value)" > <li> <a href="#"> <xsl:value-of select="@value"/> </a> <ul class="acitem"> <xsl:apply-templates select="month" /> </ul> </li> </ul> </xsl:template> But it don't work. Do I have to use here <xsl:value-of> or is there a better way ? Roelof --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324271.html On 22/01/2012 14:18, Michel Hendriksen wrote: > What about translets, or are these not really compiled? > > That's what XSLTC calls its generated code, but I don't tend to use the term because I assume no-one is likely to know what it means. Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324269.html What about translets, or are these not really compiled? On Sat, Jan 21, 2012 at 9:00 PM, Michael Kay <mike@saxonica.com> wrote: > On 20/01/2012 18:36, Rand McRanderson wrote: >> >> Hi Everyone, >> >> I was curious about if there was any implementation of XSLT which >> translated it first into a compiled language. Any one know of any >> commercial or open source projects along these lines? How about any >> implementations that compile a stylesheet into Java bytecode? >> >> > Way back in 1999, a very early version of Saxon included Java source code > generation for a subset of XSLT - with the translation from XSLT to Java > being written in XSLT, no less. It wasn't very useful (it generated really > bad code) and was quickly abandoned. > > More recently, in Saxon 9.4 released last month, Saxon-EE now does > on-the-fly bytecode generation for selected parts of your stylesheet, mixing > compiled code and interpreted code freely so either can call the other. > > This isn't exactly new, though: the XSLTC product, which became part of > Xalan, was probably the first to make a major feature of code generation. > > For a discussion of what to expect from code generation, at least in Saxon, > see > > http://www.balisage.net/Proceedings/vol7/html/Delpratt01/BalisageVol7-Delpratt01.html > > Michael Kay > Saxonica > > > --~------------------------------------------------------------------ > XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324268.html On Sat, Jan 21, 2012 at 07:19:26PM +0000, James Cummings scripsit: > Ah, index-of() that was the thing I was vaguely remembering! Many thanks! You're welcome. But please consider bookmarking http://www.w3schools.com/xsl/xsl_functions.asp and http://www.w3schools.com/xpath/xpath_functions.asp (or their various friends and relations). It might not save you any sanity -- enough functions will start pushing you in the direction of having to begin to understand the schema type model -- but it will probably be a net gain for your productivity. :) -- Graydon --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324264.html There are many solutions, but setting the top padding on the bullet cell's block to a negative value is the one I tend to use ... like this (see padding-top is -3pt (difference between 12pt text and 15pt bullet): <fo:table> <fo:table-column column-width="16pt"/> <fo:table-column /> <fo:table-body> <fo:table-row> <fo:table-cell border="1pt solid black"> <fo:block font-size="15pt">&#x2022;</fo:block> </fo:table-cell> <fo:table-cell border="1pt solid black"> <fo:block>This is some additional text that is in a different point size.</fo:block> </fo:table-cell> </fo:table-row> <fo:table-row> <fo:table-cell border="1pt solid black"> <fo:block font-size="15pt" padding-top="-3pt">&#x2022;</fo:block> </fo:table-cell> <fo:table-cell border="1pt solid black"> <fo:block>This is some additional text that is in a different point size setting the padding to shift the bullet.</fo:block> </fo:table-cell> </fo:table-row> <fo:table-row> <fo:table-cell border="1pt solid black"> <fo:block font-size="15pt" padding-top="-3pt">&#x2022;</fo:block> </fo:table-cell> <fo:table-cell border="1pt solid black"> <fo:block>This is some additional text that is in a different point size setting the padding to shift the bullet.</fo:block> </fo:table-cell> </fo:table-row> </fo:table-body> </fo:table> Kevin Brown RenderX ********************************************** Date: Fri, 20 Jan 2012 21:14:54 -0600 To: xsl-list@lists.mulberrytech.com From: Jesse Schaaf <schajx@schaafnet.com> Subject: cell height xsl Message-ID: <4F1A2DAE.9020603@schaafnet.com> > I realize 15pt is likely higher then the row height but its possible for other cells in this row to wrap and I want those cells to dictate the height. Im sure there is an easy solution to this but I am fairly new to xslt. Here is the code that I have for the cell involved. <snip/> --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324263.html On 20/01/2012 18:36, Rand McRanderson wrote: > Hi Everyone, > > I was curious about if there was any implementation of XSLT which > translated it first into a compiled language. Any one know of any > commercial or open source projects along these lines? How about any > implementations that compile a stylesheet into Java bytecode? > > Way back in 1999, a very early version of Saxon included Java source code generation for a subset of XSLT - with the translation from XSLT to Java being written in XSLT, no less. It wasn't very useful (it generated really bad code) and was quickly abandoned. More recently, in Saxon 9.4 released last month, Saxon-EE now does on-the-fly bytecode generation for selected parts of your stylesheet, mixing compiled code and interpreted code freely so either can call the other. This isn't exactly new, though: the XSLTC product, which became part of Xalan, was probably the first to make a major feature of code generation. For a discussion of what to expect from code generation, at least in Saxon, see http://www.balisage.net/Proceedings/vol7/html/Delpratt01/BalisageVol7-Delpratt01.html Michael Kay Saxonica --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324262.html On Sat, Jan 21, 2012 at 19:13, Graydon <graydon@marost.ca> wrote: > On Sat, Jan 21, 2012 at 06:43:57PM +0000, James Cummings scripsit: > [snip] > <xsl:function as="xs:string" name="d:getMonthName"> >   <xsl:param name="monthName"/> >   <xsl:variable name="monthNames" >       select="('january','february','march','april','may','june','july','august','september','october','november','december')"/> >   <xsl:sequence >       select="format-number(if (index-of($monthNames,$monthName) castable as xs:integer) >                           then index-of($monthNames,$monthName) >                           else 0,'00')" >   /> > </xsl:function> Ah, index-of() that was the thing I was vaguely remembering! Many thanks! > This is insanely fragile unless you have strict checking to enforce case, > spelling, and language of month names. Sure, as is the original. I'm regularising things from a very messy text (but fairly consistent in the dates it has on page headings), so when things don't match precise patterns I'm marking them and moving on. It is a case of getting some automated markup in there to give others a leg up in manually correcting the remaining ones. > If you're in a situation where you're going to get January, jan., jan, Janvier, > etc. you can take your original version and add tests, which has the advantage > of simplicity and ease of maintenance, or you can stuff all those tests into a > returnMonthName function, which has the advantage of abstraction and > compactness of expression.  But either way this sort of thing with > unconstrained string data month names is a pain. Yeah, see what you mean. But thanks for reminding me of index-of()! -James --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324261.html On Sat, Jan 21, 2012 at 06:43:57PM +0000, James Cummings scripsit: [snip] > <xsl:function name="jc:getMonth" as="xs:string"><xsl:param name="month"/> > <xsl:choose> > <xsl:when test="$month='january'">01</xsl:when> > <xsl:when test="$month='february'">02</xsl:when> > <xsl:when test="$month='march'">03</xsl:when> > <xsl:when test="$month='april'">04</xsl:when> > <xsl:when test="$month='may'">05</xsl:when> > <xsl:when test="$month='june'">06</xsl:when> > <xsl:when test="$month='july'">07</xsl:when> > <xsl:when test="$month='august'">08</xsl:when> > <xsl:when test="$month='september'">09</xsl:when> > <xsl:when test="$month='october'">10</xsl:when> > <xsl:when test="$month='november'">11</xsl:when> > <xsl:when test="$month='november'">12</xsl:when> > <xsl:otherwise>00</xsl:otherwise> > </xsl:choose></xsl:function> > > > But in the back of my head, since the result is just a leading-zero > sequence number in a potential list of values.... I can't help > thinking there is a better way to do this. <xsl:function as="xs:string" name="d:getMonthName"> <xsl:param name="monthName"/> <xsl:variable name="monthNames" select="('january','february','march','april','may','june','july','august','september','october','november','december')"/> <xsl:sequence select="format-number(if (index-of($monthNames,$monthName) castable as xs:integer) then index-of($monthNames,$monthName) else 0,'00')" /> </xsl:function> This is insanely fragile unless you have strict checking to enforce case, spelling, and language of month names. If you're in a situation where you're going to get January, jan., jan, Janvier, etc. you can take your original version and add tests, which has the advantage of simplicity and ease of maintenance, or you can stuff all those tests into a returnMonthName function, which has the advantage of abstraction and compactness of expression. But either way this sort of thing with unconstrained string data month names is a pain. -- Graydon --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324260.html Hiya, I have an xslt2 function which gets a lower-case month name as a string and gives back its numerical equivalent. This is really trivially done as: <xsl:function name="jc:getMonth" as="xs:string"><xsl:param name="month"/> <xsl:choose> <xsl:when test="$month='january'">01</xsl:when> <xsl:when test="$month='february'">02</xsl:when> <xsl:when test="$month='march'">03</xsl:when> <xsl:when test="$month='april'">04</xsl:when> <xsl:when test="$month='may'">05</xsl:when> <xsl:when test="$month='june'">06</xsl:when> <xsl:when test="$month='july'">07</xsl:when> <xsl:when test="$month='august'">08</xsl:when> <xsl:when test="$month='september'">09</xsl:when> <xsl:when test="$month='october'">10</xsl:when> <xsl:when test="$month='november'">11</xsl:when> <xsl:when test="$month='november'">12</xsl:when> <xsl:otherwise>00</xsl:otherwise> </xsl:choose></xsl:function> But in the back of my head, since the result is just a leading-zero sequence number in a potential list of values.... I can't help thinking there is a better way to do this. If it was the month number I had and I wanted the month name, that'd be easy as just grabbing that item from the sequence. Suggestions? -James --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324259.html Thank you Christian, your advice worked perfectly!! Jesse Schaaf Schaafnet Consulting www.schaafnet.com 952-463-7625 On 1/21/2012 4:04 AM, Christian Kirchhoff wrote: > Am 21.01.2012 04:14, schrieb Jesse Schaaf: >> I realize 15pt is likely higher then the row height but its possible >> for other cells in this row to wrap and I want those cells to dictate >> the height. >> > I can only talk from my experience in CSS. The height of the cell is > calculated according to the height of it's contents. The content - a > fo:block - again has a height that is calculated based on what's in that > block. The text in the block has a line-height, and that line-height is > calculated depending on the font-size(s) in that line. > > One character with a larger font (the bullet) triggers an increase of > the line-height, which changes the height of the block and by thus of > the cell. > > So I would try to define a fixed line-height for the fo:block, hoping > that now the bigger bullet won't have the undesired influence on the > line-height. > > I hope it helps. > > Best regards > > Christian > > Editura GmbH & Co. KG > Tempelhofer Damm 2 · 12101 Berlin > Telefon: +49 (30) 7 89 59 49-68 > Fax: +49 (30) 7 89 59 49-90 > www.editura.de > AG Berlin-Charlottenburg · HRA 43189 B · USt.Id. DE217180548 > Geschäftsführer: Stefan Krause · Ralf Szymanski > > --~------------------------------------------------------------------ > XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324258.html Am 21.01.2012 04:14, schrieb Jesse Schaaf: > I realize 15pt is likely higher then the row height but its possible > for other cells in this row to wrap and I want those cells to dictate > the height. > I can only talk from my experience in CSS. The height of the cell is calculated according to the height of it's contents. The content - a fo:block - again has a height that is calculated based on what's in that block. The text in the block has a line-height, and that line-height is calculated depending on the font-size(s) in that line. One character with a larger font (the bullet) triggers an increase of the line-height, which changes the height of the block and by thus of the cell. So I would try to define a fixed line-height for the fo:block, hoping that now the bigger bullet won't have the undesired influence on the line-height. I hope it helps. Best regards Christian Editura GmbH & Co. KG Tempelhofer Damm 2 · 12101 Berlin Telefon: +49 (30) 7 89 59 49-68 Fax: +49 (30) 7 89 59 49-90 www.editura.de AG Berlin-Charlottenburg · HRA 43189 B · USt.Id. DE217180548 Geschäftsführer: Stefan Krause · Ralf Szymanski --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324256.html So I have a table that contains a cell of which I need to display the bullet(&#x2022;). The problem I am having is that I need to make the bullet larger so I used a font-size = 15pt. This solved the issue and the bullet displays at the right size however one side effect is that my row that this bullet exists in expands in height. I realize 15pt is likely higher then the row height but its possible for other cells in this row to wrap and I want those cells to dictate the height. Im sure there is an easy solution to this but I am fairly new to xslt. Here is the code that I have for the cell involved. <fo:table-cell padding = ".5mm" border-width=".2mm" border="solid" border-right-width="0mm" border-bottom-width=".2mm" border-top-width=".2mm" text-align="center"> <xsl:for-each select="MEDDST"> <fo:block font-size="15pt"> <xsl:value-of select="'&#x2022;'" /> </fo:block> </fo:table-cell > -- Jesse Schaaf Schaafnet Consulting www.schaafnet.com 952-463-7625 --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324253.html On Fri, 2012-01-20 at 13:36 -0500, Rand McRanderson wrote: > Hi Everyone, > > I was curious about if there was any implementation of XSLT which > translated it first into a compiled language. Any one know of any > commercial or open source projects along these lines? How about any > implementations that compile a stylesheet into Java bytecode? Saxon does some bytecode translation as I understand it. Are you interested for the sake of performance or for obfuscation? Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324252.html Hi Mark, Assuming the element names are as given, and that hence each element has a unique name, probably the most straightforward approach would be to key the elements by retrieval using their names. This is largely because your requirements identify two elements as "the same" if they have the same name, and can ignore their positions in the document (at least until it comes to writing your reports). For purposes of exposition, here's an XSLT 2.0 solution: <xsl:key name="element-by-name" match="*" use="name()"/> <xsl:variable name="B" select="document('wheredoyoufind/B.xml')"/> Then you traverse A to report where elements are missing: <xsl:template match="*"> <xsl:if test="empty(key('element-by-name',name(),$B)"> ... the element is missing from B ... </xsl:if> <xsl:apply-templates/> </xsl:template> Next to report if values are different. Since you only want to do this on leaf nodes, use a separate template to match only those: <xsl:template match="*[empty(*)]"> <xsl:if test=". != key('element-by-name',name(),$B)"> ... A has a different value from B ... </xsl:if> <xsl:next-match/> </xsl:template> The next-match instruction here will (would) then apply the first template also to the elements that match the second one, so its test is also performed. To rewrite this in XSLT 1.0, you have to do two things: * Since key() can't take a third argument to define the scope of retrieval, you have to work extra to use the key on document B. So: <xsl:template match="*"> <xsl:variable name="n" select="name()"/> <xsl:for-each select="$B"> <xsl:if test="not(key('element-by-name',$n)"> ... the element is missing from B ... </xsl:if> </xsl:for-each> <xsl:apply-templates/> </xsl:template> Do similarly for the other template. * Since xsl:next-match is not available in XSLT 1.0, work around this by giving the template matching * a name, which you can call (by name) from the other template. I hope this helps. Cheers, Wendell On 1/20/2012 1:57 PM, Mark Anderson wrote: > Hi Guys > > I have an XML comparison XSL that works well for identical XML's; however, I need to create a version that will compare two slightly dissimilar XML's (whose structure I do not know--other than root element's name). > > One will always be a superset of the other (if different). > > For example > > A contains > > <elements> > <element1> > <element1a>1a</element1a> > <element1b>1b</element1b> > <element1c>1c</element1c> > </element1> > <element2> > <element2a>2a</element2a> > <element2b>2b</element2b> > <element2c>2c</element2c> > </element2> > <element3> > <element3a>3a</element3a> > <element3b>3b</element3b> > <element3c>3c</element3c> > </element3> > </elements> > > > B Contains > > <elements> > <element1> > <element1a>1a</element1a> > <element1b>1b</element1b> > <element1c>1c</element1c> > </element1> > <element3> > <element3a>4a</element3a> > <element3c>4c</element3c> > </element3> > </elements> > > I want to iterate through every element and attribute in A, find the corresponding element in B (if it exists) and compare their values. > > For example, the output needs to indicate the following: > > element2 is missing > element2/element2a is missing > element2/element2b is missing > element2/element2c is missing > element3/element3b is missing > element3a's value is different > element3b's value is different > > Any help greatly appreciated -- ====================================================================== 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324242.html Hi Guys I have an XML comparison XSL that works well for identical XML's; however, I need to create a version that will compare two slightly dissimilar XML's (whose structure I do not know--other than root element's name). One will always be a superset of the other (if different). For example A contains <elements> <element1> <element1a>1a</element1a> <element1b>1b</element1b> <element1c>1c</element1c> </element1> <element2> <element2a>2a</element2a> <element2b>2b</element2b> <element2c>2c</element2c> </element2> <element3> <element3a>3a</element3a> <element3b>3b</element3b> <element3c>3c</element3c> </element3> </elements> B Contains <elements> <element1> <element1a>1a</element1a> <element1b>1b</element1b> <element1c>1c</element1c> </element1> <element3> <element3a>4a</element3a> <element3c>4c</element3c> </element3> </elements> I want to iterate through every element and attribute in A, find the corresponding element in B (if it exists) and compare their values. For example, the output needs to indicate the following: element2 is missing element2/element2a is missing element2/element2b is missing element2/element2c is missing element3/element3b is missing element3a's value is different element3b's value is different Any help greatly appreciated Regards 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324236.html Hi Everyone, I was curious about if there was any implementation of XSLT which translated it first into a compiled language. Any one know of any commercial or open source projects along these lines? How about any implementations that compile a stylesheet into Java bytecode? Sincerely, John Thomas --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324235.html Time of the year.. Just getting over the Christmas Fun... Anyway, Its good to see people missing the XSL list :) On 20 January 2012 01:07, Norias Anoria <noriasanoria@gmail.com> wrote: > Hey XSL-List! Everyting OK? Awfully quiet. > > NORIAS > > --~------------------------------------------------------------------ > XSL-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 NodeLogic Limited Oxford www.node-logic.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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324223.html Hey XSL-List! Everyting OK? Awfully quiet. NORIAS --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324219.html It's a new year and time to plan for Balisage 2012! Balisage is where people interested in descriptive markup meet each year in August for informed technical discussion, occasionally impassioned debate, good coffee, and the incomparable ambience of one of North America's greatest cities, Montreal. We welcome anyone interested in discussing the use of descriptive markup to build strong, lasting information systems. Practitioner or theorist, tool-builder or tool-user, student or lecturer -- you are invited to submit a paper proposal for Balisage 2012. As always, papers at Balisage can address any aspect of the use of markup and markup languages to represent information and build information systems. Possible topics include but are not limited to: * XML and related technologies * Non-XML markup languages * Implementation experience with XML parsing, XSLT processors, XQuery processors, XML databases, Topic Map engines, XProc integrations, or any markup-related technology * Semantics, overlap, and other complex fundamental issues for markup languages * Case studies of markup design and deployment * Quality of information in markup systems * JSON and XML * Efficiency of Markup Software * Markup systems in and for the mobile web * The future of XML and of descriptive markup in general * Interesting applications of markup In addition, please consider becoming a Peer Reviewer. Reviewers play a critical role towards the success of Balisage. They review blind submissions -- on topics that interest them -- for technical merit, interest, and applicability. Your comments and recommendations can assist the Conference Committee in creating the program for Balisage 2012! How: * Submit full papers in XML to <info@balisage.net> * See the Instructions for Authors (http://www.balisage.net/authorinstructions.html) and Tag Set and Submission Guidelines (http://www.balisage.net/tagset.html) for details. * Apply to the Peer Review panel (http://www.balisage.net/peer/ReviewAppForm.html) Schedule: 16 March 2012 - Peer review applications due 20 April 2012 - Paper submissions due 20 April 2012 - Applications due for student support awards due 28 May 2012 - Speakers notified 13 July 2012 - Final papers due 6 August 2012 - Pre-conference Symposium 7-10 August 2012 - Balisage: The Markup Conference Help us make Balisage your favorite XML Conference. See you in Montreal! -- The Balisage 2012 Conference Committee ====================================================================== Balisage: The Markup Conference 2012 mailto:info@balisage.net August 7-10, 2012 http://www.balisage.net Preconference Symposium on August 6, 2012 ====================================================================== --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324206.html Hi David. Thanks for taking the time to fix it, David. Best regards, Fabien -----Message d'origine----- De : David Carlisle [mailto:davidc@nag.co.uk] Envoyé : lundi 16 janvier 2012 11:58 À : xsl-list@lists.mulberrytech.com Cc : Fabien Tillier Objet : Re: [xsl] merging sequences On 16/01/2012 08:47, Fabien Tillier wrote: > When David's output is sorry the last clause in my merge function had what the polite might call a premature optimisation, or the honest would call a bug... it should not try to output the first element of both lists in the last case, fixing that produces the output you expected: $ saxon9 -it m merge.xsl N112 N100 N107 P2010 N109 P2014 P2015 N108 N203 N306 N206 N307 N311 > Regarding my specific needs, Ken's solution fits better since the order is exactly as expected > N112,N100,N107,P2010,N109,P2014,P2015,N108,N203,N306,N206,N307,N311 David <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:f="data:,f" > <xsl:output method="text"/> <xsl:variable name="a" select=" 'N112','N100','N107','P2010','N109','P2014','P2015','N108','N203', 'N206','N311' "/> <xsl:variable name="b" select=" 'N112','N100', 'P2014','P2015','N108','N203','N306','N206','N307','N311' "/> <xsl:template name="m"> <xsl:sequence select="f:merge($a,$b)"/> </xsl:template> <xsl:function name="f:merge"> <xsl:param name="a"/> <xsl:param name="b"/> <xsl:choose> <xsl:when test="empty($a)"> <xsl:sequence select="$b"/> </xsl:when> <xsl:when test="empty($b)"> <xsl:sequence select="$a"/> </xsl:when> <xsl:when test="$a[1]=$b[1]"> <xsl:sequence select="$a[1],f:merge($a[position()!=1],$b[position()!=1])"/> </xsl:when> <xsl:when test="$a[1]=$b"> <xsl:sequence select="f:merge($a[position()!=1],$b)"/> </xsl:when> <xsl:when test="$b[1]=$a"> <xsl:sequence select="f:merge($a,$b[position()!=1])"/> </xsl:when> <xsl:otherwise> <xsl:sequence select="$a[1],f:merge($a[position()!=1],$b)"/> </xsl:otherwise> </xsl:choose> </xsl:function> </xsl:stylesheet> -- google plus: https:/profiles.google.com/d.p.carlisle ________________________________________________________________________ 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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324204.html On Mon, Jan 16, 2012 at 7:37 AM, David Carlisle <davidc@nag.co.uk> wrote: > An XSLT 1 processor is allowed to use any prefix it wants in the output, > You may give the system a stronger hint by using unprefixed literal result Thanks, David! The above were two key omissions in my learning so far. My frustration level is now down below the level of the ceiling, and I'm smiling again. Best wishes, Charles --~------------------------------------------------------------------ XSL-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> --~--]]> http://www.altova.com/list/xsl-list/201201/msg1000324203.html An XSLT 1 processor is allowed to use any prefix it wants in the output, prefixes used in the source or in the stylesheet are only mild hints. So using ns_1 would be conformant but not what people usually want. (In theory if you only process the file with namespace aware tools and never look at it, the prefix shouldn't