Initial import
git-svn-id: http://moon:8086/svn/software/trunk/libsrc/xerces-c-3.0.0@1 b431acfa-c32f-4a4a-93f1-934dc6c82436
This commit is contained in:
Executable
+119
@@ -0,0 +1,119 @@
|
||||
<?xml version="1.0" standalone="no"?>
|
||||
<!--
|
||||
* Licensed to the Apache Software Foundation (ASF) under one or more
|
||||
* contributor license agreements. See the NOTICE file distributed with
|
||||
* this work for additional information regarding copyright ownership.
|
||||
* The ASF licenses this file to You under the Apache License, Version 2.0
|
||||
* (the "License"); you may not use this file except in compliance with
|
||||
* the License. You may obtain a copy of the License at
|
||||
*
|
||||
* http://www.apache.org/licenses/LICENSE-2.0
|
||||
*
|
||||
* Unless required by applicable law or agreed to in writing, software
|
||||
* distributed under the License is distributed on an "AS IS" BASIS,
|
||||
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
* See the License for the specific language governing permissions and
|
||||
* limitations under the License.
|
||||
-->
|
||||
|
||||
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
|
||||
|
||||
<s1 title="Sample: SAXPrint">
|
||||
|
||||
<s2 title="SAXPrint">
|
||||
<p>SAXPrint uses the SAX APIs to parse an XML file and print
|
||||
it back. Do note that the output of this sample is not
|
||||
exactly the same as the input (in terms of whitespaces, first
|
||||
line), but the output has the same information content as the
|
||||
input.</p>
|
||||
|
||||
<s3 title="Running SAXPrint">
|
||||
|
||||
<p>The SAXPrint sample parses an XML file and prints out the
|
||||
contents again in XML (some loss occurs). To run SAXPrint,
|
||||
enter the following </p>
|
||||
|
||||
<source>SAXPrint <XML file></source>
|
||||
<p>The following parameters may be set from the command line </p>
|
||||
<source>
|
||||
Usage:
|
||||
SAXPrint [options] <XML file>
|
||||
|
||||
This program invokes the SAX Parser, and then prints the
|
||||
data returned by the various SAX handlers for the specified
|
||||
XML file.
|
||||
|
||||
Options:
|
||||
-u=xxx Handle unrepresentable chars [fail | rep | ref*].
|
||||
-v=xxx Validation scheme [always | never | auto*].
|
||||
-n Enable namespace processing.
|
||||
-s Enable schema processing.
|
||||
-f Enable full schema constraint checking.
|
||||
-x=XXX Use a particular encoding for output (LATIN1*).
|
||||
-? Show this help.
|
||||
|
||||
* = Default if not provided explicitly.
|
||||
|
||||
The parser has intrinsic support for the following encodings:
|
||||
UTF-8, USASCII, ISO8859-1, UTF-16[BL]E, UCS-4[BL]E,
|
||||
WINDOWS-1252, IBM1140, IBM037, IBM1047.
|
||||
</source>
|
||||
|
||||
<p><em>-u=fail</em> will fail when unrepresentable characters are encountered<br/>
|
||||
<em>-u=rep</em> will replace with the substitution character for that codepage<br/>
|
||||
<em>-u=ref</em> will report the character as a reference</p>
|
||||
<p><em>-v=always</em> will force validation<br/>
|
||||
<em>-v=never</em> will not use any validation<br/>
|
||||
<em>-v=auto</em> will validate if a DOCTYPE declaration or a schema declaration is present in the XML document</p>
|
||||
<p>Here is a sample output from SAXPrint</p>
|
||||
<source>cd &XercesC3InstallDir;/samples/data
|
||||
SAXPrint -v=always personal.xml
|
||||
|
||||
<?xml version="1.0" encoding="LATIN1"?>
|
||||
<personnel>
|
||||
|
||||
<person id="Big.Boss">
|
||||
<name><family>Boss</family> <given>Big</given></name>
|
||||
<email>chief@foo.com</email>
|
||||
<link subordinates="one.worker two.worker three.worker
|
||||
four.worker five.worker"></link>
|
||||
</person>
|
||||
|
||||
<person id="one.worker">
|
||||
<name><family>Worker</family> <given>One</given></name>
|
||||
<email>one@foo.com</email>
|
||||
<link manager="Big.Boss"></link>
|
||||
</person>
|
||||
|
||||
<person id="two.worker">
|
||||
<name><family>Worker</family> <given>Two</given></name>
|
||||
<email>two@foo.com</email>
|
||||
<link manager="Big.Boss"></link>
|
||||
</person>
|
||||
|
||||
<person id="three.worker">
|
||||
<name><family>Worker</family> <given>Three</given></name>
|
||||
<email>three@foo.com</email>
|
||||
<link manager="Big.Boss"></link>
|
||||
</person>
|
||||
|
||||
<person id="four.worker">
|
||||
<name><family>Worker</family> <given>Four</given></name>
|
||||
<email>four@foo.com</email>
|
||||
<link manager="Big.Boss"></link>
|
||||
</person>
|
||||
|
||||
<person id="five.worker">
|
||||
<name><family>Worker</family> <given>Five</given></name>
|
||||
<email>five@foo.com</email>
|
||||
<link manager="Big.Boss"></link>
|
||||
</person>
|
||||
|
||||
</personnel></source>
|
||||
<note>SAXPrint does not reproduce the original XML file.
|
||||
SAXPrint and DOMPrint produce different results because of
|
||||
the way the two APIs store data and capture events.</note>
|
||||
</s3>
|
||||
|
||||
</s2>
|
||||
</s1>
|
||||
Reference in New Issue
Block a user