path data bug to be fixed in 2.0?

In the example at http://cs.sru.edu/~ddailey/svg/alphabetcomma.svg  all
browsers (real and hypothetical) except for Firefox render all four shapes
the same way. Firefox, (no doubt detecting that I am trying to draw glyphs
in SVG -- a real non-non in FF-land as I understand it)  on the other hand,
is unhappy with the extra commas in my path's d attribute:

 

d=". 300 400, C 300 600, . "

 

I know I shouldn't have put the commas there and my wrists are stinging
already, so I offer a solution at
http://cs.sru.edu/~ddailey/svg/alphabet.svg that removes the extra commas
before the path subcommands

 

I seem to recall running into this once before (I often like to separate my
coordinate pairs from one another by commas, and then for fun, I begin
moving them about and forget to tidy up all the loose ends, but heck it
works in all browsers save one!). And consistent with that recollection, I
remember the good folks at Mozilla explaining that it was the other browsers
that did it wrong - they merely followed the spec. Well, should this be the
case, then I think the spec is at fault.

 

Apologies if this is just a bug in FF, but usually they are quite fastidious
in their reading of the spec!

 

Cheers

David