Re: [Inkscape-devel] RE: [ inkscape-Bugs-973768 ]letterspacingbroken
Remember that Inkscape isn't only a visual editor, it's a structural editor too.
I don't see the connection with inheritance. If we introduce a non-standard property, it needs to be at least limited and predictable. Making it inherited will give it a degree of unwelcome unpredictability while not providing any significant advantage.
And besides, even if Inkscape "isn't only a visual editor", this does not apply to -inkscape-face. This is a purely visual property which results from the user _seeing_ some font and deciding that it's good. It makes little sense to set this property when editing CSS offline; for that, normal CSS properties are usually better.
IOW, -inkscape-face should take precedence if it matches the normal CSS-specified font closely enough; otherwise it is ignored.
Yes, that it what I have in mind, and ignoring -inkscape-face on mismatch is OK too if accompanied by a warning (this is going to be an exceptional situation anyway, never affecting most users). But I don't see why we must make it inherited.
_________________________________________________________________ http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI...
On Sun, 2004-06-20 at 00:24, bulia byak wrote:
Remember that Inkscape isn't only a visual editor, it's a structural editor too.
I don't see the connection with inheritance. If we introduce a non-standard property, it needs to be at least limited and predictable. Making it inherited will give it a degree of unwelcome unpredictability while not providing any significant advantage.
Aren't there some fonts which can only be specified via this means? (i.e. the standard CSS properties aren't fine-grained enough?) People are going to want to use it for that purpose if that is the case.
IOW, -inkscape-face should take precedence if it matches the normal CSS-specified font closely enough; otherwise it is ignored.
Yes, that it what I have in mind, and ignoring -inkscape-face on mismatch is OK too if accompanied by a warning (this is going to be an exceptional situation anyway, never affecting most users). But I don't see why we must make it inherited.
Can you give me some specific examples of situations where inheritance would cause problems?
On the other hand, if it's not being inherited, I think it should be an XML attribute rather than a CSS property. CSS doesn't have "real" namespaces, so introducing non-standard CSS properties is slightly more evil, IMO.
-mental
participants (2)
-
bulia byak -
MenTaLguY