On Fri, Aug 8, 2014 at 1:30 AM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum 10353@lyskom.lysator.liu.se wrote:
Like I said, I didn't have an authoritative source (as I didn't know where to find one), and so I used two non-authoritative sources, which happened to agree: the unicode.org files, and Python 3. Up to you what you want to apply; the part that I was most noticing was the box drawing characters, which I thought was actually a font error (as I wasn't seeing the double lines).
ChrisA
Ok. Then my approach would be to keep things as they are until someone comes up with a specific complaint. :-) As I said, the box drawing stuff is fixed, so feel free to raise a new issue if you find something else which is a concrete problem.
(As a side note, I think you were justified in assuming thick/double lines was a font issue. There is no semantical difference, so I imagine the only reason why Unicode assigns separate codepoints to them instead of treating them as font variants is for compatibility with some other encoding that has both...)
pike-devel@lists.lysator.liu.se