<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Steve,<br>
<br>
as already announced:<br>
with all the intensive testing regarding unicode, gmap and others I
found following in my opinion strange behaviour in relation to
gmapsupp format:<br>
<ul>
<li>my mkgmap call for gmapsupp creation contains the option
'--product-version="1612"'</li>
<li>when checking the created gmapsupp.img with GMapTool, the
heades does contain only 'v 0.00'</li>
<li>when checking the gmapsupp.img via BaseCamp while the GPS is
connected the version column also shows 0.00</li>
<li>the detailed output of GMapTool does not contain the string
"1612" at all</li>
</ul>
This raises my concern about product-version not properly handled in
the gmapsupp conversion.<br>
<br>
Yes, I know, a gmapsupp.img may contain more than only one
product/family/map...<br>
But as mkgmap creates a gmapsupp.img for one product/family only per
run it might be worth writing the version info properly into the
header ?<br>
.... other maps (official ones) seem to propagate the release
information into that header field.<br>
<br>
I'm not completely sure if above assumptions are correct or if I
missed something.<br>
<br>
Sorry for bringing up another issue.... ;-)<br>
And thanks for looking at it.<br>
<br>
Cheers<br>
Patrik<br>
</body>
</html>