Interesting question.  Off hand it seems to me that you should put it in SPStyle if it is CSS information, but Richard could probably comment on that better.

Also, are you able to make use of (after expanding its capabilities) the font-specification attribute I had added to the style? It would be cool if you could, because it would help what I was doing too.  Now that you've been working on it for a while, perhaps you have a better idea of the answer to this question?

(By the way I'm much for free now than before, since I'm starting into thesis time.  Should be able to contribute more now!)

Gail

On Mon, May 12, 2008 at 12:16 AM, Felipe Sanches <felipe.sanches@...400...> wrote:
During this weekend I have spent some time coding parameter loading
for the font-face tag. Then, after commiting
(http://inkscape.svn.sourceforge.net/viewvc/inkscape?view=rev&revision=18594),
I noticed that style.{cpp,h} contain code that partially implements
the same thing. So, I supose that I will have to revert what I did and
use face->style to access the content of those attributes (such as
font-style, font-variant, font-stretch, etc).

Although, I have also noticed that not every attributes described on
CSS2 spec, section 15 (Fonts) are implemented. For example, none of
the attributes on section 15.3.6 ('panose-1', 'stemv',
'stemh', 'slope', 'cap-height', 'x-height', 'ascent', and 'descent')
seem to be implemented. What should I do? Should I implement them in
SPStyle? Or should I implement it on SPFontFace ?

Juca