> 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?
Its not deliberate certainly. Do you have an example. You need to quote any value that has a semi-colon in, but I think you always had to. ..Steve _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
