SVG2

SVG 2 Planning

SVG 2 will offer many things to Inkscape:

• Mesh Gradients
• Hatch Fills
• Arbitrary stroke/fill/marker order
• Arcs line join
• Auto-flowed text
• New blending and compositing modes.
• Use of blending and compositing outside of filters.
• Marker inheriting stroke color, etc.
• Etc.

It is important that Inkscape implement these features in a timely fashion. Not only will it be a benefit to our users... but it is a necessary step to insuring that these features remain in SVG 2. The W3C specification process requires at least two independent implementations of feature before final publication. Having Inkscape support these features not only will provide one of the implementations but it demonstrates to others that there is serious interest in these features.

We do need to be careful, though, to avoid the Flowed Text of SVG 1.2 debacle. Until the SVG 2 specification (or relevevant CSS specification) is in the final stages of adoption, each new feature must be developed in the 'inkscape' name space; that is to say, the '-inkscape-' prefix must be used for new elements, attributes, and 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.

Many SVG 2 features can be supported internally as SVG 2. For example, Inkscape currently uses 1-stop gradients for color palettes. On reading in, a one-stop gradient can be converted to a <solidColor> element. On writing out, if SVG 1.1 output is selected, the <colorColor> element can be converted back to a 1-stop gradient. An SVG 2 <hatch> element can be converted to a <pattern> large enough to cover the fill area. SVG 2 flowed text provides a natuaral fallback for SVG 1.1 renderers. A tab in the Preferences dialog could handle fine grain control of which SVG 2 features should be converted.

Note, no browser seems to handles the <switch> element correctly so we should not rely on this feature.

Resources

There may be multiple versions of each specification, each represents a particular snap-shot during specification writing. In order of maturity:

• Editor's Draft: The latest version not endorsed by the working group, frequent changes.
• Working Draft: The latest version endorsed by the working group.
• Last Call
• Candidate Recommendation
• Proposed Recommendation
• Recommendation

See the CSS Current Work page for more details. During the writing process, the top of each specification has links to the various versions.

SVG 2 Specification

• SVG 2 Working Draft, SVG 2 Editor's Draft.

CSS Specifications (except Text):

• CSS Animation Working draft, some support in browsers.
• CSS Color Module Level 3 Recommendation, good browser support.
• Compositing and Blending Level 1 Last Call, start of support in browsers.
• Filter Effects Module Level 1 Mostly the same as SVG 1.1, good browser support.
• CSS Masking Module Level 1 Last Call.
• CSS Transforms Module Level 1 Working Draft, some browser support.
• CSS Transitions Working Draft, some browser support.
• Web Animations (Unified SMIL, CSS Animation model) Editor's Draft, initial work.

CSS Specifications: Text

• CSS Fonts Module Level 3 Candidate Recommendation
• CSS Text Decoration Module Level 3 Candidate Recommendation
• CSS Text Module Level 3 Last Call
• CSS Writing Modes Last Call
• CSS Shapes Module Level 1 Last Call
• CSS Shapes Module Level 2 Editor's Draft (only for 'line-width').
• CSS Basic User Interface Module Level 3 Working Draft
• CSS Exclusions Module Level 1 Working Draft
• CSS Line Layout Module Level 3 Editor's Draft (Note: Working Draft is from 2002 and should be ignored)