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 u
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
wh
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.
Hi,
I need some help regarding the transliteration filters. I would like to use
them to transliterate cyrillic name tags (1251) to latin (1250). I have
tried with:
name=* {set name='${name|ascii:} '}
but i get some weird results. For example tag:
name=шума
is translated into „SHUMA“
instead o
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 bi