From 183ea8d8396eca372423fb58a06042bf8ee1c2e0 Mon Sep 17 00:00:00 2001 From: fiddlosopher Date: Tue, 2 Feb 2010 16:39:15 +0000 Subject: 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 --- README | 5 +---- man/man1/pandoc.1.md | 4 ---- 2 files changed, 1 insertion(+), 8 deletions(-) diff --git a/README b/README index 34f3e455a..81d545a60 100644 --- a/README +++ b/README @@ -96,10 +96,7 @@ Supported input formats include `markdown`, `html`, `latex`, and `rst`. Note that the `rst` reader only parses a subset of reStructuredText syntax. For example, it doesn't handle tables, option lists, or footnotes. But for simple documents it should be adequate. The `latex` -and `html` readers are also limited in what they can do. Because the -`html` reader is picky about the HTML it parses, it is recommended that -you pipe HTML through [HTML Tidy] before sending it to `pandoc`, or use -the `html2markdown` script described below. +and `html` readers are also limited in what they can do. If you don't specify a reader or writer explicitly, `pandoc` will try to determine the input and output format from the extensions of diff --git a/man/man1/pandoc.1.md b/man/man1/pandoc.1.md index 4c6be3faf..49f645140 100644 --- a/man/man1/pandoc.1.md +++ b/man/man1/pandoc.1.md @@ -60,10 +60,6 @@ should pipe input and output through `iconv`: iconv -t utf-8 input.txt | pandoc | iconv -f utf-8 -Pandoc's HTML parser is not very forgiving. If your input is -HTML, consider running it through `tidy`(1) before passing it -to Pandoc. Or use `html2markdown`(1), a wrapper around `pandoc`. - # OPTIONS -f *FORMAT*, -r *FORMAT*, \--from=*FORMAT*, \--read=*FORMAT* -- cgit v1.2.3