In other words, Inkscape should strictly adhere to the SVG standard, or perhaps offer a way to export without Inkscape-specific extensions, or warn users when inserting Inkscape-specific extensions. Once we decide to support all the weirdness there is This is a bit like Adobe illustrator and its AI files: tons ofĬrap needed for an editor but not really an 'eps' file for which there Right-click and select INSTALL FOR ALL USERS.
(you can copy this and past into explorer just change your user name) Select all fonts. A salient quote from ConTeXt's lead developer: Open Explorer (This computer) Go to: C:\Users\ '''My USER Name''' \AppData\Local\Microsoft\Windows\Fonts. For example, Inkscape handles DejaVu Sans with 9 font variants properly.Īdditionally, this Inkscape-specific property is known to break ePublisher by WebWorks and Apache Batik it is ignored by ConTeXt's SVG/MetaPost conversion. Note, a lot of work has taken place to better handle font variants inside Inkscape since this property was added (see original bug report). The CSS Fonts Module Level 3 offers an alternative way of handling font variants where the variants are kept together in the same font file.
While in theory it could be useful for tracking non-CSS compatable font variants, in practice it just duplicates information already stored in the various font properties while making Inkscape code more complicated and Inkscape SVG output bigger. The -inkscape-font-specification property should be removed.
0 kommentar(er)
