entities.html revision db9dfd9e532f40416ba17de85221f7f67bad31d8
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd"> 2<html> 3<head> 4<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> 5<style type="text/css"><!-- 6TD {font-size: 10pt; font-family: Verdana,Arial,Helvetica} 7BODY {font-size: 10pt; font-family: Verdana,Arial,Helvetica; margin-top: 5pt; margin-left: 0pt; margin-right: 0pt} 8H1 {font-size: 16pt; font-family: Verdana,Arial,Helvetica} 9H2 {font-size: 14pt; font-family: Verdana,Arial,Helvetica} 10H3 {font-size: 12pt; font-family: Verdana,Arial,Helvetica} 11A:link, A:visited, A:active { text-decoration: underline } 12--></style> 13<title>Entities or no entities</title> 14</head> 15<body bgcolor="#8b7765" text="#000000" link="#000000" vlink="#000000"> 16<table border="0" width="100%" cellpadding="5" cellspacing="0" align="center"><tr> 17<td width="180"> 18<a href="http://www.gnome.org/"><img src="smallfootonly.gif" alt="Gnome Logo"></a><a href="http://www.w3.org/Status"><img src="w3c.png" alt="W3C Logo"></a><a href="http://www.redhat.com/"><img src="redhat.gif" alt="Red Hat Logo"></a> 19</td> 20<td><table border="0" width="90%" cellpadding="2" cellspacing="0" align="center" bgcolor="#000000"><tr><td><table width="100%" border="0" cellspacing="1" cellpadding="3" bgcolor="#fffacd"><tr><td align="center"> 21<h1>The XML C library for Gnome</h1> 22<h2>Entities or no entities</h2> 23</td></tr></table></td></tr></table></td> 24</tr></table> 25<table border="0" cellpadding="4" cellspacing="0" width="100%" align="center"><tr><td bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="2" width="100%"><tr> 26<td valign="top" width="200" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td> 27<table width="100%" border="0" cellspacing="1" cellpadding="3"> 28<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Main Menu</b></center></td></tr> 29<tr><td bgcolor="#fffacd"><ul style="margin-left: -2pt"> 30<li><a href="index.html">Home</a></li> 31<li><a href="intro.html">Introduction</a></li> 32<li><a href="FAQ.html">FAQ</a></li> 33<li><a href="docs.html">Documentation</a></li> 34<li><a href="bugs.html">Reporting bugs and getting help</a></li> 35<li><a href="help.html">How to help</a></li> 36<li><a href="downloads.html">Downloads</a></li> 37<li><a href="news.html">News</a></li> 38<li><a href="XML.html">XML</a></li> 39<li><a href="XSLT.html">XSLT</a></li> 40<li><a href="architecture.html">libxml architecture</a></li> 41<li><a href="tree.html">The tree output</a></li> 42<li><a href="interface.html">The SAX interface</a></li> 43<li><a href="xmldtd.html">Validation & DTDs</a></li> 44<li><a href="xmlmem.html">Memory Management</a></li> 45<li><a href="encoding.html">Encodings support</a></li> 46<li><a href="xmlio.html">I/O Interfaces</a></li> 47<li><a href="catalog.html">Catalog support</a></li> 48<li><a href="library.html">The parser interfaces</a></li> 49<li><a href="entities.html">Entities or no entities</a></li> 50<li><a href="namespaces.html">Namespaces</a></li> 51<li><a href="upgrade.html">Upgrading 1.x code</a></li> 52<li><a href="threads.html">Thread safety</a></li> 53<li><a href="DOM.html">DOM Principles</a></li> 54<li><a href="example.html">A real example</a></li> 55<li><a href="contribs.html">Contributions</a></li> 56<li> 57<a href="xml.html">flat page</a>, <a href="site.xsl">stylesheet</a> 58</li> 59</ul></td></tr> 60</table> 61<table width="100%" border="0" cellspacing="1" cellpadding="3"> 62<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Related links</b></center></td></tr> 63<tr><td bgcolor="#fffacd"><ul style="margin-left: -2pt"> 64<li><a href="http://mail.gnome.org/archives/xml/">Mail archive</a></li> 65<li><a href="http://xmlsoft.org/XSLT/">XSLT libxslt</a></li> 66<li><a href="http://www.cs.unibo.it/~casarini/gdome2/">DOM gdome2</a></li> 67<li><a href="ftp://xmlsoft.org/">FTP</a></li> 68<li><a href="http://www.fh-frankfurt.de/~igor/projects/libxml/">Windows binaries</a></li> 69<li><a href="http://garypennington.net/libxml2/">Solaris binaries</a></li> 70<li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml">Bug Tracker</a></li> 71</ul></td></tr> 72</table> 73</td></tr></table></td> 74<td valign="top" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%"><tr><td><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table border="0" cellpadding="3" cellspacing="1" width="100%"><tr><td bgcolor="#fffacd"> 75<p>Entities in principle are similar to simple C macros. An entity defines an 76abbreviation for a given string that you can reuse many times throughout the 77content of your document. Entities are especially useful when a given string 78may occur frequently within a document, or to confine the change needed to a 79document to a restricted area in the internal subset of the document (at the 80beginning). Example:</p> 81<pre>1 <?xml version="1.0"?> 822 <!DOCTYPE EXAMPLE SYSTEM "example.dtd" [ 833 <!ENTITY xml "Extensible Markup Language"> 844 ]> 855 <EXAMPLE> 866 &xml; 877 </EXAMPLE></pre> 88<p>Line 3 declares the xml entity. Line 6 uses the xml entity, by prefixing 89its name with '&' and following it by ';' without any spaces added. There 90are 5 predefined entities in libxml allowing you to escape charaters with 91predefined meaning in some parts of the xml document content: 92<strong>&lt;</strong> for the character '<', <strong>&gt;</strong> 93for the character '>', <strong>&apos;</strong> for the character ''', 94<strong>&quot;</strong> for the character '"', and 95<strong>&amp;</strong> for the character '&'.</p> 96<p>One of the problems related to entities is that you may want the parser to 97substitute an entity's content so that you can see the replacement text in 98your application. Or you may prefer to keep entity references as such in the 99content to be able to save the document back without losing this usually 100precious information (if the user went through the pain of explicitly 101defining entities, he may have a a rather negative attitude if you blindly 102susbtitute them as saving time). The <a href="html/libxml-parser.html#XMLSUBSTITUTEENTITIESDEFAULT">xmlSubstituteEntitiesDefault()</a> 103function allows you to check and change the behaviour, which is to not 104substitute entities by default.</p> 105<p>Here is the DOM tree built by libxml for the previous document in the 106default case:</p> 107<pre>/gnome/src/gnome-xml -> /xmllint --debug test/ent1 108DOCUMENT 109version=1.0 110 ELEMENT EXAMPLE 111 TEXT 112 content= 113 ENTITY_REF 114 INTERNAL_GENERAL_ENTITY xml 115 content=Extensible Markup Language 116 TEXT 117 content=</pre> 118<p>And here is the result when substituting entities:</p> 119<pre>/gnome/src/gnome-xml -> /tester --debug --noent test/ent1 120DOCUMENT 121version=1.0 122 ELEMENT EXAMPLE 123 TEXT 124 content= Extensible Markup Language</pre> 125<p>So, entities or no entities? Basically, it depends on your use case. I 126suggest that you keep the non-substituting default behaviour and avoid using 127entities in your XML document or data if you are not willing to handle the 128entity references elements in the DOM tree.</p> 129<p>Note that at save time libxml enforces the conversion of the predefined 130entities where necessary to prevent well-formedness problems, and will also 131transparently replace those with chars (i.e. it will not generate entity 132reference elements in the DOM tree or call the reference() SAX callback when 133finding them in the input).</p> 134<p> 135<span style="background-color: #FF0000">WARNING</span>: handling entities 136on top of the libxml SAX interface is difficult!!! If you plan to use 137non-predefined entities in your documents, then the learning cuvre to handle 138then using the SAX API may be long. If you plan to use complex documents, I 139strongly suggest you consider using the DOM interface instead and let libxml 140deal with the complexity rather than trying to do it yourself.</p> 141<p><a href="mailto:daniel@veillard.com">Daniel Veillard</a></p> 142</td></tr></table></td></tr></table></td></tr></table></td> 143</tr></table></td></tr></table> 144</body> 145</html> 146