W3C home > Mailing lists > Public > html-tidy@w3.org > January to March 2007

problems in tidy.1

From: <esr@thyrsus.com>
Date: Mon, 1 Jan 2007 19:04:49 -0500
Message-Id: <200701020004.l0204nBA027990@snark.thyrsus.com>
To: html-tidy@w3.org

This is automatically generated email about problems in a man page for which
you appear to be responsible.  If you are not the right person or list, tell
me and I will attempt to correct my database.

See http://catb.org/~esr/doclifter/problems.html for details on how and
why these patches were generated.  Feel free to email me with any questions.
Note: These patches do not change the mod date of any manual page.  You
may wish to do that by hand.

Problems with tidy.1:

1. Unknown or invalid macro.  That is, one that does not fit in the
macro set that the man page seems to be using.  This is a serious
error; it often means part of your text is being lost or rendered
incorrectly.

--- tidy.1-orig	2006-12-18 12:45:53.000000000 -0500
+++ tidy.1	2006-12-18 12:46:45.000000000 -0500
@@ -259,7 +259,6 @@
 This option specifies if Tidy should add the XML declaration when outputting XML or XHTML. Note that if the input already includes an <?xml ... ?> declaration then this option will be ignored. If the encoding for the output is different from "ascii", one of the utf encodings or "raw", the declaration is always added as required by the XML standard.
 
 
-.rj 1
 \fBSee also\fR: \fIchar-encoding\fR, \fIoutput-encoding\fR
 .TP
 \fBadd-xml-space\fR
@@ -483,7 +482,6 @@
 This option specifies if Tidy should combine class names to generate a single new class name, if multiple class assignments are detected on an element.
 
 
-.rj 1
 \fBSee also\fR: \fIjoin-styles\fR, \fIrepeated-attributes\fR
 .TP
 \fBjoin-styles\fR
@@ -497,7 +495,6 @@
 This option specifies if Tidy should combine styles to generate a single new style, if multiple style values are detected on an element.
 
 
-.rj 1
 \fBSee also\fR: \fIjoin-classes\fR, \fIrepeated-attributes\fR
 .TP
 \fBliteral-attributes\fR
@@ -541,7 +538,6 @@
 Can be used to modify behavior of -c (--clean yes) option. This option specifies if Tidy should merge nested <div> such as "<div><div>...</div></div>". If set to "auto", the attributes of the inner <div> are moved to the outer one. As well, nested <div> with ID attributes are not merged. If set to "yes", the attributes of the inner <div> are discarded with the exception of "class" and "style".
 
 
-.rj 1
 \fBSee also\fR: \fIclean\fR
 .TP
 \fBncr\fR
@@ -565,7 +561,6 @@
 This option specifies new block-level tags. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. Note you can't change the content model for elements such as <TABLE>, <UL>, <OL> and <DL>.
 
 
-.rj 1
 \fBSee also\fR: \fInew-empty-tags\fR, \fInew-inline-tags\fR, \fInew-pre-tags\fR
 .TP
 \fBnew-empty-tags\fR
@@ -579,7 +574,6 @@
 This option specifies new empty inline tags. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. Remember to also declare empty tags as either inline or blocklevel.
 
 
-.rj 1
 \fBSee also\fR: \fInew-blocklevel-tags\fR, \fInew-inline-tags\fR, \fInew-pre-tags\fR
 .TP
 \fBnew-inline-tags\fR
@@ -593,7 +587,6 @@
 This option specifies new non-empty inline tags. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags.
 
 
-.rj 1
 \fBSee also\fR: \fInew-blocklevel-tags\fR, \fInew-empty-tags\fR, \fInew-pre-tags\fR
 .TP
 \fBnew-pre-tags\fR
@@ -607,7 +600,6 @@
 This option specifies new tags that are to be processed in exactly the same way as HTML's <PRE> element. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. Note you can not as yet add new CDATA elements (similar to <SCRIPT>).
 
 
-.rj 1
 \fBSee also\fR: \fInew-blocklevel-tags\fR, \fInew-empty-tags\fR, \fInew-inline-tags\fR
 .TP
 \fBnumeric-entities\fR
@@ -621,7 +613,6 @@
 This option specifies if Tidy should output entities other than the built-in HTML entities (&amp;, &lt;, &gt; and &quot;) in the numeric rather than the named entity form.
 
 
-.rj 1
 \fBSee also\fR: \fIdoctype\fR
 .TP
 \fBoutput-html\fR
@@ -695,7 +686,6 @@
 This option specifies if Tidy should keep the first or last attribute, if an attribute is repeated, e.g. has two align attributes.
 
 
-.rj 1
 \fBSee also\fR: \fIjoin-classes\fR, \fIjoin-styles\fR
 .TP
 \fBreplace-color\fR
@@ -803,7 +793,6 @@
 This option specifies if Tidy should indent block-level tags. If set to "auto", this option causes Tidy to decide whether or not to indent the content of tags such as TITLE, H1-H6, LI, TD, TD, or P depending on whether or not the content includes a block-level element. You are advised to avoid setting indent to yes as this can expose layout bugs in some browsers.
 
 
-.rj 1
 \fBSee also\fR: \fIindent-spaces\fR
 .TP
 \fBindent-attributes\fR
@@ -827,7 +816,6 @@
 This option specifies the number of spaces Tidy uses to indent content, when indentation is enabled.
 
 
-.rj 1
 \fBSee also\fR: \fIindent\fR
 .TP
 \fBmarkup\fR
@@ -911,7 +899,6 @@
 This option specifies if Tidy should line wrap attribute values, for easier editing. This option can be set independently of wrap-script-literals.
 
 
-.rj 1
 \fBSee also\fR: \fIwrap-script-literals\fR
 .TP
 \fBwrap-jste\fR
@@ -945,7 +932,6 @@
 This option specifies if Tidy should line wrap string literals that appear in script attributes. Tidy wraps long script string literals by inserting a backslash character before the line break.
 
 
-.rj 1
 \fBSee also\fR: \fIwrap-attributes\fR
 .TP
 \fBwrap-sections\fR
@@ -971,7 +957,6 @@
 Can be used to modify behavior of -c (--clean yes) option. If set to "yes" when using -c, &emdash;, &rdquo;, and other named character entities are downgraded to their closest ascii equivalents.
 
 
-.rj 1
 \fBSee also\fR: \fIclean\fR
 .TP
 \fBchar-encoding\fR
@@ -985,7 +970,6 @@
 This option specifies the character encoding Tidy uses for both the input and output. For ascii, Tidy will accept Latin-1 (ISO-8859-1) character values, but will use entities for all characters whose value > 127. For raw, Tidy will output values above 127 without translating them into entities. For latin1, characters above 255 will be written as entities. For utf8, Tidy assumes that both input and output is encoded as UTF-8. You can use iso2022 for files encoded using the ISO-2022 family of encodings e.g. ISO-2022-JP. For mac and win1252, Tidy will accept vendor specific character values, but will use entities for all characters whose value > 127.
 
 
-.rj 1
 \fBSee also\fR: \fIinput-encoding\fR, \fIoutput-encoding\fR
 .TP
 \fBinput-encoding\fR
@@ -999,7 +983,6 @@
 This option specifies the character encoding Tidy uses for the input. See char-encoding for more info.
 
 
-.rj 1
 \fBSee also\fR: \fIchar-encoding\fR
 .TP
 \fBlanguage\fR
@@ -1043,7 +1026,6 @@
 This option specifies the character encoding Tidy uses for the output. See char-encoding for more info. May only be different from input-encoding for Latin encodings (ascii, latin0, latin1, mac, win1252, ibm858).
 
 
-.rj 1
 \fBSee also\fR: \fIchar-encoding\fR
 .SS Miscellaneous options:
   
@@ -1059,7 +1041,6 @@
 This option specifies the error file Tidy uses for errors and warnings. Normally errors and warnings are output to "stderr".
 
 
-.rj 1
 \fBSee also\fR: \fIoutput-file\fR
 .TP
 \fBforce-output\fR
@@ -1113,7 +1094,6 @@
 This option specifies the output file Tidy uses for markup. Normally markup is written to "stdout".
 
 
-.rj 1
 \fBSee also\fR: \fIerror-file\fR
 .TP
 \fBquiet\fR
-----------------------------

--
                             Eric S. Raymond
Received on Tuesday, 2 January 2007 05:45:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 April 2012 06:13:56 GMT