<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Jan 7, 2021, 19:09 by pelderson@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div dir="ltr">Jmapb <<a target="_blank" href="mailto:jmapb@gmx.com" rel="noopener noreferrer">jmapb@gmx.com</a>>:<br></div><div class=""><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="">We don't want housenumbers to turn into regexes.<br></blockquote><div><br></div><div>That's a strawman argument, and an argumentum ad populum. I did not see anybody suggesting regexp in housenumbers, that's the strawman, and We is the argumentum ad populum, but I'll let that go because I agree!<br></div><div><br></div><div>However, meaningful punctiation is not regexp, and this would not be the first case in OSM. <br></div><div> <br></div></div></div></blockquote><div>I can state it in more accurate way: <br></div><div><br></div><div>if I am entering single housenumber with weird characters such as ( ) or | or ' or "<br></div><div>there should be no need to escape them.<br></div><div><br></div><div>As this would make it<br></div><div><br></div><div>- incomprehensible for most of mappers<br></div><div>- redefine all existing addr:housenumber<br></div><div><br></div><div>New tag for storing extra info is preferable over redefining existing one.<br></div><div><br></div> </body>
</html>