[prev] [thread] [next] [lurker] [Date index for 2005/10/17]
--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Oct 17, 2005 at 04:51:21PM +0100, Matthew Garrett wrote:
> On Mon, Oct 17, 2005 at 05:45:34PM +0200, Juerd wrote:
> > Matthew Garrett skribis 2005-10-17 16:44 (+0100):
> > > U+0027 is sufficiently overloaded with a large number of historical=
=20
> > > meanings that it's preferable to use a more precise Unicode code poin=
t=20
> > > wherever possible.
> >=20
> > U+2019, having two very different uses, isn't quite more precise.
>=20
> It does at least have the advantage that you know it's going to look=20
> curly.
That's about as dumb as using <BLOCKQUOTE> in HTML for the indentation
effect.
=46rom http://www.unicode.org/standard/principles.html:
Interpreting Characters and Rendering Glyphs
The difference between identifying a code point and rendering it on
screen or paper is crucial to understanding the Unicode Standard's
role in text processing. The character identified by a Unicode code
point is an abstract entity, such as "LATIN CHARACTER CAPITAL A"
or "BENGALI DIGIT 5." The mark made on screen or paper -- called a
glyph -- is a visual representation of the character.
The Unicode Standard does not define glyph images. The standard
defines how characters are interpreted, not how glyphs are
rendered. The software or hardware-rendering engine of a computer is
responsible for the appearance of the characters on the screen. The
Unicode Standard does not specify the size, shape, nor style of
on-screen characters.
If you want to send to something that looks curly, send me a PDF or=20
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.
Abigail
--C7zPtVaVf+AK4Oqc
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFDU+JGBOh7Ggo6rasRAvhRAJ9qV6zjZsKAyBNKA3+fnd6rbMlXLwCgl+Y0
DtiLQ+T9F6F3UZzUoymj9HI=
=vQVy
-----END PGP SIGNATURE-----
--C7zPtVaVf+AK4Oqc--
There's stuff above here
Generated at 20:00 on 17 Oct 2005 by mariachi 0.52