Hi Attila, I'm guessing the decision to use single quotes rather than double quotes was an arbitrary one; some source OSM files use single quotes too, and trying to preserve the source quoting style adds additional overhead. The real problem is that the data is not being escaped properly, however it looks like there was a fix for this made in r100 of the splitter. What version are you using? Chris
Hi,
I've recently noticed that the splitter will create .osm files with values in single quotes. Is there a strong reason to do so while the original input .osm file has double quotes around values?
The problem arose when some .osm "role" keys contained single quotes, such as relation #172045 - right before the end of this file there's a value with single quote
<member type="node" ref="533796734" role="Addenbrooke's"/>
which splitter "converts" to
<member type='node' ref='533796734' role='Addenbrooke's'/>
making mkgmap to complain about a "bad file" and to stop processing further.
Anyone encountered this?
Thanks, Attila