Re: Significant whitespace (was Re: Blogging sucks)

[prev] [thread] [next] [lurker] [Date index for 2005/10/17]

From: Abigail
Subject: Re: Significant whitespace (was Re: Blogging sucks)
Date: 19:02 on 17 Oct 2005
--u3/rZRmxL6MmkK24
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 17, 2005 at 07:55:14PM +0200, A. Pagaltzis wrote:
> * Abigail <abigail@xxxxxxx.xx> [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.
>=20
> 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,=20
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.
>=20
> As I said, the one hateful aspect about it.
>=20
> 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=
=20
above 255.=20


Abigail

--u3/rZRmxL6MmkK24
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFDU+c9BOh7Ggo6rasRAoODAJ9tMkPo0uC+H+K1kN0mRfZ4AjkmpwCeP86q
EigfRyqE0lKVhh7daODUz30=
=+wgf
-----END PGP SIGNATURE-----

--u3/rZRmxL6MmkK24--

Generated at 20:00 on 17 Oct 2005 by mariachi 0.52