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>-k</option></arg>
64 <arg><option>-v</option></arg>
75 determine if an XML document is well-formed. It is
76 non-validating.
80 If you do not specify any files on the command-line, and you
88 <title>WELL-FORMED DOCUMENTS</title>
91 A well-formed document must adhere to the
109 all other elements in the document. Only comments, white
123 If the document has a DTD, and it strictly complies with that
124 DTD, then the document is also considered <emphasis>valid</emphasis>.
125 <command>&dhpackage;</command> is a non-validating parser --
127 external entities (see the <option>-x</option> option).
136 separately ("<option>-d</option> output") or concatenated with the
137 option ("<option>-d</option>output"). <command>&dhpackage;</command>
144 <term><option>-c</option></term>
147 If the input file is well-formed and <command>&dhpackage;</command>
149 the output directory unchanged.
150 This implies no namespaces (turns off <option>-n</option>) and
151 requires <option>-d</option> to specify an output directory.
157 <term><option>-d output-dir</option></term>
162 By default, <option>-d</option> outputs a canonical representation
164 You can select different output formats using <option>-c</option>,
165 <option>-m</option> and <option>-N</option>.
168 The output filenames will
171 output file does not go into the same directory as the input
173 input file before it generates the output file (just like running
177 Two structurally equivalent XML documents have a byte-for-byte
188 <term><option>-e encoding</option></term>
191 Specifies the character encoding for the document, overriding
192 any document encoding declaration. <command>&dhpackage;</command>
193 supports four built-in encodings:
194 <literal>US-ASCII</literal>,
195 <literal>UTF-8</literal>,
196 <literal>UTF-16</literal>, and
197 <literal>ISO-8859-1</literal>.
198 Also see the <option>-w</option> option.
204 <term><option>-m</option></term>
209 Requires <option>-d</option> to specify an output file.
215 <term><option>-n</option></term>
219 <option>-c</option> disables namespaces.
225 <term><option>-N</option></term>
228 Adds a doctype and notation declarations to canonical XML output.
229 This matches the example output used by the formal XML test cases.
230 Requires <option>-d</option> to specify an output file.
236 <term><option>-p</option></term>
244 entities. <option>-p</option> tells it to always parse them.
245 <option>-p</option> implies <option>-x</option>.
251 <term><option>-r</option></term>
254 Normally <command>&dhpackage;</command> memory-maps the XML file
257 <option>-r</option> turns off memory-mapping and uses normal file
259 Of course, memory-mapping is automatically turned off
263 Use of memory-mapping can cause some platforms to report
273 <term><option>-s</option></term>
276 Prints an error if the document is not standalone.
277 A document is standalone if it has no external subset and no
284 <term><option>-t</option></term>
291 <option>-t</option> turns off most of the output options
292 (<option>-d</option>, <option>-m</option>, <option>-c</option>, ...).
298 <term><option>-k</option></term>
312 <term><option>-v</option></term>
316 information on the compile-time configuration of the library, and
323 <term><option>-w</option></term>
329 <option>-w</option>, &dhpackage; will try to use a Windows code
330 page. See also <option>-e</option>.
336 <term><option>-x</option></term>
342 Non-validating parsers are not required to resolve external
361 <!ENTITY header SYSTEM "header-&vers;.xml"> (parsed)
370 <term><option>--</option></term>
378 &dhpackage; -- -myfile.xml
382 <filename>-myfile.xml</filename>.
395 <title>OUTPUT</title>
397 <command>&dhpackage;</command> outputs nothing for files which are problem-free.
398 If any input file is not well-formed, or if the output for any
400 line describing the problem to standard output.
403 If the <option>-k</option> option is not provided, <command>&dhpackage;</command>
404 halts upon encountering a well-formedness or output-file error.
405 If <option>-k</option> is provided, <command>&dhpackage;</command> continues
412 …<para>For option <option>-v</option> or <option>-h</option>, <command>&dhpackage;</command> always…
416 …<listitem><para>The input files are well-formed and the output (if requested) was written successf…
426 <listitem><para>One or more input files were not well-formed or could not be parsed.</para>
431 …<listitem><para>If using the <option>-d</option> option, an error occurred opening an output file.…
436 …<listitem><para>There was a command-line argument error in how <command>&dhpackage;</command> was …
447 The errors should go to standard error, not standard output.
450 There should be a way to get <option>-d</option> to send its
451 output to standard output rather than forcing the user to send
456 <option>-d</option>, <option>-c</option>, and
457 <option>-m</option> options. If someone could explain it to
468 http://www.hcrc.ed.ac.uk/~richard/xml-check.html
483 The W3 XML specification: http://www.w3.org/TR/REC-xml
494 granted to copy, distribute and/or modify this document under