Lines Matching full:application

97     <para>The tutorial is based on a simple <acronym>XML</acronym> application I
125     <para><application>Libxml</application> declares a number of data types we
139 	      UTF-8 for use with <application>libxml's</application>
141 …url="http://www.xmlsoft.org/encoding.html"><application>libxml</application> encoding support web …
219 	    was not, <application>libxml</application> will at this point
229 	    declaration is there, <application>libxml</application> will
288 	    looking for. It uses the <application>libxml</application> string
343     <application>Libxml2</application> includes support for
344       use of <application>XPath</application> expressions to retrieve sets of
346       <application>XPath</application> <acronym>API</acronym> is <ulink
349     <para><application>XPath</application> allows searching through a document
354 	<para>A full discussion of <application>XPath</application> is beyond
360     <para>Using <application>XPath</application> requires setting up an
361       xmlXPathContext and then supplying the <application>XPath</application>
365       <application>XPath</application> expression.</para>
389 	  <para>Apply the <application>XPath</application> expression.</para>
589       general and <application>libxml</application> in particular. Thinking
590       through the design of your application in light of this issue will help
591       avoid difficulties later. Internally, <application>libxml</application>
594       converted to UTF-8 before passing it to <application>libxml</application>
598       <para><application>Libxml</application> uses
599       <application>iconv</application> if it is available to convert
600     data. Without <application>iconv</application>, only UTF-8, UTF-16 and
602     <application>iconv</application>, any format can be used provided
603     <application>iconv</application> is able to convert it to and from
604     UTF-8. Currently <application>iconv</application> supports about 150
607     <application>iconv</application> implementation is almost guaranteed to
612 	in different parts of one's code. The most common case is an application
614 	<application>libxml</application>, which assumes UTF-8 to be the
615 	internal data format. The result is an application that treats internal
630       <application>libxml's</application>
659 	    <application>libxml's</application> built-in set of conversion
667 	  separately by the application.</para>
683       <application>Libxml</application> includes a script,
684     <application>xml2-config</application>, that can be used to generate