Re: [SVG1] 0missions, typos and (likely) errors

Hi JJ,

Thanks for your detailed checking and apologies for the 
late reply. Comments inline.

On Mon, 04 Mar 2002, J.J.SOLARI wrote:

> Hello,
> 
> In translating the SVG1 specification (into French), I found some
> omissions and typos, and (likely) some errors. Here they are:
> 
> 
> In pages :
> 
> ================================
> 
> <http://www.w3.org/TR/2001/REC-SVG-20010904/coords.html>
> 
> In the very last sentence: ... If the given attribute or property is not
> currently being animated, contains the same
> 
> the expression: "...value as'baseVal'." is missing at the end of the
> sentence.

Yes. Fixed.

> 
> ================================
> 
> <http://www.w3.org/TR/2001/REC-SVG-20010904/paths.html#InterfaceSVGAnimatedPathData>
> 
> In Interface SVGAnimatedPathData, definition of normalizedPathSegList
> attribute:
> 
> [...]
> 
> readonly SVGPathSegList normalizedPathSegList
> 
> Provides access to the base (i.e., static) contents of the d attribute
> in a form where all path data commands are expressed in terms of the
> following subset of SVGPathSeg types: SVG_PATHSEG_MOVETO_ABS (M),
> SVG_PATHSEG_LINETO_ABS (L), SVG_PATHSEG_CURVETO_CUBIC_ABS (C) and
> SVG_PATHSEG_CLOSEPATH (z). Thus, if the d attribute has an "absolute
> moveto (M)" and an "absolute arcto (A)" command, then pathSegList will
> have one SVG_PATHSEG_MOVETO_ABS entry followed by a series of
> *SVG_PATHSEG_ARC_ABS* entries which approximate the arc. This alternate
> representation is available to provide a simpler interface to developers
> who would benefit from a more limited set of commands.
> 
> [...]
> 
> Since the values are expressed in the limited subset above, the
> expression "...followed by a series of *SVG_PATHSEG_ARC_ABS* entries..."
> doesn't make sense. Shouldn't it be [SVG_PATHSEG_LINETO_ABS] instead?

Not sure if it should be LINETO or CURVETO_CUBIC, but it's definitely
wrong..

> ================================
> 
> <http://www.w3.org/TR/2001/REC-SVG-20010904/shapes.html#InterfaceSVGCircleElement>
> 
> In InterfaceSVGCircleElement:
> 
> The SVGCircleElement interface corresponds to the *'rect'* element.
> 
> should be: The SVGCircleElement interface corresponds to the ['circle']
> element.

Yes. Fixed.

> 
> ================================
> 
> <http://www.w3.org/TR/2001/REC-SVG-20010904/text.html>
> 
> In10.13.3: Text on a path layout rules, last paragraph, third sentence
> beginning with "When the inline-progression-direction
> is *horizontal*..."
> 
> should be: "When the inline-progression-direction is [vertical]..."
> 

Yes. Fixed.

> =================================
> 
> <http://www.w3.org/TR/2001/REC-SVG-20010904/filters.html>
> 
> In 15.12 Filter primitive 'feComposite':
> 
> Image of the exemple doesn't correspond with SVG code (at least with
> Adobe SVGViewer 3.0, or Opera built-in SVG viewer)
> For a comparison, see a screenshot at:
> <http://www.yoyodesign.org/tmp/svg1/feComposite_with_viewer.png>
> 
> 
> In 15.19 Filter primitive 'feMerge': first line, "This filter primitive
> composites input image layers on top of each other using the *over*
> operator"
> 
> should be: "... using the [in] operator ... "
> 
> should be: the *in* operator
> 

I believe "over" (as in src_over, the painters default) is correct.


> ==================================
> <http://www.w3.org/TR/2001/REC-SVG-20010904/linking.html#SVGFragmentIdentifiers>
> 
> In 17.2.2 SVG fragment identifiers: second paragraph, first bullet, last
> sentence : ... (The bare name form of addressing *#MyElement* is
> equivalent to the XPointer formulation #xpointer(id('MyView')).)
> 
> should be: (The bare name form of addressing *#MyView* is equivalent to
> the XPointer formulation #xpointer(id('MyView')).)

Yes. Fixed.

> 
> 
> ==================================
> <http://www.w3.org/TR/2001/REC-SVG-20010904/fonts.html>
> 
> In 20.2 Overview of SVG Fonts: last exemple demonstrating referenced
> font: ... <text x="100" y="100"
>            style="font-family: 'Super Sans'; font-weight:normal;
>              font-style: italic">*Text using embedded font*</text> ...
> 
> should be: ... <text x="100" y="100"
>            style="font-family: 'Super Sans'; font-weight:normal;
>             font-style: italic">Text using *referenced* font</text> ...
> 

Yes. Fixed.

Dean

Received on Thursday, 18 April 2002 10:07:41 UTC