git.iko.soy/typeable/pandoc
on master help sign in
Fixed indent in README.
83797bcfiddlosopher
README+3−3
@@ -100,7 +100,7 @@ and `html` readers are also limited in what they can do.
100
100
101If you don't specify a reader or writer explicitly, `pandoc` will
101If you don't specify a reader or writer explicitly, `pandoc` will
102try to determine the input and output format from the extensions of
102try 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,
104
104
105 pandoc -o hello.tex hello.txt
105 pandoc -o hello.tex hello.txt
106
106
@@ -139,13 +139,13 @@ sources. The default behavior of `markdown2pdf` is to create a file with
139the same base name as the first argument and the extension `pdf`; thus,
139the same base name as the first argument and the extension `pdf`; thus,
140for example,
140for example,
141
141
142− markdown2pdf sample.txt endnotes.txt
142+ markdown2pdf sample.txt endnotes.txt
143
143
144will produce `sample.pdf`. (If `sample.pdf` exists already,
144will produce `sample.pdf`. (If `sample.pdf` exists already,
145it will be backed up before being overwritten.) An output file
145it will be backed up before being overwritten.) An output file
146name can be specified explicitly using the `-o` option:
146name can be specified explicitly using the `-o` option:
147
147
148− markdown2pdf -o book.pdf chap1 chap2
148+ markdown2pdf -o book.pdf chap1 chap2
149
149
150If no input file is specified, input will be taken from stdin.
150If no input file is specified, input will be taken from stdin.
151All of `pandoc`'s options will work with `markdown2pdf` as well.
151All of `pandoc`'s options will work with `markdown2pdf` as well.