[mkgmap-dev] mkgmap: problems with encoding file used with option --license-file
From Steve Ratcliffe steve at parabola.me.uk on Sun Dec 4 16:31:16 GMT 2016
Patrik > -> Can you tell me what characters you do see instead? > For unicode map option copyright-file I see characters that look like > black diamonds with a question mark in it (picture attached, hope it > comes through). OK thanks that helps I will post something to try later. > -> lower-case option > I've double checked with older maps I was definitely building without > the --lower-case option and the map always showed proper case (capital > and lower case) names, preserving OSM style on my Garmin devices (at > least for the last few months... didn't/couldn't check back more). > Looking in BaseCamp at the license/copyright information I can say that > we had part in capitals and part in mixed cases, assuming that > copyright-message (I was using the message, not the copyright-file > option earlier) was in capital letters only. > The license-file part was before always in mixed cases as it should be. > And to make the statment complete: the codepage option was always used > and set. In MapSource etc it will display in upper and lower case even though the label in the map is all in uppercase. It just capitalises the first letter of each work and lower cases the rest. So "OSM Road" would be stored as "OSM ROAD" and displayed as "Osm Road". All I can do is control what is actually put into the map, how any particular device displays it is up to the device. ..Steve
- Previous message: [mkgmap-dev] mkgmap: problems with encoding file used with option --license-file
- Next message: [mkgmap-dev] mkgmap: problems with encoding file used with option --license-file
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list