Jump to content

SVG

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Lucideer (talk | contribs) at 18:42, 3 March 2010 (Undid revision 347461006 by 82.252.200.234 (talk) - removing notable and relevant references, obvious POV to all this user's edits). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

"SVG" redirects here. For other uses, see SVG (disambiguation).
Scalable Vector Graphics
Filename extension
.svg, .svgz
Internet media type
image/svg+xml[1][2]
Developed byWorld Wide Web Consortium
Initial release4 September 2001 (2001-09-04)
Latest release
Tiny 1.2
22 December 2008; 16 years ago (2008-12-22)
Type of formatvector image format
Extended fromXML
Free format?Yes
Websitew3.org/Graphics/SVG/
Scalable Vector Graphics
This image illustrates the difference between bitmap and vector images. The bitmap image is composed of a fixed set of dots, while the vector image is composed of a fixed set of shapes. In the picture, scaling the bitmap reveals the dots and scaling the vector image preserves the shapes.

Scalable Vector Graphics (SVG) is a family of specifications of an XML-based file format for describing two-dimensional vector graphics, both static and dynamic (i.e. interactive or animated).

The SVG specification is an open standard that has been under development by the World Wide Web Consortium (W3C) since 1999.

SVG images and their behaviours are defined in XML text files. This means that they can be searched, indexed, scripted and, if required, compressed. Since they are XML files, SVG images can be created and edited with any text editor, but specialized SVG-based drawing programs are also available.

All major modern web browsers except Microsoft Internet Explorer (IE) support and render SVG markup directly.[3]

Overview

SVG has been in development since 1999 by a group of companies within the W3C after the competing standards Precision Graphics Markup Language(PGML) (developed from Adobe's PostScript) and Vector Markup Language(VML) (developed from Microsoft's RTF) were submitted to W3C in 1998. SVG drew on experience from the designs of both those formats.

SVG allows three types of graphic objects:

Graphical objects can be grouped, styled, transformed, and composited into previously rendered objects. SVG does not directly support z-indices[4] that separate drawing order from document order for overlapping objects, unlike some other vector markup languages like VML. Text can be in any XML namespace suitable to the application, which enhances searchability and accessibility of the SVG graphics. The feature set includes nested transformations, clipping paths, alpha masks, filter effects, template objects and extensibility.

Since 2001, the SVG specification has been updated to version 1.1 (current Recommendation) and 1.2 (still a Working Draft). The SVG Mobile Recommendation introduced two simplified profiles of SVG 1.1, SVG Basic and SVG Tiny, meant for devices with reduced computational and display capabilities. SVG Tiny later became an autonomous Recommendation (current version 1.2) and the basis for SVG 1.2. In addition to these variants and profiles, the SVG Print specification (still a Working Draft) contains guidelines for printable SVG 1.2 and SVG Tiny 1.2 documents.

The Canvas element in HTML5 provides a somewhat different approach to rendering dynamic graphics in HTML. But it doesn't allow for static rendering, and drawn elements are not identifiable in a DOM-like way.

Printing

While being primarily designated as a vector graphics markup language, the specification is also designed with the basic capabilities of a page description language (PDL), like Adobe's PDF. It contains provisions for rich graphics, and is also compatible with CSS for styling purposes. It is unlike XHTML and XSL-FO, whose primary purpose is communication of content, not presentation, and so which specify objects to be displayed but not where to place such objects. Conversely SVG is an ideal PDL for print-orientated uses, as it contains all the functionality required to place each glyph and image in a chosen location on the final page.[5] A much more print-specialized subset of SVG (SVG Print, authored by Canon, HP, Adobe and Corel) is currently a W3C Working Draft. [6]

Scripting and animation

Main article: SVG animation

SVG drawings can be dynamic and interactive. Time-based modifications to the elements can be described in SMIL, or can be programmed in a scripting language (e.g., ECMAScript or JavaScript). The W3C explicitly recommends SMIL as the standard for animation in SVG,[7] however it is more common to find SVG animated with ECMAScript because it is a language that many developers already understand, and it is more compatible with existing renderers. A rich set of event handlers such as onmouseover and onclick can be assigned to any SVG graphical object.

Compression

SVG images, being XML, contain many repeated fragments of text and are thus particularly suited to compression by gzip, though other compression methods may be used effectively. Once an SVG image has been compressed by gzip it may be referred to as an "SVGZ" image, with the corresponding filename extension. The resulting file may be as small as 20% of the original size.[8]

Development history

SVG was developed by the W3C SVG Working Group starting in 1998, after Macromedia and Microsoft introduced VML whereas Adobe Systems and Sun Microsystems submitted a competing format known as PGML. The working group was chaired by Chris Lilley of the W3C.

  • SVG 1.0 became a W3C Recommendation on 4 September 2001.[9]
  • SVG 1.1 became a W3C Recommendation on 14 January 2003.[10] The SVG 1.1 specification is modularized in order to allow subsets to be defined as profiles. Apart from this, there is very little difference between SVG 1.1 and SVG 1.0.
    • SVG Tiny and SVG Basic (the Mobile SVG Profiles) became W3C Recommendations on 14 January 2003. These are described as profiles of SVG 1.1.[11]
  • SVG Tiny 1.2 became a W3C Recommendation on 22 December 2008.[12]
  • SVG Full 1.2 is a W3C Working Draft. SVG Tiny 1.2 was initially released as a profile, and later refactored to be a complete specification, including all needed parts of SVG 1.1 and SVG 1.2. SVG 1.2 Full adds modules onto the SVGT 1.2 core.
  • SVG Print adds syntax for multi-page documents and mandatory color management support.

Mobile profiles

Because of industry demand, two mobile profiles were introduced with SVG 1.1: SVG Tiny (SVGT) and SVG Basic (SVGB). These are subsets of the full SVG standard, mainly intended for user agents with limited capabilities. In particular, SVG Tiny was defined for highly restricted mobile devices such as cellphones, and SVG Basic was defined for higher-level mobile devices, such as PDAs.

In 2003, the 3GPP adopted SVG Tiny as the mandatory vector graphics media format for next-generation phones. SVGT is the required vector graphics format and support of SVGB is optional for Multimedia Messaging Service(MMS) and Packet Switch Stream(PSS).[13] [14][15] It was later added as required format for vector graphics in 3GPP IP Multimedia Subsystem (IMS).[16] Neither mobile profile includes support for the full DOM, while only SVG Basic has optional support for scripting, but because they are fully compatible subsets of the full standard most SVG graphics can still be rendered by devices which only support the mobile profiles.[17]

SVGT 1.2 adds a microDOM (μDOM), allowing all mobile needs to be met with a single profile.

Functionality

The SVG 1.1 specification defines 14 important functional areas or feature sets:[10]

Paths
Simple or compound shape outlines drawn with curved or straight lines can be filled in or outlined (or used as a clipping path) and are expressed in a highly compact coding in which, for example, M (from 'move to') precedes the initial numeric X and Y coordinates and L (line to) will precede a subsequent point to which a line should be drawn. Further command letters (C, S, Q, T and A) precede data that is used to draw various Bézier and elliptical curves. Z is used to close a path. In all cases, absolute coordinates follow capital letter commands and relative coordinates are used after the equivalent lower-case letters.[18]
Basic Shapes
Straight-line paths or paths made up of a series of connected straight-line segments (polylines), as well as closed polygons, circles and ellipses can be drawn. Rectangles and round-cornered "rectangles" are other standard elements.[19]
Text
Unicode character text included in an SVG file is expressed as XML character data. Many visual effects are possible, and the SVG specification automatically handles bidirectional text (as when composing a combination of English and Arabic text, for example), vertical text (as Chinese was historically written) and characters along a curved path (such as the text around the edges of the Great Seal of the United States).[20]
Painting
SVG shapes can be filled and/or outlined (painted with a color, a gradient or a pattern). Fills can be opaque or have various degrees of transparency. "Markers" are end-of-line features, such as arrowheads, or symbols which can appear at the vertices of a polygon.[21]
Color
Colors can be applied to all visible SVG elements, either directly or via the 'fill', 'stroke' and other properties. Colors are specified in the same way as in CSS2, i.e. using names like black or blue, in hexadecimal such as #2f0 or #22ff00, in decimal like rgb(255,255,127) or as percentages of the form rgb(100%,100%,50%).[22]
Gradients and Patterns
SVG shapes can be filled or outlined with solid colors as above, or with color gradients or with repeating patterns. Color gradients can be linear or radial (circular), and can involve any number of colors as well as repeats. Opacity gradients can also be specified. Patterns are based on predefined raster or vector graphic objects, which can be repeated in x and/or y directions. Gradients and patterns can be animated and scripted.[23]
Since 2008, there has been discussion[24][25] among professional users of SVG that either gradient meshes or preferably diffusion curves could usefully be added to the SVG specification. It is said that a "simple representation [using diffusion curves] is capable of representing even very subtle shading effects"[26] and that "Diffusion curve images are comparable both in quality and coding efficiency with gradient meshes, but are simpler to create (according to several artists who have used both tools), and can be captured from bitmaps fully automatically."[27]
Clipping, Masking and Compositing
Graphic elements, including text, paths, basic shapes and combinations of these, can be used as outlines to define both 'inside' and 'outside' regions that can be painted (with colors, gradients and patterns) independently. Fully opaque clipping paths and semi-transparent masks are composited together to calculate the color and opacity of every pixel of the final image, using simple alpha blending.[28]
Filter Effects[29]
Main article: SVG filter effects
Interactivity
SVG images can interact with users in many ways. In addition to hyperlinks as mentioned below, any part of an SVG image can be made to trigger events representing changes in focus, mouse clicks, scrolling or zooming the image and other pointer, keyboard and document events. Event handlers may start, stop or alter animations and trigger any other scripts in response to these events.[30]
Linking[31]
Main article: XLink
Scripting
All aspects of an SVG document can be accessed and manipulated using scripts in a similar way to HTML. The default scripting language is ECMAScript (closely related to JavaScript) and there are defined Document Object Model (DOM) objects for every SVG element and attribute. Scripts are enclosed in <script> elements. They can run in response to pointer events, keyboard events and document events as required.[32]
Animation
SVG content can be animated using the built-in animation elements such as <animate>, <animateMotion> and <animateColor>. Animation is also possible by manipulating the DOM using ECMAScript, using the scripting language's built-in timers. SVG animation has been designed to be compatible with current and future versions of Synchronized Multimedia Integration Language (SMIL). Animations can be continuous, they can loop and repeat and they can respond to user events, as mentioned above.[33]
Fonts
As with HTML and CSS, text in SVG may reference external font files, such as system fonts. If the required font files do not exist on the machine where the SVG file is rendered, the text may not appear as intended. To overcome this limitation, text can be displayed in an 'SVG font', where the required glyphs are defined in SVG as a font that is then referenced from the <text> element.[34]
Metadata
In accord with the W3C's Semantic Web initiative, SVG allows authors to provide metadata about SVG images. The main facility is the <metadata> element, where the document can be described using Dublin Core metadata properties (e.g., title, creator/author, subject, description, etc). Other metadata schemas may also be used. In addition, SVG defines <title> and <desc> elements where authors can provide further plain-text descriptive material within an SVG image to help indexing, searching and retrieval by a number of means.[35]

Support for SVG in web browsers

September 2011, web browser usage share.
Source: Median values from summary table.
  Internet Explorer (38.9%)
  Firefox (25.0%)
  Google Chrome (20.9%)
  Safari (8.0%)
  Opera (2.7%)
  Mobile browsers (6.7%)

The use of SVG on the web is still limited by the lack of support in Internet Explorer which has more than 58% market share. Even the newest version 8 doesn't support SVGs.[36][37] Many web sites that serve SVG images, for example Wikipedia, also choose to provide the images in a raster format, either automatically by HTTP content negotiation or by allowing the user directly to choose the file.

Native support

As of 2009, all major desktop browsers, and many minor browsers, have some level of SVG support, except for Internet Explorer. Other browsers' implementations are not yet complete; see Comparison of layout engines for further details. As of 2010, only Opera, Safari and Google Chrome supported embedding via the <img> HTML element. Mozilla Firefox and some other browsers that can display SVG graphics currently need them embedding in <object> or <iframe> elements to display them integrated as parts of an HTML webpage.[38] However, SVG images may be included in XHTML pages using XML namespaces.[39]

Tim Berners-Lee, the inventor of the Web, has been critical of Internet Explorer for its failure to support SVG.[40] All currently supported graphical browsers on Linux systems and the Macintosh have implemented some level of SVG support.

  • Opera (since 8.0) has support for the SVG 1.1 Tiny specification while Opera 9 includes SVG 1.1 Basic support and some of SVG 1.1 Full. Since Opera 9.5 has partial SVG Tiny 1.2 support.
  • Browsers based on the Gecko layout engine (such as Firefox, Flock, Camino and SeaMonkey) all have had incomplete support for the SVG 1.1 Full specification since 2005. The Mozilla site has an overview of the modules which are supported in Firefox[41] and of the modules which are in progress in the development.[42] Gecko 1.9, included in Firefox 3.0, adds support for more of the SVG specification (including filters).[43]
  • Browsers based on WebKit (such as Apple's Safari, Google Chrome, and The Omni Group's OmniWeb) have had incomplete support for the SVG 1.1 Full specification since 2006.[44]
  • Amaya has partial SVG support.

There are several advantages to native and full support: plugins are not needed, SVG can be freely mixed with other content in a single document, and rendering and scripting become considerably more reliable.

SVG and Microsoft Internet Explorer

As of 19 March 2009, Internet Explorer 8, the latest release of IE, is the only current major browser not to provide native SVG support. IE requires a plug-in to render SVG content. There are a number of plug-ins available to assist including:

  • Google Chrome Frame from Google can support all web elements supported by WebKit, including SVG 1.0 and partially SVG 1.1.
  • RENESIS Player for Internet Explorer from examotion GmbH, supports SVG 1.1 on IE 6 and 7 and is available for download free of charge.[45]
  • Ssrc SVG Plugin from Savarese Software Research Corporation is a plug-in for rendering SVG in Internet Explorer versions 6, 7, and 8 on Windows XP, Server 2003, Vista, Server 2008, and 7. In addition, the plug-in enables Internet Explorer to load Mozilla XUL applications.[46]
  • Batik, a widely deployed Java plugin[47]
  • Bitflash, an SVG viewer intended for mobile devices, which can be installed as an IE plugin
  • Ikivo, an SVG viewer intended for mobile devices, which can be installed as an IE plugin
  • GPAC, targets SVGT 1.2[48]
  • Adobe SVG Viewer from Adobe Systems plugin supports most of SVG 1.0/1.1. Zooming and panning of the image are also supported to enable viewing of any area of the SVG lying outside the visible area of its containing window, but scrolling is not supported. Adobe SVG Viewer is available for download from Adobe Systems free of charge.[49] However, on 1 January 2009, Adobe Systems discontinued support for Adobe SVG Viewer.[50]
  • Corel SVG Viewer[51](discontinued)

SVG Web[52] is a JavaScript library for Web developers, targeted at Internet Explorer and dependent on the presence of an installed Adobe Flash plugin on the client machine. SVG Web provides partial support for SVG 1.1, SVG Animation (SMIL), Fonts, Video and Audio, DOM and style scripting.[53]

On January 5, 2010, a senior manager of the Internet Explorer team at Microsoft announced on his official blog that Microsoft had just requested to join the SVG Working Group of the W3C in order to "take part in ensuring future versions of the SVG spec will meet the needs of developers and end users," although no plans for SVG support in Internet Explorer were mentioned.[54]

Software and support in applications

Images can be rasterised using a library such as ImageMagick, which provides a quick but incomplete implementation of SVG, or Batik, which implements nearly all of SVG 1.1 and much of SVG Tiny 1.2 but requires the Java Runtime Environment.

  • 3dpaintbrush can export 3D scenes/objects to SVG files.
  • The Batik SVG Toolkit can be used by Java programs to render, generate, and manipulate SVG graphics.
  • Adobe Illustrator supports both the import and export of SVG images. When writing SVG files it has the option to embed a copy of the associated proprietary Illustrator format for later editing. This often results in changes being lost if another editor is used when the file is reopened in Illustrator because it ignores everything but the embedded Illustrator file.
  • Altsoft Xml2PDF allows converting SVG files to PDF, PS, various GDI+ formats.
  • Blender will import SVG graphics as paths.
  • Cairo is a vector graphics based library which can generate SVG. It has bindings for many programming languages including Haskell, Java, Perl, Python, Scheme, Smalltalk and several others.
  • CorelDRAW has an SVG export and import filter.
  • Ecava IntegraXor [55] created SAGE [56] (SCADA Animation Graphic Editor) which allows SVG graphic to be used in SCADA application.
  • The GIMP allows SVG images to be imported as paths or rendered bitmaps.
  • The GNOME project has had integrated SVG support throughout the desktop since 2000.
  • GNU LilyPond can export musical scores to SVG.
  • Go-oo Draw (OpenOffice.org variant) can open and export SVG files.[57]
  • Inkscape is a free software vector graphics program for Linux, Microsoft Windows and Mac OS X that uses SVG as its native image format. Inkscape also contains tools to convert pixel-based graphics to SVG.
  • ItsNat is a Java based web framework with built-in support of native SVG, Adobe SVG Viewer, Renesis, Savarese Ssrc, Batik applet and SVGWeb plugins.
  • Mappetizer is a commercial converter for spatial data to SVG.
  • Microsoft Visio can save files in the SVG format as well as the SVG compressed format.
  • OpenOffice.org Draw can export SVG drawings. Import extensions are available to import SVG images into OpenOffice.org Draw.[58]
  • OxygenOffice Draw (OpenOffice.org variant) can open and export SVG files.[59]
  • The Processing programming language has native support for the SVG format.
  • Examotion's RENESIS Player is a free SVG browser for windows. Its Windows Thumbnail Plugin allows the generation of thumbnail previews in any Windows Explorer window.
  • Scribus can export separate pages in SVG.
  • sK1 is a free software vector graphics program for Linux, supports both the import and export of SVG images.
  • Kiyut's Sketsa is a mature commercial SVG editor.
  • Svg-Edit is a lightweight, web-based, Javascript-driven SVG editor that works in any modern browser.
  • SVG Pony is a commercial converter from SVG to SVG Tiny.[60]
  • Universal Converter is a virtual printer that allows conversion of files to SVG format and also converts SVG files to other file formats.
  • ViewerSvg is a SVG to XAML converter. The exported XAML can be used in WPF or Silverlight applications.[61]
  • Xara Xtreme has an SVG export and import filter in both its free/open-source and pay versions.
  • xfig and gnuplot allow export of SVG drawings.

Mobile support

The most popular implementations for mobile phones are by Ikivo and Bitflash, while for PDAs, Bitflash and Intesis have implementations. Adobe Flash Lite has optionally supported SVG Tiny since version 1.1. At the SVG Open 2005 conference, Sun demonstrated a mobile implementation of SVG Tiny 1.1 for the Connected Limited Device Configuration (CLDC) platform.

Mobile SVG players from Ikivo and BitFlash come pre-installed, i.e., the manufacturers burn the SVG player code into their mobiles before shipping to the customers. Mobiles can also include full web browsers (such as Opera Mobile and the iPhone's Safari) that include SVG support.

The level of SVG Tiny support available varies from mobile to mobile, depending on the SVG engine installed. Many newer mobile products support additional features beyond SVG Tiny 1.1, like gradient and opacity; this standard is often referred as SVGT 1.1+. The iPhone, for example, supports declarative animation but not interactivity.

Nokia's S60 platform has built-in support for SVG. For example, icons are generally rendered using the platform's SVG engine. Nokia has also led the JSR 226: Scalable 2D Vector Graphics API expert group which defines Java ME API for SVG presentation and manipulation. This API has been implemented in S60 Platform 3rd Edition Feature Pack 1 onward.[62] Some Series 40 phones also support SVG (such as Nokia 6280).

Most Sony Ericsson phones beginning with K700 (by release date) support SVG Tiny 1.1. Phones beginning with K750 also support such features as opacity and gradients. Phones with Sony Ericsson Java Platform-8 have support for JSR 226.

SVG is also supported on various mobile devices from Motorola, Samsung, LG, and Siemens.

Hardware rendering

Implementations of SVG that uses the OpenVG API will be hardware accelerated on devices which have hardware acceleration of OpenVG. Examples include Unix-like operating systems with Gallium3D based graphics drivers and several GPUs intended for handheld devices (see OpenVG).

See also

References

  1. ^ "M Media Type registration for image/svg+xml". World Wide Web Consortium. Retrieved 19 October 2009.
  2. ^ "XML Media Types, RFC 3023". IETF. 2001-01. p. 24. Retrieved 2009-10-24. {{cite web}}: Check date values in: |date= (help)
  3. ^ Svensson, Peter (10 September 2008). "Creator of Web spots a flaw in Internet Explorer". msnbc.msn.com. Microsoft. Retrieved 16 November 2008.
  4. ^ "SVG(W3C) § 4.2-Drawing Order". World Wide Web Consortium. 15 November 2002. Retrieved 19 October 2009.
  5. ^ Alex, Danilo (2002). "SVG as a Page Description LanguageSVG as a Page Description Language". SVG Open. Retrieved 24 February 2010. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  6. ^ Alex, Danilo (21 December 2007). "SVG Print 1.2, Part 2: Language". World Wide Web Consortium. Retrieved 24 February 2010. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  7. ^ Paul, Festa (9 January 2003). "W3C releases scripting standard, caveat". CNet. Retrieved 24 February 2010.
  8. ^ "Saving compressed SVG (SVGZ)". SVG Zone. Adobe. 14 July 2009. Retrieved 24 February 2010.
  9. ^ Ferraiolo, Jon (04 September 2001). "Scalable Vector Graphics (SVG) 1.0 SpecificationScalable Vector Graphics (SVG) 1.0 Specification". World Wide Web Consortium. Retrieved 24 February 2010. {{cite web}}: Check date values in: |date= (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  10. ^ a b Ferraiolo, Jon (14 January 2003, edited in place 30 April 2009). "Scalable Vector Graphics (SVG) 1.1 Specification". World Wide Web Consortium. Retrieved 24 February 2010. {{cite web}}: Check date values in: |date= (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  11. ^ Capin, Tolga (14 January 2003, edited in place 15 June 2009). "Mobile SVG Profiles: SVG Tiny and SVG Basic". World Wide Web Consortium. Retrieved 2010-02-24. {{cite web}}: Check date values in: |date= (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  12. ^ Andersson, Ola (22 December 2008). "Scalable Vector Graphics (SVG) Tiny 1.2 Specification". World Wide Web Consortium. Retrieved 24 February 2010. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  13. ^ "SVG in 3GPP Multimedia Messaging and Streaming Services (version March 2003)". SVG Open. 2003. Retrieved 19 October 2009.
  14. ^ "3GPP Multimedia Messaging Service (MMS); Media formats and codecs (Release 5); 3GPP TS 26.140 V5.2.0 (2002-12); Technical Specification]" (zipped doc). 3GPP. 02.01.2003. Retrieved 25 February 2010. {{cite web}}: Check date values in: |date= (help)
  15. ^ "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Messaging Service (MMS); Media formats and codecs (Release 5)" (zipped doc). 3GPP TS 26.140 V5.2.0 (2002-12). 3GPP. March 2003. Retrieved 24 February 2010.
  16. ^ "3GPP Specification detail - 3GPP TS 26.141: IP Multimedia System (IMS) Messaging and Presence; Media formats and codecs". 3GPP. 10 December 2009. Retrieved 24 February 2010.
  17. ^ "Listing of phones that support SVG". Svg.org. Archived from the original on 28 July 2008. Retrieved 24 February 2010.
  18. ^ "SVG specification, "Paths"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  19. ^ "SVG specification, "Basic Shapes"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  20. ^ "SVG specification, "Text"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  21. ^ "SVG specification, "Painting: Filling, Stroking and Marker Symbols"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  22. ^ "SVG specification, "Color"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  23. ^ "SVG specification, "Gradients and Patterns"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  24. ^ "IRC log of svg on 2008-11-17". W3C. 2008. Retrieved 25 May 2009. DS: Priorities should be layout, diffusion curves, 2.5D and make sure we work well with CSS on that
  25. ^ "Propositions for the next SVG spec". W3C. 16 March 2009. Retrieved 25 May 2009. Indeed, we do plan to add new gradient capabilities to SVG in the next version, and we are looking into diffusion curves, which I think will meet your needs ... *Diffusion curves* seems really a great idea.
  26. ^ Rusin, Zack (2008). "SVG in KDE: Freedom of Beauty". SVG Open. Retrieved 25 May 2009.
  27. ^ Orzan, Alexandrina (2008). "Diffusion Curves: A Vector Representation for Smooth-Shaded Images" (PDF). ACM Transactions on Graphics (Proceedings of SIGGRAPH 2008). 27. Retrieved 25 May 2009. {{cite journal}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  28. ^ "SVG specification, "Clipping, Masking and Compositing"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  29. ^ "SVG specification, "Filter Effects"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  30. ^ "SVG specification, "Interactivity"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  31. ^ "SVG specification, "Scripting"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  32. ^ "SVG specification, "Animation"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  33. ^ "SVG specification, "Fonts"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  34. ^ "SVG specification, "Metadata"". World Wide Web Consortium. Retrieved 19 October 2009.
  35. ^ "Windows Internet Explorer 8 Expert Zone Chat (19 June 2008)". Microsoft. 19 June 2008. Retrieved 24 February 2010.
  36. ^ Schiller, Jeff (13 February 2010). "SVG Support". Retrieved 25 February 2010.
  37. ^ Lusotec (25 February 2009). "SVG image not shown by Firefox". mozilla.dev.tech.svg. Google Groups. Retrieved 25 February 2010.
  38. ^ Brettz9 (25 August 2008). "SVG In HTML Introduction". Mozilla Developer Center. Mozilla. Retrieved 25 February 2010.{{cite web}}: CS1 maint: numeric names: authors list (link)
  39. ^ Svensson, Peter (10 September 2008). "Creator of Web spots a flaw in Internet Explorer". MSNBC. Associated Press. Retrieved 25 February 2010.
  40. ^ "SVG in Firefox". Mozilla Developer Center. Mozilla. 23 October 2009. Retrieved 25 February 2010.
  41. ^ "Mozilla SVG Status". Mozilla. Retrieved 25 February 2010.
  42. ^ Mgjbot (15 January 2008). "SVG improvements in Firefox 3". Mozilla Developer Center. Mozilla. Retrieved 25 February 2010.
  43. ^ "WebKit SVG Status". WebKit. Jan 5th, 2010. Retrieved 2010-02-25. {{cite web}}: Check date values in: |date= (help)
  44. ^ "RENESIS Player – Fast, easy and smart". examotion GmbH. Retrieved 30 May 2009.
  45. ^ "Ssrc SVG: SVG Plugin for Internet Explorer". Savarese Software Research Corporation. Retrieved 30 May 2009.
  46. ^ "Download Batik". Apache Software Foundation. 9 January 2008. Retrieved 25 February 2010.
  47. ^ "GPAC Project on Advanced Content". Sourceforge. December 2008. Retrieved 25 February 2010.
  48. ^ "Adobe SVG Viewer download area". Adobe. Retrieved 19 October 2009.
  49. ^ "Adobe SVG Viewer End of Life announcement". Adobe. Retrieved 25 February 2010.
  50. ^ "Corel SVG Viewer". Corel Corporation. Retrieved 25 February 2010.
  51. ^ "svgweb: Scalable Vector Graphics for Web Browsers using Flash". Google Code. Retrieved 25 September 2009.
  52. ^ Clarke, Gavin (3rd June 2009). "Google to slip SVG into Internet Explorer". The Register. Retrieved 25 February 2010. {{cite web}}: Check date values in: |date= (help)
  53. ^ Dengler, Patrick (January 05, 2010). "Microsoft Joins W3C SVG Working Group". MSDN. Microsoft. Retrieved 25 February 2010. {{cite web}}: Check date values in: |date= (help)
  54. ^ "Ecava IntegraXor". Integraxor.com. Retrieved 19 October 2009.
  55. ^ "SAGE Documentation". Ecava.com. 20 April 2009. Retrieved 19 October 2009.
  56. ^ "Discover Go-OO". Go-oo. Retrieved 19 October 2009.
  57. ^ "SVG Import Filter". OpenOffice.org. 19. August 2009. Retrieved 2010-02-25. {{cite web}}: Check date values in: |date= (help)
  58. ^ "OxygenOffice Professional - free and multilingual office suite". Sourceforge. Retrieved 25 February 2010.
  59. ^ "SVG Pony converter". Mpaja. Retrieved 23 January 2010.
  60. ^ "ViewerSvg". www.wpf-graphics.com. 24 February 2010. Retrieved 24 February 2010.
  61. ^ "S60 Product info". S60.com. Retrieved 19 October 2009.
Wikibooks has a book on the topic of: XML - Managing Data Exchange/SVG

Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=SVG&oldid=347552625"