Umlauts and semicolons causing parsing errors?
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-error... Sent from the Mkgmap Development mailing list archive at Nabble.com.
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
Hi! Steve Ratcliffe wrote:
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.
The rule shop=Bäckerei [0x2A05 resolution 24] will produce an error Error in style: Error: (points:50): Stack size is 3 Could not open style null While I don't think using umlauts or native language in tags is a good idea, evaluating those tags should be possible, shouldn't it? bye Nop -- View this message in context: http://gis.638310.n2.nabble.com/Umlauts-and-semicolons-causing-parsing-error... Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (2)
-
NopMap -
Steve Ratcliffe