Search results

Jump to navigation Jump to search

Page title matches

  • ...more generally break compatibility with implementations that don't honour CSS <tt>style</tt> attributes). ...e document in <tt>libxml</tt> form if we want to use <tt>libcroco</tt> for CSS selectors.
    6 KB (1,063 words) - 12:28, 11 August 2017

Page text matches

  • ...ndent implementations of feature before final publication. Having Inkscape support these features not only will provide one of the implementations but it demo ...properties. It is also important that, until SVG 2 is widely supported, we support export to SVG 1.1 or clearly mark that a feature is supported only by SVG 2
    6 KB (867 words) - 13:53, 14 February 2017
  • ...a broader spectrum of styles than CSS can support using these properties. Support for "non-standard" styles is available by using '@font-face' rules that lin ...ed out of a file (or even encoded within the SVG file itself). Adding this support to Pango would be quite a bit of work. Inkscape can, however, still benefit
    4 KB (632 words) - 15:29, 20 July 2017
  • Our font rendering stack now includes support for font variations (harfbuzz (1.4), pango (1.41.1), freetype (2.8/2.9). * [https://drafts.csswg.org/css-fonts-4/#propdef-font-variation-settings CSS Fonts Level 4 'font-variation-settings' property]
    5 KB (699 words) - 20:46, 23 March 2018
  • Improving Inkscape support for internationalized/multi-lingual SVG === Read support ===
    5 KB (878 words) - 22:14, 29 April 2015
  • ...the designer intended. For this reason, SVG defaults to sRGB. Likewise, CSS supports only sRGB. As a working space for artwork not targeted exclusivel And then there are [http://www.ps.missouri.edu/PS2/support/TutorialFolder/ColorTutorial/ColorTutorial2.html spot colors]. Many designe
    7 KB (1,177 words) - 02:35, 9 January 2018
  • : <i>Tests color profile support. Hopefully the Little CMS work should address this: see [[InkscapeColor]]. ...e only relevant to Inkview; Inkscape interaction is inevitably oriented to support editing. These tests are done against Inkscape however, hence the failures.
    9 KB (1,126 words) - 02:09, 18 June 2007
  • : <i>Tests color profile support. Hopefully the lcms work should address this: see [[InkscapeColor]].</i> === CSS (not yet supported) ===
    10 KB (1,178 words) - 12:21, 11 January 2010
  • ...more generally break compatibility with implementations that don't honour CSS <tt>style</tt> attributes). ...e document in <tt>libxml</tt> form if we want to use <tt>libcroco</tt> for CSS selectors.
    6 KB (1,063 words) - 12:28, 11 August 2017
  • * png support through [[GdkPixBuf]] : <i>What's wanted in particular? Certainly inkview already support png images.</i>
    2 KB (396 words) - 20:51, 8 May 2012
  • ...provide a natural fallback mechanism that works with SVG 1.1. It relies on CSS properties applied to the <text> element to define which shapes to fill. ...synthesize bold and italic fonts. This is disabled except for the generic CSS faces ('sans-serif', 'serif', etc.).
    6 KB (1,047 words) - 19:40, 2 August 2017
  • : <i>Tests color profile support. Hopefully the Little CMS work should address this: see [[InkscapeColor]]. === CSS ===
    9 KB (1,104 words) - 15:47, 20 April 2007
  • ...e should be too as they correspond to CSS properties (but Inkscape doesn't support these properties yet).
    2 KB (303 words) - 09:25, 25 October 2019
  • * Better PS/[[EPS]] Export: <nowiki>PostScript</nowiki> level 3 gradient support, better text handling, and a command line option for batch export are in th * Better SVG/[[CSS]] Compliance: Notably, internal CSS stylesheets are now supported (read-only).
    4 KB (667 words) - 11:31, 11 January 2010
  • * Better PS/[[EPS]] Export: <nowiki>PostScript</nowiki> level 3 gradient support, better text handling, and a command line option for batch export are in th * Better SVG/[[CSS]] Compliance: Notably, internal CSS stylesheets are now supported (read-only).
    4 KB (660 words) - 12:03, 11 January 2010
  • ...phics programs, EPS is currently much more common. Inkscape's current EPS support is flakey and poorly maintained. The plan is to switch to use of Scribus' This will involve modifying the grid code to support the ability to have multiple kinds of grids, implementing at least 3 new gr
    13 KB (2,023 words) - 19:25, 29 February 2012
  • ...nge and <code>.success</code> is green. The default colors can be set in a CSS file in the theme's folder. Inside this file also there is <code>.base</co ## Open the file <code>highlights.css</code> in your new <code>Super Cool Icons</code> folder with your favorite
    7 KB (1,204 words) - 12:15, 20 September 2022
  • == Project infrastructure and platform support == * Full SVG viewbox support
    9 KB (1,393 words) - 12:16, 11 March 2023
  • ...to produce more reliable software and faster bug fixes, as well as improve support for OS X. ...nkscape and the graphics it generates highly accessible including superior support for screen readers and multi-language files.
    9 KB (1,520 words) - 14:55, 15 June 2016
  • ...f the discussion in two wiki pages: [[Accessible Graphics]] and [[Language Support]]. See also * [https://bugs.launchpad.net/inkscape/+bug/1249423 Bug #1249423 "Properly support the <switch> element and the "systemLanguage" attribute"].
    11 KB (1,652 words) - 14:55, 15 June 2016
  • ...rness/full-struct-cond-03-t.html struct-cond-03-t] : {{unknown}} - DOM support === Style sheets (CSS) ===
    38 KB (4,832 words) - 13:35, 29 October 2008

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)