aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorfiddlosopher <fiddlosopher@788f1e2b-df1e-0410-8736-df70ead52e1b>2010-03-20 18:02:32 +0000
committerfiddlosopher <fiddlosopher@788f1e2b-df1e-0410-8736-df70ead52e1b>2010-03-20 18:02:32 +0000
commit83797bc1c9367d71140e6329374932dcb973aded (patch)
treee1918f452c0c35289a3965ba73545045660a9eac
parent4cc6b71bc03e8d4e952ad18aeda6910536ec9bb7 (diff)
downloadpandoc-83797bc1c9367d71140e6329374932dcb973aded.tar.gz
Fixed indent in README.
git-svn-id: https://pandoc.googlecode.com/svn/trunk@1924 788f1e2b-df1e-0410-8736-df70ead52e1b
-rw-r--r--README6
1 files changed, 3 insertions, 3 deletions
diff --git a/README b/README
index 97be88179..26d972ec3 100644
--- a/README
+++ b/README
@@ -100,7 +100,7 @@ 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
-the input and output filenames. Thus, for example,
+the input and output filenames. Thus, for example,
pandoc -o hello.tex hello.txt
@@ -139,13 +139,13 @@ sources. The default behavior of `markdown2pdf` is to create a file with
the same base name as the first argument and the extension `pdf`; thus,
for example,
- markdown2pdf sample.txt endnotes.txt
+ markdown2pdf sample.txt endnotes.txt
will produce `sample.pdf`. (If `sample.pdf` exists already,
it will be backed up before being overwritten.) An output file
name can be specified explicitly using the `-o` option:
- markdown2pdf -o book.pdf chap1 chap2
+ markdown2pdf -o book.pdf chap1 chap2
If no input file is specified, input will be taken from stdin.
All of `pandoc`'s options will work with `markdown2pdf` as well.