[OSM-dev] using current planet with osm2pqsql
jburgess777 at googlemail.com
Tue Jul 17 00:37:48 BST 2007
On Tue, 2007-07-17 at 09:14 +1000, Brett Henderson wrote:
> I don't know why some XML parsers are accepting this character and
> others aren't but I believe the correct behaviour is to throw an error.
> This is the same problem we had with the Java XML parser a couple of
> days ago in the thread "control characters in planet.osm". o023 is
> equal to 0x13 and is an illegal XML character. For now, it is simplest
> to strip it out with a sed command.
> This character was originally entered by Potlatch. A change has been
> committed to the Potlatch API to strip this character out (and others
> like it) to prevent it happening in the future.
> Apologies if this is already known but it seems like we're wasting
> effort looking at xml parser behaviour when the real problem is invalid xml.
Yes the planet.osm cause is understood but I'd still like to know why
some installations don't see this. I'm looking to identify something
like "this occurs in libxml2 version foo and later".
I don't see much effort wasted in asking Joerg to tell me what his
version of libxml2 is.
More information about the dev