Hi Steve, hello list,

Here's a patch that documents the naming options better. It mainly
describes the --family-name option (previously only a TODO). Is this the
best way to submit them? (I noticed that a rather trivial patch that I
sent to the list, about Splitter reading hex numbers from areas.list,
was not checked in so I'm wondering if there's a better way to send
patches?)

Best regards,

Valentijn
--- options.orig	2009-08-12 11:05:57.000000000 +0200
+++ options	2009-08-12 11:09:48.000000000 +0200
@@ -123,7 +123,13 @@
 	This is an integer that identifies a family of products.
 
 --family-name
-	TODO: describe this
+	If you build several maps, this option describes the
+	family name of all of your maps. Garmin will display this
+	in the map selection screen.
+	Example: --family-name="OpenStreetmap mkgmap XL 2019"
+	TODO: at least the "-" character seems to have a strange
+	effect on the family name; latin-alphabet and digits seem
+	safe, but other characters should be checked.
 
 --product-id
 	This is an integer that identifies a product within a family.
@@ -134,8 +140,11 @@
 
 --overview-mapname=name
 	If --tdbfile is enabled, this gives the name of the overview
-	.img and .tdb files.
-	The default map name is OSM_map.
+	.img and .tdb files. The default map name is OSM_map.
+	On Garmin maps, this option describes the area of your
+	map, for example "Germany_and_Belgium".
+	TODO: underscores seem to render as spaces, not sure if this
+	is mandatory.
 	
 --overview-mapnumber=8 digit number
 	If --tdbfile is enabled, this gives the internal 8 digit
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Reply via email to