[mkgmap-dev] Umlauts and semicolons causing parsing errors?

Fri May 28 21:12:23 BST 2010

> 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