> > It only affects its (visual) aesthetic
> > quality.
>
> That is arguable. An aural user agent could pronounce "1, 2, 3" a bit
> different from "1, 2, 3" if there is a (say) thin space between the
> digits in the latter case. It could pronounce it quicker, for example.
And it could read it as "thin space", too. But it's questionable if any
speech reader is going to try and interpret such ambiguous and rarely
used characters specially. Even if it does, that doesn't make it plain
text; italics and <q speaker="Holmes"> can be interpreted by speech
readers much more usefully, but are clearly not plain text.
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
