Sorry - should say ... {tag|subst: ... Ticker On Wed, 2023-12-13 at 10:18 +0000, Ticker Berkin wrote:
Hi Diego
On the issue of case, your build is probably running without --lower-case, so everything in the .img file is UPPER. The Garmin device then initcaps stuff in a way of its own choosing.
Use of --lower-case can cause problems and unknowns with the index system where there are different case representations of the same location. Even then my Garmin device still chose to change the case sometimes as it displays.
The degree symbol can't be represented in your chosen charset and there are tables in mkgmap to handle reasonable mappings.
I suggest you use something like ... '${tag:subst:"o=>o"} in your style, where the first o is unicode degree symbol and the second is whatever you want. You will need a text editor that handles unicode.
Hope this helps Ticker
On Tue, 2023-12-12 at 18:34 +0000, helter skelter wrote:
Hello guys I have a problem with text and special characters on my map. In OSM there are some elements that contain a roman number in their name, such as "I° peak", "II° peak", "III° peak" and so on. On my rendered map I get the symbol ° replaced with the word "deg", so "Ideg peak", "Iideg peak", "Iiideg peak" and so on. I can't understand how to avoid the replacement of ° to deg. Also, I would like to keep the capital letters like in the original name, is it possible ? Thank you Cheers Diego
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev