[mkgmap-dev] Unicode maps showing locked or not found on GPS units

[Felix Hartmann]

Hi, could some people please test with their maps using unicode on their
GPS (--code-page=65001) and maybe also report FID (family-ID) used for maps.
I have the problem that some users report the maps show up as locked!

(maps created with mkgmap version 3300 as of June 18)

So far problematic:
Garmin GPSMaps 64 - FID 6371 - sent from Mac OSx Basecamp/Map Install.
Garmin Edge 1000 - FID=6531 - sent via??

Works as tested below ( sent via Mapsource, Mapinstall (Windows) and
gmapsupp.img created by mkgmap.jar (java 1.7 windows) ):
Garmin Oregon 600 - FID 6365 works...
Garmin etrex 30 - FID 6365, works...

Works without problems as long as no code-page other than latin1
characters are in the map AND is sent via Mapsource or MapInstall
(Windows) - does not work if gmapsupp.img created by mkgmap! Problems -
even German Umlauts (ÖÄÜ or "french" accents like é) are not displayed
correctly anymore (instead split into two funky looking characters).
Therefore for old units --latin1 is still the better option for old
devices for most european countries.
Garmin Vista HCx - FID=6365


So it's clear that there is something wrong in the way mkgmap.jar
creates gmapsupp.img for maps with Unicode - though it does work for
newer devices with full unicode support. Mind though I did not check on
the unit itself if cyrillic or arrabic script is actually working.


BTW 2. -- It would be great if there is a short-code like --latin1 for
unicode too! E.g. --unicode instead of --code-page=65001, just for
simplicity...

[Andrzej Popowski]

Hi,

Garmin is changing something in their map locking system. I think this
is connected with Unicode maps. Please check if original Garmin maps
work with these device, for example Winter Activity Map:
http://www.garmin.com/uk/maps/onthetrail#apps

And please report any problem to Garmin support.

[Felix Hartmann]

thanks - okay I got 2 people with problems now both using a 64. I asked
them to try the Winter Activity Map - will report back. Well and the
Edge 1000 still stands as problematic too.
Also seems that all are sending the maps for Mac OSx
Basecamp/MapInstall.. So not sure if maps sent via Windows MapInstall
are also affected!

Post by Andrzej Popowski
Hi,
Garmin is changing something in their map locking system. I think this
is connected with Unicode maps. Please check if original Garmin maps
http://www.garmin.com/uk/maps/onthetrail#apps
And please report any problem to Garmin support.

[Felix Hartmann]

Okay, Windows MapInstall has the same problem and mkgmap.jar created
gmapsupp.img too!
So I guess using Mapsource won't help either...

So far still only problematic on 64 and edge 1000.

Post by Andrzej Popowski
Hi,
Garmin is changing something in their map locking system. I think this
is connected with Unicode maps. Please check if original Garmin maps
http://www.garmin.com/uk/maps/onthetrail#apps
And please report any problem to Garmin support.

[Felix Hartmann]

Post by Andrzej Popowski
Hi,
Garmin is changing something in their map locking system. I think this
is connected with Unicode maps. Please check if original Garmin maps
http://www.garmin.com/uk/maps/onthetrail#apps
And please report any problem to Garmin support.

No problem for the free winter activity map. It loads on Edge 1000....
So only mkgmap created Unicode maps are showing up as locked...
I'll still report back if the maps using .typ-file also in unicode work
- but yes I doubt that this small change will make them work.

[Felix Hartmann]

Having the .typ-file changed by gmaptool to unicode doesn't change
anything for map authentication.... So - the error is not related to the
.typ-file as expected...

Post by Felix Hartmann

Post by Andrzej Popowski
Hi,
Garmin is changing something in their map locking system. I think
this is connected with Unicode maps. Please check if original Garmin
http://www.garmin.com/uk/maps/onthetrail#apps
And please report any problem to Garmin support.

No problem for the free winter activity map. It loads on Edge 1000....
So only mkgmap created Unicode maps are showing up as locked...
I'll still report back if the maps using .typ-file also in unicode
work - but yes I doubt that this small change will make them work.

[Steve Ratcliffe]

Hi

Post by Felix Hartmann
even German Umlauts (ÖÄÜ or "french" accents like é) are not displayed
correctly anymore (instead split into two funky looking characters).
Therefore for old units --latin1 is still the better option for old
devices for most european countries.
Garmin Vista HCx - FID=6365

I would be suprised if older units that do not contain
more than one character set support unicode.

[Felix Hartmann]

Post by Steve Ratcliffe
Hi

Post by Felix Hartmann
even German Umlauts (ÖÄÜ or "french" accents like é) are not displayed
correctly anymore (instead split into two funky looking characters).
Therefore for old units --latin1 is still the better option for old
devices for most european countries.
Garmin Vista HCx - FID=6365

I would be suprised if older units that do not contain
more than one character set support unicode.

[Steve Ratcliffe]

Post by Felix Hartmann
BTW 2. -- It would be great if there is a short-code like --latin1 for
unicode too! E.g. --unicode instead of --code-page=65001, just for
simplicity...

Patch attached.

..Steve

[Felix Hartmann]

Hi Steve,

thanks a lot. I think this should be committed... Unicode and latin1
will be the most used code-pages. And except the locking and creating of
gmapsupp.img - mkgmap produced unicode maps work fine.

Post by Steve Ratcliffe

Post by Felix Hartmann
BTW 2. -- It would be great if there is a short-code like --latin1 for
unicode too! E.g. --unicode instead of --code-page=65001, just for
simplicity...

Patch attached.
..Steve

[Felix Hartmann]