<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><br><div dir="ltr">sent from a phone</div><div dir="ltr"><br><blockquote type="cite">On 26. Dec 2020, at 23:46, Mateusz Konieczny via Tagging <tagging@openstreetmap.org> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div>I described it in the original post.<br></div><div><br></div><div><a href="https://lists.openstreetmap.org/pipermail/tagging/2020-December/057448.html">https://lists.openstreetmap.org/pipermail/tagging/2020-December/057448.html</a><br></div><div>"Many people are interested in mapping zoo detail, especially where given animal
has an enclosure
<br></div><div><br></div><div>It would be desirable to render it on many maps, likely also general purpose maps
(as in zoo areas in high zooms it is among the most important info)."<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;" preoffsettop="1252"><div> Isn’t this be like adding local names for surface values, e.g. surface:name=Schotter for a German road?<br></div></blockquote><div>No, because rendering what kind of animal is in a given enclosure is standard and <br></div><div>desirable (to the point of having many kind of tagging for renderer to achieve this),<br></div><div>while rendering surface names is highly unusual.</div></div></blockquote><br><div><br></div><div>I can understand that rendering the name of an animal is interesting for the map, but I don’t understand why it has to be the local language, I’d rather expect it to be in the language the user is using, seems way more useful </div><div><br></div><div><br></div><div>Cheers Martin </div></body></html>