<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I have a Subsurface xml file log (7 dives) that I export to CSV,
checking the option "CSV dive details". Two issues:<br>
<br>
1) The Subsurface exported CSV data are comma-delimited, yet the
Subsurface import panel has a default of tab-delimited. Given the
column headings provided by the CSV export file, it should be
rudimentary to test for the delimiter used and set the preference in
the import panel accordingly.<br>
<br>
2) This brings up a second issue. The Subsurface export file
provides headings upon re-import into Subsurface and the CSV import
table shows the imported heading in row # 2. So, it's not necessary
to supply the headings because they were provided by the import
file. But now, what should one do with the empty first row of the
table? See attached screenshot 1.<br>
<br>
3) I have dive notes that look something like this:<br>
<meta name="qrichtext" content="1">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;"><!--StartFragment-->Dive
plan:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">48m
12 min</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">asc 30m
2 min</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">30m
1 min (deep stop)</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">asc 15m
2 min; switch EAN50 20m</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">15m
1 min</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">12m
2 min</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">9m
3 min</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">6m
5 min</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">4.5m
13 min</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px; -qt-block-indent:0; text-indent:0px;">Total run
time: 41 minutes</p>
The dive notes are given, 1 line at a time, in the import table (see
attached screenshot 2). Result is that each dive takes several rows
of space in the import table: impossible to parse for import.<br>
<br>
In hand-prepared CSV imports, the program handled the information
much, much better. <br>
Kind regards,<br>
willem<br>
<br>
<br>
<br>
<br>
</body>
</html>