You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Potlatch has historically stopped you entering 0x00-0x1F. Unfortunately the code to do this is newly broken in latest Ming. At the weekend I needed to commit some Potlatch stuff on a machine that only had the latest Ming installed, so had to temporarily remove the check.
Author: smsm1 [Added to the original trac issue at 10.33am, Tuesday, 14th July 2009]
We'll need to add that check to Rails too, in the AMF controller where the strings are read. We don't need to do this on the nwr models, as the XML parser automatically does this check for us, thus would just slow things down unnecessarily.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reporter: smsm1
[Submitted to the original trac issue database at 10.47pm, Monday, 13th July 2009]
You shouldn't be able to put ascii control characters into the OSM database, as it can break the diffs.
http://lists.openstreetmap.org/pipermail/dev/2009-July/016153.html
The text was updated successfully, but these errors were encountered: