Lines Matching +full:use +full:- +full:external +full:- +full:names
1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
6 <!-- Copyright 1999,2000 Clark Cooper <coopercc@netheaven.com>
9 the terms of the MIT/X License -->
12 <meta http-equiv="Content-Style-Type" content="text/css" />
31 other open-source XML parsers.</p>
34 groff (an nroff look-alike), Jade (an implemention of ISO's DSSSL
155 <p>Expat is a stream-oriented parser. You register callback (or
227 Depth--;
245 convention may be something other than "cdecl". To use the annotation
279 Developer Studio installed, then from Windows Explorer double-click on
284 contains the "expat.h" include file and a pre-built DLL.</p>
302 only one we'll mention here is the <code>--prefix</code> option. You
304 the <code>--help</code> option.</p>
309 give the option, <code>--prefix=/home/me/mystuff</code>, then the
314 <h3>Configuring Expat Using the Pre-Processor</h3>
317 pre-processor definitions. The definition of this symbols does not
322 <dl class="cpp-symbols">
324 <dd>Include support for using and reporting DTD-based content. If
325 this is defined, default attribute values from an external DTD subset
327 type of attributes defined in the external subset. Without
329 not load external entities or process conditional sections. This does
334 "http://www.w3.org/TR/REC-xml-names/" >Namespaces in XML</a></cite>
339 encoded in UTF-16 using wide characters of the type
387 compiler and linker, all you have to do to use Expat in your programs
391 usually be done with the <code>-lexpat</code> argument. Otherwise,
397 <p>On a Unix-based system, here's what a Makefile might look like when
403 LIBS= -lexpat
405 $(CC) $(LDFLAGS) -o xmlapp xmlapp.o $(LIBS)
413 CFLAGS= -I/home/me/mystuff/include
415 LIBS= -L/home/me/mystuff/lib -lexpat
417 $(CC) $(LDFLAGS) -o xmlapp xmlapp.o $(LIBS)
434 constructing a parser for a top-level document. The object returned
444 parsing only one XML document or external parsed entity. If your
470 1, then you can use the same variable for skip flag and skip
476 info->skip = 0;
477 info->depth = 1;
485 if (! inf->skip) {
487 inf->skip = inf->depth;
493 inf->depth++;
500 inf->depth--;
502 if (! inf->skip)
505 if (inf->skip == inf->depth)
506 inf->skip = 0;
540 common first-time mistake with any of the event-oriented interfaces to
549 <!-- XXX example needed here -->
555 the value of the <code>version</code> pseudo-attribute in the XML
559 alternate processing), it should use the <code><a href=
605 <p>Element type and attribute names that belong to a given namespace
610 name (i.e. the part after the colon). Names with undeclared prefixes
611 are not well-formed when namespace processing is enabled, and will
612 trigger an error. Unprefixed attribute names are never expanded,
613 and unprefixed element names are only expanded when they are in the
617 >XML_SetReturnNSTriplet</a></code> has been called with a non-zero
618 <code>do_nst</code> parameter, then the expanded form for names with
642 to recognized UTF-8 and UTF-16 (1 and 2 byte encodings of Unicode),
647 <?xml version="1.0" encoding="ISO-8859-2"?>
650 <p>External parsed entities may begin with a text declaration, which
661 <p><a name="builtin_encodings"></a>There are four built-in encodings
664 <li>UTF-8</li>
665 <li>UTF-16</li>
666 <li>ISO-8859-1</li>
667 <li>US-ASCII</li>
685 <li>Every ASCII character that can appear in a well-formed XML document
690 equal to 65535 (0xFFFF)<em>This does not apply to the built-in support
691 for UTF-16 and UTF-8</em></li>
700 array. A -1 in this array indicates a malformed byte. If the value is
701 -2, -3, or -4, then the byte is the beginning of a 2, 3, or 4 byte
702 sequence respectively. Multi-byte sequences are sent to the convert
704 function should return the Unicode scalar value for the sequence or -1
709 it passes to the handlers are always encoded in UTF-8 or UTF-16
713 <h3>Handling External Entity References</h3>
715 <p>Expat does not read or parse external entities directly. Note that
716 any external DTD is a special case of an external entity. If you've
717 set no <code>ExternalEntityRefHandler</code>, then external entity
719 the information needed to read and parse the external entity.</p>
727 use <code><a href= "#XML_Parse" >XML_Parse</a></code> or <code><a
729 parser. Since external entities my refer to other external entities,
740 <dd>Don't parse parameter entities or the external subset</dd>
742 <dd>Parse parameter entites and the external subset unless
745 <dd>Always parse parameter entities and the external subset</dd>
748 <p>In order to read an external DTD, you also have to set an external
751 <h3 id="stop-resume">Temporarily Stopping Parsing</h3>
770 if a application-domain error is found in the XML being parsed or if
782 the rough structure (in pseudo-code):</p>
807 function mentioned in the pseudo-code above:</p>
814 been an error), or the parse is stopped. Return non-zero when
858 non-zero when the parse is suspended.
878 <p>Now that we've seen what a mess the top-level parsing loop can
879 become, what have we gained? Very simply, we can now use the <code><a
886 <p>To stop parsing from a handler function, use the <code><a href=
891 <!-- XXX really need more here -->
895 <!-- ================================================================ -->
906 Construct a new parser. If encoding is non-null, it specifies a
907 character encoding to use for the document. This overrides the document
908 encoding declaration. There are four built-in encodings:
910 <li>US-ASCII</li>
911 <li>UTF-8</li>
912 <li>UTF-16</li>
913 <li>ISO-8859-1</li>
925 expanded element names and attribute names are returned as a concatenation
930 in XML. For instance, <code>'\xFF'</code> is not legal in UTF-8, and
931 <code>'\xFFFF'</code> is not legal in UTF-16. There is a special case when
933 the local part will be concatenated without any separator - this is intended
934 to support RDF processors. It is a programming error to use the null separator
952 specified in <code>ms</code>. If <code>ms</code> is NULL, then use the
966 Construct a new <code>XML_Parser</code> object for parsing an external
993 the parser, except for the unknownEncodingHandler. The parser's external
994 state is re-initialized except for the values of ns and ns_triplets.
1074 typical use would look like this:
1109 call-back handler, except when aborting (when <code>resumable</code>
1111 call-backs may still follow because they would otherwise get
1119 while making multiple call-backs on a contiguous chunk of characters,</li>
1124 call-backs, except when parsing an external parameter entity and
1135 <dd>when suspending while parsing an external PE.</dd>
1140 not being handled appropriately; see <a href= "#stop-resume"
1156 external entity reference handler returns. It is up to the
1174 within a handler call-back. Returns same status codes as <code><a
1236 The former implies UTF-8 encoding, the latter two imply UTF-16 encoding.
1299 is <em>NOT nul-terminated</em>. You have to use the length argument
1304 may <em>NOT immediately</em> terminate call-backs if the parser is currently
1305 processing such a single block of contiguous markup-free text, as the parser
1396 that they will be encoded in UTF-8 or UTF-16. Line boundaries are not
1443 <p>Set an external entity reference handler. This handler is also
1444 called for processing an external DTD subset if parameter entity parsing
1457 <p>The <code>base</code> parameter is the base to use for relative
1467 handling of the external entity reference. Returning
1477 parser, the body of the external entity can be recursively parsed.</p>
1528 <p>The <code>is_parameter_entity</code> argument will be non-zero for
1563 at most once per parsed (external) entity. The optional application
1570 value is -1, then that byte is invalid as the initial byte in a sequence.
1571 If the value is -n, where n is an integer > 1, then n is the number of
1573 call to the function pointed at by convert. This function may return -1
1577 string s is <em>NOT</em> nul-terminated and points at the sequence of
1643 text declarations discovered in external entities. The way to
1647 contain -1, 0, or 1 indicating respectively that there was no
1667 before any external or internal subset is parsed. Both <code>sysid</code>
1669 will be non-zero if the DOCTYPE declaration has an internal subset.</p>
1683 after parsing any external subset.</p>
1797 <code>isrequired</code>, but they will have the non-NULL fixed value
1820 The <code>is_parameter_entity</code> argument will be non-zero in the
1824 <code>value</code> will be non-NULL and <code>systemId</code>,
1827 provided in the <code>value_length</code> parameter. Do not use
1829 legal to have zero-length values. Instead check for whether or not
1831 argument will have a non-NULL value only for unparsed entity
1857 compatibility. Use instead <a href= "#XML_SetEntityDeclHandler"
1889 This happens when there is an external subset or a reference to a
1968 entity and for the end-tag event for empty element tags (the later can
1969 be used to distinguish empty-element tags from empty elements using
2082 >XML_StartElementHandler</a></code>, or -1 if there is no ID
2103 in the start-tag rather than defaulted. Each attribute/value pair counts
2115 passing a non-null encoding argument to the parser creation functions.
2129 This enables parsing of parameter entities, including the external
2130 parameter entity that is the external DTD subset, according to
2149 Sets the hash salt to use for internal hash calculations.
2154 <p><b>Note:</b>This call is optional, as the parser will auto-generate
2167 <p>This function allows an application to provide an external subset
2169 an external subset of their own. For documents which specify an
2170 external subset in their DOCTYPE declaration, the application-provided
2173 application-provided subset will be parsed, but the
2180 <p>The application-provided external subset is read by calling the
2181 external entity reference handler set via <code><a href=
2195 the document had a DTD with an external subset. This holds true even if
2196 the external entity reference handler returns without action.</p>
2209 sets whether or not prefixes are returned with names qualified with a
2211 non-zero, then afterwards namespace qualified names (that is qualified
2256 Some macros are also defined that support compile-time tests of the
2301 identifying the feature-test macros Expat was compiled with. Since an
2339 <p>The following functions allow external code to share the memory
2340 allocator an <code>XML_Parser</code> has been configured to use. This
2341 is especially useful for third-party libraries that interact with a
2344 libraries which use different C standard libraries (this can happen on
2353 <code>parser</code> object has been configured to use. Returns a
2365 <code>parser</code> object has been configured to use.
2390 src="valid-xhtml10.png" alt="Valid XHTML 1.0!"