It's a huge mistake for Unicode to have two different code points having the same glyph. There should not be semantic meaning that disappears when something is printed.
We're going to be suffering for that mistake for a looong time.
We're going to be suffering for that mistake for a looong time.
a+b=d+d
Shouldn't be uppercased.
It's an insoluble problem to put contextual semantic info into Unicode characters, because individual characters have no context.
It's used in typesetting sometimes, and if a character is used then it should have an encoding.
IMO there's little semantic difference so it doesn't deserve a character. We should have drawn the line between content and formatting, but it's too late and what we have now is emoji and one-use glyphs. [1]
No. In Japanese, how you read/pronounce a character depends on context. Sometimes they are the same as Chinese, sometimes not.
Take mountain (山) for example.
Using the Chinese pronouncation it is "san". 富士山 (Mount Fuji) is ふじさん "Fuji san"
Using Japanese pronouncation it is "yama". 山登り (Mountain Climbing) is やまのぼり "yamanoboru"
(and don't call me Shirley)
PS: Isn't り pronounced "ri" and る pronounced "ru"?
Yes, I typoed that and it's too late to fix it. り is "ri", not "ru".
exactly!
I can see why you'd say that, but who decides whether it should?