For destinations or names with more than one line, it's common to have each line separated by a forward slash. I've tried to customize my map to replace semicolon with slash, but the slash does not appear. Is the slash an allowed character in a name or destination? I'm using the Latin1 character set. Brian
I have noticed that the slash, plus all following text, is mostly suppressed on my Nuvi 2795. The official Garmin maps manage to use a slash between multiple refs and destinations - maybe they are escaping it in some way? Looking at the same file with BaseCamp shows that the full text is present in the map file, so the problem is (at least partially) with the device and how it handles the strings. In the past I remember it working on my old 255W, although the spoken instructions stopped at the slash, so "A1/M2 Destination" would be read out as "A1" only. //colin On 2015-12-22 15:34, Brian Egge wrote:
For destinations or names with more than one line, it's common to have each line separated by a forward slash. I've tried to customize my map to replace semicolon with slash, but the slash does not appear. Is the slash an allowed character in a name or destination? I'm using the Latin1 character set.
Brian _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Tue, Dec 22, 2015 at 02:34:57PM +0000, Brian Egge wrote:
For destinations or names with more than one line, it's common to have each line separated by a forward slash. I've tried to customize my map to replace semicolon with slash, but the slash does not appear. Is the slash an allowed character in a name or destination? I'm using the Latin1 character set.
It should be allowed at least in names. A long time ago, I added a rule to the default style that applies the names from type=boundary relations to the lines, and I used the slash as a separator. It worked on my Garmin Edge 705. I think that the rule was effectively removed later, by the special processing of boundaries. The rule is still there (or was as of r3643), in the file resources/styles/default/relations, but probably unreachable. I no longer have any Garmin device, so I cannot reliably test this. BTW, note that ${attribute} and $(member_attribute) refer to different objects in the apply rules. I implemented the logic for $(member_attribute), so that you could write such rules in the first place. The $() syntax refers to the attributes of relation members, while ${} refers to the attributes of the relation on which the apply is being executed. Best regards, Marko
participants (3)
-
Brian Egge -
Colin Smale -
Marko Mäkelä