On 7/19/07, Gail Banaszkiewicz <gbanaszk@...1686...> wrote:
If this is true, and I'm not missing something (which is certainly possible), why the need for the Inkscape: attribute?
Of course, all this changes if we update our UI to show actual font families (like just Arrus and BernhardMod), and all available styles of that family in another column.
That (UI) is one reason, and it's indeed a reason because all other design software does it the right way - family separate from all fonts within the family. We should do the same, or at least try to.
And the other reason is that we must still strive to provide an as-faithful-as-possible CSS specification for the font, even if we (Inkscape) won't use it. And that means, again, storing family name separately and the weight, style etc approximated by CSS properties.