On Mon, Oct 17, 2005 at 07:55:14PM +0200, A. Pagaltzis wrote: > * Abigail <abig...@abigail.nl> [2005-10-17 19:45]: > > If you want to send to something that looks curly, send me a > > PDF or an image. If you want to indicate you're contracting two > > words, use a apostrophe. And let *me* decide whether I want > > them straight or curly. > > Meanwhile everyone is using apostrophes as straight quote marks.
Yeah. And guess what? I've been using computers since 1981, and it hasn't bothered me once. I'm human, and I understand context. It's the same character used for different purposes, but what purpose it is, is always clear. > This would have been sane if Unicode had conceded the overloaded > meaning of U+0027 and defined a separate apostrophe character > distinct from U+2019. > > As I said, the one hateful aspect about it. > > Of course, that new apostrophe codepoint would show up just as > mangled in non-Unicode-aware apps as the curly quotes do. My terminal doesn't do Unicode (and the ones that do suck in different ways - I'm sticking with rxvt). Nor does the font (6x13) I use has glyphs above 255. Abigail
pgpxi7keqbGfG.pgp
Description: PGP signature
