Ah. I think I understand why now. I think it's to do with the namespace of items in the variable. Using node() is probably an acceptable fix though, so I won't mess with it.
On 14 December 2014 at 09:12, Miika Turkia <miika.tur...@gmail.com> wrote: > I go the weights to show for me by using node() along with the node-set. I > am a bit puzzled by this as I haven't seen similar syntax anywhere on the > web, but if that is the way to do it and it works for others as well... Can > you also test the patch that I just sent? > > For the export, it is good to follow the specifications as closely as > possible (and here I refer to both written specs and the xml schema). > However, for the import we need to be quite lax as I think every single > application produces different UDDF output - at least that is my take from > the sample files I have received. > > miika > > On Sun, Dec 14, 2014 at 1:37 AM, Long, Martin <mar...@longhome.co.uk> wrote: >> >> I'll look into this. The weight at the end was removed intentionally. >> I admit I'm not entirely sure what happened here. I think it was when >> I added the correct namespace this stopped working, and removing >> weight made it work for me. I'll investigate this further tonight. >> >> Btw, weights are now in the informationafterdive. This is an area of >> contradiction between the spec and the schema. I think 'after' makes >> slightly more sense, as you may add/remove weights at the start of the >> dive. Anyway, I need to clarify that. >> >> On 13 December 2014 at 19:59, Miika Turkia <miika.tur...@gmail.com> wrote: >> > On Sat, Dec 13, 2014 at 2:34 AM, Martin Long <mar...@longhome.co.uk> >> > wrote: >> >> >> >> - <leadquantity> >> >> - <xsl:value-of >> >> select="sum(xt:node-set($trimmedweightlist)/weight)"/> >> >> - </leadquantity> >> > >> > ... >> >> >> >> + <leadquantity> >> >> + <xsl:value-of >> >> select="sum(xt:node-set($trimmedweightlist))"/> >> >> + </leadquantity> >> > >> > >> > I am testing the UDDF export and don't see any weights exported. Was the >> > "/weight" removed here intentionally when moving the code around? Adding >> > that to the XSLT does not solve the problem. So do you have any idea of >> > what >> > is wrong here? >> > >> > miika > > _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface