Jump to content

SVG

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Hylobius (talk | contribs) at 15:07, 5 April 2011 ('very notable of' -> 'very notable exception of'). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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; 15 years ago (2008-12-22)
Type of formatvector image format
Extended fromXML
Free format?Yes
Websitew3.org/Graphics/SVG/
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 behaviors 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 drawing programs are also available that support SVG file formats.

All major modern web browsers have at least some degree of support and render SVG markup directly with the very notable exception of Microsoft Internet Explorer (IE),[3] except IE9 which now has limited support of the SVG feature set[4] after years of ignoring SVG in favor of proprietary formats.[5] Currently, support for browsers running under Android is also limited.

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.[6]

SVG allows three types of graphic objects: vector graphics, raster graphics, and text. Graphical objects, including PNG and JPEG raster images, can be grouped, styled, transformed, and composited into previously rendered objects. SVG does not directly support z-indices[7] 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 search ability 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.

Although not directly comparable to SVG since it is a bitmap based format, the Canvas element in HTML5 provides an approach to rendering dynamic graphics in HTML that's procedural rather than declarative: instead of specifying the shapes to draw in XML, the author executes drawing commands from a script. Canvas does not allow for static rendering, and drawn elements are not identifiable in a DOM-like way.

Printing

Though the SVG Specification primarily focuses on vector graphics markup language, its design includes 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, whose primary purpose is communication of content, not presentation, and therefore specifies objects to be displayed but not where to place such objects. Conversely SVG is an ideal PDL for print-oriented uses, as it contains all the functionality required to place each glyph and image in a chosen location on the final page.[8] A much more print-specialized subset of SVG (SVG Print, authored by Canon, HP, Adobe and Corel) is currently a W3C Working Draft.[9]

Scripting and 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.[10] 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 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.[11]

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.[12]
  • SVG 1.1 became a W3C Recommendation on 14 January 2003.[13] 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.[14]
  • SVG Tiny 1.2 became a W3C Recommendation on 22 December 2008.[15]
  • SVG Full 1.2 has had a W3C Working Draft in process for years, but now will be dropped soon in favor of a SVG 2.0.[16] 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.
  • SVG 1.1 Second Edition, which includes all the errata and clarifications, but no new features to the original SVG 1.1 was given as a Last Call publication on June 22, 2010.[16] It is expected to be approved later this year.
  • SVG 2.0 will completely rework draft 1.2 with more integration with new web features such as CSS, HTML5 and WOFF.

The MPEG-4 Part 20 standard - Lightweight Application Scene Representation (LASeR) and Simple Aggregation Format (SAF) is based on SVG Tiny.[17] It was developed by MPEG (ISO/IEC JTC1/SC29/WG11) and published as ISO/IEC 14496-20:2006.[18] SVG capabilities are enhanced in MPEG-4 Part 20 with key features for mobile services, such as dynamic updates, binary encoding, state-of-art font representation.[19] SVG was also accommodated in MPEG-4 Part 11, in the Extensible MPEG-4 Textual (XMT) format - a textual representation of the MPEG-4 multimedia content using XML.[20]

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-switched Streaming Service (PSS).[21][22][23] It was later added as required format for vector graphics in 3GPP IP Multimedia Subsystem (IMS).[24] 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.[25]

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:[13]

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.[26]
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.[27]
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).[28]
Painting
SVG shapes can be filled and/or outlined (painted with a colour, 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.[29]
Colour
Colours can be applied to all visible SVG elements, either directly or via the 'fill', 'stroke' and other properties. Colours 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%).[30]
Gradients and Patterns
SVG shapes can be filled or outlined with solid colours as above, or with colour gradients or with repeating patterns. Colour gradients can be linear or radial (circular), and can involve any number of colours 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.[31]
Since 2008, there has been discussion[32][33] 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"[34] 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."[35]
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.[36]
Filter Effects[37]
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.[38]
Linking
SVG images can contain hyperlinks to other documents, using XLink. URLs of SVG images can specify geometrical transforms in the fragment section.[39]
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.[40]
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.[41]
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.[42]
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.[43]

An SVG image can define components and use them repeatedly. SVG image can also contain raster graphics (usually PNG and JPEG images) and other SVG images.

SVG on the web

Google announced on 31 August 2010 that it had begun to index SVG content on the web, whether it is in standalone files or embedded in HTML, and that users would start to see such content listed among their search results.[44] It was announced on 8 December 2010 that Google Image Search would also begin indexing SVG files.[45] On 28 January 2011, it was discovered that Google was allowing Image Search results to be restricted exclusively to SVG files.[46] This feature was announced officially on 11 February 2011.[47]

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 older versions of Internet Explorer (IE) which (as of December 2010) is the most widely-used browser. The most widely deployed version of IE (version 8) does not support SVG.[48][49] However, IE9 (released March 14, 2011) does support the basic SVG feature set.[4] Many web sites that serve SVG images, such as Wikipedia, also 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

Konqueror was the first browser to support SVG in release version 3.2 in february 2004. As of 2010, all major desktop browsers, and many minor ones, have some level of SVG support. Other browsers' implementations are not yet complete; see Comparison of layout engines for further details. As of 2010, only Konqueror, 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 embedded in <object> or <iframe> elements to display them integrated as parts of an HTML webpage.[50] However, SVG images may be included in XHTML pages using XML namespaces.[51]

Tim Berners-Lee, the inventor of the Web, has been critical of Internet Explorer for its failure to support SVG.[52] 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. It also supports SVGZ (compressed SVG).
  • 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[53] and of the modules which are in progress in the development.[54] Gecko 1.9, included in Firefox 3.0, adds support for more of the SVG specification (including filters).[55]
  • 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.[56]
  • 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.

Compatibility

Internet Explorer, up to and including IE8, was the only major browser not to provide native SVG support. Native support became partially available in IE9 (the current version of IE, as of March 2011).[4] IE8 and older require a plug-in to render SVG content. There are a number of plug-ins available to assist, including:

  • 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.[57]
  • 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
  • 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.[60] However, on 1 January 2009, Adobe Systems discontinued support for Adobe SVG Viewer.[61]

Ample SDK Open-Source JavaScript GUI Framework provides partial support for SVG 1.1, SMIL, DOM and style scripting in Internet Explorer (5.5 - 8.0) too. It is not dependent on any plugins and relies on presence of alternative Vector Graphics format VML in Internet Explorer.

SVG Web[64] 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.[65]

Raphaël is another JavaScript library that takes advantage of the intersection between VML's and SVG's features to create vector graphics and animate them.

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 at that time.[66] Internet Explorer 9 beta supports a basic SVG feature set based on the SVG 1.1 W3C recommendation. Functionality has been implemented for most of the SVG document structure, interactivity through scripting, and styling inline and through CSS. The presentation elements, attributes and DOM interfaces that have been implemented include basic shapes, colors, filling, gradients, patterns, paths, and text.[67]

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.
  • ABViewer,[68] viewing, editing and conversion.
  • ACD Canvas supports importing and exporting SVG.
  • Adobe Acrobat (since version 5.1) supports SVG 1.0 only in so called "alternate presentations" in PDF format.[69]
  • 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 whereafter 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.
  • Batik SVG Toolkit can be used by Java programs to render, generate, and manipulate SVG graphics.
  • Blender will import SVG graphics as paths. As of 2.53 it will also now export UV Maps as SVG files.
  • Cairo is a vector graphics based library which can generate SVG. It has bindings for many programming languages including C++, Haskell, Java, Perl, Python, Scheme, Smalltalk and several others.
  • CorelDRAW has an SVG export and import filter.
  • Ecava IntegraXor[70] created SAGE [71] (SCADA Animation Graphic Editor) which allows SVG graphic to be used in SCADA application.
  • GIMP allows SVG images to be imported as paths or rendered bitmaps. GIMP paths are compatible with SVG.
  • 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.[72]
  • Google Docs can export a drawing into SVG files.
  • Graphviz can create graph diagrams in SVG.
  • ImageBot is a HTML5 based SVG and image editor. Can import and export SVG files.[73]
  • Inkscape is an open source 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. Inkscape can import PDF files and thus can transform content in PDF 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.
  • Joffice is a Java based Office suite with built-in support of SVG.
  • LibreOffice Writer word processor and Draw can import SVG files.[74]
  • Mappetizer is a commercial converter for spatial data to SVG.
  • Microsoft Visio since version 2003 can import and save files in the SVG format as well as the SVG compressed format.[75][76]
  • OpenOffice.org Draw can export SVG drawings. Import extensions are available to import SVG images into OpenOffice.org Draw.[77]
  • Opera SVG Viewer is an Opera widget image browser that allows to preview and scale all SVG files from a directory.[78]
  • OxygenOffice Draw (OpenOffice.org variant) can open and export SVG files.[79]
  • PDFTron's PDF2SVG is a commercial PDF to SVG conversion software. Available as a Command-line application and as an SDK on multiple platforms, including Windows, Mac OS X and Linux.[80]
  • The Processing programming language has native support for the SVG format.
  • QuickLook is a feature of Mac OS X that can display a variety of files, including SVG.
  • Scribus can import SVG files and export separate pages in SVG.
  • ShareCAD,[81] free on-line SVG viewer.
  • Sheetster Supports creation and display of SVG spreadsheet charts.
  • sK1 is a free software vector graphics program for Linux, supports both the import and export of SVG images.
  • Sketsa (Kiyut) is a mature commercial SVG editor.
  • SVG Kit for Adobe Creative Suite is a plug-in, which adds full-functional support of SVG images to Adobe InDesign and Adobe Photoshop.
  • SVG Pony is a commercial converter from SVG to SVG Tiny.[82]
  • SVG-edit is a lightweight, web-based, Javascript-driven SVG editor that works in any modern browser.
  • 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.[83]
  • Virtual Mechanics SiteSpinner applications export to SVG.
  • Xara Xtreme can export in SVG format. The free/open-source GNU/LINUX version also has a limited import filter.
  • xfig and gnuplot allow export of SVG drawings.
  • VectorPen[84] is an OpenSource Project,[85] which allows one to convert the files created on digital notepades[86] to vector based PDF or SVG.

Mobile support

The most popular implementations for mobile phones are by Ikivo and BitFlash, while for PDAs, BitFlash and Intesis have implementations. 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. 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.[87]

Mobiles which use Opera Mobile, and the built-in iPhone's browser, also include SVG support. However, even if it uses the WebKit engine, the Android built-in browser still does not support SVG.[88] Currently, only Firefox Mobile 4.0b2 (beta) for Android supports SVG by default.[89]

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.[90] 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 mobile/BenQ-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

Template:Multicol

Template:Multicol-break

Template:Multicol-end

References

  1. ^ "M Media Type registration for image/svg+xml". World Wide Web Consortium. 22 December 2008. Retrieved 29 August 2010.
  2. ^ "XML Media Types, RFC 3023". Internet Engineering Task Force. January 2001. p. 24. Retrieved 29 August 2010.
  3. ^ Svensson, Peter (10 September 2008). "Creator of Web spots a flaw in Internet Explorer". MSNBC. Microsoft. Retrieved 29 August 2010.
  4. ^ a b c "What's New in Internet Explorer 9". Microsoft Developer Network. Microsoft. 22 March 2011. Retrieved 22 March 2011.
  5. ^ http://channel9.msdn.com/Blogs/Joshua/Microsoft-and-Adobe-Killing-SVG
  6. ^ "Secret Origin of SVG". World Wide Web Consortium. 21 December 2007. Retrieved 1 January 2011.
  7. ^ "Scalable Vector Graphics (SVG) 1.2 W3C Working Draft § 4.2-Drawing Order". World Wide Web Consortium. 15 November 2002. Retrieved 29 August 2010.
  8. ^ Alex, Danilo; Fujisawa, Jun (2002). "SVG as a Page Description LanguageSVG as a Page Description Language". SVG Open. Retrieved 24 February 2010.
  9. ^ 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)
  10. ^ Paul, Festa (9 January 2003). "W3C releases scripting standard, caveat". CNet. Retrieved 24 February 2010.
  11. ^ "Saving compressed SVG (SVGZ)". SVG Zone. Adobe Systems. 14 July 2009. Retrieved 24 February 2010.
  12. ^ Ferraiolo, Jon (4 September 2001). "Scalable Vector Graphics (SVG) 1.0 Specification". World Wide Web Consortium. Retrieved 24 February 2010. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  13. ^ 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)
  14. ^ Capin, Tolga (14 January 2003, edited in place 15 June 2009). "Mobile SVG Profiles: SVG Tiny and SVG Basic". World Wide Web Consortium. Retrieved 24 October 2010. {{cite web}}: Check date values in: |date= (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  15. ^ 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)
  16. ^ a b Dengler, Patrick (8 July 2010). "Getting to SVG 2.0: A report from the SVG Working Group Face-to-Face (May 24th – June 1st 2010)". Microsoft Developer Network. Microsoft. Retrieved 26 August 2010.
  17. ^ Concolato, Cyril (July 2005). "MPEG-4 LASeR white paper". International Organization for Standardization. Retrieved 29 August 2010.
  18. ^ "ISO/IEC 14496-20:2008 - Information technology -- Coding of audio-visual objects -- Part 20: Lightweight Application Scene Representation (LASeR) and Simple Aggregation Format (SAF)". International Organization for Standardization. Retrieved 30 October 2009.
  19. ^ "LASeR - the MPEG standard for Rich Media Services" (PDF). Retrieved 11 April 2010.
  20. ^ Chiariglione, Leonardo (8 March 2005). "Riding the media bits - Bits and bytes". Retrieved 30 October 2009.
  21. ^ "SVG in 3GPP Multimedia Messaging and Streaming Services (version March 2003)". SVG Open. 2003. Retrieved 19 October 2009.
  22. ^ "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. 2 January 2003. Retrieved 25 February 2010.
  23. ^ "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.
  24. ^ "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.
  25. ^ "Listing of phones that support SVG". Svg.org. Archived from the original on 28 July 2008. Retrieved 24 October 2010.
  26. ^ "SVG specification, "Paths"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  27. ^ "SVG specification, "Basic Shapes"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  28. ^ "SVG specification, "Text"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  29. ^ "SVG specification, "Painting: Filling, Stroking and Marker Symbols"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  30. ^ "SVG specification, "Color"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  31. ^ "SVG specification, "Gradients and Patterns"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  32. ^ "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
  33. ^ "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.
  34. ^ Rusin, Zack (2008). "SVG in KDE: Freedom of Beauty". SVG Open. Retrieved 25 May 2009.
  35. ^ 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)
  36. ^ "SVG specification, "Clipping, Masking and Compositing"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  37. ^ "SVG specification, "Filter Effects"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  38. ^ "SVG specification, "Interactivity"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  39. ^ "SVG specification, "Scripting"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  40. ^ "SVG specification, "Animation"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  41. ^ "SVG specification, "Fonts"". World Wide Web Consortium. 14 January 2003. Retrieved 19 October 2009.
  42. ^ "SVG specification, "Metadata"". World Wide Web Consortium. Retrieved 19 October 2009.
  43. ^ Stanescu, Bogdan (31 August 2010). "Google now indexes SVG". Webmaster central blog. Google, Inc. Retrieved 1 September 2010. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  44. ^ "googleimages". Google, Inc. 8 December 2010. Retrieved 17 February 2011.
  45. ^ Chitu, Alex (28 January 2011). "Google Image Search Indexes SVG Files". Google Operating System blog. Retrieved 28 January 2011.
  46. ^ Singhal, Amit (11 February 2011). "This week in search 2/11/11". Google, Inc. Retrieved 17 February 2011.
  47. ^ "Windows Internet Explorer 8 Expert Zone Chat (19 June 2008)". Microsoft. 19 June 2008. Retrieved 24 October 2010.
  48. ^ Schiller, Jeff (13 February 2010). "SVG Support". Retrieved 25 February 2010.
  49. ^ Lusotec (25 February 2009). "SVG image not shown by Firefox". mozilla.dev.tech.svg. Google Groups. Retrieved 25 February 2010.
  50. ^ 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)
  51. ^ Svensson, Peter (10 September 2008). "Creator of Web spots a flaw in Internet Explorer". MSNBC. Associated Press. Retrieved 25 February 2010.
  52. ^ "SVG in Firefox". Mozilla Developer Center. Mozilla. 23 October 2009. Retrieved 25 February 2010.
  53. ^ "Mozilla SVG Status". Mozilla. Retrieved 25 February 2010.
  54. ^ Mgjbot (15 January 2008). "SVG improvements in Firefox 3". Mozilla Developer Center. Mozilla. Retrieved 25 February 2010.
  55. ^ "WebKit SVG Status". WebKit. Jan 5th, 2010. Retrieved 2010-02-25. {{cite web}}: Check date values in: |date= (help)
  56. ^ "Ssrc SVG: SVG Plugin for Internet Explorer". Savarese Software Research Corporation. Retrieved 30 May 2009.
  57. ^ "Download Batik". Apache Software Foundation. 9 January 2008. Retrieved 25 February 2010.
  58. ^ "GPAC Project on Advanced Content". Sourceforge. December 2008. Retrieved 25 February 2010.
  59. ^ "Adobe SVG Viewer download area". Adobe Systems. Retrieved 19 October 2009.
  60. ^ "Adobe SVG Viewer End of Life announcement". Adobe Systems. Retrieved 25 February 2010.
  61. ^ "Corel SVG Viewer". Corel Corporation. Retrieved 25 February 2010.
  62. ^ "Renesis Player – Fast, easy and smart". examotion GmbH. Retrieved 30 May 2009.
  63. ^ "svgweb: Scalable Vector Graphics for Web Browsers using Flash". Google Code. Retrieved 25 September 2009.
  64. ^ Clarke, Gavin (3 June 2009). "Google to slip SVG into Internet Explorer". The Register. Retrieved 25 February 2010.
  65. ^ Dengler, Patrick (5 January 2010). "Microsoft Joins W3C SVG Working Group". MSDN. Microsoft. Retrieved 25 February 2010.
  66. ^ "Internet Explorer 9 Beta Guide for Developers". Microsoft Developer Network. Microsoft. 15 September 2010. Retrieved 15 September 2010.
  67. ^ "?". cadsofttools.com.
  68. ^ Adobe Systems Incorporated (2003). "PDF Reference fourth edition - Adobe® Portable Document Format Version 1.5" (PDF). Retrieved 23 February 2010. [dead link]
  69. ^ "Ecava IntegraXor". Integraxor.com. Retrieved 19 October 2009.
  70. ^ "SAGE Documentation". Ecava.com. 20 April 2009. Retrieved 19 October 2009.
  71. ^ "Discover Go-OO". Go-oo. Retrieved 19 October 2009.
  72. ^ "ImageBot.com".
  73. ^ "New Features –LibreOffice". LibreOffice. Retrieved 10 February 2011.
  74. ^ "File formats that you can import into a Visio drawing". Retrieved 1 December 2010.
  75. ^ "Introducing Microsoft Office Visio 2003". Retrieved 1 December 2010.
  76. ^ "SVG Import Filter". OpenOffice.org. 19 August 2009. Retrieved 25 February 2010.
  77. ^ SpShut (3 February 2010). "Opera SVG Viewer allows to preview and scale all SVG files from a directory using Opera browser rendering engine". Opera Software. Retrieved 6 March 2010.
  78. ^ "OxygenOffice Professional - free and multilingual office suite". Sourceforge. Retrieved 25 February 2010.
  79. ^ "PDFTron: PDF components and PDF tools - PDF2SVG". PDFtron.com. Retrieved 29 August 2010.
  80. ^ "ShareCAD.org - Ihre CAD-Dateien ansehen und gemeinsam benutzen!". ShareCAD.org. 2010. Retrieved 29 August 2010.
  81. ^ "SVG Pony converter". Mpaja.com. Retrieved 29 August 2010.
  82. ^ "ViewerSvg". www.wpf-graphics.com. 24 October 2010. Retrieved 24 October 2010.
  83. ^ Vectorpen.com
  84. ^ Github.com
  85. ^ Vectorpen.com
  86. ^ "SVG Open 2005 Conference and Exhibition - Proceedings - Cartoon Oriented User Interfaces". SVG Open. Retrieved 29 August 2010.
  87. ^ "Browser doesn't render SVG images". Google. Retrieved 1 January 2011.
  88. ^ "Firefox Mobile 4.0b2 (beta) for Android supports SVG images". google/fralacos. Retrieved 2 January 2011.
  89. ^ "S60 Product info". S60.com. Archived from the original on 13 October 2007. Retrieved 19 October 2009.

Template:Link GA