W3C home > Mailing lists > Public > www-svg@w3.org > September 2002

Re: [SVG1.0] no tspan allowed inside an anchor?

From: Jim Ley <jim@jibbering.com>
Date: Tue, 10 Sep 2002 18:51:40 -0000
Message-ID: <034f01c258fb$19b19820$ca969dc3@emedia.co.uk>
To: "Chris Lilley" <chris@w3.org>, <www-svg@w3.org>

"Chris Lilley" <chris@w3.org>
> Whether these two types of elements happen to have the same of
> different attrribute sets is largely orthogonal.
> (Note to self, check what XAG says about theis once online again)

2.8 is the only relevant bit in the document that I can see, "don't
overload the semantics of elements", I don't think it would be, I think
the semantics are "a chunk of text", I can see and am more than willing
to concede the argument though.

> Here is an example. Sending the entire block to a speech synth, with
> prosodic changes for the span-like (phrasal) elements gives verry
> different results to sending each of the elements of pieces of PCDATA
> separately.

I fully see the problem there, but I don't see the difference between
<text> that has <text> as a parent, and text which doesn't, it can be
styled with css, it can be identified with XPath, I don't see that it
needs seperate elements, it may or may not be neater I guess depending on
your viewpoint.

Received on Tuesday, 10 September 2002 14:57:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:53:55 UTC