git.iko.soy/typeable/pandoc
on master help sign in
Removed advice to pipe through tidy before HTML reader.

This is obsolete, now that we have a forgiving HTML parser. git-svn-id: https://pandoc.googlecode.com/svn/trunk@1827 788f1e2b-df1e-0410-8736-df70ead52e1b

commit183ea8d8396eca372423fb58a06042bf8ee1c2e0 authorfiddlosopher <fiddlosopher@788f1e2b-df1e-0410-8736-df70ead52e1b> dateTue 2 Feb 2010, 16:39 (17 years ago) parent9fee73d
2 files changed+1−8
compare with master
unifiedsplit
README+1−4 man/man1/pandoc.1.md−4
README+1−4
@@ -96,10 +96,7 @@ Supported input formats include `markdown`, `html`, `latex`, and `rst`.
9696Note that the `rst` reader only parses a subset of reStructuredText
9797syntax. For example, it doesn't handle tables, option lists, or
9898footnotes. But for simple documents it should be adequate. The `latex`
99−and `html` readers are also limited in what they can do. Because the
100−`html` reader is picky about the HTML it parses, it is recommended that
101−you pipe HTML through [HTML Tidy] before sending it to `pandoc`, or use
102−the `html2markdown` script described below.
99+and `html` readers are also limited in what they can do.
103100
104101If you don't specify a reader or writer explicitly, `pandoc` will
105102try to determine the input and output format from the extensions of
man/man1/pandoc.1.md−4
@@ -60,10 +60,6 @@ should pipe input and output through `iconv`:
6060
6161 iconv -t utf-8 input.txt | pandoc | iconv -f utf-8
6262
63−Pandoc's HTML parser is not very forgiving. If your input is
64−HTML, consider running it through `tidy`(1) before passing it
65−to Pandoc. Or use `html2markdown`(1), a wrapper around `pandoc`.
66−
6763# OPTIONS
6864
6965-f *FORMAT*, -r *FORMAT*, \--from=*FORMAT*, \--read=*FORMAT*