© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
We should fix the problems with the style selector and with the Text and Font dialog, status bar, and Text-Tool controls. Going back to "Sans" I don't think is a valid option.
A little history. At one point the default font was Bitstream Vera Sans. This font was likely only installed on Linux systems and caused problems for those who didn't have the font installed. I changed it a couple of years ago to Sans based on what Pango does (incorrectly, I now believe). This causes problems for those viewing the SVG outside of Inkscape since there is no font (that I know of) simply called Sans. Pango will match Sans to the generic CSS font name "sans-serif" and thus use the CSS "sans-serif" fall-back font so viewing old Inkscape files shouldn't be a problem.
A related problem is that Pango is happy to manufacture oblique/italic font faces from regular fonts by slewing the regular face. This is probably valid for content viewers but probably not for content creators (e.g. Inkscape). It will also happily list bold font faces where none actually exist (but does not manufacture a bold face). It would be better if we could generate a list of font faces that are actually installed on a users computer. (Note, the creation of oblique/italic/bold font faces where none exist is probably a configuration option, at least on Linux; see: /etc/fonts/
A final problem that we should address is that Inkscape wraps a font list with single quotes. This breaks the use of font lists in other SVG renders. Single quotes should be put around individual fonts if the font name contains a space.
CSS Font specification (which SVG 1.1 references):
http://