git.iko.soy/typeable/pandoc
on master help sign in
Fixed indent in README.

git-svn-id: https://pandoc.googlecode.com/svn/trunk@1924 788f1e2b-df1e-0410-8736-df70ead52e1b

commit83797bc1c9367d71140e6329374932dcb973aded authorfiddlosopher <fiddlosopher@788f1e2b-df1e-0410-8736-df70ead52e1b> dateSat 20 Mar 2010, 18:02 (17 years ago) parent4cc6b71
1 file changed+3−3
README+3−3
README+3−3
@@ -100,7 +100,7 @@ and `html` readers are also limited in what they can do.
100100
101101If you don't specify a reader or writer explicitly, `pandoc` will
102102try to determine the input and output format from the extensions of
103−the input and output filenames. Thus, for example,
103+the input and output filenames. Thus, for example,
104104
105105 pandoc -o hello.tex hello.txt
106106
@@ -139,13 +139,13 @@ sources. The default behavior of `markdown2pdf` is to create a file with
139139the same base name as the first argument and the extension `pdf`; thus,
140140for example,
141141
142− markdown2pdf sample.txt endnotes.txt
142+ markdown2pdf sample.txt endnotes.txt
143143
144144will produce `sample.pdf`. (If `sample.pdf` exists already,
145145it will be backed up before being overwritten.) An output file
146146name can be specified explicitly using the `-o` option:
147147
148− markdown2pdf -o book.pdf chap1 chap2
148+ markdown2pdf -o book.pdf chap1 chap2
149149
150150If no input file is specified, input will be taken from stdin.
151151All of `pandoc`'s options will work with `markdown2pdf` as well.