Search results
Jump to navigation
Jump to search
Page title matches
- 1 KB (209 words) - 16:32, 5 January 2012
Page text matches
- #redirect[[Spec preferences unweirdification]]46 bytes (4 words) - 17:06, 5 January 2012
- SVG Fonts are defined in section 20 of the SVG 1.1 spec: http://www.w3.org/TR/SVG11/fonts.html221 bytes (37 words) - 21:53, 25 March 2008
- ** I am still working on getting us on the spec page --rejon1,006 bytes (144 words) - 11:01, 8 June 2007
- https://blueprints.launchpad.net/inkscape/+spec/sort-out-xara-xtreme-functions This spec provides a listing of functionality in Xara but not in Inkscape. It also i715 bytes (96 words) - 10:20, 31 March 2012
- * SVG's animation spec855 bytes (107 words) - 07:46, 6 January 2012
- == Functional spec ==4 KB (674 words) - 10:17, 31 March 2012
- ...st) ambiguous as to whether coordinates can contain units, whereas the SVG spec disallows units. (The [[OpenDocument]] spec has a typo saying svg:rx twice instead of "svg:rx and svg:ry".)9 KB (1,392 words) - 02:33, 22 January 2006
- As a first glance without looking much at either the spec or inkscape Looking back at the full SVG (1.1) spec, is Inkscape already able to claim to be a "[http://www.w3.org/TR/SVG11/con4 KB (575 words) - 15:36, 20 April 2007
- ...hree to a certain cap would require the other two change too since the svg spec doesn't allow multiple caps. Apart from this incongruity the change I belie2 KB (317 words) - 03:38, 8 May 2013
- Just supporting SVG Fonts as per spec is not much fun. Designing fonts in Inkscape should be much more than just2 KB (289 words) - 23:57, 6 March 2011
- from a spec, and then work on implementing the code to pass the unit test; this is the In spec testing, the application is run against various input cases and caused to g4 KB (671 words) - 22:42, 13 February 2011
- https://blueprints.launchpad.net/inkscape/+spec/guides-improvement * This spec adds basic managing operations such as add, remove, copy, visible/invisible6 KB (960 words) - 10:48, 31 March 2012
- ...tylesheets interact the same way as in HTML; the relevant part of the HTML spec is http://www.w3.org/TR/html4/present/styles.html#h-14.3.6 KB (1,063 words) - 12:28, 11 August 2017
- https://blueprints.launchpad.net/inkscape/+spec/crash-recovery So I'm trying to design a dialog which takes care of these problems. This spec also suggests how the files should be managed at the point of crashing and3 KB (451 words) - 10:15, 31 March 2012
- ** Choice of PDF spec. (PDF/X-1a, PDF/X-3)2 KB (351 words) - 00:10, 20 December 2013
- ** [http://www.nongnu.org/chmspec/latest/ unofficial CHM spec]4 KB (661 words) - 22:14, 3 July 2007
- ...text layout using code written for the never-adopted "flowed-text" SVG1.2 spec. There are several problems with this code:4 KB (605 words) - 03:04, 4 July 2012
- ...ype="CSS"</code>). [http://www.w3.org/TR/SVG11/animate.html#TargetElement (SPEC)] ...quite intuitive [http://www.w3.org/TR/SVG11/animate.html#ClockValueSyntax (SPEC)]. Depending on the combination of those 3 attributes, the interval of time15 KB (2,295 words) - 08:56, 28 February 2011
- * For title/desc, the default *would* have a lang attribute (note, SVG 2 spec currently uses `lang` not `xml:lang`), and would be the *first* such child5 KB (878 words) - 22:14, 29 April 2015
- ...;</code> elements are allowed anywhere in an SVG document according to the spec, but Inkscape seems to have some trouble if they are not in the <code><d6 KB (937 words) - 17:40, 15 January 2017