Comment 1 for bug 169973

Originator: NO

First of all, why do you call the attribute -inkscape-font-specification?
it is not standard SVG and therefore must be in Inkscape namespace:
inkscape:font-specification, otherwise it will be invalid SVG. This is also
what Miklos used in his PDF import code.

I think you chose this name because nonstandard CSS properties must start
with - and cannot contain a colon. But, why do we need this value as a CSS
property at all? You can still store its value in SPStyle without it being
part of style="" string (I think). Or at least, if we do use
-inkscape-font-specification CSS property, we must have it named
inkscape:font-specification when written as an attribute.

Also, why did you remove support for the font proprty in SPStyle? It is
standard CSS and we must support it, it's actually different from the new
inkscape font spec property. Currently it's not well supported, but it's no
reason to remove it.