Scalable Vector Graphics: Difference between revisions

From PsiForum
Jump to navigation Jump to search
(←Created page with '{{short description|Open standard for two-dimensional vector graphics}} {{redirect|SVG}} {{For|help about SVG images on Wikipedia|Wikipedia:SVG help}} {{Use dmy dates|date=February 2014}} {{Infobox file format | name = Scalable Vector Graphics | icon = SVG Logo.svg | icon_size = 200px | iconcaption = | screenshot = | caption = | _noextcode = on | extension = | extensions = <code>.svg</code>, <code>.svgz</code>...')
 
(←Replaced content with '<!--Scalable Vector Graphics-->')
Tag: Replaced
 
Line 1: Line 1:
−
{{short description|Open standard for two-dimensional vector graphics}}
+
<!--Scalable Vector Graphics-->
−
{{redirect|SVG}}
 
−
{{For|help about SVG images on Wikipedia|Wikipedia:SVG help}}
 
−
{{Use dmy dates|date=February 2014}}
 
−
{{Infobox file format
 
−
| name          = Scalable Vector Graphics
 
−
| icon          = SVG Logo.svg
 
−
| icon_size    = 200px
 
−
| iconcaption  =
 
−
| screenshot    =
 
−
| caption      =
 
−
| _noextcode    = on
 
−
| extension    =
 
−
| extensions    = <code>.svg</code>, <code>.svgz</code>
 
−
| _nomimecode  = on
 
−
| mime          = <code>image/svg+xml</code><ref>{{cite web |title=Media Type Registration for image/svg+xml |url=http://www.w3.org/TR/SVG/mimereg.html |publisher=[[World Wide Web Consortium|W3C]] |access-date=5 February 2014}}</ref><ref>{{cite document |title=XML Media Types |date=January 2001 |url=http://tools.ietf.org/html/rfc3023#section-8.19 |access-date=5 February 2014|last1=St. Laurent |first1=Simon |last2=Makoto |first2=Murata |last3=Kohn |first3=Dan }}</ref>
 
−
| type_code    = <!-- {{hlist |"svg" |"svgz"}} -->
 
−
| uniform_type  = <code>public.svg-image</code>
 
−
| conforms_to  = <!--<code>public.image</code><br /><code>public.xml</code>-->
 
−
| magic        =
 
−
| developer    = [[World Wide Web Consortium|W3C]]
 
−
| released      = {{start date and age|df=yes|paren=yes|2001|09|04}}
 
−
| latest_release_version = 1.1 (Second Edition)
 
−
| latest_release_date = {{start date and age|2011|08|16|df=yes}}
 
−
| genre        = [[Vector graphics]]
 
−
| container_for =
 
−
| contained_by  =
 
−
| extended_from = [[XML]]
 
−
| extended_to  =
 
−
| standard      = {{URL|https://www.w3.org/TR/SVG/|W3C SVG}}
 
−
| open          = Yes
 
−
| url          = {{URL|https://www.w3.org/Graphics/SVG/}}
 
−
}}
 
−
 
 
−
'''Scalable Vector Graphics''' ('''SVG''') is an [[XML]]-based [[vector image format]] for [[two-dimensional]] graphics with support for interactivity and animation. The SVG specification is an [[open standard]] developed by the [[World Wide Web Consortium]] (W3C) since 1999.
 
−
 
 
−
SVG images are defined in a [[vector graphics]] format and stored in [[XML]] text files. SVG images can thus be [[Scale (ratio)|scaled]] in size without loss of quality, and SVG files can be [[search algorithm|searched]], [[subject indexing|indexed]], [[scripting language|scripted]], and [[data compression|compressed]]. The XML text files can be created and edited with [[text editor]]s or [[vector graphics editor]]s, and are [[Comparison of layout engines (Scalable Vector Graphics)|rendered]] by the most-used [[web browser]]s.
 
−
 
 
−
==Overview==
 
−
[[File:Bitmap VS SVG.svg|right|300px|thumb|This image illustrates the difference between bitmap and vector images. The bitmap image is composed of a fixed set of pixels, while the vector image is composed of a fixed set of shapes. In the picture, [[image scaling|scaling]] the bitmap reveals the pixels while scaling the vector image preserves the shapes.]]
 
−
 
 
−
SVG has been in development within the [[World Wide Web Consortium]] (W3C) since 1999 after six competing proposals for vector graphics languages had been submitted to the consortium during 1998 (see below).<ref name="secretOrigin" />
 
−
 
 
−
The early SVG Working Group decided not to develop any of the commercial submissions, but to create a new markup language that was informed by but not really based on any of them.<ref name="secretOrigin">{{cite web |url=http://www.w3.org/Graphics/SVG/WG/wiki/Secret_Origin_of_SVG|title=Secret Origin of SVG|date=21 December 2007|publisher=[[World Wide Web Consortium]]|access-date=1 January 2011}}</ref>
 
−
 
 
−
SVG allows three types of graphic objects: [[vector graphics|vector graphic]] shapes such as paths and outlines consisting of straight lines and curves, [[bitmap]] images, and text. Graphical objects can be grouped, styled, transformed and composited into previously [[rendering (computer graphics)|rendered]] objects. The feature set includes nested [[transformation (geometry)|transformations]], [[clipping path]]s, [[alpha compositing|alpha masks]], [[SVG filter effect|filter effects]] and template objects. SVG drawings can be [[Interactivity|interactive]] and can include [[animation]], defined in the SVG XML elements or via [[Scripting language|scripting]] that accesses the SVG [[Document Object Model]] (DOM). SVG uses [[Cascading Style Sheets|CSS]] for styling and [[JavaScript]] for scripting. Text, including [[internationalization and localization]], appearing in plain text within the SVG DOM, enhances the [[Accessibility#Web accessibility|accessibility]] of SVG graphics.<ref name="SVG1.1-2E"/>
 
−
 
 
−
The SVG specification was updated to version 1.1 in 2011. There are two 'Mobile SVG Profiles,' SVG Tiny and SVG Basic, meant for [[mobile device]]s with reduced computational and display capabilities.<ref>{{cite web|last1=Capin|first1=Tolga|title=Mobile SVG Profiles: SVG Tiny and SVG Basic|url=https://www.w3.org/TR/SVGMobile/|publisher=W3C|access-date=28 January 2017}}</ref> Scalable Vector Graphics 2 became a [[World Wide Web Consortium#Specification maturation|W3C Candidate Recommendation]] on 15 September 2016. SVG 2 incorporates several new features in addition to those of SVG 1.1 and SVG Tiny 1.2.<ref>{{cite web|title=Scalable Vector Graphics (SVG) 2|url=https://www.w3.org/TR/SVG2/|publisher=W3C|access-date=28 January 2017}}</ref>
 
−
 
 
−
===Printing===
 
−
Though the SVG Specification primarily focuses on [[vector graphics markup language]], its design includes the basic capabilities of a [[page description language]] like Adobe's [[Portable Document Format|PDF]]. It contains provisions for rich graphics, and is compatible with [[Cascading Style Sheets|CSS]] for styling purposes. SVG has the information needed to place each glyph and image in a chosen location on a printed page.<ref>{{cite web|url=http://www.svgopen.org/2002/papers/danilo_fujisawa__svg_as_page_description_language/index.html|title=SVG as a Page Description Language|last1=Alex|first1=Danilo|first2=Jun|last2=Fujisawa|year=2002|publisher=svgopen.org|access-date=24 February 2010}}</ref>
 
−
 
 
−
===Scripting and animation===
 
−
{{Main|SVG animation}}
 
−
SVG drawings can be dynamic and interactive. Time-based modifications to the elements can be described in [[Synchronized Multimedia Integration Language|SMIL]], or can be programmed in a [[scripting language]] (e.g. [[JavaScript]]). The W3C explicitly recommends SMIL as the standard for animation in SVG.<ref>{{cite web|url=http://news.cnet.com/2100-1023-979976.html|title=W3C releases scripting standard, caveat|last=Paul|first=Festa|date=9 January 2003|publisher=[[CNET Networks|CNet]]|access-date=24 February 2010}}</ref>
 
−
 
 
−
A rich set of [[event handler]]s such as "''onmouseover"'' and "''onclick"'' can be assigned to any SVG graphical object to apply actions and events.
 
−
 
 
−
===Compression===
 
−
SVG images, being XML, contain many repeated fragments of text, so they are well suited for [[Data compression#Lossless|lossless data compression]] algorithms. When an SVG image has been compressed with the [[gzip]] algorithm, it is referred to as an "SVGZ" image and uses the corresponding <code>.svgz</code> filename extension. Conforming SVG 1.1 viewers will display compressed images.<ref>See {{URL|http://www.w3.org/TR/SVG11/conform.html#ConformingSVGViewers}} which states, "SVG implementations must correctly support gzip-encoded [RFC1952] and deflate-encoded [RFC1951] data streams, for any content type (including SVG, script files, images)."</ref> An SVGZ file is typically 20 to 50 percent of the original size.<ref>{{cite web|url=https://www.adobe.com/svg/illustrator/compressedsvg.html|title=Saving compressed SVG (SVGZ)|work=SVG Zone|publisher=[[Adobe Systems]]|date=14 July 2009|access-date=24 February 2010}}</ref> W3C provides SVGZ files to test for conformance.<ref>For example, {{URL|http://dev.w3.org/SVG/profiles/1.1F2/test/harness/htmlObject/conform-viewers-01-t.html}}</ref>
 
−
 
 
−
==Development history==
 
−
SVG was developed by the W3C [[SVG Working Group]] starting in 1998, after six competing vector graphics submissions were received that year:
 
−
* Web Schematics, from [[Council for the Central Laboratory of the Research Councils|CCLRC]]<ref>{{Cite web|url=https://www.w3.org/TR/1998/NOTE-WebSchematics-19980331/Overview.html|title=Schematic Graphics|website=www.w3.org}}</ref>
 
−
* [[PGML]], from [[Adobe Systems]], [[IBM]], [[Netscape]] and [[Sun Microsystems]]<ref>{{cite web|url=http://www.w3.org/TR/1998/NOTE-PGML-19980410|title=Precision Graphics Markup Language (PGML)|last=Al-Shamma|first=Nabeel|author2=Robert Ayers |author3=Richard Cohn |author4=Jon Ferraiolo |author5=Martin Newell |author6=Roger K. de Bry |author7=Kevin McCluskey |author8=Jerry Evans |date=10 April 1998|publisher=[[W3C]]|access-date=2009-05-08}}</ref>
 
−
* [[Vector Markup Language|VML]], by [[Autodesk]], [[Hewlett-Packard]], [[Macromedia]], [[Microsoft]], and [[Vision Corporation|Vision]]<ref>{{cite web|url=http://www.w3.org/TR/1998/NOTE-VML-19980513|title=Vector Markup Language (VML)|last=Mathews|first=Brian|author2=Brian Dister |author3=John Bowler |author4=Howard Cooper stein |author5=Ajay Jindal |author6=Tuan Nguyen |author7=Peter Wu |author8=Troy Sandal |date=13 May 1998|publisher=[[W3C]]|access-date=2009-05-08}}</ref>
 
−
* Hyper Graphics Markup Language (HGML), by [[Orange UK]] and [[University of Plymouth|PRP]]<ref>{{Cite web|url=https://www.w3.org/TR/NOTE-HGML.html|title=Hyper Graphics Markup Language (HGML)|website=www.w3.org}}</ref>
 
−
* [[Computer Graphics Metafile|WebCGM]], from [[Boeing]], InterCAP Graphics Systems, [[Stellent|Inso Corporation]], [[Council for the Central Laboratory of the Research Councils|CCLRC]], and [[Xerox]]<ref>{{Cite web|url=http://xml.coverpages.org/NOTE-WebCGM-19981104.html|title=WebCGM Profile|website=xml.coverpages.org}}</ref>
 
−
* DrawML, from Excosoft AB<ref name="secretOrigin"/>
 
−
The working group was chaired at the time by [[Chris Lilley (W3C)|Chris Lilley]] of the W3C.
 
−
 
 
−
=== Version 1.x ===
 
−
* SVG 1.0 became a [[W3C Recommendation]] on 4 September 2001.<ref>{{cite web|url=http://www.w3.org/TR/SVG10/|title=Scalable Vector Graphics (SVG) 1.0 Specification|last=Ferraiolo|first=Jon|date=4 September 2001|publisher=World Wide Web Consortium|access-date=24 February 2010}}</ref>
 
−
* SVG 1.1 became a W3C Recommendation on 14 January 2003.<ref name="svg11">{{cite web|url=http://www.w3.org/TR/SVG11/|title=Scalable Vector Graphics (SVG) 1.1 Specification|last=Ferraiolo|first=Jon|date=16 August 2011|publisher=World Wide Web Consortium|access-date=14 April 2016}}</ref> 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.<ref>{{cite web|url=http://www.w3.org/TR/2003/REC-SVGMobile-20030114/|title=Mobile SVG Profiles: SVG Tiny and SVG Basic|publisher=World Wide Web Consortium|last=Capin|first=Tolga|date=15 June 2009|access-date=24 October 2010}}</ref>
 
−
* SVG Tiny 1.2 became a W3C Recommendation on 22 December 2008.<ref>{{cite web|url=http://www.w3.org/TR/SVGTiny12/|title=Scalable Vector Graphics (SVG) Tiny 1.2 Specification|publisher=World Wide Web Consortium|date=22 December 2008|first=Ola|last=Andersson|access-date=24 February 2010}}</ref> It was initially drafted as a profile of the planned SVG Full 1.2 (which has since been dropped in favor of SVG 2),<ref name="ieblog">{{cite web|url=https://blogs.msdn.microsoft.com/ie/2010/06/08/getting-to-svg-2-0-a-report-from-the-svg-working-group-face-to-face-may-24th-june-1st-2010/|title=Getting to SVG 2.0: A report from the SVG Working Group Face-to-Face (May 24th – June 1st 2010)|last=Dengler|first=Patrick|date=8 July 2010|work=[[Microsoft Developer Network]]|publisher=[[Microsoft]]|access-date=26 August 2010}}</ref> but was later refactored as a standalone specification. It is generally poorly supported.
 
−
* SVG 1.1 Second Edition, which includes all the errata and clarifications, but no new features to the original SVG 1.1 was released on 16 August 2011.<ref name="SVG1.1-2E">{{cite web|url=http://www.w3.org/TR/2011/REC-SVG11-20110816/|title=Scalable Vector Graphics (SVG) 1.1 (Second Edition)|publisher=W3C}}</ref>
 
−
* SVG Tiny 1.2 Portable/Secure, A more secure subset of the SVG Tiny 1.2 profile introduced as an IETF draft standard on July 29, 2020.<ref>{{cite journal |title=SVG Tiny Portable/Secure |url=https://tools.ietf.org/html/draft-svg-tiny-ps-abrotman-00.html |website=IETF - Internet Engineering Task Force |access-date=9 February 2021|last1=Brotman |first1=Alex |last2=Adams |first2=J. Trent }}</ref> Also known as SVG Tiny P/S. SVG Tiny 1.2 Portable/Secure is a requirement of the [[Brand Indicators for Message Identification|BIMI]] draft standard.<ref>{{cite web |title=Implementation Guide |url=https://bimigroup.org/implementation-guide/ |website=BIMI Group |access-date=9 February 2021}}</ref>
 
−
 
 
−
===Version 2===
 
−
SVG 2 removes or deprecates some features of SVG 1.1 and incorporates new features from [[HTML5]] and [[Web Open Font Format]]:<ref name=diff/>
 
−
* For example, SVG 2 removes several font elements such as <code>glyph</code> and <code>altGlyph</code> (replaced by the WOFF font format).
 
−
* The <code>xml:space</code> attribute is deprecated in favor of CSS.
 
−
* HTML5 features such as <code>translate</code> and <code>data-*</code> attributes have been added.
 
−
* Text handling features from SVG Tiny 1.2 are annotated as to be included, but not yet formalized in text.<ref>{{cite web |url=https://svgwg.org/svg2-draft/text.html |title=Chapter 11: Text |date=2020-05-26|publisher=World Wide Web Consortium |access-date=31 December 2020 }}</ref> Some other 1.2 features are cherry-picked in,<ref name=diff>{{cite web |url=https://svgwg.org/svg2-draft/changes.html |title=Appendix K: Changes from SVG 1.1 |date=2020-05-26|publisher=World Wide Web Consortium |access-date=31 December 2020 }}</ref> but SVG 2 is not a superset of SVG tiny 1.2 in general.
 
−
 
 
−
SVG 2 reached the Candidate Recommendation stage on 15 September 2016,<ref>{{cite web|url=https://www.w3.org/TR/2016/CR-SVG2-20160915/|title=Scalable Vector Graphics (SVG) 2|date=2016-09-15|publisher=World Wide Web Consortium|access-date=2021-08-17}}</ref> and revised versions were published on 7 August 2018 and 4 October 2018.<ref>{{cite web|url=https://www.w3.org/TR/2018/CR-SVG2-20181004/|title=Scalable Vector Graphics (SVG) 2|date=2018-10-04|publisher=World Wide Web Consortium|access-date=2021-08-17}}</ref> The latest draft was released on 8 June 2021.<ref>{{cite web|url=https://svgwg.org/svg2-draft/|title=Scalable Vector Graphics (SVG) 2|date=2021-06-08|publisher=World Wide Web Consortium|access-date=2021-08-17}}</ref>
 
−
 
 
−
===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 agent]]s with limited capabilities. In particular, SVG Tiny was defined for highly restricted mobile devices such as [[cellphone]]s; it does not support styling or scripting.<ref name="tiny1.x">{{cite web|title=SVG Tiny 1.2|url=http://www.w3.org/TR/SVGTiny12/intro.html#SVGTiny12|work=Scalable Vector Graphics (SVG) Tiny 1.2 Specification|publisher=[[World Wide Web Consortium|W3C]]|date=2008-12-22|access-date=2014-03-05}}</ref> SVG Basic was defined for higher-level mobile devices, such as [[smartphone]]s.
 
−
 
 
−
In 2003, the [[3GPP]], an international telecommunications standards group, 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.<ref>{{cite web|url=http://www.svgopen.org/2003/paperAbstracts/svgmms.htm|title=SVG in 3GPP Multimedia Messaging and Streaming Services (version March 2003)|publisher=SVG Open|year=2003|access-date=19 October 2009}}</ref><ref>{{cite web|url=https://www.3gpp.org/ftp/Specs/archive/26_series/26.140/26140-520.zip|title=3GPP Multimedia Messaging Service (MMS); Media formats and codecs (Release 5); 3GPP TS 26.140 V5.2.0 (2002-12); Technical Specification|date=2 January 2003|format=[[ZIP (file format)|zipped]] doc|publisher=[[3GPP]]|access-date=25 February 2010|df=dmy-all}}</ref><ref>{{cite web|url=https://www.3gpp.org/ftp/Specs/archive/26_series/26.234/26234-540.zip|title=3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Messaging Service (MMS); Media formats and codecs (Release 5)|work=3GPP TS 26.140 V5.2.0 (2002-12)|date=March 2003|publisher=[[3GPP]]|format=[[ZIP (file format)|zipped]] doc|access-date=24 February 2010|df=dmy-all}}</ref> It was later{{When|date=October 2017}} added as required format for vector graphics in 3GPP [[IP Multimedia Subsystem]] (IMS).<ref>{{cite web|url=http://www.3gpp.org/ftp/Specs/html-info/26141.htm|title=3GPP Specification detail - 3GPP TS 26.141: IP Multimedia System (IMS) Messaging and Presence; Media formats and codecs|date=10 December 2009|publisher=[[3GPP]]|access-date=24 February 2010}}</ref><ref>{{cite web|url=https://www.intelegain.com|title=Building Interactive Websites using Scalable Vector Graphics (SVG) – [With Examples]|publisher=intelegain.com|access-date=21 November 2018|archive-url=https://www.intelegain.com/scalable-vector-graphics/|archive-date=21 November 2018}}</ref>
 
−
 
 
−
====Differences from non-mobile SVG====
 
−
Neither mobile profile includes support for the full Document Object Model (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.<ref>{{cite web|url=http://svg.org/special/svg_phones|title=Listing of phones that support SVG|publisher=Svg.org|access-date=24 October 2010|archive-url=http://webarchive.loc.gov/all/20100108141222/http://www.svg.org/special/svg_phones|archive-date=8 January 2010}}</ref>
 
−
 
 
−
SVGT 1.2 adds a microDOM (μDOM), styling and scripting.<ref name="tiny1.x" />
 
−
 
 
−
===Related work===
 
−
The [[MPEG-4 Part 20]] standard - ''Lightweight Application Scene Representation (LASeR) and Simple Aggregation Format (SAF)'' is based on SVG Tiny.<ref>{{cite web|url=http://mpeg.chiariglione.org/technologies/mpeg-4/mp04-lsr/index.htm|title=MPEG-4 LASeR white paper|date=July 2005|access-date=29 August 2010|publisher=[[International Organization for Standardization]]|first=Cyril|last=Concolato}}</ref> It was developed by [[MPEG]] ([[ISO/IEC JTC1]]/SC29/WG11) and published as ISO/IEC 14496-20:2006.<ref>{{cite web|url=http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=52454|title=ISO/IEC 14496-20:2008 - Information technology – Coding of audio-visual objects – Part 20: Lightweight Application Scene Representation (LASeR) and Simple Aggregation Format (SAF)|publisher=[[International Organization for Standardization]]| access-date=30 October 2009}}</ref> 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.<ref>{{cite web|url=http://www.mpeg-laser.org/documents/LASeRWhitePaper.pdf|title=LASeR - the MPEG standard for Rich Media Services|access-date=11 April 2010}}</ref> SVG was also accommodated in [[MPEG-4 Part 11]], in the [[Extensible MPEG-4 Textual Format|Extensible MPEG-4 Textual (XMT) format]] - a textual representation of the MPEG-4 multimedia content using [[XML]].<ref>{{cite web|url=http://ride.chiariglione.org/bits_and_bytes/bits_and_bytes.htm|title=Riding the media bits - Bits and bytes|first=Leonardo|last=Chiariglione|date=8 March 2005|access-date=30 October 2009|url-status=dead|archive-url=https://web.archive.org/web/20100925220237/http://ride.chiariglione.org/bits_and_bytes/bits_and_bytes.htm|archive-date=25 September 2010|df=dmy-all}}</ref>
 
−
 
 
−
==Functionality==
 
−
The SVG 1.1 specification defines 14 functional areas or feature sets:<ref name="svg11" />
 
−
 
 
−
;Paths
 
−
:Simple or compound shape outlines are drawn with curved or straight lines that can be filled in, outlined, or used as a [[clipping path]]. Paths have a compact coding.
 
−
:For example, <dfn><code>M</code></dfn> (for "move to") precedes initial numeric <var>x</var> and <var>y</var> [[Cartesian coordinate system|coordinates]], and <dfn><code>L</code></dfn> (for "line to") precedes a point to which a line should be drawn. Further command letters (<code>C</code>, <code>S</code>, <code>Q</code>, <code>T</code>, and <code>A</code>) precede data that is used to draw various [[Bézier curve|Bézier]] and [[Ellipse|elliptical]] curves. <code>Z</code> 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.<ref name="path">{{cite web|url=http://www.w3.org/TR/SVG11/paths.html |title=SVG specification, "Paths" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;Basic shapes
 
−
:Straight-line paths and 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 also standard elements.<ref name="shap">{{cite web|url=http://www.w3.org/TR/SVG11/shapes.html |title=SVG specification, "Basic Shapes" |publisher=World Wide Web Consortium|date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;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 (for composing a combination of English and Arabic text, for example), vertical text (as Chinese or Japanese may be written) and characters along a curved path (such as the text around the edge of the [[Great Seal of the United States]]).<ref name="text">{{cite web|url=http://www.w3.org/TR/SVG11/text.html |title=SVG specification, "Text" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;Painting
 
−
:SVG shapes can be filled and outlined (painted with a color, a gradient, or a pattern). Fills may be opaque, or have any degree of transparency.
 
−
:"Markers" are line-end features, such as arrowheads, or symbols that can appear at the vertices of a polygon.<ref name="pntg">{{cite web|url=http://www.w3.org/TR/SVG11/painting.html |title=SVG specification, "Painting: Filling, Stroking and Marker Symbols" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;Color
 
−
:Colors can be applied to all visible SVG elements, either directly or via <code>fill</code>, <code>stroke</code>, and other properties. Colors are specified in the same way as in [[Cascading Style Sheets|CSS2]], i.e. using names like <code>black</code> or <code>blue</code>, in [[hexadecimal]] such as <code>#2f0</code> or <code>#22ff00</code>, in decimal like <code>rgb(255,255,127)</code>, or as percentages of the form <code>rgb(100%,100%,50%)</code>.<ref name="colr">{{cite web|url=http://www.w3.org/TR/SVG11/color.html |title=SVG specification, "Color" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;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 <code>x</code> and <code>y</code> directions. Gradients and patterns can be animated and scripted.<ref name="patt">{{cite web|url=http://www.w3.org/TR/SVG11/pservers.html |title=SVG specification, "Gradients and Patterns" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
:Since 2008, there has been discussion<ref>{{cite web
 
−
|url=http://www.w3.org/2008/11/17-svg-irc
 
−
|title=IRC log of svg on 2008-11-17
 
−
|quote=DS: Priorities should be layout, diffusion curves, 2.5D and make sure we work well with CSS on that
 
−
|publisher=W3C
 
−
|year=2008
 
−
|access-date=25 May 2009}}</ref><ref>{{cite web
 
−
|url=http://lists.w3.org/Archives/Public/www-svg/2009Mar/0084.html
 
−
|title=Propositions for the next SVG spec
 
−
|quote=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.
 
−
|publisher=W3C
 
−
|date=16 March 2009
 
−
|access-date=25 May 2009
 
−
}}</ref> among professional users of SVG that either [[Image gradient|gradient]] [[Color gradient#gradient mesh|meshes]] or preferably [[diffusion curve]]s 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"<ref>{{cite web
 
−
|url=http://www.svgopen.org/2008/papers/104-SVG_in_KDE/
 
−
|title=SVG in KDE: Freedom of Beauty
 
−
|last=Rusin
 
−
|first=Zack
 
−
|publisher=SVG Open
 
−
|year=2008
 
−
|access-date=25 May 2009 }}</ref> 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."<ref>{{cite journal
 
−
|title=Diffusion Curves: A Vector Representation for Smooth-Shaded Images
 
−
|url=http://artis.imag.fr/Publications/2008/OBWBTS08/diffusion_curves.pdf
 
−
|last1=Orzan
 
−
|first1=Alexandrina
 
−
|last2=Bousseau |first2=Adrien |last3=Winnemöller |first3=Holger |last4=Barla |first4=Pascal |last5=Thollot |first5=Joëlle |last6=Salesin |first6=David
 
−
|journal=ACM Transactions on Graphics
 
−
|volume=27
 
−
|year=2008
 
−
|doi=10.1145/1360612.1360691
 
−
|access-date=25 May 2009
 
−
}}</ref> The current draft of SVG 2 includes gradient meshes.<ref>{{Cite web
 
−
|url=https://svgwg.org/svg2-draft/pservers.html#MeshGradients
 
−
|title=Scalable Vector Graphics (SVG) 2, W3C Editor's Draft 13 June 2013
 
−
|publisher=SVG WG
 
−
|year=2013
 
−
|access-date=17 September 2013
 
−
}}</ref>
 
−
;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 [[alpha compositing|alpha]] blending.<ref name="mask">{{cite web|url=http://www.w3.org/TR/SVG11/masking.html |title=SVG specification, "Clipping, Masking and Compositing" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;Filter effects<ref name="filt">{{cite web|url=http://www.w3.org/TR/SVG11/filters.html |title=SVG specification, "Filter Effects" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
:{{Main|SVG filter effects}}
 
−
:A filter effect consists of a series of graphics operations that are applied to a given source vector graphic to produce a modified [[bitmapped]] result.
 
−
;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 receptive to user interface [[event (computing)|events]] such as changes in [[focus (computing)|focus]], mouse clicks, scrolling or zooming the image and other pointer, keyboard and document events. Event handlers may start, stop or alter animations as well as trigger scripts in response to such events.<ref name="intr">{{cite web|url=http://www.w3.org/TR/SVG11/interact.html |title=SVG specification, "Interactivity" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;Linking
 
−
:SVG images can contain hyperlinks to other documents, using [[XLink]]. Through the use of the <code><nowiki><view></nowiki></code> element or a [[fragment identifier]], [[URL]]s can link to SVG files that change the visible area of the document. This allows for creating specific view states that are used to zoom in/out of a specific area or to limit the view to a specific element. This is helpful when creating [[Sprite (computer graphics)|sprites]]. [[XLink]] support in combination with the <code><nowiki><use></nowiki></code> element also allow linking to and re-using internal and external elements. This allows coders to do more with less markup and makes for cleaner code.<ref name="link">{{cite web|url=http://www.w3.org/TR/SVG11/linking.html |title=SVG specification, "Linking" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;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 [[JavaScript]] and there are defined [[Document Object Model]] (DOM) objects for every SVG element and attribute. Scripts are enclosed in <code>&lt;script&gt;</code> elements. They can run in response to pointer events, keyboard events and document events as required.<ref name="scrp">{{cite web|url=http://www.w3.org/TR/SVG11/script.html |title=SVG specification, "Scripting" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;Animation
 
−
:{{Main|SVG animation}}
 
−
: SVG content can be animated using the built-in animation elements such as <code>&lt;animate&gt;</code>, <code>&lt;animateMotion&gt;</code> and <code>&lt;animateColor&gt;</code>. Content can be animated by manipulating the DOM using ECMAScript and 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.<ref name="anim">{{cite web|url=http://www.w3.org/TR/SVG11/animate.html |title=SVG specification, "Animation" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;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 [[glyph]]s are defined in SVG as a font that is then referenced from the <code>&lt;text&gt;</code> element.<ref name="font">{{cite web|url=http://www.w3.org/TR/SVG11/fonts.html |title=SVG specification, "Fonts" |publisher=World Wide Web Consortium |date=14 January 2003 |access-date=19 October 2009}}</ref>
 
−
;Metadata
 
−
:In accord with the [[W3C]]'s [[Semantic Web]] initiative, SVG allows authors to provide [[metadata]] about SVG content. The main facility is the <code>&lt;metadata&gt;</code> 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 <code>&lt;title&gt;</code> and <code>&lt;desc&gt;</code> elements where authors may also provide plain-text descriptive material within an SVG image to help indexing, searching and retrieval by a number of means.<ref name="meta">{{cite web|url=http://www.w3.org/TR/SVG11/metadata.html |title=SVG specification, "Metadata" |publisher=World Wide Web Consortium |access-date=19 October 2009}}</ref>
 
−
 
 
−
An SVG document can define components including shapes, gradients etc., and use them repeatedly. SVG images can also contain [[raster graphics]], such as [[Portable Network Graphics|PNG]] and [[JPEG]] images, and further SVG images.
 
−
 
 
−
===Example===
 
−
[[File:SVG example markup grid.svg]]
 
−
<!--
 
−
***********************************
 
−
READ THIS: Please do not edit the SVG markup below! The SVG image included in the article is a static image which will not be updated if this code is modified. Please use https://en.wikipedia.org/wiki/Wikipedia:Sandbox for any test edits you wish to make.
 
−
***********************************
 
−
-->
 
−
 
 
−
This code will produce the colored shapes shown in the image, excluding the grid and labels:
 
−
<syntaxhighlight lang="xml">
 
−
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
 
−
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
 
−
<svg width="391" height="391" viewBox="-70.5 -70.5 391 391" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
 
−
<rect fill="#fff" stroke="#000" x="-70" y="-70" width="390" height="390"/>
 
−
<g opacity="0.8">
 
−
<rect x="25" y="25" width="200" height="200" fill="lime" stroke-width="4" stroke="pink" />
 
−
<circle cx="125" cy="125" r="75" fill="orange" />
 
−
<polyline points="50,150 50,200 200,200 200,100" stroke="red" stroke-width="4" fill="none" />
 
−
<line x1="50" y1="50" x2="200" y2="200" stroke="blue" stroke-width="4" />
 
−
</g>
 
−
</svg>
 
−
</syntaxhighlight>
 
−
 
 
−
== SVG on the web ==
 
−
 
 
−
The use of SVG on the web was limited by the lack of support in older versions of [[Internet Explorer]] (IE). Many websites that serve SVG images also provide the images in a [[Raster graphics|raster format]], either automatically by [[HTTP]] [[content negotiation]] or by allowing the user directly to choose the file.
 
−
 
 
−
[[Google]] announced on 31 August 2010 that it had started to index SVG content on the web, whether it is in standalone files or embedded in [[HTML]], and that users would begin to see such content listed among their search results.<ref>{{cite web|last1=Stanescu|first1=Bogdan|last2=Sarapata|first2=John|url=http://googlewebmastercentral.blogspot.com/2010/08/google-now-indexes-svg.html|title=Google now indexes SVG|work=Webmaster central blog|publisher=Google, Inc|date=31 August 2010|access-date=1 September 2010}}</ref>
 
−
It was announced on 8 December 2010 that [[Google Image Search]] would also begin indexing SVG files.<ref>{{cite web|publisher=Google, Inc|title=googleimages|url=https://www.twitter.com/googleimages/status/12589924704329728|access-date=17 February 2011|date=8 December 2010}}</ref> The site announced an option to restrict image searches to SVG files on 11 February 2011.<ref>{{cite web|last=Singhal|first=Amit|title=This week in search 2/11/11|url=http://googleblog.blogspot.com/2011/02/this-week-in-search-21111.html|publisher=Google, Inc|access-date=17 February 2011|date=11 February 2011}}</ref>
 
−
 
 
−
===Native browser support===
 
−
[[Konqueror]] was the first browser to support SVG in release version 3.2 in February 2004.<ref>{{Cite web |url=http://dot.kde.org/2003/09/16/kde-conquers-vectors-ksvg |title=KDE Conquers the Vectors with KSVG |last=Streichardt |first=Andreas |date=16 September 2003 |work=KDE News |access-date=11 February 2012}}</ref> As of 2011, 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 (Scalable Vector Graphics)|comparison of layout engines]] for further details.
 
−
 
 
−
Some earlier versions of Firefox (e.g. versions between 1.5 and 3.6<ref>{{Cite journal|url=https://bugzilla.mozilla.org/show_bug.cgi?id=276431 |title=Bug 276431 - external SVG not loaded from img tag |publisher=Mozilla}}{{inconsistent cite}}</ref>), as well as a smattering of other now-outdated web browsers capable of displaying SVG graphics, needed them embedded in <code>&lt;object&gt;</code> or <code>&lt;iframe&gt;</code> [[HTML element|elements]] to display them integrated as parts of an HTML webpage instead of using the standard way of integrating images with <code>&lt;img&gt;</code>.<ref>{{cite web|url=http://groups.google.com/group/mozilla.dev.tech.svg/browse_thread/thread/75f14ac7244b0fa5/a6ccf7261c5110b7?lnk=raot|title=SVG image not shown by Firefox|work=mozilla.dev.tech.svg|publisher=[[Google Groups]]|date=25 February 2009|access-date=25 February 2010|author=Lusotec}}</ref> However, SVG images may be included in XHTML pages using [[XML namespace]]s.<ref>{{cite web|url=https://developer.mozilla.org/en/SVG_In_HTML_Introduction|title=SVG In HTML Introduction|publisher=[[Mozilla]]|date=25 August 2008|work=Mozilla Developer Center|author=Brettz9|access-date=25 February 2010|archive-date=5 December 2008|archive-url=https://web.archive.org/web/20081205022530/https://developer.mozilla.org/en/SVG_In_HTML_Introduction|url-status=dead}}</ref>
 
−
 
 
−
[[Tim Berners-Lee]], the inventor of the [[World Wide Web]], was critical of early versions of Internet Explorer for its failure to support SVG.<ref>{{cite news|url=http://www.nbcnews.com/id/26646919|title=Creator of Web spots a flaw in Internet Explorer|agency=Associated Press|date=10 September 2008|first=Peter|last=Svensson|access-date=25 February 2010|publisher=[[NBC News]]}}</ref>
 
−
* [[Opera (web browser)|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. Opera 9.5 has partial SVG Tiny 1.2 support. It also supports SVGZ (compressed SVG).
 
−
* Browsers based on the [[Gecko (layout engine)|Gecko]] [[Browser engine|layout engine]] (such as [[Mozilla Firefox|Firefox]], [[Flock (web browser)|Flock]], [[Camino (web browser)|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<ref>{{cite web|url=https://developer.mozilla.org/en/docs/SVG_in_Firefox|title=SVG in Firefox|work=Mozilla Developer Center|publisher=[[Mozilla]]|date=23 October 2009|access-date=25 February 2010}}</ref> and of the modules which are <!-- This phrase is confusing. Does it mean what modules are in development or or which are not implemented at all?  -->in development.<ref>{{cite web|url=https://www.mozilla.org/projects/svg/status.html|title=Mozilla SVG Status |publisher=[[Mozilla]]|access-date=25 February 2010}}</ref> Gecko 1.9, included in [[Mozilla Firefox 3|Firefox 3.0]], adds support for more of the SVG specification (including filters).<ref>{{cite web|url=https://developer.mozilla.org/en/docs/SVG_improvements_in_Firefox_3|title=SVG improvements in Firefox 3|publisher=[[Mozilla]]|work=Mozilla Developer Center|date=15 January 2008|author=Mgjbot|access-date=25 February 2010}}</ref>
 
−
* [[Pale Moon (web browser)|Pale Moon]], which uses the [[Goanna (software)|Goanna]] layout engine (a fork of the [[Gecko (software)|Gecko]] engine), supports SVG.
 
−
* Browsers based on [[WebKit]] (such as [[Apple Inc.|Apple]]'s [[Safari (web browser)|Safari]], [[Google Chrome]], and [[The Omni Group]]'s [[OmniWeb]]) have had incomplete support for the SVG 1.1 Full specification since 2006.<ref>{{cite web|url=http://webkit.org/projects/svg/status.xml|title=WebKit SVG Status|publisher=[[WebKit]]|date=5 January 2010|access-date=25 February 2010}}</ref>
 
−
* [[Amaya (web browser)|Amaya]] has partial SVG support.
 
−
* [[Internet Explorer 8]] and older versions do not support SVG.<ref>{{cite web|url=http://www.microsoft.com/windowsxp/expertzone/chats/transcripts/08_0619_ez_ie8.mspx|title=Windows Internet Explorer 8 Expert Zone Chat (19 June 2008)|publisher=Microsoft|date=19 June 2008|access-date=24 October 2010}}</ref><ref>{{cite web|url=http://www.codedread.com/svg-support.php|title=SVG Support|last=Schiller|first=Jeff|date=13 February 2010|access-date=25 February 2010}}</ref> IE9 (released 14 March 2011) supports the basic SVG feature set.<ref name="IE9">{{cite web|url=http://msdn.microsoft.com/en-us/library/ff974378(VS.85).aspx|title=What's New in Internet Explorer 9|date=22 March 2011|work=[[Microsoft Developer Network]]|publisher=[[Microsoft]]|access-date=22 March 2011}}</ref> IE10 extended SVG support by adding SVG 1.1 filters.<ref>{{cite web|title=SVG (Windows)|url=https://msdn.microsoft.com/en-us/library/ie/hh673562(v=vs.85).aspx|website=Internet Explorer Dev Center|publisher=[[Microsoft]]|access-date=27 August 2014}}</ref>
 
−
* Microsoft Edge supports <!-- How much does it support? Basic, tiny, or full? 1.1? --> SVG 1.1.<ref>{{cite web|url=https://developer.microsoft.com/en-us/microsoft-edge/platform/status/|title=Microsoft Edge web platform features status and roadmap - Microsoft Edge Development|website=developer.microsoft.com|access-date=19 April 2018}}</ref>
 
−
* The [[Maxthon|Maxthon Cloud Browser]] also supports SVG.{{citation needed|reason=Not mentioned on the Maxthon page|date=March 2015}}
 
−
 
 
−
There are several advantages to native and full support: [[Plug-in (computing)|plugins]] are not needed, SVG can be freely mixed with other content in a single document, and rendering and scripting become considerably more reliable.<ref>{{cite web|url=https://msdn.microsoft.com/en-us/library/ie/hh968248.aspx|publisher=[[Microsoft Developer Network|MSDN]]|title=Get ready for plug-in free browsing|year=2014|access-date=2014-03-05}}</ref>
 
−
 
 
−
===Mobile support===
 
−
SVG Tiny (SVGT) 1.1 and 1.2 are mobile profiles for SVG. SVGT 1.2 includes some features not found in SVG 1.1, including non-scaling strokes, which are supported by some SVG 1.1 implementations, such as Opera, Firefox and WebKit. As shared code bases between desktop and mobile browsers increased, the use of SVG 1.1 over SVGT 1.2 also increased.
 
−
 
 
−
Support for SVG may be limited to SVGT on older or more limited [[Smart Phone|smart phones]] or may be primarily limited by their respective operating system. [[Adobe Flash Lite]] has optionally supported SVG Tiny since version 1.1. At the SVG Open 2005 conference, [[Sun Microsystems|Sun]] demonstrated a mobile implementation of SVG Tiny 1.1 for the [[Connected Limited Device Configuration]] (CLDC) platform.<ref>{{cite web|title=SVG Open 2005 Conference and Exhibition - Proceedings - Cartoon Oriented User Interfaces|url=http://www.svgopen.org/2005/proceedings.html#paper108|publisher=svgopen.org|access-date=29 August 2010}}</ref>
 
−
 
 
−
Mobiles that use [[Opera Mobile]], as well as the [[iPhone]]'s built in browser, also include SVG support. However, even though it used the [[WebKit]] engine, the [[Android (operating system)|Android]] built-in browser did not support SVG prior to v3.0 (Honeycomb).<ref>{{cite web|title=Browser doesn't render SVG images|url=https://code.google.com/p/android/issues/detail?id=1376|access-date=1 January 2011}}</ref> Prior to v3.0, Firefox Mobile 4.0b2 (beta) for Android was the first browser running under Android to support SVG by default.<ref>{{cite web|title=Firefox Mobile 4.0b2 (beta) for Android supports SVG images|url=https://code.google.com/p/android/issues/detail?id=1376#c30|date=2010-12-16|work=[[Android (operating system)|Android]] Issue 1376|access-date=2014-01-29}}</ref>
 
−
 
 
−
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 is sometimes referred to as "SVGT 1.1+", though there is no such standard.
 
−
 
 
−
[[Research In Motion|RIM]]'s [[BlackBerry]] has built-in support for SVG Tiny 1.1 since version 5.0.<ref>{{cite web|title=Support for SVG|url=http://docs.blackberry.com/en/developers/deliverables/11844/Native_SVG_support_887737_11.jsp|publisher=RIM|access-date=6 October 2011}}</ref> Support continues for WebKit-based BlackBerry Torch browser in OS 6 and 7.<ref>{{cite web|title=BlackBerry Torch The HTML5 Developer Scorecard|url=http://www.sencha.com/blog/blackberry-torch-the-html5-developer-scorecard|publisher=[[Sencha]]|access-date=6 October 2011}}</ref>
 
−
 
 
−
[[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 [[Application programming interface|API]] expert group that defines [[Java Platform, Micro Edition|Java ME]] API for SVG presentation and manipulation. This API has been implemented in S60 Platform 3rd Edition Feature Pack 1 and onward.<ref>{{cite web|url=http://www.s60.com/business/productinfo/applicationsandtechnologies/java/supportedfeaturesin3rdedition|title=S60 Product info|archive-url=https://web.archive.org/web/20071013152026/http://www.s60.com/business/productinfo/applicationsandtechnologies/java/supportedfeaturesin3rdedition|archive-date=13 October 2007|publisher=S60.com|access-date=19 October 2009}}</ref> Some [[Series 40 (software platform)|Series 40 phones]] also support SVG (such as [[Nokia 6280]]).
 
−
 
 
−
Most [[Sony Ericsson]] phones beginning with [[Sony Ericsson K700|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|Sony Ericsson Java Platform-8]] have support for JSR 226.
 
−
 
 
−
[[Windows Phone]] has supported SVG since version 7.5.
 
−
 
 
−
SVG is also supported on various mobile devices from [[Motorola]], [[Samsung]], [[LG]], and [[Siemens mobile]]/[[BenQ-Siemens]]. eSVG, an SVG rendering library mainly written for [[Embedded system|embedded]] devices, is available on some mobile platforms.<ref>{{Cite web|url=http://www.svgopen.org/2002/papers/jezic__esvg/|access-date=5 April 2012|title=SVG for Embedded Systems|first=Damir|last=Jezic|date=15–17 July 2002|publisher=svgopen.org|work=Zurich 2002}}</ref><ref>{{cite web|url=http://www.intesis.hr/products/esvg|title=eSVG|work=Intesis Intelligent Embedded Software|year=2010|access-date=2014-01-29}}</ref>
 
−
 
 
−
==Application support==
 
−
SVG images can be produced by the use of a [[vector graphics editor]], such as [[Inkscape]], [[Adobe Illustrator]], [[Adobe Flash Professional]], or [[CorelDRAW]], and rendered to common [[Raster graphics|raster]] image formats such as [[Portable Network Graphics|PNG]] using the same software. Additionally, editors like [[Inkscape]] and [[Boxy SVG]] provide tools to trace raster images to [[Bézier curve]]s typically using [[image tracing]] back-ends like [[potrace]],<ref name="selinger">{{cite web|url=http://potrace.sourceforge.net/|last=Selinger|first=Peter|year=2001–2013|title=Potrace – Transforming bitmaps into vector graphics|work=[[SourceForge]] project [[Potrace]]|access-date=2014-01-29}}</ref><ref>{{cite web|url=http://wiki.inkscape.org/wiki/index.php/Tools#Vectorize.2Ftrace|title=Vectorize/trace|work=Inkscape wiki|year=2012|access-date=2014-01-29}}</ref> [https://github.com/autotrace/autotrace autotrace], and [https://github.com/jankovicsandras/imagetracerjs imagetracerjs].
 
−
 
 
−
Software can be programmed to render SVG images by using a [[library (computing)|library]] such as [[librsvg]] used by [[GNOME]] since 2000, [[Batik (software)|Batik]] or [https://www.thorvg.org/ ThorVG] since 2020 for the lightweight systems. SVG images can also be rendered to any desired popular image format by using [[ImageMagick]], a free command-line utility (which also uses librsvg under the hood).
 
−
 
 
−
For web-based applications, the mode of usage termed [https://www.w3.org/wiki/SVG_Security#Inline_SVG Inline SVG] allows SVG content to be embedded within an HTML document using an <code>&lt;svg&gt;</code> tag. Its graphical capabilities can then be employed to create sophisticated user interfaces as the SVG and HTML share context, event handling, and CSS.
 
−
 
 
−
Other uses for SVG include embedding for use in [[word processing]] (e.g. with [[LibreOffice]]) and [[desktop publishing]] (e.g. [[Scribus]]), [[Plot (graphics)|plotting graphs]] (e.g. [[gnuplot]]), and importing paths (e.g. for use in [[GIMP]] or [[Blender (software)|Blender]]). The application services [[Microsoft 365]] and [[Microsoft Office 2019]] offer support for exporting,<ref>{{Cite web|date=September 2019|title=What's new in PowerPoint for Microsoft 365|url=https://support.microsoft.com/en-us/office/what-s-new-in-powerpoint-for-microsoft-365-e8ef980c-5b12-4fff-ae3f-0819e6a21a1f|url-status=live|archive-url=https://web.archive.org/web/20210313183903/https://support.microsoft.com/en-us/office/what-s-new-in-powerpoint-for-microsoft-365-e8ef980c-5b12-4fff-ae3f-0819e6a21a1f|archive-date=2021-03-13|access-date=2021-04-17|website=support.microsoft.com|language=en-US}}</ref> importing and editing SVG images. The [[Uniform Type Identifier]] for SVG used by Apple is <code>public.svg-image</code> and conforms to <code>public.image</code> and <code>public.xml</code>.
 
−
 
 
−
==Security==
 
−
It is common to see SVG described as an image format, but it is actually a document format, similar to HTML documents, and so can host script or CSS. The main security issues occur if SVG files are naively treated as image files because they can harbour malicious content. For instance, if they are deployed as a CSS background image, or a logo on some website, or in some image gallery then such content could be activated. At the very least, this could lock-up your browser (the so-called [[Billion laughs attack]]), but could also lead to [[Code injection|HTML Injection]] and [[Cross-site_scripting]] attacks. The W3C therefore stipulate certain requirements when SVG is simply used for images: [https://www.w3.org/wiki/SVG_Security SVG Security].
 
−
 
 
−
However, [https://www.w3.org/wiki/SVG_Security#Inline_SVG Inline SVG] is considered less of a security risk because the content is part of a greater document, and so scripting and CSS would not be unexpected.
 
−
 
 
−
==See also==
 
−
{{SVGSeries}}
 
−
* [[Canvas element]]
 
−
* [[Comparison of graphics file formats]]
 
−
* [[Comparison of raster-to-vector conversion software]]
 
−
* [[Comparison of vector graphics editors]]
 
−
* [[Computer graphics]]
 
−
* [[Computer Graphics Metafile]]
 
−
* [[Image file formats]]
 
−
* [[Resolution independence]]
 
−
* [[Commons:Help:SVG#SVG files in MediaWiki|SVG files in MediaWiki]] on [[Commons:Help:SVG|Commons: Help:SVG]]
 
−
 
 
−
==References==
 
−
{{Reflist}}
 
−
 
 
−
==External links==
 
−
{{sisterlinks|d=y|c=Category:SVG|mw=SVG|b=XML - Managing Data Exchange/SVG|wikt=SVG|v=Vector Drawing|m=SVG|s=no|n=no|q=no}}
 
−
* {{Official website|http://www.w3.org/Graphics/SVG|W3C SVG page}} specifications, list of implementations
 
−
* [http://www.w3.org/Graphics/SVG/IG/resources/svgprimer.html W3C SVG primer] W3C Primer (draft) under auspices of SVG Interest Group
 
−
 
 
−
{{W3C Standards}}
 
−
{{vector graphics markup languages}}
 
−
{{Graphics file formats}}
 
−
{{SVG Plugins}}
 
−
{{Web interfaces}}
 
−
 
 
−
{{Authority control}}
 
−
 
 
−
[[Category:Scalable Vector Graphics| ]]
 
−
[[Category:Articles with example code]]
 
−
[[Category:Computer file formats]]
 
−
[[Category:Graphics file formats]]
 
−
[[Category:HTML5]]
 
−
[[Category:Open formats]]
 
−
[[Category:Page description markup languages]]
 
−
<!-- the "| " sorts before "A" in cat -->
 
−
[[Category:Vector graphics markup languages]]
 
−
[[Category:World Wide Web Consortium standards]]
 
−
[[Category:XML markup languages]]
 
−
[[Category:Computer-related introductions in 2001]]
 

Latest revision as of 22:56, 23 February 2022

Retrieved from "https://wiki.tachyony.co.uk/w/index.php?title=Scalable_Vector_Graphics&oldid=11922"