Lines Matching +full:- +full:- +full:output +full:- +full:document
2 <!-- Fill in your name for FIRSTNAME and SURNAME. -->
5 <!-- Please adjust the date whenever revising the manpage. -->
7 <!-- SECTION should be 1-8, maybe w/ subsection other parameters are
8 allowed: see man(7), man(1). -->
42 <refpurpose>Determines if an XML document is well-formed</refpurpose>
47 <arg><option>-s</option></arg>
48 <arg><option>-n</option></arg>
49 <arg><option>-p</option></arg>
50 <arg><option>-x</option></arg>
52 <arg><option>-e <replaceable>encoding</replaceable></option></arg>
53 <arg><option>-w</option></arg>
55 <arg><option>-d <replaceable>output-dir</replaceable></option></arg>
56 <arg><option>-c</option></arg>
57 <arg><option>-m</option></arg>
59 <arg><option>-r</option></arg>
60 <arg><option>-t</option></arg>
61 <arg><option>-N</option></arg>
63 <arg><option>-v</option></arg>
74 determine if an XML document is well-formed. It is
75 non-validating.
79 If you do not specify any files on the command-line, and you
87 <title>WELL-FORMED DOCUMENTS</title>
90 A well-formed document must adhere to the
108 all other elements in the document. Only comments, white
122 If the document has a DTD, and it strictly complies with that
123 DTD, then the document is also considered <emphasis>valid</emphasis>.
124 <command>&dhpackage;</command> is a non-validating parser --
126 external entities (see the <option>-x</option> option).
135 separately ("<option>-d</option> output") or concatenated with the
136 option ("<option>-d</option>output"). <command>&dhpackage;</command>
143 <term><option>-c</option></term>
146 If the input file is well-formed and <command>&dhpackage;</command>
148 the output directory unchanged.
149 This implies no namespaces (turns off <option>-n</option>) and
150 requires <option>-d</option> to specify an output directory.
156 <term><option>-d output-dir</option></term>
161 By default, <option>-d</option> outputs a canonical representation
163 You can select different output formats using <option>-c</option>,
164 <option>-m</option> and <option>-N</option>.
167 The output filenames will
170 output file does not go into the same directory as the input
172 input file before it generates the output file (just like running
176 Two structurally equivalent XML documents have a byte-for-byte
187 <term><option>-e encoding</option></term>
190 Specifies the character encoding for the document, overriding
191 any document encoding declaration. <command>&dhpackage;</command>
192 supports four built-in encodings:
193 <literal>US-ASCII</literal>,
194 <literal>UTF-8</literal>,
195 <literal>UTF-16</literal>, and
196 <literal>ISO-8859-1</literal>.
197 Also see the <option>-w</option> option.
203 <term><option>-m</option></term>
208 Requires <option>-d</option> to specify an output file.
214 <term><option>-n</option></term>
218 <option>-c</option> disables namespaces.
224 <term><option>-N</option></term>
227 Adds a doctype and notation declarations to canonical XML output.
228 This matches the example output used by the formal XML test cases.
229 Requires <option>-d</option> to specify an output file.
235 <term><option>-p</option></term>
243 entities. <option>-p</option> tells it to always parse them.
244 <option>-p</option> implies <option>-x</option>.
250 <term><option>-r</option></term>
253 Normally <command>&dhpackage;</command> memory-maps the XML file
256 <option>-r</option> turns off memory-mapping and uses normal file
258 Of course, memory-mapping is automatically turned off
262 Use of memory-mapping can cause some platforms to report
272 <term><option>-s</option></term>
275 Prints an error if the document is not standalone.
276 A document is standalone if it has no external subset and no
283 <term><option>-t</option></term>
290 <option>-t</option> turns off most of the output options
291 (<option>-d</option>, <option>-m</option>, <option>-c</option>, ...).
297 <term><option>-v</option></term>
301 information on the compile-time configuration of the library, and
308 <term><option>-w</option></term>
314 <option>-w</option>, &dhpackage; will try to use a Windows code
315 page. See also <option>-e</option>.
321 <term><option>-x</option></term>
327 Non-validating parsers are not required to resolve external
346 <!ENTITY header SYSTEM "header-&vers;.xml"> (parsed)
355 <term><option>--</option></term>
363 &dhpackage; -- -myfile.xml
367 <filename>-myfile.xml</filename>.
380 <title>OUTPUT</title>
382 If an input file is not well-formed,
384 the problem to standard output. If a file is well formed,
393 <command>&dhpackage;</command> returns a 0 - noerr result,
394 even if the file is not well-formed. There is no good way for
396 check a file -- it must parse <command>&dhpackage;</command>'s
397 standard output.
400 The errors should go to standard error, not standard output.
403 There should be a way to get <option>-d</option> to send its
404 output to standard output rather than forcing the user to send
409 <option>-d</option>, <option>-c</option>, and
410 <option>-m</option> options. If someone could explain it to
421 http://www.hcrc.ed.ac.uk/~richard/xml-check.html
436 The W3 XML specification: http://www.w3.org/TR/REC-xml
447 granted to copy, distribute and/or modify this document under