W3C home > Mailing lists > Public > www-svg@w3.org > April 2005

Re: [SVGMobile12] Chapter 7

From: Cameron McCormack <cam-www-svg@aka.mcc.id.au>
Date: Thu, 28 Apr 2005 23:18:39 +1000
To: www-svg@w3.org
Message-ID: <20050428131839.GA20123@port.mcc.id.au>

Hi Chris.

I wrote:
> >   Also, a lot of the red monospace text describing the
> >   transformations is quite unreadable.

Chris Lilley:
> To clarify - is it the styling that makes it unreadable, or are you
> using 'red monospaced' to indicate the particular pieces of text whose
> content is unreadable?

Just to identify.  I think it was mostly the lack of indentation that I
found caused the unreadability.

> The spec says:
>   In the above definition, g[n] refers to the element with
>   the id "g-n"

Ah ok I missed that line.

> We might say that more clearly as
>   In the above definition, E[n] refers to the element called
>   E with the id "g-n". So, in Example "n=2" the element
>   hierarchy from the root to the rect is svg[g-2], g[g-1],
>   g[g-0] and rect[elt].
> Would that be clearer? SVG Tiny 1.2 does not allow nested svg elements,
> so the closest ancestor *is* also the outermost one. The distinction
> will be important for SVG Full though, which does allow nested svg
> elements.

Ok.  The above text seems clear to me.  I think the main thing though
was that I jumped in to section 7.7.5 and missed the g[n] syntax


  e-mail : cam (at) mcc.id.au    	icq : 26955922
     web : http://mcc.id.au/	        msn : cam-msn (at) aka.mcc.id.au
  office : +61399055779		     jabber : heycam (at) jabber.org
Received on Thursday, 28 April 2005 13:18:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:02 UTC