Font Specification Implementation
Bug #169973 reported by
Gail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
- New attribute in an object's style string called
-inkscape-
- This will be useful when we can support fonts that don't fit into the
confines of CSS (if either pango enhances their PangoFontDescri
structure, or we can get around its limitations)
- Framework in place to separate font families from their "styles" (faces)
in the text and font dialog - need only the code that does the actual
separation
- Text and Styles dialog shows only fonts it can handle
Changed in inkscape: | |
importance: | Undecided → Wishlist |
milestone: | none → 0.46 |
status: | New → Triaged |
tags: |
added: styles svg text removed: other |
tags: |
added: fonts removed: text |
To post a comment you must log in.
Originator: NO
First of all, why do you call the attribute -inkscape- font-specificat ion? font-specificat ion, otherwise it will be invalid SVG. This is also
it is not standard SVG and therefore must be in Inkscape namespace:
inkscape:
what Miklos used in his PDF import code.
I think you chose this name because nonstandard CSS properties must start font-specificat ion CSS property, we must have it named font-specificat ion when written as an attribute.
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-
inkscape:
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.