I do not remember the details of UDDF specification, so should dig into it to make sure. But only fail3.uddf includes divecomputers in section equipment. In UDDF, each dive references into this equipment section for the used dive computer. And for the fail.uddf and fail2.uddf this info is missing, so the reference not returning any sensible data.
On Fri, Mar 22, 2024 at 4:39 PM Henrik B A <hen...@synth.no> wrote: > Miika: Are you able to see what's wrong with the import, based on the > files I provided? > > Henrik > > On Sun, Mar 17, 2024 at 8:04 PM Miika Turkia via subsurface < > subsurface@subsurface-divelog.org> wrote: > >> On Sun, Mar 17, 2024 at 8:59 PM Michael Keller via subsurface < >> subsurface@subsurface-divelog.org> wrote: >> >>> Hi Berthold. >>> >>> >>> On 17/03/24 21:16, Berthold Stoeger via subsurface wrote: >>> >>> >>> >>> I reworked quite a bit of the string handling in the parser recently. >>> Did >>> >>> this work with older versions? Especially the dive buddy thing could be >>> >>> a consequence of the rework. >>> >>> >>> UDDF import / export uses XSLT to convert the Subsurface XML to / from >>> UDDF, so the parser / generator used is the same that is used to save and >>> load Subsurface log files - so if this was caused by a bug in the parser >>> then it is strange that this has not been reported already by users trying >>> to load / save log files. >>> >> >> Subsurface's own logs, whether in XML or in git storage, are not going >> through XSLT parsing. The XSLT file used for UDDF import is only used for >> that format, so it is quite limited user base that could face the issue. >> _______________________________________________ >> subsurface mailing list -- subsurface@subsurface-divelog.org >> To unsubscribe send an email to subsurface-le...@subsurface-divelog.org >> >
_______________________________________________ subsurface mailing list -- subsurface@subsurface-divelog.org To unsubscribe send an email to subsurface-le...@subsurface-divelog.org
