From: Alexander Savenkov (email@example.com)
Date: Sat Apr 03 2004 - 06:24:59 EST
2004-04-03T02:34:38+03:00 D. Starner <firstname.lastname@example.org> wrote:
>> > 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.
Yeah, and it could read it as ďall your base are belong to usĒ. And
your browser renders it as a hollow square. Hey, and my cat canít read
it at all. Whatís the point of this?
> But it's questionable if any
> speech reader is going to try and interpret such ambiguous and rarely
> used characters specially.
As I already have said in another message, theyíre not that ambiguous
and rarely used. If someone misuses them, thatís his problem.
> 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.
You canít markup everything just like you canít make everything
plain text. Iíve no objections to <q speaker="Holmes">. Thatís just
-- Alexander Savenkov http://www.xmlhack.ru/ email@example.com http://www.xmlhack.ru/authors/croll/
This archive was generated by hypermail 2.1.5 : Sat Apr 03 2004 - 07:09:28 EST