bulia byak wrote:
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.
Ok, good, I'm glad that I'm on the right page here. It looks like pango does not give the proper family name (please feel free to tell me otherwise if you know it is supposed to), so we will either need to find something else that can do this, or implement it ourselves. I assume the latter makes the most sense. I believe this is, relatively speaking, the only complex aspect of this task.
Thanks, Gail