Misplaced Pages

SVG

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

Scalable Vector Graphics ( SVG ) is an XML -based vector image format for defining two-dimensional graphics, having support for interactivity and animation. The SVG specification is an open standard developed by the World Wide Web Consortium since 1999.

#185814

38-577: SVG images are defined in a vector graphics format and stored in XML text files. SVG images can thus be scaled in size without loss of quality, and SVG files can be searched , indexed , scripted , and compressed . The XML text files can be created and edited with text editors or vector graphics editors , and are rendered by most web browsers . If used for images, SVG can host scripts or CSS, potentially leading to cross-site scripting attacks or other security vulnerabilities. SVG has been in development within

76-441: A .smi or .smil file extension. However, SAMI files and Macintosh self mounting images also use .smi , which creates some ambiguity at first glance. As a result, SMIL files commonly use the .smil file extension to avoid confusion. SMIL was created during a time when structured data using XML was very popular and during a time when Internet Explorer was very popular. Thus "combining" SMIL with other markup languages

114-452: A scripting language (e.g. JavaScript ). The W3C explicitly recommends SMIL as the standard for animation in SVG. A rich set of event handlers such as "onmouseover" and "onclick" can be assigned to any SVG graphical object to apply actions and events. Because of industry demand, two mobile profiles were introduced with SVG 1.1: SVG Tiny (SVGT) and SVG Basic (SVGB). These are subsets of

152-467: A voice browser , while combining SMIL with MusicXML would allow for the creation of infinitely-recombinable sequences of music sheets. Combining SMIL+VoiceXML or SMIL+MusicXML with RSS or Atom could be useful in the creation of an audible pseudo-podcast with embedded hyperlinks, while combining SMIL+SVG with VoiceXML and/or MusicXML would be useful in the creation of an automatically audio-enabled vector graphics animation with embedded hyperlinks. SMIL

190-632: A W3C Recommendation on 13 December 2005. n SMIL 2.1 includes a small number of extensions based on practical experience gathered using SMIL in the Multimedia Messaging System on mobile phones. SMIL 3.0 became a W3C Recommendation in December 2008. It was first submitted as a W3C Working draft on December 21, 2006. The last draft revision was released on October 6, 2008. Authoring and rendering tools for smilText and SMIL 3.0 PanZoom functionality : Demos A SMIL document

228-604: A W3C Recommendation on 9 August 2001. SMIL 2.0 introduced a modular language structure that facilitated integration of SMIL semantics into other XML-based languages. Basic animation and timing modules were integrated into Scalable Vector Graphics ( SVG ) and the SMIL modules formed a basis for Timed-Text . The modular structure made it possible to define the standard SMIL language profile and the XHTML+SMIL language profile with common syntax and standard semantics. SMIL 2.1 became

266-533: A few other, now outdated, web browsers capable of displaying SVG graphics, needed them embedded in <object> or <iframe> elements to display them integrated as parts of an HTML webpage instead of using the standard way of integrating images with <img> . However, SVG images may be included in XHTML pages using XML namespaces . Tim Berners-Lee , the inventor of the World Wide Web ,

304-837: A free command-line utility (which also uses librsvg under the hood). For web-based applications, the mode of usage termed Inline SVG allows SVG content to be embedded within an HTML document using an <svg> 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 ), plotting graphs (e.g. gnuplot ), and importing paths (e.g. for use in GIMP or Blender ). The application services Microsoft 365 and Microsoft Office 2019 offer support for exporting, importing and editing SVG images. The Uniform Type Identifier for SVG used by Apple

342-486: A logo on some website, or in some image gallery, then when the image is loaded in a browser it activates a script or other content. This could lock up the browser (the Billion laughs attack ), but could also lead to HTML injection and cross-site scripting attacks. The W3C therefore stipulate certain requirements when SVG is simply used for images: SVG Security. The W3C says that Inline SVG (an SVG file loaded natively on

380-618: A website) 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. The MPEG-4 Part 20 standard - Lightweight Application Scene Representation (LASeR) and Simple Aggregation Format (SAF) is based on SVG Tiny. It was developed by MPEG ( ISO/IEC JTC 1 /SC29/WG11) and published as ISO/IEC 14496-20:2006. 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. SVG

418-400: Is public.svg-image and conforms to public.image and public.xml . As a document format, similar to HTML documents, SVG can host scripts or CSS. This is an issue when an attacker can upload a SVG file to a website, such as a profile picture, and the file is treated as a normal picture but contains malicious content. For instance, if an SVG file is deployed as a CSS background image, or

SECTION 10

#1732780467186

456-405: Is a World Wide Web Consortium recommended Extensible Markup Language (XML) markup language to describe multimedia presentations. It defines markup for timing, layout, animations, visual transitions, and media embedding, among other things. SMIL allows presenting media items such as text, images, video, audio, links to other SMIL presentations, and files from multiple web servers. SMIL markup

494-457: 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 devices, is available on some mobile platforms. SVG images can be hand coded or produced by the use of a vector graphics editor, such as Inkscape , Adobe Illustrator , Adobe Flash Professional , or CorelDRAW , and rendered to common raster image formats such as PNG using

532-470: Is an XML-based application, and is a part of many Multimedia Messaging Service (MMS) applications. SMIL can be combined with other XML-based specifications such as with SVG (as has been done with SVG animation ) and with XHTML (as done with HTML+TIME ). As of 2008 , the W3C Recommendation for SMIL is SMIL 3.0 . SMIL 1.0 became a W3C Recommendation on 15 June 1998. SMIL 2.0 became

570-625: Is anticipated for use within Text Encoding Initiative (TEI) documents. SMIL is being implemented on handheld and mobile devices and has also spawned the Multimedia Messaging Service (MMS) which is a video and picture equivalent of Short Message Service (SMS). SMIL is also one of the underlying technologies used for " Advanced Content " in the (discontinued) HD DVD format for adding interactive content (menus etc.). The field of Digital Signage

608-586: Is embracing SMIL as a means of controlling dynamic advertising in public areas. Most commonly used web browsers have native support for SMIL, but it has not been implemented in Microsoft browsers. It was to be deprecated in Google Chrome, but it has now been decided to suspend that intent until alternatives are sufficiently developed. Other software that implement SMIL playback include: Media player boxes based on dedicated 1080p decoder chips such as

646-935: Is similar in structure to an HTML document in that they are typically divided between an optional <head> section and a required <body> section. The <head> section contains layout and metadata information. The <body> section contains the timing information, and is generally composed of combinations of three main tags—sequential (" <seq> ", simple playlists), parallel (" <par> ", multi-zone/multi-layer playback) and exclusive (" <excl> ", event-triggered interrupts). SMIL refers to media objects by URLs , allowing them to be shared between presentations and stored on different servers for load balancing . The language can also associate different media objects with different bandwidth requirements. For playback scheduling, SMIL supports ISO-8601 wallclock() date/time specification to define begin/end events for playlists. SMIL files take either

684-439: Is the required vector graphics format and support of SVGB is optional for Multimedia Messaging Service (MMS) and Packet-switched Streaming Service. It was later added as required format for vector graphics in 3GPP IP Multimedia Subsystem (IMS). 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

722-420: Is typically 20 to 50 percent of the original size. W3C provides SVGZ files to test for conformance. The SVG 1.1 specification defines 14 functional areas or feature sets: An SVG document can define components including shapes, gradients etc., and use them repeatedly. SVG images can also contain raster graphics , such as PNG and JPEG images, and further SVG images. [REDACTED] This code will produce

760-587: Is written in XML, and has similarities to HTML . Members of the World Wide Web Consortium (also known as the "W3C") created SMIL for streaming media presentations, and published SMIL 1.0 in June 1998. Many of these W3C members helped author several versions of SMIL specifications between 1996 (when the first multimedia workshops were hosted by the W3C) and 2008 (when SMIL 3.0 was published). SMIL

798-589: 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). 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. SVG was developed by the W3C SVG Working Group starting in 1998, after six competing vector graphics submissions were received that year: The working group

SECTION 20

#1732780467186

836-699: The SVG Open 2005 conference, Sun demonstrated a mobile implementation of SVG Tiny 1.1 for the Connected Limited Device Configuration (CLDC) platform. 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 built-in browser did not support SVG prior to v3.0 (Honeycomb). Prior to v3.0, Firefox Mobile 4.0b2 (beta) for Android

874-664: The SVG XML elements or via scripting that accesses the SVG Document Object Model (DOM). SVG uses CSS for styling and JavaScript for scripting. Text, including internationalization and localization , appearing in plain text within the SVG DOM, enhances the accessibility of SVG graphics. Though the SVG Specification primarily focuses on vector graphics markup language , its design includes

912-459: The basic capabilities of a page description language like Adobe's PDF . It contains provisions for rich graphics, and is compatible with CSS for styling purposes. SVG has the information needed to place each glyph and image in a chosen location on a printed page. SVG drawings can be dynamic and interactive. Time-based modifications to the elements can be described in SMIL , or can be programmed in

950-799: The colored shapes shown in the image, excluding the grid and labels: 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 format , either automatically by HTTP content negotiation or by allowing the user directly to choose the file. Konqueror was the first browser to support SVG in release version 3.2 in February 2004. 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 for further details. Some earlier versions of Firefox (e.g. versions between 1.5 and 3.6), as well as

988-417: The combination of multimedia-laden .smil files with RSS or Atom syndication would be useful for accessibility to audio-enabled podcasts by the deaf through Timed Text closed captions, and can also turn multimedia into hypermedia that can be hyperlinked to other linkable audio and video multimedia. VoiceXML can be combined with SMIL to provide a sequential reading of several pre-provided pages or slides in

1026-470: 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 ; it does not support styling or scripting. SVG Basic was defined for higher-level mobile devices, such as smartphones . In 2003, the 3GPP , an international telecommunications standards group, adopted SVG Tiny as the mandatory vector graphics media format for next-generation phones. SVGT

1064-413: The full standard, most SVG graphics can still be rendered by devices which only support the mobile profiles. SVGT 1.2 adds a microDOM (μDOM), styling and scripting. SVGT 1.2 also 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,

1102-736: The platform's SVG engine. Nokia has also led the JSR 226: Scalable 2D Vector Graphics API expert group that defines Java ME API for SVG presentation and manipulation. This API has been implemented in S60 Platform 3rd Edition Feature Pack 1 and onward. 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. Windows Phone has supported SVG since version 7.5. SVG

1140-502: The same software. Additionally, editors like Inkscape and Boxy SVG provide tools to trace raster images to Bézier curves typically using image tracing back-ends like potrace , autotrace, and imagetracerjs. Software can be programmed to render SVG images by using a library such as librsvg used by GNOME since 2000, Batik and ThorVG (Thor Vector Graphics) since 2020 for lightweight systems. SVG images can also be rendered to any desired popular image format by using ImageMagick ,

1178-413: The use of SVG 1.1 over SVGT 1.2 also increased. SVG images, being XML, contain many repeated fragments of text, so they are well suited for 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 .svgz filename extension. Conforming SVG 1.1 viewers will display compressed images. An SVGZ file

SVG - Misplaced Pages Continue

1216-902: 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 . Scale (ratio) Too Many Requests If you report this error to the Wikimedia System Administrators, please include the details below. Request from 172.68.168.133 via cp1102 cp1102, Varnish XID 575569964 Upstream caches: cp1102 int Error: 429, Too Many Requests at Thu, 28 Nov 2024 07:54:27 GMT Synchronized Multimedia Integration Language Synchronized Multimedia Integration Language ( SMIL ( / s m aɪ l / ))

1254-806: Was chaired at the time by Chris Lilley of the W3C. Early adoption was limited due to lack of support in older versions of Internet Explorer. However, as of 2011, all major desktop browsers began to support SVG. Native browser support offers various advantages, such as not requiring plugins, allowing SVG to be mixed with other content, and improving rendering and scripting reliability. Mobile support for SVG exists in various forms, with different devices and browsers supporting SVG Tiny 1.1 or 1.2. SVG can be produced using vector graphics editors and rendered into raster formats. In web-based applications, Inline SVG allows embedding SVG content within HTML documents. The SVG specification

1292-487: Was considered one of the best current practices of the day. SMIL is one of three means by which SVG animation can be achieved (the others being JavaScript and CSS animations ). While RSS and Atom are web syndication methods, with the former being more popular as a syndication method for podcasts , SMIL is potentially useful as a script or playlist that can tie sequential pieces of multimedia together and can then be syndicated through RSS or Atom. In addition,

1330-518: Was critical of early versions of Internet Explorer for its failure to support SVG. 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. Support for SVG may be limited to SVGT on older or more limited 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

1368-892: Was released on 08 March 2023. SVG supports interactivity, animation, and rich graphical capabilities, making it suitable for both web and print applications. SVG images can be compressed with the gzip algorithm, resulting in SVGZ files that are typically 20–50% smaller than the original. SVG also supports metadata, enabling better indexing, searching, and retrieval of SVG content. SVG allows three types of graphic objects: vector graphic shapes (such as paths consisting of straight lines and curves), bitmap images, and text. Graphical objects can be grouped, styled, transformed and composited into previously rendered objects. The feature set includes nested transformations , clipping paths , alpha masks , filter effects and template objects. SVG drawings can be interactive and can include animation , defined in

1406-672: Was the first browser running under Android to support SVG by default. 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. RIM 's BlackBerry has built-in support for SVG Tiny 1.1 since version 5.0. Support continues for WebKit-based BlackBerry Torch browser in OS 6 and 7. Nokia 's S60 platform has built-in support for SVG. For example, icons are generally rendered using

1444-580: Was updated to version 1.1 in 2011. Scalable Vector Graphics 2 became a 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. SVG 2 removes or deprecates some features of SVG 1.1 and incorporates new features from HTML5 and Web Open Font Format : SVG 2 reached the Candidate Recommendation stage on 15 September 2016, and revised versions were published on 7 August 2018 and 4 October 2018. The latest draft

#185814