From 9fee73d2a335e7ea8dbbfc149cfa4be580afbdca Mon Sep 17 00:00:00 2001 From: fiddlosopher Date: Tue, 2 Feb 2010 07:37:01 +0000 Subject: Allow absolute URI as parameter (in this case, content is downloaded). + Adds dependency on HTTP. + If a parameter is an absolute URI, pandoc will try to get the content via HTTP. + So, you can do: pandoc -r html -w markdown http://www.fsf.org git-svn-id: https://pandoc.googlecode.com/svn/trunk@1826 788f1e2b-df1e-0410-8736-df70ead52e1b --- man/man1/pandoc.1.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) (limited to 'man') diff --git a/man/man1/pandoc.1.md b/man/man1/pandoc.1.md index 6ade178b7..4c6be3faf 100644 --- a/man/man1/pandoc.1.md +++ b/man/man1/pandoc.1.md @@ -26,6 +26,11 @@ format). For output to a file, use the `-o` option: pandoc -o output.html input.txt +Instead of a file, an absolute URI may be given. In this case +pandoc will fetch the content using HTTP: + + pandoc -f html -t markdown http://www.fsf.org + The input and output formats may be specified using command-line options (see **OPTIONS**, below, for details). If these formats are not specified explicitly, Pandoc will attempt to determine them @@ -48,9 +53,10 @@ markdown: the differences are described in the *README* file in the user documentation. If standard markdown syntax is desired, the `--strict` option may be used. -Pandoc uses the UTF-8 character encoding for both input and output. -If your local character encoding is not UTF-8, you should pipe input -and output through `iconv`: +Pandoc uses the UTF-8 character encoding for both input and output +(unless compiled with GHC 6.12 or higher, in which case it uses +the local encoding). If your local character encoding is not UTF-8, you +should pipe input and output through `iconv`: iconv -t utf-8 input.txt | pandoc | iconv -f utf-8 -- cgit v1.2.3