Hi, I think different models of GPS react differently. Most common is that new devices require digital signature for Unicode maps. Maps with CP1252 usually work. At least handheld GPS, more problems could be with nuvi. -- Best regards, Andrzej

Hi Felix, I guess the idea is that Garmin holds certificates and only offers signing services for money. Or doesn't offer at all. Well, maps aren't encrypted, so you could hack firmware in your GPS to disable verification. -- Best regards, Andrzej

Hello, I just found this page: https://www.gpsrchive.com/GPSMAP/GPSMAP%2066/Common%20Issues.html Due to issue 26 it seems solved. But I do not fully understand whether the issue truly no longer exists or it has been solved by not using UTF-8 maps. If the latter is the case then it seems to be big problem for me to accept it. Someone could confirm which of the cases it is? Thanks Marek 2021-08-02 14:50 GMT+02:00, Marek Greško <mgresko8@gmail.com>:

Hi,

that is what I was afraid about. I use only UTF-8 maps. My current device of choice would be GPSmap66s since the other do not possess features I would expect. Has somebody experience with this device and UTF-8 maps? Are they working?

Thanks

Marek

2021-07-31 15:18 GMT+02:00, Andrzej Popowski <popej@poczta.onet.pl>:

...

Hi,

I think different models of GPS react differently. Most common is that new devices require digital signature for Unicode maps. Maps with CP1252 usually work. At least handheld GPS, more problems could be with nuvi.

-- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

of course - any new device needs hacked firmware or non unicode maps. 1251 or whatever works however. I explained it above - tested that many times. If we cannot come up how to digitally sign a map (maybe any code signing certificate would be fine? but I have no clue how they signed the maps and which parts are signed) it's that way On Tue, 3 Aug 2021 at 17:59, Andrzej Popowski <popej@poczta.onet.pl> wrote:

Hi Marek,

I have tested on 66st firmware 7.20. Unicode maps compiled with mkgmap are rejected, the same message as you have found on issue 26 - "Cannot authenticate maps".

-- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- Felix Hartman - Openmtbmap.org & VeloMap.org

Just make a map of Cyprus and check if you get greek in the South, and Turkish special characters in the north. The Latin alphabet without special characters like ö or accents is covered in nearly all codepages. On Wed, 4 Aug 2021, 07:15 7770 <7770@foskan.eu> wrote:

Hi. i have made maps using the --code-page=65001 option. Maps are read just fine by GPSMAP 66st with all firmwares i have had (at least since 4.xx up till 7.60).

Could there be something overriding this setting and not making the map unicode, is there a way to check what the map really is?

i use map data from geofabrik.de.

regards Karl

On tisdag 3 augusti 2021 kl. 17:59:15 CEST Andrzej Popowski wrote:

...

Hi Marek,

I have tested on 66st firmware 7.20. Unicode maps compiled with mkgmap are rejected, the same message as you have found on issue 26 - "Cannot authenticate maps".

_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi. I checked some maps where i have bits of Russia and Ukraine, all names are transliterated. Is this bacause of data, i use data from geofabrik.de or a setting when running mkgmap? Can i retain original names in original writing? Regards Karl On onsdag 4 augusti 2021 kl. 16:20:48 CEST Andrzej Popowski wrote:

Hi,

65001 is exactly Unicode UTF-8, that we are talking about. It doesn't work for me.