Thanks, the fix seems to be working properly.
miika
On Sat, Jun 16, 2018 at 4:21 PM, Rainer Mohr wrote:
> Sent via personal mail to Miika
>
> Rainer
>
> Am 16.06.18 um 02:15 schrieb Miika Turkia:
>
> I just sent a pull req that should take care of this. However, I do not
> possess test data wit
Sent via personal mail to Miika
Rainer
Am 16.06.18 um 02:15 schrieb Miika Turkia:
I just sent a pull req that should take care of this. However, I do
not possess test data with the new format. Could you Rainer send me a
sample file? (The addition for support for the new format is quite
trivia
I just sent a pull req that should take care of this. However, I do not
possess test data with the new format. Could you Rainer send me a sample
file? (The addition for support for the new format is quite trivial, but
still I would like to test it out.)
miika
On Fri, Jun 15, 2018 at 12:32 AM, Mii
I will try to take a look into this within a few days
miika
> On 8 Jun 2018, at 0.25, Dirk Hohndel wrote:
>
> Miika is the wunderkind-slash-madman who maintains our importers and deals
> with the XSLT...
>
> /D
>
>> On Jun 7, 2018, at 1:58 AM, Rainer Mohr wrote:
>>
>> Gentlemen,
>>
>> Jus
Miika is the wunderkind-slash-madman who maintains our importers and deals with
the XSLT...
/D
> On Jun 7, 2018, at 1:58 AM, Rainer Mohr wrote:
>
> Gentlemen,
>
> Just noticed, that the Suunto DM5 Import is very broken as it can't parse the
> profile data from recent and semi-recent DM5 file
Gentlemen,
Just noticed, that the Suunto DM5 Import is very broken as it can't
parse the profile data from recent and semi-recent DM5 files properly.
Suunto has once again changed their data structures in the profile part
of DM5. Noticed after quite a few broken profiles popped up on divelogs.d
