<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 13, 2014, at 7:03 PM, Stephan Knauss <<a href="mailto:osm@stephans-server.de">osm@stephans-server.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">No local mapper wants to read München (Munich) on the map. So why should Japanese or Chinese mappers want to read something on their map?</span></blockquote></div><br><div>- if they were using a Japanese only map, then I can understand, but that would be pulling from the name:ja= tag, right?</div><div><br></div><div>- every single major sign, Street name, Highway exit, Large train station identifying sign, City Building label, etc is labeled in English as well as Japanese. Every single one of the 2000 or so tollway exits are labeled in english, and the hundreds of thousands of blue intersection road signs are also printed bi-lingually as well - as a service to the forigners living there, as mastering reading and understanding all the Kanji for the various place names takes a decade or so of straight practice. </div><div><br></div><div> If they sign most everything imaginable that is important in Japanese + English, having it mapped that way too seems reasonable.</div><div><br></div><div>Understanding that this "JA (en)" schema is bad for the database makes sense - but couldn't those also be pulling from the name:*= tags?</div><div><br></div><div><br></div><div>Javbw</div></body></html>