[mkgmap-dev] Unicode maps showing locked or not found on GPS unitsFrom Felix Hartmann extremecarver at gmail.com on Tue Jul 1 08:11:18 BST 2014
On 30.06.2014 22:42, Steve Ratcliffe wrote: > > Hi > >> 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. > From your description it sounds as if the unicode characters > are just being displayed as latin1. > > If you have: Ã¤ Ã© Ã¡ instead of ä é á that would be it. That*s the case. Also for address search it therefore gets problematic to find addresses using any of theese "special" characters.. As long as you use 1252 they display fine, if one switches to Unicode they show up as above "scrambled" like above... > > ..Steve -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
- Previous message: [mkgmap-dev] Why is there a code-page in the .typ-file? And - is there a code-page a gmapsupp.img?
- Next message: [mkgmap-dev] Unicode maps showing locked or not found on GPS units
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list