On Thu, Apr 15, 2010 at 09:10:30PM +0000, Vegard Øye wrote:
Date: Thu, 15 Apr 2010 21:28:33 +0200 From: [email protected]
× is included in ISO 8859-1 (Latin-1), so it should be quite safe anyway, Unicode or no Unicode.
"Safe"? As if we weren't fighting with shitty software all the time.
Emacs is not shitty software. :)
Granted.
And the nice advantage of UTF-8 is that it's ASCII-compatible -- i.e. as long as it does not contain codepoints above 127, problems never occur.
I think that's nice too, but Asians complain because their characters are encoded as multi-byte all the way, increasing the file size. (Us Norwegians only encounter multi-byte with Ææ Øø Åå, so we get a much nicer deal. Of course, UTF-8 doesn't save us from the madness of the Norwegian QWERTY layout.)
Sure. And with UTF-16, you get two bytes for any character up to 0xFFFF, if I'm not mistaken. Plus the null char and byte order problems. But we're getting *really* off topic here :-)
Thanks for the tip. So I guess it's either "commit [2c87f791af]" or "revision [2c87f791af]". What sounds best? (The brackets are for consistency with Trac.)
From the mentioned man page:
The word "commit" is often used by git in the same places other revision control systems use the words "revision" or "version". And indeed, I don't remember even seeing "revision" being used at all on the Git mailing list or other gitly places. Štěpán