Lines Matching +full:- +full:- +full:output +full:- +full:document
10 In brief, TinyXml parses an XML document, and builds from that a
11 Document Object Model (DOM) that can be read, modified, and saved.
14 your own document markups. Where HTML does a very good job of marking
15 documents for browsers, XML allows you to define any kind of document
16 markup, for example a document that describes a "to do" list for an
22 read spec is at <a href="http://www.w3.org/TR/2004/REC-xml-20040204/">
23 http://www.w3.org/TR/2004/REC-xml-20040204/</a>. An intro to XML
28 TinyXml uses a Document Object Model (DOM), meaning the XML data is parsed
30 written to disk or another output stream. You can also construct an XML document from
31 scratch with C++ objects and write this to disk or another output
36 There is an example file - xmltest.cpp - to get you started.
43 compliant XML output. TinyXml should compile on any reasonably C++
46 the UTF-8 encoding, and the first 64k character entities.
51 It doesnt parse or use DTDs (Document Type Definitions) or XSLs
75 - @subpage tutorial0
114 <h3> UTF-8 </h3>
116 TinyXml supports UTF-8 allowing to manipulate XML files in any language. TinyXml
117 also supports "legacy mode" - the encoding used before UTF-8 support and
126 <li> If the non-standard but common "UTF-8 lead bytes" (0xef 0xbb 0xbf)
127 begin the file or data stream, TinyXml will read it as UTF-8. </li>
128 <li> If the declaration tag is read, and it has an encoding="UTF-8", then
129 TinyXml will read it as UTF-8. </li>
131 TinyXml will read it as UTF-8. </li>
148 For English users, using English XML, UTF-8 is the same as low-ASCII. You
149 don't need to be aware of UTF-8 or change your code in any way. You can think
150 of UTF-8 as a "superset" of ASCII.
152 UTF-8 is not a double byte format - but it is a standard encoding of Unicode!
154 It is common to see the term "Unicode" improperly refer to UTF-16, a wide byte encoding
157 For "high-ascii" languages - everything not English, pretty much - TinyXml can
159 in UTF-8. That can be a little tricky, older programs and operating systems
161 modern ones) can output UTF-8, but older or stubborn (or just broken) ones
162 still output text in the default code page.
164 For example, Japanese systems traditionally use SHIFT-JIS encoding.
165 Text encoded as SHIFT-JIS can not be read by tinyxml.
166 A good text editor can import SHIFT-JIS and then save as UTF-8.
175 system, you won't see output that matches the GIF file even if you can parse
176 it correctly. Also note that (at least on my Windows machine) console output
178 the file. This is not a bug in TinyXml - just an OS issue. No data is lost or
179 destroyed by TinyXml. The console just doesn't render UTF-8.
183 TinyXml recognizes the pre-defined "character entities", meaning special
194 These are recognized when the XML document is read, and translated to there
195 UTF-8 equivalents. For instance, text with the XML of:
207 The syntax " " or " " are both to the non-breaking space characher.
215 C style output:
216 - based on FILE*
217 - the Print() and SaveFile() methods
219 Generates formatted output, with plenty of white space, intended to be as
220 human-readable as possible. They are very fast, and tolerant of ill formed
221 XML documents. For example, an XML document that contains 2 root elements
225 - based on FILE*
226 - the Parse() and LoadFile() methods
231 - based on std::ostream
232 - operator<<
234 Generates condensed output, intended for network transmission rather than
237 a document should contain the correct one root element. Additional root level
241 - based on std::istream
242 - operator>>
245 part is knowing when the XML document is complete, since there will almost
248 are ill-constructed with more than one root element will not read correctly.
271 Where browsing an XML document in a robust way, it is important to check
276 TiXmlElement* root = document.FirstChildElement( "Document" );
279 TiXmlElement* element = root->FirstChildElement( "Element" );
282 TiXmlElement* child = element->FirstChildElement( "Child" );
285 TiXmlElement* child2 = child->NextSiblingElement( "Child" );
295 TiXmlHandle docHandle( &document );
296 TiXmlElement* child2 = docHandle.FirstChild( "Document" ).FirstChild( "Element" ).Child( "Child", 1…
323 disk and generate output on the screen. It also tests walking the
334 <li>tinyxml: tinyxml library, non-STL </li>
336 <li>tinyXmlTest: test app, non-STL </li>
364 <!-- Our to do list data -->
372 (say "demo.xml") you would create a document, and parse it in:
387 document node.
394 <!-- Our to do list data -->
451 This software is provided 'as-is', without any express or implied
475 The definitive spec: <a href="http://www.w3.org/TR/2004/REC-xml-20040204/">
476 http://www.w3.org/TR/2004/REC-xml-20040204/</a>