Hi!
A fellow mapper has encountered a problem that mkgmap throws error messages
for rendering rules that have a semicolon or an umlaut in the value after
switching to mkgmap 1625.
The same ruleset did work with older versions. Is this a deliberate change
or a bug?
bye
Nop
--
View this message in context:
http://gis.638310.n2.nabble.com/Umlauts-and-semicolons-causing-parsing-errors-tp5114051p5114051.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
