Search results
Jump to navigation
Jump to search
- *[[XSLT]]384 bytes (59 words) - 04:13, 1 April 2011
- ...T.''' This implementation is done in the XSLT language, and uses libxml's XSLT parser that is already linked with Inkscape. ...s (i.e. there is no implementation of Inkscape::Extension::Implementation::XSLT::effect(), only ::open() and ::save() )5 KB (846 words) - 19:54, 3 February 2023
- Then commit all changed files (XML, HTML, SVG, XSLT). Before a new release, copy the latest HTML file to inkscape_web/doc so it812 bytes (139 words) - 05:43, 27 July 2016
- [[Dia]] makes use of XSLT which hopefully [[Inkscape]] could share.2 KB (301 words) - 13:00, 19 November 2009
- Initial XSLT file done. Initial unit and global tests done. This export extension uses the XSLT extension system (already used by XAML export).11 KB (1,653 words) - 13:23, 18 January 2011
- ...ml files (which are xml files). These could be translated to/from SVG via XSLT.3 KB (441 words) - 15:54, 27 February 2008
- * [http://www.linuxjournal.com/article/9283 Use Inkscape and XSLT to Create Cross-Platform Reports and Forms] by Chad Files for Linux Journal16 KB (2,200 words) - 09:30, 4 August 2016
- *Rewrite the '''XAML importer''' in Python (currenly XSLT) to match the capabilities of the new XAML exporter (i.e. support for diffe20 KB (3,131 words) - 10:10, 17 March 2024
- ...ly, and in places where Inkscape isn't even installed - all you need is an XSLT processor. This would be highly cool since some of the programs (I'm lookin28 KB (4,555 words) - 13:06, 31 March 2012
- == XSLT effects == * '''XSLT''' is now supported for input, output and effect extensions. This is used120 KB (19,789 words) - 21:12, 2 May 2021
- == XSLT effects == * '''XSLT''' is now supported for input, output and effect extensions. This is used109 KB (18,126 words) - 14:39, 5 August 2016