404 karma · joined August 17, 2010
As for this particular character (cold), both variants are familiar to Japanese readers, with the one described as Japanese in your link being the one you'd typically see in print, while the other one is common in handwriting, and nobody in Japan would treat these two as different. From a Japanese point of view, this is definitely the kind of thing you change by switching fonts.
This pdf is the official list of basic chinese characters, published by the Japanese governement. Look on page 9, it shows both variants of this characters in hand writing.
http://www.bunka.go.jp/kokugo_nihongo/pdf/jouyoukanjihyou_h2...
The fact that one of the variants in not familiar to Chinese readers complicates the issue, but there are at least reasonable reasons to argue that this is one, not two, characters.
I think it is possible to argue that han unification was not done very well and that the UC made too many classification mistakes (although I personally think it is generally not that bad), but I don't think arguing that unification is a bad thing entirely has legs.
The variations on characters which have been merged are usually even closer than that. More like the single or double storey "a", or the single or double loop "g".
By the way, Unicode is about scripts, not languages. If we started distinguishing by language, we might need to start remembering that china doesn't have a single language. Duplicating all those characters again to cover Mandarin and Cantonese and Wu and Hakka and Hokkien?
Should we have a different letter for Æ in Bokmål and Nynorsk? How about Riskmål?
The equivalent of Æ and Ä in Han scripts have not been unified. The equivalent of a in Futura and a in Verdana have. There's tons of chinese characters, so a few of them are bound to be borderline and maybe contentious. But overall, Han unification was unavoidable for a project like Unicode.
Here are two screenshots in Japanese and Chinese, taken from the http://www.yomiuri.co.jp/ for one, and http://www.cntv.cn/ for the other. Neither media outlet can be accused of being cultural sellouts misrepresenting the written tradition of their countries.
Japanese: https://www.dropbox.com/s/lpb3dk26ftds6oh/Screenshot%202015-... Chinese: https://www.dropbox.com/s/dcwv33ho0juracg/Screenshot%202015-...
These are the same characters, and unifying them is the only sane thing to do. The same is true for most characters. There are also some characters which are clearly distinct in both scripts, and unicode treats them as different. Some are grey-zone, and there is room for reasonable disagreement.
But as a whole, the case of unification of Chinese and Japanese is stronger than for Antiqua and Fraktur.
Should Norwegian A and English A be different Unicode code points just because Norwegian also has Ø, proving that it is a different writing system? You may want to debate whether i and ı should the same letter (they aren't), but most letters in the Turkish alphabet are the same as the letters in the English alphabet.
Japan has had a tendency to includes all sorts of crap, including this example of actual crap, into its character sets/encodings. Japan also has a history of working with the various standard bodies like the Unicode Consortium. Because Japanese systems had the pile of poo, unicode has it.
For a different example, 国 and 國 used to be the same character, but China and Japan (left) have both diverged the traditional form still used in Taiwan (right). Unicode treats them as separate.
今 Looks slightly different in traditional Chinese vs other languages. In traditional Chinese, the little straight line between the two angled lines is sloped, while it is horizontal in simplified Chinese, Japanese or Korean. Any reader of any of these languages would have no issue if the variant they are used to was replaced by the other one. They might think you have a sloppy handwriting or an ugly font if they even notice, but that's about it. Unicode treats them as the same.
Also, since CJK languages are comfortable with having an unbounded set of letters to work from, they tend to be comfortable with declaring every odd thing a separate letter. Witness the mess that half-width katakana is. Or notice that the origin of most emoji is not in the disregard of white old men for "lesser" languages, but comes from importing existing characters from Japanese encodings.
Which also hints at one more factor. Historically, and still very much to this day, Japan has been much more active in standardization bodies than most other non western countries. Unsurprisingly, Japanese is much better supported by modern software than many other non western languages.
Not only is it language dependent (and any solution baked into css needs to work for all languages where it is relevant), and do various publishers have slightly differing rules about it, but it also depends on the meaning, as this example shows. Whether "Now" is part of the "Google Now" name, or works as an adverb influences the casing.
CSS has become quite a bit more complicated these days, but it is still quite far form being sentient.
TL;DR: Proper title casing is AI-complete
Some business models are impossible without slavery. Does this mean slavery should be allowed?
Stallman's argument here is the same: if the particular software you make can't survive financially without abusing people, then you shouldn't have a right to make that software. And he considers all proprietary software to be abusing people's human rights.
So if you want to counter him, saying that it will put developers out if work is no more valid that saying that abolition of slavery is bad because of the financial hardship it would impose on the cotton industry.
To counter Stallman, you have to come up with arguments showing that non free software does not abuse its users.
Don't worry too much about this one. I am French, and the phrasing of OCaml's error messages is just as strange before the transliteration.