On Mon, Mar 12, 2018 at 2:23 PM, <osm.tagg...@thorsten.engler.id.au> wrote: > Actually, that can easily happen if you have 1½ but some software wants to > convert it to simple ASCII and doesn't add a space between the 1 and 1/2 when > converting the ½. While if the original text already is "1 1/2" this doesn't > happen. > > Obviously, in a perfect world, where everything is Unicode and stays Unicode, > I would agree that using ½ is better than 1/2. Unfortunately, we still have > to often assume that a string will get converted from Unicode into ASCII or > some specific ANSI codepage.
There are very few projects that are as global in scope as OpenStreetMap. If we can't presume that Unicode works in our pipeline, there's little hope for us; we already have to deal with a great many names in non-Latin scripts. I'm all for 1½ or 1¹⁄₂ (two different ways of writing it; there are other possibilities like 1⅟₂ but normalization should take care of all of them.) _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
