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. > -----Original Message----- > From: Andrew Hain <andrewhain...@hotmail.co.uk> > Sent: Tuesday, 13 March 2018 03:16 > To: Tag discussion, strategy and related tools > <tagging@openstreetmap.org> > Subject: Re: [Tagging] Tagging fraction house numbers? > > Unicode fractions have an important advantage: they can’t run into a > previous number, 1½ rather than 11/2. > > -- > Andrew > > ________________________________________ > From: James <james2...@gmail.com> > Sent: 12 March 2018 15:43:33 > To: Tag discussion, strategy and related tools > Subject: [Tagging] Tagging fraction house numbers? > > https://i.imgur.com/eigT5hX_d.jpg?maxwidth=640&shape=thumb&fidelity= > medium > > How should this be tagged in housenumber? Using unicode ( ½ ) or > ASCII( 1/2 )? > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
