git.iko.soy/typeable/pandoc

on 01ed46d help sign in

fromb8e0b46

swap

to2 ahead, 10274 behind

compare

.circleci/config.ymldeleted−72

@@ -1,72 +0,0 @@

1−version: "2.1"

2−jobs:

3− build:

4− macos:

5− xcode: 11.1.0

6− environment:

7− HOMEBREW_NO_AUTO_UPDATE: 1

8− steps:

9− - checkout

10− - restore_cache:

11− # See https://circleci.com/docs/2.0/caching/

12− name: Restore Cached Dependencies

13− keys:

14− - stack-dependencies-{{ checksum "stack.yaml" }}

15− - run:

16− name: Install stack

17− command: stack --version || (curl -sSL https://get.haskellstack.org/ | sh -s - -f)

18− - run:

19− name: Resolve/Update Dependencies

20− command: stack --no-terminal setup

21− - run:

22− name: Run tests

23− command: stack --no-terminal test

24− - run:

25− name: Install executable

26− command: stack --no-terminal install

27− - run:

28− name: Create artifacts

29− command: |

30− export VERSION=$(grep '^[Vv]ersion:' pandoc.cabal | awk '{print $$2;}')

31− export ARTIFACTS=macos-release-candidate

32− export RESOURCES=${ARTIFACTS}/Resources

33− export ROOT=${ARTIFACTS}/pandoc

34− export DEST=${ROOT}/usr/local

35− export ME=$(whoami)

36− export BASE=pandoc-$VERSION

37− mkdir -p ${ARTIFACTS}

38− mkdir -p ${RESOURCES}

39− mkdir -p ${DEST}/bin

40− mkdir -p ${DEST}/share/man/man1

41− cp ~/.local/bin/pandoc ${DEST}/bin/

42− strip ${DEST}/bin/pandoc

43− cp man/pandoc.1 ${DEST}/share/man/man1/pandoc.1

44− ~/.local/bin/pandoc -s COPYING.md -Vpagetitle=License -o ${RESOURCES}/license.html

45− chown -R $ME:staff ${ROOT}

46− sed -e "s/PANDOCVERSION/${VERSION}/" macos/distribution.xml.in > ${ARTIFACTS}/distribution.xml

47− cp macos/Makefile ${ARTIFACTS}/

48− echo ${VERSION} > ${ARTIFACTS}/version.txt

49− zip -r macos-release-candidate.zip ${ARTIFACTS}

50−

51− - save_cache:

52− name: Cache Dependencies

53− key: stack-dependencies-{{ checksum "stack.yaml" }}

54− paths:

55− - "/root/.stack"

56− - ".stack-work"

57− - "/usr/local/bin/stack"

58−

59− - store_artifacts:

60− # https://circleci.com/docs/2.0/artifacts/

61− path: macos-release-candidate.zip

62− destination: macos-release-candidate.zip

63−

64−workflows:

65− version: 2

66− release:

67− jobs:

68− - build:

69− filters:

70− branches:

71− only:

72− - /rc\/.*/

.editorconfigdeleted−24

@@ -1,24 +0,0 @@

1−root = true

2−

3−[*]

4−charset = utf-8

5−end_of_line = lf

6−indent_style = space

7−indent_size = 2

8−insert_final_newline = true

9−trim_trailing_whitespace = true

10−

11−[*.{zip,docx}]

12−charset =

13−end_of_line =

14−indent_style =

15−indent_size =

16−insert_final_newline =

17−trim_trailing_whitespace =

18−

19−[*.{markdown,md}]

20−trim_trailing_whitespace = false

21−

22−[test/*]

23−insert_final_newline = false

24−trim_trailing_whitespace = false

.gitattributesdeleted−1

@@ -1 +0,0 @@

1−test/fb2/reader/* -text

.github/FUNDING.ymldeleted−1

@@ -1 +0,0 @@

1−github: [jgm,tarleb]

.github/ISSUE_TEMPLATE/bug_report.mddeleted−25

@@ -1,25 +0,0 @@

1−---

2−name: Bug report

3−about: Create a report to help us improve

4−title: ''

5−labels: 'bug'

6−assignees: ''

7−

8−---

9−

10−<!--

11−Thank you for reporting an issue! Before you continue, please make sure that you have

12−

13−- searched the issue tracker for similar issues (including closed issues): https://github.com/jgm/pandoc/issues

14−- searched the pandoc-discuss mailing list for solutions: https://groups.google.com/forum/#!forum/pandoc-discuss

15−- reproduced your issue on the latest release of pandoc, or on https://pandoc.org/try

16−

17−Note that this bug tracker is for reporting bugs, not asking questions. For questions, use the pandoc-discuss mailing list.

18−-->

19−

20−**Explain the problem.**

21−Include the exact command line you used and all inputs necessary to reproduce the issue. Please create as minimal an example as possible, to help the maintainers isolate the problem. Explain the output you received and how it differs from what you expected.

22−

23−**Pandoc version?**

24−What version of pandoc are you using, on what OS?

25−

.github/ISSUE_TEMPLATE/config.ymldeleted−9

@@ -1,9 +0,0 @@

1−blank_issues_enabled: false

2−contact_links:

3− - name: Ask a question

4− url: https://groups.google.com/forum/#!forum/pandoc-discuss

5− about: "Discussion forum for pandoc (may be used as an email list)"

6− - name: Contributing Guidelines

7− url: https://pandoc.org/CONTRIBUTING.html

8− about: "Guidelines for submitting bug reports and code improvements"

9−

.github/ISSUE_TEMPLATE/feature_request.mddeleted−21

@@ -1,21 +0,0 @@

1−---

2−name: Feature request

3−about: Suggest an idea for this project

4−title: ''

5−labels: 'enhancement'

6−assignees: ''

7−

8−---

9−

10−<!--

11−Thank you for suggesting a feature! Before you continue, please make sure that you have

12−

13−- read the contributing guidelines: https://pandoc.org/CONTRIBUTING.html

14−- searched the issue tracker for similar issues (including closed issues): https://github.com/jgm/pandoc/issues

15−- searched the pandoc-discuss mailing list for relevant discussions: https://groups.google.com/forum/#!forum/pandoc-discuss

16−-->

17−

18−**Describe your proposed improvement and the problem it solves.**

19−

20−**Describe alternatives you've considered.**

21−

.github/workflows/ci.ymldeleted−275

@@ -1,275 +0,0 @@

1−name: CI tests

2−

3−on:

4− push:

5− branches:

6− - '*'

7− - '!rc/*'

8− paths-ignore:

9− - 'doc/**'

10− - 'MANUAL.txt'

11− - '*.md'

12− - 'RELEASE_CHECKLIST'

13− - 'BUGS'

14− - 'changelog'

15− - 'README.template'

16− - 'appveyor.yml'

17− - 'tools/**'

18− - 'linux/**'

19− - 'macos/**'

20− - 'windows/**'

21− - 'man/**'

22− pull_request:

23− paths-ignore:

24− - 'doc/**'

25− - 'MANUAL.txt'

26− - '*.md'

27− - 'RELEASE_CHECKLIST'

28− - 'BUGS'

29− - 'changelog'

30− - 'README.template'

31− - 'appveyor.yml'

32− - 'tools/**'

33− - 'linux/**'

34− - 'macos/**'

35− - 'windows/**'

36− - 'man/**'

37−

38−jobs:

39− linux:

40−

41− runs-on: ubuntu-18.04

42− strategy:

43− fail-fast: true

44− matrix:

45− versions:

46− - ghc: '8.0.2'

47− cabal: '2.4'

48− prefix: 'v2-'

49− cabalopts: ''

50− testopts: ''

51− - ghc: '8.2.2'

52− cabal: '2.4'

53− prefix: 'v2-'

54− cabalopts: ''

55− testopts: ''

56− - ghc: '8.4.4'

57− cabal: '2.4'

58− prefix: 'v2-'

59− cabalopts: '-f-embed_data_files'

60− testopts: ''

61− - ghc: '8.6.5'

62− cabal: '3.2'

63− prefix: ''

64− cabalopts: ''

65− testopts: '--test-option=--hide-successes'

66− - ghc: '8.8.4'

67− cabal: '3.2'

68− prefix: ''

69− cabalopts: ''

70− testopts: '--test-option=--hide-successes'

71− - ghc: '8.10.4'

72− cabal: '3.2'

73− prefix: ''

74− cabalopts: '-ftrypandoc'

75− testopts: '--test-option=--hide-successes'

76− - ghc: '9.0.1'

77− cabal: '3.4'

78− prefix: ''

79− cabalopts: ''

80− testopts: '--test-option=--hide-successes'

81− steps:

82− - uses: actions/checkout@v2

83−

84− # needed by memory

85− - name: Install numa

86− run: sudo apt-get install libnuma-dev

87−

88− # need to install older cabal/ghc versions from ppa repository

89−

90− - name: Install recent cabal/ghc

91− uses: haskell/actions/setup@v1

92− with:

93− ghc-version: ${{ matrix.versions.ghc }}

94− cabal-version: ${{ matrix.versions.cabal }}

95−

96− # declare/restore cached things

97− # caching doesn't work for scheduled runs yet

98− # https://github.com/actions/cache/issues/63

99−

100− - name: Cache cabal global package db

101− id: cabal-global

102− uses: actions/cache@v2

103− with:

104− path: |

105− ~/.cabal

106− key: ${{ runner.os }}-${{ matrix.versions.ghc }}-${{ matrix.versions.cabal }}-cabal-global-${{ hashFiles('cabal.project') }}

107−

108− - name: Cache cabal work

109− id: cabal-local

110− uses: actions/cache@v2

111− with:

112− path: |

113− dist-newstyle

114− key: ${{ runner.os }}-${{ matrix.versions.ghc }}-${{ matrix.versions.cabal }}-cabal-local

115−

116− - name: Install dependencies

117− run: |

118− cabal ${{ matrix.versions.prefix }}update

119− cabal ${{ matrix.versions.prefix }}build ${{ matrix.versions.cabalopts }} --dependencies-only --enable-tests --disable-optimization

120−

121− - name: Build and test

122− run: |

123− cabal ${{ matrix.versions.prefix }}build ${{ matrix.versions.cabalopts }} --enable-tests --disable-optimization 2>&1 | tee build.log

124− # fail if warnings in local build

125− ! grep -q ": *[Ww]arning:" build.log || exit 1

126− cabal ${{ matrix.versions.prefix }}test ${{ matrix.versions.cabalopts }} --disable-optimization ${{ matrix.versions.testopts }}

127−

128− windows:

129−

130− runs-on: windows-2019

131−

132− steps:

133− - uses: actions/checkout@v2

134−

135− # We should have ghc 8.10, cabal, stack pre-installed

136− # - uses: haskell/actions/setup@v1

137− # with:

138− # enable-stack: true

139− # stack-version: 'latest'

140−

141− # declare/restore cached things

142− # caching doesn't work for scheduled runs yet

143− # https://github.com/actions/cache/issues/63

144−

145− - name: Cache stack global package db

146− id: stack-global-package-db

147− uses: actions/cache@v2

148− with:

149− path: |

150− C:\Users\runneradmin\AppData\Roaming\stack\

151− key: ${{ runner.os }}-appdata-roaming-stack-${{ hashFiles('stack.yaml') }}

152−

153− # stack's local package dbs for the project and each package

154− # - name: Cache .stack-work

155− # uses: actions/cache@v1

156− # with:

157− # path: .stack-work

158− # key: ${{ runner.os }}-stack-work-${{ hashFiles('stack.yaml') }}

159− # restore-keys: ${{ runner.os }}-stack-work

160−

161− - name: Install dependencies

162− run: |

163− stack update

164− stack install happy

165− stack test --dependencies-only --fast

166− - name: Build and test

167− shell: cmd

168− run: |

169− stack test --fast --test-arguments=--hide-successes

170−

171− macos:

172−

173− runs-on: macOS-10.15

174− strategy:

175− fail-fast: true

176− matrix:

177− versions:

178− - ghc: '8.8.4'

179− cabal: '3.2'

180−

181− steps:

182− - uses: actions/checkout@v2

183−

184− - name: Install recent cabal/ghc

185− uses: haskell/actions/setup@v1

186− with:

187− ghc-version: ${{ matrix.versions.ghc }}

188− cabal-version: ${{ matrix.versions.cabal }}

189−

190− # declare/restore cached things

191− # caching doesn't work for scheduled runs yet

192− # https://github.com/actions/cache/issues/63

193−

194− - name: Cache cabal global package db

195− id: cabal-global

196− uses: actions/cache@v2

197− with:

198− path: |

199− ~/.cabal

200− key: ${{ runner.os }}-${{ matrix.versions.ghc }}-${{ matrix.versions.cabal }}-cabal-global-${{ hashFiles('cabal.project') }}

201−

202− - name: Cache cabal work

203− id: cabal-local

204− uses: actions/cache@v2

205− with:

206− path: |

207− dist-newstyle

208− key: ${{ runner.os }}-${{ matrix.versions.ghc }}-${{ matrix.versions.cabal }}-cabal-local

209−

210− - name: Install dependencies

211− run: |

212− cabal v2-update

213− cabal v2-build --dependencies-only --enable-tests --disable-optimization

214− - name: Build and test

215− run: |

216− cabal v2-build --enable-tests --disable-optimization 2>&1 | tee build.log

217− # fail if warnings in local build

218− ! grep -q ": *[Ww]arning:" build.log || exit 1

219− cabal v2-test --disable-optimization

220−

221− benchmark:

222−

223− runs-on: ubuntu-18.04

224− strategy:

225− fail-fast: true

226− matrix:

227− versions:

228− - ghc: '8.8.4'

229− cabal: '3.2'

230− - ghc: '8.10.2'

231− cabal: '3.2'

232− steps:

233− - uses: actions/checkout@v2

234−

235− # need to install older cabal/ghc versions from ppa repository

236−

237− - name: Install recent cabal/ghc

238− uses: haskell/actions/setup@v1

239− with:

240− ghc-version: ${{ matrix.versions.ghc }}

241− cabal-version: ${{ matrix.versions.cabal }}

242−

243− # declare/restore cached things

244− # caching doesn't work for scheduled runs yet

245− # https://github.com/actions/cache/issues/63

246−

247− - name: Cache cabal global package db

248− id: cabal-global

249− uses: actions/cache@v2

250− with:

251− path: |

252− ~/.cabal

253− key: benchmark-${{ runner.os }}-${{ matrix.versions.ghc }}-${{ matrix.versions.cabal }}-cabal-global-${{ hashFiles('cabal.project') }}

254−

255− - name: Cache cabal work

256− id: cabal-local

257− uses: actions/cache@v2

258− with:

259− path: |

260− dist-newstyle

261− key: benchmark-${{ runner.os }}-${{ matrix.versions.ghc }}-${{ matrix.versions.cabal }}-cabal-local

262−

263− - name: Install dependencies

264− run: |

265− v2=$([ "${{ matrix.versions.cabal }}" = "2.2" ] && printf 'new' || printf 'v2')

266− cabal $v2-update

267− cabal $v2-build --dependencies-only --enable-optimization=1 --enable-benchmarks --disable-tests

268−

269− - name: Build and test

270− run: |

271− v2=$([ "${{ matrix.versions.cabal }}" = "2.2" ] && printf 'new' || printf 'v2')

272− cabal $v2-build --enable-optimization=1 --enable-benchmarks --disable-tests 2>&1 | tee build.log

273− # fail if warnings in local build

274− ! grep -q ": *[Ww]arning:" build.log || exit 1

275− cabal $v2-bench --enable-optimization=1 --benchmark-options='--timeout=6 +RTS -T -RTS'

.github/workflows/commit-validation.ymldeleted−38

@@ -1,38 +0,0 @@

1−name: commit-validation

2−on: [ push, pull_request ]

3−

4−jobs:

5− check-commit-msg-length:

6− runs-on: ubuntu-latest

7− steps:

8− - uses: actions/checkout@v1

9− - name: Check commit message length

10− run: |

11− # Get last commit messages

12− if [ "${{github.event_name}}" = "push" ]; then

13− if [ "${{github.event.before}}" = "0000000000000000000000000000000000000000" ]; then

14− # We are on a new branch

15− current="$(echo '${{github.ref}}' | sed 's!^refs/heads!origin!')"

16− readarray -t other < <(git show-ref | awk -F' ' '{ sub(/^refs\/remotes\//,"",$NF); }($NF != "'"$current"'"){print "^" $NF;}')

17− LOG_RANGE=( "$current" "${other[@]}" )

18− unset current other

19− else

20− # We are on existing branch

21− LOG_RANGE=( "${{github.event.before}}.." )

22− fi

23− elif [ "${{github.event_name}}" = "pull_request" ]; then

24− LOG_RANGE=( "origin/${{github.base_ref}}.." )

25− fi

26− if [[ -v LOG_RANGE ]]; then

27− if git log --no-merges --pretty=format:"%s" "${LOG_RANGE[@]}" -- | grep -qE "^[^#].{78}"; then

28− echo -e "Last commit log contains a line with more than 78 characters:\n"

29− git log --no-merges --pretty=format:"%h: %s" "${LOG_RANGE[@]}" -- | grep -E "^[^:]+: [^#].{78}"

30− echo

31− exit 1

32− else

33− echo "Commit log looks good."

34− fi

35− unset LOG_RANGE

36− else

37− echo "Not checking commits on ${{github.event_name}}"

38− fi

.github/workflows/format-validation.ymldeleted−88

@@ -1,88 +0,0 @@

1−name: Format validation

2−

3−on:

4− push:

5− branches:

6− - '*'

7− - '!rc/*'

8− paths:

9− - 'test/writer.jats_articleauthoring'

10− - 'test/writer.jats_publishing'

11− - 'test/writer.jats_archiving'

12− - 'test/tables.jats_archiving'

13− - 'test/tables/nordics.jats_archiving'

14− - 'test/tables/planets.jats_archiving'

15− - 'test/tables/students.jats_archiving'

16− pull_request:

17− branches:

18− - '*'

19− - '!rc/*'

20− paths:

21− - 'test/writer.jats_articleauthoring'

22− - 'test/writer.jats_publishing'

23− - 'test/writer.jats_archiving'

24− - 'test/tables.jats_archiving'

25− - 'test/tables/nordics.jats_archiving'

26− - 'test/tables/planets.jats_archiving'

27− - 'test/tables/students.jats_archiving'

28−

29−jobs:

30− jats:

31− name: JATS

32− runs-on: ubuntu-latest

33− env:

34− VALIDATOR_URL: "https://jats-validator.hubmed.org/dtd/"

35− strategy:

36− fail-fast: false

37− matrix:

38− tagset:

39− - articleauthoring

40− - publishing

41− - archiving

42− steps:

43− - name: Checkout

44− uses: actions/checkout@v2

45−

46− - name: Validate writer output

47− run: |

48− filename=test/writer.jats_${{ matrix.tagset }}

49− printf "Validating file %s\n" "$filename"

50− json="$(curl --form "xml=@${filename}" --silent "$VALIDATOR_URL")"

51− err_count="$(printf '%s' "$json" | jq '.errors | length')"

52− if [ "$err_count" -eq 0 ]; then

53− printf "File was validated successfully.\n"

54− exit 0

55− else

56− printf "Validator report:\n%s" "$json"

57− exit 1

58− fi

59−

60− - name: Validate tables

61− # Archiving has the simplest template, so we only check with that.

62− if: matrix.tagset == 'archiving'

63− run: |

64− tmpl="$(cat <<EOF

65− <?xml version="1.0" encoding="utf-8" ?>

66− <!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.2 20190208//EN"

67− "JATS-archivearticle1.dtd">

68− <article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="1.2" article-type="other">

69− <front><article-meta></article-meta></front>

70− <body>%s</body></article>

71− EOF

72− )"

73− jats_file="$(mktemp jats-tables.XXXXX)"

74− exit_code=0

75− for f in tables tables/nordics tables/planets tables/students; do

76− filename=test/$f.jats_archiving

77− printf "Validating %s...\n" "$filename"

78− printf "$tmpl" "$(cat $filename)" > "$jats_file"

79− json="$(curl --form "xml=@${jats_file}" --silent "$VALIDATOR_URL")"

80− err_count="$(printf "%s" "$json" | jq '.errors | length')"

81− if [ "$err_count" -eq 0 ]; then

82− printf "Table output is valid when used as body content.\n"

83− else

84− printf "Validator report:\n%s" "$json"

85− exit_code=1

86− fi

87− done

88− exit "$exit_code"

.github/workflows/lint.ymldeleted−33

@@ -1,33 +0,0 @@

1−name: Lint

2−

3−# Trigger the workflow on push or pull request, but only for the

4−# master branch

5−on:

6− pull_request:

7− branch: [master]

8− push:

9− branch: [master]

10− paths-ignore:

11− - LICENSE

12− - README.md

13− - CHANGELOG.md

14− - stack.yaml

15− - .travis.yml

16−

17−jobs:

18− lint:

19− name: Lint

20− runs-on: ubuntu-latest

21− env:

22− hlint_script: https://raw.github.com/ndmitchell/hlint/master/misc/run.sh

23−

24− steps:

25− - name: Checkout

26− uses: actions/checkout@v2

27−

28− - name: Check cabal file for missing test files

29− run: make check-cabal

30−

31− - name: Download and run hlint

32− run: |

33− curl -sSL "${hlint_script}" | sh -s .

.github/workflows/nightly.ymldeleted−91

@@ -1,91 +0,0 @@

1−name: Nightly

2−

3−on:

4− schedule:

5− - cron: '53 7 * * *'

6−

7−jobs:

8− linux:

9−

10− runs-on: ubuntu-18.04

11− steps:

12− - uses: actions/checkout@v2

13−

14− - name: Install recent cabal/ghc

15− uses: haskell/actions/setup@v1

16− with:

17− ghc-version: '8.10.3'

18− cabal-version: '3.2'

19−

20− - name: Install dependencies

21− run: |

22− ghc --version

23− cabal --version

24− cabal v2-update

25− cabal v2-build --dependencies-only

26− - name: Build

27− run: |

28− cabal v2-install

29− strip $HOME/.cabal/bin/pandoc

30− - name: Install artifact

31− run: |

32− export ARTIFACTS=nightly-linux/pandoc-nightly-linux-$(date +%Y-%m-%d)

33− mkdir -p ${ARTIFACTS}

34− cp $HOME/.cabal/bin/pandoc ${ARTIFACTS}/

35− cp COPYRIGHT ${ARTIFACTS}/

36− echo "Built from ${GITHUB_SHA}" > ${ARTIFACTS}/README.nightly.txt

37− - uses: actions/upload-artifact@master

38− with:

39− name: nightly-linux

40− path: nightly-linux

41−

42− windows:

43−

44− runs-on: windows-2019

45−

46− steps:

47− - uses: actions/checkout@v2

48− - name: Install dependencies

49− run: |

50− stack update

51− stack build --dependencies-only pandoc

52− - name: Build artifacts

53− shell: cmd

54− run: |

55− for /f %%a in ('powershell -Command "Get-Date -format yyyy-MM-dd"') do set THEDATE=%%a

56− set ARTIFACTS=%CD%\nightly-windows\pandoc-nightly-windows-%THEDATE%

57− mkdir %ARTIFACTS%

58− stack build pandoc

59− forfiles /P .\.stack-work\install /M pandoc*.exe /S /C "cmd /C copy @path %%ARTIFACTS%%"

60− copy COPYRIGHT %ARTIFACTS%

61− ren %ARTIFACTS%\COPYRIGHT COPYRIGHT.txt

62− echo Built from %GITHUB_SHA% > %ARTIFACTS%\README.nightly.txt

63− - uses: actions/upload-artifact@master

64− with:

65− name: nightly-windows

66− path: nightly-windows

67−

68− macos:

69−

70− runs-on: macOS-10.15

71−

72− steps:

73− - uses: actions/checkout@v2

74− - name: Install dependencies

75− run: |

76− stack update

77− stack build --dependencies-only pandoc

78− - name: Build artifacts

79− run: |

80− export ARTIFACTS=nightly-macos/pandoc-nightly-macos-$(date +%Y-%m-%d)

81− mkdir -p ${ARTIFACTS}

82− stack build pandoc

83− for f in $(find .stack-work/install -name 'pandoc*' -perm +001 -type f); do cp $f ${ARTIFACTS}/; done

84− mv ${ARTIFACTS}/pandoc ${ARTIFACTS}/pandoc

85− cp COPYRIGHT ${ARTIFACTS}/

86− echo "Built from ${GITHUB_SHA}" > ${ARTIFACTS}/README.nightly.txt

87− - uses: actions/upload-artifact@master

88− with:

89− name: nightly-macos

90− path: nightly-macos

91−

.github/workflows/release-candidate.ymldeleted−83

@@ -1,83 +0,0 @@

1−name: Release candidate

2−

3−on:

4− push:

5− branches:

6− - 'rc/**'

7−

8−jobs:

9− linux:

10−

11− runs-on: ubuntu-18.04

12− steps:

13− - uses: actions/checkout@v1

14− - name: Create linux package

15− run: |

16− make debpkg

17− mkdir linux-release-candidate

18− cp linux/artifacts/*.deb linux-release-candidate/

19− cp linux/artifacts/*.tar.gz linux-release-candidate/

20− - uses: actions/upload-artifact@v2

21− with:

22− name: linux-release-candidate

23− path: linux-release-candidate

24−

25− windows:

26−

27− runs-on: windows-2019

28− strategy:

29− fail-fast: true

30− matrix:

31− versions:

32− - osarch: "windows-x86_64"

33− arch: "x64"

34− stack_opts: "-j1"

35− steps:

36− - uses: actions/checkout@v1

37− - name: Install dependencies

38− run: |

39− stack update

40− stack build ${{ matrix.versions.stack_opts }} --dependencies-only pandoc

41− - name: Create windows package

42− shell: cmd

43− run: |

44− for /f %%a in ('powershell -Command "Get-Date -format yyyy-MM-dd"') do set THEDATE=%%a

45− stack build ${{ matrix.versions.stack_opts }} pandoc

46− for /f "tokens=1-2 delims= " %%a in ('stack exec pandoc -- --version') do (

47− @set VERSION=%%b

48− goto :next

49− )

50− :next

51− if "%VERSION%" == "" (

52− echo Error: could not determine version number.

53− exit /b 1

54− )

55− echo Detected version %VERSION%

56− @set WINDOWS=%CD%\windows

57− @set RELEASE=%WINDOWS%\pandoc-%VERSION%

58− mkdir %RELEASE%

59− forfiles /P .\.stack-work\install /M pandoc.exe /S /C "cmd /C echo @path && echo %%WINDOWS%% && copy @path %%RELEASE%%"

60− stack exec pandoc -- -s --toc MANUAL.txt -o %RELEASE%\MANUAL.html

61− stack exec pandoc -- -s COPYING.md -t rtf -o %RELEASE%\COPYING.rtf

62− copy %RELEASE%\COPYING.rtf %WINDOWS%

63− copy COPYRIGHT %RELEASE%\COPYRIGHT.txt

64− cd windows

65− echo Creating msi...

66− dir

67− @set WIXBIN="c:\Program Files (x86)\WiX Toolset v3.11\bin"

68− @set WORKDIR=%CD%

69− echo Running candle...

70− %WIXBIN%\candle -arch ${{ matrix.versions.arch }} -dVERSION=%VERSION% -dBINPATH=%RELEASE% *.wxs -out wixobj\

71− if %errorlevel% neq 0 exit /b %errorlevel%

72− echo Running light...

73− %WIXBIN%\light -sw1076 -ext WixUIExtension -ext WixUtilExtension -cultures:en-us -loc Pandoc-en-us.wxl -out %WORKDIR%\pandoc-%VERSION%-${{ matrix.versions.osarch }}-UNSIGNED.msi wixobj\*.wixobj

74− 7z a "pandoc-%VERSION%-${{ matrix.versions.osarch }}.zip" pandoc-%VERSION%

75− cd ..

76− mkdir windows-release-candidate

77− copy windows\pandoc-%VERSION%-${{ matrix.versions.osarch }}-UNSIGNED.msi windows-release-candidate

78− copy windows\pandoc-%VERSION%-${{ matrix.versions.osarch }}.zip windows-release-candidate

79− copy windows\Makefile windows-release-candidate

80− - uses: actions/upload-artifact@v2

81− with:

82− name: windows-release-candidate

83− path: windows-release-candidate

.gitignore+4−19

@@ -1,35 +1,20 @@

11*~

2−.DS_Store

3−*.orig

4−deb/.vagrant

52dist/*

6−MANUAL.*

7−!MANUAL.txt

3+README.*

4+!README.Debian

5+INSTALL.*

86.configure-stamp

9−.cabal-sandbox

10−cabal.sandbox.config

11−pandoc.cabal.orig

127man/man?/*.1

138man/man?/*.5

149man/man?/*.html

1510*.diff

11+pandoc.cabal.orig

1612*.o

1713*.hi

1814*.pyc

19−.hie/

20−.policeman-evidence/

21−.projectile/

22−.vscode/

2315/COPYING.rtf

2416/COPYRIGHT.txt

2517/cabal-dev/

2618/windows/*.msi

2719/windows/*.wixpdb

2820windows/*.wixobj

29−data/reference.docx

30−data/reference.odt

31−.stack-work

32−/stack.yaml.lock

33−cabal.project.local

34−/dist-newstyle/

35−pandoc-2*/

.gitmodulesnew file+3

@@ -0,0 +1,3 @@

1+[submodule "templates"]

2+ path = data/templates

3+ url = https://github.com/jgm/pandoc-templates.git

.hlint.yamldeleted−112

@@ -1,112 +0,0 @@

1−# HLint configuration file

2−# https://github.com/ndmitchell/hlint

3−##########################

4−

5−# Specify additional command line arguments

6−#

7−- arguments: [--color=auto, --cpp-ansi]

8−

9−# Ignore some builtin hints

10−#

11−- ignore: {name: "Avoid lambda"}

12−- ignore: {name: "Use bimap"}

13−- ignore: {name: "Eta reduce"}

14−- ignore: {name: "Evaluate"}

15−- ignore: {name: "Reduce duplication"} # TODO: could be more fine-grained

16−- ignore: {name: "Use &&&"}

17−- ignore: {name: "Use String"}

18−- ignore: {name: "Use camelCase"}

19−- ignore: {name: "Use fmap"} # specific for GHC 7.8 compat

20−- ignore: {name: "Use isDigit"}

21−

22−- ignore:

23− name: "Monad law, left identity"

24− within: Text.Pandoc.App.OutputSettings

25−

26−- ignore:

27− name: "Move brackets to avoid $"

28− within: Text.Pandoc.Writers.CslJson

29−

30−- ignore:

31− name: "Redundant <$>"

32− within:

33− - Text.Pandoc.Readers.Docx.Parse

34− - Text.Pandoc.Writers.MediaWiki

35− - Text.Pandoc.Writers.OpenDocument

36− - Text.Pandoc.Writers.Powerpoint.Output

37− - Text.Pandoc.Writers.Powerpoint.Presentation

38−

39−- ignore:

40− name: "Redundant return"

41− within: Text.Pandoc.Citeproc.BibTeX

42−

43−# With recent hlint this rule has given false positives on TH

44−- ignore:

45− name: "Redundant bracket"

46−

47−

48−- ignore:

49− name: "Use <$>"

50− within:

51− - Text.Pandoc.Readers.LaTeX

52− - Text.Pandoc.Readers.Markdown

53−

54−- ignore:

55− name: "Use camelCase"

56− within:

57− - Tests.Writers.Docbook

58− - Tests.Writers.Native

59− - Text.Pandoc.Citeproc

60− - Text.Pandoc.Extensions

61− - Text.Pandoc.Lua.Marshaling.Version

62− - Text.Pandoc.Lua.Module.Pandoc

63− - Text.Pandoc.Lua.Module.Utils

64− - Text.Pandoc.Readers.Odt.ContentReader

65− - Text.Pandoc.Readers.Odt.Namespaces

66−

67−- ignore:

68− name: "Use forM_"

69− within:

70− - Text.Pandoc.Readers.DocBook

71−

72−- ignore:

73− name: "Use Just"

74− within:

75− - Text.Pandoc.Citeproc.MetaValue

76− - Text.Pandoc.Readers.Odt.ContentReader

77− - Text.Pandoc.Writers.Roff

78−

79−- ignore:

80− name: "Use list comprehension"

81− within: Text.Pandoc.Citeproc.BibTeX

82−

83−- ignore:

84− name: "Use list literal pattern"

85− within: Text.Pandoc.Citeproc.MetaValue

86−

87−# TODO: check

88−- ignore:

89− name: "Use second"

90− within:

91− - Text.Pandoc.Citeproc.BibTeX

92− - Text.Pandoc.Citeproc.Locator

93−

94−# TODO: check

95−- ignore:

96− name: "Use sortOn"

97− within: Text.Pandoc.Writers.OpenDocument

98−

99−- ignore:

100− name: "Use tuple-section"

101− within:

102− - Text.Pandoc.Readers.EPUB

103− - Text.Pandoc.ImageSize

104− - Text.Pandoc.Readers.Markdown

105− - Text.Pandoc.Readers.RST

106−

107−# fromRight is only in base >= 4.10

108−- ignore:

109− name: "Use fromRight"

110−

111−# Define some custom infix operators

112−# - fixity: infixr 3 ~^#^~

.mailmapdeleted−37

@@ -1,37 +0,0 @@

1−Adam Brandizzi <brandizzi@gmail.com>

2−Albert Krewinkel <albert@zeitkraut.de> <albert+github@zeitkraut.de>

3−Albert Krewinkel <albert@zeitkraut.de> <albert.krewinkel@tourstream.eu>

4−Albert Krewinkel <albert@zeitkraut.de> <tarleb@moltkeplatz.de>

5−Albert Krewinkel <albert@zeitkraut.de> <tarleb@zeitkraut.de>

6−Alexander Krotov <ilabdsf@gmail.com>

7−Alex Ivkin <alex@ivkin.net>

8−Alex Ivkin <alex@ivkin.net> <alexivkin@users.noreply.github.com>

9−Andrew Dunning <andunning@gmail.com>

10−Andrew Dunning <andunning@gmail.com> <adunning@users.noreply.github.com>

11−Andrew Newman <andrewfnewman@gmail.com>

12−Clare Macrae <clare.macrae@googlemail.com> <github@cfmacrae.fastmail.co.uk>

13−Hugo Roy <hugo@fsfe.org>

14−Hugo Roy <hugo@xps.ampoliros.net>

15−John MacFarlane <jgm@berkeley.edu> <fiddlosopher@788f1e2b-df1e-0410-8736-df70ead52e1b>

16−John MacFarlane <jgm@berkeley.edu> <fiddlosopher@gmail.com>

17−John MacFarlane <jgm@berkeley.edu> <jgm@Johns-MacBook-Pro.local>

18−Jose Luis Duran <jlduran@gmail.com> <jlduran@users.noreply.github.com>

19−Marc Schreiber <schrieveslaach@online.de>

20−Masayoshi Takahashi <maki@rubycolor.org>

21−Matthew Pickering <matthewtpickering@gmail.com>

22−Mauro Bieg <mauro.bieg@gmail.com>

23−Mauro Bieg <mauro.bieg@gmail.com> <maurobieg@Mauros-MacBook-Air.local>

24−Mauro Bieg <mauro.bieg@gmail.com> <mb21@server.fake>

25−Mauro Bieg <mauro.bieg@gmail.com> <mb21@users.noreply.github.com>

26−Mauro Bieg <mb21@users.noreply.github.com>

27−Nils Carlson <nils.carlson@ludd.ltu.se>

28−Nils Carlson <nils.carlson@ludd.ltu.se> <pyssling@ludd.ltu.se>

29−Robin Lambertz <robinlambertz+dev@gmail.com>

30−Roland Hieber <rohieb@rohieb.name> <rohieb@users.noreply.github.com>

31−Sebastian Talmon <35015406+stalmon@users.noreply.github.com>

32−Sergei Trofimovich <slyfox@gentoo.org> <siarheit@google.com>

33−Sergei Trofimovich <slyfox@gentoo.org> <slyfox@inbox.ru>

34−Stefan Björk <stefan.bjork@gmail.com> <stefan@airistotle.local>

35−Thomas Hodgson <hello@twshodgson.net> <twsh@users.noreply.github.com>

36−Timm Albers <timmm.albers@gmail.com> <timm.albers@open-xchange.com>

37−Yan Pashkovsky <yanpaso@gmail.com> <Yanpas@users.noreply.github.com>

.stylish-haskell.yamldeleted−171

@@ -1,171 +0,0 @@

1−# stylish-haskell configuration file

2−# ==================================

3−

4−# The stylish-haskell tool is mainly configured by specifying steps. These steps

5−# are a list, so they have an order, and one specific step may appear more than

6−# once (if needed). Each file is processed by these steps in the given order.

7−steps:

8− # Convert some ASCII sequences to their Unicode equivalents. This is disabled

9− # by default.

10− # - unicode_syntax:

11− # # In order to make this work, we also need to insert the UnicodeSyntax

12− # # language pragma. If this flag is set to true, we insert it when it's

13− # # not already present. You may want to disable it if you configure

14− # # language extensions using some other method than pragmas. Default:

15− # # true.

16− # add_language_pragma: true

17−

18− # Align the right hand side of some elements. This is quite conservative

19− # and only applies to statements where each element occupies a single

20− # line.

21− - simple_align:

22− cases: true

23− top_level_patterns: true

24− records: true

25−

26− # Import cleanup

27− - imports:

28− # There are different ways we can align names and lists.

29− #

30− # - global: Align the import names and import list throughout the entire

31− # file.

32− #

33− # - file: Like global, but don't add padding when there are no qualified

34− # imports in the file.

35− #

36− # - group: Only align the imports per group (a group is formed by adjacent

37− # import lines).

38− #

39− # - none: Do not perform any alignment.

40− #

41− # Default: global.

42− align: none

43−

44− # Following options affect only import list alignment.

45− #

46− # List align has following options:

47− #

48− # - after_alias: Import list is aligned with end of import including

49− # 'as' and 'hiding' keywords.

50− #

51− # > import qualified Data.List as List (concat, foldl, foldr, head,

52− # > init, last, length)

53− #

54− # - with_alias: Import list is aligned with start of alias or hiding.

55− #

56− # > import qualified Data.List as List (concat, foldl, foldr, head,

57− # > init, last, length)

58− #

59− # - new_line: Import list starts always on new line.

60− #

61− # > import qualified Data.List as List

62− # > (concat, foldl, foldr, head, init, last, length)

63− #

64− # Default: after_alias

65− list_align: after_alias

66−

67− # Long list align style takes effect when import is too long. This is

68− # determined by 'columns' setting.

69− #

70− # - inline: This option will put as much specs on same line as possible.

71− #

72− # - new_line: Import list will start on new line.

73− #

74− # - new_line_multiline: Import list will start on new line when it's

75− # short enough to fit to single line. Otherwise it'll be multiline.

76− #

77− # - multiline: One line per import list entry.

78− # Type with constructor list acts like single import.

79− #

80− # > import qualified Data.Map as M

81− # > ( empty

82− # > , singleton

83− # > , ...

84− # > , delete

85− # > )

86− #

87− # Default: inline

88− long_list_align: inline

89−

90− # List padding determines indentation of import list on lines after import.

91− # This option affects 'list_align' and 'long_list_align'.

92− list_padding: 4

93−

94− # Separate lists option affects formatting of import list for type

95− # or class. The only difference is single space between type and list

96− # of constructors, selectors and class functions.

97− #

98− # - true: There is single space between Foldable type and list of it's

99− # functions.

100− #

101− # > import Data.Foldable (Foldable (fold, foldl, foldMap))

102− #

103− # - false: There is no space between Foldable type and list of it's

104− # functions.

105− #

106− # > import Data.Foldable (Foldable(fold, foldl, foldMap))

107− #

108− # Default: true

109− separate_lists: true

110−

111− # Language pragmas

112− - language_pragmas:

113− # We can generate different styles of language pragma lists.

114− #

115− # - vertical: Vertical-spaced language pragmas, one per line.

116− #

117− # - compact: A more compact style.

118− #

119− # - compact_line: Similar to compact, but wrap each line with

120− # `{-#LANGUAGE #-}'.

121− #

122− # Default: vertical.

123− style: vertical

124−

125− # Align affects alignment of closing pragma brackets.

126− #

127− # - true: Brackets are aligned in same column.

128− #

129− # - false: Brackets are not aligned together. There is only one space

130− # between actual import and closing bracket.

131− #

132− # Default: true

133− align: true

134−

135− # stylish-haskell can detect redundancy of some language pragmas. If this

136− # is set to true, it will remove those redundant pragmas. Default: true.

137− remove_redundant: true

138−

139− # Replace tabs by spaces. This is disabled by default.

140− # - tabs:

141− # # Number of spaces to use for each tab. Default: 8, as specified by the

142− # # Haskell report.

143− # spaces: 8

144−

145− # Remove trailing whitespace

146− - trailing_whitespace: {}

147−

148−# A common setting is the number of columns (parts of) code will be wrapped

149−# to. Different steps take this into account. Default: 80.

150−columns: 80

151−

152−# By default, line endings are converted according to the OS. You can override

153−# preferred format here.

154−#

155−# - native: Native newline format. CRLF on Windows, LF on other OSes.

156−#

157−# - lf: Convert to LF ("\n").

158−#

159−# - crlf: Convert to CRLF ("\r\n").

160−#

161−# Default: native.

162−newline: native

163−

164−# Sometimes, language extensions are specified in a cabal file or from the

165−# command line instead of using language pragmas in the file. stylish-haskell

166−# needs to be aware of these, so it can parse the file correctly.

167−#

168−# No language extensions are enabled by default.

169−# language_extensions:

170− # - TemplateHaskell

171− # - QuasiQuotes

.travis.ymlnew file+8

@@ -0,0 +1,8 @@

1+language: haskell

2+before_install:

3+ - cabal install cabal-dev

4+ - 'git clone https://github.com/jgm/pandoc-types && cabal-dev add-source pandoc-types'

5+install:

6+ - cabal-dev install-deps --enable-tests

7+script:

8+ - 'cabal-dev configure --enable-tests && cabal-dev build && cabal-dev test'

AUTHORS.mddeleted−330

@@ -1,330 +0,0 @@

1−# Contributors

2−

3−- Anabra

4−- Aner Lucero

5−- Arata Mizuki

6−- Arfon Smith

7−- Aaron Wolen

8−- Albert Krewinkel

9−- Alex Ivkin

10−- Alex Toldaiev

11−- Alex Vong

12−- Alexander Kondratskiy

13−- Alexander Krotov

14−- Alexander Sulfrian

15−- Alexander V Vershilov

16−- Alexandre Franke

17−- Alfred Wechselberger

18−- Amogh Rathore

19−- Anders Waldenborg

20−- Andreas Lööw

21−- Andrew Dunning

22−- Andy Morris

23−- Anti-Distinctlyminty

24−- Antoine Latter

25−- Antonio Terceiro

26−- Arata Mizuki

27−- Arfon Smith

28−- Arlo O'Keeffe

29−- Artyom Kazak

30−- Agustín Martín Barbero

31−- B. Scott Michel

32−- Ben Firshman

33−- Ben Gamari

34−- Ben Steinberg

35−- Beni Cherniavsky-Paskin

36−- Benoit Schweblin

37−- Bjorn Buckwalter

38−- Blake Eryx

39−- Bodigrim

40−- Bradley Kuhn

41−- Brent Yorgey

42−- Brian Leung

43−- Bryan O'Sullivan

44−- Caleb McDaniel

45−- Caleb Mclennan

46−- Calvin Beck

47−- Carlos Sosa

48−- Cécile Chemin

49−- Cédric Couralet

50−- Charanjit Singh

51−- Chris Black

52−- Christian Conkle

53−- Christian Despres

54−- Christoffer Ackelman

55−- Christoffer Sawicki

56−- Clare Macrae

57−- Clint Adams

58−- Conal Elliott

59−- Cormac Relf

60−- Craig S. Bosma

61−- Damien Clochard

62−- Daniel Bergey

63−- Daniel Maslowski

64−- Daniel T. Staal

65−- Daniele D'Orazio

66−- David A Roberts

67−- David Lazar

68−- David Martschenko

69−- David Röthlisberger

70−- Denis Laxalde

71−- Denis Maier

72−- Derek Chen-Becker

73−- Diego Balseiro

74−- Dimitri Sabadie

75−- Dmitry Pogodin

76−- Dmitry Volodin

77−- Douglas Calvert

78−- Eigil Rischel

79−- Emanuel Evans

80−- Emerson Harkin

81−- Emily Bourke

82−- Emily Eisenberg

83−- Eric Kow

84−- Erik Rask

85−- Eric Seidel

86−- Eric Schrijver

87−- Ethan Riley

88−- Étienne Bersac

89−- Felix Yan

90−- Félix Baylac-Jacqué

91−- Florian Beeres

92−- Florian Eitel

93−- Florian Klink

94−- Florian Kohrt

95−- Francesco Occhipinti

96−- François Gannaz

97−- Frederik Elwert

98−- Freiric Barral

99−- Freirich Raabe

100−- Frerich Raabe

101−- Fyodor Sheremetyev

102−- Gabor Pali

103−- Gavin Beatty

104−- Gottfried Haider

105−- Greg Maslov

106−- Greg Rundlett

107−- Grégory Bataille

108−- Gwern Branwen

109−- Hamish Mackenzie

110−- Hans-Peter Deifel

111−- Heiko Schlittermann

112−- Henrik Tramberend

113−- Henry de Valence

114−- Hubert Plociniczak

115−- Ian Max Andolina

116−- Igor Khorlo

117−- Igor Pashev

118−- Ilya V. Portnov

119−- Ivan Trubach

120−- Ivo Clarysse

121−- Jared Lander

122−- J. B. Rainsberger

123−- J. Lewis Muir

124−- Jaime Marquínez Ferrándiz

125−- Jake Zimmerman

126−- Jakob Voß

127−- James Aspnes

128−- Jamie F. Olson

129−- Jan Larres

130−- Jan Schulz

131−- Jan Tojnar

132−- Jan-Otto Kröpke

133−- Jason Ronallo

134−- Jeff Arnold

135−- Jeff Runningen

136−- Jens Getreu

137−- Jens Petersen

138−- Jeroen de Haas

139−- Jerry Sky

140−- Jesse Rosenthal

141−- Joe Hermaszewski

142−- Joe Hillenbrand

143−- John KetzerX

144−- John MacFarlane

145−- John Muccigrosso

146−- John Luke Bentley

147−- Jonas Smedegaard

148−- Jonas Scholl

149−- Jonathan Daugherty

150−- Jose Luis Duran

151−- José de Mattos Neto

152−- Josef Svenningsson

153−- Joseph C. Sible

154−- Julien Cretel

155−- Julien Dutant

156−- Juliette Fourcot

157−- Juliusz Gonera

158−- Justin Bogner

159−- Jérémy Bobbio

160−- Karl Pettersson

161−- Keiichiro Shikano

162−- Kelsey Hightower

163−- Kolen Cheung

164−- Konstantin Zudov

165−- Kristof Bastiaensen

166−- Krystof Beuermann

167−- Herwig Stuetz

168−- Lars-Dominik Braun

169−- Laurent P. René de Cotret

170−- Leif Metcalf

171−- Leonard Rosenthol

172−- Lila

173−- Loïc Grobol

174−- Lorenzo

175−- Lucas Escot

176−- Luke Plant

177−- Marc Schreiber

178−- Mark Szepieniec

179−- Mark Wright

180−- Martin Linn

181−- Masayoshi Takahashi

182−- Matej Kollar

183−- Mathias Schenner

184−- Mathias Walter

185−- Mathieu Boespflug

186−- Mathieu Duponchelle

187−- Matthew Doty

188−- Matthew Eddey

189−- Matthew Pickering

190−- Matthias C. M. Troffaes

191−- Mauro Bieg

192−- Max Bolingbroke

193−- Max Rydahl Andersen

194−- Merijn Verstraaten

195−- Michael Beaumont

196−- Michael Chladek

197−- Michael Hoffmann

198−- Michael Peyton Jones

199−- Michael Reed

200−- Michael Snoyman

201−- Michael Thompson

202−- Mike Tzou

203−- MinRK

204−- Morton Fox

205−- Nathan Gass

206−- Neil Mayhew

207−- Nick Bart

208−- Nick Berendsen

209−- Nick Fleisher

210−- Nicolas Kaiser

211−- Nikolay Yakimov

212−- Nils Carlson

213−- Nixon Enraght-Moony

214−- Nokome Bentley

215−- Ole Martin Ruud

216−- Oliver Matthews

217−- Ophir Lifshitz

218−- Or Neeman

219−- OvidiusCicero

220−- Owen McGrath

221−- Pablo Rodríguez

222−- Pascal Wagler

223−- Paul Tilley

224−- Paul Rivier

225−- Paulo Tanimoto

226−- Pete Ryland

227−- Peter Wang

228−- Philip Pesca

229−- Philippe Ombredanne

230−- Phillip Alday

231−- Prayag Verma

232−- Puneeth Chaganti

233−- Ralf Stephan

234−- Raniere Silva

235−- Raymond Ehlers

236−- Recai Oktaş

237−- Roland Hieber

238−- Roman Beránek

239−- RyanGlScott

240−- Salim B

241−- Sascha Wilde

242−- Scott Morrison

243−- Sebastian Talmon

244−- Sergei Trofimovich

245−- Sergey Astanin

246−- Shahbaz Youssefi

247−- Shaun Attfield

248−- Shim Myeongseob

249−- Shin Sang-jae

250−- Sidarth Kapur

251−- Sidharth Kapur

252−- Simon Hengel

253−- Stefan Dresselhaus

254−- Sumit Sahrawat

255−- Tarik Graba

256−- Tatiana Porras

257−- Thenaesh Elango

258−- Thomas Hodgson

259−- Thomas Weißschuh

260−- Tim Lin

261−- Timm Albers

262−- Timothy Humphries

263−- Tiziano Müller

264−- Todd Sifleet

265−- Tom Leese

266−- Tristan de Cacqueray

267−- Tristan Stenner

268−- Uli Köhler

269−- Urs Liska

270−- Václav Zeman

271−- Václav Haisman

272−- Vaibhav Sagar

273−- Vanessa McHale

274−- Vasily Alferov

275−- Viktor Kronvall

276−- Vincent

277−- Vlad Hanciuta

278−- Wandmalfarbe

279−- Waldir Pimenta

280−- Wikiwide

281−- Winnie Hellmann

282−- Xavier Olive

283−- Yan Pashkovsky

284−- Yoan Blanc

285−- Yuchen Pei

286−- Zihang Chen

287−- a-vrma

288−- andrebauer

289−- argent0

290−- badumont

291−- blmage

292−- bucklereed

293−- bumper314

294−- chinapedia

295−- cholonam

296−- csforste

297−- dbecher-ito

298−- d-dorazio

299−- ebiim

300−- favonia

301−- infinity0x

302−- jeongminkim-islab

303−- kaizshang91

304−- lux-lth

305−- lwolfsonkin

306−- mbrackeantidot

307−- nkalvi

308−- niszet

309−- nuew

310−- obcat

311−- oltolm

312−- oquechy

313−- quasicomputational

314−- qerub

315−- robabla

316−- roblabla

317−- rodja.trappe

318−- rski

319−- shreevatsa.public

320−- takahashim

321−- taotieren

322−- tecosaur

323−- TEC

324−- tgkokk

325−- the-solipsist

326−- timo-a

327−- thsutton

328−- vijayphoenix

329−- wiefling

330−- wuffi

CONTRIBUTING.md+47−341

@@ -1,174 +1,41 @@

11Contributing to pandoc

22======================

33

4−Welcome to pandoc! Very soon after its beginnings in 2006, pandoc

5−has been influenced, improved, and modified, by users, devs, and

6−newcomers alike. The project thrives on its active community. It is

7−great to have you here.

8−

9−How can I help?

10−---------------

11−

12−There are many ways in which you can support pandoc. Here are a few

13−ideas:

14−

15− * Participate in online discussions. The [pandoc-discuss] mailing

16− list is a good place for this. This gives valuable input and

17− makes it easier to improve the program.

18−

19− * Help with questions. Every request that is answered by the wider

20− community frees time for programming contributors. This will

21− speed up development of new features and issue fixes. Don't

22− underestimate your knowledge, please share it!

23−

24− Good places to help are the [pandoc-discuss] mailing list, Q/A

25− sites like StackOverflow, community forums (e.g.

26− [RStudio][RStudio Community], [Zettlr][Zettlr Forum]), and, for

27− technical questions, the GitHub [issue tracker].

28−

29− * Write or improve documentation. If you ran into a problem which

30− took more time to figure out than expected, please consider to

31− save other users from the same experience. People writing the

32− documentation tend to lack an outside view, so please help

33− provide one. Good documentation is both difficult and extremely

34− important.

35−

36− The official docs are not the only place for documentation.

37− Pandoc also has a [Wiki][pandoc wiki]. Private blogs can serve

38− as documentation just as the official manual can.

39−

40− * Contribute code. No matter whether it's a small fix in a format

41− template or a huge lump of Haskell code: help is welcome. It's

42− usually a good idea to talk about the plans early, as this can

43− prevent unnecessary work. See below for more information.

44−

45− * Last but not least: consider funding the development and

46− maintenance of pandoc financially. You can find sponsor buttons

47− on the [pandoc website] and the [GitHub repository][GitHub

48− repo].

49−

50−A rich ecosystem of libraries, editors, filters, and templates has

51−developed around pandoc; conversely, pandoc builds and depends on a

52−large number of libraries. Contributing to any of these projects is

53−another way that can help to ensure stability, and to keep pushing

54−the boundaries of what is possible with pandoc.

55−

56−[RStudio Community]: https://community.rstudio.com/

57−[Zettlr Forum]: https://forum.zettlr.com/

58−[pandoc wiki]: https://github.com/jgm/pandoc/wiki

59−[pandoc website]: https://pandoc.org

60−[GitHub repo]: https://github.com/jgm/pandoc

61−

62−Have a question?

63−----------------

64−

65−Ask on [pandoc-discuss].

66−

67−

684Found a bug?

695------------

706

71−Bug reports are welcome! Please report all bugs on pandoc's GitHub

7+Bug reports are welcome! Please report all bugs on pandoc's github

728[issue tracker].

739

74−Before you submit a bug report, search the [open issues] *and* [closed issues]

75−to make sure the issue hasn't come up before. Also, check the [User's Guide] and

76−[FAQs] for anything relevant.

10+Before you submit a bug report, search the (open *and* closed) issues to make

11+sure the issue hasn't come up before. Also, check the [User's Guide] and [FAQs]

12+for anything relevant.

7713

78−Make sure you can reproduce the bug with the [latest released

79−version] of pandoc---or, even better, the development version,

80−since the bug may have been fixed since the last release.

81−[Nightly builds] are available, so you don't need to compile

82−from source to test against the development version.

83−(To fetch a nightly, visit the link, click the topmost "Nightly"

84−in the table, then choose your platform under "Artifacts." Note

85−that you must be logged in with a GitHub account.)

14+Make sure you can reproduce the bug with the latest released version of pandoc

15+(or, even better, the development version).

8616

87−Your report should give detailed, *reproducible* instructions, including

17+Your report should give detailed instructions for how to reproduce the problem,

18+including

8819

89− * the pandoc version (check using `pandoc -v`)

9020 * the exact command line used

9121 * the exact input used

9222 * the output received

9323 * the output you expected instead

9424

9525A small test case (just a few lines) is ideal. If your input is large,

96−try to whittle it down to a *minimum working example*.

97−

98−Out of scope?

99−-------------

100−

101−A less than perfect conversion does not necessarily mean there's

102−a bug in pandoc. Quoting from the MANUAL:

103−

104−> Because pandoc's intermediate representation of a document is less

105−> expressive than many of the formats it converts between, one should

106−> not expect perfect conversions between every format and every other.

107−> Pandoc attempts to preserve the structural elements of a document, but

108−> not formatting details such as margin size. And some document elements,

109−> such as complex tables, may not fit into pandoc's simple document

110−> model. While conversions from pandoc's Markdown to all formats aspire

111−> to be perfect, conversions from formats more expressive than pandoc's

112−> Markdown can be expected to be lossy.

113−

114−For example, both `docx` and `odt` formats can represent margin size, but

115−because pandoc's internal document model does not contain a representation of

116−margin size, this information will be lost on converting from docx

117−to `odt`. (You can, however, customize margin size using `--reference-doc`.)

118−

119−So before submitting a bug report, consider whether it might be

120−"out of scope." If it concerns a feature of documents that isn't

121−representable in pandoc's Markdown, then it very likely is.

122−(If in doubt, you can always ask on [pandoc-discuss].)

123−

124−Fixing bugs from the issue tracker

125−----------------------------------

126−

127−Almost all the bugs on the issue tracker have one or more associated

128−tags. These are used to indicate the *complexity* and *nature* of a

129−bug. There is not yet a way to indicate priority. An up to date

130−summary of issues can be found on [GitHub labels].

131−

132−* [good first issue] — The perfect starting point for new contributors. The

133− issue is generic and can be resolved without deep knowledge of the code

134− base.

135−* [enhancement] — A feature which would be desirable. We recommend

136− you discuss any proposed enhancement on pandoc-discuss before

137− writing code.

138−* [bug] — A problem which needs to be fixed.

139−* [complexity:low] — The fix should only be a couple of lines.

140−* [complexity:high] — The fix might require structural changes or in depth

141− knowledge of the code base.

142−* [new:reader] — A request to add a new input format.

143−* [new:writer] — A request to add a new output format.

144−* [docs] — A discrepancy, or ambiguity in the documentation.

145−* [status:in-progress] — Someone is actively working on or planning to work on the

146− ticket.

147−* [status:more-discussion-needed] — It is unclear what the correct approach

148− to solving the ticket is. Before starting on tickets such as this it

149− would be advisable to post on the ticket.

150−* [status:more-info-needed] — We require more information from a user before

151− we can classify a report properly.

152−

153−Issues related to a specific format are tagged accordingly, e.g. feature request

154−or bug reports related to Markdown are labelled with [format:markdown].

26+try to whittle it down to the minimum necessary to illustrate the problem.

15527

15628Have an idea for a new feature?

15729-------------------------------

15830

159−First, search [pandoc-discuss] and the issue tracker (both [open issues] *and*

160−[closed issues]) to make sure that the idea has not been discussed before.

31+First, search [pandoc-discuss] and the issue tracker (both open and closed

32+issues) to make sure that the idea has not been discussed before.

16133

16234Explain the rationale for the feature you're requesting. Why would this

16335feature be useful? Consider also any possible drawbacks, including backwards

16436compatibility, new library dependencies, and performance issues.

16537

166−Features are very rarely "implement and forget", as all code must be

167−maintained. This is especially relevant for large or complex

168−contributions. It is helpful to be sympathetic to that fact, and to

169−communicate future plans and availability clearly.

170−

171−Any potential new feature is best discussed on [pandoc-discuss]

38+It is best to discuss a potential new feature on [pandoc-discuss]

17239before opening an issue.

17340

17441Patches and pull requests

@@ -193,8 +60,6 @@ Please follow these guidelines:

193603. Follow the stylistic conventions you find in the existing

19461 pandoc code. Use spaces, not tabs, and wrap code to 80 columns.

19562 Always include type signatures for top-level functions.

196− Consider installing [EditorConfig], this will help you to follow the

197− coding style prevalent in pandoc.

19863

199644. Your code should compile without warnings (`-Wall` clean).

20065

@@ -205,7 +70,7 @@ Please follow these guidelines:

20570 below under [Tests](#tests).) If you are adding a new writer or reader,

20671 you must include tests.

20772

208−7. If you are adding a new feature, include updates to `MANUAL.txt`.

73+7. If you are adding a new feature, include updates to the README.

20974

210758. All code must be released under the general license governing pandoc

21176 (GPL v2).

@@ -213,180 +78,50 @@ Please follow these guidelines:

213789. It is better not to introduce new dependencies. Dependencies on

21479 external C libraries should especially be avoided.

21580

216−10. We aim for compatibility with ghc versions from 8.0 to the

217− latest release. All pull requests and commits are tested

218− automatically on GitHub Actions.

219−

22081Tests

22182-----

22283

22384Tests can be run as follows:

22485

225− cabal install --only-dependencies --enable-tests

22686 cabal configure --enable-tests

22787 cabal build

22888 cabal test

22989

230−or, if you're using [stack],

231−

232− stack setup

233− stack test

234−

235−The test program is `test/test-pandoc.hs`.

236−

237−To run particular tests (pattern-matching on their names), use

238−the `-p` option:

239−

240− cabal install pandoc --enable-tests

241− cabal test --test-options='-p markdown'

242−

243−Or with stack:

244−

245− stack test --test-arguments='-p markdown'

246−

247−It is often helpful to add `-j4` (run tests in parallel) and

248−`--hide-successes` (don't clutter output with successes) to the test

249−arguments as well. Collecting all options in a `cabal.project.local`

250−file in the project's root directory can help to keep `cabal`

251−commands short. E.g.:

252−

253− flags: +embed_data_files

254− tests: True

255− test-show-details: direct

256− test-options: -j4 --hide-successes

257−

258−If you add a new feature to pandoc, please add tests as well, following

259−the pattern of the existing tests. The test suite code is in

260−`test/test-pandoc.hs`. If you are adding a new reader or writer, it is

261−probably easiest to add some data files to the `test` directory, and

262−modify `test/Tests/Old.hs`. Otherwise, it is better to modify the module

263−under the `test/Tests` hierarchy corresponding to the pandoc module you

264−are changing. Alternatively, you may add a "command test" to

265−the `/test/command/` hierarchy, following the pattern of the tests there.

266−These test files should have a meaningful name, which can include the issue

267−number and/or the feature that's being tested. For example, `5474-tables.md`

268−refers to both issue and feature.

269−

270−You can rebuild the golden tests in `tests/` by passing

271−`--accept` to the test script. (If you're using stack, `stack

272−test --test-arguments "--accept"`; or `make TESTARGS=--accept`).

273−Then check the changed golden files for accuracy, and

274−commit the changes. For docx or pptx tests, open the files in Word

275−or Powerpoint to ensure that they weren't corrupted and that

276−they had the expected result, and mention the Word/Powerpoint

277−version and OS in your commit comment.

278−

279−Code style

280−----------

281−

282−Pandoc uses [hlint] to identify opportunities for code improvements

283−like redundant brackets or unnecessary `Language` extensions.

284−However, sometimes there are cases where there are good reasons to

285−use code different from what hlint proposes. In these cases, the

286−respective warning should be disabled in the file `.hlint.yaml`.

287−

288−There should be no errors when running `hlint .`; this is checked by

289−the continuous integration (CI) setup. It is recommended that

290−contributors check their code with a local hlint installation, but

291−relying on the CI is fine, too.

292−

293−A good way to ensure no new warnings are introduced is to use a Git

294−[pre-commit hook] which runs hlint on all updated Haskell files

295−before creating a commit:

296−

297− #!/bin/sh

298− git diff --diff-filter=MA --cached --name-only | grep '\.hs$' | \

299− xargs hlint --hint .hlint.yaml

300−

301−(If you are using GNU `xargs`, add the `-r` option immediately

302−after `xargs`.)

303−

304−Saving this to `.git/hooks/pre-commit`, and making the script

305−executable, will prevent accidental introduction of potentially

306−problematic code.

307−

308−Benchmarks

309−----------

310−

311−To run benchmarks with cabal:

312−

313− cabal configure --enable-benchmarks

314− cabal build

315− cabal bench

316−

317−With stack:

318−

319− stack bench

320−

321−

322−Using the REPL

323−--------------

90+The test program is `tests/test-pandoc.hs`.

32491

325−With a recent version of cabal, you can do `cabal repl` and get

326−a ghci REPL for working with pandoc. With [stack], use

327−`stack ghci`.

92+Benchmarks can be enabled by passing the `--enable-benchmarks` flag

93+to `cabal configure`, and run using `cabal bench`.

32894

329−We recommend using the following `.ghci` file (which can be

330−placed in the source directory):

331−

332− :set -fobject-code

333− :set -XTypeSynonymInstances

334− :set -XScopedTypeVariables

335− :set -XOverloadedStrings

336−

337−Profiling

338−---------

339−

340−To diagnose a performance issue with parsing, first try using

341−the `--trace` option. This will give you a record of when block

342−parsers succeed, so you can spot backtracking issues.

343−

344−To use the GHC profiler with cabal:

345−

346− cabal clean

347− cabal install --enable-library-profiling --enable-executable-profiling

348− pandoc +RTS -p -RTS [file]...

349− less pandoc.prof

350−

351−With stack:

352−

353− stack clean

354− stack install --profile

355− pandoc +RTS -p -RTS [file]...

356− less pandoc.prof

95+The code

96+--------

35797

358−Templates

359−---------

98+Pandoc has a publicly accessible git repository on

99+github: <http://github.com/jgm/pandoc>. To get a local copy of the source:

360100

361−The default templates live in `data/templates`, which is a git

362−subtree linked to <https://github.com/jgm/pandoc-templates.git>.

363−The purpose of maintaining a separate repository is to allow

364−people to maintain variant templates as a fork.

101+ git clone git://github.com/jgm/pandoc.git

365102

366−You can modify the templates and submit patches without worrying

367−much about this: when these patches are merged, we will

368−push them to the main templates repository by doing

103+Note: after cloning the repository (and in the future after pulling from it),

104+you should do

369105

370− git subtree push --prefix=data/templates templates master

106+ git submodule update --init

371107

372−where `templates` is a remote pointing to the templates

373−repository.

108+to pull in changes to the templates (`data/templates/`). You can automate this

109+by creating a file `.git/hooks/post-merge` with the contents:

374110

375−The code

376−--------

111+ #!/bin/sh

112+ git submodule update --init

377113

378−Pandoc has a publicly accessible git repository on

379−GitHub: <https://github.com/jgm/pandoc>. To get a local copy of the source:

114+and making it executable:

380115

381− git clone https://github.com/jgm/pandoc.git

116+ chmod +x .git/hooks/post-merge

382117

383118The source for the main pandoc program is `pandoc.hs`. The source for

384119the pandoc library is in `src/`, the source for the tests is in

385−`test/`, and the source for the benchmarks is in `benchmark/`.

120+`tests/`, and the source for the benchmarks is in `benchmark/`.

386121

387122The modules `Text.Pandoc.Definition`, `Text.Pandoc.Builder`, and

388−`Text.Pandoc.Generic` are in a separate library `pandoc-types`. The code can

389−be found in <https://github.com/jgm/pandoc-types>.

123+`Text.Pandoc.Generics` are in a separate library `pandoc-types`. The code can

124+be found in a <http://github.com/jgm/pandoc-types>.

390125

391126To build pandoc, you will need a working installation of the

392127[Haskell platform].

@@ -399,20 +134,20 @@ The library is structured as follows:

399134 - `Text.Pandoc.Definition` (in `pandoc-types`) defines the types

400135 used for representing a pandoc document.

401136 - `Text.Pandoc.Builder` (in `pandoc-types`) provides functions for

402− building pandoc documents programmatically.

137+ building pandoc documents programatically.

403138 - `Text.Pandoc.Generics` (in `pandoc-types`) provides functions allowing

404139 you to promote functions that operate on parts of pandoc documents

405140 to functions that operate on whole pandoc documents, walking the

406141 tree automatically.

407142 - `Text.Pandoc.Readers.*` are the readers, and `Text.Pandoc.Writers.*`

408143 are the writers.

409− - `Text.Pandoc.Citeproc.*` contain the code for citation handling,

410− including an interface to the [citeproc] library.

144+ - `Text.Pandoc.Biblio` is a utility module for formatting citations

145+ using citeproc-hs.

411146 - `Text.Pandoc.Data` is used to embed data files when the `embed_data_files`

412− cabal flag is used.

413− - `Text.Pandoc.Emoji` is a thin wrapper around [emojis].

147+ cabal flag is used. It is generated from `src/Text/Pandoc/Data.hsb` using

148+ the preprocessor [hsb2hs].

414149 - `Text.Pandoc.Highlighting` contains the interface to the

415− skylighting library, which is used for code syntax highlighting.

150+ highlighting-kate library, which is used for code syntax highlighting.

416151 - `Text.Pandoc.ImageSize` is a utility module containing functions for

417152 calculating image sizes from the contents of image files.

418153 - `Text.Pandoc.MIME` contains functions for associating MIME types

@@ -421,14 +156,15 @@ The library is structured as follows:

421156 - `Text.Pandoc.PDF` contains functions for producing a PDF from a

422157 LaTeX source.

423158 - `Text.Pandoc.Parsing` contains parsing functions used in multiple readers.

159+ - `Text.Pandoc.Pretty` is a pretty-printing library specialized to

424160 the needs of pandoc.

425161 - `Text.Pandoc.SelfContained` contains functions for making an HTML

426162 file "self-contained," by importing remotely linked images, CSS,

427− and JavaScript and turning them into `data:` URLs.

163+ and javascript and turning them into `data:` URLs.

428164 - `Text.Pandoc.Shared` is a grab-bag of shared utility functions.

429165 - `Text.Pandoc.Writers.Shared` contains utilities used in writers only.

430166 - `Text.Pandoc.Slides` contains functions for splitting a markdown document

431− into slides, using the conventions described in the MANUAL.

167+ into slides, using the conventions described in the README.

432168 - `Text.Pandoc.Templates` defines pandoc's templating system.

433169 - `Text.Pandoc.UTF8` contains functions for converting text to and from

434170 UTF8 bytestrings (strict and lazy).

@@ -437,39 +173,9 @@ The library is structured as follows:

437173 - `Text.Pandoc.UUID` contains functions for generating UUIDs.

438174 - `Text.Pandoc.XML` contains functions for formatting XML.

439175

440−Lua filters

441−-----------

442−

443−If you've written a useful pandoc [lua filter](lua-filters.html),

444−you may want to consider submitting a pull request to the

445−[lua-filters repository](https://github.com/pandoc/lua-filters).

446−

447−[open issues]: https://github.com/jgm/pandoc/issues

448−[closed issues]: https://github.com/jgm/pandoc/issues?q=is%3Aissue+is%3Aclosed

449−[latest released version]: https://github.com/jgm/pandoc/releases/latest

450−[Nightly builds]: https://github.com/jgm/pandoc/actions?query=workflow%3ANightly

451−[pandoc-discuss]: https://groups.google.com/group/pandoc-discuss

176+[pandoc-discuss]: http://groups.google.com/group/pandoc-discuss

452177[issue tracker]: https://github.com/jgm/pandoc/issues

453−[User's Guide]: https://pandoc.org/MANUAL.html

454−[FAQs]: https://pandoc.org/faqs.html

455−[EditorConfig]: https://editorconfig.org/

456−[Haskell platform]: https://www.haskell.org/platform/

457−[hlint]: https://hackage.haskell.org/package/hlint

458−[citeproc]: https://hackage.haskell.org/package/citeproc

459−[emojis]: https://hackage.haskell.org/package/emojis

460−[hsb2hs]: https://hackage.haskell.org/package/hsb2hs

461−[pre-commit hook]: https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks

462−[GitHub labels]: https://github.com/jgm/pandoc/labels

463−[good first issue]:https://github.com/jgm/pandoc/labels/good%20first%20issue

464−[enhancement]: https://github.com/jgm/pandoc/labels/enhancement

465−[bug]: https://github.com/jgm/pandoc/labels/bug

466−[complexity:low]: https://github.com/jgm/pandoc/labels/complexity:low

467−[complexity:high]: https://github.com/jgm/pandoc/labels/complexity:high

468−[docs]: https://github.com/jgm/pandoc/labels/docs

469−[format:markdown]: https://github.com/jgm/pandoc/labels/format:markdown

470−[new:reader]: https://github.com/jgm/pandoc/labels/new:reader

471−[new:writer]: https://github.com/jgm/pandoc/labels/new:writer

472−[status:in-progress]: https://github.com/jgm/pandoc/labels/status:in-progress

473−[status:more-discussion-needed]: https://github.com/jgm/pandoc/labels/status:more-discussion-needed

474−[status:more-info-needed]: https://github.com/jgm/pandoc/labels/status:more-info-needed

475−[stack]: https://github.com/commercialhaskell/stack

178+[User's Guide]: http://johnmacfarlane.net/pandoc/README.html

179+[FAQs]: http://johnmacfarlane.net/pandoc/faqs.html

180+[Haskell platform]: http://www.haskell.org/platform/

181+[hsb2hs]: http://hackage.haskell.org/package/hsb2hs

COPYINGnew file+346

@@ -0,0 +1,346 @@

1+GNU GENERAL PUBLIC LICENSE

2+==========================

3+

4+Version 2, June 1991

5+

6+Copyright (C) 1989, 1991 Free Software Foundation, Inc.

7+51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA

8+

9+Everyone is permitted to copy and distribute verbatim copies

10+of this license document, but changing it is not allowed.

11+

12+Preamble

13+--------

14+

15+The licenses for most software are designed to take away your

16+freedom to share and change it. By contrast, the GNU General Public

17+License is intended to guarantee your freedom to share and change free

18+software--to make sure the software is free for all its users. This

19+General Public License applies to most of the Free Software

20+Foundation's software and to any other program whose authors commit to

21+using it. (Some other Free Software Foundation software is covered by

22+the GNU Library General Public License instead.) You can apply it to

23+your programs, too.

24+

25+When we speak of free software, we are referring to freedom, not

26+price. Our General Public Licenses are designed to make sure that you

27+have the freedom to distribute copies of free software (and charge for

28+this service if you wish), that you receive source code or can get it

29+if you want it, that you can change the software or use pieces of it

30+in new free programs; and that you know you can do these things.

31+

32+To protect your rights, we need to make restrictions that forbid

33+anyone to deny you these rights or to ask you to surrender the rights.

34+These restrictions translate to certain responsibilities for you if you

35+distribute copies of the software, or if you modify it.

36+

37+For example, if you distribute copies of such a program, whether

38+gratis or for a fee, you must give the recipients all the rights that

39+you have. You must make sure that they, too, receive or can get the

40+source code. And you must show them these terms so they know their

41+rights.

42+

43+We protect your rights with two steps: (1) copyright the software, and

44+(2) offer you this license which gives you legal permission to copy,

45+distribute and/or modify the software.

46+

47+Also, for each author's protection and ours, we want to make certain

48+that everyone understands that there is no warranty for this free

49+software. If the software is modified by someone else and passed on, we

50+want its recipients to know that what they have is not the original, so

51+that any problems introduced by others will not reflect on the original

52+authors' reputations.

53+

54+Finally, any free program is threatened constantly by software

55+patents. We wish to avoid the danger that redistributors of a free

56+program will individually obtain patent licenses, in effect making the

57+program proprietary. To prevent this, we have made it clear that any

58+patent must be licensed for everyone's free use or not licensed at all.

59+

60+The precise terms and conditions for copying, distribution and

61+modification follow.

62+

63+GNU GENERAL PUBLIC LICENSE

64+--------------------------

65+

66+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

67+

68+0. This License applies to any program or other work which contains

69+ a notice placed by the copyright holder saying it may be distributed

70+ under the terms of this General Public License. The "Program", below,

71+ refers to any such program or work, and a "work based on the Program"

72+ means either the Program or any derivative work under copyright law:

73+ that is to say, a work containing the Program or a portion of it,

74+ either verbatim or with modifications and/or translated into another

75+ language. (Hereinafter, translation is included without limitation in

76+ the term "modification".) Each licensee is addressed as "you".

77+

78+ Activities other than copying, distribution and modification are not

79+ covered by this License; they are outside its scope. The act of

80+ running the Program is not restricted, and the output from the Program

81+ is covered only if its contents constitute a work based on the

82+ Program (independent of having been made by running the Program).

83+ Whether that is true depends on what the Program does.

84+

85+1. You may copy and distribute verbatim copies of the Program's

86+ source code as you receive it, in any medium, provided that you

87+ conspicuously and appropriately publish on each copy an appropriate

88+ copyright notice and disclaimer of warranty; keep intact all the

89+ notices that refer to this License and to the absence of any warranty;

90+ and give any other recipients of the Program a copy of this License

91+ along with the Program.

92+

93+ You may charge a fee for the physical act of transferring a copy, and

94+ you may at your option offer warranty protection in exchange for a fee.

95+

96+2. You may modify your copy or copies of the Program or any portion

97+ of it, thus forming a work based on the Program, and copy and

98+ distribute such modifications or work under the terms of Section 1

99+ above, provided that you also meet all of these conditions:

100+

101+ a) You must cause the modified files to carry prominent notices

102+ stating that you changed the files and the date of any change.

103+

104+ b) You must cause any work that you distribute or publish, that in

105+ whole or in part contains or is derived from the Program or any

106+ part thereof, to be licensed as a whole at no charge to all third

107+ parties under the terms of this License.

108+

109+ c) If the modified program normally reads commands interactively

110+ when run, you must cause it, when started running for such

111+ interactive use in the most ordinary way, to print or display an

112+ announcement including an appropriate copyright notice and a

113+ notice that there is no warranty (or else, saying that you provide

114+ a warranty) and that users may redistribute the program under

115+ these conditions, and telling the user how to view a copy of this

116+ License. (Exception: if the Program itself is interactive but

117+ does not normally print such an announcement, your work based on

118+ the Program is not required to print an announcement.)

119+

120+ These requirements apply to the modified work as a whole. If

121+ identifiable sections of that work are not derived from the Program,

122+ and can be reasonably considered independent and separate works in

123+ themselves, then this License, and its terms, do not apply to those

124+ sections when you distribute them as separate works. But when you

125+ distribute the same sections as part of a whole which is a work based

126+ on the Program, the distribution of the whole must be on the terms of

127+ this License, whose permissions for other licensees extend to the

128+ entire whole, and thus to each and every part regardless of who wrote it.

129+

130+ Thus, it is not the intent of this section to claim rights or contest

131+ your rights to work written entirely by you; rather, the intent is to

132+ exercise the right to control the distribution of derivative or

133+ collective works based on the Program.

134+

135+ In addition, mere aggregation of another work not based on the Program

136+ with the Program (or with a work based on the Program) on a volume of

137+ a storage or distribution medium does not bring the other work under

138+ the scope of this License.

139+

140+3. You may copy and distribute the Program (or a work based on it,

141+ under Section 2) in object code or executable form under the terms of

142+ Sections 1 and 2 above provided that you also do one of the following:

143+

144+ a) Accompany it with the complete corresponding machine-readable

145+ source code, which must be distributed under the terms of Sections

146+ 1 and 2 above on a medium customarily used for software interchange; or,

147+

148+ b) Accompany it with a written offer, valid for at least three

149+ years, to give any third party, for a charge no more than your

150+ cost of physically performing source distribution, a complete

151+ machine-readable copy of the corresponding source code, to be

152+ distributed under the terms of Sections 1 and 2 above on a medium

153+ customarily used for software interchange; or,

154+

155+ c) Accompany it with the information you received as to the offer

156+ to distribute corresponding source code. (This alternative is

157+ allowed only for noncommercial distribution and only if you

158+ received the program in object code or executable form with such

159+ an offer, in accord with Subsection b above.)

160+

161+ The source code for a work means the preferred form of the work for

162+ making modifications to it. For an executable work, complete source

163+ code means all the source code for all modules it contains, plus any

164+ associated interface definition files, plus the scripts used to

165+ control compilation and installation of the executable. However, as a

166+ special exception, the source code distributed need not include

167+ anything that is normally distributed (in either source or binary

168+ form) with the major components (compiler, kernel, and so on) of the

169+ operating system on which the executable runs, unless that component

170+ itself accompanies the executable.

171+

172+ If distribution of executable or object code is made by offering

173+ access to copy from a designated place, then offering equivalent

174+ access to copy the source code from the same place counts as

175+ distribution of the source code, even though third parties are not

176+ compelled to copy the source along with the object code.

177+

178+4. You may not copy, modify, sublicense, or distribute the Program

179+ except as expressly provided under this License. Any attempt

180+ otherwise to copy, modify, sublicense or distribute the Program is

181+ void, and will automatically terminate your rights under this License.

182+ However, parties who have received copies, or rights, from you under

183+ this License will not have their licenses terminated so long as such

184+ parties remain in full compliance.

185+

186+5. You are not required to accept this License, since you have not

187+ signed it. However, nothing else grants you permission to modify or

188+ distribute the Program or its derivative works. These actions are

189+ prohibited by law if you do not accept this License. Therefore, by

190+ modifying or distributing the Program (or any work based on the

191+ Program), you indicate your acceptance of this License to do so, and

192+ all its terms and conditions for copying, distributing or modifying

193+ the Program or works based on it.

194+

195+6. Each time you redistribute the Program (or any work based on the

196+ Program), the recipient automatically receives a license from the

197+ original licensor to copy, distribute or modify the Program subject to

198+ these terms and conditions. You may not impose any further

199+ restrictions on the recipients' exercise of the rights granted herein.

200+ You are not responsible for enforcing compliance by third parties to

201+ this License.

202+

203+7. If, as a consequence of a court judgment or allegation of patent

204+ infringement or for any other reason (not limited to patent issues),

205+ conditions are imposed on you (whether by court order, agreement or

206+ otherwise) that contradict the conditions of this License, they do not

207+ excuse you from the conditions of this License. If you cannot

208+ distribute so as to satisfy simultaneously your obligations under this

209+ License and any other pertinent obligations, then as a consequence you

210+ may not distribute the Program at all. For example, if a patent

211+ license would not permit royalty-free redistribution of the Program by

212+ all those who receive copies directly or indirectly through you, then

213+ the only way you could satisfy both it and this License would be to

214+ refrain entirely from distribution of the Program.

215+

216+ If any portion of this section is held invalid or unenforceable under

217+ any particular circumstance, the balance of the section is intended to

218+ apply and the section as a whole is intended to apply in other

219+ circumstances.

220+

221+ It is not the purpose of this section to induce you to infringe any

222+ patents or other property right claims or to contest validity of any

223+ such claims; this section has the sole purpose of protecting the

224+ integrity of the free software distribution system, which is

225+ implemented by public license practices. Many people have made

226+ generous contributions to the wide range of software distributed

227+ through that system in reliance on consistent application of that

228+ system; it is up to the author/donor to decide if he or she is willing

229+ to distribute software through any other system and a licensee cannot

230+ impose that choice.

231+

232+ This section is intended to make thoroughly clear what is believed to

233+ be a consequence of the rest of this License.

234+

235+8. If the distribution and/or use of the Program is restricted in

236+ certain countries either by patents or by copyrighted interfaces, the

237+ original copyright holder who places the Program under this License

238+ may add an explicit geographical distribution limitation excluding

239+ those countries, so that distribution is permitted only in or among

240+ countries not thus excluded. In such case, this License incorporates

241+ the limitation as if written in the body of this License.

242+

243+9. The Free Software Foundation may publish revised and/or new versions

244+ of the General Public License from time to time. Such new versions will

245+ be similar in spirit to the present version, but may differ in detail to

246+ address new problems or concerns.

247+

248+ Each version is given a distinguishing version number. If the Program

249+ specifies a version number of this License which applies to it and "any

250+ later version", you have the option of following the terms and conditions

251+ either of that version or of any later version published by the Free

252+ Software Foundation. If the Program does not specify a version number of

253+ this License, you may choose any version ever published by the Free Software

254+ Foundation.

255+

256+10. If you wish to incorporate parts of the Program into other free

257+ programs whose distribution conditions are different, write to the author

258+ to ask for permission. For software which is copyrighted by the Free

259+ Software Foundation, write to the Free Software Foundation; we sometimes

260+ make exceptions for this. Our decision will be guided by the two goals

261+ of preserving the free status of all derivatives of our free software and

262+ of promoting the sharing and reuse of software generally.

263+

264+NO WARRANTY

265+

266+11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY

267+ FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN

268+ OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES

269+ PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED

270+ OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

271+ MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS

272+ TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE

273+ PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,

274+ REPAIR OR CORRECTION.

275+

276+12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING

277+ WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR

278+ REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,

279+ INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING

280+ OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED

281+ TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY

282+ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER

283+ PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE

284+ POSSIBILITY OF SUCH DAMAGES.

285+

286+END OF TERMS AND CONDITIONS

287+

288+How to Apply These Terms to Your New Programs

289+---------------------------------------------

290+

291+If you develop a new program, and you want it to be of the greatest

292+possible use to the public, the best way to achieve this is to make it

293+free software which everyone can redistribute and change under these terms.

294+

295+To do so, attach the following notices to the program. It is safest

296+to attach them to the start of each source file to most effectively

297+convey the exclusion of warranty; and each file should have at least

298+the "copyright" line and a pointer to where the full notice is found.

299+

300+ <one line to give the program's name and a brief idea of what it does.>

301+ Copyright (C) <year> <name of author>

302+

303+ This program is free software; you can redistribute it and/or modify

304+ it under the terms of the GNU General Public License as published by

305+ the Free Software Foundation; either version 2 of the License, or

306+ (at your option) any later version.

307+

308+ This program is distributed in the hope that it will be useful,

309+ but WITHOUT ANY WARRANTY; without even the implied warranty of

310+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

311+ GNU General Public License for more details.

312+

313+ You should have received a copy of the GNU General Public License

314+ along with this program; if not, write to the Free Software

315+ Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA

316+

317+Also add information on how to contact you by electronic and paper mail.

318+

319+If the program is interactive, make it output a short notice like this

320+when it starts in an interactive mode:

321+

322+ Gnomovision version 69, Copyright (C) year name of author

323+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.

324+ This is free software, and you are welcome to redistribute it

325+ under certain conditions; type `show c' for details.

326+

327+The hypothetical commands `show w' and `show c' should show the appropriate

328+parts of the General Public License. Of course, the commands you use may

329+be called something other than `show w' and `show c'; they could even be

330+mouse-clicks or menu items--whatever suits your program.

331+

332+You should also get your employer (if you work as a programmer) or your

333+school, if any, to sign a "copyright disclaimer" for the program, if

334+necessary. Here is a sample; alter the names:

335+

336+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program

337+ `Gnomovision' (which makes passes at compilers) written by James Hacker.

338+

339+ <signature of Ty Coon>, 1 April 1989

340+ Ty Coon, President of Vice

341+

342+This General Public License does not permit incorporating your program into

343+proprietary programs. If your program is a subroutine library, you may

344+consider it more useful to permit linking proprietary applications with the

345+library. If this is what you want to do, use the GNU Library General

346+Public License instead of this License.

COPYING.mddeleted−361

@@ -1,361 +0,0 @@

1−### GNU GENERAL PUBLIC LICENSE

2−

3−Version 2, June 1991

4−

5− Copyright (C) 1989, 1991 Free Software Foundation, Inc.

6− 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA

7−

8− Everyone is permitted to copy and distribute verbatim copies

9− of this license document, but changing it is not allowed.

10−

11−### Preamble

12−

13−The licenses for most software are designed to take away your freedom

14−to share and change it. By contrast, the GNU General Public License is

15−intended to guarantee your freedom to share and change free

16−software--to make sure the software is free for all its users. This

17−General Public License applies to most of the Free Software

18−Foundation's software and to any other program whose authors commit to

19−using it. (Some other Free Software Foundation software is covered by

20−the GNU Lesser General Public License instead.) You can apply it to

21−your programs, too.

22−

23−When we speak of free software, we are referring to freedom, not

24−price. Our General Public Licenses are designed to make sure that you

25−have the freedom to distribute copies of free software (and charge for

26−this service if you wish), that you receive source code or can get it

27−if you want it, that you can change the software or use pieces of it

28−in new free programs; and that you know you can do these things.

29−

30−To protect your rights, we need to make restrictions that forbid

31−anyone to deny you these rights or to ask you to surrender the rights.

32−These restrictions translate to certain responsibilities for you if

33−you distribute copies of the software, or if you modify it.

34−

35−For example, if you distribute copies of such a program, whether

36−gratis or for a fee, you must give the recipients all the rights that

37−you have. You must make sure that they, too, receive or can get the

38−source code. And you must show them these terms so they know their

39−rights.

40−

41−We protect your rights with two steps: (1) copyright the software, and

42−(2) offer you this license which gives you legal permission to copy,

43−distribute and/or modify the software.

44−

45−Also, for each author's protection and ours, we want to make certain

46−that everyone understands that there is no warranty for this free

47−software. If the software is modified by someone else and passed on,

48−we want its recipients to know that what they have is not the

49−original, so that any problems introduced by others will not reflect

50−on the original authors' reputations.

51−

52−Finally, any free program is threatened constantly by software

53−patents. We wish to avoid the danger that redistributors of a free

54−program will individually obtain patent licenses, in effect making the

55−program proprietary. To prevent this, we have made it clear that any

56−patent must be licensed for everyone's free use or not licensed at

57−all.

58−

59−The precise terms and conditions for copying, distribution and

60−modification follow.

61−

62−### TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

63−

64−**0.** This License applies to any program or other work which

65−contains a notice placed by the copyright holder saying it may be

66−distributed under the terms of this General Public License. The

67−"Program", below, refers to any such program or work, and a "work

68−based on the Program" means either the Program or any derivative work

69−under copyright law: that is to say, a work containing the Program or

70−a portion of it, either verbatim or with modifications and/or

71−translated into another language. (Hereinafter, translation is

72−included without limitation in the term "modification".) Each licensee

73−is addressed as "you".

74−

75−Activities other than copying, distribution and modification are not

76−covered by this License; they are outside its scope. The act of

77−running the Program is not restricted, and the output from the Program

78−is covered only if its contents constitute a work based on the Program

79−(independent of having been made by running the Program). Whether that

80−is true depends on what the Program does.

81−

82−**1.** You may copy and distribute verbatim copies of the Program's

83−source code as you receive it, in any medium, provided that you

84−conspicuously and appropriately publish on each copy an appropriate

85−copyright notice and disclaimer of warranty; keep intact all the

86−notices that refer to this License and to the absence of any warranty;

87−and give any other recipients of the Program a copy of this License

88−along with the Program.

89−

90−You may charge a fee for the physical act of transferring a copy, and

91−you may at your option offer warranty protection in exchange for a

92−fee.

93−

94−**2.** You may modify your copy or copies of the Program or any

95−portion of it, thus forming a work based on the Program, and copy and

96−distribute such modifications or work under the terms of Section 1

97−above, provided that you also meet all of these conditions:

98−

99−

100−**a)** You must cause the modified files to carry prominent notices

101−stating that you changed the files and the date of any change.

102−

103−

104−**b)** You must cause any work that you distribute or publish, that in

105−whole or in part contains or is derived from the Program or any part

106−thereof, to be licensed as a whole at no charge to all third parties

107−under the terms of this License.

108−

109−

110−**c)** If the modified program normally reads commands interactively

111−when run, you must cause it, when started running for such interactive

112−use in the most ordinary way, to print or display an announcement

113−including an appropriate copyright notice and a notice that there is

114−no warranty (or else, saying that you provide a warranty) and that

115−users may redistribute the program under these conditions, and telling

116−the user how to view a copy of this License. (Exception: if the

117−Program itself is interactive but does not normally print such an

118−announcement, your work based on the Program is not required to print

119−an announcement.)

120−

121−These requirements apply to the modified work as a whole. If

122−identifiable sections of that work are not derived from the Program,

123−and can be reasonably considered independent and separate works in

124−themselves, then this License, and its terms, do not apply to those

125−sections when you distribute them as separate works. But when you

126−distribute the same sections as part of a whole which is a work based

127−on the Program, the distribution of the whole must be on the terms of

128−this License, whose permissions for other licensees extend to the

129−entire whole, and thus to each and every part regardless of who wrote

130−it.

131−

132−Thus, it is not the intent of this section to claim rights or contest

133−your rights to work written entirely by you; rather, the intent is to

134−exercise the right to control the distribution of derivative or

135−collective works based on the Program.

136−

137−In addition, mere aggregation of another work not based on the Program

138−with the Program (or with a work based on the Program) on a volume of

139−a storage or distribution medium does not bring the other work under

140−the scope of this License.

141−

142−**3.** You may copy and distribute the Program (or a work based on it,

143−under Section 2) in object code or executable form under the terms of

144−Sections 1 and 2 above provided that you also do one of the following:

145−

146−

147−**a)** Accompany it with the complete corresponding machine-readable

148−source code, which must be distributed under the terms of Sections 1

149−and 2 above on a medium customarily used for software interchange; or,

150−

151−

152−**b)** Accompany it with a written offer, valid for at least three

153−years, to give any third party, for a charge no more than your cost of

154−physically performing source distribution, a complete machine-readable

155−copy of the corresponding source code, to be distributed under the

156−terms of Sections 1 and 2 above on a medium customarily used for

157−software interchange; or,

158−

159−

160−**c)** Accompany it with the information you received as to the offer

161−to distribute corresponding source code. (This alternative is allowed

162−only for noncommercial distribution and only if you received the

163−program in object code or executable form with such an offer, in

164−accord with Subsection b above.)

165−

166−The source code for a work means the preferred form of the work for

167−making modifications to it. For an executable work, complete source

168−code means all the source code for all modules it contains, plus any

169−associated interface definition files, plus the scripts used to

170−control compilation and installation of the executable. However, as a

171−special exception, the source code distributed need not include

172−anything that is normally distributed (in either source or binary

173−form) with the major components (compiler, kernel, and so on) of the

174−operating system on which the executable runs, unless that component

175−itself accompanies the executable.

176−

177−If distribution of executable or object code is made by offering

178−access to copy from a designated place, then offering equivalent

179−access to copy the source code from the same place counts as

180−distribution of the source code, even though third parties are not

181−compelled to copy the source along with the object code.

182−

183−**4.** You may not copy, modify, sublicense, or distribute the Program

184−except as expressly provided under this License. Any attempt otherwise

185−to copy, modify, sublicense or distribute the Program is void, and

186−will automatically terminate your rights under this License. However,

187−parties who have received copies, or rights, from you under this

188−License will not have their licenses terminated so long as such

189−parties remain in full compliance.

190−

191−**5.** You are not required to accept this License, since you have not

192−signed it. However, nothing else grants you permission to modify or

193−distribute the Program or its derivative works. These actions are

194−prohibited by law if you do not accept this License. Therefore, by

195−modifying or distributing the Program (or any work based on the

196−Program), you indicate your acceptance of this License to do so, and

197−all its terms and conditions for copying, distributing or modifying

198−the Program or works based on it.

199−

200−**6.** Each time you redistribute the Program (or any work based on

201−the Program), the recipient automatically receives a license from the

202−original licensor to copy, distribute or modify the Program subject to

203−these terms and conditions. You may not impose any further

204−restrictions on the recipients' exercise of the rights granted herein.

205−You are not responsible for enforcing compliance by third parties to

206−this License.

207−

208−**7.** If, as a consequence of a court judgment or allegation of

209−patent infringement or for any other reason (not limited to patent

210−issues), conditions are imposed on you (whether by court order,

211−agreement or otherwise) that contradict the conditions of this

212−License, they do not excuse you from the conditions of this License.

213−If you cannot distribute so as to satisfy simultaneously your

214−obligations under this License and any other pertinent obligations,

215−then as a consequence you may not distribute the Program at all. For

216−example, if a patent license would not permit royalty-free

217−redistribution of the Program by all those who receive copies directly

218−or indirectly through you, then the only way you could satisfy both it

219−and this License would be to refrain entirely from distribution of the

220−Program.

221−

222−If any portion of this section is held invalid or unenforceable under

223−any particular circumstance, the balance of the section is intended to

224−apply and the section as a whole is intended to apply in other

225−circumstances.

226−

227−It is not the purpose of this section to induce you to infringe any

228−patents or other property right claims or to contest validity of any

229−such claims; this section has the sole purpose of protecting the

230−integrity of the free software distribution system, which is

231−implemented by public license practices. Many people have made

232−generous contributions to the wide range of software distributed

233−through that system in reliance on consistent application of that

234−system; it is up to the author/donor to decide if he or she is willing

235−to distribute software through any other system and a licensee cannot

236−impose that choice.

237−

238−This section is intended to make thoroughly clear what is believed to

239−be a consequence of the rest of this License.

240−

241−**8.** If the distribution and/or use of the Program is restricted in

242−certain countries either by patents or by copyrighted interfaces, the

243−original copyright holder who places the Program under this License

244−may add an explicit geographical distribution limitation excluding

245−those countries, so that distribution is permitted only in or among

246−countries not thus excluded. In such case, this License incorporates

247−the limitation as if written in the body of this License.

248−

249−**9.** The Free Software Foundation may publish revised and/or new

250−versions of the General Public License from time to time. Such new

251−versions will be similar in spirit to the present version, but may

252−differ in detail to address new problems or concerns.

253−

254−Each version is given a distinguishing version number. If the Program

255−specifies a version number of this License which applies to it and

256−"any later version", you have the option of following the terms and

257−conditions either of that version or of any later version published by

258−the Free Software Foundation. If the Program does not specify a

259−version number of this License, you may choose any version ever

260−published by the Free Software Foundation.

261−

262−**10.** If you wish to incorporate parts of the Program into other

263−free programs whose distribution conditions are different, write to

264−the author to ask for permission. For software which is copyrighted by

265−the Free Software Foundation, write to the Free Software Foundation;

266−we sometimes make exceptions for this. Our decision will be guided by

267−the two goals of preserving the free status of all derivatives of our

268−free software and of promoting the sharing and reuse of software

269−generally.

270−

271−**NO WARRANTY**

272−

273−**11.** BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO

274−WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.

275−EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR

276−OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY

277−KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE

278−IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

279−PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE

280−PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME

281−THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

282−

283−**12.** IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN

284−WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY

285−AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU

286−FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR

287−CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE

288−PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING

289−RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A

290−FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF

291−SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH

292−DAMAGES.

293−

294−### END OF TERMS AND CONDITIONS

295−

296−### How to Apply These Terms to Your New Programs

297−

298−If you develop a new program, and you want it to be of the greatest

299−possible use to the public, the best way to achieve this is to make it

300−free software which everyone can redistribute and change under these

301−terms.

302−

303−To do so, attach the following notices to the program. It is safest to

304−attach them to the start of each source file to most effectively

305−convey the exclusion of warranty; and each file should have at least

306−the "copyright" line and a pointer to where the full notice is found.

307−

308− one line to give the program's name and an idea of what it does.

309− Copyright (C) yyyy name of author

310−

311− This program is free software; you can redistribute it and/or

312− modify it under the terms of the GNU General Public License

313− as published by the Free Software Foundation; either version 2

314− of the License, or (at your option) any later version.

315−

316− This program is distributed in the hope that it will be useful,

317− but WITHOUT ANY WARRANTY; without even the implied warranty of

318− MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

319− GNU General Public License for more details.

320−

321− You should have received a copy of the GNU General Public License

322− along with this program; if not, write to the Free Software

323− Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.

324−

325−Also add information on how to contact you by electronic and paper

326−mail.

327−

328−If the program is interactive, make it output a short notice like this

329−when it starts in an interactive mode:

330−

331− Gnomovision version 69, Copyright (C) year name of author

332− Gnomovision comes with ABSOLUTELY NO WARRANTY; for details

333− type `show w'. This is free software, and you are welcome

334− to redistribute it under certain conditions; type `show c'

335− for details.

336−

337−The hypothetical commands \`show w' and \`show c' should show the

338−appropriate parts of the General Public License. Of course, the

339−commands you use may be called something other than \`show w' and

340−\`show c'; they could even be mouse-clicks or menu items--whatever

341−suits your program.

342−

343−You should also get your employer (if you work as a programmer) or

344−your school, if any, to sign a "copyright disclaimer" for the program,

345−if necessary. Here is a sample; alter the names:

346−

347− Yoyodyne, Inc., hereby disclaims all copyright

348− interest in the program `Gnomovision'

349− (which makes passes at compilers) written

350− by James Hacker.

351−

352− signature of Ty Coon, 1 April 1989

353− Ty Coon, President of Vice

354−

355−This General Public License does not permit incorporating your program

356−into proprietary programs. If your program is a subroutine library,

357−you may consider it more useful to permit linking proprietary

358−applications with the library. If this is what you want to do, use the

359−[GNU Lesser General Public

360−License](https://www.gnu.org/licenses/lgpl.html) instead of this

361−License.

COPYRIGHT+51−140

@@ -1,8 +1,7 @@

11Pandoc

2−Copyright (C) 2006-2021 John MacFarlane <jgm at berkeley dot edu>

2+Copyright (C) 2006-2013 John MacFarlane <jgm at berkeley dot edu>

33

4−With the exceptions noted below, this code is released under the [GPL],

5−version 2 or later:

4+This code is released under the [GPL], version 2 or later:

65

76 This program is free software; you can redistribute it and/or modify

87 it under the terms of the GNU General Public License as published by

@@ -18,188 +17,100 @@ version 2 or later:

1817 along with this program; if not, write to the Free Software

1918 Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA

2019

21−The GNU General Public License is available in the file COPYING.md in

20+The GNU General Public License is available in the file COPYING in

2221the source distribution. On Debian systems, the complete text of the

2322GPL can be found in `/usr/share/common-licenses/GPL`.

2423

25−[GPL]: https://www.gnu.org/copyleft/gpl.html

24+[GPL]: http://www.gnu.org/copyleft/gpl.html

2625

2726Pandoc's complete source code is available from the [Pandoc home page].

2827

29−[Pandoc home page]: https://pandoc.org

28+[Pandoc home page]: http://johnmacfarlane.net/pandoc/

3029

31−Pandoc includes some code with different copyrights, or subject to different

32−licenses. The copyright and license statements for these sources are included

33−below. All are GPL-compatible licenses.

34−

35−----------------------------------------------------------------------

36−The modules in the `pandoc-types` repository (Text.Pandoc.Definition,

37−Text.Pandoc.Builder, Text.Pandoc.Generics, Text.Pandoc.JSON,

38−Text.Pandoc.Walk) are licensed under the BSD 3-clause license:

39−

40−Copyright (c) 2006-2021, John MacFarlane

41−

42−All rights reserved.

43−

44−Redistribution and use in source and binary forms, with or without

45−modification, are permitted provided that the following conditions are met:

46−

47− * Redistributions of source code must retain the above copyright

48− notice, this list of conditions and the following disclaimer.

49−

50− * Redistributions in binary form must reproduce the above

51− copyright notice, this list of conditions and the following

52− disclaimer in the documentation and/or other materials provided

53− with the distribution.

54−

55− * Neither the name of John MacFarlane nor the names of other

56− contributors may be used to endorse or promote products derived

57− from this software without specific prior written permission.

58−

59−THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS

60−"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT

61−LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR

62−A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT

63−OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

64−SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

65−LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,

66−DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY

67−THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

68−(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE

69−OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

70−

71−----------------------------------------------------------------------

72−Pandoc's templates (in `data/templates`) are dual-licensed as either

73−GPL (v2 or higher, same as pandoc) or (at your option) the BSD

74−3-clause license.

75−

76−Copyright (c) 2014--2021, John MacFarlane

77−

78−----------------------------------------------------------------------

79−src/Text/Pandoc/Writers/Muse.hs

80−Copyright (C) 2017-2020 Alexander Krotov

81−

82−Released under the GNU General Public License version 2 or later.

30+Pandoc includes some code from other authors. The copyright and license

31+statements for these sources are included below. All are GPL-compatible

32+licenses.

8333

8434----------------------------------------------------------------------

8535src/Text/Pandoc/Writers/Texinfo.hs

86−Copyright (C) 2008-2021 John MacFarlane and Peter Wang

36+Copyright (C) 2008-2010 John MacFarlane and Peter Wang

8737

88−Released under the GNU General Public License version 2 or later.

38+Released under the GPL.

8939

9040----------------------------------------------------------------------

9141src/Text/Pandoc/Writers/OpenDocument.hs

92−Copyright (C) 2008-2021 Andrea Rossato and John MacFarlane

42+Copyright (C) 2008-2010 Andrea Rossato and John MacFarlane

9343

94−Released under the GNU General Public License version 2 or later.

44+Released under the GPL.

9545

9646----------------------------------------------------------------------

9747src/Text/Pandoc/Writers/Org.hs

98−Copyright (C) 2010-2021 Puneeth Chaganti, John MacFarlane, and

99− Albert Krewinkel

100−

101−Released under the GNU General Public License version 2 or later.

102−

103−----------------------------------------------------------------------

104−src/Text/Pandoc/Writers/ZimWiki.hs

105−Copyright (C) 2017 Alex Ivkin

48+Copyright (C) 2010 Puneeth Chaganti

10649

107−Released under the GNU General Public License version 2 or later.

108−

109−----------------------------------------------------------------------

110−src/Text/Pandoc/Readers/Docx.hs

111−src/Text/Pandoc/Readers/Docx/*

112−Copyright (C) 2014-2020 Jesse Rosenthal

113−

114−Released under the GNU General Public License version 2 or later.

50+Released under the GPL.

11551

11652----------------------------------------------------------------------

11753src/Text/Pandoc/Readers/Textile.hs

118−Copyright (C) 2010-2021 Paul Rivier and John MacFarlane

54+Copyright (C) 2010 Paul Rivier

11955

120−Released under the GNU General Public License version 2 or later.

56+Released under the GPL.

12157

12258----------------------------------------------------------------------

123−src/Text/Pandoc/Readers/TikiWiki.hs

124−Copyright (C) 2017 Robin Lee Powell

59+src/Text/Pandoc/Biblio.hs

60+Copyright (C) 2008-2010 Andrea Rossato

12561

126−Released under the GNU General Public License version 2 or later.

127−

128−----------------------------------------------------------------------

129−src/Text/Pandoc/Readers/JATS.hs

130−Copyright (C) 2017-2018 Hamish Mackenzie

131−

132−Released under the GNU General Public License version 2 or later.

62+Released under the GPL.

13363

13464----------------------------------------------------------------------

135−src/Text/Pandoc/Readers/EPUB.hs

136−Copyright (C) 2014-2021 Matthew Pickering and John MacFarlane

65+data/LaTeXMathML.js

66+Adapted by Jeff Knisely and Douglas Woodall from

67+ASCIIMathML.js v. 1.4.7

68+Copyright (C) 2005 Peter Jipsen

13769

138−Released under the GNU General Public License version 2 or later.

70+Released under the GPL.

13971

14072----------------------------------------------------------------------

141−src/Text/Pandoc/Readers/Org.hs

142−src/Text/Pandoc/Readers/Org/*

143−test/Tests/Readers/Org/*

144−Copyright (C) 2014-2021 Albert Krewinkel

73+data/MathMLInHTML.js

74+Copyright (C) 2004 Peter Jipsen http://www.chapman.edu/~jipsen

14575

14676Released under the GNU General Public License version 2 or later.

77+See the GNU General Public License

78+(at http://www.gnu.org/copyleft/gpl.html) for more details.

14779

14880----------------------------------------------------------------------

149−src/Text/Pandoc/Lua.hs

150−src/Text/Pandoc/Lua/*

151−test/lua/*

152−Copyright (C) 2017--2021 Albert Krewinkel and John MacFarlane

81+s5/default

82+S5 slides.js and css files

83+by Eric A. Meyer

84+<http://meyerweb.com/eric/tools/s5

15385

154−Released under the GNU General Public License version 2 or later.

86+Released under an explicit Public Domain License

15587

15688----------------------------------------------------------------------

157−src/Text/Pandoc/Readers/Jira.hs

158−src/Text/Pandoc/Writers/Jira.hs

159−test/Tests/Readers/Jira.hs

160−Copyright (C) 2019--2021 Albert Krewinkel

89+slidy/default

90+Slidy javascript and CSS

91+by Dave Raggett

92+http://www.w3.org/Talks/Tools/Slidy2

16193

162−Released under the GNU General Public License version 2 or later.

94+Released under W3C document and software licenses

16395

16496----------------------------------------------------------------------

165−src/Text/Pandoc/Readers/FB2.hs

166−Copyright (C) 2018--2019 Alexander Krotov

97+slideous/default

98+Slideous javascript and CSS

99+by Stefan Gössner

100+http://goessner.net/

167101

168−Released under the GNU General Public License version 2 or later.

102+Released under Creative Commons GNU LGPL License

169103

170−----------------------------------------------------------------------

171−data/pandoc.lua

172−Copyright (C) 2017-2021 Albert Krewinkel

104+------------------------------------------------------------------------

105+windows/modpath.iss

106+Copyright (c) 2007 Jared Breland

107+http://legroom.net/software

173108

174−Released under the GNU General Public License version 2 or later.

109+Released under the GPL.

175110

176−----------------------------------------------------------------------

177−The dzslides template contains JavaScript and CSS from Paul Rouget's

111+------------------------------------------------------------------------

112+The dzslides template contains javascript and CSS from Paul Rouget's

178113dzslides template.

179−https://github.com/paulrouget/dzslides

114+http://github.com/apulrouget/dzslides

180115

181116Released under the Do What the Fuck You Want To Public License.

182−

183−------------------------------------------------------------------------

184−Pandoc embeds a Lua interpreter (via hslua).

185−

186−Copyright © 1994–2020 Lua.org, PUC-Rio.

187−

188−Permission is hereby granted, free of charge, to any person obtaining

189−a copy of this software and associated documentation files (the

190−"Software"), to deal in the Software without restriction, including

191−without limitation the rights to use, copy, modify, merge, publish,

192−distribute, sublicense, and/or sell copies of the Software, and to

193−permit persons to whom the Software is furnished to do so, subject to

194−the following conditions:

195−

196−The above copyright notice and this permission notice shall be

197−included in all copies or substantial portions of the Software.

198−

199−THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,

200−EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF

201−MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND

202−NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE

203−LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION

204−OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION

205−WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

HCAR-Pandoc.texnew file+35

@@ -0,0 +1,35 @@

1+% Pandoc-JP.tex

2+\begin{hcarentry}{Pandoc}

3+\label{pandoc}

4+\report{John MacFarlane}%05/11

5+\status{active development}

6+\participants{Andrea Rossato, Peter Wang, Paulo Tanimoto, Eric Kow,

7+Luke Plant, Justin Bogner, Paul Rivier, Nathan Gass, Puneeth Chaganti,

8+Josef Svenningsson, Etienne Millon, Joost Kremers}

9+\makeheader

10+

11+Pandoc aspires to be the swiss army knife of text markup formats: it

12+can read markdown and (with some limitations) HTML, LaTeX, Textile, and

13+reStructuredText, and it can write markdown, reStructuredText, HTML,

14+DocBook XML, OpenDocument XML, ODT, RTF, groff man, MediaWiki markup,

15+GNU Texinfo, LaTeX, ConTeXt, EPUB, Textile, Emacs org-mode,

16+Slidy, and S5. Pandoc's markdown syntax includes extensions for LaTeX math,

17+tables, definition lists, footnotes, and more.

18+

19+Since the last report, many new features have been added and improvements

20+made. Some highlights:

21+\begin{compactitem}

22+\item Support for Textile input and output.

23+\item Support for Emacs org-mode output.

24+\item A new ``builder'' module for constructing Pandoc documents programatically.

25+\item Support for \LaTeX math macros in markdown documents.

26+\item Support for automatic citations and bibliographies using Andrea

27+Rossato's citeproc-hs library.

28+\end{compactitem}

29+

30+These last two changes bring two of the most powerful features of \LaTeX

31+to pandoc.

32+

33+\FurtherReading

34+ \url{http://johnmacfarlane.net/pandoc/}

35+\end{hcarentry}

INSTALLnew file+208

@@ -0,0 +1,208 @@

1+% Installing pandoc

2+

3+These instructions explain how to install pandoc from source.

4+Binary packages or ports of pandoc are available for freebsd

5+and several linux distributions, so check your package manager.

6+There are also binary installers for Windows and Mac OS X.

7+

8+If you are installing the development version from github, see also:

9+https://github.com/jgm/pandoc/wiki/Installing-the-development-version-of-pandoc

10+

11+Quick install

12+-------------

13+

14+1. Install the [Haskell platform]. This will give you [GHC] and

15+ the [cabal-install] build tool, as well as `alex` and `happy`.

16+ If you do not use the Haskell platform, you'll need to install

17+ `alex` and `happy` separately:

18+

19+ cabal install alex happy

20+

21+2. Update your package database:

22+

23+ cabal update

24+

25+3. Use `cabal` to install pandoc and its dependencies:

26+

27+ cabal install pandoc

28+

29+ This procedure will install the released version of pandoc,

30+ which will be downloaded automatically from HackageDB.

31+ If you want to install a modified or development version

32+ of pandoc instead, switch to the source directory and do

33+ as above, but without the 'pandoc':

34+

35+ cabal install

36+

37+ Note: If you obtained the source from the git repository (rather

38+ than a release tarball), you'll need to do

39+

40+ git submodule update --init

41+

42+ to fetch the contents of `data/templates` before `cabal install`.

43+

44+4. Make sure the `$CABALDIR/bin` directory is in your path. You should

45+ now be able to run `pandoc`:

46+

47+ pandoc --help

48+

49+ [Not sure where `$CABALDIR` is?](http://www.haskell.org/haskellwiki/Cabal-Install#The_cabal-install_configuration_file)

50+

51+5. Make sure the `$CABALDIR/share/man/man1` directory is in your `MANPATH`.

52+ You should now be able to access the `pandoc` man page:

53+

54+ man pandoc

55+

56+6. If you want to process citations with pandoc, you will also need to

57+ install a separate package, `pandoc-citeproc`. This can be installed

58+ using cabal:

59+

60+ cabal install pandoc-citeproc

61+

62+ By default `pandoc-citeproc` uses the "i;unicode-casemap" method

63+ to sort bibliography entries (RFC 5051). If you would like to

64+ use the locale-sensitive unicode collation algorithm instead,

65+ specify the `unicode_collation` flag:

66+

67+ cabal install pandoc-citeproc -funicode_collation

68+

69+ Note that this requires the `text-icu` library, which in turn

70+ depends on the C library `icu4c`. Installation directions

71+ vary by platform. Here is how it might work on OSX with homebrew:

72+

73+ brew install icu4c

74+ cabal install --extra-lib-dirs=/usr/local/Cellar/icu4c/51.1/lib \

75+ --extra-include-dirs=/usr/local/Cellar/icu4c/51.1/include \

76+ -funicode_collation text-icu pandoc-citeproc

77+

78+[GHC]: http://www.haskell.org/ghc/

79+[Haskell platform]: http://hackage.haskell.org/platform/

80+[cabal-install]: http://hackage.haskell.org/trac/hackage/wiki/CabalInstall

81+

82+Custom install

83+--------------

84+

85+This is a step-by-step procedure that offers maximal control

86+over the build and installation. Most users should use the

87+quick install, but this information may be of use to packagers.

88+For more details, see the [Cabal User's Guide]. These instructions

89+assume that the pandoc source directory is your working directory.

90+

91+1. Install dependencies: in addition to the [Haskell platform],

92+ you will need a number of additional libraries. You can install

93+ them all with

94+

95+ cabal update

96+ cabal install --only-dependencies

97+

98+2. Configure:

99+

100+ cabal configure --prefix=DIR --bindir=DIR --libdir=DIR \

101+ --datadir=DIR --libsubdir=DIR --datasubdir=DIR --docdir=DIR \

102+ --htmldir=DIR --program-prefix=PREFIX --program-suffix=SUFFIX \

103+ --mandir=DIR --flags=FLAGSPEC

104+

105+ All of the options have sensible defaults that can be overridden

106+ as needed.

107+

108+ `FLAGSPEC` is a list of Cabal configuration flags, optionally

109+ preceded by a `-` (to force the flag to `false`), and separated

110+ by spaces. Pandoc's flags include:

111+

112+ - `embed_data_files`: embed all data files into the binary (default no).

113+ This is helpful if you want to create a relocatable binary.

114+ Note: if this option is selected, you need to install the

115+ `hsb2hs` preprocessor:

116+

117+ cabal install hsb2hs

118+

119+ - `http-conduit`: use the `http-conduit` library to fetch external

120+ resources (default yes -- without this, pandoc cannot make SSL

121+ connections)

122+

123+3. Build:

124+

125+ cabal build

126+

127+4. Build API documentation:

128+

129+ cabal haddock --html-location=URL --hyperlink-source

130+

131+5. Copy the files:

132+

133+ cabal copy --destdir=PATH

134+

135+ The default destdir is `/`.

136+

137+6. Register pandoc as a GHC package:

138+

139+ cabal register

140+

141+ Package managers may want to use the `--gen-script` option to

142+ generate a script that can be run to register the package at

143+ install time.

144+

145+Creating a relocatable binary

146+-----------------------------

147+

148+It is possible to compile pandoc such that the data files

149+pandoc uses are embedded in the binary. The resulting binary

150+can be run from any directory and is completely self-contained.

151+

152+ cabal install hsb2hs # a required build tool

153+ cabal install --flags="embed_data_files" citeproc-hs

154+ cabal configure --flags="embed_data_files"

155+ cabal build

156+

157+You can find the pandoc executable in `dist/build/pandoc`. Copy this wherever

158+you please.

159+

160+[zip-archive]: http://hackage.haskell.org/package/zip-archive

161+[highlighting-kate]: http://hackage.haskell.org/package/highlighting-kate

162+[blaze-html]: http://hackage.haskell.org/package/blaze-html

163+[Cabal User's Guide]: http://www.haskell.org/cabal/release/latest/doc/users-guide/builders.html#setup-configure-paths

164+

165+Running tests

166+-------------

167+

168+Pandoc comes with an automated test suite integrated to cabal.

169+To build the tests:

170+

171+ cabal configure --enable-tests && cabal build

172+

173+To run the tests:

174+

175+ cabal test

176+

177+To run particular tests (pattern-matching on their names), use

178+the `-t` option:

179+

180+ cabal test --test-options='-t markdown'

181+

182+If you add a new feature to pandoc, please add tests as well, following

183+the pattern of the existing tests. The test suite code is in

184+`tests/test-pandoc.hs`. If you are adding a new reader or writer, it is

185+probably easiest to add some data files to the `tests` directory, and

186+modify `tests/Tests/Old.hs`. Otherwise, it is better to modify the module

187+under the `tests/Tests` hierarchy corresponding to the pandoc module you

188+are changing.

189+

190+Running benchmarks

191+------------------

192+

193+To build the benchmarks:

194+

195+ cabal configure --enable-benchmarks && cabal build

196+

197+To run the benchmarks:

198+

199+ cabal bench

200+

201+To use a smaller sample size so the benchmarks run faster:

202+

203+ cabal bench --benchmark-options='-s 20'

204+

205+To run just the markdown benchmarks:

206+

207+ cabal bench --benchmark-options='markdown'

208+

INSTALL.mddeleted−415

@@ -1,415 +0,0 @@

1−# Installing pandoc

2−

3−The simplest way to get the latest pandoc release is to use the installer.

4−

5−<a href="https://github.com/jgm/pandoc/releases/latest"

6− class="btn btn-primary" id="downloadInstallerBtn">

7− Download the latest installer

8−</a>

9−

10−For alternative ways to install pandoc, see below

11−under the heading for your operating system.

12−

13−## Windows

14−

15−There is a package installer at pandoc's [download page].

16−This will install pandoc, replacing older versions, and

17−update your path to include the directory where pandoc's

18−binaries are installed.

19−

20−If you prefer not to use the msi installer, we also provide

21−a zip file that contains pandoc's binaries and

22−documentation. Simply unzip this file and move the binaries

23−to a directory of your choice.

24−

25−Alternatively, you can install pandoc using

26−[Chocolatey](https://chocolatey.org):

27−

28− choco install pandoc

29−

30−Chocolatey can also install other software that integrates with Pandoc.

31−For example, to install `rsvg-convert` (from [librsvg], covering formats

32−without SVG support), [Python] (to use Pandoc filters), and

33−[MiKTeX] (to typeset PDFs with [LaTeX]):

34−

35− choco install rsvg-convert python miktex

36−

37−Using multiple installation methods can result in two separate

38−installations of pandoc; it is recommended to properly uninstall

39−pandoc before switching to an alternative installation method.

40−

41−By default, Pandoc creates PDFs using LaTeX.

42−We recommend installing it via [MiKTeX].

43−

44−## macOS

45−

46−There is a package installer at pandoc's [download page].

47−If you later want to uninstall the package, you can do so

48−by downloading [this script][uninstaller]

49−and running it with `perl uninstall-pandoc.pl`.

50−

51−Alternatively, you can install pandoc using

52−[Homebrew](https://brew.sh):

53−

54− brew install pandoc

55−

56−Homebrew can also install other software that integrates with Pandoc.

57−For example, to install [librsvg] (its `rsvg-convert` covers formats

58−without SVG support), [Python] (to use Pandoc filters), and

59−[BasicTeX] (to typeset PDFs with [LaTeX]):

60−

61− brew install librsvg python homebrew/cask/basictex

62−

63−Note: On unsupported versions of macOS (more than three releases old),

64−Homebrew installs from source, which takes additional time and disk space

65−for the `ghc` compiler and dependent Haskell libraries.

66−

67−We also provide a zip file containing the binaries and man

68−pages, for those who prefer not to use the installer. Simply

69−unzip the file and move the binaries and man pages to

70−whatever directory you like.

71−

72−By default, Pandoc creates PDFs using LaTeX. Because a full [MacTeX]

73−installation uses four gigabytes of disk space, we recommend

74−[BasicTeX] or [TinyTeX](https://yihui.org/tinytex/)

75−and using the `tlmgr` tool to install additional packages

76−as needed. If you receive errors warning of fonts not found:

77−

78− tlmgr install collection-fontsrecommended

79−

80−## Linux

81−

82−Check whether the pandoc version in your package manager is

83−not outdated. Pandoc is in the [Debian], [Ubuntu], [Slackware],

84−[Arch], [Fedora], [NiXOS], [openSUSE], [gentoo] and [Void] repositories.

85−

86−To get the latest release, we provide a binary package for amd64

87−architecture on the **[download page]**.

88−

89−The executable is statically linked and

90−has no dynamic dependencies or dependencies on external

91−data files. Note: because of the static

92−linking, the pandoc binary from this package cannot use lua

93−filters that require external lua modules written in C.

94−

95−Both a tarball and a deb installer are provided. To install the deb:

96−

97− sudo dpkg -i $DEB

98−

99−where `$DEB` is the path to the downloaded deb. This will

100−install the `pandoc` executable and man page.

101−

102−If you use an RPM-based distro, you may be able to install

103−the deb from our download page using `alien`.

104−

105−On any distro, you may install from the tarball into `$DEST`

106−(say, `/usr/local/` or `$HOME/.local`) by doing

107−

108− tar xvzf $TGZ --strip-components 1 -C $DEST

109−

110−where `$TGZ` is the path to the downloaded zipped tarball.

111−For Pandoc versions before 2.0, which don't provide

112−a tarball, try instead

113−

114− ar p $DEB data.tar.gz | tar xvz --strip-components 2 -C $DEST

115−

116−You can also install from source, using the

117−instructions below under [Compiling from source].

118−Note that most distros have the Haskell platform in their

119−package repositories. For example, on Debian/Ubuntu,

120−you can install it with `apt-get install haskell-platform`.

121−

122−For PDF output, you'll need LaTeX. We recommend installing

123−[TeX Live](https://www.tug.org/texlive/) via your package

124−manager. (On Debian/Ubuntu, `apt-get install texlive`.)

125−

126−## Chrome OS

127−

128−On Chrome OS, pandoc can be installed using the

129−[chromebrew](https://github.com/skycocker/chromebrew) package manager

130−with the command:

131−

132−```sh

133−crew install pandoc

134−```

135−

136−This will automatically build and configure pandoc for the specific

137−device you are using.

138−

139−## BSD

140−

141−Pandoc is in the [NetBSD] and [FreeBSD ports] repositories.

142−

143−## Docker

144−

145−The official Docker images for pandoc can be found at

146−<https://github.com/pandoc/dockerfiles> and at

147−[dockerhub](https://hub.docker.com/).

148−

149−The [pandoc/core](https://hub.docker.com/r/pandoc/core)

150−image contains `pandoc`.

151−

152−The [pandoc/latex](https://hub.docker.com/r/pandoc/latex)

153−image also contains the minimal LaTeX installation needed

154−to produce PDFs using pandoc.

155−

156−To run pandoc using Docker, converting `README.md` to `README.pdf`:

157−

158− docker run --rm --volume "`pwd`:/data" --user `id -u`:`id -g` pandoc/latex README.md -o README.pdf

159−

160−## GitHub Actions

161−

162−Pandoc can be run through

163−[GitHub Actions](https://github.com/features/actions). For some

164−examples, see <https://github.com/pandoc/pandoc-action-example>.

165−

166−## Compiling from source

167−

168−If for some reason a binary package is not available for your

169−platform, or if you want to hack on pandoc or use a non-released

170−version, you can install from source.

171−

172−### Getting the pandoc source code

173−

174−Source tarballs can be found at

175−<https://hackage.haskell.org/package/pandoc>. For example, to

176−fetch the source for version 1.17.0.3:

177−

178− wget https://hackage.haskell.org/package/pandoc-1.17.0.3/pandoc-1.17.0.3.tar.gz

179− tar xvzf pandoc-1.17.0.3.tar.gz

180− cd pandoc-1.17.0.3

181−

182−Or you can fetch the development code by cloning the repository:

183−

184− git clone https://github.com/jgm/pandoc

185− cd pandoc

186−

187−Note: there may be times when the development code is broken

188−or depends on other libraries which must be installed

189−separately. Unless you really know what you're doing, install

190−the last released version.

191−

192−### Quick stack method

193−

194−The easiest way to build pandoc from source is to use [stack][stack]:

195−

196−1. Install [stack][stack]. Note that Pandoc requires stack >= 1.7.0.

197−

198−2. Change to the pandoc source directory and issue the following commands:

199−

200− stack setup

201− stack install

202−

203− `stack setup` will automatically download the ghc compiler

204− if you don't have it. `stack install` will install the

205− `pandoc` executable into `~/.local/bin`, which you should

206− add to your `PATH`. This process will take a while, and

207− will consume a considerable amount of disk space.

208−

209−### Quick cabal method

210−

211−1. Install the [Haskell platform]. This will give you [GHC] and

212− the [cabal-install] build tool. Note that pandoc requires

213− GHC >= 7.10 and cabal >= 2.0.

214−

215−2. Update your package database:

216−

217− cabal update

218−

219−3. Check your cabal version with

220−

221− cabal --version

222−

223− If you have a version less than 2.0, install the latest with:

224−

225− cabal install cabal-install

226−

227−4. Use `cabal` to install pandoc and its dependencies:

228−

229− cabal install pandoc

230−

231− This procedure will install the released version of pandoc,

232− which will be downloaded automatically from HackageDB.

233−

234− If you want to install a modified or development version

235− of pandoc instead, switch to the source directory and do

236− as above, but without the 'pandoc':

237−

238− cabal install

239−

240−5. Make sure the `$CABALDIR/bin` directory is in your path. You should

241− now be able to run `pandoc`:

242−

243− pandoc --help

244−

245− [Not sure where `$CABALDIR` is?](https://wiki.haskell.org/Cabal-Install#The_cabal-install_configuration_file)

246−

247−5. By default `pandoc` uses the "i;unicode-casemap" method

248− to sort bibliography entries (RFC 5051). If you would like to

249− use the locale-sensitive unicode collation algorithm instead,

250− specify the `icu` flag (which affects the dependency `citeproc`):

251−

252− cabal install pandoc -ficu

253−

254− Note that this requires the `text-icu` library, which in turn

255− depends on the C library `icu4c`. Installation directions

256− vary by platform. Here is how it might work on macOS with Homebrew:

257−

258− brew install icu4c

259− stack install pandoc \

260− --flag "citeproc:icu" \

261− --extra-lib-dirs=/usr/local/opt/icu4c/lib \

262− --extra-include-dirs=/usr/local/opt/icu4c/include

263−

264−6. The `pandoc.1` man page will be installed automatically. cabal shows

265− you where it is installed: you may need to set your `MANPATH`

266− accordingly. If `MANUAL.txt` has been modified, the man page can be

267− rebuilt: `make man/pandoc.1`.

268−

269−

270−### Custom cabal method

271−

272−This is a step-by-step procedure that offers maximal control

273−over the build and installation. Most users should use the

274−quick install, but this information may be of use to packagers.

275−For more details, see the [Cabal User's Guide]. These instructions

276−assume that the pandoc source directory is your working directory.

277−You will need cabal version 2.0 or higher.

278−

279−1. Install dependencies: in addition to the [Haskell platform],

280− you will need a number of additional libraries. You can install

281− them all with

282−

283− cabal update

284− cabal install --only-dependencies

285−

286−2. Configure:

287−

288− cabal configure --prefix=DIR --bindir=DIR --libdir=DIR \

289− --datadir=DIR --libsubdir=DIR --datasubdir=DIR --docdir=DIR \

290− --htmldir=DIR --program-prefix=PREFIX --program-suffix=SUFFIX \

291− --mandir=DIR --flags=FLAGSPEC --enable-tests

292−

293− All of the options have sensible defaults that can be overridden

294− as needed.

295−

296− `FLAGSPEC` is a list of Cabal configuration flags, optionally

297− preceded by a `-` (to force the flag to `false`), and separated

298− by spaces. Pandoc's flags include:

299−

300− - `embed_data_files`: embed all data files into the binary (default no).

301− This is helpful if you want to create a relocatable binary.

302−

303− - `https`: enable support for downloading resources over https

304− (using the `http-client` and `http-client-tls` libraries).

305−

306−3. Build:

307−

308− cabal build

309− cabal test

310−

311−4. Build API documentation:

312−

313− cabal haddock --html-location=URL --hyperlink-source

314−

315−5. Copy the files:

316−

317− cabal copy --destdir=PATH

318−

319− The default destdir is `/`.

320−

321−6. Register pandoc as a GHC package:

322−

323− cabal register

324−

325− Package managers may want to use the `--gen-script` option to

326− generate a script that can be run to register the package at

327− install time.

328−

329−### Creating a relocatable binary

330−

331−It is possible to compile pandoc such that the data files

332−pandoc uses are embedded in the binary. The resulting binary

333−can be run from any directory and is completely self-contained.

334−With cabal, add `-fembed_data_files` to the `cabal configure`

335−or `cabal install` commands.

336−

337−With stack, use `--flag pandoc:embed_data_files`.

338−

339−

340−

341−### Running tests

342−

343−Pandoc comes with an automated test suite.

344−To run with cabal, `cabal test`; to run with stack, `stack

345−test`.

346−

347−To run particular tests (pattern-matching on their names), use

348−the `-p` option:

349−

350− cabal install pandoc --enable-tests

351− cabal test --test-options='-p markdown'

352−

353−Or with stack:

354−

355− stack test --test-arguments='-p markdown'

356−

357−It is often helpful to add `-j4` (run tests in parallel)

358−and `--hide-successes` (don't clutter output with successes)

359−to the test arguments as well.

360−

361−If you add a new feature to pandoc, please add tests as well, following

362−the pattern of the existing tests. The test suite code is in

363−`test/test-pandoc.hs`. If you are adding a new reader or writer, it is

364−probably easiest to add some data files to the `test` directory, and

365−modify `test/Tests/Old.hs`. Otherwise, it is better to modify the module

366−under the `test/Tests` hierarchy corresponding to the pandoc module you

367−are changing.

368−

369−### Running benchmarks

370−

371−To build and run the benchmarks:

372−

373− cabal configure --enable-benchmarks && cabal build

374− cabal bench

375−

376−or with stack:

377−

378− stack bench

379−

380−To use a smaller sample size so the benchmarks run faster:

381−

382− cabal bench --benchmark-options='-s 20'

383−

384−To run just the markdown benchmarks:

385−

386− cabal bench --benchmark-options='markdown'

387−

388−

389−[Arch]: https://www.archlinux.org/packages/community/x86_64/pandoc/

390−[Cabal User's Guide]: https://cabal.readthedocs.io/

391−[Debian]: https://packages.debian.org/pandoc

392−[Fedora]: https://apps.fedoraproject.org/packages/pandoc

393−[FreeBSD ports]: https://www.freshports.org/textproc/hs-pandoc/

394−[GHC]: https://www.haskell.org/ghc/

395−[Haskell platform]: https://hackage.haskell.org/platform/

396−[MacPorts]: https://trac.macports.org/browser/trunk/dports/textproc/pandoc/Portfile

397−[MacTeX]: https://tug.org/mactex/

398−[BasicTeX]: https://www.tug.org/mactex/morepackages.html

399−[LaTeX]: https://www.latex-project.org

400−[MiKTeX]: https://miktex.org/

401−[librsvg]: https://wiki.gnome.org/Projects/LibRsvg

402−[Python]: https://www.python.org

403−[NetBSD]: https://pkgsrc.se/wip/pandoc

404−[NixOS]: https://nixos.org/nixos/packages.html

405−[Slackware]: https://www.slackbuilds.org/result/?search=pandoc&sv=

406−[Ubuntu]: https://packages.ubuntu.com/pandoc

407−[download page]: https://github.com/jgm/pandoc/releases/latest

408−[gentoo]: https://packages.gentoo.org/package/app-text/pandoc

409−[haskell repository]: https://wiki.archlinux.org/index.php/Haskell_Package_Guidelines#.5Bhaskell.5D

410−[openSUSE]: https://software.opensuse.org/package/pandoc

411−[source tarball]: https://hackage.haskell.org/package/pandoc

412−[stack]: https://docs.haskellstack.org/en/stable/install_and_upgrade.html

413−[cabal-install]: https://hackage.haskell.org/package/cabal-install

414−[Void]: https://voidlinux.org/

415−[uninstaller]: https://raw.githubusercontent.com/jgm/pandoc/master/macos/uninstall-pandoc.pl

Interact.hsnew file+30

@@ -0,0 +1,30 @@

1+-- Get an interactive shell with the right packages to load

2+-- pandoc modules.

3+

4+-- To use:

5+-- runghc Interact.hs

6+-- then,

7+-- :l Text/Pandoc.hs

8+-- (or whichever package you like)

9+

10+-- You must have first done a 'cabal configure' or 'cabal install'

11+

12+import System.Process

13+import Distribution.Simple.LocalBuildInfo

14+import Distribution.Package

15+import Distribution.Version

16+import Data.List (intercalate)

17+

18+main = do

19+ setupConfig' <- readFile "dist/setup-config"

20+ let setupConfig = read $ unlines $ drop 1 $ lines setupConfig'

21+ let (Just (ComponentLocalBuildInfo { componentPackageDeps = deps })) = libraryConfig setupConfig

22+ let packageSpecs = map (toPackageSpec . snd) deps

23+ let args = ["-optP-include", "-optP../dist/build/autogen/cabal_macros.h","-cpp","-I../dist/build/autogen","-i../dist/build/autogen"] ++ concatMap (\p -> ["-package",p]) packageSpecs

24+ print args

25+ ph <- runProcess "ghci" args (Just "src") Nothing Nothing Nothing Nothing

26+ waitForProcess ph

27+

28+toPackageSpec pkg = pkgN ++ "-" ++ pkgV

29+ where (PackageName pkgN) = pkgName pkg

30+ pkgV = intercalate "." $ map show $ versionBranch $ pkgVersion pkg

MANUAL.txtdeleted−6520

@@ -1,6520 +0,0 @@

1−---

2−title: Pandoc User's Guide

3−author: John MacFarlane

4−date: June 20, 2021

5−---

6−

7−# Synopsis

8−

9−`pandoc` [*options*] [*input-file*]...

10−

11−# Description

12−

13−Pandoc is a [Haskell] library for converting from one markup format to

14−another, and a command-line tool that uses this library.

15−

16−Pandoc can convert between numerous markup and word processing formats,

17−including, but not limited to, various flavors of [Markdown], [HTML],

18−[LaTeX] and [Word docx]. For the full lists of input and output formats,

19−see the `--from` and `--to` [options below][General options].

20−Pandoc can also produce [PDF] output: see [creating a PDF], below.

21−

22−Pandoc's enhanced version of Markdown includes syntax for [tables],

23−[definition lists], [metadata blocks], [footnotes], [citations], [math],

24−and much more. See below under [Pandoc's Markdown].

25−

26−Pandoc has a modular design: it consists of a set of readers, which parse

27−text in a given format and produce a native representation of the document

28−(an _abstract syntax tree_ or AST), and a set of writers, which convert

29−this native representation into a target format. Thus, adding an input

30−or output format requires only adding a reader or writer. Users can also

31−run custom [pandoc filters] to modify the intermediate AST.

32−

33−Because pandoc's intermediate representation of a document is less

34−expressive than many of the formats it converts between, one should

35−not expect perfect conversions between every format and every other.

36−Pandoc attempts to preserve the structural elements of a document, but

37−not formatting details such as margin size. And some document elements,

38−such as complex tables, may not fit into pandoc's simple document

39−model. While conversions from pandoc's Markdown to all formats aspire

40−to be perfect, conversions from formats more expressive than pandoc's

41−Markdown can be expected to be lossy.

42−

43−## Using pandoc

44−

45−If no *input-files* are specified, input is read from *stdin*.

46−Output goes to *stdout* by default. For output to a file,

47−use the `-o` option:

48−

49− pandoc -o output.html input.txt

50−

51−By default, pandoc produces a document fragment. To produce a standalone

52−document (e.g. a valid HTML file including `<head>` and `<body>`),

53−use the `-s` or `--standalone` flag:

54−

55− pandoc -s -o output.html input.txt

56−

57−For more information on how standalone documents are produced, see

58−[Templates] below.

59−

60−If multiple input files are given, `pandoc` will concatenate them all (with

61−blank lines between them) before parsing. (Use `--file-scope` to parse files

62−individually.)

63−

64−## Specifying formats

65−

66−The format of the input and output can be specified explicitly using

67−command-line options. The input format can be specified using the

68−`-f/--from` option, the output format using the `-t/--to` option.

69−Thus, to convert `hello.txt` from Markdown to LaTeX, you could type:

70−

71− pandoc -f markdown -t latex hello.txt

72−

73−To convert `hello.html` from HTML to Markdown:

74−

75− pandoc -f html -t markdown hello.html

76−

77−Supported input and output formats are listed below under [Options]

78−(see `-f` for input formats and `-t` for output formats). You

79−can also use `pandoc --list-input-formats` and

80−`pandoc --list-output-formats` to print lists of supported

81−formats.

82−

83−If the input or output format is not specified explicitly, `pandoc`

84−will attempt to guess it from the extensions of the filenames.

85−Thus, for example,

86−

87− pandoc -o hello.tex hello.txt

88−

89−will convert `hello.txt` from Markdown to LaTeX. If no output file

90−is specified (so that output goes to *stdout*), or if the output file's

91−extension is unknown, the output format will default to HTML.

92−If no input file is specified (so that input comes from *stdin*), or

93−if the input files' extensions are unknown, the input format will

94−be assumed to be Markdown.

95−

96−## Character encoding

97−

98−Pandoc uses the UTF-8 character encoding for both input and output.

99−If your local character encoding is not UTF-8, you

100−should pipe input and output through [`iconv`]:

101−

102− iconv -t utf-8 input.txt | pandoc | iconv -f utf-8

103−

104−Note that in some output formats (such as HTML, LaTeX, ConTeXt,

105−RTF, OPML, DocBook, and Texinfo), information about

106−the character encoding is included in the document header, which

107−will only be included if you use the `-s/--standalone` option.

108−

109−[`iconv`]: https://www.gnu.org/software/libiconv/

110−

111−## Creating a PDF

112−

113−To produce a PDF, specify an output file with a `.pdf` extension:

114−

115− pandoc test.txt -o test.pdf

116−

117−By default, pandoc will use LaTeX to create the PDF, which requires

118−that a LaTeX engine be installed (see `--pdf-engine` below).

119−Alternatively, pandoc can use ConTeXt, roff ms, or HTML as an

120−intermediate format. To do this, specify an output file with a

121−`.pdf` extension, as before, but add the `--pdf-engine` option

122−or `-t context`, `-t html`, or `-t ms` to the command line.

123−The tool used to generate the PDF from the intermediate format

124−may be specified using `--pdf-engine`.

125−

126−You can control the PDF style using variables, depending on

127−the intermediate format used: see [variables for LaTeX],

128−[variables for ConTeXt], [variables for `wkhtmltopdf`],

129−[variables for ms]. When HTML is used as an intermediate

130−format, the output can be styled using `--css`.

131−

132−To debug the PDF creation, it can be useful to look at the intermediate

133−representation: instead of `-o test.pdf`, use for example `-s -o test.tex`

134−to output the generated LaTeX. You can then test it with `pdflatex test.tex`.

135−

136−When using LaTeX, the following packages need to be available

137−(they are included with all recent versions of [TeX Live]):

138−[`amsfonts`], [`amsmath`], [`lm`], [`unicode-math`],

139−[`iftex`], [`listings`] (if the

140−`--listings` option is used), [`fancyvrb`], [`longtable`],

141−[`booktabs`], [`graphicx`] (if the document

142−contains images), [`hyperref`], [`xcolor`],

143−[`ulem`], [`geometry`] (with the `geometry` variable set),

144−[`setspace`] (with `linestretch`), and

145−[`babel`] (with `lang`). The use of `xelatex` or `lualatex` as

146−the PDF engine requires [`fontspec`]. `lualatex` uses

147−[`selnolig`]. `xelatex` uses [`polyglossia`] (with `lang`),

148−[`xecjk`], and [`bidi`] (with the `dir` variable set). If the

149−`mathspec` variable is set, `xelatex` will use [`mathspec`]

150−instead of [`unicode-math`]. The [`upquote`] and [`microtype`]

151−packages are used if available, and [`csquotes`] will be used

152−for [typography] if the `csquotes` variable or metadata field is

153−set to a true value. The [`natbib`], [`biblatex`], [`bibtex`],

154−and [`biber`] packages can optionally be used for [citation

155−rendering]. The following packages will be used to improve

156−output quality if present, but pandoc does not require them to

157−be present: [`upquote`] (for straight quotes in verbatim

158−environments), [`microtype`] (for better spacing adjustments),

159−[`parskip`] (for better inter-paragraph spaces), [`xurl`] (for

160−better line breaks in URLs), [`bookmark`] (for better PDF

161−bookmarks), and [`footnotehyper`] or [`footnote`] (to allow

162−footnotes in tables).

163−

164−[TeX Live]: https://www.tug.org/texlive/

165−[`amsfonts`]: https://ctan.org/pkg/amsfonts

166−[`amsmath`]: https://ctan.org/pkg/amsmath

167−[`babel`]: https://ctan.org/pkg/babel

168−[`biber`]: https://ctan.org/pkg/biber

169−[`biblatex`]: https://ctan.org/pkg/biblatex

170−[`bibtex`]: https://ctan.org/pkg/bibtex

171−[`bidi`]: https://ctan.org/pkg/bidi

172−[`bookmark`]: https://ctan.org/pkg/bookmark

173−[`booktabs`]: https://ctan.org/pkg/booktabs

174−[`csquotes`]: https://ctan.org/pkg/csquotes

175−[`fancyvrb`]: https://ctan.org/pkg/fancyvrb

176−[`fontspec`]: https://ctan.org/pkg/fontspec

177−[`footnote`]: https://ctan.org/pkg/footnote

178−[`footnotehyper`]: https://ctan.org/pkg/footnotehyper

179−[`geometry`]: https://ctan.org/pkg/geometry

180−[`graphicx`]: https://ctan.org/pkg/graphicx

181−[`grffile`]: https://ctan.org/pkg/grffile

182−[`hyperref`]: https://ctan.org/pkg/hyperref

183−[`iftex`]: https://ctan.org/pkg/iftex

184−[`listings`]: https://ctan.org/pkg/listings

185−[`lm`]: https://ctan.org/pkg/lm

186−[`longtable`]: https://ctan.org/pkg/longtable

187−[`mathspec`]: https://ctan.org/pkg/mathspec

188−[`microtype`]: https://ctan.org/pkg/microtype

189−[`natbib`]: https://ctan.org/pkg/natbib

190−[`parskip`]: https://ctan.org/pkg/parskip

191−[`polyglossia`]: https://ctan.org/pkg/polyglossia

192−[`prince`]: https://www.princexml.com/

193−[`setspace`]: https://ctan.org/pkg/setspace

194−[`ulem`]: https://ctan.org/pkg/ulem

195−[`unicode-math`]: https://ctan.org/pkg/unicode-math

196−[`upquote`]: https://ctan.org/pkg/upquote

197−[`weasyprint`]: https://weasyprint.org

198−[`wkhtmltopdf`]: https://wkhtmltopdf.org

199−[`xcolor`]: https://ctan.org/pkg/xcolor

200−[`xecjk`]: https://ctan.org/pkg/xecjk

201−[`xurl`]: https://ctan.org/pkg/xurl

202−[`selnolig`]: https://ctan.org/pkg/selnolig

203−

204−

205−

206−## Reading from the Web

207−

208−Instead of an input file, an absolute URI may be given. In this case

209−pandoc will fetch the content using HTTP:

210−

211− pandoc -f html -t markdown https://www.fsf.org

212−

213−It is possible to supply a custom User-Agent string or other

214−header when requesting a document from a URL:

215−

216− pandoc -f html -t markdown --request-header User-Agent:"Mozilla/5.0" \

217− https://www.fsf.org

218−

219−# Options

220−

221−## General options {.options}

222−

223−`-f` *FORMAT*, `-r` *FORMAT*, `--from=`*FORMAT*, `--read=`*FORMAT*

224−

225−: Specify input format. *FORMAT* can be:

226−

227− ::: {#input-formats}

228− - `bibtex` ([BibTeX] bibliography)

229− - `biblatex` ([BibLaTeX] bibliography)

230− - `commonmark` ([CommonMark] Markdown)

231− - `commonmark_x` ([CommonMark] Markdown with extensions)

232− - `creole` ([Creole 1.0])

233− - `csljson` ([CSL JSON] bibliography)

234− - `csv` ([CSV] table)

235− - `docbook` ([DocBook])

236− - `docx` ([Word docx])

237− - `dokuwiki` ([DokuWiki markup])

238− - `epub` ([EPUB])

239− - `fb2` ([FictionBook2] e-book)

240− - `gfm` ([GitHub-Flavored Markdown]),

241− or the deprecated and less accurate `markdown_github`;

242− use [`markdown_github`](#markdown-variants) only

243− if you need extensions not supported in [`gfm`](#markdown-variants).

244− - `haddock` ([Haddock markup])

245− - `html` ([HTML])

246− - `ipynb` ([Jupyter notebook])

247− - `jats` ([JATS] XML)

248− - `jira` ([Jira]/Confluence wiki markup)

249− - `json` (JSON version of native AST)

250− - `latex` ([LaTeX])

251− - `markdown` ([Pandoc's Markdown])

252− - `markdown_mmd` ([MultiMarkdown])

253− - `markdown_phpextra` ([PHP Markdown Extra])

254− - `markdown_strict` (original unextended [Markdown])

255− - `mediawiki` ([MediaWiki markup])

256− - `man` ([roff man])

257− - `muse` ([Muse])

258− - `native` (native Haskell)

259− - `odt` ([ODT])

260− - `opml` ([OPML])

261− - `org` ([Emacs Org mode])

262− - `rst` ([reStructuredText])

263− - `t2t` ([txt2tags])

264− - `textile` ([Textile])

265− - `tikiwiki` ([TikiWiki markup])

266− - `twiki` ([TWiki markup])

267− - `vimwiki` ([Vimwiki])

268− :::

269−

270− Extensions can be individually enabled or disabled by

271− appending `+EXTENSION` or `-EXTENSION` to the format name.

272− See [Extensions] below, for a list of extensions and

273− their names. See `--list-input-formats` and `--list-extensions`,

274− below.

275−

276−`-t` *FORMAT*, `-w` *FORMAT*, `--to=`*FORMAT*, `--write=`*FORMAT*

277−

278−: Specify output format. *FORMAT* can be:

279−

280− ::: {#output-formats}

281− - `asciidoc` ([AsciiDoc]) or `asciidoctor` ([AsciiDoctor])

282− - `beamer` ([LaTeX beamer][`beamer`] slide show)

283− - `bibtex` ([BibTeX] bibliography)

284− - `biblatex` ([BibLaTeX] bibliography)

285− - `commonmark` ([CommonMark] Markdown)

286− - `commonmark_x` ([CommonMark] Markdown with extensions)

287− - `context` ([ConTeXt])

288− - `csljson` ([CSL JSON] bibliography)

289− - `docbook` or `docbook4` ([DocBook] 4)

290− - `docbook5` (DocBook 5)

291− - `docx` ([Word docx])

292− - `dokuwiki` ([DokuWiki markup])

293− - `epub` or `epub3` ([EPUB] v3 book)

294− - `epub2` (EPUB v2)

295− - `fb2` ([FictionBook2] e-book)

296− - `gfm` ([GitHub-Flavored Markdown]),

297− or the deprecated and less accurate `markdown_github`;

298− use [`markdown_github`](#markdown-variants) only

299− if you need extensions not supported in [`gfm`](#markdown-variants).

300− - `haddock` ([Haddock markup])

301− - `html` or `html5` ([HTML], i.e. [HTML5]/XHTML [polyglot markup])

302− - `html4` ([XHTML] 1.0 Transitional)

303− - `icml` ([InDesign ICML])

304− - `ipynb` ([Jupyter notebook])

305− - `jats_archiving` ([JATS] XML, Archiving and Interchange Tag Set)

306− - `jats_articleauthoring` ([JATS] XML, Article Authoring Tag Set)

307− - `jats_publishing` ([JATS] XML, Journal Publishing Tag Set)

308− - `jats` (alias for `jats_archiving`)

309− - `jira` ([Jira]/Confluence wiki markup)

310− - `json` (JSON version of native AST)

311− - `latex` ([LaTeX])

312− - `man` ([roff man])

313− - `markdown` ([Pandoc's Markdown])

314− - `markdown_mmd` ([MultiMarkdown])

315− - `markdown_phpextra` ([PHP Markdown Extra])

316− - `markdown_strict` (original unextended [Markdown])

317− - `mediawiki` ([MediaWiki markup])

318− - `ms` ([roff ms])

319− - `muse` ([Muse]),

320− - `native` (native Haskell),

321− - `odt` ([OpenOffice text document][ODT])

322− - `opml` ([OPML])

323− - `opendocument` ([OpenDocument])

324− - `org` ([Emacs Org mode])

325− - `pdf` ([PDF])

326− - `plain` (plain text),

327− - `pptx` ([PowerPoint] slide show)

328− - `rst` ([reStructuredText])

329− - `rtf` ([Rich Text Format])

330− - `texinfo` ([GNU Texinfo])

331− - `textile` ([Textile])

332− - `slideous` ([Slideous] HTML and JavaScript slide show)

333− - `slidy` ([Slidy] HTML and JavaScript slide show)

334− - `dzslides` ([DZSlides] HTML5 + JavaScript slide show),

335− - `revealjs` ([reveal.js] HTML5 + JavaScript slide show)

336− - `s5` ([S5] HTML and JavaScript slide show)

337− - `tei` ([TEI Simple])

338− - `xwiki` ([XWiki markup])

339− - `zimwiki` ([ZimWiki markup])

340− - the path of a custom Lua writer, see [Custom writers] below

341− :::

342−

343− Note that `odt`, `docx`, `epub`, and `pdf` output will not be directed

344− to *stdout* unless forced with `-o -`.

345−

346− Extensions can be individually enabled or

347− disabled by appending `+EXTENSION` or `-EXTENSION` to the format

348− name. See [Extensions] below, for a list of extensions and their

349− names. See `--list-output-formats` and `--list-extensions`, below.

350−

351−`-o` *FILE*, `--output=`*FILE*

352−

353−: Write output to *FILE* instead of *stdout*. If *FILE* is

354− `-`, output will go to *stdout*, even if a non-textual format

355− (`docx`, `odt`, `epub2`, `epub3`) is specified.

356−

357−`--data-dir=`*DIRECTORY*

358−

359−: Specify the user data directory to search for pandoc data files.

360− If this option is not specified, the default user data directory

361− will be used. On \*nix and macOS systems this will be the `pandoc`

362− subdirectory of the XDG data directory (by default,

363− `$HOME/.local/share`, overridable by setting the `XDG_DATA_HOME`

364− environment variable). If that directory does not exist and

365− `$HOME/.pandoc` exists, it will be used (for backwards compatibility).

366− On Windows the default user data directory is

367− `C:\Users\USERNAME\AppData\Roaming\pandoc`.

368− You can find the default user data directory on your system by

369− looking at the output of `pandoc --version`.

370− Data files placed in this directory (for example, `reference.odt`,

371− `reference.docx`, `epub.css`, `templates`) will override

372− pandoc's normal defaults.

373−

374−`-d` *FILE*, `--defaults=`*FILE*

375−

376−: Specify a set of default option settings. *FILE* is a YAML

377− file whose fields correspond to command-line option

378− settings. All options for document conversion, including input

379− and output files, can be set using a defaults file. The file will

380− be searched for first in the working directory, and then in

381− the `defaults` subdirectory of the user data directory

382− (see `--data-dir`). The `.yaml` extension may be omitted.

383− See the section [Default files] for more information on the

384− file format. Settings from the defaults file may be

385− overridden or extended by subsequent options on the command

386− line.

387−

388−`--bash-completion`

389−

390−: Generate a bash completion script. To enable bash completion

391− with pandoc, add this to your `.bashrc`:

392−

393− eval "$(pandoc --bash-completion)"

394−

395−`--verbose`

396−

397−: Give verbose debugging output.

398−

399−`--quiet`

400−

401−: Suppress warning messages.

402−

403−`--fail-if-warnings`

404−

405−: Exit with error status if there are any warnings.

406−

407−`--log=`*FILE*

408−

409−: Write log messages in machine-readable JSON format to

410− *FILE*. All messages above DEBUG level will be written,

411− regardless of verbosity settings (`--verbose`, `--quiet`).

412−

413−`--list-input-formats`

414−

415−: List supported input formats, one per line.

416−

417−`--list-output-formats`

418−

419−: List supported output formats, one per line.

420−

421−`--list-extensions`[`=`*FORMAT*]

422−

423−: List supported extensions for *FORMAT*, one per line, preceded

424− by a `+` or `-` indicating whether it is enabled by default

425− in *FORMAT*. If *FORMAT* is not specified, defaults for

426− pandoc's Markdown are given.

427−

428−`--list-highlight-languages`

429−

430−: List supported languages for syntax highlighting, one per

431− line.

432−

433−`--list-highlight-styles`

434−

435−: List supported styles for syntax highlighting, one per line.

436− See `--highlight-style`.

437−

438−`-v`, `--version`

439−

440−: Print version.

441−

442−`-h`, `--help`

443−

444−: Show usage message.

445−

446−[Markdown]: https://daringfireball.net/projects/markdown/

447−[CommonMark]: https://commonmark.org

448−[PHP Markdown Extra]: https://michelf.ca/projects/php-markdown/extra/

449−[GitHub-Flavored Markdown]: https://help.github.com/articles/github-flavored-markdown/

450−[MultiMarkdown]: https://fletcherpenney.net/multimarkdown/

451−[reStructuredText]: https://docutils.sourceforge.io/docs/ref/rst/introduction.html

452−[S5]: https://meyerweb.com/eric/tools/s5/

453−[Slidy]: https://www.w3.org/Talks/Tools/Slidy2/

454−[Slideous]: https://goessner.net/articles/slideous/

455−[HTML]: https://www.w3.org/html/

456−[HTML5]: https://html.spec.whatwg.org/

457−[polyglot markup]: https://www.w3.org/TR/html-polyglot/

458−[XHTML]: https://www.w3.org/TR/xhtml1/

459−[LaTeX]: https://www.latex-project.org/

460−[`beamer`]: https://ctan.org/pkg/beamer

461−[Beamer User's Guide]: http://mirrors.ctan.org/macros/latex/contrib/beamer/doc/beameruserguide.pdf

462−[ConTeXt]: https://www.contextgarden.net/

463−[Rich Text Format]: https://en.wikipedia.org/wiki/Rich_Text_Format

464−[DocBook]: https://docbook.org

465−[JATS]: https://jats.nlm.nih.gov

466−[Jira]: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all

467−[txt2tags]: https://txt2tags.org

468−[EPUB]: http://idpf.org/epub

469−[OPML]: http://dev.opml.org/spec2.html

470−[OpenDocument]: http://opendocument.xml.org

471−[ODT]: https://en.wikipedia.org/wiki/OpenDocument

472−[Textile]: https://www.promptworks.com/textile

473−[MediaWiki markup]: https://www.mediawiki.org/wiki/Help:Formatting

474−[DokuWiki markup]: https://www.dokuwiki.org/dokuwiki

475−[ZimWiki markup]: https://zim-wiki.org/manual/Help/Wiki_Syntax.html

476−[XWiki markup]: https://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/Features/XWikiSyntax/

477−[TWiki markup]: https://twiki.org/cgi-bin/view/TWiki/TextFormattingRules

478−[TikiWiki markup]: https://doc.tiki.org/Wiki-Syntax-Text#The_Markup_Language_Wiki-Syntax

479−[Haddock markup]: https://www.haskell.org/haddock/doc/html/ch03s08.html

480−[Creole 1.0]: http://www.wikicreole.org/wiki/Creole1.0

481−[CSV]: https://tools.ietf.org/html/rfc4180

482−[roff man]: https://man.cx/groff_man(7)

483−[roff ms]: https://man.cx/groff_ms(7)

484−[Haskell]: https://www.haskell.org

485−[GNU Texinfo]: https://www.gnu.org/software/texinfo/

486−[Emacs Org mode]: https://orgmode.org

487−[AsciiDoc]: https://www.methods.co.nz/asciidoc/

488−[AsciiDoctor]: https://asciidoctor.org/

489−[DZSlides]: https://paulrouget.com/dzslides/

490−[Word docx]: https://en.wikipedia.org/wiki/Office_Open_XML

491−[PDF]: https://www.adobe.com/pdf/

492−[reveal.js]: https://revealjs.com/

493−[FictionBook2]: http://www.fictionbook.org/index.php/Eng:XML_Schema_Fictionbook_2.1

494−[Jupyter notebook]: https://nbformat.readthedocs.io/en/latest/

495−[InDesign ICML]: https://wwwimages.adobe.com/www.adobe.com/content/dam/acom/en/devnet/indesign/sdk/cs6/idml/idml-cookbook.pdf

496−[TEI Simple]: https://github.com/TEIC/TEI-Simple

497−[Muse]: https://amusewiki.org/library/manual

498−[PowerPoint]: https://en.wikipedia.org/wiki/Microsoft_PowerPoint

499−[Vimwiki]: https://vimwiki.github.io

500−[CSL JSON]: https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html

501−[BibTeX]: https://ctan.org/pkg/bibtex

502−[BibLaTeX]: https://ctan.org/pkg/biblatex

503−

504−## Reader options {.options}

505−

506−`--shift-heading-level-by=`*NUMBER*

507−

508−: Shift heading levels by a positive or negative integer.

509− For example, with `--shift-heading-level-by=-1`, level 2

510− headings become level 1 headings, and level 3 headings

511− become level 2 headings. Headings cannot have a level

512− less than 1, so a heading that would be shifted below level 1

513− becomes a regular paragraph. Exception: with a shift of -N,

514− a level-N heading at the beginning of the document

515− replaces the metadata title. `--shift-heading-level-by=-1`

516− is a good choice when converting HTML or Markdown documents that

517− use an initial level-1 heading for the document title and

518− level-2+ headings for sections. `--shift-heading-level-by=1`

519− may be a good choice for converting Markdown documents that

520− use level-1 headings for sections to HTML, since pandoc uses

521− a level-1 heading to render the document title.

522−

523−`--base-header-level=`*NUMBER*

524−

525−: *Deprecated. Use `--shift-heading-level-by`=X instead,

526− where X = NUMBER - 1.* Specify the base level for headings

527− (defaults to 1).

528−

529−`--strip-empty-paragraphs`

530−

531−: *Deprecated. Use the `+empty_paragraphs` extension instead.*

532− Ignore paragraphs with no content. This option is useful

533− for converting word processing documents where users have

534− used empty paragraphs to create inter-paragraph space.

535−

536−`--indented-code-classes=`*CLASSES*

537−

538−: Specify classes to use for indented code blocks--for example,

539− `perl,numberLines` or `haskell`. Multiple classes may be separated

540− by spaces or commas.

541−

542−`--default-image-extension=`*EXTENSION*

543−

544−: Specify a default extension to use when image paths/URLs have no

545− extension. This allows you to use the same source for formats that

546− require different kinds of images. Currently this option only affects

547− the Markdown and LaTeX readers.

548−

549−`--file-scope`

550−

551−: Parse each file individually before combining for multifile

552− documents. This will allow footnotes in different files with the

553− same identifiers to work as expected. If this option is set,

554− footnotes and links will not work across files. Reading binary

555− files (docx, odt, epub) implies `--file-scope`.

556−

557−`-F` *PROGRAM*, `--filter=`*PROGRAM*

558−

559−: Specify an executable to be used as a filter transforming the

560− pandoc AST after the input is parsed and before the output is

561− written. The executable should read JSON from stdin and write

562− JSON to stdout. The JSON must be formatted like pandoc's own

563− JSON input and output. The name of the output format will be

564− passed to the filter as the first argument. Hence,

565−

566− pandoc --filter ./caps.py -t latex

567−

568− is equivalent to

569−

570− pandoc -t json | ./caps.py latex | pandoc -f json -t latex

571−

572− The latter form may be useful for debugging filters.

573−

574− Filters may be written in any language. `Text.Pandoc.JSON`

575− exports `toJSONFilter` to facilitate writing filters in Haskell.

576− Those who would prefer to write filters in python can use the

577− module [`pandocfilters`], installable from PyPI. There are also

578− pandoc filter libraries in [PHP], [perl], and

579− [JavaScript/node.js].

580−

581− In order of preference, pandoc will look for filters in

582−

583− 1. a specified full or relative path (executable or

584− non-executable)

585−

586− 2. `$DATADIR/filters` (executable or non-executable)

587− where `$DATADIR` is the user data directory (see

588− `--data-dir`, above).

589−

590− 3. `$PATH` (executable only)

591−

592− Filters, Lua-filters, and citeproc processing are applied in

593− the order specified on the command line.

594−

595−`-L` *SCRIPT*, `--lua-filter=`*SCRIPT*

596−

597−: Transform the document in a similar fashion as JSON filters (see

598− `--filter`), but use pandoc's built-in Lua filtering system. The given

599− Lua script is expected to return a list of Lua filters which will be

600− applied in order. Each Lua filter must contain element-transforming

601− functions indexed by the name of the AST element on which the filter

602− function should be applied.

603−

604− The `pandoc` Lua module provides helper functions for element

605− creation. It is always loaded into the script's Lua environment.

606−

607− See the [Lua filters documentation] for further details.

608−

609− In order of preference, pandoc will look for Lua filters in

610−

611− 1. a specified full or relative path

612−

613− 2. `$DATADIR/filters` where `$DATADIR` is the user data

614− directory (see `--data-dir`, above).

615−

616− Filters, Lua filters, and citeproc processing are applied in

617− the order specified on the command line.

618−

619−`-M` *KEY*[`=`*VAL*], `--metadata=`*KEY*[`:`*VAL*]

620−

621−: Set the metadata field *KEY* to the value *VAL*. A value specified

622− on the command line overrides a value specified in the document

623− using [YAML metadata blocks][Extension: `yaml_metadata_block`].

624− Values will be parsed as YAML boolean or string values. If no value is

625− specified, the value will be treated as Boolean true. Like

626− `--variable`, `--metadata` causes template variables to be set.

627− But unlike `--variable`, `--metadata` affects the metadata of the

628− underlying document (which is accessible from filters and may be

629− printed in some output formats) and metadata values will be escaped

630− when inserted into the template.

631−

632−`--metadata-file=`*FILE*

633−

634−: Read metadata from the supplied YAML (or JSON) file. This

635− option can be used with every input format, but string scalars

636− in the YAML file will always be parsed as Markdown. Generally,

637− the input will be handled the same as in [YAML metadata

638− blocks][Extension: `yaml_metadata_block`]. This option can be

639− used repeatedly to include multiple metadata files; values in

640− files specified later on the command line will be preferred

641− over those specified in earlier files. Metadata values

642− specified inside the document, or by using `-M`, overwrite

643− values specified with this option.

644−

645−`-p`, `--preserve-tabs`

646−

647−: Preserve tabs instead of converting them to spaces. (By default, pandoc

648− converts tabs to spaces before parsing its input.) Note that this will

649− only affect tabs in literal code spans and code blocks. Tabs in regular

650− text are always treated as spaces.

651−

652−`--tab-stop=`*NUMBER*

653−

654−: Specify the number of spaces per tab (default is 4).

655−

656−`--track-changes=accept`|`reject`|`all`

657−

658−: Specifies what to do with insertions, deletions, and comments

659− produced by the MS Word "Track Changes" feature. `accept` (the

660− default) processes all the insertions and deletions.

661− `reject` ignores them. Both `accept` and `reject` ignore comments.

662− `all` includes all insertions, deletions, and comments, wrapped

663− in spans with `insertion`, `deletion`, `comment-start`, and

664− `comment-end` classes, respectively. The author and time of

665− change is included. `all` is useful for scripting: only

666− accepting changes from a certain reviewer, say, or before a

667− certain date. If a paragraph is inserted or deleted,

668− `track-changes=all` produces a span with the class

669− `paragraph-insertion`/`paragraph-deletion` before the

670− affected paragraph break. This option only affects the docx

671− reader.

672−

673−`--extract-media=`*DIR*

674−

675−: Extract images and other media contained in or linked from

676− the source document to the path *DIR*, creating it if

677− necessary, and adjust the images references in the document

678− so they point to the extracted files. Media are downloaded,

679− read from the file system, or extracted from a binary

680− container (e.g. docx), as needed. The original file paths

681− are used if they are relative paths not containing `..`.

682− Otherwise filenames are constructed from the SHA1 hash of

683− the contents.

684−

685−`--abbreviations=`*FILE*

686−

687−: Specifies a custom abbreviations file, with abbreviations

688− one to a line. If this option is not specified, pandoc will

689− read the data file `abbreviations` from the user data

690− directory or fall back on a system default. To see the

691− system default, use

692− `pandoc --print-default-data-file=abbreviations`. The only

693− use pandoc makes of this list is in the Markdown reader.

694− Strings found in this list will be followed by a nonbreaking

695− space, and the period will not produce sentence-ending space

696− in formats like LaTeX. The strings may not contain spaces.

697−

698−[`pandocfilters`]: https://github.com/jgm/pandocfilters

699−[PHP]: https://github.com/vinai/pandocfilters-php

700−[perl]: https://metacpan.org/pod/Pandoc::Filter

701−[JavaScript/node.js]: https://github.com/mvhenderson/pandoc-filter-node

702−[Lua filters documentation]: https://pandoc.org/lua-filters.html

703−

704−## General writer options {.options}

705−

706−`-s`, `--standalone`

707−

708−: Produce output with an appropriate header and footer (e.g. a

709− standalone HTML, LaTeX, TEI, or RTF file, not a fragment). This option

710− is set automatically for `pdf`, `epub`, `epub3`, `fb2`, `docx`, and `odt`

711− output. For `native` output, this option causes metadata to

712− be included; otherwise, metadata is suppressed.

713−

714−`--template=`*FILE*|*URL*

715−

716−: Use the specified file as a custom template for the generated document.

717− Implies `--standalone`. See [Templates], below, for a description

718− of template syntax. If no extension is specified, an extension

719− corresponding to the writer will be added, so that `--template=special`

720− looks for `special.html` for HTML output. If the template is not

721− found, pandoc will search for it in the `templates` subdirectory of

722− the user data directory (see `--data-dir`). If this option is not used,

723− a default template appropriate for the output format will be used (see

724− `-D/--print-default-template`).

725−

726−`-V` *KEY*[`=`*VAL*], `--variable=`*KEY*[`:`*VAL*]

727−

728−: Set the template variable *KEY* to the value *VAL* when rendering the

729− document in standalone mode. If no *VAL* is specified, the

730− key will be given the value `true`.

731−

732−`-D` *FORMAT*, `--print-default-template=`*FORMAT*

733−

734−: Print the system default template for an output *FORMAT*. (See `-t`

735− for a list of possible *FORMAT*s.) Templates in the user data

736− directory are ignored. This option may be used with

737− `-o`/`--output` to redirect output to a file, but

738− `-o`/`--output` must come before `--print-default-template`

739− on the command line.

740−

741− Note that some of the default templates use partials, for

742− example `styles.html`. To print the partials, use

743− `--print-default-data-file`: for example,

744− `--print-default-data-file=templates/styles.html`.

745−

746−`--print-default-data-file=`*FILE*

747−

748−: Print a system default data file. Files in the user data directory

749− are ignored. This option may be used with `-o`/`--output` to

750− redirect output to a file, but `-o`/`--output` must come before

751− `--print-default-data-file` on the command line.

752−

753−`--eol=crlf`|`lf`|`native`

754−

755−: Manually specify line endings: `crlf` (Windows), `lf`

756− (macOS/Linux/UNIX), or `native` (line endings appropriate

757− to the OS on which pandoc is being run). The default is

758− `native`.

759−

760−`--dpi`=*NUMBER*

761−

762−: Specify the default dpi (dots per inch) value for conversion

763− from pixels to inch/centimeters and vice versa. (Technically,

764− the correct term would be ppi: pixels per inch.) The default

765− is 96dpi. When images contain information about dpi

766− internally, the encoded value is used instead of the default

767− specified by this option.

768−

769−`--wrap=auto`|`none`|`preserve`

770−

771−: Determine how text is wrapped in the output (the source

772− code, not the rendered version). With `auto` (the default),

773− pandoc will attempt to wrap lines to the column width specified by

774− `--columns` (default 72). With `none`, pandoc will not wrap

775− lines at all. With `preserve`, pandoc will attempt to

776− preserve the wrapping from the source document (that is,

777− where there are nonsemantic newlines in the source, there

778− will be nonsemantic newlines in the output as well).

779− Automatic wrapping does not currently work in HTML output.

780− In `ipynb` output, this option affects wrapping of the

781− contents of markdown cells.

782−

783−`--columns=`*NUMBER*

784−

785−: Specify length of lines in characters. This affects text wrapping

786− in the generated source code (see `--wrap`). It also affects

787− calculation of column widths for plain text tables (see [Tables] below).

788−

789−`--toc`, `--table-of-contents`

790−

791−: Include an automatically generated table of contents (or, in

792− the case of `latex`, `context`, `docx`, `odt`,

793− `opendocument`, `rst`, or `ms`, an instruction to create

794− one) in the output document. This option has no effect

795− unless `-s/--standalone` is used, and it has no effect

796− on `man`, `docbook4`, `docbook5`, or `jats` output.

797−

798− Note that if you are producing a PDF via `ms`, the table

799− of contents will appear at the beginning of the

800− document, before the title. If you would prefer it to

801− be at the end of the document, use the option

802− `--pdf-engine-opt=--no-toc-relocation`.

803−

804−`--toc-depth=`*NUMBER*

805−

806−: Specify the number of section levels to include in the table

807− of contents. The default is 3 (which means that level-1, 2, and 3

808− headings will be listed in the contents).

809−

810−`--strip-comments`

811−

812−: Strip out HTML comments in the Markdown or Textile source,

813− rather than passing them on to Markdown, Textile or HTML

814− output as raw HTML. This does not apply to HTML comments

815− inside raw HTML blocks when the `markdown_in_html_blocks`

816− extension is not set.

817−

818−`--no-highlight`

819−

820−: Disables syntax highlighting for code blocks and inlines, even when

821− a language attribute is given.

822−

823−`--highlight-style=`*STYLE*|*FILE*

824−

825−: Specifies the coloring style to be used in highlighted source code.

826− Options are `pygments` (the default), `kate`, `monochrome`,

827− `breezeDark`, `espresso`, `zenburn`, `haddock`, and `tango`.

828− For more information on syntax highlighting in pandoc, see

829− [Syntax highlighting], below. See also

830− `--list-highlight-styles`.

831−

832− Instead of a *STYLE* name, a JSON file with extension

833− `.theme` may be supplied. This will be parsed as a KDE

834− syntax highlighting theme and (if valid) used as the

835− highlighting style.

836−

837− To generate the JSON version of an existing style,

838− use `--print-highlight-style`.

839−

840−`--print-highlight-style=`*STYLE*|*FILE*

841−

842−: Prints a JSON version of a highlighting style, which can

843− be modified, saved with a `.theme` extension, and used

844− with `--highlight-style`. This option may be used with

845− `-o`/`--output` to redirect output to a file, but

846− `-o`/`--output` must come before `--print-highlight-style`

847− on the command line.

848−

849−`--syntax-definition=`*FILE*

850−

851−: Instructs pandoc to load a KDE XML syntax definition file,

852− which will be used for syntax highlighting of appropriately

853− marked code blocks. This can be used to add support for

854− new languages or to use altered syntax definitions for

855− existing languages. This option may be repeated to add

856− multiple syntax definitions.

857−

858−`-H` *FILE*, `--include-in-header=`*FILE*|*URL*

859−

860−: Include contents of *FILE*, verbatim, at the end of the header.

861− This can be used, for example, to include special

862− CSS or JavaScript in HTML documents. This option can be used

863− repeatedly to include multiple files in the header. They will be

864− included in the order specified. Implies `--standalone`.

865−

866−`-B` *FILE*, `--include-before-body=`*FILE*|*URL*

867−

868−: Include contents of *FILE*, verbatim, at the beginning of the

869− document body (e.g. after the `<body>` tag in HTML, or the

870− `\begin{document}` command in LaTeX). This can be used to include

871− navigation bars or banners in HTML documents. This option can be

872− used repeatedly to include multiple files. They will be included in

873− the order specified. Implies `--standalone`.

874−

875−`-A` *FILE*, `--include-after-body=`*FILE*|*URL*

876−

877−: Include contents of *FILE*, verbatim, at the end of the document

878− body (before the `</body>` tag in HTML, or the

879− `\end{document}` command in LaTeX). This option can be used

880− repeatedly to include multiple files. They will be included in the

881− order specified. Implies `--standalone`.

882−

883−`--resource-path=`*SEARCHPATH*

884−

885−: List of paths to search for images and other resources.

886− The paths should be separated by `:` on Linux, UNIX, and

887− macOS systems, and by `;` on Windows. If `--resource-path`

888− is not specified, the default resource path is the working

889− directory. Note that, if `--resource-path` is specified,

890− the working directory must be explicitly listed or it

891− will not be searched. For example:

892− `--resource-path=.:test` will search the working directory

893− and the `test` subdirectory, in that order.

894− This option can be used repeatedly. Search path components

895− that come later on the command line will be searched before

896− those that come earlier, so

897− `--resource-path foo:bar --resource-path baz:bim` is

898− equivalent to `--resource-path baz:bim:foo:bar`.

899−

900−`--request-header=`*NAME*`:`*VAL*

901−

902−: Set the request header *NAME* to the value *VAL* when making

903− HTTP requests (for example, when a URL is given on the

904− command line, or when resources used in a document must be

905− downloaded). If you're behind a proxy, you also need to set

906− the environment variable `http_proxy` to `http://...`.

907−

908−`--no-check-certificate`

909−

910−: Disable the certificate verification to allow access to

911− unsecure HTTP resources (for example when the certificate

912− is no longer valid or self signed).

913−

914−## Options affecting specific writers {.options}

915−

916−`--self-contained`

917−

918−: Produce a standalone HTML file with no external dependencies, using

919− `data:` URIs to incorporate the contents of linked scripts, stylesheets,

920− images, and videos. Implies `--standalone`. The resulting file should be

921− "self-contained," in the sense that it needs no external files and no net

922− access to be displayed properly by a browser. This option works only with

923− HTML output formats, including `html4`, `html5`, `html+lhs`, `html5+lhs`,

924− `s5`, `slidy`, `slideous`, `dzslides`, and `revealjs`. Scripts, images,

925− and stylesheets at absolute URLs will be downloaded; those at relative

926− URLs will be sought relative to the working directory (if the first source

927− file is local) or relative to the base URL (if the first source

928− file is remote). Elements with the attribute

929− `data-external="1"` will be left alone; the documents they

930− link to will not be incorporated in the document.

931− Limitation: resources that are loaded dynamically through

932− JavaScript cannot be incorporated; as a result,

933− `--self-contained` does not work with `--mathjax`, and some

934− advanced features (e.g. zoom or speaker notes) may not work

935− in an offline "self-contained" `reveal.js` slide show.

936−

937−`--html-q-tags`

938−

939−: Use `<q>` tags for quotes in HTML. (This option only has an

940− effect if the `smart` extension is enabled for the input

941− format used.)

942−

943−`--ascii`

944−

945−: Use only ASCII characters in output. Currently supported for XML

946− and HTML formats (which use entities instead of UTF-8 when this

947− option is selected), CommonMark, gfm, and Markdown (which use

948− entities), roff ms (which use hexadecimal escapes), and to a

949− limited degree LaTeX (which uses standard commands for accented

950− characters when possible). roff man output uses ASCII by default.

951−

952−`--reference-links`

953−

954−: Use reference-style links, rather than inline links, in writing Markdown

955− or reStructuredText. By default inline links are used. The

956− placement of link references is affected by the

957− `--reference-location` option.

958−

959−`--reference-location=block`|`section`|`document`

960−

961−: Specify whether footnotes (and references, if `reference-links` is

962− set) are placed at the end of the current (top-level) block, the

963− current section, or the document. The default is

964− `document`. Currently only affects the markdown writer.

965−

966−`--markdown-headings=setext`|`atx`

967−

968−: Specify whether to use ATX-style (`#`-prefixed) or

969− Setext-style (underlined) headings for level 1 and 2

970− headings in Markdown output. (The default is `atx`.)

971− ATX-style headings are always used for levels 3+.

972− This option also affects Markdown cells in `ipynb` output.

973−

974−`--atx-headers`

975−

976−: *Deprecated synonym for `--markdown-headings=atx`.*

977−

978−`--top-level-division=default`|`section`|`chapter`|`part`

979−

980−: Treat top-level headings as the given division type in

981− LaTeX, ConTeXt, DocBook, and TEI output. The hierarchy

982− order is part, chapter, then section; all headings are

983− shifted such that the top-level heading becomes the

984− specified type. The default behavior is to determine the

985− best division type via heuristics: unless other conditions

986− apply, `section` is chosen. When the `documentclass`

987− variable is set to `report`, `book`, or `memoir` (unless the

988− `article` option is specified), `chapter` is implied as the

989− setting for this option. If `beamer` is the output format,

990− specifying either `chapter` or `part` will cause top-level

991− headings to become `\part{..}`, while second-level headings

992− remain as their default type.

993−

994−`-N`, `--number-sections`

995−

996−: Number section headings in LaTeX, ConTeXt, HTML, Docx, ms, or EPUB

997− output. By default, sections are not numbered. Sections with class

998− `unnumbered` will never be numbered, even if `--number-sections`

999− is specified.

1000−

1001−`--number-offset=`*NUMBER*[`,`*NUMBER*`,`*...*]

1002−

1003−: Offset for section headings in HTML output (ignored in other

1004− output formats). The first number is added to the section number for

1005− top-level headings, the second for second-level headings, and so on.

1006− So, for example, if you want the first top-level heading in your

1007− document to be numbered "6", specify `--number-offset=5`.

1008− If your document starts with a level-2 heading which you want to

1009− be numbered "1.5", specify `--number-offset=1,4`.

1010− Offsets are 0 by default. Implies `--number-sections`.

1011−

1012−`--listings`

1013−

1014−: Use the [`listings`] package for LaTeX code blocks. The package

1015− does not support multi-byte encoding for source code. To handle UTF-8

1016− you would need to use a custom template. This issue is fully

1017− documented here: [Encoding issue with the listings package].

1018−

1019−`-i`, `--incremental`

1020−

1021−: Make list items in slide shows display incrementally (one by one).

1022− The default is for lists to be displayed all at once.

1023−

1024−`--slide-level=`*NUMBER*

1025−

1026−: Specifies that headings with the specified level create

1027− slides (for `beamer`, `s5`, `slidy`, `slideous`, `dzslides`). Headings

1028− above this level in the hierarchy are used to divide the

1029− slide show into sections; headings below this level create

1030− subheads within a slide. Note that content that is

1031− not contained under slide-level headings will not appear in

1032− the slide show. The default is to set the slide level based

1033− on the contents of the document; see [Structuring the slide

1034− show].

1035−

1036−`--section-divs`

1037−

1038−: Wrap sections in `<section>` tags (or `<div>` tags for `html4`),

1039− and attach identifiers to the enclosing `<section>` (or `<div>`)

1040− rather than the heading itself. See

1041− [Heading identifiers], below.

1042−

1043−`--email-obfuscation=none`|`javascript`|`references`

1044−

1045−: Specify a method for obfuscating `mailto:` links in HTML documents.

1046− `none` leaves `mailto:` links as they are. `javascript` obfuscates

1047− them using JavaScript. `references` obfuscates them by printing their

1048− letters as decimal or hexadecimal character references. The default

1049− is `none`.

1050−

1051−`--id-prefix=`*STRING*

1052−

1053−: Specify a prefix to be added to all identifiers and internal links

1054− in HTML and DocBook output, and to footnote numbers in Markdown

1055− and Haddock output. This is useful for preventing duplicate

1056− identifiers when generating fragments to be included in other pages.

1057−

1058−`-T` *STRING*, `--title-prefix=`*STRING*

1059−

1060−: Specify *STRING* as a prefix at the beginning of the title

1061− that appears in the HTML header (but not in the title as it

1062− appears at the beginning of the HTML body). Implies `--standalone`.

1063−

1064−`-c` *URL*, `--css=`*URL*

1065−

1066−: Link to a CSS style sheet. This option can be used repeatedly to

1067− include multiple files. They will be included in the order specified.

1068−

1069− A stylesheet is required for generating EPUB. If none is

1070− provided using this option (or the `css` or `stylesheet`

1071− metadata fields), pandoc will look for a file `epub.css` in the

1072− user data directory (see `--data-dir`). If it is not

1073− found there, sensible defaults will be used.

1074−

1075−`--reference-doc=`*FILE*

1076−

1077−: Use the specified file as a style reference in producing a

1078− docx or ODT file.

1079−

1080− Docx

1081−

1082− : For best results, the reference docx should be a modified

1083− version of a docx file produced using pandoc. The contents

1084− of the reference docx are ignored, but its stylesheets and

1085− document properties (including margins, page size, header,

1086− and footer) are used in the new docx. If no reference docx

1087− is specified on the command line, pandoc will look for a

1088− file `reference.docx` in the user data directory (see

1089− `--data-dir`). If this is not found either, sensible

1090− defaults will be used.

1091−

1092− To produce a custom `reference.docx`, first get a copy of

1093− the default `reference.docx`: `pandoc

1094− -o custom-reference.docx --print-default-data-file reference.docx`.

1095− Then open `custom-reference.docx` in Word, modify the

1096− styles as you wish, and save the file. For best

1097− results, do not make changes to this file other than

1098− modifying the styles used by pandoc:

1099−

1100− Paragraph styles:

1101−

1102− - Normal

1103− - Body Text

1104− - First Paragraph

1105− - Compact

1106− - Title

1107− - Subtitle

1108− - Author

1109− - Date

1110− - Abstract

1111− - Bibliography

1112− - Heading 1

1113− - Heading 2

1114− - Heading 3

1115− - Heading 4

1116− - Heading 5

1117− - Heading 6

1118− - Heading 7

1119− - Heading 8

1120− - Heading 9

1121− - Block Text

1122− - Footnote Text

1123− - Definition Term

1124− - Definition

1125− - Caption

1126− - Table Caption

1127− - Image Caption

1128− - Figure

1129− - Captioned Figure

1130− - TOC Heading

1131−

1132− Character styles:

1133−

1134− - Default Paragraph Font

1135− - Body Text Char

1136− - Verbatim Char

1137− - Footnote Reference

1138− - Hyperlink

1139− - Section Number

1140−

1141− Table style:

1142−

1143− - Table

1144−

1145− ODT

1146−

1147− : For best results, the reference ODT should be a modified

1148− version of an ODT produced using pandoc. The contents of

1149− the reference ODT are ignored, but its stylesheets are used

1150− in the new ODT. If no reference ODT is specified on the

1151− command line, pandoc will look for a file `reference.odt` in

1152− the user data directory (see `--data-dir`). If this is not

1153− found either, sensible defaults will be used.

1154−

1155− To produce a custom `reference.odt`, first get a copy of

1156− the default `reference.odt`: `pandoc

1157− -o custom-reference.odt --print-default-data-file reference.odt`.

1158− Then open `custom-reference.odt` in LibreOffice, modify

1159− the styles as you wish, and save the file.

1160−

1161− PowerPoint

1162−

1163− : Templates included with Microsoft PowerPoint 2013 (either with

1164− `.pptx` or `.potx` extension) are known to work, as are most

1165− templates derived from these.

1166−

1167− The specific requirement is that the template should begin with

1168− the following first four layouts:

1169−

1170− 1. Title Slide

1171− 2. Title and Content

1172− 3. Section Header

1173− 4. Two Content

1174−

1175− All templates included with a recent version of MS PowerPoint

1176− will fit these criteria. (You can click on `Layout` under the

1177− `Home` menu to check.)

1178−

1179− You can also modify the default `reference.pptx`: first run

1180− `pandoc -o custom-reference.pptx --print-default-data-file

1181− reference.pptx`, and then modify `custom-reference.pptx`

1182− in MS PowerPoint (pandoc will use the first four layout

1183− slides, as mentioned above).

1184−

1185−`--epub-cover-image=`*FILE*

1186−

1187−: Use the specified image as the EPUB cover. It is recommended

1188− that the image be less than 1000px in width and height. Note that

1189− in a Markdown source document you can also specify `cover-image`

1190− in a YAML metadata block (see [EPUB Metadata], below).

1191−

1192−`--epub-metadata=`*FILE*

1193−

1194−: Look in the specified XML file for metadata for the EPUB.

1195− The file should contain a series of [Dublin Core elements].

1196− For example:

1197−

1198− <dc:rights>Creative Commons</dc:rights>

1199− <dc:language>es-AR</dc:language>

1200−

1201− By default, pandoc will include the following metadata elements:

1202− `<dc:title>` (from the document title), `<dc:creator>` (from the

1203− document authors), `<dc:date>` (from the document date, which should

1204− be in [ISO 8601 format]), `<dc:language>` (from the `lang`

1205− variable, or, if is not set, the locale), and `<dc:identifier

1206− id="BookId">` (a randomly generated UUID). Any of these may be

1207− overridden by elements in the metadata file.

1208−

1209− Note: if the source document is Markdown, a YAML metadata block

1210− in the document can be used instead. See below under

1211− [EPUB Metadata].

1212−

1213−`--epub-embed-font=`*FILE*

1214−

1215−: Embed the specified font in the EPUB. This option can be repeated

1216− to embed multiple fonts. Wildcards can also be used: for example,

1217− `DejaVuSans-*.ttf`. However, if you use wildcards on the command

1218− line, be sure to escape them or put the whole filename in single quotes,

1219− to prevent them from being interpreted by the shell. To use the

1220− embedded fonts, you will need to add declarations like the following

1221− to your CSS (see `--css`):

1222−

1223− @font-face {

1224− font-family: DejaVuSans;

1225− font-style: normal;

1226− font-weight: normal;

1227− src:url("DejaVuSans-Regular.ttf");

1228− }

1229− @font-face {

1230− font-family: DejaVuSans;

1231− font-style: normal;

1232− font-weight: bold;

1233− src:url("DejaVuSans-Bold.ttf");

1234− }

1235− @font-face {

1236− font-family: DejaVuSans;

1237− font-style: italic;

1238− font-weight: normal;

1239− src:url("DejaVuSans-Oblique.ttf");

1240− }

1241− @font-face {

1242− font-family: DejaVuSans;

1243− font-style: italic;

1244− font-weight: bold;

1245− src:url("DejaVuSans-BoldOblique.ttf");

1246− }

1247− body { font-family: "DejaVuSans"; }

1248−

1249−`--epub-chapter-level=`*NUMBER*

1250−

1251−: Specify the heading level at which to split the EPUB into separate

1252− "chapter" files. The default is to split into chapters at level-1

1253− headings. This option only affects the internal composition of the

1254− EPUB, not the way chapters and sections are displayed to users. Some

1255− readers may be slow if the chapter files are too large, so for large

1256− documents with few level-1 headings, one might want to use a chapter

1257− level of 2 or 3.

1258−

1259−`--epub-subdirectory=`*DIRNAME*

1260−

1261−: Specify the subdirectory in the OCF container that is to hold

1262− the EPUB-specific contents. The default is `EPUB`. To put

1263− the EPUB contents in the top level, use an empty string.

1264−

1265−`--ipynb-output=all|none|best`

1266−

1267−: Determines how ipynb output cells are treated. `all` means

1268− that all of the data formats included in the original are

1269− preserved. `none` means that the contents of data cells

1270− are omitted. `best` causes pandoc to try to pick the

1271− richest data block in each output cell that is compatible

1272− with the output format. The default is `best`.

1273−

1274−`--pdf-engine=`*PROGRAM*

1275−

1276−: Use the specified engine when producing PDF output.

1277− Valid values are `pdflatex`, `lualatex`, `xelatex`, `latexmk`,

1278− `tectonic`, `wkhtmltopdf`, `weasyprint`, `prince`, `context`,

1279− and `pdfroff`. If the engine is not in your PATH, the full

1280− path of the engine may be specified here. If this option

1281− is not specified, pandoc uses the following defaults

1282− depending on the output format specified using `-t/--to`:

1283−

1284− - `-t latex` or none: `pdflatex` (other options: `xelatex`, `lualatex`,

1285− `tectonic`, `latexmk`)

1286− - `-t context`: `context`

1287− - `-t html`: `wkhtmltopdf` (other options: `prince`, `weasyprint`;

1288− see [print-css.rocks](https://print-css.rocks) for a good

1289− introduction to PDF generation from HTML/CSS.)

1290− - `-t ms`: `pdfroff`

1291−

1292−`--pdf-engine-opt=`*STRING*

1293−

1294−: Use the given string as a command-line argument to the `pdf-engine`.

1295− For example, to use a persistent directory `foo` for `latexmk`'s

1296− auxiliary files, use `--pdf-engine-opt=-outdir=foo`.

1297− Note that no check for duplicate options is done.

1298−

1299−[Dublin Core elements]: https://www.dublincore.org/specifications/dublin-core/dces/

1300−[ISO 8601 format]: https://www.w3.org/TR/NOTE-datetime

1301−[Encoding issue with the listings package]:

1302− https://en.wikibooks.org/wiki/LaTeX/Source_Code_Listings#Encoding_issue

1303−

1304−## Citation rendering {.options}

1305−

1306−`-C`, `--citeproc`

1307−

1308−: Process the citations in the file, replacing them with

1309− rendered citations and adding a bibliography.

1310− Citation processing will not take place unless bibliographic

1311− data is supplied, either through an external file specified

1312− using the `--bibliography` option or the `bibliography`

1313− field in metadata, or via a `references` section in metadata

1314− containing a list of citations in CSL YAML format with

1315− Markdown formatting. The style is controlled by a [CSL]

1316− stylesheet specified using the `--csl` option or the `csl`

1317− field in metadata. (If no stylesheet is specified,

1318− the `chicago-author-date` style will be used by default.)

1319− The citation processing transformation may be applied before

1320− or after filters or Lua filters (see `--filter`,

1321− `--lua-filter`): these transformations are applied in the

1322− order they appear on the command line. For more

1323− information, see the section on [Citations].

1324−

1325−`--bibliography=`*FILE*

1326−

1327−: Set the `bibliography` field in the document's metadata to *FILE*,

1328− overriding any value set in the metadata. If you supply

1329− this argument multiple times, each *FILE* will be added to

1330− bibliography. If *FILE* is a URL, it will be fetched

1331− via HTTP. If *FILE* is not found relative to the

1332− working directory, it will be sought in the resource path

1333− (see `--resource-path`).

1334−

1335−`--csl=`*FILE*

1336−

1337−: Set the `csl` field in the document's metadata to *FILE*,

1338− overriding any value set in the metadata. (This is equivalent to

1339− `--metadata csl=FILE`.) If *FILE* is a URL, it will be

1340− fetched via HTTP. If *FILE* is not found relative to the

1341− working directory, it will be sought in the resource path

1342− (see `--resource-path`) and finally in the `csl`

1343− subdirectory of the pandoc user data directory.

1344−

1345−`--citation-abbreviations=`*FILE*

1346−

1347−: Set the `citation-abbreviations` field in the document's metadata to

1348− *FILE*, overriding any value set in the metadata. (This is equivalent to

1349− `--metadata citation-abbreviations=FILE`.)

1350− If *FILE* is a URL, it will be fetched via HTTP. If *FILE* is not

1351− found relative to the working directory, it will be sought

1352− in the resource path (see `--resource-path`) and finally in

1353− the `csl` subdirectory of the pandoc user data directory.

1354−

1355−`--natbib`

1356−

1357−: Use [`natbib`] for citations in LaTeX output. This option

1358− is not for use with the `--citeproc` option or with PDF

1359− output. It is intended for use in producing a LaTeX file

1360− that can be processed with [`bibtex`].

1361−

1362−`--biblatex`

1363−

1364−: Use [`biblatex`] for citations in LaTeX output. This option

1365− is not for use with the `--citeproc` option or with PDF

1366− output. It is intended for use in producing a LaTeX file

1367− that can be processed with [`bibtex`] or [`biber`].

1368−

1369−## Math rendering in HTML {.options}

1370−

1371−The default is to render TeX math as far as possible using

1372−Unicode characters. Formulas are put inside a `span` with

1373−`class="math"`, so that they may be styled differently from the

1374−surrounding text if needed. However, this gives acceptable

1375−results only for basic math, usually you will want to use

1376−`--mathjax` or another of the following options.

1377−

1378−`--mathjax`[`=`*URL*]

1379−

1380−: Use [MathJax] to display embedded TeX math in HTML output.

1381− TeX math will be put between `\(...\)` (for inline math)

1382− or `\[...\]` (for display math) and wrapped in `<span>` tags

1383− with class `math`. Then the MathJax JavaScript will render it.

1384− The *URL* should point to the `MathJax.js` load script.

1385− If a *URL* is not provided, a link to the Cloudflare CDN will

1386− be inserted.

1387−

1388−`--mathml`

1389−

1390−: Convert TeX math to [MathML] (in `epub3`, `docbook4`,

1391− `docbook5`, `jats`, `html4` and `html5`). This is the

1392− default in `odt` output. Note that currently only Firefox

1393− and Safari (and select e-book readers) natively support

1394− MathML.

1395−

1396−`--webtex`[`=`*URL*]

1397−

1398−: Convert TeX formulas to `<img>` tags that link to an external script

1399− that converts formulas to images. The formula will be URL-encoded

1400− and concatenated with the URL provided. For SVG images you can for

1401− example use `--webtex https://latex.codecogs.com/svg.latex?`.

1402− If no URL is specified, the CodeCogs URL generating PNGs

1403− will be used (`https://latex.codecogs.com/png.latex?`).

1404− Note: the `--webtex` option will affect Markdown output

1405− as well as HTML, which is useful if you're targeting a

1406− version of Markdown without native math support.

1407−

1408−`--katex`[`=`*URL*]

1409−

1410−: Use [KaTeX] to display embedded TeX math in HTML output.

1411− The *URL* is the base URL for the KaTeX library. That directory

1412− should contain a `katex.min.js` and a `katex.min.css` file.

1413− If a *URL* is not provided, a link to the KaTeX CDN will be inserted.

1414−

1415−`--gladtex`

1416−

1417−: Enclose TeX math in `<eq>` tags in HTML output. The resulting HTML

1418− can then be processed by [GladTeX] to produce SVG images of the typeset

1419− formulas and an HTML file with these images embedded.

1420−

1421− pandoc -s --gladtex input.md -o myfile.htex

1422− gladtex -d image_dir myfile.htex

1423− # produces myfile.html and images in image_dir

1424−

1425−[MathML]: https://www.w3.org/Math/

1426−[MathJax]: https://www.mathjax.org

1427−[KaTeX]: https://github.com/Khan/KaTeX

1428−[GladTeX]: https://humenda.github.io/GladTeX/

1429−

1430−## Options for wrapper scripts {.options}

1431−

1432−`--dump-args`

1433−

1434−: Print information about command-line arguments to *stdout*, then exit.

1435− This option is intended primarily for use in wrapper scripts.

1436− The first line of output contains the name of the output file specified

1437− with the `-o` option, or `-` (for *stdout*) if no output file was

1438− specified. The remaining lines contain the command-line arguments,

1439− one per line, in the order they appear. These do not include regular

1440− pandoc options and their arguments, but do include any options appearing

1441− after a `--` separator at the end of the line.

1442−

1443−`--ignore-args`

1444−

1445−: Ignore command-line arguments (for use in wrapper scripts).

1446− Regular pandoc options are not ignored. Thus, for example,

1447−

1448− pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1

1449−

1450− is equivalent to

1451−

1452− pandoc -o foo.html -s

1453−

1454−# Exit codes

1455−

1456−If pandoc completes successfully, it will return exit code 0.

1457−Nonzero exit codes have the following meanings:

1458−

1459− Code Error

1460−----- ------------------------------------

1461− 3 PandocFailOnWarningError

1462− 4 PandocAppError

1463− 5 PandocTemplateError

1464− 6 PandocOptionError

1465− 21 PandocUnknownReaderError

1466− 22 PandocUnknownWriterError

1467− 23 PandocUnsupportedExtensionError

1468− 24 PandocCiteprocError

1469− 31 PandocEpubSubdirectoryError

1470− 43 PandocPDFError

1471− 44 PandocXMLError

1472− 47 PandocPDFProgramNotFoundError

1473− 61 PandocHttpError

1474− 62 PandocShouldNeverHappenError

1475− 63 PandocSomeError

1476− 64 PandocParseError

1477− 65 PandocParsecError

1478− 66 PandocMakePDFError

1479− 67 PandocSyntaxMapError

1480− 83 PandocFilterError

1481− 91 PandocMacroLoop

1482− 92 PandocUTF8DecodingError

1483− 93 PandocIpynbDecodingError

1484− 94 PandocUnsupportedCharsetError

1485− 97 PandocCouldNotFindDataFileError

1486− 99 PandocResourceNotFound

1487−----- ------------------------------------

1488−

1489−# Default files

1490−

1491−The `--defaults` option may be used to specify a package

1492−of options. Here is a sample defaults file demonstrating all of

1493−the fields that may be used:

1494−

1495−``` yaml

1496−from: markdown+emoji

1497−# reader: may be used instead of from:

1498−to: html5

1499−# writer: may be used instead of to:

1500−

1501−# leave blank for output to stdout:

1502−output-file:

1503−# leave blank for input from stdin, use [] for no input:

1504−input-files:

1505−- preface.md

1506−- content.md

1507−# or you may use input-file: with a single value

1508−

1509−# Include options from the specified defaults files.

1510−# The files will be searched for first in the working directory

1511−# and then in the defaults subdirectory of the user data directory.

1512−# The files are included in the same order in which they appear in

1513−# the list. Options specified in this defaults file always have

1514−# priority over the included ones.

1515−defaults:

1516−- defsA

1517−- defsB

1518−

1519−template: letter

1520−standalone: true

1521−self-contained: false

1522−

1523−# note that structured variables may be specified:

1524−variables:

1525− documentclass: book

1526− classoption:

1527− - twosides

1528− - draft

1529−

1530−# metadata values specified here are parsed as literal

1531−# string text, not markdown:

1532−metadata:

1533− author:

1534− - Sam Smith

1535− - Julie Liu

1536−metadata-files:

1537−- boilerplate.yaml

1538−# or you may use metadata-file: with a single value

1539−

1540−# Note that these take files, not their contents:

1541−include-before-body: []

1542−include-after-body: []

1543−include-in-header: []

1544−resource-path: ["."]

1545−

1546−# turn on built-in citation processing. Note that if you need

1547−# control over when the citeproc processing is done relative

1548−# to other filters, you should instead use `citeproc` in the

1549−# list of `filters` (see below).

1550−citeproc: true

1551−csl: ieee

1552−bibliography:

1553−- foobar.bib

1554−- barbaz.json

1555−citation-abbreviations: abbrevs.json

1556−

1557−# Filters will be assumed to be Lua filters if they have

1558−# the .lua extension, and json filters otherwise. But

1559−# the filter type can also be specified explicitly, as shown.

1560−# Filters are run in the order specified.

1561−# To include the built-in citeproc filter, use either `citeproc`

1562−# or `{type: citeproc}`.

1563−filters:

1564−- wordcount.lua

1565−- type: json

1566− path: foo.lua

1567−

1568−file-scope: false

1569−

1570−data-dir:

1571−

1572−# ERROR, WARNING, or INFO

1573−verbosity: INFO

1574−log-file: log.json

1575−

1576−# citeproc, natbib, or biblatex. This only affects LaTeX

1577−# output. If you want to use citeproc to format citations,

1578−# you should also set 'citeproc: true' (see above).

1579−cite-method: citeproc

1580−

1581−# part, chapter, section, or default:

1582−top-level-division: chapter

1583−abbreviations:

1584−

1585−pdf-engine: pdflatex

1586−pdf-engine-opts:

1587−- "-shell-escape"

1588−# you may also use pdf-engine-opt: with a single option

1589−# pdf-engine-opt: "-shell-escape"

1590−

1591−# auto, preserve, or none

1592−wrap: auto

1593−columns: 78

1594−dpi: 72

1595−

1596−extract-media: mediadir

1597−

1598−table-of-contents: true

1599−toc-depth: 2

1600−number-sections: false

1601−# a list of offsets at each heading level

1602−number-offset: [0,0,0,0,0,0]

1603−# toc: may also be used instead of table-of-contents:

1604−shift-heading-level-by: 1

1605−section-divs: true

1606−identifier-prefix: foo

1607−title-prefix: ""

1608−strip-empty-paragraphs: true

1609−# lf, crlf, or native

1610−eol: lf

1611−strip-comments: false

1612−indented-code-classes: []

1613−ascii: true

1614−default-image-extension: ".jpg"

1615−

1616−# either a style name of a style definition file:

1617−highlight-style: pygments

1618−syntax-definitions:

1619−- c.xml

1620−# or you may use syntax-definition: with a single value

1621−listings: false

1622−

1623−reference-doc: myref.docx

1624−

1625−# method is plain, webtex, gladtex, mathml, mathjax, katex

1626−# you may specify a url with webtex, mathjax, katex

1627−html-math-method:

1628− method: mathjax

1629− url: "https://cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js"

1630−# none, references, or javascript

1631−email-obfuscation: javascript

1632−

1633−tab-stop: 8

1634−preserve-tabs: true

1635−

1636−incremental: false

1637−slide-level: 2

1638−

1639−epub-subdirectory: EPUB

1640−epub-metadata: meta.xml

1641−epub-fonts:

1642−- foobar.otf

1643−epub-chapter-level: 1

1644−epub-cover-image: cover.jpg

1645−

1646−reference-links: true

1647−# block, section, or document

1648−reference-location: block

1649−markdown-headings: setext

1650−

1651−# accept, reject, or all

1652−track-changes: accept

1653−

1654−html-q-tags: false

1655−css:

1656−- site.css

1657−

1658−# none, all, or best

1659−ipynb-output: best

1660−

1661−# A list of two-element lists

1662−request-headers:

1663−- ["User-Agent", "Mozilla/5.0"]

1664−

1665−fail-if-warnings: false

1666−dump-args: false

1667−ignore-args: false

1668−trace: false

1669−```

1670−

1671−Fields that are omitted will just have their regular

1672−default values. So a defaults file can be as simple as

1673−one line:

1674−

1675−``` yaml

1676−verbosity: INFO

1677−```

1678−

1679−In fields that expect a file path (or list of file paths), the

1680−following syntax may be used to interpolate environment variables:

1681−

1682−``` yaml

1683−csl: ${HOME}/mycsldir/special.csl

1684−```

1685−

1686−`${USERDATA}` may also be used; this will always resolve to the

1687−user data directory that is current when the defaults file is

1688−parsed, regardless of the setting of the environment

1689−variable `USERDATA`.

1690−

1691−`${.}` will resolve to the directory containing the default

1692−file itself. This allows you to refer to resources contained

1693−in that directory:

1694−

1695−``` yaml

1696−epub-cover-image: ${.}/cover.jpg

1697−epub-metadata: ${.}/meta.xml

1698−resource-path:

1699−- . # the working directory from which pandoc is run

1700−- ${.}/images # the images subdirectory of the directory

1701− # containing this defaults file

1702−```

1703−

1704−This environment variable interpolation syntax *only* works in

1705−fields that expect file paths.

1706−

1707−Default files can be placed in the `defaults` subdirectory of

1708−the user data directory and used from any directory. For

1709−example, one could create a file specifying defaults for writing

1710−letters, save it as `letter.yaml` in the `defaults` subdirectory

1711−of the user data directory, and then invoke these defaults

1712−from any directory using `pandoc --defaults letter`

1713−or `pandoc -dletter`.

1714−

1715−When multiple defaults are used, their contents will be combined.

1716−

1717−Note that, where command-line arguments may be repeated

1718−(`--metadata-file`, `--css`, `--include-in-header`,

1719−`--include-before-body`, `--include-after-body`, `--variable`,

1720−`--metadata`, `--syntax-definition`), the values specified on

1721−the command line will combine with values specified in the

1722−defaults file, rather than replacing them.

1723−

1724−# Templates

1725−

1726−When the `-s/--standalone` option is used, pandoc uses a template to

1727−add header and footer material that is needed for a self-standing

1728−document. To see the default template that is used, just type

1729−

1730− pandoc -D *FORMAT*

1731−

1732−where *FORMAT* is the name of the output format. A custom template

1733−can be specified using the `--template` option. You can also override

1734−the system default templates for a given output format *FORMAT*

1735−by putting a file `templates/default.*FORMAT*` in the user data

1736−directory (see `--data-dir`, above). *Exceptions:*

1737−

1738−- For `odt` output, customize the `default.opendocument`

1739− template.

1740−- For `pdf` output, customize the `default.latex` template

1741− (or the `default.context` template, if you use `-t context`,

1742− or the `default.ms` template, if you use `-t ms`, or the

1743− `default.html` template, if you use `-t html`).

1744−- `docx` and `pptx` have no template (however, you can use

1745− `--reference-doc` to customize the output).

1746−

1747−Templates contain *variables*, which allow for the inclusion of

1748−arbitrary information at any point in the file. They may be set at the

1749−command line using the `-V/--variable` option. If a variable is not set,

1750−pandoc will look for the key in the document's metadata, which can be set

1751−using either [YAML metadata blocks][Extension: `yaml_metadata_block`]

1752−or with the `-M/--metadata` option. In addition, some variables

1753−are given default values by pandoc. See [Variables] below for

1754−a list of variables used in pandoc's default templates.

1755−

1756−If you use custom templates, you may need to revise them as pandoc

1757−changes. We recommend tracking the changes in the default templates,

1758−and modifying your custom templates accordingly. An easy way to do this

1759−is to fork the [pandoc-templates] repository and merge in

1760−changes after each pandoc release.

1761−

1762− [pandoc-templates]: https://github.com/jgm/pandoc-templates

1763−

1764−## Template syntax

1765−

1766−### Comments

1767−

1768−Anything between the sequence `$--` and the end of the

1769−line will be treated as a comment and omitted from the output.

1770−

1771−### Delimiters

1772−

1773−To mark variables and control structures in the template,

1774−either `$`...`$` or `${`...`}` may be used as delimiters.

1775−The styles may also be mixed in the same template, but the

1776−opening and closing delimiter must match in each case. The

1777−opening delimiter may be followed by one or more spaces

1778−or tabs, which will be ignored. The closing delimiter may

1779−be followed by one or more spaces or tabs, which will be

1780−ignored.

1781−

1782−To include a literal `$` in the document, use `$$`.

1783−

1784−### Interpolated variables

1785−

1786−A slot for an interpolated variable is a variable name surrounded

1787−by matched delimiters. Variable names must begin with a letter

1788−and can contain letters, numbers, `_`, `-`, and `.`. The

1789−keywords `it`, `if`, `else`, `endif`, `for`, `sep`, and `endfor` may

1790−not be used as variable names. Examples:

1791−

1792−```

1793−$foo$

1794−$foo.bar.baz$

1795−$foo_bar.baz-bim$

1796−$ foo $

1797−${foo}

1798−${foo.bar.baz}

1799−${foo_bar.baz-bim}

1800−${ foo }

1801−```

1802−

1803−Variable names with periods are used to get at structured

1804−variable values. So, for example, `employee.salary` will return the

1805−value of the `salary` field of the object that is the value of

1806−the `employee` field.

1807−

1808−- If the value of the variable is simple value, it will be

1809− rendered verbatim. (Note that no escaping is done;

1810− the assumption is that the calling program will escape

1811− the strings appropriately for the output format.)

1812−- If the value is a list, the values will be concatenated.

1813−- If the value is a map, the string `true` will be rendered.

1814−- Every other value will be rendered as the empty string.

1815−

1816−### Conditionals

1817−

1818−A conditional begins with `if(variable)` (enclosed in

1819−matched delimiters) and ends with `endif` (enclosed in matched

1820−delimiters). It may optionally contain an `else` (enclosed in

1821−matched delimiters). The `if` section is used if

1822−`variable` has a non-empty value, otherwise the `else`

1823−section is used (if present). Examples:

1824−

1825−```

1826−$if(foo)$bar$endif$

1827−

1828−$if(foo)$

1829− $foo$

1830−$endif$

1831−

1832−$if(foo)$

1833−part one

1834−$else$

1835−part two

1836−$endif$

1837−

1838−${if(foo)}bar${endif}

1839−

1840−${if(foo)}

1841− ${foo}

1842−${endif}

1843−

1844−${if(foo)}

1845−${ foo.bar }

1846−${else}

1847−no foo!

1848−${endif}

1849−```

1850−

1851−The keyword `elseif` may be used to simplify complex nested

1852−conditionals:

1853−

1854−```

1855−$if(foo)$

1856−XXX

1857−$elseif(bar)$

1858−YYY

1859−$else$

1860−ZZZ

1861−$endif$

1862−```

1863−

1864−### For loops

1865−

1866−A for loop begins with `for(variable)` (enclosed in

1867−matched delimiters) and ends with `endfor` (enclosed in matched

1868−delimiters.

1869−

1870−- If `variable` is an array, the material inside the loop will

1871− be evaluated repeatedly, with `variable` being set to each

1872− value of the array in turn, and concatenated.

1873−- If `variable` is a map, the material inside will be set to

1874− the map.

1875−- If the value of the associated variable is not an array or

1876− a map, a single iteration will be performed on its value.

1877−

1878−Examples:

1879−

1880−```

1881−$for(foo)$$foo$$sep$, $endfor$

1882−

1883−$for(foo)$

1884− - $foo.last$, $foo.first$

1885−$endfor$

1886−

1887−${ for(foo.bar) }

1888− - ${ foo.bar.last }, ${ foo.bar.first }

1889−${ endfor }

1890−

1891−$for(mymap)$

1892−$it.name$: $it.office$

1893−$endfor$

1894−```

1895−

1896−You may optionally specify a separator between consecutive

1897−values using `sep` (enclosed in matched delimiters). The

1898−material between `sep` and the `endfor` is the separator.

1899−

1900−```

1901−${ for(foo) }${ foo }${ sep }, ${ endfor }

1902−```

1903−

1904−Instead of using `variable` inside the loop, the special

1905−anaphoric keyword `it` may be used.

1906−

1907−```

1908−${ for(foo.bar) }

1909− - ${ it.last }, ${ it.first }

1910−${ endfor }

1911−```

1912−

1913−### Partials

1914−

1915−Partials (subtemplates stored in different files) may be

1916−included by using the name of the partial, followed

1917−by `()`, for example:

1918−

1919−```

1920−${ styles() }

1921−```

1922−

1923−Partials will be sought in the directory containing

1924−the main template. The file name will be assumed to

1925−have the same extension as the main template if it

1926−lacks an extension. When calling the partial, the

1927−full name including file extension can also be used:

1928−

1929−```

1930−${ styles.html() }

1931−```

1932−

1933−(If a partial is not found in the directory of the

1934−template and the template path is given as a relative

1935−path, it will also be sought in the `templates`

1936−subdirectory of the user data directory.)

1937−

1938−Partials may optionally be applied to variables using

1939−a colon:

1940−

1941−```

1942−${ date:fancy() }

1943−

1944−${ articles:bibentry() }

1945−```

1946−

1947−If `articles` is an array, this will iterate over its

1948−values, applying the partial `bibentry()` to each one. So the

1949−second example above is equivalent to

1950−

1951−```

1952−${ for(articles) }

1953−${ it:bibentry() }

1954−${ endfor }

1955−```

1956−

1957−Note that the anaphoric keyword `it` must be used when

1958−iterating over partials. In the above examples,

1959−the `bibentry` partial should contain `it.title`

1960−(and so on) instead of `articles.title`.

1961−

1962−Final newlines are omitted from included partials.

1963−

1964−Partials may include other partials.

1965−

1966−A separator between values of an array may be specified

1967−in square brackets, immediately after the variable name

1968−or partial:

1969−

1970−```

1971−${months[, ]}$

1972−

1973−${articles:bibentry()[; ]$

1974−```

1975−

1976−The separator in this case is literal and (unlike with `sep`

1977−in an explicit `for` loop) cannot contain interpolated

1978−variables or other template directives.

1979−

1980−### Nesting

1981−

1982−To ensure that content is "nested," that is, subsequent lines

1983−indented, use the `^` directive:

1984−

1985−```

1986−$item.number$ $^$$item.description$ ($item.price$)

1987−```

1988−

1989−In this example, if `item.description` has multiple lines,

1990−they will all be indented to line up with the first line:

1991−

1992−```

1993−00123 A fine bottle of 18-year old

1994− Oban whiskey. ($148)

1995−```

1996−

1997−To nest multiple lines to the same level, align them

1998−with the `^` directive in the template. For example:

1999−

2000−```

2001−$item.number$ $^$$item.description$ ($item.price$)

2002− (Available til $item.sellby$.)

2003−```

2004−

2005−will produce

2006−

2007−```

2008−00123 A fine bottle of 18-year old

2009− Oban whiskey. ($148)

2010− (Available til March 30, 2020.)

2011−```

2012−

2013−If a variable occurs by itself on a line, preceded by whitespace

2014−and not followed by further text or directives on the same line,

2015−and the variable's value contains multiple lines, it will be

2016−nested automatically.

2017−

2018−### Breakable spaces

2019−

2020−Normally, spaces in the template itself (as opposed to values of

2021−the interpolated variables) are not breakable, but they can be

2022−made breakable in part of the template by using the `~` keyword

2023−(ended with another `~`).

2024−

2025−```

2026−$~$This long line may break if the document is rendered

2027−with a short line length.$~$

2028−```

2029−

2030−### Pipes

2031−

2032−A pipe transforms the value of a variable or partial. Pipes are

2033−specified using a slash (`/`) between the variable name (or partial)

2034−and the pipe name. Example:

2035−

2036−```

2037−$for(name)$

2038−$name/uppercase$

2039−$endfor$

2040−

2041−$for(metadata/pairs)$

2042−- $it.key$: $it.value$

2043−$endfor$

2044−

2045−$employee:name()/uppercase$

2046−```

2047−

2048−Pipes may be chained:

2049−

2050−```

2051−$for(employees/pairs)$

2052−$it.key/alpha/uppercase$. $it.name$

2053−$endfor$

2054−```

2055−

2056−Some pipes take parameters:

2057−

2058−```

2059−|----------------------|------------|

2060−$for(employee)$

2061−$it.name.first/uppercase/left 20 "| "$$it.name.salary/right 10 " | " " |"$

2062−$endfor$

2063−|----------------------|------------|

2064−```

2065−

2066−Currently the following pipes are predefined:

2067−

2068−- `pairs`: Converts a map or array to an array of maps,

2069− each with `key` and `value` fields. If the original

2070− value was an array, the `key` will be the array index,

2071− starting with 1.

2072−

2073−- `uppercase`: Converts text to uppercase.

2074−

2075−- `lowercase`: Converts text to lowercase.

2076−

2077−- `length`: Returns the length of the value: number

2078− of characters for a textual value, number of elements

2079− for a map or array.

2080−

2081−- `reverse`: Reverses a textual value or array,

2082− and has no effect on other values.

2083−

2084−- `first`: Returns the first value of an array, if

2085− applied to a non-empty array; otherwise returns

2086− the original value.

2087−

2088−- `last`: Returns the last value of an array, if

2089− applied to a non-empty array; otherwise returns

2090− the original value.

2091−

2092−- `rest`: Returns all but the first value of an array, if

2093− applied to a non-empty array; otherwise returns

2094− the original value.

2095−

2096−- `allbutlast`: Returns all but the last value of an array, if

2097− applied to a non-empty array; otherwise returns

2098− the original value.

2099−

2100−- `chomp`: Removes trailing newlines (and breakable space).

2101−

2102−- `nowrap`: Disables line wrapping on breakable spaces.

2103−

2104−- `alpha`: Converts textual values that can be

2105− read as an integer into lowercase alphabetic

2106− characters `a..z` (mod 26). This can be used to get lettered

2107− enumeration from array indices. To get uppercase

2108− letters, chain with `uppercase`.

2109−

2110−- `roman`: Converts textual values that can be

2111− read as an integer into lowercase roman numerials.

2112− This can be used to get lettered enumeration from array indices.

2113− To get uppercase roman, chain with `uppercase`.

2114−

2115−- `left n "leftborder" "rightborder"`: Renders a textual value

2116− in a block of width `n`, aligned to the left, with an optional

2117− left and right border. Has no effect on other values. This

2118− can be used to align material in tables. Widths are positive

2119− integers indicating the number of characters. Borders

2120− are strings inside double quotes; literal `"` and `\` characters

2121− must be backslash-escaped.

2122−

2123−- `right n "leftborder" "rightborder"`: Renders a textual value

2124− in a block of width `n`, aligned to the right, and has no

2125− effect on other values.

2126−

2127−- `center n "leftborder" "rightborder"`: Renders a textual

2128− value in a block of width `n`, aligned to the center, and has

2129− no effect on other values.

2130−

2131−

2132−## Variables

2133−

2134−### Metadata variables

2135−

2136−`title`, `author`, `date`

2137−: allow identification of basic aspects of the document. Included

2138− in PDF metadata through LaTeX and ConTeXt. These can be set

2139− through a [pandoc title block][Extension: `pandoc_title_block`],

2140− which allows for multiple authors, or through a

2141− [YAML metadata block][Extension: `yaml_metadata_block`]:

2142−

2143− ---

2144− author:

2145− - Aristotle

2146− - Peter Abelard

2147− ...

2148−

2149− Note that if you just want to set PDF or HTML metadata, without

2150− including a title block in the document itself, you can

2151− set the `title-meta`, `author-meta`, and `date-meta`

2152− variables. (By default these are set automatically, based

2153− on `title`, `author`, and `date`.) The page title in HTML

2154− is set by `pagetitle`, which is equal to `title` by default.

2155−

2156−`subtitle`

2157−: document subtitle, included in HTML, EPUB, LaTeX, ConTeXt, and docx

2158− documents

2159−

2160−`abstract`

2161−: document summary, included in LaTeX, ConTeXt, AsciiDoc, and docx

2162− documents

2163−

2164−`keywords`

2165−: list of keywords to be included in HTML, PDF, ODT, pptx, docx

2166− and AsciiDoc metadata; repeat as for `author`, above

2167−

2168−`subject`

2169−: document subject, included in ODT, PDF, docx and pptx metadata

2170−

2171−`description`

2172−: document description, included in ODT, docx and pptx metadata. Some

2173− applications show this as `Comments` metadata.

2174−

2175−`category`

2176−: document category, included in docx and pptx metadata

2177−

2178−Additionally,

2179−any root-level string metadata, not included in ODT, docx

2180−or pptx metadata is added as a *custom property*.

2181−The following [YAML] metadata block for instance:

2182−

2183− ---

2184− title: 'This is the title'

2185− subtitle: "This is the subtitle"

2186− author:

2187− - Author One

2188− - Author Two

2189− description: |

2190− This is a long

2191− description.

2192−

2193− It consists of two paragraphs

2194− ...

2195−

2196−will include `title`, `author` and `description` as standard document

2197−properties and `subtitle` as a custom property when converting to docx,

2198−ODT or pptx.

2199−

2200−### Language variables

2201−

2202−`lang`

2203−: identifies the main language of the document using IETF language

2204− tags (following the [BCP 47] standard), such as `en` or `en-GB`.

2205− The [Language subtag lookup] tool can look up or verify these tags.

2206− This affects most formats, and controls hyphenation in PDF output

2207− when using LaTeX (through [`babel`] and [`polyglossia`]) or ConTeXt.

2208−

2209− Use native pandoc [Divs and Spans] with the `lang` attribute to

2210− switch the language:

2211−

2212− ---

2213− lang: en-GB

2214− ...

2215−

2216− Text in the main document language (British English).

2217−

2218− ::: {lang=fr-CA}

2219− > Cette citation est écrite en français canadien.

2220− :::

2221−

2222− More text in English. ['Zitat auf Deutsch.']{lang=de}

2223−

2224−`dir`

2225−: the base script direction, either `rtl` (right-to-left)

2226− or `ltr` (left-to-right).

2227−

2228− For bidirectional documents, native pandoc `span`s and

2229− `div`s with the `dir` attribute (value `rtl` or `ltr`) can

2230− be used to override the base direction in some output

2231− formats. This may not always be necessary if the final

2232− renderer (e.g. the browser, when generating HTML) supports

2233− the [Unicode Bidirectional Algorithm].

2234−

2235− When using LaTeX for bidirectional documents, only the

2236− `xelatex` engine is fully supported (use

2237− `--pdf-engine=xelatex`).

2238−

2239−[BCP 47]: https://tools.ietf.org/html/bcp47

2240−[Unicode Bidirectional Algorithm]: https://www.w3.org/International/articles/inline-bidi-markup/uba-basics

2241−[Language subtag lookup]: https://r12a.github.io/app-subtags/

2242−

2243−### Variables for HTML

2244−

2245−`document-css`

2246−: Enables inclusion of most of the [CSS] in the `styles.html`

2247− [partial](#partials) (have a look with

2248− `pandoc --print-default-data-file=templates/styles.html`).

2249− Unless you use [`--css`](#option--css), this variable

2250− is set to `true` by default. You can disable it with

2251− e.g. `pandoc -M document-css=false`.

2252−

2253−`mainfont`

2254−: sets the CSS `font-family` property on the `html` element.

2255−

2256−`fontsize`

2257−: sets the base CSS `font-size`, which you'd usually set

2258− to e.g. `20px`, but it also accepts `pt`

2259− (12pt = 16px in most browsers).

2260−

2261−`fontcolor`

2262−: sets the CSS `color` property on the `html` element.

2263−

2264−`linkcolor`

2265−: sets the CSS `color` property on all links.

2266−

2267−`monofont`

2268−: sets the CSS `font-family` property on `code` elements.

2269−

2270−`monobackgroundcolor`

2271−: sets the CSS `background-color` property on `code` elements

2272− and adds extra padding.

2273−

2274−`linestretch`

2275−: sets the CSS `line-height` property on the `html` element,

2276− which is preferred to be unitless.

2277−

2278−`backgroundcolor`

2279−: sets the CSS `background-color` property on the `html` element.

2280−

2281−`margin-left`, `margin-right`, `margin-top`, `margin-bottom`

2282−: sets the corresponding CSS `padding` properties on the `body` element.

2283−

2284−To override or extend some [CSS] for just one document, include for example:

2285−

2286− ---

2287− header-includes: |

2288− <style>

2289− blockquote {

2290− font-style: italic;

2291− }

2292− tr.even {

2293− background-color: #f0f0f0;

2294− }

2295− td, th {

2296− padding: 0.5em 2em 0.5em 0.5em;

2297− }

2298− tbody {

2299− border-bottom: none;

2300− }

2301− </style>

2302− ---

2303−

2304−[CSS]: https://developer.mozilla.org/en-US/docs/Learn/CSS

2305−

2306−### Variables for HTML math

2307−

2308−`classoption`

2309−: when using [KaTeX](#option--katex), you can render display

2310−math equations flush left using [YAML metadata](#layout) or with

2311−`-M classoption=fleqn`.

2312−

2313−### Variables for HTML slides

2314−

2315−These affect HTML output when [producing slide shows with pandoc].

2316−

2317−`institute`

2318−: author affiliations: can be a list when there are multiple authors

2319−

2320−`revealjs-url`

2321−: base URL for reveal.js documents (defaults to

2322− `https://unpkg.com/reveal.js@^4/`)

2323−

2324−`s5-url`

2325−: base URL for S5 documents (defaults to `s5/default`)

2326−

2327−`slidy-url`

2328−: base URL for Slidy documents (defaults to

2329− `https://www.w3.org/Talks/Tools/Slidy2`)

2330−

2331−`slideous-url`

2332−: base URL for Slideous documents (defaults to `slideous`)

2333−

2334−`title-slide-attributes`

2335−: additional attributes for the title slide of reveal.js slide shows.

2336− See [background in reveal.js and beamer] for an example.

2337−

2338−All [reveal.js configuration options] are available as variables.

2339−To turn off boolean flags that default to true in reveal.js, use `0`.

2340−

2341−[reveal.js configuration options]: https://revealjs.com/config/

2342−

2343−### Variables for Beamer slides

2344−

2345−These variables change the appearance of PDF slides using [`beamer`].

2346−

2347−`aspectratio`

2348−: slide aspect ratio (`43` for 4:3 [default], `169` for 16:9,

2349− `1610` for 16:10, `149` for 14:9, `141` for 1.41:1, `54` for 5:4,

2350− `32` for 3:2)

2351−

2352−`beamerarticle`

2353−: produce an article from Beamer slides

2354−

2355−`beameroption`

2356−: add extra beamer option with `\setbeameroption{}`

2357−

2358−`institute`

2359−: author affiliations: can be a list when there are multiple authors

2360−

2361−`logo`

2362−: logo image for slides

2363−

2364−`navigation`

2365−: controls navigation symbols (default is `empty` for no navigation

2366− symbols; other valid values are `frame`, `vertical`, and `horizontal`)

2367−

2368−`section-titles`

2369−: enables "title pages" for new sections (default is true)

2370−

2371−`theme`, `colortheme`, `fonttheme`, `innertheme`, `outertheme`

2372−: beamer themes

2373−

2374−`themeoptions`

2375−: options for LaTeX beamer themes (a list).

2376−

2377−`titlegraphic`

2378−: image for title slide

2379−

2380−### Variables for PowerPoint

2381−

2382−These variables control the visual aspects of a slide show that

2383−are not easily controlled via templates.

2384−

2385−`monofont`

2386−: font to use for code.

2387−

2388−### Variables for LaTeX

2389−

2390−Pandoc uses these variables when [creating a PDF] with a LaTeX engine.

2391−

2392−#### Layout

2393−

2394−`block-headings`

2395−: make `\paragraph` and `\subparagraph` (fourth- and

2396− fifth-level headings, or fifth- and sixth-level with book

2397− classes) free-standing rather than run-in; requires further

2398− formatting to distinguish from `\subsubsection` (third- or

2399− fourth-level headings). Instead of using this option,

2400− [KOMA-Script] can adjust headings more extensively:

2401−

2402− ---

2403− documentclass: scrartcl

2404− header-includes: |

2405− \RedeclareSectionCommand[

2406− beforeskip=-10pt plus -2pt minus -1pt,

2407− afterskip=1sp plus -1sp minus 1sp,

2408− font=\normalfont\itshape]{paragraph}

2409− \RedeclareSectionCommand[

2410− beforeskip=-10pt plus -2pt minus -1pt,

2411− afterskip=1sp plus -1sp minus 1sp,

2412− font=\normalfont\scshape,

2413− indent=0pt]{subparagraph}

2414− ...

2415−

2416−`classoption`

2417−: option for document class, e.g. `oneside`; repeat for multiple options:

2418−

2419− ---

2420− classoption:

2421− - twocolumn

2422− - landscape

2423− ...

2424−

2425−`documentclass`

2426−: document class: usually one of the standard classes,

2427− [`article`], [`book`], and [`report`]; the [KOMA-Script]

2428− equivalents, `scrartcl`, `scrbook`, and `scrreprt`, which

2429− default to smaller margins; or [`memoir`]

2430−

2431−`geometry`

2432−: option for [`geometry`] package, e.g. `margin=1in`;

2433− repeat for multiple options:

2434−

2435− ---

2436− geometry:

2437− - top=30mm

2438− - left=20mm

2439− - heightrounded

2440− ...

2441−

2442−`hyperrefoptions`

2443−: option for [`hyperref`] package, e.g. `linktoc=all`;

2444− repeat for multiple options:

2445−

2446− ---

2447− hyperrefoptions:

2448− - linktoc=all

2449− - pdfwindowui

2450− - pdfpagemode=FullScreen

2451− ...

2452−

2453−`indent`

2454−: if true, pandoc will use document class settings for

2455− indentation (the default LaTeX template otherwise removes

2456− indentation and adds space between paragraphs)

2457−

2458−`linestretch`

2459−: adjusts line spacing using the [`setspace`]

2460− package, e.g. `1.25`, `1.5`

2461−

2462−`margin-left`, `margin-right`, `margin-top`, `margin-bottom`

2463−: sets margins if `geometry` is not used (otherwise `geometry`

2464− overrides these)

2465−

2466−`pagestyle`

2467−: control `\pagestyle{}`: the default article class

2468− supports `plain` (default), `empty` (no running heads or page numbers),

2469− and `headings` (section titles in running heads)

2470−

2471−`papersize`

2472−: paper size, e.g. `letter`, `a4`

2473−

2474−`secnumdepth`

2475−: numbering depth for sections (with `--number-sections` option

2476− or `numbersections` variable)

2477−

2478−#### Fonts

2479−

2480−`fontenc`

2481−: allows font encoding to be specified through `fontenc` package (with

2482− `pdflatex`); default is `T1` (see [LaTeX font encodings guide])

2483−

2484−`fontfamily`

2485−: font package for use with `pdflatex`:

2486− [TeX Live] includes many options, documented in the [LaTeX Font Catalogue].

2487− The default is [Latin Modern][`lm`].

2488−

2489−`fontfamilyoptions`

2490−: options for package used as `fontfamily`; repeat for multiple options.

2491− For example, to use the Libertine font with proportional lowercase

2492− (old-style) figures through the [`libertinus`] package:

2493−

2494− ---

2495− fontfamily: libertinus

2496− fontfamilyoptions:

2497− - osf

2498− - p

2499− ...

2500−

2501−`fontsize`

2502−: font size for body text. The standard classes allow 10pt, 11pt, and

2503− 12pt. To use another size, set `documentclass` to one of

2504− the [KOMA-Script] classes, such as `scrartcl` or `scrbook`.

2505−

2506−`mainfont`, `sansfont`, `monofont`, `mathfont`, `CJKmainfont`

2507−: font families for use with `xelatex` or

2508− `lualatex`: take the name of any system font, using the

2509− [`fontspec`] package. `CJKmainfont` uses the [`xecjk`] package.

2510−

2511−`mainfontoptions`, `sansfontoptions`, `monofontoptions`, `mathfontoptions`, `CJKoptions`

2512−: options to use with `mainfont`, `sansfont`, `monofont`, `mathfont`,

2513− `CJKmainfont` in `xelatex` and `lualatex`. Allow for any

2514− choices available through [`fontspec`]; repeat for multiple

2515− options. For example, to use the [TeX Gyre] version of

2516− Palatino with lowercase figures:

2517−

2518− ---

2519− mainfont: TeX Gyre Pagella

2520− mainfontoptions:

2521− - Numbers=Lowercase

2522− - Numbers=Proportional

2523− ...

2524−

2525−`microtypeoptions`

2526−: options to pass to the microtype package

2527−

2528−#### Links

2529−

2530−`colorlinks`

2531−: add color to link text; automatically enabled if any of

2532− `linkcolor`, `filecolor`, `citecolor`, `urlcolor`, or `toccolor` are set

2533−

2534−`linkcolor`, `filecolor`, `citecolor`, `urlcolor`, `toccolor`

2535−: color for internal links, external links, citation links, linked

2536− URLs, and links in table of contents, respectively: uses options

2537− allowed by [`xcolor`], including the `dvipsnames`, `svgnames`, and

2538− `x11names` lists

2539−

2540−`links-as-notes`

2541−: causes links to be printed as footnotes

2542−

2543−#### Front matter

2544−

2545−`lof`, `lot`

2546−: include list of figures, list of tables

2547−

2548−`thanks`

2549−: contents of acknowledgments footnote after document title

2550−

2551−`toc`

2552−: include table of contents (can also be set using

2553− `--toc/--table-of-contents`)

2554−

2555−`toc-depth`

2556−: level of section to include in table of contents

2557−

2558−#### BibLaTeX Bibliographies

2559−

2560−These variables function when using BibLaTeX for [citation rendering].

2561−

2562−`biblatexoptions`

2563−: list of options for biblatex

2564−

2565−`biblio-style`

2566−: bibliography style, when used with `--natbib` and `--biblatex`.

2567−

2568−`biblio-title`

2569−: bibliography title, when used with `--natbib` and `--biblatex`.

2570−

2571−`bibliography`

2572−: bibliography to use for resolving references

2573−

2574−`natbiboptions`

2575−: list of options for natbib

2576−

2577−[KOMA-Script]: https://ctan.org/pkg/koma-script

2578−[LaTeX Font Catalogue]: https://tug.org/FontCatalogue/

2579−[LaTeX font encodings guide]: https://ctan.org/pkg/encguide

2580−[TeX Gyre]: http://www.gust.org.pl/projects/e-foundry/tex-gyre

2581−[`article`]: https://ctan.org/pkg/article

2582−[`book`]: https://ctan.org/pkg/book

2583−[`libertinus`]: https://ctan.org/pkg/libertinus

2584−[`memoir`]: https://ctan.org/pkg/memoir

2585−[`report`]: https://ctan.org/pkg/report

2586−

2587−### Variables for ConTeXt

2588−

2589−Pandoc uses these variables when [creating a PDF] with ConTeXt.

2590−

2591−`fontsize`

2592−: font size for body text (e.g. `10pt`, `12pt`)

2593−

2594−`headertext`, `footertext`

2595−: text to be placed in running header or footer (see [ConTeXt Headers and

2596− Footers]); repeat up to four times for different placement

2597−

2598−`indenting`

2599−: controls indentation of paragraphs, e.g. `yes,small,next` (see

2600− [ConTeXt Indentation]); repeat for multiple options

2601−

2602−`interlinespace`

2603−: adjusts line spacing, e.g. `4ex` (using [`setupinterlinespace`]);

2604− repeat for multiple options

2605−

2606−`layout`

2607−: options for page margins and text arrangement (see [ConTeXt Layout]);

2608− repeat for multiple options

2609−

2610−`linkcolor`, `contrastcolor`

2611−: color for links outside and inside a page, e.g. `red`, `blue` (see

2612− [ConTeXt Color])

2613−

2614−`linkstyle`

2615−: typeface style for links, e.g. `normal`, `bold`, `slanted`, `boldslanted`,

2616− `type`, `cap`, `small`

2617−

2618−`lof`, `lot`

2619−: include list of figures, list of tables

2620−

2621−`mainfont`, `sansfont`, `monofont`, `mathfont`

2622−: font families: take the name of any system font (see

2623− [ConTeXt Font Switching])

2624−

2625−`margin-left`, `margin-right`, `margin-top`, `margin-bottom`

2626−: sets margins, if `layout` is not used (otherwise `layout`

2627− overrides these)

2628−

2629−`pagenumbering`

2630−: page number style and location (using [`setuppagenumbering`]);

2631− repeat for multiple options

2632−

2633−`papersize`

2634−: paper size, e.g. `letter`, `A4`, `landscape` (see [ConTeXt Paper Setup]);

2635− repeat for multiple options

2636−

2637−`pdfa`

2638−: adds to the preamble the setup necessary to generate PDF/A

2639− of the type specified, e.g. `1a:2005`, `2a`. If no type is

2640− specified (i.e. the value is set to True, by e.g.

2641− `--metadata=pdfa` or `pdfa: true` in a YAML metadata block),

2642− `1b:2005` will be used as default, for reasons of backwards

2643− compatibility. Using `--variable=pdfa` without specified value

2644− is not supported. To successfully generate PDF/A the required

2645− ICC color profiles have to be available and the content and all

2646− included files (such as images) have to be standard conforming.

2647− The ICC profiles and output intent may be specified using the

2648− variables `pdfaiccprofile` and `pdfaintent`. See also [ConTeXt

2649− PDFA] for more details.

2650−

2651−`pdfaiccprofile`

2652−: when used in conjunction with `pdfa`, specifies the ICC profile to use

2653− in the PDF, e.g. `default.cmyk`. If left unspecified, `sRGB.icc` is

2654− used as default. May be repeated to include multiple profiles. Note that

2655− the profiles have to be available on the system. They can be obtained

2656− from [ConTeXt ICC Profiles].

2657−

2658−`pdfaintent`

2659−: when used in conjunction with `pdfa`, specifies the output intent for

2660− the colors, e.g. `ISO coated v2 300\letterpercent\space (ECI)`

2661− If left unspecified, `sRGB IEC61966-2.1` is used as default.

2662−

2663−`toc`

2664−: include table of contents (can also be set using

2665− `--toc/--table-of-contents`)

2666−

2667−`whitespace`

2668−: spacing between paragraphs, e.g. `none`, `small` (using

2669− [`setupwhitespace`])

2670−

2671−`includesource`

2672−: include all source documents as file attachments in the PDF file

2673−

2674−[ConTeXt Paper Setup]: https://wiki.contextgarden.net/PaperSetup

2675−[ConTeXt Layout]: https://wiki.contextgarden.net/Layout

2676−[ConTeXt Font Switching]: https://wiki.contextgarden.net/Font_Switching

2677−[ConTeXt Color]: https://wiki.contextgarden.net/Color

2678−[ConTeXt Headers and Footers]: https://wiki.contextgarden.net/Headers_and_Footers

2679−[ConTeXt Indentation]: https://wiki.contextgarden.net/Indentation

2680−[ConTeXt ICC Profiles]: https://wiki.contextgarden.net/PDFX#ICC_profiles

2681−[ConTeXt PDFA]: https://wiki.contextgarden.net/PDF/A

2682−[`setupwhitespace`]: https://wiki.contextgarden.net/Command/setupwhitespace

2683−[`setupinterlinespace`]: https://wiki.contextgarden.net/Command/setupinterlinespace

2684−[`setuppagenumbering`]: https://wiki.contextgarden.net/Command/setuppagenumbering

2685−

2686−### Variables for `wkhtmltopdf`

2687−

2688−Pandoc uses these variables when [creating a PDF] with [`wkhtmltopdf`].

2689−The `--css` option also affects the output.

2690−

2691−`footer-html`, `header-html`

2692−: add information to the header and footer

2693−

2694−`margin-left`, `margin-right`, `margin-top`, `margin-bottom`

2695−: set the page margins

2696−

2697−`papersize`

2698−: sets the PDF paper size

2699−

2700−### Variables for man pages

2701−

2702−`adjusting`

2703−: adjusts text to left (`l`), right (`r`), center (`c`),

2704− or both (`b`) margins

2705−

2706−`footer`

2707−: footer in man pages

2708−

2709−`header`

2710−: header in man pages

2711−

2712−`hyphenate`

2713−: if `true` (the default), hyphenation will be used

2714−

2715−`section`

2716−: section number in man pages

2717−

2718−### Variables for ms

2719−

2720−`fontfamily`

2721−: font family (e.g. `T` or `P`)

2722−

2723−`indent`

2724−: paragraph indent (e.g. `2m`)

2725−

2726−`lineheight`

2727−: line height (e.g. `12p`)

2728−

2729−`pointsize`

2730−: point size (e.g. `10p`)

2731−

2732−### Variables set automatically

2733−

2734−Pandoc sets these variables automatically in response to [options] or

2735−document contents; users can also modify them. These vary depending

2736−on the output format, and include the following:

2737−

2738−`body`

2739−: body of document

2740−

2741−`date-meta`

2742−: the `date` variable converted to ISO 8601 YYYY-MM-DD,

2743− included in all HTML based formats (dzslides, epub,

2744− html, html4, html5, revealjs, s5, slideous, slidy).

2745− The recognized formats for `date` are: `mm/dd/yyyy`,

2746− `mm/dd/yy`, `yyyy-mm-dd` (ISO 8601), `dd MM yyyy`

2747− (e.g. either `02 Apr 2018` or `02 April 2018`),

2748− `MM dd, yyyy` (e.g. `Apr. 02, 2018` or `April 02, 2018),

2749− `yyyy[mm[dd]]]` (e.g. `20180402, `201804` or `2018`).

2750−

2751−`header-includes`

2752−: contents specified by `-H/--include-in-header` (may have multiple

2753− values)

2754−

2755−`include-before`

2756−: contents specified by `-B/--include-before-body` (may have

2757− multiple values)

2758−

2759−`include-after`

2760−: contents specified by `-A/--include-after-body` (may have

2761− multiple values)

2762−

2763−`meta-json`

2764−: JSON representation of all of the document's metadata. Field

2765− values are transformed to the selected output format.

2766−

2767−`numbersections`

2768−: non-null value if `-N/--number-sections` was specified

2769−

2770−`sourcefile`, `outputfile`

2771−: source and destination filenames, as given on the command line.

2772− `sourcefile` can also be a list if input comes from multiple files,

2773− or empty if input is from stdin. You can use the following snippet in

2774− your template to distinguish them:

2775−

2776− $if(sourcefile)$

2777− $for(sourcefile)$

2778− $sourcefile$

2779− $endfor$

2780− $else$

2781− (stdin)

2782− $endif$

2783−

2784− Similarly, `outputfile` can be `-` if output goes to the terminal.

2785−

2786− If you need absolute paths, use e.g. `$curdir$/$sourcefile$`.

2787−

2788−`curdir`

2789−: working directory from which pandoc is run.

2790−

2791−`toc`

2792−: non-null value if `--toc/--table-of-contents` was specified

2793−

2794−`toc-title`

2795−: title of table of contents (works only with EPUB,

2796− HTML, opendocument, odt, docx, pptx, beamer, LaTeX)

2797−

2798−[pandoc-templates]: https://github.com/jgm/pandoc-templates

2799−

2800−# Extensions

2801−

2802−The behavior of some of the readers and writers can be adjusted by

2803−enabling or disabling various extensions.

2804−

2805−An extension can be enabled by adding `+EXTENSION`

2806−to the format name and disabled by adding `-EXTENSION`. For example,

2807−`--from markdown_strict+footnotes` is strict Markdown with footnotes

2808−enabled, while `--from markdown-footnotes-pipe_tables` is pandoc's

2809−Markdown without footnotes or pipe tables.

2810−

2811−The markdown reader and writer make by far the most use of extensions.

2812−Extensions only used by them are therefore covered in the

2813−section [Pandoc's Markdown] below (See [Markdown variants] for

2814−`commonmark` and `gfm`.) In the following, extensions that also work

2815−for other formats are covered.

2816−

2817−Note that markdown extensions added to the `ipynb` format

2818−affect Markdown cells in Jupyter notebooks (as do command-line

2819−options like `--atx-headers`).

2820−

2821−## Typography

2822−

2823−#### Extension: `smart` ####

2824−

2825−Interpret straight quotes as curly quotes, `---` as em-dashes,

2826−`--` as en-dashes, and `...` as ellipses. Nonbreaking spaces are

2827−inserted after certain abbreviations, such as "Mr."

2828−

2829−This extension can be enabled/disabled for the following formats:

2830−

2831−input formats

2832−: `markdown`, `commonmark`, `latex`, `mediawiki`, `org`, `rst`, `twiki`

2833−

2834−output formats

2835−: `markdown`, `latex`, `context`, `rst`

2836−

2837−enabled by default in

2838−: `markdown`, `latex`, `context` (both input and output)

2839−

2840−Note: If you are *writing* Markdown, then the `smart` extension

2841−has the reverse effect: what would have been curly quotes comes

2842−out straight.

2843−

2844−In LaTeX, `smart` means to use the standard TeX ligatures

2845−for quotation marks (` `` ` and ` '' ` for double quotes,

2846−`` ` `` and `` ' `` for single quotes) and dashes (`--` for

2847−en-dash and `---` for em-dash). If `smart` is disabled,

2848−then in reading LaTeX pandoc will parse these characters

2849−literally. In writing LaTeX, enabling `smart` tells pandoc

2850−to use the ligatures when possible; if `smart` is disabled

2851−pandoc will use unicode quotation mark and dash characters.

2852−

2853−## Headings and sections

2854−

2855−#### Extension: `auto_identifiers` ####

2856−

2857−A heading without an explicitly specified identifier will be

2858−automatically assigned a unique identifier based on the heading text.

2859−

2860−This extension can be enabled/disabled for the following formats:

2861−

2862−input formats

2863−: `markdown`, `latex`, `rst`, `mediawiki`, `textile`

2864−

2865−output formats

2866−: `markdown`, `muse`

2867−

2868−enabled by default in

2869−: `markdown`, `muse`

2870−

2871−The default algorithm used to derive the identifier from the

2872−heading text is:

2873−

2874− - Remove all formatting, links, etc.

2875− - Remove all footnotes.

2876− - Remove all non-alphanumeric characters,

2877− except underscores, hyphens, and periods.

2878− - Replace all spaces and newlines with hyphens.

2879− - Convert all alphabetic characters to lowercase.

2880− - Remove everything up to the first letter (identifiers may

2881− not begin with a number or punctuation mark).

2882− - If nothing is left after this, use the identifier `section`.

2883−

2884−Thus, for example,

2885−

2886− Heading Identifier

2887− ------------------------------- ----------------------------

2888− `Heading identifiers in HTML` `heading-identifiers-in-html`

2889− `Maître d'hôtel` `maître-dhôtel`

2890− `*Dogs*?--in *my* house?` `dogs--in-my-house`

2891− `[HTML], [S5], or [RTF]?` `html-s5-or-rtf`

2892− `3. Applications` `applications`

2893− `33` `section`

2894−

2895−These rules should, in most cases, allow one to determine the identifier

2896−from the heading text. The exception is when several headings have the

2897−same text; in this case, the first will get an identifier as described

2898−above; the second will get the same identifier with `-1` appended; the

2899−third with `-2`; and so on.

2900−

2901−(However, a different algorithm is used if

2902−`gfm_auto_identifiers` is enabled; see below.)

2903−

2904−These identifiers are used to provide link targets in the table of

2905−contents generated by the `--toc|--table-of-contents` option. They

2906−also make it easy to provide links from one section of a document to

2907−another. A link to this section, for example, might look like this:

2908−

2909− See the section on

2910− [heading identifiers](#heading-identifiers-in-html-latex-and-context).

2911−

2912−Note, however, that this method of providing links to sections works

2913−only in HTML, LaTeX, and ConTeXt formats.

2914−

2915−If the `--section-divs` option is specified, then each section will

2916−be wrapped in a `section` (or a `div`, if `html4` was specified),

2917−and the identifier will be attached to the enclosing `<section>`

2918−(or `<div>`) tag rather than the heading itself. This allows entire

2919−sections to be manipulated using JavaScript or treated differently in

2920−CSS.

2921−

2922−#### Extension: `ascii_identifiers` ####

2923−

2924−Causes the identifiers produced by `auto_identifiers` to be pure ASCII.

2925−Accents are stripped off of accented Latin letters, and non-Latin

2926−letters are omitted.

2927−

2928−#### Extension: `gfm_auto_identifiers` ####

2929−

2930−Changes the algorithm used by `auto_identifiers` to conform to

2931−GitHub's method. Spaces are converted to dashes (`-`),

2932−uppercase characters to lowercase characters, and punctuation

2933−characters other than `-` and `_` are removed.

2934−Emojis are replaced by their names.

2935−

2936−## Math Input

2937−

2938−The extensions [`tex_math_dollars`](#extension-tex_math_dollars),

2939−[`tex_math_single_backslash`](#extension-tex_math_single_backslash), and

2940−[`tex_math_double_backslash`](#extension-tex_math_double_backslash)

2941−are described in the section about Pandoc's Markdown.

2942−

2943−However, they can also be used with HTML input. This is handy for

2944−reading web pages formatted using MathJax, for example.

2945−

2946−## Raw HTML/TeX

2947−

2948−The following extensions are described in more detail in

2949−their respective sections of [Pandoc's Markdown]:

2950−

2951−- [`raw_html`](#extension-raw_html) allows HTML elements which

2952− are not representable in pandoc's AST to be parsed as raw HTML.

2953− By default, this is disabled for HTML input.

2954−

2955−- [`raw_tex`](#extension-raw_tex) allows raw LaTeX, TeX, and ConTeXt

2956− to be included in a document. This extension can be enabled/disabled

2957− for the following formats (in addition to `markdown`):

2958−

2959− input formats

2960− : `latex`, `textile`, `html` (environments, `\ref`, and

2961− `\eqref` only), `ipynb`

2962−

2963− output formats

2964− : `textile`, `commonmark`

2965−

2966− Note: as applied to `ipynb`, `raw_html` and `raw_tex` affect not

2967− only raw TeX in markdown cells, but data with mime type

2968− `text/html` in output cells. Since the `ipynb` reader attempts

2969− to preserve the richest possible outputs when several options

2970− are given, you will get best results if you disable `raw_html`

2971− and `raw_tex` when converting to formats like `docx` which don't

2972− allow raw `html` or `tex`.

2973−

2974−- [`native_divs`](#extension-native_divs) causes HTML `div`

2975− elements to be parsed as native pandoc Div blocks.

2976− If you want them to be parsed as raw HTML, use

2977− `-f html-native_divs+raw_html`.

2978−

2979−- [`native_spans`](#extension-native_spans) causes HTML `span`

2980− elements to be parsed as native pandoc Span inlines.

2981− If you want them to be parsed as raw HTML, use

2982− `-f html-native_spans+raw_html`. If you want to drop all

2983− `div`s and `span`s when converting HTML to Markdown, you

2984− can use `pandoc -f html-native_divs-native_spans -t markdown`.

2985−

2986−## Literate Haskell support

2987−

2988−#### Extension: `literate_haskell` ####

2989−

2990−Treat the document as literate Haskell source.

2991−

2992−This extension can be enabled/disabled for the following formats:

2993−

2994−input formats

2995−: `markdown`, `rst`, `latex`

2996−

2997−output formats

2998−: `markdown`, `rst`, `latex`, `html`

2999−

3000−If you append `+lhs` (or `+literate_haskell`) to one of the formats

3001−above, pandoc will treat the document as literate Haskell source.

3002−This means that

3003−

3004− - In Markdown input, "bird track" sections will be parsed as Haskell

3005− code rather than block quotations. Text between `\begin{code}`

3006− and `\end{code}` will also be treated as Haskell code. For

3007− ATX-style headings the character '=' will be used instead of '#'.

3008−

3009− - In Markdown output, code blocks with classes `haskell` and `literate`

3010− will be rendered using bird tracks, and block quotations will be

3011− indented one space, so they will not be treated as Haskell code.

3012− In addition, headings will be rendered setext-style (with underlines)

3013− rather than ATX-style (with '#' characters). (This is because ghc

3014− treats '#' characters in column 1 as introducing line numbers.)

3015−

3016− - In restructured text input, "bird track" sections will be parsed

3017− as Haskell code.

3018−

3019− - In restructured text output, code blocks with class `haskell` will

3020− be rendered using bird tracks.

3021−

3022− - In LaTeX input, text in `code` environments will be parsed as

3023− Haskell code.

3024−

3025− - In LaTeX output, code blocks with class `haskell` will be rendered

3026− inside `code` environments.

3027−

3028− - In HTML output, code blocks with class `haskell` will be rendered

3029− with class `literatehaskell` and bird tracks.

3030−

3031−Examples:

3032−

3033− pandoc -f markdown+lhs -t html

3034−

3035−reads literate Haskell source formatted with Markdown conventions and writes

3036−ordinary HTML (without bird tracks).

3037−

3038− pandoc -f markdown+lhs -t html+lhs

3039−

3040−writes HTML with the Haskell code in bird tracks, so it can be copied

3041−and pasted as literate Haskell source.

3042−

3043−Note that GHC expects the bird tracks in the first column, so indented

3044−literate code blocks (e.g. inside an itemized environment) will not be

3045−picked up by the Haskell compiler.

3046−

3047−## Other extensions

3048−

3049−#### Extension: `empty_paragraphs` ####

3050−

3051−Allows empty paragraphs. By default empty paragraphs are

3052−omitted.

3053−

3054−This extension can be enabled/disabled for the following formats:

3055−

3056−input formats

3057−: `docx`, `html`

3058−

3059−output formats

3060−: `docx`, `odt`, `opendocument`, `html`

3061−

3062−#### Extension: `native_numbering` ####

3063−

3064−Enables native numbering of figures and tables. Enumeration

3065−starts at 1.

3066−

3067−This extension can be enabled/disabled for the following formats:

3068−

3069−output formats

3070−: `odt`, `opendocument`

3071−

3072−#### Extension: `xrefs_name` ####

3073−

3074−Links to headings, figures and tables inside the document are

3075−substituted with cross-references that will use the name or caption

3076−of the referenced item. The original link text is replaced once

3077−the generated document is refreshed. This extension can be combined

3078−with `xrefs_number` in which case numbers will appear before the

3079−name.

3080−

3081−Text in cross-references is only made consistent with the referenced

3082−item once the document has been refreshed.

3083−

3084−This extension can be enabled/disabled for the following formats:

3085−

3086−output formats

3087−: `odt`, `opendocument`

3088−

3089−#### Extension: `xrefs_number` ####

3090−

3091−Links to headings, figures and tables inside the document are

3092−substituted with cross-references that will use the number

3093−of the referenced item. The original link text is discarded.

3094−This extension can be combined with `xrefs_name` in which case

3095−the name or caption numbers will appear after the number.

3096−

3097−For the `xrefs_number` to be useful heading numbers must be enabled

3098−in the generated document, also table and figure captions must be enabled

3099−using for example the `native_numbering` extension.

3100−

3101−Numbers in cross-references are only visible in the final document once

3102−it has been refreshed.

3103−

3104−This extension can be enabled/disabled for the following formats:

3105−

3106−output formats

3107−: `odt`, `opendocument`

3108−

3109−#### Extension: `styles` #### {#ext-styles}

3110−

3111−When converting from docx, read all docx styles as divs (for

3112−paragraph styles) and spans (for character styles) regardless

3113−of whether pandoc understands the meaning of these styles.

3114−This can be used with [docx custom styles](#custom-styles).

3115−Disabled by default.

3116−

3117−input formats

3118−: `docx`

3119−

3120−#### Extension: `amuse` ####

3121−

3122−In the `muse` input format, this enables Text::Amuse

3123−extensions to Emacs Muse markup.

3124−

3125−#### Extension: `raw_markdown` ####

3126−

3127−In the `ipynb` input format, this causes Markdown cells

3128−to be included as raw Markdown blocks (allowing lossless

3129−round-tripping) rather than being parsed. Use this only

3130−when you are targeting `ipynb` or a markdown-based

3131−output format.

3132−

3133−#### Extension: `citations` {#org-citations}

3134−

3135−Some aspects of [Pandoc's Markdown citation syntax](#citations)

3136−are also accepted in `org` input.

3137−

3138−#### Extension: `element_citations` ####

3139−

3140−In the `jats` output formats, this causes reference items to

3141−be replaced with `<element-citation>` elements. These

3142−elements are not influenced by CSL styles, but all information

3143−on the item is included in tags.

3144−

3145−#### Extension: `ntb` ####

3146−

3147−In the `context` output format this enables the use of [Natural Tables

3148−(TABLE)](https://wiki.contextgarden.net/TABLE) instead of the default

3149−[Extreme Tables (xtables)](https://wiki.contextgarden.net/xtables).

3150−Natural tables allow more fine-grained global customization but come

3151−at a performance penalty compared to extreme tables.

3152−

3153−

3154−# Pandoc's Markdown

3155−

3156−Pandoc understands an extended and slightly revised version of

3157−John Gruber's [Markdown] syntax. This document explains the syntax,

3158−noting differences from standard Markdown. Except where noted, these

3159−differences can be suppressed by using the `markdown_strict` format instead

3160−of `markdown`. Extensions can be enabled or disabled to specify the

3161−behavior more granularly. They are described in the following. See also

3162−[Extensions] above, for extensions that work also on other formats.

3163−

3164−## Philosophy

3165−

3166−Markdown is designed to be easy to write, and, even more importantly,

3167−easy to read:

3168−

3169−> A Markdown-formatted document should be publishable as-is, as plain

3170−> text, without looking like it's been marked up with tags or formatting

3171−> instructions.

3172−> -- [John Gruber](https://daringfireball.net/projects/markdown/syntax#philosophy)

3173−

3174−This principle has guided pandoc's decisions in finding syntax for

3175−tables, footnotes, and other extensions.

3176−

3177−There is, however, one respect in which pandoc's aims are different

3178−from the original aims of Markdown. Whereas Markdown was originally

3179−designed with HTML generation in mind, pandoc is designed for multiple

3180−output formats. Thus, while pandoc allows the embedding of raw HTML,

3181−it discourages it, and provides other, non-HTMLish ways of representing

3182−important document elements like definition lists, tables, mathematics, and

3183−footnotes.

3184−

3185−## Paragraphs

3186−

3187−A paragraph is one or more lines of text followed by one or more blank lines.

3188−Newlines are treated as spaces, so you can reflow your paragraphs as you like.

3189−If you need a hard line break, put two or more spaces at the end of a line.

3190−

3191−#### Extension: `escaped_line_breaks` ####

3192−

3193−A backslash followed by a newline is also a hard line break.

3194−Note: in multiline and grid table cells, this is the only way

3195−to create a hard line break, since trailing spaces in the cells

3196−are ignored.

3197−

3198−## Headings

3199−

3200−There are two kinds of headings: Setext and ATX.

3201−

3202−### Setext-style headings ###

3203−

3204−A setext-style heading is a line of text "underlined" with a row of `=` signs

3205−(for a level-one heading) or `-` signs (for a level-two heading):

3206−

3207− A level-one heading

3208− ===================

3209−

3210− A level-two heading

3211− -------------------

3212−

3213−The heading text can contain inline formatting, such as emphasis (see

3214−[Inline formatting], below).

3215−

3216−

3217−### ATX-style headings ###

3218−

3219−An ATX-style heading consists of one to six `#` signs and a line of

3220−text, optionally followed by any number of `#` signs. The number of

3221−`#` signs at the beginning of the line is the heading level:

3222−

3223− ## A level-two heading

3224−

3225− ### A level-three heading ###

3226−

3227−As with setext-style headings, the heading text can contain formatting:

3228−

3229− # A level-one heading with a [link](/url) and *emphasis*

3230−

3231−#### Extension: `blank_before_header` ####

3232−

3233−Standard Markdown syntax does not require a blank line before a heading.

3234−Pandoc does require this (except, of course, at the beginning of the

3235−document). The reason for the requirement is that it is all too easy for a

3236−`#` to end up at the beginning of a line by accident (perhaps through line

3237−wrapping). Consider, for example:

3238−

3239− I like several of their flavors of ice cream:

3240− #22, for example, and #5.

3241−

3242−#### Extension: `space_in_atx_header` ####

3243−

3244−Many Markdown implementations do not require a space between the

3245−opening `#`s of an ATX heading and the heading text, so that

3246−`#5 bolt` and `#hashtag` count as headings. With this extension,

3247−pandoc does require the space.

3248−

3249−### Heading identifiers ###

3250−

3251−See also the [`auto_identifiers`

3252−extension](#extension-auto_identifiers) above.

3253−

3254−#### Extension: `header_attributes` ####

3255−

3256−Headings can be assigned attributes using this syntax at the end

3257−of the line containing the heading text:

3258−

3259− {#identifier .class .class key=value key=value}

3260−

3261−Thus, for example, the following headings will all be assigned the identifier

3262−`foo`:

3263−

3264− # My heading {#foo}

3265−

3266− ## My heading ## {#foo}

3267−

3268− My other heading {#foo}

3269− ---------------

3270−

3271−(This syntax is compatible with [PHP Markdown Extra].)

3272−

3273−Note that although this syntax allows assignment of classes and key/value

3274−attributes, writers generally don't use all of this information. Identifiers,

3275−classes, and key/value attributes are used in HTML and HTML-based formats such

3276−as EPUB and slidy. Identifiers are used for labels and link anchors in the

3277−LaTeX, ConTeXt, Textile, Jira markup, and AsciiDoc writers.

3278−

3279−Headings with the class `unnumbered` will not be numbered, even if

3280−`--number-sections` is specified. A single hyphen (`-`) in an attribute

3281−context is equivalent to `.unnumbered`, and preferable in non-English

3282−documents. So,

3283−

3284− # My heading {-}

3285−

3286−is just the same as

3287−

3288− # My heading {.unnumbered}

3289−

3290−If the `unlisted` class is present in addition to `unnumbered`,

3291−the heading will not be included in a table of contents.

3292−(Currently this feature is only implemented for certain

3293−formats: those based on LaTeX and HTML, PowerPoint, and RTF.)

3294−

3295−#### Extension: `implicit_header_references` ####

3296−

3297−Pandoc behaves as if reference links have been defined for each heading.

3298−So, to link to a heading

3299−

3300− # Heading identifiers in HTML

3301−

3302−you can simply write

3303−

3304− [Heading identifiers in HTML]

3305−

3306−or

3307−

3308− [Heading identifiers in HTML][]

3309−

3310−or

3311−

3312− [the section on heading identifiers][heading identifiers in

3313− HTML]

3314−

3315−instead of giving the identifier explicitly:

3316−

3317− [Heading identifiers in HTML](#heading-identifiers-in-html)

3318−

3319−If there are multiple headings with identical text, the corresponding

3320−reference will link to the first one only, and you will need to use explicit

3321−links to link to the others, as described above.

3322−

3323−Like regular reference links, these references are case-insensitive.

3324−

3325−Explicit link reference definitions always take priority over

3326−implicit heading references. So, in the following example, the

3327−link will point to `bar`, not to `#foo`:

3328−

3329− # Foo

3330−

3331− [foo]: bar

3332−

3333− See [foo]

3334−

3335−## Block quotations

3336−

3337−Markdown uses email conventions for quoting blocks of text.

3338−A block quotation is one or more paragraphs or other block elements

3339−(such as lists or headings), with each line preceded by a `>` character

3340−and an optional space. (The `>` need not start at the left margin, but

3341−it should not be indented more than three spaces.)

3342−

3343− > This is a block quote. This

3344− > paragraph has two lines.

3345− >

3346− > 1. This is a list inside a block quote.

3347− > 2. Second item.

3348−

3349−A "lazy" form, which requires the `>` character only on the first

3350−line of each block, is also allowed:

3351−

3352− > This is a block quote. This

3353− paragraph has two lines.

3354−

3355− > 1. This is a list inside a block quote.

3356− 2. Second item.

3357−

3358−Among the block elements that can be contained in a block quote are

3359−other block quotes. That is, block quotes can be nested:

3360−

3361− > This is a block quote.

3362− >

3363− > > A block quote within a block quote.

3364−

3365−If the `>` character is followed by an optional space, that space

3366−will be considered part of the block quote marker and not part of

3367−the indentation of the contents. Thus, to put an indented code

3368−block in a block quote, you need five spaces after the `>`:

3369−

3370− > code

3371−

3372−#### Extension: `blank_before_blockquote` ####

3373−

3374−Standard Markdown syntax does not require a blank line before a

3375−block quote. Pandoc does require this (except, of course, at

3376−the beginning of the document). The reason for the requirement

3377−is that it is all too easy for a `>` to end up at the beginning

3378−of a line by accident (perhaps through line wrapping). So,

3379−unless the `markdown_strict` format is used, the following does

3380−not produce a nested block quote in pandoc:

3381−

3382− > This is a block quote.

3383− >> Nested.

3384−

3385−

3386−## Verbatim (code) blocks

3387−

3388−### Indented code blocks ###

3389−

3390−A block of text indented four spaces (or one tab) is treated as verbatim

3391−text: that is, special characters do not trigger special formatting,

3392−and all spaces and line breaks are preserved. For example,

3393−

3394− if (a > 3) {

3395− moveShip(5 * gravity, DOWN);

3396− }

3397−

3398−The initial (four space or one tab) indentation is not considered part

3399−of the verbatim text, and is removed in the output.

3400−

3401−Note: blank lines in the verbatim text need not begin with four spaces.

3402−

3403−

3404−### Fenced code blocks ###

3405−

3406−#### Extension: `fenced_code_blocks` ####

3407−

3408−In addition to standard indented code blocks, pandoc supports

3409−*fenced* code blocks. These begin with a row of three or more

3410−tildes (`~`) and end with a row of tildes that must be at least as long as

3411−the starting row. Everything between these lines is treated as code. No

3412−indentation is necessary:

3413−

3414− ~~~~~~~

3415− if (a > 3) {

3416− moveShip(5 * gravity, DOWN);

3417− }

3418− ~~~~~~~

3419−

3420−Like regular code blocks, fenced code blocks must be separated

3421−from surrounding text by blank lines.

3422−

3423−If the code itself contains a row of tildes or backticks, just use a longer

3424−row of tildes or backticks at the start and end:

3425−

3426− ~~~~~~~~~~~~~~~~

3427− ~~~~~~~~~~

3428− code including tildes

3429− ~~~~~~~~~~

3430− ~~~~~~~~~~~~~~~~

3431−

3432−#### Extension: `backtick_code_blocks` ####

3433−

3434−Same as `fenced_code_blocks`, but uses backticks (`` ` ``) instead of tildes

3435−(`~`).

3436−

3437−#### Extension: `fenced_code_attributes` ####

3438−

3439−Optionally, you may attach attributes to fenced or backtick code block using

3440−this syntax:

3441−

3442− ~~~~ {#mycode .haskell .numberLines startFrom="100"}

3443− qsort [] = []

3444− qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++

3445− qsort (filter (>= x) xs)

3446− ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

3447−

3448−Here `mycode` is an identifier, `haskell` and `numberLines` are

3449−classes, and `startFrom` is an attribute with value `100`. Some

3450−output formats can use this information to do syntax

3451−highlighting. Currently, the only output formats that uses this

3452−information are HTML, LaTeX, Docx, Ms, and PowerPoint. If

3453−highlighting is supported for your output format and language,

3454−then the code block above will appear highlighted, with numbered

3455−lines. (To see which languages are supported, type `pandoc

3456−--list-highlight-languages`.) Otherwise, the code block above

3457−will appear as follows:

3458−

3459− <pre id="mycode" class="haskell numberLines" startFrom="100">

3460− <code>

3461− ...

3462− </code>

3463− </pre>

3464−

3465−The `numberLines` (or `number-lines`) class will cause the lines

3466−of the code block to be numbered, starting with `1` or the value

3467−of the `startFrom` attribute. The `lineAnchors` (or

3468−`line-anchors`) class will cause the lines to be clickable

3469−anchors in HTML output.

3470−

3471−A shortcut form can also be used for specifying the language of

3472−the code block:

3473−

3474− ```haskell

3475− qsort [] = []

3476− ```

3477−

3478−This is equivalent to:

3479−

3480− ``` {.haskell}

3481− qsort [] = []

3482− ```

3483−

3484−If the `fenced_code_attributes` extension is disabled, but

3485−input contains class attribute(s) for the code block, the first

3486−class attribute will be printed after the opening fence as a bare

3487−word.

3488−

3489−To prevent all highlighting, use the `--no-highlight` flag.

3490−To set the highlighting style, use `--highlight-style`.

3491−For more information on highlighting, see [Syntax highlighting],

3492−below.

3493−

3494−## Line blocks

3495−

3496−#### Extension: `line_blocks` ####

3497−

3498−A line block is a sequence of lines beginning with a vertical bar (`|`)

3499−followed by a space. The division into lines will be preserved in

3500−the output, as will any leading spaces; otherwise, the lines will

3501−be formatted as Markdown. This is useful for verse and addresses:

3502−

3503− | The limerick packs laughs anatomical

3504− | In space that is quite economical.

3505− | But the good ones I've seen

3506− | So seldom are clean

3507− | And the clean ones so seldom are comical

3508−

3509− | 200 Main St.

3510− | Berkeley, CA 94718

3511−

3512−The lines can be hard-wrapped if needed, but the continuation

3513−line must begin with a space.

3514−

3515− | The Right Honorable Most Venerable and Righteous Samuel L.

3516− Constable, Jr.

3517− | 200 Main St.

3518− | Berkeley, CA 94718

3519−

3520−Inline formatting (such as emphasis) is allowed in the content,

3521−but not block-level formatting (such as block quotes or lists).

3522−

3523−This syntax is borrowed from [reStructuredText].

3524−

3525−## Lists

3526−

3527−### Bullet lists ###

3528−

3529−A bullet list is a list of bulleted list items. A bulleted list

3530−item begins with a bullet (`*`, `+`, or `-`). Here is a simple

3531−example:

3532−

3533− * one

3534− * two

3535− * three

3536−

3537−This will produce a "compact" list. If you want a "loose" list, in which

3538−each item is formatted as a paragraph, put spaces between the items:

3539−

3540− * one

3541−

3542− * two

3543−

3544− * three

3545−

3546−The bullets need not be flush with the left margin; they may be

3547−indented one, two, or three spaces. The bullet must be followed

3548−by whitespace.

3549−

3550−List items look best if subsequent lines are flush with the first

3551−line (after the bullet):

3552−

3553− * here is my first

3554− list item.

3555− * and my second.

3556−

3557−But Markdown also allows a "lazy" format:

3558−

3559− * here is my first

3560− list item.

3561− * and my second.

3562−

3563−### Block content in list items ###

3564−

3565−A list item may contain multiple paragraphs and other block-level

3566−content. However, subsequent paragraphs must be preceded by a blank line

3567−and indented to line up with the first non-space content after

3568−the list marker.

3569−

3570− * First paragraph.

3571−

3572− Continued.

3573−

3574− * Second paragraph. With a code block, which must be indented

3575− eight spaces:

3576−

3577− { code }

3578−

3579−Exception: if the list marker is followed by an indented code

3580−block, which must begin 5 spaces after the list marker, then

3581−subsequent paragraphs must begin two columns after the last

3582−character of the list marker:

3583−

3584− * code

3585−

3586− continuation paragraph

3587−

3588−List items may include other lists. In this case the preceding blank

3589−line is optional. The nested list must be indented to line up with

3590−the first non-space character after the list marker of the

3591−containing list item.

3592−

3593− * fruits

3594− + apples

3595− - macintosh

3596− - red delicious

3597− + pears

3598− + peaches

3599− * vegetables

3600− + broccoli

3601− + chard

3602−

3603−As noted above, Markdown allows you to write list items "lazily," instead of

3604−indenting continuation lines. However, if there are multiple paragraphs or

3605−other blocks in a list item, the first line of each must be indented.

3606−

3607− + A lazy, lazy, list

3608− item.

3609−

3610− + Another one; this looks

3611− bad but is legal.

3612−

3613− Second paragraph of second

3614− list item.

3615−

3616−### Ordered lists ###

3617−

3618−Ordered lists work just like bulleted lists, except that the items

3619−begin with enumerators rather than bullets.

3620−

3621−In standard Markdown, enumerators are decimal numbers followed

3622−by a period and a space. The numbers themselves are ignored, so

3623−there is no difference between this list:

3624−

3625− 1. one

3626− 2. two

3627− 3. three

3628−

3629−and this one:

3630−

3631− 5. one

3632− 7. two

3633− 1. three

3634−

3635−#### Extension: `fancy_lists` ####

3636−

3637−Unlike standard Markdown, pandoc allows ordered list items to be marked

3638−with uppercase and lowercase letters and roman numerals, in addition to

3639−Arabic numerals. List markers may be enclosed in parentheses or followed by a

3640−single right-parentheses or period. They must be separated from the

3641−text that follows by at least one space, and, if the list marker is a

3642−capital letter with a period, by at least two spaces.[^2]

3643−

3644−[^2]: The point of this rule is to ensure that normal paragraphs

3645− starting with people's initials, like

3646−

3647− B. Russell was an English philosopher.

3648−

3649− do not get treated as list items.

3650−

3651− This rule will not prevent

3652−

3653− (C) 2007 Joe Smith

3654−

3655− from being interpreted as a list item. In this case, a backslash

3656− escape can be used:

3657−

3658− (C\) 2007 Joe Smith

3659−

3660−The `fancy_lists` extension also allows '`#`' to be used as an

3661−ordered list marker in place of a numeral:

3662−

3663− #. one

3664− #. two

3665−

3666−#### Extension: `startnum` ####

3667−

3668−Pandoc also pays attention to the type of list marker used, and to the

3669−starting number, and both of these are preserved where possible in the

3670−output format. Thus, the following yields a list with numbers followed

3671−by a single parenthesis, starting with 9, and a sublist with lowercase

3672−roman numerals:

3673−

3674− 9) Ninth

3675− 10) Tenth

3676− 11) Eleventh

3677− i. subone

3678− ii. subtwo

3679− iii. subthree

3680−

3681−Pandoc will start a new list each time a different type of list

3682−marker is used. So, the following will create three lists:

3683−

3684− (2) Two

3685− (5) Three

3686− 1. Four

3687− * Five

3688−

3689−If default list markers are desired, use `#.`:

3690−

3691− #. one

3692− #. two

3693− #. three

3694−

3695−#### Extension: `task_lists` ####

3696−

3697−Pandoc supports task lists, using the syntax of GitHub-Flavored Markdown.

3698−

3699− - [ ] an unchecked task list item

3700− - [x] checked item

3701−

3702−### Definition lists ###

3703−

3704−#### Extension: `definition_lists` ####

3705−

3706−Pandoc supports definition lists, using the syntax of

3707−[PHP Markdown Extra] with some extensions.[^3]

3708−

3709− Term 1

3710−

3711− : Definition 1

3712−

3713− Term 2 with *inline markup*

3714−

3715− : Definition 2

3716−

3717− { some code, part of Definition 2 }

3718−

3719− Third paragraph of definition 2.

3720−

3721−Each term must fit on one line, which may optionally be followed by

3722−a blank line, and must be followed by one or more definitions.

3723−A definition begins with a colon or tilde, which may be indented one

3724−or two spaces.

3725−

3726−A term may have multiple definitions, and each definition may

3727−consist of one or more block elements (paragraph, code block,

3728−list, etc.), each indented four spaces or one tab stop. The

3729−body of the definition (including the first line, aside from the

3730−colon or tilde) should be indented four spaces. However, as with

3731−other Markdown lists, you can "lazily" omit indentation except

3732−at the beginning of a paragraph or other block element:

3733−

3734− Term 1

3735−

3736− : Definition

3737− with lazy continuation.

3738−

3739− Second paragraph of the definition.

3740−

3741−If you leave space before the definition (as in the example above),

3742−the text of the definition will be treated as a paragraph. In some

3743−output formats, this will mean greater spacing between term/definition

3744−pairs. For a more compact definition list, omit the space before the

3745−definition:

3746−

3747− Term 1

3748− ~ Definition 1

3749−

3750− Term 2

3751− ~ Definition 2a

3752− ~ Definition 2b

3753−

3754−Note that space between items in a definition list is required.

3755−(A variant that loosens this requirement, but disallows "lazy"

3756−hard wrapping, can be activated with `compact_definition_lists`: see

3757−[Non-default extensions], below.)

3758−

3759−[^3]: I have been influenced by the suggestions of [David

3760− Wheeler](https://justatheory.com/2009/02/modest-markdown-proposal/).

3761−

3762−### Numbered example lists ###

3763−

3764−#### Extension: `example_lists` ####

3765−

3766−The special list marker `@` can be used for sequentially numbered

3767−examples. The first list item with a `@` marker will be numbered '1',

3768−the next '2', and so on, throughout the document. The numbered examples

3769−need not occur in a single list; each new list using `@` will take up

3770−where the last stopped. So, for example:

3771−

3772− (@) My first example will be numbered (1).

3773− (@) My second example will be numbered (2).

3774−

3775− Explanation of examples.

3776−

3777− (@) My third example will be numbered (3).

3778−

3779−Numbered examples can be labeled and referred to elsewhere in the

3780−document:

3781−

3782− (@good) This is a good example.

3783−

3784− As (@good) illustrates, ...

3785−

3786−The label can be any string of alphanumeric characters, underscores,

3787−or hyphens.

3788−

3789−Note: continuation paragraphs in example lists must always

3790−be indented four spaces, regardless of the length of the

3791−list marker. That is, example lists always behave as if the

3792−`four_space_rule` extension is set. This is because example

3793−labels tend to be long, and indenting content to the

3794−first non-space character after the label would be awkward.

3795−

3796−

3797−### Ending a list ###

3798−

3799−What if you want to put an indented code block after a list?

3800−

3801− - item one

3802− - item two

3803−

3804− { my code block }

3805−

3806−Trouble! Here pandoc (like other Markdown implementations) will treat

3807−`{ my code block }` as the second paragraph of item two, and not as

3808−a code block.

3809−

3810−To "cut off" the list after item two, you can insert some non-indented

3811−content, like an HTML comment, which won't produce visible output in

3812−any format:

3813−

3814− - item one

3815− - item two

3816−

3817− <!-- end of list -->

3818−

3819− { my code block }

3820−

3821−You can use the same trick if you want two consecutive lists instead

3822−of one big list:

3823−

3824− 1. one

3825− 2. two

3826− 3. three

3827−

3828− <!-- -->

3829−

3830− 1. uno

3831− 2. dos

3832− 3. tres

3833−

3834−## Horizontal rules

3835−

3836−A line containing a row of three or more `*`, `-`, or `_` characters

3837−(optionally separated by spaces) produces a horizontal rule:

3838−

3839− * * * *

3840−

3841− ---------------

3842−

3843−

3844−## Tables

3845−

3846−Four kinds of tables may be used. The first three kinds presuppose the use of

3847−a fixed-width font, such as Courier. The fourth kind can be used with

3848−proportionally spaced fonts, as it does not require lining up columns.

3849−

3850−#### Extension: `table_captions` ####

3851−

3852−A caption may optionally be provided with all 4 kinds of tables (as

3853−illustrated in the examples below). A caption is a paragraph beginning

3854−with the string `Table:` (or just `:`), which will be stripped off.

3855−It may appear either before or after the table.

3856−

3857−#### Extension: `simple_tables` ####

3858−

3859−Simple tables look like this:

3860−

3861− Right Left Center Default

3862− ------- ------ ---------- -------

3863− 12 12 12 12

3864− 123 123 123 123

3865− 1 1 1 1

3866−

3867− Table: Demonstration of simple table syntax.

3868−

3869−The header and table rows must each fit on one line. Column

3870−alignments are determined by the position of the header text relative

3871−to the dashed line below it:[^4]

3872−

3873− - If the dashed line is flush with the header text on the right side

3874− but extends beyond it on the left, the column is right-aligned.

3875− - If the dashed line is flush with the header text on the left side

3876− but extends beyond it on the right, the column is left-aligned.

3877− - If the dashed line extends beyond the header text on both sides,

3878− the column is centered.

3879− - If the dashed line is flush with the header text on both sides,

3880− the default alignment is used (in most cases, this will be left).

3881−

3882−[^4]: This scheme is due to Michel Fortin, who proposed it on the

3883− [Markdown discussion list](http://six.pairlist.net/pipermail/markdown-discuss/2005-March/001097.html).

3884−

3885−The table must end with a blank line, or a line of dashes followed by

3886−a blank line.

3887−

3888−The column header row may be omitted, provided a dashed line is used

3889−to end the table. For example:

3890−

3891− ------- ------ ---------- -------

3892− 12 12 12 12

3893− 123 123 123 123

3894− 1 1 1 1

3895− ------- ------ ---------- -------

3896−

3897−When the header row is omitted, column alignments are determined on the basis

3898−of the first line of the table body. So, in the tables above, the columns

3899−would be right, left, center, and right aligned, respectively.

3900−

3901−#### Extension: `multiline_tables` ####

3902−

3903−Multiline tables allow header and table rows to span multiple lines

3904−of text (but cells that span multiple columns or rows of the table are

3905−not supported). Here is an example:

3906−

3907− -------------------------------------------------------------

3908− Centered Default Right Left

3909− Header Aligned Aligned Aligned

3910− ----------- ------- --------------- -------------------------

3911− First row 12.0 Example of a row that

3912− spans multiple lines.

3913−

3914− Second row 5.0 Here's another one. Note

3915− the blank line between

3916− rows.

3917− -------------------------------------------------------------

3918−

3919− Table: Here's the caption. It, too, may span

3920− multiple lines.

3921−

3922−These work like simple tables, but with the following differences:

3923−

3924− - They must begin with a row of dashes, before the header text

3925− (unless the header row is omitted).

3926− - They must end with a row of dashes, then a blank line.

3927− - The rows must be separated by blank lines.

3928−

3929−In multiline tables, the table parser pays attention to the widths of

3930−the columns, and the writers try to reproduce these relative widths in

3931−the output. So, if you find that one of the columns is too narrow in the

3932−output, try widening it in the Markdown source.

3933−

3934−The header may be omitted in multiline tables as well as simple tables:

3935−

3936− ----------- ------- --------------- -------------------------

3937− First row 12.0 Example of a row that

3938− spans multiple lines.

3939−

3940− Second row 5.0 Here's another one. Note

3941− the blank line between

3942− rows.

3943− ----------- ------- --------------- -------------------------

3944−

3945− : Here's a multiline table without a header.

3946−

3947−It is possible for a multiline table to have just one row, but the row

3948−should be followed by a blank line (and then the row of dashes that ends

3949−the table), or the table may be interpreted as a simple table.

3950−

3951−#### Extension: `grid_tables` ####

3952−

3953−Grid tables look like this:

3954−

3955− : Sample grid table.

3956−

3957− +---------------+---------------+--------------------+

3958− | Fruit | Price | Advantages |

3959− +===============+===============+====================+

3960− | Bananas | $1.34 | - built-in wrapper |

3961− | | | - bright color |

3962− +---------------+---------------+--------------------+

3963− | Oranges | $2.10 | - cures scurvy |

3964− | | | - tasty |

3965− +---------------+---------------+--------------------+

3966−

3967−The row of `=`s separates the header from the table body, and can be

3968−omitted for a headerless table. The cells of grid tables may contain

3969−arbitrary block elements (multiple paragraphs, code blocks, lists,

3970−etc.). Cells that span multiple columns or rows are not

3971−supported. Grid tables can be created easily using Emacs' table-mode

3972−(`M-x table-insert`).

3973−

3974−Alignments can be specified as with pipe tables, by putting

3975−colons at the boundaries of the separator line after the

3976−header:

3977−

3978− +---------------+---------------+--------------------+

3979− | Right | Left | Centered |

3980− +==============:+:==============+:==================:+

3981− | Bananas | $1.34 | built-in wrapper |

3982− +---------------+---------------+--------------------+

3983−

3984−For headerless tables, the colons go on the top line instead:

3985−

3986− +--------------:+:--------------+:------------------:+

3987− | Right | Left | Centered |

3988− +---------------+---------------+--------------------+

3989−

3990−##### Grid Table Limitations #####

3991−

3992−Pandoc does not support grid tables with row spans or column spans.

3993−This means that neither variable numbers of columns across rows nor

3994−variable numbers of rows across columns are supported by Pandoc.

3995−All grid tables must have the same number of columns in each row,

3996−and the same number of rows in each column. For example, the

3997−Docutils [sample grid tables] will not render as expected with

3998−Pandoc.

3999−

4000−[sample grid tables]: https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#grid-tables

4001−

4002−

4003−#### Extension: `pipe_tables` ####

4004−

4005−Pipe tables look like this:

4006−

4007− | Right | Left | Default | Center |

4008− |------:|:-----|---------|:------:|

4009− | 12 | 12 | 12 | 12 |

4010− | 123 | 123 | 123 | 123 |

4011− | 1 | 1 | 1 | 1 |

4012−

4013− : Demonstration of pipe table syntax.

4014−

4015−The syntax is identical to [PHP Markdown Extra tables]. The beginning and

4016−ending pipe characters are optional, but pipes are required between all

4017−columns. The colons indicate column alignment as shown. The header

4018−cannot be omitted. To simulate a headerless table, include a header

4019−with blank cells.

4020−

4021−Since the pipes indicate column boundaries, columns need not be vertically

4022−aligned, as they are in the above example. So, this is a perfectly

4023−legal (though ugly) pipe table:

4024−

4025− fruit| price

4026− -----|-----:

4027− apple|2.05

4028− pear|1.37

4029− orange|3.09

4030−

4031−The cells of pipe tables cannot contain block elements like paragraphs

4032−and lists, and cannot span multiple lines. If a pipe table contains a

4033−row whose Markdown content is wider than the column width (see

4034−`--columns`), then the table will take up the full text width and

4035−the cell contents will wrap, with the relative cell widths determined

4036−by the number of dashes in the line separating the table header from

4037−the table body. (For example `---|-` would make the first column 3/4

4038−and the second column 1/4 of the full text width.)

4039−On the other hand, if no lines are wider than column width, then

4040−cell contents will not be wrapped, and the cells will be sized

4041−to their contents.

4042−

4043−Note: pandoc also recognizes pipe tables of the following

4044−form, as can be produced by Emacs' orgtbl-mode:

4045−

4046− | One | Two |

4047− |-----+-------|

4048− | my | table |

4049− | is | nice |

4050−

4051−The difference is that `+` is used instead of `|`. Other orgtbl features

4052−are not supported. In particular, to get non-default column alignment,

4053−you'll need to add colons as above.

4054−

4055−[PHP Markdown Extra tables]: https://michelf.ca/projects/php-markdown/extra/#table

4056−

4057−## Metadata blocks

4058−

4059−#### Extension: `pandoc_title_block` ####

4060−

4061−If the file begins with a title block

4062−

4063− % title

4064− % author(s) (separated by semicolons)

4065− % date

4066−

4067−it will be parsed as bibliographic information, not regular text. (It

4068−will be used, for example, in the title of standalone LaTeX or HTML

4069−output.) The block may contain just a title, a title and an author,

4070−or all three elements. If you want to include an author but no

4071−title, or a title and a date but no author, you need a blank line:

4072−

4073−```

4074−%

4075−% Author

4076−```

4077−

4078−```

4079−% My title

4080−%

4081−% June 15, 2006

4082−```

4083−

4084−The title may occupy multiple lines, but continuation lines must

4085−begin with leading space, thus:

4086−

4087−```

4088−% My title

4089− on multiple lines

4090−```

4091−

4092−If a document has multiple authors, the authors may be put on

4093−separate lines with leading space, or separated by semicolons, or

4094−both. So, all of the following are equivalent:

4095−

4096−```

4097−% Author One

4098− Author Two

4099−```

4100−

4101−```

4102−% Author One; Author Two

4103−```

4104−

4105−```

4106−% Author One;

4107− Author Two

4108−```

4109−

4110−The date must fit on one line.

4111−

4112−All three metadata fields may contain standard inline formatting

4113−(italics, links, footnotes, etc.).

4114−

4115−Title blocks will always be parsed, but they will affect the output only

4116−when the `--standalone` (`-s`) option is chosen. In HTML output, titles

4117−will appear twice: once in the document head -- this is the title that

4118−will appear at the top of the window in a browser -- and once at the

4119−beginning of the document body. The title in the document head can have

4120−an optional prefix attached (`--title-prefix` or `-T` option). The title

4121−in the body appears as an H1 element with class "title", so it can be

4122−suppressed or reformatted with CSS. If a title prefix is specified with

4123−`-T` and no title block appears in the document, the title prefix will

4124−be used by itself as the HTML title.

4125−

4126−The man page writer extracts a title, man page section number, and

4127−other header and footer information from the title line. The title

4128−is assumed to be the first word on the title line, which may optionally

4129−end with a (single-digit) section number in parentheses. (There should

4130−be no space between the title and the parentheses.) Anything after

4131−this is assumed to be additional footer and header text. A single pipe

4132−character (`|`) should be used to separate the footer text from the header

4133−text. Thus,

4134−

4135− % PANDOC(1)

4136−

4137−will yield a man page with the title `PANDOC` and section 1.

4138−

4139− % PANDOC(1) Pandoc User Manuals

4140−

4141−will also have "Pandoc User Manuals" in the footer.

4142−

4143− % PANDOC(1) Pandoc User Manuals | Version 4.0

4144−

4145−will also have "Version 4.0" in the header.

4146−

4147−#### Extension: `yaml_metadata_block` ####

4148−

4149−A [YAML] metadata block is a valid YAML object, delimited by a line of three

4150−hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots

4151−(`...`) at the bottom. A YAML metadata block may occur anywhere in the

4152−document, but if it is not at the beginning, it must be preceded by a blank

4153−line. (Note that, because of the way pandoc concatenates input files when

4154−several are provided, you may also keep the metadata in a separate YAML file

4155−and pass it to pandoc as an argument, along with your Markdown files:

4156−

4157− pandoc chap1.md chap2.md chap3.md metadata.yaml -s -o book.html

4158−

4159−Just be sure that the YAML file begins with `---` and ends with `---` or

4160−`...`.) Alternatively, you can use the `--metadata-file` option. Using

4161−that approach however, you cannot reference content (like footnotes)

4162−from the main markdown input document.

4163−

4164−Metadata will be taken from the fields of the YAML object and added to any

4165−existing document metadata. Metadata can contain lists and objects (nested

4166−arbitrarily), but all string scalars will be interpreted as Markdown. Fields

4167−with names ending in an underscore will be ignored by pandoc. (They may be

4168−given a role by external processors.) Field names must not be

4169−interpretable as YAML numbers or boolean values (so, for

4170−example, `yes`, `True`, and `15` cannot be used as field names).

4171−

4172−A document may contain multiple metadata blocks. If two

4173−metadata blocks attempt to set the same field, the value from

4174−the second block will be taken.

4175−

4176−When pandoc is used with `-t markdown` to create a Markdown document,

4177−a YAML metadata block will be produced only if the `-s/--standalone`

4178−option is used. All of the metadata will appear in a single block

4179−at the beginning of the document.

4180−

4181−Note that [YAML] escaping rules must be followed. Thus, for example,

4182−if a title contains a colon, it must be quoted, and if it contains a

4183−backslash escape, then it must be ensured that it is not treated as a

4184−[YAML escape sequence]. The pipe character (`|`) can be used to begin

4185−an indented block that will be interpreted literally, without need for

4186−escaping. This form is necessary when the field contains blank lines

4187−or block-level formatting:

4188−

4189− ---

4190− title: 'This is the title: it contains a colon'

4191− author:

4192− - Author One

4193− - Author Two

4194− keywords: [nothing, nothingness]

4195− abstract: |

4196− This is the abstract.

4197−

4198− It consists of two paragraphs.

4199− ...

4200−

4201−The literal block after the `|` must be indented relative to the

4202−line containing the `|`. If it is not, the YAML will be invalid

4203−and pandoc will not interpret it as metadata. For an overview

4204−of the complex rules governing YAML, see the [Wikipedia entry on

4205−YAML syntax].

4206−

4207−Template variables will be set automatically from the metadata. Thus, for

4208−example, in writing HTML, the variable `abstract` will be set to the HTML

4209−equivalent of the Markdown in the `abstract` field:

4210−

4211− <p>This is the abstract.</p>

4212− <p>It consists of two paragraphs.</p>

4213−

4214−Variables can contain arbitrary YAML structures, but the template must match

4215−this structure. The `author` variable in the default templates expects a

4216−simple list or string, but can be changed to support more complicated

4217−structures. The following combination, for example, would add an affiliation

4218−to the author if one is given:

4219−

4220− ---

4221− title: The document title

4222− author:

4223− - name: Author One

4224− affiliation: University of Somewhere

4225− - name: Author Two

4226− affiliation: University of Nowhere

4227− ...

4228−

4229−To use the structured authors in the example above, you would need a custom

4230−template:

4231−

4232− $for(author)$

4233− $if(author.name)$

4234− $author.name$$if(author.affiliation)$ ($author.affiliation$)$endif$

4235− $else$

4236− $author$

4237− $endif$

4238− $endfor$

4239−

4240−Raw content to include in the document's header may be specified

4241−using `header-includes`; however, it is important to mark up

4242−this content as raw code for a particular output format, using

4243−the [`raw_attribute` extension](#extension-raw_attribute)), or it

4244−will be interpreted as markdown. For example:

4245−

4246− header-includes:

4247− - |

4248− ```{=latex}

4249− \let\oldsection\section

4250− \renewcommand{\section}[1]{\clearpage\oldsection{#1}}

4251− ```

4252−

4253−Note: the `yaml_metadata_block` extension works with

4254−`commonmark` as well as `markdown` (and it is enabled by default

4255−in `gfm` and `commonmark_x`). However, in these formats the

4256−following restrictions apply:

4257−

4258−- The YAML metadata block must occur at the beginning of the

4259− document (and there can be only one). If multiple files are

4260− given as arguments to pandoc, only the first can be a YAML

4261− metadata block.

4262−

4263−- The leaf nodes of the YAML structure are parsed in isolation from

4264− each other and from the rest of the document. So, for

4265− example, you can't use a reference link in these contexts

4266− if the link definition is somewhere else in the document.

4267−

4268−[YAML escape sequence]: https://yaml.org/spec/1.2/spec.html#id2776092

4269−[Wikipedia entry on YAML syntax]: https://en.m.wikipedia.org/wiki/YAML#Syntax

4270−

4271−## Backslash escapes

4272−

4273−#### Extension: `all_symbols_escapable` ####

4274−

4275−Except inside a code block or inline code, any punctuation or space

4276−character preceded by a backslash will be treated literally, even if it

4277−would normally indicate formatting. Thus, for example, if one writes

4278−

4279− *\*hello\**

4280−

4281−one will get

4282−

4283− <em>*hello*</em>

4284−

4285−instead of

4286−

4287− <strong>hello</strong>

4288−

4289−This rule is easier to remember than standard Markdown's rule,

4290−which allows only the following characters to be backslash-escaped:

4291−

4292− \`*_{}[]()>#+-.!

4293−

4294−(However, if the `markdown_strict` format is used, the standard Markdown rule

4295−will be used.)

4296−

4297−A backslash-escaped space is parsed as a nonbreaking space. In TeX output,

4298−it will appear as `~`. In HTML and XML output, it will appear as a

4299−literal unicode nonbreaking space character (note that it will thus

4300−actually look "invisible" in the generated HTML source; you can still

4301−use the `--ascii` command-line option to make it appear as an explicit

4302−entity).

4303−

4304−A backslash-escaped newline (i.e. a backslash occurring at the end of

4305−a line) is parsed as a hard line break. It will appear in TeX output as

4306−`\\` and in HTML as `<br />`. This is a nice alternative to

4307−Markdown's "invisible" way of indicating hard line breaks using

4308−two trailing spaces on a line.

4309−

4310−Backslash escapes do not work in verbatim contexts.

4311−

4312−## Inline formatting

4313−

4314−### Emphasis ###

4315−

4316−To *emphasize* some text, surround it with `*`s or `_`, like this:

4317−

4318− This text is _emphasized with underscores_, and this

4319− is *emphasized with asterisks*.

4320−

4321−Double `*` or `_` produces **strong emphasis**:

4322−

4323− This is **strong emphasis** and __with underscores__.

4324−

4325−A `*` or `_` character surrounded by spaces, or backslash-escaped,

4326−will not trigger emphasis:

4327−

4328− This is * not emphasized *, and \*neither is this\*.

4329−

4330−#### Extension: `intraword_underscores` ####

4331−

4332−Because `_` is sometimes used inside words and identifiers,

4333−pandoc does not interpret a `_` surrounded by alphanumeric

4334−characters as an emphasis marker. If you want to emphasize

4335−just part of a word, use `*`:

4336−

4337− feas*ible*, not feas*able*.

4338−

4339−

4340−### Strikeout ###

4341−

4342−#### Extension: `strikeout` ####

4343−

4344−To strikeout a section of text with a horizontal line, begin and end it

4345−with `~~`. Thus, for example,

4346−

4347− This ~~is deleted text.~~

4348−

4349−

4350−### Superscripts and subscripts ###

4351−

4352−#### Extension: `superscript`, `subscript` ####

4353−

4354−Superscripts may be written by surrounding the superscripted text by `^`

4355−characters; subscripts may be written by surrounding the subscripted

4356−text by `~` characters. Thus, for example,

4357−

4358− H~2~O is a liquid. 2^10^ is 1024.

4359−

4360−The text between `^...^` or `~...~` may not contain spaces or

4361−newlines. If the superscripted or subscripted text contains

4362−spaces, these spaces must be escaped with backslashes. (This is

4363−to prevent accidental superscripting and subscripting through

4364−the ordinary use of `~` and `^`, and also bad interactions with

4365−footnotes.) Thus, if you want the letter P with 'a cat' in

4366−subscripts, use `P~a\ cat~`, not `P~a cat~`.

4367−

4368−### Verbatim ###

4369−

4370−To make a short span of text verbatim, put it inside backticks:

4371−

4372− What is the difference between `>>=` and `>>`?

4373−

4374−If the verbatim text includes a backtick, use double backticks:

4375−

4376− Here is a literal backtick `` ` ``.

4377−

4378−(The spaces after the opening backticks and before the closing

4379−backticks will be ignored.)

4380−

4381−The general rule is that a verbatim span starts with a string

4382−of consecutive backticks (optionally followed by a space)

4383−and ends with a string of the same number of backticks (optionally

4384−preceded by a space).

4385−

4386−Note that backslash-escapes (and other Markdown constructs) do not

4387−work in verbatim contexts:

4388−

4389− This is a backslash followed by an asterisk: `\*`.

4390−

4391−#### Extension: `inline_code_attributes` ####

4392−

4393−Attributes can be attached to verbatim text, just as with

4394−[fenced code blocks]:

4395−

4396− `<$>`{.haskell}

4397−

4398−### Small caps ###

4399−

4400−To write small caps, use the `smallcaps` class:

4401−

4402− [Small caps]{.smallcaps}

4403−

4404−Or, without the `bracketed_spans` extension:

4405−

4406− <span class="smallcaps">Small caps</span>

4407−

4408−For compatibility with other Markdown flavors, CSS is also supported:

4409−

4410− <span style="font-variant:small-caps;">Small caps</span>

4411−

4412−This will work in all output formats that support small caps.

4413−

4414−

4415−## Math

4416−

4417−#### Extension: `tex_math_dollars` ####

4418−

4419−Anything between two `$` characters will be treated as TeX math. The

4420−opening `$` must have a non-space character immediately to its right,

4421−while the closing `$` must have a non-space character immediately to its

4422−left, and must not be followed immediately by a digit. Thus,

4423−`$20,000 and $30,000` won't parse as math. If for some reason

4424−you need to enclose text in literal `$` characters, backslash-escape

4425−them and they won't be treated as math delimiters.

4426−

4427−For display math, use `$$` delimiters. (In this case, the delimiters

4428−may be separated from the formula by whitespace. However, there can be

4429−no blank lines betwen the opening and closing `$$` delimiters.)

4430−

4431−TeX math will be printed in all output formats. How it is rendered

4432−depends on the output format:

4433−

4434−LaTeX

4435− ~ It will appear verbatim surrounded by `\(...\)` (for inline

4436− math) or `\[...\]` (for display math).

4437−

4438−Markdown, Emacs Org mode, ConTeXt, ZimWiki

4439− ~ It will appear verbatim surrounded by `$...$` (for inline

4440− math) or `$$...$$` (for display math).

4441−

4442−XWiki

4443− ~ It will appear verbatim surrounded by `{{formula}}..{{/formula}}`.

4444−

4445−reStructuredText

4446− ~ It will be rendered using an [interpreted text role `:math:`].

4447−

4448−AsciiDoc

4449− ~ For AsciiDoc output format (`-t asciidoc`) it will appear verbatim

4450− surrounded by `latexmath:[$...$]` (for inline math) or

4451− `[latexmath]++++\[...\]+++` (for display math).

4452− For AsciiDoctor output format (`-t asciidoctor`) the LaTex delimiters

4453− (`$..$` and `\[..\]`) are omitted.

4454−

4455−Texinfo

4456− ~ It will be rendered inside a `@math` command.

4457−

4458−roff man, Jira markup

4459− ~ It will be rendered verbatim without `$`'s.

4460−

4461−MediaWiki, DokuWiki

4462− ~ It will be rendered inside `<math>` tags.

4463−

4464−Textile

4465− ~ It will be rendered inside `<span class="math">` tags.

4466−

4467−RTF, OpenDocument

4468− ~ It will be rendered, if possible, using Unicode characters,

4469− and will otherwise appear verbatim.

4470−

4471−ODT

4472− ~ It will be rendered, if possible, using MathML.

4473−

4474−DocBook

4475− ~ If the `--mathml` flag is used, it will be rendered using MathML

4476− in an `inlineequation` or `informalequation` tag. Otherwise it

4477− will be rendered, if possible, using Unicode characters.

4478−

4479−Docx

4480− ~ It will be rendered using OMML math markup.

4481−

4482−FictionBook2

4483− ~ If the `--webtex` option is used, formulas are rendered as images

4484− using CodeCogs or other compatible web service, downloaded

4485− and embedded in the e-book. Otherwise, they will appear verbatim.

4486−

4487−HTML, Slidy, DZSlides, S5, EPUB

4488− ~ The way math is rendered in HTML will depend on the

4489− command-line options selected. Therefore see [Math rendering in HTML]

4490− above.

4491−

4492−[interpreted text role `:math:`]: https://docutils.sourceforge.io/docs/ref/rst/roles.html#math

4493−

4494−## Raw HTML

4495−

4496−#### Extension: `raw_html` ####

4497−

4498−Markdown allows you to insert raw HTML (or DocBook) anywhere in a document

4499−(except verbatim contexts, where `<`, `>`, and `&` are interpreted

4500−literally). (Technically this is not an extension, since standard

4501−Markdown allows it, but it has been made an extension so that it can

4502−be disabled if desired.)

4503−

4504−The raw HTML is passed through unchanged in HTML, S5, Slidy, Slideous,

4505−DZSlides, EPUB, Markdown, CommonMark, Emacs Org mode, and Textile

4506−output, and suppressed in other formats.

4507−

4508−For a more explicit way of including raw HTML in a Markdown

4509−document, see the [`raw_attribute` extension][Extension: `raw_attribute`].

4510−

4511−In the CommonMark format, if `raw_html` is enabled, superscripts,

4512−subscripts, strikeouts and small capitals will be represented as HTML.

4513−Otherwise, plain-text fallbacks will be used. Note that even if

4514−`raw_html` is disabled, tables will be rendered with HTML syntax if

4515−they cannot use pipe syntax.

4516−

4517−#### Extension: `markdown_in_html_blocks` ####

4518−

4519−Standard Markdown allows you to include HTML "blocks": blocks

4520−of HTML between balanced tags that are separated from the surrounding text

4521−with blank lines, and start and end at the left margin. Within

4522−these blocks, everything is interpreted as HTML, not Markdown;

4523−so (for example), `*` does not signify emphasis.

4524−

4525−Pandoc behaves this way when the `markdown_strict` format is used; but

4526−by default, pandoc interprets material between HTML block tags as Markdown.

4527−Thus, for example, pandoc will turn

4528−

4529− <table>

4530− <tr>

4531− <td>*one*</td>

4532− <td>[a link](https://google.com)</td>

4533− </tr>

4534− </table>

4535−

4536−into

4537−

4538− <table>

4539− <tr>

4540− <td><em>one</em></td>

4541− <td><a href="https://google.com">a link</a></td>

4542− </tr>

4543− </table>

4544−

4545−whereas `Markdown.pl` will preserve it as is.

4546−

4547−There is one exception to this rule: text between `<script>`,

4548−`<style>`, and `<textarea>` tags is not interpreted as Markdown.

4549−

4550−This departure from standard Markdown should make it easier to mix

4551−Markdown with HTML block elements. For example, one can surround

4552−a block of Markdown text with `<div>` tags without preventing it

4553−from being interpreted as Markdown.

4554−

4555−#### Extension: `native_divs` ####

4556−

4557−Use native pandoc `Div` blocks for content inside `<div>` tags.

4558−For the most part this should give the same output as

4559−`markdown_in_html_blocks`, but it makes it easier to write pandoc

4560−filters to manipulate groups of blocks.

4561−

4562−#### Extension: `native_spans` ####

4563−

4564−Use native pandoc `Span` blocks for content inside `<span>` tags.

4565−For the most part this should give the same output as `raw_html`,

4566−but it makes it easier to write pandoc filters to manipulate groups

4567−of inlines.

4568−

4569−#### Extension: `raw_tex` ####

4570−

4571−In addition to raw HTML, pandoc allows raw LaTeX, TeX, and ConTeXt to be

4572−included in a document. Inline TeX commands will be preserved and passed

4573−unchanged to the LaTeX and ConTeXt writers. Thus, for example, you can use

4574−LaTeX to include BibTeX citations:

4575−

4576− This result was proved in \cite{jones.1967}.

4577−

4578−Note that in LaTeX environments, like

4579−

4580− \begin{tabular}{|l|l|}\hline

4581− Age & Frequency \\ \hline

4582− 18--25 & 15 \\

4583− 26--35 & 33 \\

4584− 36--45 & 22 \\ \hline

4585− \end{tabular}

4586−

4587−the material between the begin and end tags will be interpreted as raw

4588−LaTeX, not as Markdown.

4589−

4590−For a more explicit and flexible way of including raw TeX in a

4591−Markdown document, see the [`raw_attribute`

4592−extension][Extension: `raw_attribute`].

4593−

4594−Inline LaTeX is ignored in output formats other than Markdown, LaTeX,

4595−Emacs Org mode, and ConTeXt.

4596−

4597−### Generic raw attribute ###

4598−

4599−#### Extension: `raw_attribute` ####

4600−

4601−Inline spans and fenced code blocks with a special

4602−kind of attribute will be parsed as raw content with the

4603−designated format. For example, the following produces a raw

4604−roff `ms` block:

4605−

4606− ```{=ms}

4607− .MYMACRO

4608− blah blah

4609− ```

4610−And the following produces a raw `html` inline element:

4611−

4612− This is `<a>html</a>`{=html}

4613−

4614−This can be useful to insert raw xml into `docx` documents, e.g.

4615−a pagebreak:

4616−

4617− ```{=openxml}

4618− <w:p>

4619− <w:r>

4620− <w:br w:type="page"/>

4621− </w:r>

4622− </w:p>

4623− ```

4624−

4625−The format name should match the target format name (see

4626−`-t/--to`, above, for a list, or use `pandoc

4627−--list-output-formats`). Use `openxml` for `docx` output,

4628−`opendocument` for `odt` output, `html5` for `epub3` output,

4629−`html4` for `epub2` output, and `latex`, `beamer`,

4630−`ms`, or `html5` for `pdf` output (depending on what you

4631−use for `--pdf-engine`).

4632−

4633−This extension presupposes that the relevant kind of

4634−inline code or fenced code block is enabled. Thus, for

4635−example, to use a raw attribute with a backtick code block,

4636−`backtick_code_blocks` must be enabled.

4637−

4638−The raw attribute cannot be combined with regular attributes.

4639−

4640−## LaTeX macros

4641−

4642−#### Extension: `latex_macros` ####

4643−

4644−When this extension is enabled, pandoc will parse LaTeX

4645−macro definitions and apply the resulting macros to all LaTeX

4646−math and raw LaTeX. So, for example, the following will work in

4647−all output formats, not just LaTeX:

4648−

4649− \newcommand{\tuple}[1]{\langle #1 \rangle}

4650−

4651− $\tuple{a, b, c}$

4652−

4653−Note that LaTeX macros will not be applied if they occur

4654−inside a raw span or block marked with the

4655−[`raw_attribute` extension](#extension-raw_attribute).

4656−

4657−When `latex_macros` is disabled, the raw LaTeX and math will

4658−not have macros applied. This is usually a better approach when

4659−you are targeting LaTeX or PDF.

4660−

4661−Macro definitions in LaTeX will be passed through as raw LaTeX

4662−only if `latex_macros` is not enabled. Macro definitions in

4663−Markdown source (or other formats allowing `raw_tex`) will

4664−be passed through regardless of whether `latex_macros` is

4665−enabled.

4666−

4667−## Links

4668−

4669−Markdown allows links to be specified in several ways.

4670−

4671−### Automatic links ###

4672−

4673−If you enclose a URL or email address in pointy brackets, it

4674−will become a link:

4675−

4676− <https://google.com>

4677− <sam@green.eggs.ham>

4678−

4679−### Inline links ###

4680−

4681−An inline link consists of the link text in square brackets,

4682−followed by the URL in parentheses. (Optionally, the URL can

4683−be followed by a link title, in quotes.)

4684−

4685− This is an [inline link](/url), and here's [one with

4686− a title](https://fsf.org "click here for a good time!").

4687−

4688−There can be no space between the bracketed part and the parenthesized part.

4689−The link text can contain formatting (such as emphasis), but the title cannot.

4690−

4691−Email addresses in inline links are not autodetected, so they have to be

4692−prefixed with `mailto`:

4693−

4694− [Write me!](mailto:sam@green.eggs.ham)

4695−

4696−### Reference links ###

4697−

4698−An *explicit* reference link has two parts, the link itself and the link

4699−definition, which may occur elsewhere in the document (either

4700−before or after the link).

4701−

4702−The link consists of link text in square brackets, followed by a label in

4703−square brackets. (There cannot be space between the two unless the

4704−`spaced_reference_links` extension is enabled.) The link definition

4705−consists of the bracketed label, followed by a colon and a space, followed by

4706−the URL, and optionally (after a space) a link title either in quotes or in

4707−parentheses. The label must not be parseable as a citation (assuming

4708−the `citations` extension is enabled): citations take precedence over

4709−link labels.

4710−

4711−Here are some examples:

4712−

4713− [my label 1]: /foo/bar.html "My title, optional"

4714− [my label 2]: /foo

4715− [my label 3]: https://fsf.org (The free software foundation)

4716− [my label 4]: /bar#special 'A title in single quotes'

4717−

4718−The URL may optionally be surrounded by angle brackets:

4719−

4720− [my label 5]: <http://foo.bar.baz>

4721−

4722−The title may go on the next line:

4723−

4724− [my label 3]: https://fsf.org

4725− "The free software foundation"

4726−

4727−Note that link labels are not case sensitive. So, this will work:

4728−

4729− Here is [my link][FOO]

4730−

4731− [Foo]: /bar/baz

4732−

4733−In an *implicit* reference link, the second pair of brackets is

4734−empty:

4735−

4736− See [my website][].

4737−

4738− [my website]: http://foo.bar.baz

4739−

4740−Note: In `Markdown.pl` and most other Markdown implementations,

4741−reference link definitions cannot occur in nested constructions

4742−such as list items or block quotes. Pandoc lifts this arbitrary

4743−seeming restriction. So the following is fine in pandoc, though

4744−not in most other implementations:

4745−

4746− > My block [quote].

4747− >

4748− > [quote]: /foo

4749−

4750−#### Extension: `shortcut_reference_links` ####

4751−

4752−In a *shortcut* reference link, the second pair of brackets may

4753−be omitted entirely:

4754−

4755− See [my website].

4756−

4757− [my website]: http://foo.bar.baz

4758−

4759−### Internal links ###

4760−

4761−To link to another section of the same document, use the automatically

4762−generated identifier (see [Heading identifiers]). For example:

4763−

4764− See the [Introduction](#introduction).

4765−

4766−or

4767−

4768− See the [Introduction].

4769−

4770− [Introduction]: #introduction

4771−

4772−Internal links are currently supported for HTML formats (including

4773−HTML slide shows and EPUB), LaTeX, and ConTeXt.

4774−

4775−## Images

4776−

4777−A link immediately preceded by a `!` will be treated as an image.

4778−The link text will be used as the image's alt text:

4779−

4780− 

4781−

4782− ![movie reel]

4783−

4784− [movie reel]: movie.gif

4785−

4786−#### Extension: `implicit_figures` ####

4787−

4788−An image with nonempty alt text, occurring by itself in a

4789−paragraph, will be rendered as a figure with a caption. The

4790−image's alt text will be used as the caption.

4791−

4792− 

4793−

4794−How this is rendered depends on the output format. Some output

4795−formats (e.g. RTF) do not yet support figures. In those

4796−formats, you'll just get an image in a paragraph by itself, with

4797−no caption.

4798−

4799−If you just want a regular inline image, just make sure it is not

4800−the only thing in the paragraph. One way to do this is to insert a

4801−nonbreaking space after the image:

4802−

4803− \

4804−

4805−Note that in reveal.js slide shows, an image in a paragraph

4806−by itself that has the `stretch` class will fill the screen,

4807−and the caption and figure tags will be omitted.

4808−

4809−#### Extension: `link_attributes` ####

4810−

4811−Attributes can be set on links and images:

4812−

4813− An inline {#id .class width=30 height=20px}

4814− and a reference ![image][ref] with attributes.

4815−

4816− [ref]: foo.jpg "optional title" {#id .class key=val key2="val 2"}

4817−

4818−(This syntax is compatible with [PHP Markdown Extra] when only `#id`

4819−and `.class` are used.)

4820−

4821−For HTML and EPUB, all known HTML5 attributes except `width` and

4822−`height` (but including `srcset` and `sizes`) are passed through

4823−as is. Unknown attributes are passed through as custom

4824−attributes, with `data-` prepended. The other writers ignore

4825−attributes that are not specifically supported by their output format.

4826−

4827−The `width` and `height` attributes on images are treated specially. When

4828−used without a unit, the unit is assumed to be pixels. However, any of

4829−the following unit identifiers can be used: `px`, `cm`, `mm`, `in`, `inch`

4830−and `%`. There must not be any spaces between the number and the unit.

4831−For example:

4832−

4833−```

4834−{ width=50% }

4835−```

4836−

4837−- Dimensions may be converted to a form that is compatible with

4838− the output format (for example, dimensions given in pixels will

4839− be converted to inches when converting HTML to LaTeX). Conversion

4840− between pixels and physical measurements is affected by the

4841− `--dpi` option (by default, 96 dpi is assumed, unless the image

4842− itself contains dpi information).

4843−- The `%` unit is generally relative to some available space.

4844− For example the above example will render to the following.

4845− - HTML: `<img href="file.jpg" style="width: 50%;" />`

4846− - LaTeX: `\includegraphics[width=0.5\textwidth,height=\textheight]{file.jpg}`

4847− (If you're using a custom template, you need to configure `graphicx`

4848− as in the default template.)

4849− - ConTeXt: `\externalfigure[file.jpg][width=0.5\textwidth]`

4850−- Some output formats have a notion of a class

4851− ([ConTeXt](https://wiki.contextgarden.net/Using_Graphics#Multiple_Image_Settings))

4852− or a unique identifier (LaTeX `\caption`), or both (HTML).

4853−- When no `width` or `height` attributes are specified, the fallback

4854− is to look at the image resolution and the dpi metadata embedded in

4855− the image file.

4856−

4857−## Divs and Spans

4858−

4859−Using the `native_divs` and `native_spans` extensions

4860−(see [above][Extension: `native_divs`]), HTML syntax can

4861−be used as part of markdown to create native `Div` and `Span`

4862−elements in the pandoc AST (as opposed to raw HTML).

4863−However, there is also nicer syntax available:

4864−

4865−#### Extension: `fenced_divs` ####

4866−

4867−Allow special fenced syntax for native `Div` blocks. A Div

4868−starts with a fence containing at least three consecutive

4869−colons plus some attributes. The attributes may optionally

4870−be followed by another string of consecutive colons.

4871−The attribute syntax is exactly as in fenced code blocks (see

4872−[Extension: `fenced_code_attributes`]). As with fenced

4873−code blocks, one can use either attributes in curly braces

4874−or a single unbraced word, which will be treated as a class

4875−name. The Div ends with another line containing a string of at

4876−least three consecutive colons. The fenced Div should be

4877−separated by blank lines from preceding and following blocks.

4878−

4879−Example:

4880−

4881− ::::: {#special .sidebar}

4882− Here is a paragraph.

4883−

4884− And another.

4885− :::::

4886−

4887−Fenced divs can be nested. Opening fences are distinguished

4888−because they *must* have attributes:

4889−

4890− ::: Warning ::::::

4891− This is a warning.

4892−

4893− ::: Danger

4894− This is a warning within a warning.

4895− :::

4896− ::::::::::::::::::

4897−

4898−Fences without attributes are always closing fences. Unlike

4899−with fenced code blocks, the number of colons in the closing

4900−fence need not match the number in the opening fence. However,

4901−it can be helpful for visual clarity to use fences of different

4902−lengths to distinguish nested divs from their parents.

4903−

4904−

4905−#### Extension: `bracketed_spans` ####

4906−

4907−A bracketed sequence of inlines, as one would use to begin

4908−a link, will be treated as a `Span` with attributes if it is

4909−followed immediately by attributes:

4910−

4911− [This is *some text*]{.class key="val"}

4912−

4913−## Footnotes

4914−

4915−#### Extension: `footnotes` ####

4916−

4917−Pandoc's Markdown allows footnotes, using the following syntax:

4918−

4919− Here is a footnote reference,[^1] and another.[^longnote]

4920−

4921− [^1]: Here is the footnote.

4922−

4923− [^longnote]: Here's one with multiple blocks.

4924−

4925− Subsequent paragraphs are indented to show that they

4926− belong to the previous footnote.

4927−

4928− { some.code }

4929−

4930− The whole paragraph can be indented, or just the first

4931− line. In this way, multi-paragraph footnotes work like

4932− multi-paragraph list items.

4933−

4934− This paragraph won't be part of the note, because it

4935− isn't indented.

4936−

4937−The identifiers in footnote references may not contain spaces, tabs,

4938−or newlines. These identifiers are used only to correlate the

4939−footnote reference with the note itself; in the output, footnotes

4940−will be numbered sequentially.

4941−

4942−The footnotes themselves need not be placed at the end of the

4943−document. They may appear anywhere except inside other block elements

4944−(lists, block quotes, tables, etc.). Each footnote should be

4945−separated from surrounding content (including other footnotes)

4946−by blank lines.

4947−

4948−#### Extension: `inline_notes` ####

4949−

4950−Inline footnotes are also allowed (though, unlike regular notes,

4951−they cannot contain multiple paragraphs). The syntax is as follows:

4952−

4953− Here is an inline note.^[Inlines notes are easier to write, since

4954− you don't have to pick an identifier and move down to type the

4955− note.]

4956−

4957−Inline and regular footnotes may be mixed freely.

4958−

4959−## Citation syntax

4960−

4961−#### Extension: `citations` ####

4962−

4963−To cite a bibliographic item with an identifier foo, use the

4964−syntax `@foo`. Normal citations should be included in square

4965−brackets, with semicolons separating distinct items:

4966−

4967− Blah blah [@doe99; @smith2000; @smith2004].

4968−

4969−How this is rendered depends on the citation style. In an

4970−author-date style, it might render as

4971−

4972− Blah blah (Doe 1999, Smith 2000, 2004).

4973−

4974−In a footnote style, it might render as

4975−

4976− Blah blah.[^1]

4977−

4978− [^1]: John Doe, "Frogs," *Journal of Amphibians* 44 (1999);

4979− Susan Smith, "Flies," *Journal of Insects* (2000);

4980− Susan Smith, "Bees," *Journal of Insects* (2004).

4981−

4982−See the [CSL user documentation] for more information about CSL

4983−styles and how they affect rendering.

4984−

4985−Unless a citation key start with a letter, digit, or `_`,

4986−and contains only alphanumerics and internal punctuation

4987−characters (`:.#$%&-+?<>~/`), it must be surrounded

4988−by curly braces, which are not considered part of the key.

4989−In `@Foo_bar.baz.`, the key is `Foo_bar.baz`. The final

4990−period is not *internal* punctuation, so it is not included in

4991−the key. In `@{Foo_bar.baz.}`, the key is `Foo_bar.baz.`, including

4992−the final period. The curly braces are recommended if you use URLs as

4993−keys: `[@{https://example.com/bib?name=foobar&date=2000}, p. 33]`.

4994−

4995−Citation items may optionally include a prefix, a locator, and

4996−a suffix. In

4997−

4998− Blah blah [see @doe99, pp. 33-35 and *passim*; @smith04, chap. 1].

4999−

5000−The first item (`doe99`) has prefix `see `, locator `pp. 33-35`,

5001−and suffix `and *passim*`. The second item (`smith04`) has

5002−locator `chap. 1` and no prefix or suffix.

5003−

5004−Pandoc uses some heuristics to separate the locator from the

5005−rest of the subject. It is sensitive to the locator terms

5006−defined in the [CSL locale files]. Either abbreviated or

5007−unabbreviated forms are accepted. In the `en-US` locale, locator

5008−terms can be written in either singular or plural forms, as

5009−`book`, `bk.`/`bks.`; `chapter`, `chap.`/`chaps.`; `column`,

5010−`col.`/`cols.`; `figure`, `fig.`/`figs.`; `folio`,

5011−`fol.`/`fols.`; `number`, `no.`/`nos.`; `line`, `l.`/`ll.`;

5012−`note`, `n.`/`nn.`; `opus`, `op.`/`opp.`; `page`, `p.`/`pp.`;

5013−`paragraph`, `para.`/`paras.`; `part`, `pt.`/`pts.`; `section`,

5014−`sec.`/`secs.`; `sub verbo`, `s.v.`/`s.vv.`; `verse`,

5015−`v.`/`vv.`; `volume`, `vol.`/`vols.`; `¶`/`¶¶`; `§`/`§§`. If no

5016−locator term is used, "page" is assumed.

5017−

5018−In complex cases, you can force something to be treated as

5019−a locator by enclosing it in curly braces or prevent parsing

5020−the suffix as locator by prepending curly braces:

5021−

5022− [@smith{ii, A, D-Z}, with a suffix]

5023− [@smith, {pp. iv, vi-xi, (xv)-(xvii)} with suffix here]

5024− [@smith{}, 99 years later]

5025−

5026−A minus sign (`-`) before the `@` will suppress mention of

5027−the author in the citation. This can be useful when the

5028−author is already mentioned in the text:

5029−

5030− Smith says blah [-@smith04].

5031−

5032−You can also write an author-in-text citation, by omitting the

5033−square brackets:

5034−

5035− @smith04 says blah.

5036−

5037− @smith04 [p. 33] says blah.

5038−

5039−This will cause the author's name to be rendered, followed by

5040−the bibliographical details. Use this form when you want to

5041−make the citation the subject of a sentence.

5042−

5043−When you are using a note style, it is usually better to let

5044−citeproc create the footnotes from citations rather than writing

5045−an explicit note. If you do write an explicit note that

5046−contains a citation, note that normal citations will be put in

5047−parentheses, while author-in-text citations will not. For

5048−this reason, it is sometimes preferable to use the

5049−author-in-text style inside notes when using a note style.

5050−

5051−[CSL user documentation]: https://citationstyles.org/authors/

5052−[CSL]: https://docs.citationstyles.org/en/stable/specification.html

5053−[CSL markup specs]: https://docs.citationstyles.org/en/1.0/release-notes.html#rich-text-markup-within-fields

5054−[Chicago Manual of Style]: https://chicagomanualofstyle.org

5055−[Citation Style Language]: https://citationstyles.org

5056−[Zotero Style Repository]: https://www.zotero.org/styles

5057−[finding and editing styles]: https://citationstyles.org/authors/

5058−[CSL locale files]: https://github.com/citation-style-language/locales

5059−

5060−## Non-default extensions

5061−

5062−The following Markdown syntax extensions are not enabled by default

5063−in pandoc, but may be enabled by adding `+EXTENSION` to the format

5064−name, where `EXTENSION` is the name of the extension. Thus, for

5065−example, `markdown+hard_line_breaks` is Markdown with hard line breaks.

5066−

5067−#### Extension: `rebase_relative_paths` ####

5068−

5069−Rewrite relative paths for Markdown links and images, depending

5070−on the path of the file containing the link or image link. For

5071−each link or image, pandoc will compute the directory of the

5072−containing file, relative to the working directory, and prepend

5073−the resulting path to the link or image path.

5074−

5075−The use of this extension is best understood by example.

5076−Suppose you have a a subdirectory for each chapter of a book,

5077−`chap1`, `chap2`, `chap3`. Each contains a file `text.md` and a

5078−number of images used in the chapter. You would like to have

5079−`` in `chap1/text.md` refer to

5080−`chap1/spider.jpg` and `` in `chap2/text.md`

5081−refer to `chap2/spider.jpg`. To do this, use

5082−

5083− pandoc chap*/*.md -f markdown+rebase_relative_paths

5084−

5085−Without this extension, you would have to use

5086−`` in `chap1/text.md` and

5087−`` in `chap2/text.md`. Links with

5088−relative paths will be rewritten in the same way as images.

5089−

5090−Absolute paths and URLs are not changed. Neither are empty

5091−paths or paths consisting entirely of a fragment, e.g., `#foo`.

5092−

5093−Note that relative paths in reference links and images will

5094−be rewritten relative to the file containing the link

5095−reference definition, not the file containing the reference link

5096−or image itself, if these differ.

5097−

5098−#### Extension: `attributes` ####

5099−

5100−Allows attributes to be attached to any inline or block-level

5101−element. The syntax for the attributes is the same as that

5102−used in [`header_attributes`][Extension: `header_attributes`].

5103−

5104−- Attributes that occur immediately after an inline

5105− element affect that element. If they follow a space, then they

5106− belong to the space. (Hence, this option subsumes

5107− `inline_code_attributes` and `link_attributes`.)

5108−- Attributes that occur immediately before a block

5109− element, on a line by themselves, affect that

5110− element.

5111−- Consecutive attribute specifiers may be used,

5112− either for blocks or for inlines. Their attributes

5113− will be combined.

5114−- Attributes that occur at the end of the text of

5115− a Setext or ATX heading (separated by whitespace

5116− from the text) affect the heading element. (Hence, this

5117− option subsumes `header_attributes`.)

5118−- Attributes that occur after the opening fence

5119− in a fenced code block affect the code block element. (Hence,

5120− this option subsumes `fenced_code_attributes`.)

5121−- Attributes that occur at the end of a reference

5122− link definition affect links that refer to that

5123− definition.

5124−

5125−Note that pandoc's AST does not currently allow attributes

5126−to be attached to arbitrary elements. Hence a Span or Div

5127−container will be added if needed.

5128−

5129−#### Extension: `old_dashes` ####

5130−

5131−Selects the pandoc <= 1.8.2.1 behavior for parsing smart dashes:

5132−`-` before a numeral is an en-dash, and `--` is an em-dash.

5133−This option only has an effect if `smart` is enabled. It is

5134−selected automatically for `textile` input.

5135−

5136−#### Extension: `angle_brackets_escapable` ####

5137−

5138−Allow `<` and `>` to be backslash-escaped, as they can be in

5139−GitHub flavored Markdown but not original Markdown. This is

5140−implied by pandoc's default `all_symbols_escapable`.

5141−

5142−#### Extension: `lists_without_preceding_blankline` ####

5143−

5144−Allow a list to occur right after a paragraph, with no intervening

5145−blank space.

5146−

5147−#### Extension: `four_space_rule` ####

5148−

5149−Selects the pandoc <= 2.0 behavior for parsing lists, so that

5150−four spaces indent are needed for list item continuation

5151−paragraphs.

5152−

5153−#### Extension: `spaced_reference_links` ####

5154−

5155−Allow whitespace between the two components of a reference link,

5156−for example,

5157−

5158− [foo] [bar].

5159−

5160−#### Extension: `hard_line_breaks` ####

5161−

5162−Causes all newlines within a paragraph to be interpreted as hard line

5163−breaks instead of spaces.

5164−

5165−#### Extension: `ignore_line_breaks` ####

5166−

5167−Causes newlines within a paragraph to be ignored, rather than being

5168−treated as spaces or as hard line breaks. This option is intended for

5169−use with East Asian languages where spaces are not used between words,

5170−but text is divided into lines for readability.

5171−

5172−#### Extension: `east_asian_line_breaks` ####

5173−

5174−Causes newlines within a paragraph to be ignored, rather than

5175−being treated as spaces or as hard line breaks, when they occur

5176−between two East Asian wide characters. This is a better choice

5177−than `ignore_line_breaks` for texts that include a mix of East

5178−Asian wide characters and other characters.

5179−

5180−#### Extension: `emoji` ####

5181−

5182−Parses textual emojis like `:smile:` as Unicode emoticons.

5183−

5184−#### Extension: `tex_math_single_backslash` ####

5185−

5186−Causes anything between `\(` and `\)` to be interpreted as inline

5187−TeX math, and anything between `\[` and `\]` to be interpreted

5188−as display TeX math. Note: a drawback of this extension is that

5189−it precludes escaping `(` and `[`.

5190−

5191−#### Extension: `tex_math_double_backslash` ####

5192−

5193−Causes anything between `\\(` and `\\)` to be interpreted as inline

5194−TeX math, and anything between `\\[` and `\\]` to be interpreted

5195−as display TeX math.

5196−

5197−#### Extension: `markdown_attribute` ####

5198−

5199−By default, pandoc interprets material inside block-level tags as Markdown.

5200−This extension changes the behavior so that Markdown is only parsed

5201−inside block-level tags if the tags have the attribute `markdown=1`.

5202−

5203−#### Extension: `mmd_title_block` ####

5204−

5205−Enables a [MultiMarkdown] style title block at the top of

5206−the document, for example:

5207−

5208− Title: My title

5209− Author: John Doe

5210− Date: September 1, 2008

5211− Comment: This is a sample mmd title block, with

5212− a field spanning multiple lines.

5213−

5214−See the MultiMarkdown documentation for details. If `pandoc_title_block` or

5215−`yaml_metadata_block` is enabled, it will take precedence over

5216−`mmd_title_block`.

5217−

5218−#### Extension: `abbreviations` ####

5219−

5220−Parses PHP Markdown Extra abbreviation keys, like

5221−

5222− *[HTML]: Hypertext Markup Language

5223−

5224−Note that the pandoc document model does not support

5225−abbreviations, so if this extension is enabled, abbreviation keys are

5226−simply skipped (as opposed to being parsed as paragraphs).

5227−

5228−#### Extension: `autolink_bare_uris` ####

5229−

5230−Makes all absolute URIs into links, even when not surrounded by

5231−pointy braces `<...>`.

5232−

5233−#### Extension: `mmd_link_attributes` ####

5234−

5235−Parses multimarkdown style key-value attributes on link

5236−and image references. This extension should not be confused with the

5237−[`link_attributes`](#extension-link_attributes) extension.

5238−

5239− This is a reference ![image][ref] with multimarkdown attributes.

5240−

5241− [ref]: https://path.to/image "Image title" width=20px height=30px

5242− id=myId class="myClass1 myClass2"

5243−

5244−#### Extension: `mmd_header_identifiers` ####

5245−

5246−Parses multimarkdown style heading identifiers (in square brackets,

5247−after the heading but before any trailing `#`s in an ATX heading).

5248−

5249−#### Extension: `compact_definition_lists` ####

5250−

5251−Activates the definition list syntax of pandoc 1.12.x and earlier.

5252−This syntax differs from the one described above under [Definition lists]

5253−in several respects:

5254−

5255− - No blank line is required between consecutive items of the

5256− definition list.

5257− - To get a "tight" or "compact" list, omit space between consecutive

5258− items; the space between a term and its definition does not affect

5259− anything.

5260− - Lazy wrapping of paragraphs is not allowed: the entire definition must

5261− be indented four spaces.[^6]

5262−

5263−[^6]: To see why laziness is incompatible with relaxing the requirement

5264− of a blank line between items, consider the following example:

5265−

5266− bar

5267− : definition

5268− foo

5269− : definition

5270−

5271− Is this a single list item with two definitions of "bar," the first of

5272− which is lazily wrapped, or two list items? To remove the ambiguity

5273− we must either disallow lazy wrapping or require a blank line between

5274− list items.

5275−

5276−#### Extension: `gutenberg` ####

5277−

5278−Use [Project Gutenberg] conventions for `plain` output:

5279−all-caps for strong emphasis, surround by underscores

5280−for regular emphasis, add extra blank space around headings.

5281−

5282− [Project Gutenberg]: https://www.gutenberg.org

5283−

5284−#### Extension: `sourcepos` ####

5285−

5286−Include source position attributes when parsing `commonmark`.

5287−For elements that accept attributes, a `data-pos` attribute

5288−is added; other elements are placed in a surrounding

5289−Div or Span elemnet with a `data-pos` attribute.

5290−

5291−## Markdown variants

5292−

5293−In addition to pandoc's extended Markdown, the following Markdown

5294−variants are supported:

5295−

5296−- `markdown_phpextra` (PHP Markdown Extra)

5297−- `markdown_github` (deprecated GitHub-Flavored Markdown)

5298−- `markdown_mmd` (MultiMarkdown)

5299−- `markdown_strict` (Markdown.pl)

5300−- `commonmark` (CommonMark)

5301−- `gfm` (Github-Flavored Markdown)

5302−- `commonmark_x` (CommonMark with many pandoc extensions)

5303−

5304−To see which extensions are supported for a given format,

5305−and which are enabled by default, you can use the command

5306−

5307− pandoc --list-extensions=FORMAT

5308−

5309−where `FORMAT` is replaced with the name of the format.

5310−

5311−Note that the list of extensions for `commonmark`,

5312−`gfm`, and `commonmark_x` are defined relative to default

5313−commonmark. So, for example, `backtick_code_blocks`

5314−does not appear as an extension, since it is enabled by

5315−default and cannot be disabled.

5316−

5317−# Citations

5318−

5319−When the `--citeproc` option is used, pandoc can automatically generate

5320−citations and a bibliography in a number of styles. Basic usage is

5321−

5322− pandoc --citeproc myinput.txt

5323−

5324−To use this feature, you will need to have

5325−

5326−- a document containing citations (see [Extension: `citations`]);

5327−- a source of bibliographic data: either an external bibliography

5328− file or a list of `references` in the document's YAML metadata

5329−- optionally, a [CSL] citation style.

5330−

5331−## Specifying bibliographic data

5332−

5333−You can specify an external bibliography using the

5334−`bibliography` metadata field in a YAML metadata section or the

5335−`--bibliography` command line argument. If you want to use

5336−multiple bibliography files, you can supply multiple

5337−`--bibliography` arguments or set `bibliography` metadata field

5338−to YAML array. A bibliography may have any of these formats:

5339−

5340− Format File extension

5341− ------------ --------------

5342− BibLaTeX .bib

5343− BibTeX .bibtex

5344− CSL JSON .json

5345− CSL YAML .yaml

5346−

5347−Note that `.bib` can be used with both BibTeX and BibLaTeX files;

5348−use the extension `.bibtex` to force interpretation as BibTeX.

5349−

5350−In BibTeX and BibLaTeX databases, pandoc parses LaTeX markup

5351−inside fields such as `title`; in CSL YAML databases, pandoc

5352−Markdown; and in CSL JSON databases, an [HTML-like markup][CSL

5353−markup specs]:

5354−

5355−`<i>...</i>`

5356−: italics

5357−

5358−`<b>...</b>`

5359−: bold

5360−

5361−`<span style="font-variant:small-caps;">...</span>` or `<sc>...</sc>`

5362−: small capitals

5363−

5364−`<sub>...</sub>`

5365−: subscript

5366−

5367−`<sup>...</sup>`

5368−: superscript

5369−

5370−`<span class="nocase">...</span>`

5371−: prevent a phrase from being capitalized as title case

5372−

5373−As an alternative to specifying a bibliography file using

5374−`--bibliography` or the YAML metadata field `bibliography`, you

5375−can include the citation data directly in the `references` field

5376−of the document's YAML metadata. The field should contain an

5377−array of YAML-encoded references, for example:

5378−

5379− ---

5380− references:

5381− - type: article-journal

5382− id: WatsonCrick1953

5383− author:

5384− - family: Watson

5385− given: J. D.

5386− - family: Crick

5387− given: F. H. C.

5388− issued:

5389− date-parts:

5390− - - 1953

5391− - 4

5392− - 25

5393− title: 'Molecular structure of nucleic acids: a structure for

5394− deoxyribose nucleic acid'

5395− title-short: Molecular structure of nucleic acids

5396− container-title: Nature

5397− volume: 171

5398− issue: 4356

5399− page: 737-738

5400− DOI: 10.1038/171737a0

5401− URL: https://www.nature.com/articles/171737a0

5402− language: en-GB

5403− ...

5404−

5405−If both an external bibliography and inline (YAML metadata)

5406−references are provided, both will be used. In case of

5407−conflicting `id`s, the inline references will take precedence.

5408−

5409−Note that `pandoc` can be used to produce such a YAML metadata

5410−section from a BibTeX, BibLaTeX, or CSL JSON bibliography:

5411−

5412− pandoc chem.bib -s -f biblatex -t markdown

5413− pandoc chem.json -s -f csljson -t markdown

5414−

5415−Indeed, `pandoc` can convert between any of these

5416−citation formats:

5417−

5418− pandoc chem.bib -s -f biblatex -t csljson

5419− pandoc chem.yaml -s -f markdown -t biblatex

5420−

5421−Running pandoc on a bibliography file with the `--citeproc`

5422−option will create a formatted bibliography in the format

5423−of your choice:

5424−

5425− pandoc chem.bib -s --citeproc -o chem.html

5426− pandoc chem.bib -s --citeproc -o chem.pdf

5427−

5428−### Capitalization in titles

5429−

5430−If you are using a bibtex or biblatex bibliography, then observe

5431−the following rules:

5432−

5433− - English titles should be in title case. Non-English titles should

5434− be in sentence case, and the `langid` field in biblatex should be

5435− set to the relevant language. (The following values are treated

5436− as English: `american`, `british`, `canadian`, `english`,

5437− `australian`, `newzealand`, `USenglish`, or `UKenglish`.)

5438−

5439− - As is standard with bibtex/biblatex, proper names should be

5440− protected with curly braces so that they won't be lowercased

5441− in styles that call for sentence case. For example:

5442−

5443− title = {My Dinner with {Andre}}

5444−

5445− - In addition, words that should remain lowercase (or camelCase)

5446− should be protected:

5447−

5448− title = {Spin Wave Dispersion on the {nm} Scale}

5449−

5450− Though this is not necessary in bibtex/biblatex, it is necessary

5451− with citeproc, which stores titles internally in sentence case,

5452− and converts to title case in styles that require it. Here we

5453− protect "nm" so that it doesn't get converted to "Nm" at this stage.

5454−

5455−If you are using a CSL bibliography (either JSON or YAML), then observe

5456−the following rules:

5457−

5458− - All titles should be in sentence case.

5459−

5460− - Use the `language` field for non-English titles to prevent their

5461− conversion to title case in styles that call for this. (Conversion

5462− happens only if `language` begins with `en` or is left empty.)

5463−

5464− - Protect words that should not be converted to title case using

5465− this syntax:

5466−

5467− Spin wave dispersion on the <span class="nocase">nm</span> scale

5468−

5469−### Conference Papers, Published vs. Unpublished

5470−

5471−For a formally published conference paper, use the biblatex entry type

5472−`inproceedings` (which will be mapped to CSL `paper-conference`).

5473−

5474−For an unpublished manuscript, use the biblatex entry type

5475−`unpublished` without an `eventtitle` field (this entry type

5476−will be mapped to CSL `manuscript`).

5477−

5478−For a talk, an unpublished conference paper, or a poster

5479−presentation, use the biblatex entry type `unpublished` with an

5480−`eventtitle` field (this entry type will be mapped to CSL

5481−`speech`). Use the biblatex `type` field to indicate the type,

5482−e.g. "Paper", or "Poster". `venue` and `eventdate` may be useful

5483−too, though `eventdate` will not be rendered by most CSL styles.

5484−Note that `venue` is for the event's venue, unlike `location`

5485−which describes the publisher's location; do not use the latter

5486−for an unpublished conference paper.

5487−

5488−

5489−## Specifying a citation style

5490−

5491−Citations and references can be formatted using any style supported by the

5492−[Citation Style Language], listed in the [Zotero Style Repository].

5493−These files are specified using the `--csl` option or the `csl`

5494−(or `citation-style`) metadata field. By default, pandoc will

5495−use the [Chicago Manual of Style] author-date format. (You can

5496−override this default by copying a CSL style of your choice

5497−to `default.csl` in your user data directory.)

5498−The CSL project provides further information on [finding and

5499−editing styles].

5500−

5501−The `--citation-abbreviations` option (or the

5502−`citation-abbreviations` metadata field) may be used to specify

5503−a JSON file containing abbreviations of journals that should be

5504−used in formatted bibliographies when `form="short"` is

5505−specified. The format of the file can be illustrated with an

5506−example:

5507−

5508−

5509− { "default": {

5510− "container-title": {

5511− "Lloyd's Law Reports": "Lloyd's Rep",

5512− "Estates Gazette": "EG",

5513− "Scots Law Times": "SLT"

5514− }

5515− }

5516− }

5517−

5518−

5519−## Citations in note styles

5520−

5521−Pandoc's citation processing is designed to allow you to

5522−move between author-date, numerical, and note styles without

5523−modifying the markdown source. When you're using a note

5524−style, avoid inserting footnotes manually. Instead, insert

5525−citations just as you would in an author-date style---for

5526−example,

5527−

5528− Blah blah [@foo, p. 33].

5529−

5530−The footnote will be created automatically. Pandoc will take

5531−care of removing the space and moving the note before or

5532−after the period, depending on the setting of

5533−`notes-after-punctuation`, as described below in [Other relevant

5534−metadata fields].

5535−

5536−In some cases you may need to put a citation inside a regular

5537−footnote. Normal citations in footnotes (such as `[@foo, p.

5538−33]`) will be rendered in parentheses. In-text citations (such

5539−as `@foo [p. 33]`) will be rendered without parentheses. (A

5540−comma will be added if appropriate.) Thus:

5541−

5542− [^1]: Some studies [@foo; @bar, p. 33] show that

5543− frubulicious zoosnaps are quantical. For a survey

5544− of the literature, see @baz [chap. 1].

5545−

5546−## Raw content in a style

5547−

5548−To include raw content in a prefix, suffix, delimiter, or term,

5549−surround it with these tags indicating the format:

5550−

5551− {{jats}}&lt;ref&gt;{{/jats}}

5552−

5553−Without the tags, the string will be interpreted as a string

5554−and escaped in the output, rather than being passed through raw.

5555−

5556−This feature allows stylesheets to be customized to give

5557−different output for different output formats. However,

5558−stylesheets customized in this way will not be usable

5559−by other CSL implementations.

5560−

5561−

5562−

5563−## Placement of the bibliography

5564−

5565−If the style calls for a list of works cited, it will be placed

5566−in a div with id `refs`, if one exists:

5567−

5568− ::: {#refs}

5569− :::

5570−

5571−Otherwise, it will be placed at the end of the document.

5572−Generation of the bibliography can be suppressed by setting

5573−`suppress-bibliography: true` in the YAML metadata.

5574−

5575−If you wish the bibliography to have a section heading, you can

5576−set `reference-section-title` in the metadata, or put the heading

5577−at the beginning of the div with id `refs` (if you are using it)

5578−or at the end of your document:

5579−

5580− last paragraph...

5581−

5582− # References

5583−

5584−The bibliography will be inserted after this heading. Note that

5585−the `unnumbered` class will be added to this heading, so that the

5586−section will not be numbered.

5587−

5588−## Including uncited items in the bibliography

5589−

5590−If you want to include items in the bibliography without actually

5591−citing them in the body text, you can define a dummy `nocite` metadata

5592−field and put the citations there:

5593−

5594− ---

5595− nocite: |

5596− @item1, @item2

5597− ...

5598−

5599− @item3

5600−

5601−In this example, the document will contain a citation for `item3`

5602−only, but the bibliography will contain entries for `item1`, `item2`, and

5603−`item3`.

5604−

5605−It is possible to create a bibliography with all the citations,

5606−whether or not they appear in the document, by using a wildcard:

5607−

5608− ---

5609− nocite: |

5610− @*

5611− ...

5612−

5613−For LaTeX output, you can also use [`natbib`] or [`biblatex`] to

5614−render the bibliography. In order to do so, specify bibliography

5615−files as outlined above, and add `--natbib` or `--biblatex`

5616−argument to `pandoc` invocation. Bear in mind that bibliography

5617−files have to be in either BibTeX (for `--natbib`)

5618−or BibLaTeX (for `--biblatex`) format.

5619−

5620−## Other relevant metadata fields

5621−

5622−A few other metadata fields affect bibliography formatting:

5623−

5624−`link-citations`

5625−: If true, citations will be

5626− hyperlinked to the corresponding bibliography entries

5627− (for author-date and numerical styles only).

5628−

5629−`lang`

5630−: The `lang` field will affect how the style is localized,

5631− for example in the translation of labels, the use

5632− of quotation marks, and the way items are sorted.

5633− (For backwards compatibility, `locale` may be used instead

5634− of `lang`, but this use is deprecated.)

5635−

5636− A BCP 47 language tag is expected: for example, `en`,

5637− `de`, `en-US`, `fr-CA`, `ug-Cyrl`. The unicode extension

5638− syntax (after `-u-`) may be used to specify options for

5639− collation (sorting) more precisely. Here are some examples:

5640−

5641− - `zh-u-co-pinyin` -- Chinese with the Pinyin collation.

5642− - `es-u-co-trad` -- Spanish with the traditional collation

5643− (with `Ch` sorting after `C`).

5644− - `fr-u-kb` -- French with "backwards" accent sorting

5645− (with `coté` sorting after `côte`).

5646− - `en-US-u-kf-upper` -- English with uppercase letters sorting

5647− before lower (default is lower before upper).

5648−

5649−`notes-after-punctuation`

5650−: If true (the default), pandoc will put footnote citations

5651− after following punctuation. For example, if the source

5652− contains `blah blah [@jones99].`, the result will look like

5653− `blah blah.[^1]`, with the note moved after the period and

5654− the space collapsed. If false, the space will still be

5655− collapsed, but the footnote will not be moved after the

5656− punctuation.

5657−

5658−

5659−# Slide shows

5660−

5661−You can use pandoc to produce an HTML + JavaScript slide presentation

5662−that can be viewed via a web browser. There are five ways to do this,

5663−using [S5], [DZSlides], [Slidy], [Slideous], or [reveal.js].

5664−You can also produce a PDF slide show using LaTeX [`beamer`], or

5665−slides shows in Microsoft [PowerPoint] format.

5666−

5667−Here's the Markdown source for a simple slide show, `habits.txt`:

5668−

5669− % Habits

5670− % John Doe

5671− % March 22, 2005

5672−

5673− # In the morning

5674−

5675− ## Getting up

5676−

5677− - Turn off alarm

5678− - Get out of bed

5679−

5680− ## Breakfast

5681−

5682− - Eat eggs

5683− - Drink coffee

5684−

5685− # In the evening

5686−

5687− ## Dinner

5688−

5689− - Eat spaghetti

5690− - Drink wine

5691−

5692− ------------------

5693−

5694− 

5695−

5696− ## Going to sleep

5697−

5698− - Get in bed

5699− - Count sheep

5700−

5701−To produce an HTML/JavaScript slide show, simply type

5702−

5703− pandoc -t FORMAT -s habits.txt -o habits.html

5704−

5705−where `FORMAT` is either `s5`, `slidy`, `slideous`, `dzslides`, or `revealjs`.

5706−

5707−For Slidy, Slideous, reveal.js, and S5, the file produced by

5708−pandoc with the `-s/--standalone` option embeds a link to

5709−JavaScript and CSS files, which are assumed to be available at

5710−the relative path `s5/default` (for S5), `slideous` (for

5711−Slideous), `reveal.js` (for reveal.js), or at the Slidy website

5712−at `w3.org` (for Slidy). (These paths can be changed by setting

5713−the `slidy-url`, `slideous-url`, `revealjs-url`, or `s5-url`

5714−variables; see [Variables for HTML slides], above.) For

5715−DZSlides, the (relatively short) JavaScript and CSS are included

5716−in the file by default.

5717−

5718−With all HTML slide formats, the `--self-contained` option can

5719−be used to produce a single file that contains all of the data

5720−necessary to display the slide show, including linked scripts,

5721−stylesheets, images, and videos.

5722−

5723−To produce a PDF slide show using beamer, type

5724−

5725− pandoc -t beamer habits.txt -o habits.pdf

5726−

5727−Note that a reveal.js slide show can also be converted to a PDF

5728−by printing it to a file from the browser.

5729−

5730−To produce a Powerpoint slide show, type

5731−

5732− pandoc habits.txt -o habits.pptx

5733−

5734−## Structuring the slide show

5735−

5736−By default, the *slide level* is the highest heading level in

5737−the hierarchy that is followed immediately by content, and not another

5738−heading, somewhere in the document. In the example above, level-1 headings

5739−are always followed by level-2 headings, which are followed by content,

5740−so the slide level is 2. This default can be overridden using

5741−the `--slide-level` option.

5742−

5743−The document is carved up into slides according to the following

5744−rules:

5745−

5746− * A horizontal rule always starts a new slide.

5747−

5748− * A heading at the slide level always starts a new slide.

5749−

5750− * Headings *below* the slide level in the hierarchy create

5751− headings *within* a slide. (In beamer, a "block" will be

5752− created. If the heading has the class `example`, an

5753− `exampleblock` environment will be used; if it has the class

5754− `alert`, an `alertblock` will be used; otherwise a regular

5755− `block` will be used.)

5756−

5757− * Headings *above* the slide level in the hierarchy create

5758− "title slides," which just contain the section title

5759− and help to break the slide show into sections.

5760− Non-slide content under these headings will be included

5761− on the title slide (for HTML slide shows) or in a

5762− subsequent slide with the same title (for beamer).

5763−

5764− * A title page is constructed automatically from the document's title

5765− block, if present. (In the case of beamer, this can be disabled

5766− by commenting out some lines in the default template.)

5767−

5768−These rules are designed to support many different styles of slide show. If

5769−you don't care about structuring your slides into sections and subsections,

5770−you can just use level-1 headings for all each slide. (In that case, level-1

5771−will be the slide level.) But you can also structure the slide show into

5772−sections, as in the example above.

5773−

5774−Note: in reveal.js slide shows, if slide level is 2, a two-dimensional

5775−layout will be produced, with level-1 headings building horizontally

5776−and level-2 headings building vertically. It is not recommended that

5777−you use deeper nesting of section levels with reveal.js.

5778−

5779−## Incremental lists

5780−

5781−By default, these writers produce lists that display "all at once."

5782−If you want your lists to display incrementally (one item at a time),

5783−use the `-i` option. If you want a particular list to depart from the

5784−default, put it in a `div` block with class `incremental` or

5785−`nonincremental`. So, for example, using the `fenced div` syntax, the

5786−following would be incremental regardless of the document default:

5787−

5788− ::: incremental

5789−

5790− - Eat spaghetti

5791− - Drink wine

5792−

5793− :::

5794−

5795−or

5796−

5797− ::: nonincremental

5798−

5799− - Eat spaghetti

5800− - Drink wine

5801−

5802− :::

5803−

5804−While using `incremental` and `nonincremental` divs are the

5805−recommended method of setting incremental lists on a per-case basis,

5806−an older method is also supported: putting lists inside a blockquote

5807−will depart from the document default (that is, it will display

5808−incrementally without the `-i` option and all at once with the `-i`

5809−option):

5810−

5811− > - Eat spaghetti

5812− > - Drink wine

5813−

5814−Both methods allow incremental and nonincremental lists to be mixed

5815−in a single document.

5816−

5817−Note: Neither the `-i/--incremental` option nor any of the

5818−methods described here currently works for PowerPoint output.

5819−

5820−## Inserting pauses

5821−

5822−You can add "pauses" within a slide by including a paragraph containing

5823−three dots, separated by spaces:

5824−

5825− # Slide with a pause

5826−

5827− content before the pause

5828−

5829− . . .

5830−

5831− content after the pause

5832−

5833−Note: this feature is not yet implemented for PowerPoint output.

5834−

5835−## Styling the slides

5836−

5837−You can change the style of HTML slides by putting customized CSS files

5838−in `$DATADIR/s5/default` (for S5), `$DATADIR/slidy` (for Slidy),

5839−or `$DATADIR/slideous` (for Slideous),

5840−where `$DATADIR` is the user data directory (see `--data-dir`, above).

5841−The originals may be found in pandoc's system data directory (generally

5842−`$CABALDIR/pandoc-VERSION/s5/default`). Pandoc will look there for any

5843−files it does not find in the user data directory.

5844−

5845−For dzslides, the CSS is included in the HTML file itself, and may

5846−be modified there.

5847−

5848−All [reveal.js configuration options] can be set through variables.

5849−For example, themes can be used by setting the `theme` variable:

5850−

5851− -V theme=moon

5852−

5853−Or you can specify a custom stylesheet using the `--css` option.

5854−

5855−To style beamer slides, you can specify a `theme`, `colortheme`,

5856−`fonttheme`, `innertheme`, and `outertheme`, using the `-V` option:

5857−

5858− pandoc -t beamer habits.txt -V theme:Warsaw -o habits.pdf

5859−

5860−Note that heading attributes will turn into slide attributes

5861−(on a `<div>` or `<section>`) in HTML slide formats, allowing you

5862−to style individual slides. In beamer, the only heading attribute

5863−that affects slides is the `allowframebreaks` class, which sets the

5864−`allowframebreaks` option, causing multiple slides to be created

5865−if the content overfills the frame. This is recommended especially for

5866−bibliographies:

5867−

5868− # References {.allowframebreaks}

5869−

5870−## Speaker notes

5871−

5872−Speaker notes are supported in reveal.js and PowerPoint (pptx)

5873−output. You can add notes to your Markdown document thus:

5874−

5875− ::: notes

5876−

5877− This is my note.

5878−

5879− - It can contain Markdown

5880− - like this list

5881−

5882− :::

5883−

5884−To show the notes window in reveal.js, press `s` while viewing the

5885−presentation. Speaker notes in PowerPoint will be available, as usual,

5886−in handouts and presenter view.

5887−

5888−Notes are not yet supported for other slide formats, but the notes

5889−will not appear on the slides themselves.

5890−

5891−## Columns

5892−

5893−To put material in side by side columns, you can use a native

5894−div container with class `columns`, containing two or more div

5895−containers with class `column` and a `width` attribute:

5896−

5897− :::::::::::::: {.columns}

5898− ::: {.column width="40%"}

5899− contents...

5900− :::

5901− ::: {.column width="60%"}

5902− contents...

5903− :::

5904− ::::::::::::::

5905−

5906−### Additional columns attributes in beamer

5907−

5908−The div containers with classes `columns` and `column` can optionally have

5909−an `align` attribute.

5910−The class `columns` can optionally have a `totalwidth` attribute or an

5911−`onlytextwidth` class.

5912−

5913− :::::::::::::: {.columns align=center totalwidth=8em}

5914− ::: {.column width="40%"}

5915− contents...

5916− :::

5917− ::: {.column width="60%" align=bottom}

5918− contents...

5919− :::

5920− ::::::::::::::

5921−

5922−The `align` attributes on `columns` and `column` can be used with the

5923−values `top`, `top-baseline`, `center` and `bottom` to vertically align

5924−the columns. It defaults to `top` in `columns`.

5925−

5926−The `totalwidth` attribute limits the width of the columns to the given value.

5927−

5928− :::::::::::::: {.columns align=top .onlytextwidth}

5929− ::: {.column width="40%" align=center}

5930− contents...

5931− :::

5932− ::: {.column width="60%"}

5933− contents...

5934− :::

5935− ::::::::::::::

5936−

5937−The class `onlytextwidth` sets the `totalwidth` to `\textwidth`.

5938−

5939−See Section 12.7 of the [Beamer User's Guide] for more details.

5940−

5941−## Frame attributes in beamer

5942−

5943−Sometimes it is necessary to add the LaTeX `[fragile]` option to

5944−a frame in beamer (for example, when using the `minted` environment).

5945−This can be forced by adding the `fragile` class to the heading

5946−introducing the slide:

5947−

5948− # Fragile slide {.fragile}

5949−

5950−All of the other frame attributes described in Section 8.1 of

5951−the [Beamer User's Guide] may also be used: `allowdisplaybreaks`,

5952−`allowframebreaks`, `b`, `c`, `t`, `environment`, `label`, `plain`,

5953−`shrink`, `standout`, `noframenumbering`.

5954−

5955−## Background in reveal.js and beamer

5956−

5957−Background images can be added to self-contained reveal.js slideshows and

5958−to beamer slideshows.

5959−

5960−For the same image on every slide, use the configuration

5961−option `background-image` either in the YAML metadata block

5962−or as a command-line variable. (There are no other options in

5963−beamer and the rest of this section concerns reveal.js slideshows.)

5964−

5965−For reveal.js, you can instead use the reveal.js-native option

5966−`parallaxBackgroundImage`. You can also set `parallaxBackgroundHorizontal`

5967−and `parallaxBackgroundVertical` the same way and must also set

5968−`parallaxBackgroundSize` to have your values take effect.

5969−

5970−To set an image for a particular reveal.js slide, add

5971−`{data-background-image="/path/to/image"}`

5972−to the first slide-level heading on the slide (which may even be empty).

5973−

5974−In reveal.js's overview mode, the parallaxBackgroundImage will show up

5975−only on the first slide.

5976−

5977−Other reveal.js background settings also work on individual slides, including

5978−`data-background-size`, `data-background-repeat`, `data-background-color`,

5979−`data-transition`, and `data-transition-speed`.

5980−

5981−To add a background image to the automatically generated title slide, use the

5982−`title-slide-attributes` variable in the YAML metadata block. It must contain

5983−a map of attribute names and values.

5984−

5985−See the [reveal.js documentation](https://revealjs.com/backgrounds/) for more

5986−details.

5987−

5988−For example in reveal.js:

5989−

5990−```

5991−---

5992−title: My Slideshow

5993−parallaxBackgroundImage: /path/to/my/background_image.png

5994−title-slide-attributes:

5995− data-background-image: /path/to/title_image.png

5996− data-background-size: contain

5997−---

5998−

5999−## Slide One

6000−

6001−Slide 1 has background_image.png as its background.

6002−

6003−## {data-background-image="/path/to/special_image.jpg"}

6004−

6005−Slide 2 has a special image for its background, even though the heading has no content.

6006−```

6007−

6008−# EPUBs

6009−

6010−## EPUB Metadata

6011−

6012−EPUB metadata may be specified using the `--epub-metadata` option, but

6013−if the source document is Markdown, it is better to use a [YAML metadata

6014−block][Extension: `yaml_metadata_block`]. Here is an example:

6015−

6016− ---

6017− title:

6018− - type: main

6019− text: My Book

6020− - type: subtitle

6021− text: An investigation of metadata

6022− creator:

6023− - role: author

6024− text: John Smith

6025− - role: editor

6026− text: Sarah Jones

6027− identifier:

6028− - scheme: DOI

6029− text: doi:10.234234.234/33

6030− publisher: My Press

6031− rights: © 2007 John Smith, CC BY-NC

6032− ibooks:

6033− version: 1.3.4

6034− ...

6035−

6036−The following fields are recognized:

6037−

6038−`identifier`

6039− ~ Either a string value or an object with fields `text` and

6040− `scheme`. Valid values for `scheme` are `ISBN-10`,

6041− `GTIN-13`, `UPC`, `ISMN-10`, `DOI`, `LCCN`, `GTIN-14`,

6042− `ISBN-13`, `Legal deposit number`, `URN`, `OCLC`,

6043− `ISMN-13`, `ISBN-A`, `JP`, `OLCC`.

6044−

6045−`title`

6046− ~ Either a string value, or an object with fields `file-as` and

6047− `type`, or a list of such objects. Valid values for `type` are

6048− `main`, `subtitle`, `short`, `collection`, `edition`, `extended`.

6049−

6050−`creator`

6051− ~ Either a string value, or an object with fields `role`, `file-as`,

6052− and `text`, or a list of such objects. Valid values for `role` are

6053− [MARC relators], but

6054− pandoc will attempt to translate the human-readable versions

6055− (like "author" and "editor") to the appropriate marc relators.

6056−

6057−`contributor`

6058− ~ Same format as `creator`.

6059−

6060−`date`

6061− ~ A string value in `YYYY-MM-DD` format. (Only the year is necessary.)

6062− Pandoc will attempt to convert other common date formats.

6063−

6064−`lang` (or legacy: `language`)

6065− ~ A string value in [BCP 47] format. Pandoc will default to the local

6066− language if nothing is specified.

6067−

6068−`subject`

6069− ~ A string value or a list of such values.

6070−

6071−`description`

6072− ~ A string value.

6073−

6074−`type`

6075− ~ A string value.

6076−

6077−`format`

6078− ~ A string value.

6079−

6080−`relation`

6081− ~ A string value.

6082−

6083−`coverage`

6084− ~ A string value.

6085−

6086−`rights`

6087− ~ A string value.

6088−

6089−`belongs-to-collection`

6090− ~ A string value. identifies the name of a collection to which

6091− the EPUB Publication belongs.

6092−

6093−`group-position`

6094− ~ The `group-position` field indicates the numeric position in which

6095− the EPUB Publication belongs relative to other works belonging to

6096− the same `belongs-to-collection` field.

6097−

6098−`cover-image`

6099− ~ A string value (path to cover image).

6100−

6101−`css` (or legacy: `stylesheet`)

6102− ~ A string value (path to CSS stylesheet).

6103−

6104−`page-progression-direction`

6105− ~ Either `ltr` or `rtl`. Specifies the `page-progression-direction`

6106− attribute for the [`spine` element].

6107−

6108−`ibooks`

6109− ~ iBooks-specific metadata, with the following fields:

6110−

6111− - `version`: (string)

6112− - `specified-fonts`: `true`|`false` (default `false`)

6113− - `ipad-orientation-lock`: `portrait-only`|`landscape-only`

6114− - `iphone-orientation-lock`: `portrait-only`|`landscape-only`

6115− - `binding`: `true`|`false` (default `true`)

6116− - `scroll-axis`: `vertical`|`horizontal`|`default`

6117−

6118−[MARC relators]: https://loc.gov/marc/relators/relaterm.html

6119−[`spine` element]: http://idpf.org/epub/301/spec/epub-publications.html#sec-spine-elem

6120−

6121−## The `epub:type` attribute

6122−

6123−For `epub3` output, you can mark up the heading that corresponds to an EPUB

6124−chapter using the [`epub:type` attribute][epub-type]. For example, to set

6125−the attribute to the value `prologue`, use this markdown:

6126−

6127− # My chapter {epub:type=prologue}

6128−

6129−Which will result in:

6130−

6131− <body epub:type="frontmatter">

6132− <section epub:type="prologue">

6133− <h1>My chapter</h1>

6134−

6135−Pandoc will output `<body epub:type="bodymatter">`, unless

6136−you use one of the following values, in which case either

6137−`frontmatter` or `backmatter` will be output.

6138−

6139−`epub:type` of first section `epub:type` of body

6140−---------------------------- ------------------

6141−prologue frontmatter

6142−abstract frontmatter

6143−acknowledgments frontmatter

6144−copyright-page frontmatter

6145−dedication frontmatter

6146−credits frontmatter

6147−keywords frontmatter

6148−imprint frontmatter

6149−contributors frontmatter

6150−other-credits frontmatter

6151−errata frontmatter

6152−revision-history frontmatter

6153−titlepage frontmatter

6154−halftitlepage frontmatter

6155−seriespage frontmatter

6156−foreword frontmatter

6157−preface frontmatter

6158−appendix backmatter

6159−colophon backmatter

6160−bibliography backmatter

6161−index backmatter

6162−

6163−[epub-type]: http://www.idpf.org/epub/31/spec/epub-contentdocs.html#sec-epub-type-attribute

6164−

6165−## Linked media

6166−

6167−By default, pandoc will download media referenced from any `<img>`, `<audio>`,

6168−`<video>` or `<source>` element present in the generated EPUB,

6169−and include it in the EPUB container, yielding a completely

6170−self-contained EPUB. If you want to link to external media resources

6171−instead, use raw HTML in your source and add `data-external="1"` to the tag

6172−with the `src` attribute. For example:

6173−

6174− <audio controls="1">

6175− <source src="https://example.com/music/toccata.mp3"

6176− data-external="1" type="audio/mpeg">

6177− </source>

6178− </audio>

6179−

6180−# Jupyter notebooks

6181−

6182−When creating a [Jupyter notebook], pandoc will try to infer the

6183−notebook structure. Code blocks with the class `code` will be

6184−taken as code cells, and intervening content will be taken as

6185−Markdown cells. Attachments will automatically be created for

6186−images in Markdown cells. Metadata will be taken from the

6187−`jupyter` metadata field. For example:

6188−

6189−````

6190−---

6191−title: My notebook

6192−jupyter:

6193− nbformat: 4

6194− nbformat_minor: 5

6195− kernelspec:

6196− display_name: Python 2

6197− language: python

6198− name: python2

6199− language_info:

6200− codemirror_mode:

6201− name: ipython

6202− version: 2

6203− file_extension: ".py"

6204− mimetype: "text/x-python"

6205− name: "python"

6206− nbconvert_exporter: "python"

6207− pygments_lexer: "ipython2"

6208− version: "2.7.15"

6209−---

6210−

6211−# Lorem ipsum

6212−

6213−**Lorem ipsum** dolor sit amet, consectetur adipiscing elit. Nunc luctus

6214−bibendum felis dictum sodales.

6215−

6216−``` code

6217−print("hello")

6218−```

6219−

6220−## Pyout

6221−

6222−``` code

6223−from IPython.display import HTML

6224−HTML("""

6225−<script>

6226−console.log("hello");

6227−</script>

6228−<b>HTML</b>

6229−""")

6230−```

6231−

6232−## Image

6233−

6234−This image  will be

6235−included as a cell attachment.

6236−````

6237−

6238−If you want to add cell attributes, group cells differently, or

6239−add output to code cells, then you need to include divs to

6240−indicate the structure. You can use either [fenced

6241−divs][Extension: `fenced_divs`] or [native divs][Extension:

6242−`native_divs`] for this. Here is an example:

6243−

6244−````

6245−:::::: {.cell .markdown}

6246−# Lorem

6247−

6248−**Lorem ipsum** dolor sit amet, consectetur adipiscing elit. Nunc luctus

6249−bibendum felis dictum sodales.

6250−::::::

6251−

6252−:::::: {.cell .code execution_count=1}

6253−``` {.python}

6254−print("hello")

6255−```

6256−

6257−::: {.output .stream .stdout}

6258−```

6259−hello

6260−```

6261−:::

6262−::::::

6263−

6264−:::::: {.cell .code execution_count=2}

6265−``` {.python}

6266−from IPython.display import HTML

6267−HTML("""

6268−<script>

6269−console.log("hello");

6270−</script>

6271−<b>HTML</b>

6272−""")

6273−```

6274−

6275−::: {.output .execute_result execution_count=2}

6276−```{=html}

6277−<script>

6278−console.log("hello");

6279−</script>

6280−<b>HTML</b>

6281−hello

6282−```

6283−:::

6284−::::::

6285−````

6286−

6287−If you include raw HTML or TeX in an output cell, use the

6288−[raw attribute][Extension: `fenced_attribute`], as shown

6289−in the last cell of the example above. Although pandoc can

6290−process "bare" raw HTML and TeX, the result is often

6291−interspersed raw elements and normal textual elements, and

6292−in an output cell pandoc expects a single, connected raw

6293−block. To avoid using raw HTML or TeX except when

6294−marked explicitly using raw attributes, we recommend

6295−specifying the extensions `-raw_html-raw_tex+raw_attribute` when

6296−translating between Markdown and ipynb notebooks.

6297−

6298−Note that options and extensions that affect reading and

6299−writing of Markdown will also affect Markdown cells in ipynb

6300−notebooks. For example, `--wrap=preserve` will preserve

6301−soft line breaks in Markdown cells; `--atx-headers` will

6302−cause ATX-style headings to be used; and `--preserve-tabs` will

6303−prevent tabs from being turned to spaces.

6304−

6305−# Syntax highlighting

6306−

6307−Pandoc will automatically highlight syntax in [fenced code blocks] that

6308−are marked with a language name. The Haskell library [skylighting] is

6309−used for highlighting. Currently highlighting is supported only for

6310−HTML, EPUB, Docx, Ms, and LaTeX/PDF output. To see a list of language names

6311−that pandoc will recognize, type `pandoc --list-highlight-languages`.

6312−

6313−The color scheme can be selected using the `--highlight-style` option.

6314−The default color scheme is `pygments`, which imitates the default color

6315−scheme used by the Python library pygments (though pygments is not actually

6316−used to do the highlighting). To see a list of highlight styles,

6317−type `pandoc --list-highlight-styles`.

6318−

6319−If you are not satisfied with the predefined styles, you can

6320−use `--print-highlight-style` to generate a JSON `.theme` file which

6321−can be modified and used as the argument to `--highlight-style`. To

6322−get a JSON version of the `pygments` style, for example:

6323−

6324− pandoc --print-highlight-style pygments > my.theme

6325−

6326−Then edit `my.theme` and use it like this:

6327−

6328− pandoc --highlight-style my.theme

6329−

6330−If you are not satisfied with the built-in highlighting, or you

6331−want highlight a language that isn't supported, you can use the

6332−`--syntax-definition` option to load a [KDE-style XML syntax definition

6333−file](https://docs.kde.org/stable5/en/kate/katepart/highlight.html).

6334−Before writing your own, have a look at KDE's [repository of syntax

6335−definitions](https://github.com/KDE/syntax-highlighting/tree/master/data/syntax).

6336−

6337−To disable highlighting, use the `--no-highlight` option.

6338−

6339−[skylighting]: https://github.com/jgm/skylighting

6340−

6341−# Custom Styles

6342−

6343−Custom styles can be used in the docx and ICML formats.

6344−

6345−## Output

6346−

6347−By default, pandoc's docx and ICML output applies a predefined set of styles

6348−for blocks such as paragraphs and block quotes, and uses largely default

6349−formatting (italics, bold) for inlines. This will work for most

6350−purposes, especially alongside a `reference.docx` file. However, if you

6351−need to apply your own styles to blocks, or match a preexisting set of

6352−styles, pandoc allows you to define custom styles for blocks and text

6353−using `div`s and `span`s, respectively.

6354−

6355−If you define a `div` or `span` with the attribute `custom-style`,

6356−pandoc will apply your specified style to the contained elements (with

6357−the exception of elements whose function depends on a style, like

6358−headings, code blocks, block quotes, or links). So, for example, using

6359−the `bracketed_spans` syntax,

6360−

6361− [Get out]{custom-style="Emphatically"}, he said.

6362−

6363−would produce a docx file with "Get out" styled with character

6364−style `Emphatically`. Similarly, using the `fenced_divs` syntax,

6365−

6366− Dickinson starts the poem simply:

6367−

6368− ::: {custom-style="Poetry"}

6369− | A Bird came down the Walk---

6370− | He did not know I saw---

6371− :::

6372−

6373−would style the two contained lines with the `Poetry` paragraph style.

6374−

6375−For docx output, styles will be defined in the output file as inheriting

6376−from normal text, if the styles are not yet in your reference.docx.

6377−If they are already defined, pandoc will not alter the definition.

6378−

6379−This feature allows for greatest customization in conjunction with

6380−[pandoc filters]. If you want all paragraphs after block quotes to be

6381−indented, you can write a filter to apply the styles necessary. If you

6382−want all italics to be transformed to the `Emphasis` character style

6383−(perhaps to change their color), you can write a filter which will

6384−transform all italicized inlines to inlines within an `Emphasis`

6385−custom-style `span`.

6386−

6387−For docx output, you don't need to enable any extensions for

6388−custom styles to work.

6389−

6390−[pandoc filters]: https://pandoc.org/filters.html

6391−

6392−## Input

6393−

6394−The docx reader, by default, only reads those styles that it can

6395−convert into pandoc elements, either by direct conversion or

6396−interpreting the derivation of the input document's styles.

6397−

6398−By enabling the [`styles` extension](#ext-styles) in the docx reader

6399−(`-f docx+styles`), you can produce output that maintains the styles

6400−of the input document, using the `custom-style` class. Paragraph

6401−styles are interpreted as divs, while character styles are interpreted

6402−as spans.

6403−

6404−For example, using the `custom-style-reference.docx` file in the test

6405−directory, we have the following different outputs:

6406−

6407−Without the `+styles` extension:

6408−

6409− $ pandoc test/docx/custom-style-reference.docx -f docx -t markdown

6410− This is some text.

6411−

6412− This is text with an *emphasized* text style. And this is text with a

6413− **strengthened** text style.

6414−

6415− > Here is a styled paragraph that inherits from Block Text.

6416−

6417−And with the extension:

6418−

6419− $ pandoc test/docx/custom-style-reference.docx -f docx+styles -t markdown

6420−

6421− ::: {custom-style="First Paragraph"}

6422− This is some text.

6423− :::

6424−

6425− ::: {custom-style="Body Text"}

6426− This is text with an [emphasized]{custom-style="Emphatic"} text style.

6427− And this is text with a [strengthened]{custom-style="Strengthened"}

6428− text style.

6429− :::

6430−

6431− ::: {custom-style="My Block Style"}

6432− > Here is a styled paragraph that inherits from Block Text.

6433− :::

6434−

6435−With these custom styles, you can use your input document as a

6436−reference-doc while creating docx output (see below), and maintain the

6437−same styles in your input and output files.

6438−

6439−# Custom writers

6440−

6441−Pandoc can be extended with custom writers written in [Lua]. (Pandoc

6442−includes a Lua interpreter, so Lua need not be installed separately.)

6443−

6444−To use a custom writer, simply specify the path to the Lua script

6445−in place of the output format. For example:

6446−

6447− pandoc -t data/sample.lua

6448−

6449−Creating a custom writer requires writing a Lua function for each

6450−possible element in a pandoc document. To get a documented example

6451−which you can modify according to your needs, do

6452−

6453− pandoc --print-default-data-file sample.lua

6454−

6455−Note that custom writers have no default template. If you want

6456−to use `--standalone` with a custom writer, you will need to

6457−specify a template manually using `--template` or add a new

6458−default template with the name

6459−`default.NAME_OF_CUSTOM_WRITER.lua` to the `templates`

6460−subdirectory of your user data directory (see [Templates]).

6461−

6462−[Lua]: https://www.lua.org

6463−

6464−# Reproducible builds

6465−

6466−Some of the document formats pandoc targets (such as EPUB,

6467−docx, and ODT) include build timestamps in the generated document.

6468−That means that the files generated on successive builds will

6469−differ, even if the source does not. To avoid this, set the

6470−`SOURCE_DATE_EPOCH` environment variable, and the timestamp will

6471−be taken from it instead of the current time.

6472−`SOURCE_DATE_EPOCH` should contain an integer unix timestamp

6473−(specifying the number of second since midnight UTC January 1, 1970).

6474−

6475−Some document formats also include a unique identifier. For

6476−EPUB, this can be set explicitly by setting the `identifier`

6477−metadata field (see [EPUB Metadata], above).

6478−

6479−# A note on security

6480−

6481−If you use pandoc to convert user-contributed content in a web

6482−application, here are some things to keep in mind:

6483−

6484−1. Although pandoc itself will not create or modify any files other

6485− than those you explicitly ask it create (with the exception

6486− of temporary files used in producing PDFs), a filter or custom

6487− writer could in principle do anything on your file system. Please

6488− audit filters and custom writers very carefully before using them.

6489−

6490−2. If your application uses pandoc as a Haskell library (rather than

6491− shelling out to the executable), it is possible to use it in a mode

6492− that fully isolates pandoc from your file system, by running the

6493− pandoc operations in the `PandocPure` monad. See the document

6494− [Using the pandoc API](https://pandoc.org/using-the-pandoc-api.html)

6495− for more details.

6496−

6497−3. Pandoc's parsers can exhibit pathological performance on some

6498− corner cases. It is wise to put any pandoc operations under

6499− a timeout, to avoid DOS attacks that exploit these issues.

6500− If you are using the pandoc executable, you can add the

6501− command line options `+RTS -M512M -RTS` (for example) to limit

6502− the heap size to 512MB.

6503−

6504−4. The HTML generated by pandoc is not guaranteed to be safe.

6505− If `raw_html` is enabled for the Markdown input, users can

6506− inject arbitrary HTML. Even if `raw_html` is disabled,

6507− users can include dangerous content in URLs and attributes.

6508− To be safe, you should run all the generated HTML through

6509− an HTML sanitizer.

6510−

6511−# Authors

6512−

6513−Copyright 2006--2021 John MacFarlane (jgm@berkeley.edu). Released

6514−under the [GPL], version 2 or greater. This software carries no

6515−warranty of any kind. (See COPYRIGHT for full copyright and

6516−warranty notices.) For a full list of contributors, see the file

6517−AUTHORS.md in the pandoc source code.

6518−

6519−[GPL]: https://www.gnu.org/copyleft/gpl.html "GNU General Public License"

6520−[YAML]: https://yaml.org/spec/1.2/spec.html "YAML v1.2 Spec"

Makefile+34−131

@@ -1,148 +1,51 @@

1−version?=$(shell grep '^[Vv]ersion:' pandoc.cabal | awk '{print $$2;}')

2−pandoc=$(shell find dist -name pandoc -type f -exec ls -t {} \; | head -1)

3−SOURCEFILES?=$(shell git ls-tree -r master --name-only | grep "\.hs$$")

4−BRANCH?=master

5−ARCH=$(shell uname -m)

6−DOCKERIMAGE=registry.gitlab.b-data.ch/ghc/ghc4pandoc:8.10.4

7−COMMIT=$(shell git rev-parse --short HEAD)

8−TIMESTAMP=$(shell date "+%Y%m%d_%H%M")

9−LATESTBENCH=$(word 1,$(shell ls -t bench_*.csv 2>/dev/null))

10−BASELINE?=$(LATESTBENCH)

11−ifeq ($(BASELINE),)

12−BASELINECMD=

13−else

14−BASELINECMD=--baseline $(BASELINE)

15−endif

16−GHCOPTS=-fdiagnostics-color=always -j4 +RTS -A8m -RTS

17−WEBSITE=../../web/pandoc.org

18−REVISION?=1

19−# For gauge:

20−# BENCHARGS?=--small --ci=0.90 --match=pattern $(PATTERN)

21−# For tasty-bench:

22−BENCHARGS?=--csv bench_$(TIMESTAMP).csv $(BASELINECMD) --timeout=6 +RTS -T -RTS $(if $(PATTERN),--pattern "$(PATTERN)",)

1+# This Makefile is for development only. It requires cabal-dev.

2+# To get started, do 'make prep' and then 'make' or 'make quick'.

233

24−quick:

25− stack install --ghc-options='$(GHCOPTS)' --install-ghc --flag 'pandoc:embed_data_files' --fast --test --ghc-options='$(GHCOPTS)' --test-arguments='-j4 --hide-successes $(TESTARGS)'

26−

27−quick-cabal:

28− cabal new-configure . --ghc-options '$(GHCOPTS)' --disable-optimization --enable-tests

29− cabal new-build -j4 . --disable-optimization

30− cabal new-run test-pandoc --disable-optimization -- --hide-successes $(TESTARGS)

4+.PHONY: prep submodules all quick bench clean veryclean install sdist

315

32−full-cabal:

33− cabal new-configure . --ghc-options '$(GHCOPTS)' --flags '+embed_data_files +trypandoc' --enable-tests --enable-benchmarks

34− cabal new-build . --disable-optimization

35− cabal new-run test-pandoc --disable-optimization -- --hide-successes $(TESTARGS)

6+all:

7+ cabal-dev configure --enable-tests --enable-benchmarks && cabal-dev build

368

37−full:

38− stack install --flag 'pandoc:embed_data_files' --flag 'pandoc:trypandoc' --bench --no-run-benchmarks --test --test-arguments='-j4 --hide-successes' --ghc-options '-Wall -Werror -fno-warn-unused-do-bind -O0 $(GHCOPTS)'

9+test: all

10+ cabal test

3911

40−ghci:

41− stack ghci --flag 'pandoc:embed_data_files'

12+prof:

13+ cabal-dev configure --disable-tests --enable-library-profiling --enable-executable-profiling && cabal-dev build

4214

43−haddock:

44− stack haddock

15+prep: submodules pandoc-types citeproc-hs

16+ (cabal-dev --version || (cabal update && cabal install cabal-dev)) && \

17+ cabal-dev update && \

18+ cabal-dev install-deps --enable-library-profiling --enable-tests --enable-benchmarks

4519

46−# Note: to accept current results of golden tests,

47−# make test TESTARGS='--accept'

48−test:

49− stack test --flag 'pandoc:embed_data_files' --fast --test-arguments='-j4 --hide-successes $(TESTARGS)' --ghc-options '$(GHCOPTS)'

20+submodules:

21+ git submodule update --init

5022

51−ghcid:

52− ghcid -c "stack repl --flag 'pandoc:embed_data_files'"

23+quick:

24+ cabal-dev configure --enable-tests --disable-optimization && cabal-dev build

5325

54−ghcid-test:

55− ghcid -c "stack repl --ghc-options=-XNoImplicitPrelude --flag 'pandoc:embed_data_files' --ghci-options=-fobject-code pandoc:lib pandoc:test-pandoc"

26+relocatable:

27+ cabal-dev configure -fembed_data_files && cabal-dev build

5628

5729bench:

58− stack bench \

59− --ghc-options '$(GHCOPTS)' \

60− --benchmark-arguments='$(BENCHARGS)' 2>&1 | \

61− tee "bench_latest.txt"

62−

63−reformat:

64− for f in $(SOURCEFILES); do echo $$f; stylish-haskell -i $$f ; done

65−

66−lint: hlint fix_spacing

67−

68−hlint:

69− for f in $(SOURCEFILES); do echo $$f; hlint --verbose --refactor --refactor-options='-s -o -' $$f; done

70−

71−fix_spacing:

72− # Fix trailing newlines and spaces at ends of lines

73− for f in $(SOURCEFILES); do printf '%s\n' "`cat $$f`" | sed -e 's/ *$$//' > $$f.tmp; mv $$f.tmp $$f; done

74−

75−changes_github:

76− pandoc --filter tools/extract-changes.hs changelog.md -t gfm --wrap=none --template tools/changes_template.html | sed -e 's/\\#/#/g' | pbcopy

77−

78−dist: man/pandoc.1

79− cabal sdist

80− rm -rf "pandoc-${version}"

81− tar xvzf dist/pandoc-${version}.tar.gz

82− cd pandoc-${version}

83− stack setup && stack test && cd .. && rm -rf "pandoc-${version}"

84−

85−check: checkdocs check-cabal

86−

87−checkdocs:

88− ! grep -q -n -e "\t" MANUAL.txt changelog.md

89−

90−debpkg: man/pandoc.1

91− docker run -v `pwd`:/mnt \

92− -v `pwd`/linux/artifacts:/artifacts \

93− --user $(id -u):$(id -g) \

94− -e REVISION=$(REVISION) \

95− -w /mnt \

96− --memory=0 \

97− --rm \

98− $(DOCKERIMAGE) \

99− bash \

100− /mnt/linux/make_artifacts.sh 2>&1 > docker.log

101−

102−man/pandoc.1: MANUAL.txt man/pandoc.1.before man/pandoc.1.after

103− pandoc $< -f markdown -t man -s \

104− --lua-filter man/manfilter.lua \

105− --include-before-body man/pandoc.1.before \

106− --include-after-body man/pandoc.1.after \

107− --metadata author="" \

108− --variable footer="pandoc $(version)" \

109− -o $@

110−

111−README.md: README.template MANUAL.txt tools/update-readme.lua

112− pandoc --lua-filter tools/update-readme.lua \

113− --reference-location=section -t gfm $< -o $@

114−

115−download_stats:

116− curl https://api.github.com/repos/jgm/pandoc/releases | \

117− jq -r '.[] | .assets | .[] | "\(.download_count)\t\(.name)"'

118−

119−pandoc-templates:

120− rm ../pandoc-templates/default.* ; \

121− cp data/templates/* ../pandoc-templates/ ; \

122− pushd ../pandoc-templates/ && \

123− git add * && \

124− git commit -m "Updated templates for pandoc $(version)" && \

125− popd

126−

127−trypandoc:

128− ssh -t macfarlane 'cd src/pandoc && git pull && stack install --flag pandoc:trypandoc --flag pandoc:embed_data_files && cd trypandoc && sudo make install'

30+ cabal-dev configure --enable-benchmarks && cabal-dev build

12931

130−update-website:

131− make -C $(WEBSITE) update

132− make -C $(WEBSITE)

133− make -C $(WEBSITE) upload

32+sdist:

33+ dist/setup/setup sdist

34+ # cabal sdist won't work, see https://github.com/haskell/cabal/issues/403

13435

13536clean:

136− stack clean

37+ cabal-dev clean

13738

138−check-cabal: git-files.txt sdist-files.txt

139− echo "Checking to see if all committed test/data files are in sdist."

140− diff -u $^

39+veryclean: clean

40+ rm -rf pandoc-types citeproc-hs dist cabal-dev

14141

142−sdist-files.txt: .FORCE

143− cabal sdist --list-only | sed 's/\.\///' | grep '^\(test\|data\)\/' | sort > $@

42+pandoc-types:

43+ git clone https://github.com/jgm/pandoc-types && \

44+ cabal-dev add-source pandoc-types

14445

145−git-files.txt: .FORCE

146− git ls-tree -r --name-only HEAD | grep '^\(test\|data\)\/' | sort > $@

46+citeproc-hs: pandoc-types

47+ darcs get --lazy http://gorgias.mine.nu/repos/citeproc-hs && \

48+ cabal-dev add-source citeproc-hs

14749

148−.PHONY: .FORCE deps quick full haddock install clean test bench changes_github dist prof download_stats reformat lint weigh doc/lua-filters.md pandoc-templates trypandoc update-website debpkg checkdocs ghcid ghci fix_spacing hlint check check-cabal

50+install:

51+ cabal-dev install --enable-tests

PROFILINGnew file+6

@@ -0,0 +1,6 @@

1+To use the GHC profiler:

2+

3+cabal clean

4+cabal install --enable-library-profiling --enable-executable-profiling

5+pandoc +RTS -p -RTS [file]...

6+less pandoc.prof

READMEnew file+2845

@@ -0,0 +1,2845 @@

1+% Pandoc User's Guide

2+% John MacFarlane

3+% January 19, 2013

4+

5+Synopsis

6+========

7+

8+pandoc [*options*] [*input-file*]...

9+

10+Description

11+===========

12+

13+Pandoc is a [Haskell] library for converting from one markup format to

14+another, and a command-line tool that uses this library. It can read

15+[markdown] and (subsets of) [Textile], [reStructuredText], [HTML],

16+[LaTeX], [MediaWiki markup], [Haddock markup], [OPML], and [DocBook]; and

17+it can write plain text, [markdown], [reStructuredText], [XHTML], [HTML 5],

18+[LaTeX] (including [beamer] slide shows), [ConTeXt], [RTF], [OPML], [DocBook],

19+[OpenDocument], [ODT], [Word docx], [GNU Texinfo], [MediaWiki markup],

20+[EPUB] (v2 or v3), [FictionBook2], [Textile], [groff man] pages, [Emacs

21+Org-Mode], [AsciiDoc], and [Slidy], [Slideous], [DZSlides], [reveal.js]

22+or [S5] HTML slide shows. It can also produce [PDF] output on systems

23+where LaTeX is installed.

24+

25+Pandoc's enhanced version of markdown includes syntax for footnotes,

26+tables, flexible ordered lists, definition lists, fenced code blocks,

27+superscript, subscript, strikeout, title blocks, automatic tables of

28+contents, embedded LaTeX math, citations, and markdown inside HTML block

29+elements. (These enhancements, described below under

30+[Pandoc's markdown](#pandocs-markdown), can be disabled using the

31+`markdown_strict` input or output format.)

32+

33+In contrast to most existing tools for converting markdown to HTML, which

34+use regex substitutions, Pandoc has a modular design: it consists of a

35+set of readers, which parse text in a given format and produce a native

36+representation of the document, and a set of writers, which convert

37+this native representation into a target format. Thus, adding an input

38+or output format requires only adding a reader or writer.

39+

40+Using `pandoc`

41+--------------

42+

43+If no *input-file* is specified, input is read from *stdin*.

44+Otherwise, the *input-files* are concatenated (with a blank

45+line between each) and used as input. Output goes to *stdout* by

46+default (though output to *stdout* is disabled for the `odt`, `docx`,

47+`epub`, and `epub3` output formats). For output to a file, use the

48+`-o` option:

49+

50+ pandoc -o output.html input.txt

51+

52+Instead of a file, an absolute URI may be given. In this case

53+pandoc will fetch the content using HTTP:

54+

55+ pandoc -f html -t markdown http://www.fsf.org

56+

57+If multiple input files are given, `pandoc` will concatenate them all (with

58+blank lines between them) before parsing.

59+

60+The format of the input and output can be specified explicitly using

61+command-line options. The input format can be specified using the

62+`-r/--read` or `-f/--from` options, the output format using the

63+`-w/--write` or `-t/--to` options. Thus, to convert `hello.txt` from

64+markdown to LaTeX, you could type:

65+

66+ pandoc -f markdown -t latex hello.txt

67+

68+To convert `hello.html` from html to markdown:

69+

70+ pandoc -f html -t markdown hello.html

71+

72+Supported output formats are listed below under the `-t/--to` option.

73+Supported input formats are listed below under the `-f/--from` option. Note

74+that the `rst`, `textile`, `latex`, and `html` readers are not complete;

75+there are some constructs that they do not parse.

76+

77+If the input or output format is not specified explicitly, `pandoc`

78+will attempt to guess it from the extensions of

79+the input and output filenames. Thus, for example,

80+

81+ pandoc -o hello.tex hello.txt

82+

83+will convert `hello.txt` from markdown to LaTeX. If no output file

84+is specified (so that output goes to *stdout*), or if the output file's

85+extension is unknown, the output format will default to HTML.

86+If no input file is specified (so that input comes from *stdin*), or

87+if the input files' extensions are unknown, the input format will

88+be assumed to be markdown unless explicitly specified.

89+

90+Pandoc uses the UTF-8 character encoding for both input and output.

91+If your local character encoding is not UTF-8, you

92+should pipe input and output through `iconv`:

93+

94+ iconv -t utf-8 input.txt | pandoc | iconv -f utf-8

95+

96+Creating a PDF

97+--------------

98+

99+Earlier versions of pandoc came with a program, `markdown2pdf`, that

100+used pandoc and pdflatex to produce a PDF. This is no longer needed,

101+since `pandoc` can now produce `pdf` output itself. To produce a PDF, simply

102+specify an output file with a `.pdf` extension. Pandoc will create a latex

103+file and use pdflatex (or another engine, see `--latex-engine`) to convert it

104+to PDF:

105+

106+ pandoc test.txt -o test.pdf

107+

108+Production of a PDF requires that a LaTeX engine be installed (see

109+`--latex-engine`, below), and assumes that the following LaTeX packages are

110+available: `amssymb`, `amsmath`, `ifxetex`, `ifluatex`, `listings` (if the

111+`--listings` option is used), `fancyvrb`, `longtable`, `url`,

112+`graphicx`, `hyperref`, `ulem`, `babel` (if the `lang` variable is set),

113+`fontspec` (if `xelatex` or `lualatex` is used as the LaTeX engine), `xltxtra`

114+and `xunicode` (if `xelatex` is used).

115+

116+`hsmarkdown`

117+------------

118+

119+A user who wants a drop-in replacement for `Markdown.pl` may create

120+a symbolic link to the `pandoc` executable called `hsmarkdown`. When

121+invoked under the name `hsmarkdown`, `pandoc` will behave as if

122+invoked with `-f markdown_strict --email-obfuscation=references`,

123+and all command-line options will be treated as regular arguments.

124+However, this approach does not work under Cygwin, due to problems with

125+its simulation of symbolic links.

126+

127+[Cygwin]: http://www.cygwin.com/

128+[`iconv`]: http://www.gnu.org/software/libiconv/

129+[CTAN]: http://www.ctan.org "Comprehensive TeX Archive Network"

130+[TeX Live]: http://www.tug.org/texlive/

131+[MacTeX]: http://www.tug.org/mactex/

132+

133+Options

134+=======

135+

136+General options

137+---------------

138+

139+`-f` *FORMAT*, `-r` *FORMAT*, `--from=`*FORMAT*, `--read=`*FORMAT*

140+: Specify input format. *FORMAT* can be `native` (native Haskell),

141+ `json` (JSON version of native AST), `markdown` (pandoc's

142+ extended markdown), `markdown_strict` (original unextended markdown),

143+ `markdown_phpextra` (PHP Markdown Extra extended markdown),

144+ `markdown_github` (github extended markdown),

145+ `textile` (Textile), `rst` (reStructuredText), `html` (HTML),

146+ `docbook` (DocBook), `opml` (OPML), `mediawiki` (MediaWiki markup),

147+ `haddock` (Haddock markup), or `latex` (LaTeX).

148+ If `+lhs` is appended to `markdown`, `rst`, `latex`, or `html`,

149+ the input will be treated as literate Haskell source:

150+ see [Literate Haskell support](#literate-haskell-support), below.

151+ Markdown syntax extensions can be individually enabled or disabled

152+ by appending `+EXTENSION` or `-EXTENSION` to the format name.

153+ So, for example, `markdown_strict+footnotes+definition_lists`

154+ is strict markdown with footnotes and definition lists enabled,

155+ and `markdown-pipe_tables+hard_line_breaks` is pandoc's markdown

156+ without pipe tables and with hard line breaks. See [Pandoc's

157+ markdown](#pandocs-markdown), below, for a list of extensions and

158+ their names.

159+

160+`-t` *FORMAT*, `-w` *FORMAT*, `--to=`*FORMAT*, `--write=`*FORMAT*

161+: Specify output format. *FORMAT* can be `native` (native Haskell),

162+ `json` (JSON version of native AST), `plain` (plain text),

163+ `markdown` (pandoc's extended markdown), `markdown_strict` (original

164+ unextended markdown), `markdown_phpextra` (PHP Markdown extra

165+ extended markdown), `markdown_github` (github extended markdown),

166+ `rst` (reStructuredText), `html` (XHTML 1), `html5` (HTML 5),

167+ `latex` (LaTeX), `beamer` (LaTeX beamer slide show),

168+ `context` (ConTeXt), `man` (groff man), `mediawiki` (MediaWiki markup),

169+ `textile` (Textile), `org` (Emacs Org-Mode), `texinfo` (GNU Texinfo),

170+ `opml` (OPML), `docbook` (DocBook), `opendocument` (OpenDocument), `odt`

171+ (OpenOffice text document), `docx` (Word docx),

172+ `rtf` (rich text format), `epub` (EPUB v2 book), `epub3`

173+ (EPUB v3), `fb2` (FictionBook2 e-book), `asciidoc` (AsciiDoc), `slidy`

174+ (Slidy HTML and javascript slide show), `slideous` (Slideous HTML and

175+ javascript slide show), `dzslides` (DZSlides HTML5 + javascript slide

176+ show), `revealjs` (reveal.js HTML5 + javascript slide show), `s5`

177+ (S5 HTML and javascript slide show), or the path of a custom

178+ lua writer (see [Custom writers](#custom-writers), below). Note that

179+ `odt`, `epub`, and `epub3` output will not be directed to *stdout*; an

180+ output filename must be specified using the `-o/--output` option. If

181+ `+lhs` is appended to `markdown`, `rst`, `latex`, `beamer`, `html`, or

182+ `html5`, the output will be rendered as literate Haskell source: see

183+ [Literate Haskell support](#literate-haskell-support), below. Markdown

184+ syntax extensions can be individually enabled or disabled by appending

185+ `+EXTENSION` or `-EXTENSION` to the format name, as described above

186+ under `-f`.

187+

188+`-o` *FILE*, `--output=`*FILE*

189+: Write output to *FILE* instead of *stdout*. If *FILE* is

190+ `-`, output will go to *stdout*. (Exception: if the output

191+ format is `odt`, `docx`, `epub`, or `epub3`, output to stdout is disabled.)

192+

193+`--data-dir=`*DIRECTORY*

194+: Specify the user data directory to search for pandoc data files.

195+ If this option is not specified, the default user data directory

196+ will be used. This is

197+

198+ $HOME/.pandoc

199+

200+ in unix,

201+

202+ C:\Documents And Settings\USERNAME\Application Data\pandoc

203+

204+ in Windows XP, and

205+

206+ C:\Users\USERNAME\AppData\Roaming\pandoc

207+

208+ in Windows 7. (You can find the default user data directory

209+ on your system by looking at the output of `pandoc --version`.)

210+ A `reference.odt`, `reference.docx`, `default.csl`,

211+ `epub.css`, `templates`, `slidy`, `slideous`, or `s5` directory

212+ placed in this directory will override pandoc's normal defaults.

213+

214+`-v`, `--version`

215+: Print version.

216+

217+`-h`, `--help`

218+: Show usage message.

219+

220+Reader options

221+--------------

222+

223+`-R`, `--parse-raw`

224+: Parse untranslatable HTML codes and LaTeX environments as raw HTML

225+ or LaTeX, instead of ignoring them. Affects only HTML and LaTeX

226+ input. Raw HTML can be printed in markdown, reStructuredText, HTML,

227+ Slidy, Slideous, DZSlides, reveal.js, and S5 output; raw LaTeX

228+ can be printed in markdown, reStructuredText, LaTeX, and ConTeXt output.

229+ The default is for the readers to omit untranslatable HTML codes and

230+ LaTeX environments. (The LaTeX reader does pass through untranslatable

231+ LaTeX *commands*, even if `-R` is not specified.)

232+

233+`-S`, `--smart`

234+: Produce typographically correct output, converting straight quotes

235+ to curly quotes, `---` to em-dashes, `--` to en-dashes, and

236+ `...` to ellipses. Nonbreaking spaces are inserted after certain

237+ abbreviations, such as "Mr." (Note: This option is significant only when

238+ the input format is `markdown`, `markdown_strict`, or `textile`. It

239+ is selected automatically when the input format is `textile` or the

240+ output format is `latex` or `context`, unless `--no-tex-ligatures`

241+ is used.)

242+

243+`--old-dashes`

244+: Selects the pandoc <= 1.8.2.1 behavior for parsing smart dashes: `-` before

245+ a numeral is an en-dash, and `--` is an em-dash. This option is selected

246+ automatically for `textile` input.

247+

248+`--base-header-level=`*NUMBER*

249+: Specify the base level for headers (defaults to 1).

250+

251+`--indented-code-classes=`*CLASSES*

252+: Specify classes to use for indented code blocks--for example,

253+ `perl,numberLines` or `haskell`. Multiple classes may be separated

254+ by spaces or commas.

255+

256+`--default-image-extension=`*EXTENSION*

257+: Specify a default extension to use when image paths/URLs have no

258+ extension. This allows you to use the same source for formats that

259+ require different kinds of images. Currently this option only affects

260+ the markdown and LaTeX readers.

261+

262+`--filter=`*EXECUTABLE*

263+: Specify an executable to be used as a filter transforming the

264+ Pandoc AST after the input is parsed and before the output is

265+ written. The executable should read JSON from stdin and write

266+ JSON to stdout. The JSON must be formatted like pandoc's own

267+ JSON input and output. The name of the output format will be

268+ passed to the filter as the first argument. Hence,

269+

270+ pandoc --filter ./caps.py -t latex

271+

272+ is equivalent to

273+

274+ pandoc -t json | ./caps.py latex | pandoc -f json -t latex

275+

276+ The latter form may be useful for debugging filters.

277+

278+ Filters may be written in any language. `Text.Pandoc.JSON`

279+ exports `toJSONFilter` to facilitate writing filters in Haskell.

280+ Those who would prefer to write filters in python can use the

281+ module `pandocfilters`, installable from PyPI. See

282+ <http://github.com/jgm/pandocfilters> for the module and several

283+ examples. Note that the *EXECUTABLE* will be sought in the user's

284+ `PATH`, and not in the working directory, if no directory is

285+ provided. If you want to run a script in the working directory,

286+ preface the filename with `./`.

287+

288+`-M` *KEY[=VAL]*, `--metadata=`*KEY[:VAL]*

289+: Set the metadata field *KEY* to the value *VAL*. A value specified

290+ on the command line overrides a value specified in the document.

291+ Values will be parsed as YAML boolean or string values. If no value is

292+ specified, the value will be treated as Boolean true. Like

293+ `--variable`, `--metadata` causes template variables to be set.

294+ But unlike `--variable`, `--metadata` affects the metadata of the

295+ underlying document (which is accessible from filters and may be

296+ printed in some output formats).

297+

298+`--normalize`

299+: Normalize the document after reading: merge adjacent

300+ `Str` or `Emph` elements, for example, and remove repeated `Space`s.

301+

302+`-p`, `--preserve-tabs`

303+: Preserve tabs instead of converting them to spaces (the default).

304+ Note that this will only affect tabs in literal code spans and code

305+ blocks; tabs in regular text will be treated as spaces.

306+

307+`--tab-stop=`*NUMBER*

308+: Specify the number of spaces per tab (default is 4).

309+

310+General writer options

311+----------------------

312+

313+`-s`, `--standalone`

314+: Produce output with an appropriate header and footer (e.g. a

315+ standalone HTML, LaTeX, or RTF file, not a fragment). This option

316+ is set automatically for `pdf`, `epub`, `epub3`, `fb2`, `docx`, and `odt`

317+ output.

318+

319+`--template=`*FILE*

320+: Use *FILE* as a custom template for the generated document. Implies

321+ `--standalone`. See [Templates](#templates) below for a description

322+ of template syntax. If no extension is specified, an extension

323+ corresponding to the writer will be added, so that `--template=special`

324+ looks for `special.html` for HTML output. If the template is not

325+ found, pandoc will search for it in the user data directory

326+ (see `--data-dir`). If this option is not used, a default

327+ template appropriate for the output format will be used (see

328+ `-D/--print-default-template`).

329+

330+`-V` *KEY[=VAL]*, `--variable=`*KEY[:VAL]*

331+: Set the template variable *KEY* to the value *VAL* when rendering the

332+ document in standalone mode. This is generally only useful when the

333+ `--template` option is used to specify a custom template, since

334+ pandoc automatically sets the variables used in the default

335+ templates. If no *VAL* is specified, the key will be given the

336+ value `true`.

337+

338+`-D` *FORMAT*, `--print-default-template=`*FORMAT*

339+: Print the default template for an output *FORMAT*. (See `-t`

340+ for a list of possible *FORMAT*s.)

341+

342+`--print-default-data-file=`*FILE*

343+: Print a default data file.

344+

345+`--no-wrap`

346+: Disable text wrapping in output. By default, text is wrapped

347+ appropriately for the output format.

348+

349+`--columns`=*NUMBER*

350+: Specify length of lines in characters (for text wrapping).

351+

352+`--toc`, `--table-of-contents`

353+: Include an automatically generated table of contents (or, in

354+ the case of `latex`, `context`, and `rst`, an instruction to create

355+ one) in the output document. This option has no effect on `man`,

356+ `docbook`, `slidy`, `slideous`, `s5`, `docx`, or `odt` output.

357+

358+`--toc-depth=`*NUMBER*

359+: Specify the number of section levels to include in the table

360+ of contents. The default is 3 (which means that level 1, 2, and 3

361+ headers will be listed in the contents).

362+

363+`--no-highlight`

364+: Disables syntax highlighting for code blocks and inlines, even when

365+ a language attribute is given.

366+

367+`--highlight-style`=*STYLE*

368+: Specifies the coloring style to be used in highlighted source code.

369+ Options are `pygments` (the default), `kate`, `monochrome`,

370+ `espresso`, `zenburn`, `haddock`, and `tango`.

371+

372+`-H` *FILE*, `--include-in-header=`*FILE*

373+: Include contents of *FILE*, verbatim, at the end of the header.

374+ This can be used, for example, to include special

375+ CSS or javascript in HTML documents. This option can be used

376+ repeatedly to include multiple files in the header. They will be

377+ included in the order specified. Implies `--standalone`.

378+

379+`-B` *FILE*, `--include-before-body=`*FILE*

380+: Include contents of *FILE*, verbatim, at the beginning of the

381+ document body (e.g. after the `<body>` tag in HTML, or the

382+ `\begin{document}` command in LaTeX). This can be used to include

383+ navigation bars or banners in HTML documents. This option can be

384+ used repeatedly to include multiple files. They will be included in

385+ the order specified. Implies `--standalone`.

386+

387+`-A` *FILE*, `--include-after-body=`*FILE*

388+: Include contents of *FILE*, verbatim, at the end of the document

389+ body (before the `</body>` tag in HTML, or the

390+ `\end{document}` command in LaTeX). This option can be be used

391+ repeatedly to include multiple files. They will be included in the

392+ order specified. Implies `--standalone`.

393+

394+Options affecting specific writers

395+----------------------------------

396+

397+`--self-contained`

398+: Produce a standalone HTML file with no external dependencies, using

399+ `data:` URIs to incorporate the contents of linked scripts, stylesheets,

400+ images, and videos. The resulting file should be "self-contained,"

401+ in the sense that it needs no external files and no net access to be

402+ displayed properly by a browser. This option works only with HTML output

403+ formats, including `html`, `html5`, `html+lhs`, `html5+lhs`, `s5`,

404+ `slidy`, `slideous`, `dzslides`, and `revealjs`. Scripts, images, and

405+ stylesheets at absolute URLs will be downloaded; those at relative URLs

406+ will be sought first relative to the working directory, then relative to

407+ the user data directory (see `--data-dir`), and finally relative to

408+ pandoc's default data directory. `--self-contained` does not

409+ work with `--mathjax`.

410+

411+`--offline`

412+: Deprecated synonym for `--self-contained`.

413+

414+`-5`, `--html5`

415+: Produce HTML5 instead of HTML4. This option has no effect for writers

416+ other than `html`. (*Deprecated:* Use the `html5` output format instead.)

417+

418+`--html-q-tags`

419+: Use `<q>` tags for quotes in HTML.

420+

421+`--ascii`

422+: Use only ascii characters in output. Currently supported only

423+ for HTML output (which uses numerical entities instead of

424+ UTF-8 when this option is selected).

425+

426+`--reference-links`

427+: Use reference-style links, rather than inline links, in writing markdown

428+ or reStructuredText. By default inline links are used.

429+

430+`--atx-headers`

431+: Use ATX style headers in markdown and asciidoc output. The default is

432+ to use setext-style headers for levels 1-2, and then ATX headers.

433+

434+`--chapters`

435+: Treat top-level headers as chapters in LaTeX, ConTeXt, and DocBook

436+ output. When the LaTeX template uses the report, book, or

437+ memoir class, this option is implied. If `--beamer` is used,

438+ top-level headers will become `\part{..}`.

439+

440+`-N`, `--number-sections`

441+: Number section headings in LaTeX, ConTeXt, HTML, or EPUB output.

442+ By default, sections are not numbered. Sections with class

443+ `unnumbered` will never be numbered, even if `--number-sections`

444+ is specified.

445+

446+`--number-offset`=*NUMBER[,NUMBER,...]*,

447+: Offset for section headings in HTML output (ignored in other

448+ output formats). The first number is added to the section number for

449+ top-level headers, the second for second-level headers, and so on.

450+ So, for example, if you want the first top-level header in your

451+ document to be numbered "6", specify `--number-offset=5`.

452+ If your document starts with a level-2 header which you want to

453+ be numbered "1.5", specify `--number-offset=1,4`.

454+ Offsets are 0 by default. Implies `--number-sections`.

455+

456+`--no-tex-ligatures`

457+: Do not convert quotation marks, apostrophes, and dashes to

458+ the TeX ligatures when writing LaTeX or ConTeXt. Instead, just

459+ use literal unicode characters. This is needed for using advanced

460+ OpenType features with XeLaTeX and LuaLaTeX. Note: normally

461+ `--smart` is selected automatically for LaTeX and ConTeXt

462+ output, but it must be specified explicitly if `--no-tex-ligatures`

463+ is selected. If you use literal curly quotes, dashes, and ellipses

464+ in your source, then you may want to use `--no-tex-ligatures`

465+ without `--smart`.

466+

467+`--listings`

468+: Use listings package for LaTeX code blocks

469+

470+`-i`, `--incremental`

471+: Make list items in slide shows display incrementally (one by one).

472+ The default is for lists to be displayed all at once.

473+

474+`--slide-level`=*NUMBER*

475+: Specifies that headers with the specified level create

476+ slides (for `beamer`, `s5`, `slidy`, `slideous`, `dzslides`). Headers

477+ above this level in the hierarchy are used to divide the

478+ slide show into sections; headers below this level create

479+ subheads within a slide. The default is to set the slide level

480+ based on the contents of the document; see

481+ [Structuring the slide show](#structuring-the-slide-show), below.

482+

483+`--section-divs`

484+: Wrap sections in `<div>` tags (or `<section>` tags in HTML5),

485+ and attach identifiers to the enclosing `<div>` (or `<section>`)

486+ rather than the header itself.

487+ See [Section identifiers](#header-identifiers-in-html-latex-and-context), below.

488+

489+`--email-obfuscation=`*none|javascript|references*

490+: Specify a method for obfuscating `mailto:` links in HTML documents.

491+ *none* leaves `mailto:` links as they are. *javascript* obfuscates

492+ them using javascript. *references* obfuscates them by printing their

493+ letters as decimal or hexadecimal character references.

494+

495+`--id-prefix`=*STRING*

496+: Specify a prefix to be added to all automatically generated identifiers

497+ in HTML and DocBook output, and to footnote numbers in markdown output.

498+ This is useful for preventing duplicate identifiers when generating

499+ fragments to be included in other pages.

500+

501+`-T` *STRING*, `--title-prefix=`*STRING*

502+: Specify *STRING* as a prefix at the beginning of the title

503+ that appears in the HTML header (but not in the title as it

504+ appears at the beginning of the HTML body). Implies

505+ `--standalone`.

506+

507+`-c` *URL*, `--css=`*URL*

508+: Link to a CSS style sheet. This option can be be used repeatedly to

509+ include multiple files. They will be included in the order specified.

510+

511+`--reference-odt=`*FILE*

512+: Use the specified file as a style reference in producing an ODT.

513+ For best results, the reference ODT should be a modified version

514+ of an ODT produced using pandoc. The contents of the reference ODT

515+ are ignored, but its stylesheets are used in the new ODT. If no

516+ reference ODT is specified on the command line, pandoc will look

517+ for a file `reference.odt` in the user data directory (see

518+ `--data-dir`). If this is not found either, sensible defaults will be

519+ used.

520+

521+`--reference-docx=`*FILE*

522+: Use the specified file as a style reference in producing a docx file.

523+ For best results, the reference docx should be a modified version

524+ of a docx file produced using pandoc. The contents of the reference docx

525+ are ignored, but its stylesheets are used in the new docx. If no

526+ reference docx is specified on the command line, pandoc will look

527+ for a file `reference.docx` in the user data directory (see

528+ `--data-dir`). If this is not found either, sensible defaults will be

529+ used. The following styles are used by pandoc: [paragraph]

530+ Normal, Compact, Title, Authors, Date, Heading 1, Heading 2, Heading 3,

531+ Heading 4, Heading 5, Block Quote, Definition Term, Definition,

532+ Body Text, Table Caption, Image Caption; [character] Default

533+ Paragraph Font, Body Text Char, Verbatim Char, Footnote Ref,

534+ Link.

535+

536+`--epub-stylesheet=`*FILE*

537+: Use the specified CSS file to style the EPUB. If no stylesheet

538+ is specified, pandoc will look for a file `epub.css` in the

539+ user data directory (see `--data-dir`). If it is not

540+ found there, sensible defaults will be used.

541+

542+`--epub-cover-image=`*FILE*

543+: Use the specified image as the EPUB cover. It is recommended

544+ that the image be less than 1000px in width and height.

545+

546+`--epub-metadata=`*FILE*

547+: Look in the specified XML file for metadata for the EPUB.

548+ The file should contain a series of Dublin Core elements,

549+ as documented at <http://dublincore.org/documents/dces/>.

550+ For example:

551+

552+ <dc:rights>Creative Commons</dc:rights>

553+ <dc:language>es-AR</dc:language>

554+

555+ By default, pandoc will include the following metadata elements:

556+ `<dc:title>` (from the document title), `<dc:creator>` (from the

557+ document authors), `<dc:date>` (from the document date, which should

558+ be in [ISO 8601 format]), `<dc:language>` (from the `lang`

559+ variable, or, if is not set, the locale), and `<dc:identifier

560+ id="BookId">` (a randomly generated UUID). Any of these may be

561+ overridden by elements in the metadata file.

562+

563+`--epub-embed-font=`*FILE*

564+: Embed the specified font in the EPUB. This option can be repeated

565+ to embed multiple fonts. To use embedded fonts, you

566+ will need to add declarations like the following to your CSS (see

567+ `--epub-stylesheet`):

568+

569+ @font-face {

570+ font-family: DejaVuSans;

571+ font-style: normal;

572+ font-weight: normal;

573+ src:url("DejaVuSans-Regular.ttf");

574+ }

575+ @font-face {

576+ font-family: DejaVuSans;

577+ font-style: normal;

578+ font-weight: bold;

579+ src:url("DejaVuSans-Bold.ttf");

580+ }

581+ @font-face {

582+ font-family: DejaVuSans;

583+ font-style: italic;

584+ font-weight: normal;

585+ src:url("DejaVuSans-Oblique.ttf");

586+ }

587+ @font-face {

588+ font-family: DejaVuSans;

589+ font-style: italic;

590+ font-weight: bold;

591+ src:url("DejaVuSans-BoldOblique.ttf");

592+ }

593+ body { font-family: "DejaVuSans"; }

594+

595+`--epub-chapter-level=`*NUMBER*

596+: Specify the header level at which to split the EPUB into separate

597+ "chapter" files. The default is to split into chapters at level 1

598+ headers. This option only affects the internal composition of the

599+ EPUB, not the way chapters and sections are displayed to users. Some

600+ readers may be slow if the chapter files are too large, so for large

601+ documents with few level 1 headers, one might want to use a chapter

602+ level of 2 or 3.

603+

604+`--latex-engine=`*pdflatex|lualatex|xelatex*

605+: Use the specified LaTeX engine when producing PDF output.

606+ The default is `pdflatex`. If the engine is not in your PATH,

607+ the full path of the engine may be specified here.

608+

609+Citation rendering

610+------------------

611+

612+`--bibliography=`*FILE*

613+: Set the `bibliography` field in the document's metadata to *FILE*,

614+ overriding any value set in the metadata, and process citations

615+ using `pandoc-citeproc`. (This is equivalent to

616+ `--metadata bibliography=FILE --filter pandoc-citeproc`.)

617+

618+`--csl=`*FILE*

619+: Set the `csl` field in the document's metadata to *FILE*,

620+ overriding any value set in the metadata. (This is equivalent to

621+ `--metadata csl=FILE`.)

622+

623+`--citation-abbreviations=`*FILE*

624+: Set the `citation-abbreviations` field in the document's metadata to

625+ *FILE*, overriding any value set in the metadata. (This is equivalent to

626+ `--metadata citation-abbreviations=FILE`.)

627+

628+`--natbib`

629+: Use natbib for citations in LaTeX output.

630+

631+`--biblatex`

632+: Use biblatex for citations in LaTeX output.

633+

634+Math rendering in HTML

635+----------------------

636+

637+`-m` [*URL*], `--latexmathml`[=*URL*]

638+: Use the [LaTeXMathML] script to display embedded TeX math in HTML output.

639+ To insert a link to a local copy of the `LaTeXMathML.js` script,

640+ provide a *URL*. If no *URL* is provided, the contents of the

641+ script will be inserted directly into the HTML header, preserving

642+ portability at the price of efficiency. If you plan to use math on

643+ several pages, it is much better to link to a copy of the script,

644+ so it can be cached.

645+

646+`--mathml`[=*URL*]

647+: Convert TeX math to MathML (in `docbook` as well as `html` and `html5`).

648+ In standalone `html` output, a small javascript (or a link to such a

649+ script if a *URL* is supplied) will be inserted that allows the MathML to

650+ be viewed on some browsers.

651+

652+`--jsmath`[=*URL*]

653+: Use [jsMath] to display embedded TeX math in HTML output.

654+ The *URL* should point to the jsMath load script (e.g.

655+ `jsMath/easy/load.js`); if provided, it will be linked to in

656+ the header of standalone HTML documents. If a *URL* is not provided,

657+ no link to the jsMath load script will be inserted; it is then

658+ up to the author to provide such a link in the HTML template.

659+

660+`--mathjax`[=*URL*]

661+: Use [MathJax] to display embedded TeX math in HTML output.

662+ The *URL* should point to the `MathJax.js` load script.

663+ If a *URL* is not provided, a link to the MathJax CDN will

664+ be inserted.

665+

666+`--gladtex`

667+: Enclose TeX math in `<eq>` tags in HTML output. These can then

668+ be processed by [gladTeX] to produce links to images of the typeset

669+ formulas.

670+

671+`--mimetex`[=*URL*]

672+: Render TeX math using the [mimeTeX] CGI script. If *URL* is not

673+ specified, it is assumed that the script is at `/cgi-bin/mimetex.cgi`.

674+

675+`--webtex`[=*URL*]

676+: Render TeX formulas using an external script that converts TeX

677+ formulas to images. The formula will be concatenated with the URL

678+ provided. If *URL* is not specified, the Google Chart API will be used.

679+

680+Options for wrapper scripts

681+---------------------------

682+

683+`--dump-args`

684+: Print information about command-line arguments to *stdout*, then exit.

685+ This option is intended primarily for use in wrapper scripts.

686+ The first line of output contains the name of the output file specified

687+ with the `-o` option, or `-` (for *stdout*) if no output file was

688+ specified. The remaining lines contain the command-line arguments,

689+ one per line, in the order they appear. These do not include regular

690+ Pandoc options and their arguments, but do include any options appearing

691+ after a `--` separator at the end of the line.

692+

693+`--ignore-args`

694+: Ignore command-line arguments (for use in wrapper scripts).

695+ Regular Pandoc options are not ignored. Thus, for example,

696+

697+ pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1

698+

699+ is equivalent to

700+

701+ pandoc -o foo.html -s

702+

703+[LaTeXMathML]: http://math.etsu.edu/LaTeXMathML/

704+[jsMath]: http://www.math.union.edu/~dpvc/jsmath/

705+[MathJax]: http://www.mathjax.org/

706+[gladTeX]: http://ans.hsh.no/home/mgg/gladtex/

707+[mimeTeX]: http://www.forkosh.com/mimetex.html

708+[CSL]: http://CitationStyles.org

709+

710+Templates

711+=========

712+

713+When the `-s/--standalone` option is used, pandoc uses a template to

714+add header and footer material that is needed for a self-standing

715+document. To see the default template that is used, just type

716+

717+ pandoc -D FORMAT

718+

719+where `FORMAT` is the name of the output format. A custom template

720+can be specified using the `--template` option. You can also override

721+the system default templates for a given output format `FORMAT`

722+by putting a file `templates/default.FORMAT` in the user data

723+directory (see `--data-dir`, above). *Exceptions:* For `odt` output,

724+customize the `default.opendocument` template. For `pdf` output,

725+customize the `default.latex` template.

726+

727+Templates may contain *variables*. Variable names are sequences of

728+alphanumerics, `-`, and `_`, starting with a letter. A variable name

729+surrounded by `$` signs will be replaced by its value. For example,

730+the string `$title$` in

731+

732+ <title>$title$</title>

733+

734+will be replaced by the document title.

735+

736+To write a literal `$` in a template, use `$$`.

737+

738+Some variables are set automatically by pandoc. These vary somewhat

739+depending on the output format, but include metadata fields (such

740+as `title`, `author`, and `date`) as well as the following:

741+

742+`header-includes`

743+: contents specified by `-H/--include-in-header` (may have multiple

744+ values)

745+`toc`

746+: non-null value if `--toc/--table-of-contents` was specified

747+`include-before`

748+: contents specified by `-B/--include-before-body` (may have

749+ multiple values)

750+`include-after`

751+: contents specified by `-A/--include-after-body` (may have

752+ multiple values)

753+`body`

754+: body of document

755+`lang`

756+: language code for HTML or LaTeX documents

757+`slidy-url`

758+: base URL for Slidy documents (defaults to

759+ `http://www.w3.org/Talks/Tools/Slidy2`)

760+`slideous-url`

761+: base URL for Slideous documents (defaults to `default`)

762+`s5-url`

763+: base URL for S5 documents (defaults to `ui/default`)

764+`revealjs-url`

765+: base URL for reveal.js documents (defaults to `reveal.js`)

766+`theme`

767+: reveal.js or LaTeX beamer theme

768+`transition`

769+: reveal.js transition

770+`fontsize`

771+: font size (10pt, 11pt, 12pt) for LaTeX documents

772+`documentclass`

773+: document class for LaTeX documents

774+`classoption`

775+: option for LaTeX documentclass, e.g. `oneside`; may be repeated

776+ for multiple options

777+`geometry`

778+: options for LaTeX `geometry` class, e.g. `margin=1in`;

779+ may be repeated for multiple options

780+`mainfont`, `sansfont`, `monofont`, `mathfont`

781+: fonts for LaTeX documents (works only with xelatex

782+ and lualatex)

783+`colortheme`

784+: colortheme for LaTeX beamer documents

785+`fonttheme`

786+: fonttheme for LaTeX beamer documents

787+`linkcolor`

788+: color for internal links in LaTeX documents (`red`, `green`,

789+ `magenta`, `cyan`, `blue`, `black`)

790+`urlcolor`

791+: color for external links in LaTeX documents

792+`citecolor`

793+: color for citation links in LaTeX documents

794+`links-as-notes`

795+: causes links to be printed as footnotes in LaTeX documents

796+`biblio-style`

797+: bibliography style in LaTeX, when used with `--natbib`

798+`section`

799+: section number in man pages

800+`header`

801+: header in man pages

802+`footer`

803+: footer in man pages

804+

805+Variables may be set at the command line using the `-V/--variable`

806+option. Variables set in this way override metadata fields with

807+the same name.

808+

809+Templates may contain conditionals. The syntax is as follows:

810+

811+ $if(variable)$

812+ X

813+ $else$

814+ Y

815+ $endif$

816+

817+This will include `X` in the template if `variable` has a non-null

818+value; otherwise it will include `Y`. `X` and `Y` are placeholders for

819+any valid template text, and may include interpolated variables or other

820+conditionals. The `$else$` section may be omitted.

821+

822+When variables can have multiple values (for example, `author` in

823+a multi-author document), you can use the `$for$` keyword:

824+

825+ $for(author)$

826+ <meta name="author" content="$author$" />

827+ $endfor$

828+

829+You can optionally specify a separator to be used between

830+consecutive items:

831+

832+ $for(author)$$author$$sep$, $endfor$

833+

834+A dot can be used to select a field of a variable that takes

835+an object as its value. So, for example:

836+

837+ $author.name$ ($author.affiliation$)

838+

839+If you use custom templates, you may need to revise them as pandoc

840+changes. We recommend tracking the changes in the default templates,

841+and modifying your custom templates accordingly. An easy way to do this

842+is to fork the pandoc-templates repository

843+(<http://github.com/jgm/pandoc-templates>) and merge in changes after each

844+pandoc release.

845+

846+Pandoc's markdown

847+=================

848+

849+Pandoc understands an extended and slightly revised version of

850+John Gruber's [markdown] syntax. This document explains the syntax,

851+noting differences from standard markdown. Except where noted, these

852+differences can be suppressed by using the `markdown_strict` format instead

853+of `markdown`. An extensions can be enabled by adding `+EXTENSION`

854+to the format name and disabled by adding `-EXTENSION`. For example,

855+`markdown_strict+footnotes` is strict markdown with footnotes

856+enabled, while `markdown-footnotes-pipe_tables` is pandoc's

857+markdown without footnotes or pipe tables.

858+

859+Philosophy

860+----------

861+

862+Markdown is designed to be easy to write, and, even more importantly,

863+easy to read:

864+

865+> A Markdown-formatted document should be publishable as-is, as plain

866+> text, without looking like it's been marked up with tags or formatting

867+> instructions.

868+> -- [John Gruber](http://daringfireball.net/projects/markdown/syntax#philosophy)

869+

870+This principle has guided pandoc's decisions in finding syntax for

871+tables, footnotes, and other extensions.

872+

873+There is, however, one respect in which pandoc's aims are different

874+from the original aims of markdown. Whereas markdown was originally

875+designed with HTML generation in mind, pandoc is designed for multiple

876+output formats. Thus, while pandoc allows the embedding of raw HTML,

877+it discourages it, and provides other, non-HTMLish ways of representing

878+important document elements like definition lists, tables, mathematics, and

879+footnotes.

880+

881+Paragraphs

882+----------

883+

884+A paragraph is one or more lines of text followed by one or more blank line.

885+Newlines are treated as spaces, so you can reflow your paragraphs as you like.

886+If you need a hard line break, put two or more spaces at the end of a line.

887+

888+**Extension: `escaped_line_breaks`**

889+

890+A backslash followed by a newline is also a hard line break.

891+

892+Headers

893+-------

894+

895+There are two kinds of headers, Setext and atx.

896+

897+### Setext-style headers ###

898+

899+A setext-style header is a line of text "underlined" with a row of `=` signs

900+(for a level one header) or `-` signs (for a level two header):

901+

902+ A level-one header

903+ ==================

904+

905+ A level-two header

906+ ------------------

907+

908+The header text can contain inline formatting, such as emphasis (see

909+[Inline formatting](#inline-formatting), below).

910+

911+

912+### Atx-style headers ###

913+

914+An Atx-style header consists of one to six `#` signs and a line of

915+text, optionally followed by any number of `#` signs. The number of

916+`#` signs at the beginning of the line is the header level:

917+

918+ ## A level-two header

919+

920+ ### A level-three header ###

921+

922+As with setext-style headers, the header text can contain formatting:

923+

924+ # A level-one header with a [link](/url) and *emphasis*

925+

926+**Extension: `blank_before_header`**

927+

928+Standard markdown syntax does not require a blank line before a header.

929+Pandoc does require this (except, of course, at the beginning of the

930+document). The reason for the requirement is that it is all too easy for a

931+`#` to end up at the beginning of a line by accident (perhaps through line

932+wrapping). Consider, for example:

933+

934+ I like several of their flavors of ice cream:

935+ #22, for example, and #5.

936+

937+

938+### Header identifiers in HTML, LaTeX, and ConTeXt ###

939+

940+**Extension: `header_attributes`**

941+

942+Headers can be assigned attributes using this syntax at the end

943+of the line containing the header text:

944+

945+ {#identifier .class .class key=value key=value}

946+

947+Although this syntax allows assignment of classes and key/value attributes,

948+only identifiers currently have any affect in the writers (and only in some

949+writers: HTML, LaTeX, ConTeXt, Textile, AsciiDoc). Thus, for example,

950+the following headers will all be assigned the identifier `foo`:

951+

952+ # My header {#foo}

953+

954+ ## My header ## {#foo}

955+

956+ My other header {#foo}

957+ ---------------

958+

959+(This syntax is compatible with [PHP Markdown Extra].)

960+

961+Headers with the class `unnumbered` will not be numbered, even if

962+`--number-sections` is specified. A single hyphen (`-`) in an attribute

963+context is equivalent to `.unnumbered`, and preferable in non-English

964+documents. So,

965+

966+ # My header {-}

967+

968+is just the same as

969+

970+ # My header {.unnumbered}

971+

972+**Extension: `auto_identifiers`**

973+

974+A header without an explicitly specified identifier will be

975+automatically assigned a unique identifier based on the header text.

976+To derive the identifier from the header text,

977+

978+ - Remove all formatting, links, etc.

979+ - Remove all footnotes.

980+ - Remove all punctuation, except underscores, hyphens, and periods.

981+ - Replace all spaces and newlines with hyphens.

982+ - Convert all alphabetic characters to lowercase.

983+ - Remove everything up to the first letter (identifiers may

984+ not begin with a number or punctuation mark).

985+ - If nothing is left after this, use the identifier `section`.

986+

987+Thus, for example,

988+

989+ Header Identifier

990+ ------------------------------- ----------------------------

991+ Header identifiers in HTML `header-identifiers-in-html`

992+ *Dogs*?--in *my* house? `dogs--in-my-house`

993+ [HTML], [S5], or [RTF]? `html-s5-or-rtf`

994+ 3. Applications `applications`

995+ 33 `section`

996+

997+These rules should, in most cases, allow one to determine the identifier

998+from the header text. The exception is when several headers have the

999+same text; in this case, the first will get an identifier as described

1000+above; the second will get the same identifier with `-1` appended; the

1001+third with `-2`; and so on.

1002+

1003+These identifiers are used to provide link targets in the table of

1004+contents generated by the `--toc|--table-of-contents` option. They

1005+also make it easy to provide links from one section of a document to

1006+another. A link to this section, for example, might look like this:

1007+

1008+ See the section on

1009+ [header identifiers](#header-identifiers-in-html-latex-and-context).

1010+

1011+Note, however, that this method of providing links to sections works

1012+only in HTML, LaTeX, and ConTeXt formats.

1013+

1014+If the `--section-divs` option is specified, then each section will

1015+be wrapped in a `div` (or a `section`, if `--html5` was specified),

1016+and the identifier will be attached to the enclosing `<div>`

1017+(or `<section>`) tag rather than the header itself. This allows entire

1018+sections to be manipulated using javascript or treated differently in

1019+CSS.

1020+

1021+**Extension: `implicit_header_references`**

1022+

1023+Pandoc behaves as if reference links have been defined for each header.

1024+So, instead of

1025+

1026+ [header identifiers](#header-identifiers-in-html)

1027+

1028+you can simply write

1029+

1030+ [header identifiers]

1031+

1032+or

1033+

1034+ [header identifiers][]

1035+

1036+or

1037+

1038+ [the section on header identifiers][header identifiers]

1039+

1040+If there are multiple headers with identical text, the corresponding

1041+reference will link to the first one only, and you will need to use explicit

1042+links to link to the others, as described above.

1043+

1044+Unlike regular reference links, these references are case-sensitive.

1045+

1046+Note: if you have defined an explicit identifier for a header,

1047+then implicit references to it will not work.

1048+

1049+Block quotations

1050+----------------

1051+

1052+Markdown uses email conventions for quoting blocks of text.

1053+A block quotation is one or more paragraphs or other block elements

1054+(such as lists or headers), with each line preceded by a `>` character

1055+and a space. (The `>` need not start at the left margin, but it should

1056+not be indented more than three spaces.)

1057+

1058+ > This is a block quote. This

1059+ > paragraph has two lines.

1060+ >

1061+ > 1. This is a list inside a block quote.

1062+ > 2. Second item.

1063+

1064+A "lazy" form, which requires the `>` character only on the first

1065+line of each block, is also allowed:

1066+

1067+ > This is a block quote. This

1068+ paragraph has two lines.

1069+

1070+ > 1. This is a list inside a block quote.

1071+ 2. Second item.

1072+

1073+Among the block elements that can be contained in a block quote are

1074+other block quotes. That is, block quotes can be nested:

1075+

1076+ > This is a block quote.

1077+ >

1078+ > > A block quote within a block quote.

1079+

1080+**Extension: `blank_before_blockquote`**

1081+

1082+Standard markdown syntax does not require a blank line before a block

1083+quote. Pandoc does require this (except, of course, at the beginning of the

1084+document). The reason for the requirement is that it is all too easy for a

1085+`>` to end up at the beginning of a line by accident (perhaps through line

1086+wrapping). So, unless the `markdown_strict` format is used, the following does

1087+not produce a nested block quote in pandoc:

1088+

1089+ > This is a block quote.

1090+ >> Nested.

1091+

1092+

1093+Verbatim (code) blocks

1094+----------------------

1095+

1096+### Indented code blocks ###

1097+

1098+A block of text indented four spaces (or one tab) is treated as verbatim

1099+text: that is, special characters do not trigger special formatting,

1100+and all spaces and line breaks are preserved. For example,

1101+

1102+ if (a > 3) {

1103+ moveShip(5 * gravity, DOWN);

1104+ }

1105+

1106+The initial (four space or one tab) indentation is not considered part

1107+of the verbatim text, and is removed in the output.

1108+

1109+Note: blank lines in the verbatim text need not begin with four spaces.

1110+

1111+

1112+### Fenced code blocks ###

1113+

1114+**Extension: `fenced_code_blocks`**

1115+

1116+In addition to standard indented code blocks, Pandoc supports

1117+*fenced* code blocks. These begin with a row of three or more

1118+tildes (`~`) or backticks (`` ` ``) and end with a row of tildes or

1119+backticks that must be at least as long as the starting row. Everything

1120+between these lines is treated as code. No indentation is necessary:

1121+

1122+ ~~~~~~~

1123+ if (a > 3) {

1124+ moveShip(5 * gravity, DOWN);

1125+ }

1126+ ~~~~~~~

1127+

1128+Like regular code blocks, fenced code blocks must be separated

1129+from surrounding text by blank lines.

1130+

1131+If the code itself contains a row of tildes or backticks, just use a longer

1132+row of tildes or backticks at the start and end:

1133+

1134+ ~~~~~~~~~~~~~~~~

1135+ ~~~~~~~~~~

1136+ code including tildes

1137+ ~~~~~~~~~~

1138+ ~~~~~~~~~~~~~~~~

1139+

1140+Optionally, you may attach attributes to the code block using

1141+this syntax:

1142+

1143+ ~~~~ {#mycode .haskell .numberLines startFrom="100"}

1144+ qsort [] = []

1145+ qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++

1146+ qsort (filter (>= x) xs)

1147+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1148+

1149+Here `mycode` is an identifier, `haskell` and `numberLines` are classes, and

1150+`startFrom` is an attribute with value `100`. Some output formats can use this

1151+information to do syntax highlighting. Currently, the only output formats

1152+that uses this information are HTML and LaTeX. If highlighting is supported

1153+for your output format and language, then the code block above will appear

1154+highlighted, with numbered lines. (To see which languages are supported, do

1155+`pandoc --version`.) Otherwise, the code block above will appear as follows:

1156+

1157+ <pre id="mycode" class="haskell numberLines" startFrom="100">

1158+ <code>

1159+ ...

1160+ </code>

1161+ </pre>

1162+

1163+A shortcut form can also be used for specifying the language of

1164+the code block:

1165+

1166+ ```haskell

1167+ qsort [] = []

1168+ ```

1169+

1170+This is equivalent to:

1171+

1172+ ``` {.haskell}

1173+ qsort [] = []

1174+ ```

1175+

1176+To prevent all highlighting, use the `--no-highlight` flag.

1177+To set the highlighting style, use `--highlight-style`.

1178+

1179+Line blocks

1180+-----------

1181+

1182+**Extension: `line_blocks`**

1183+

1184+A line block is a sequence of lines beginning with a vertical bar (`|`)

1185+followed by a space. The division into lines will be preserved in

1186+the output, as will any leading spaces; otherwise, the lines will

1187+be formatted as markdown. This is useful for verse and addresses:

1188+

1189+ | The limerick packs laughs anatomical

1190+ | In space that is quite economical.

1191+ | But the good ones I've seen

1192+ | So seldom are clean

1193+ | And the clean ones so seldom are comical

1194+

1195+ | 200 Main St.

1196+ | Berkeley, CA 94718

1197+

1198+The lines can be hard-wrapped if needed, but the continuation

1199+line must begin with a space.

1200+

1201+ | The Right Honorable Most Venerable and Righteous Samuel L.

1202+ Constable, Jr.

1203+ | 200 Main St.

1204+ | Berkeley, CA 94718

1205+

1206+This syntax is borrowed from [reStructuredText].

1207+

1208+Lists

1209+-----

1210+

1211+### Bullet lists ###

1212+

1213+A bullet list is a list of bulleted list items. A bulleted list

1214+item begins with a bullet (`*`, `+`, or `-`). Here is a simple

1215+example:

1216+

1217+ * one

1218+ * two

1219+ * three

1220+

1221+This will produce a "compact" list. If you want a "loose" list, in which

1222+each item is formatted as a paragraph, put spaces between the items:

1223+

1224+ * one

1225+

1226+ * two

1227+

1228+ * three

1229+

1230+The bullets need not be flush with the left margin; they may be

1231+indented one, two, or three spaces. The bullet must be followed

1232+by whitespace.

1233+

1234+List items look best if subsequent lines are flush with the first

1235+line (after the bullet):

1236+

1237+ * here is my first

1238+ list item.

1239+ * and my second.

1240+

1241+But markdown also allows a "lazy" format:

1242+

1243+ * here is my first

1244+ list item.

1245+ * and my second.

1246+

1247+### The four-space rule ###

1248+

1249+A list item may contain multiple paragraphs and other block-level

1250+content. However, subsequent paragraphs must be preceded by a blank line

1251+and indented four spaces or a tab. The list will look better if the first

1252+paragraph is aligned with the rest:

1253+

1254+ * First paragraph.

1255+

1256+ Continued.

1257+

1258+ * Second paragraph. With a code block, which must be indented

1259+ eight spaces:

1260+

1261+ { code }

1262+

1263+List items may include other lists. In this case the preceding blank

1264+line is optional. The nested list must be indented four spaces or

1265+one tab:

1266+

1267+ * fruits

1268+ + apples

1269+ - macintosh

1270+ - red delicious

1271+ + pears

1272+ + peaches

1273+ * vegetables

1274+ + brocolli

1275+ + chard

1276+

1277+As noted above, markdown allows you to write list items "lazily," instead of

1278+indenting continuation lines. However, if there are multiple paragraphs or

1279+other blocks in a list item, the first line of each must be indented.

1280+

1281+ + A lazy, lazy, list

1282+ item.

1283+

1284+ + Another one; this looks

1285+ bad but is legal.

1286+

1287+ Second paragraph of second

1288+ list item.

1289+

1290+**Note:** Although the four-space rule for continuation paragraphs

1291+comes from the official [markdown syntax guide], the reference implementation,

1292+`Markdown.pl`, does not follow it. So pandoc will give different results than

1293+`Markdown.pl` when authors have indented continuation paragraphs fewer than

1294+four spaces.

1295+

1296+The [markdown syntax guide] is not explicit whether the four-space

1297+rule applies to *all* block-level content in a list item; it only

1298+mentions paragraphs and code blocks. But it implies that the rule

1299+applies to all block-level content (including nested lists), and

1300+pandoc interprets it that way.

1301+

1302+ [markdown syntax guide]:

1303+ http://daringfireball.net/projects/markdown/syntax#list

1304+

1305+### Ordered lists ###

1306+

1307+Ordered lists work just like bulleted lists, except that the items

1308+begin with enumerators rather than bullets.

1309+

1310+In standard markdown, enumerators are decimal numbers followed

1311+by a period and a space. The numbers themselves are ignored, so

1312+there is no difference between this list:

1313+

1314+ 1. one

1315+ 2. two

1316+ 3. three

1317+

1318+and this one:

1319+

1320+ 5. one

1321+ 7. two

1322+ 1. three

1323+

1324+**Extension: `fancy_lists`**

1325+

1326+Unlike standard markdown, Pandoc allows ordered list items to be marked

1327+with uppercase and lowercase letters and roman numerals, in addition to

1328+arabic numerals. List markers may be enclosed in parentheses or followed by a

1329+single right-parentheses or period. They must be separated from the

1330+text that follows by at least one space, and, if the list marker is a

1331+capital letter with a period, by at least two spaces.[^2]

1332+

1333+[^2]: The point of this rule is to ensure that normal paragraphs

1334+ starting with people's initials, like

1335+

1336+ B. Russell was an English philosopher.

1337+

1338+ do not get treated as list items.

1339+

1340+ This rule will not prevent

1341+

1342+ (C) 2007 Joe Smith

1343+

1344+ from being interpreted as a list item. In this case, a backslash

1345+ escape can be used:

1346+

1347+ (C\) 2007 Joe Smith

1348+

1349+The `fancy_lists` extension also allows '`#`' to be used as an

1350+ordered list marker in place of a numeral:

1351+

1352+ #. one

1353+ #. two

1354+

1355+**Extension: `startnum`**

1356+

1357+Pandoc also pays attention to the type of list marker used, and to the

1358+starting number, and both of these are preserved where possible in the

1359+output format. Thus, the following yields a list with numbers followed

1360+by a single parenthesis, starting with 9, and a sublist with lowercase

1361+roman numerals:

1362+

1363+ 9) Ninth

1364+ 10) Tenth

1365+ 11) Eleventh

1366+ i. subone

1367+ ii. subtwo

1368+ iii. subthree

1369+

1370+Pandoc will start a new list each time a different type of list

1371+marker is used. So, the following will create three lists:

1372+

1373+ (2) Two

1374+ (5) Three

1375+ 1. Four

1376+ * Five

1377+

1378+If default list markers are desired, use `#.`:

1379+

1380+ #. one

1381+ #. two

1382+ #. three

1383+

1384+

1385+### Definition lists ###

1386+

1387+**Extension: `definition_lists`**

1388+

1389+Pandoc supports definition lists, using a syntax inspired by

1390+[PHP Markdown Extra] and [reStructuredText]:[^3]

1391+

1392+ Term 1

1393+

1394+ : Definition 1

1395+

1396+ Term 2 with *inline markup*

1397+

1398+ : Definition 2

1399+

1400+ { some code, part of Definition 2 }

1401+

1402+ Third paragraph of definition 2.

1403+

1404+Each term must fit on one line, which may optionally be followed by

1405+a blank line, and must be followed by one or more definitions.

1406+A definition begins with a colon or tilde, which may be indented one

1407+or two spaces. The body of the definition (including the first line,

1408+aside from the colon or tilde) should be indented four spaces. A term may have

1409+multiple definitions, and each definition may consist of one or more block

1410+elements (paragraph, code block, list, etc.), each indented four spaces or one

1411+tab stop.

1412+

1413+If you leave space after the definition (as in the example above),

1414+the blocks of the definitions will be considered paragraphs. In some

1415+output formats, this will mean greater spacing between term/definition

1416+pairs. For a compact definition list, do not leave space between the

1417+definition and the next term:

1418+

1419+ Term 1

1420+ ~ Definition 1

1421+ Term 2

1422+ ~ Definition 2a

1423+ ~ Definition 2b

1424+

1425+[^3]: I have also been influenced by the suggestions of [David Wheeler](http://www.justatheory.com/computers/markup/modest-markdown-proposal.html).

1426+

1427+[PHP Markdown Extra]: http://www.michelf.com/projects/php-markdown/extra/

1428+

1429+

1430+### Numbered example lists ###

1431+

1432+**Extension: `example_lists`**

1433+

1434+The special list marker `@` can be used for sequentially numbered

1435+examples. The first list item with a `@` marker will be numbered '1',

1436+the next '2', and so on, throughout the document. The numbered examples

1437+need not occur in a single list; each new list using `@` will take up

1438+where the last stopped. So, for example:

1439+

1440+ (@) My first example will be numbered (1).

1441+ (@) My second example will be numbered (2).

1442+

1443+ Explanation of examples.

1444+

1445+ (@) My third example will be numbered (3).

1446+

1447+Numbered examples can be labeled and referred to elsewhere in the

1448+document:

1449+

1450+ (@good) This is a good example.

1451+

1452+ As (@good) illustrates, ...

1453+

1454+The label can be any string of alphanumeric characters, underscores,

1455+or hyphens.

1456+

1457+

1458+### Compact and loose lists ###

1459+

1460+Pandoc behaves differently from `Markdown.pl` on some "edge

1461+cases" involving lists. Consider this source:

1462+

1463+ + First

1464+ + Second:

1465+ - Fee

1466+ - Fie

1467+ - Foe

1468+

1469+ + Third

1470+

1471+Pandoc transforms this into a "compact list" (with no `<p>` tags around

1472+"First", "Second", or "Third"), while markdown puts `<p>` tags around

1473+"Second" and "Third" (but not "First"), because of the blank space

1474+around "Third". Pandoc follows a simple rule: if the text is followed by

1475+a blank line, it is treated as a paragraph. Since "Second" is followed

1476+by a list, and not a blank line, it isn't treated as a paragraph. The

1477+fact that the list is followed by a blank line is irrelevant. (Note:

1478+Pandoc works this way even when the `markdown_strict` format is specified. This

1479+behavior is consistent with the official markdown syntax description,

1480+even though it is different from that of `Markdown.pl`.)

1481+

1482+

1483+### Ending a list ###

1484+

1485+What if you want to put an indented code block after a list?

1486+

1487+ - item one

1488+ - item two

1489+

1490+ { my code block }

1491+

1492+Trouble! Here pandoc (like other markdown implementations) will treat

1493+`{ my code block }` as the second paragraph of item two, and not as

1494+a code block.

1495+

1496+To "cut off" the list after item two, you can insert some non-indented

1497+content, like an HTML comment, which won't produce visible output in

1498+any format:

1499+

1500+ - item one

1501+ - item two

1502+

1503+ <!-- end of list -->

1504+

1505+ { my code block }

1506+

1507+You can use the same trick if you want two consecutive lists instead

1508+of one big list:

1509+

1510+ 1. one

1511+ 2. two

1512+ 3. three

1513+

1514+ <!-- -->

1515+

1516+ 1. uno

1517+ 2. dos

1518+ 3. tres

1519+

1520+Horizontal rules

1521+----------------

1522+

1523+A line containing a row of three or more `*`, `-`, or `_` characters

1524+(optionally separated by spaces) produces a horizontal rule:

1525+

1526+ * * * *

1527+

1528+ ---------------

1529+

1530+

1531+Tables

1532+------

1533+

1534+Four kinds of tables may be used. The first three kinds presuppose the use of

1535+a fixed-width font, such as Courier. The fourth kind can be used with

1536+proportionally spaced fonts, as it does not require lining up columns.

1537+

1538+### Simple tables

1539+

1540+**Extension: `simple_tables`, `table_captions`**

1541+

1542+Simple tables look like this:

1543+

1544+ Right Left Center Default

1545+ ------- ------ ---------- -------

1546+ 12 12 12 12

1547+ 123 123 123 123

1548+ 1 1 1 1

1549+

1550+ Table: Demonstration of simple table syntax.

1551+

1552+The headers and table rows must each fit on one line. Column

1553+alignments are determined by the position of the header text relative

1554+to the dashed line below it:[^4]

1555+

1556+ - If the dashed line is flush with the header text on the right side

1557+ but extends beyond it on the left, the column is right-aligned.

1558+ - If the dashed line is flush with the header text on the left side

1559+ but extends beyond it on the right, the column is left-aligned.

1560+ - If the dashed line extends beyond the header text on both sides,

1561+ the column is centered.

1562+ - If the dashed line is flush with the header text on both sides,

1563+ the default alignment is used (in most cases, this will be left).

1564+

1565+[^4]: This scheme is due to Michel Fortin, who proposed it on the

1566+ [Markdown discussion list](http://six.pairlist.net/pipermail/markdown-discuss/2005-March/001097.html).

1567+

1568+The table must end with a blank line, or a line of dashes followed by

1569+a blank line. A caption may optionally be provided (as illustrated in

1570+the example above). A caption is a paragraph beginning with the string

1571+`Table:` (or just `:`), which will be stripped off. It may appear either

1572+before or after the table.

1573+

1574+The column headers may be omitted, provided a dashed line is used

1575+to end the table. For example:

1576+

1577+ ------- ------ ---------- -------

1578+ 12 12 12 12

1579+ 123 123 123 123

1580+ 1 1 1 1

1581+ ------- ------ ---------- -------

1582+

1583+When headers are omitted, column alignments are determined on the basis

1584+of the first line of the table body. So, in the tables above, the columns

1585+would be right, left, center, and right aligned, respectively.

1586+

1587+### Multiline tables

1588+

1589+**Extension: `multiline_tables`, `table_captions`**

1590+

1591+Multiline tables allow headers and table rows to span multiple lines

1592+of text (but cells that span multiple columns or rows of the table are

1593+not supported). Here is an example:

1594+

1595+ -------------------------------------------------------------

1596+ Centered Default Right Left

1597+ Header Aligned Aligned Aligned

1598+ ----------- ------- --------------- -------------------------

1599+ First row 12.0 Example of a row that

1600+ spans multiple lines.

1601+

1602+ Second row 5.0 Here's another one. Note

1603+ the blank line between

1604+ rows.

1605+ -------------------------------------------------------------

1606+

1607+ Table: Here's the caption. It, too, may span

1608+ multiple lines.

1609+

1610+These work like simple tables, but with the following differences:

1611+

1612+ - They must begin with a row of dashes, before the header text

1613+ (unless the headers are omitted).

1614+ - They must end with a row of dashes, then a blank line.

1615+ - The rows must be separated by blank lines.

1616+

1617+In multiline tables, the table parser pays attention to the widths of

1618+the columns, and the writers try to reproduce these relative widths in

1619+the output. So, if you find that one of the columns is too narrow in the

1620+output, try widening it in the markdown source.

1621+

1622+Headers may be omitted in multiline tables as well as simple tables:

1623+

1624+ ----------- ------- --------------- -------------------------

1625+ First row 12.0 Example of a row that

1626+ spans multiple lines.

1627+

1628+ Second row 5.0 Here's another one. Note

1629+ the blank line between

1630+ rows.

1631+ ----------- ------- --------------- -------------------------

1632+

1633+ : Here's a multiline table without headers.

1634+

1635+It is possible for a multiline table to have just one row, but the row

1636+should be followed by a blank line (and then the row of dashes that ends

1637+the table), or the table may be interpreted as a simple table.

1638+

1639+### Grid tables

1640+

1641+**Extension: `grid_tables`, `table_captions`**

1642+

1643+Grid tables look like this:

1644+

1645+ : Sample grid table.

1646+

1647+ +---------------+---------------+--------------------+

1648+ | Fruit | Price | Advantages |

1649+ +===============+===============+====================+

1650+ | Bananas | $1.34 | - built-in wrapper |

1651+ | | | - bright color |

1652+ +---------------+---------------+--------------------+

1653+ | Oranges | $2.10 | - cures scurvy |

1654+ | | | - tasty |

1655+ +---------------+---------------+--------------------+

1656+

1657+The row of `=`s separates the header from the table body, and can be

1658+omitted for a headerless table. The cells of grid tables may contain

1659+arbitrary block elements (multiple paragraphs, code blocks, lists,

1660+etc.). Alignments are not supported, nor are cells that span multiple

1661+columns or rows. Grid tables can be created easily using [Emacs table mode].

1662+

1663+ [Emacs table mode]: http://table.sourceforge.net/

1664+

1665+### Pipe tables

1666+

1667+**Extension: `pipe_tables`, `table_captions`**

1668+

1669+Pipe tables look like this:

1670+

1671+ | Right | Left | Default | Center |

1672+ |------:|:-----|---------|:------:|

1673+ | 12 | 12 | 12 | 12 |

1674+ | 123 | 123 | 123 | 123 |

1675+ | 1 | 1 | 1 | 1 |

1676+

1677+ : Demonstration of simple table syntax.

1678+

1679+The syntax is [the same as in PHP markdown extra]. The beginning and

1680+ending pipe characters are optional, but pipes are required between all

1681+columns. The colons indicate column alignment as shown. The header

1682+can be omitted, but the horizontal line must still be included, as

1683+it defines column alignments.

1684+

1685+Since the pipes indicate column boundaries, columns need not be vertically

1686+aligned, as they are in the above example. So, this is a perfectly

1687+legal (though ugly) pipe table:

1688+

1689+ fruit| price

1690+ -----|-----:

1691+ apple|2.05

1692+ pear|1.37

1693+ orange|3.09

1694+

1695+The cells of pipe tables cannot contain block elements like paragraphs

1696+and lists, and cannot span multiple lines.

1697+

1698+ [the same as in PHP markdown extra]:

1699+ http://michelf.ca/projects/php-markdown/extra/#table

1700+

1701+Note: Pandoc also recognizes pipe tables of the following

1702+form, as can produced by Emacs' orgtbl-mode:

1703+

1704+ | One | Two |

1705+ |-----+-------|

1706+ | my | table |

1707+ | is | nice |

1708+

1709+The difference is that `+` is used instead of `|`. Other orgtbl features

1710+are not supported. In particular, to get non-default column alignment,

1711+you'll need to add colons as above.

1712+

1713+Title block

1714+-----------

1715+

1716+**Extension: `pandoc_title_block`**

1717+

1718+If the file begins with a title block

1719+

1720+ % title

1721+ % author(s) (separated by semicolons)

1722+ % date

1723+

1724+it will be parsed as bibliographic information, not regular text. (It

1725+will be used, for example, in the title of standalone LaTeX or HTML

1726+output.) The block may contain just a title, a title and an author,

1727+or all three elements. If you want to include an author but no

1728+title, or a title and a date but no author, you need a blank line:

1729+

1730+ %

1731+ % Author

1732+

1733+ % My title

1734+ %

1735+ % June 15, 2006

1736+

1737+The title may occupy multiple lines, but continuation lines must

1738+begin with leading space, thus:

1739+

1740+ % My title

1741+ on multiple lines

1742+

1743+If a document has multiple authors, the authors may be put on

1744+separate lines with leading space, or separated by semicolons, or

1745+both. So, all of the following are equivalent:

1746+

1747+ % Author One

1748+ Author Two

1749+

1750+ % Author One; Author Two

1751+

1752+ % Author One;

1753+ Author Two

1754+

1755+The date must fit on one line.

1756+

1757+All three metadata fields may contain standard inline formatting

1758+(italics, links, footnotes, etc.).

1759+

1760+Title blocks will always be parsed, but they will affect the output only

1761+when the `--standalone` (`-s`) option is chosen. In HTML output, titles

1762+will appear twice: once in the document head -- this is the title that

1763+will appear at the top of the window in a browser -- and once at the

1764+beginning of the document body. The title in the document head can have

1765+an optional prefix attached (`--title-prefix` or `-T` option). The title

1766+in the body appears as an H1 element with class "title", so it can be

1767+suppressed or reformatted with CSS. If a title prefix is specified with

1768+`-T` and no title block appears in the document, the title prefix will

1769+be used by itself as the HTML title.

1770+

1771+The man page writer extracts a title, man page section number, and

1772+other header and footer information from the title line. The title

1773+is assumed to be the first word on the title line, which may optionally

1774+end with a (single-digit) section number in parentheses. (There should

1775+be no space between the title and the parentheses.) Anything after

1776+this is assumed to be additional footer and header text. A single pipe

1777+character (`|`) should be used to separate the footer text from the header

1778+text. Thus,

1779+

1780+ % PANDOC(1)

1781+

1782+will yield a man page with the title `PANDOC` and section 1.

1783+

1784+ % PANDOC(1) Pandoc User Manuals

1785+

1786+will also have "Pandoc User Manuals" in the footer.

1787+

1788+ % PANDOC(1) Pandoc User Manuals | Version 4.0

1789+

1790+will also have "Version 4.0" in the header.

1791+

1792+YAML metadata block

1793+-------------------

1794+

1795+**Extension: `yaml_metadata_block`**

1796+

1797+A YAML metadata block is a valid YAML object, delimited by a line of three

1798+hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots

1799+(`...`) at the bottom. A YAML metadata block may occur anywhere in the

1800+document, but if it is not at the beginning, it must be preceded by a blank

1801+line.

1802+

1803+Metadata will be taken from the fields of the YAML object and added to any

1804+existing document metadata. Metadata can contain lists and objects (nested

1805+arbitrarily), but all string scalars will be interpreted as markdown. Fields

1806+with names ending in an underscore will be ignored by pandoc. (They may be

1807+given a role by external processors.)

1808+

1809+A document may contain multiple metadata blocks. The metadata fields will

1810+be combined through a *left-biased union*: if two metadata blocks attempt

1811+to set the same field, the value from the first block will be taken.

1812+

1813+Note that YAML escaping rules must be followed. Thus, for example,

1814+if a title contains a colon, it must be quoted. The pipe character

1815+(`|`) can be used to begin an indented block that will be interpreted

1816+literally, without need for escaping. This form is necessary

1817+when the field contains blank lines:

1818+

1819+ ---

1820+ title: 'This is the title: it contains a colon'

1821+ author:

1822+ - name: Author One

1823+ affiliation: University of Somewhere

1824+ - name: Author Two

1825+ affiliation: University of Nowhere

1826+ tags: [nothing, nothingness]

1827+ abstract: |

1828+ This is the abstract.

1829+

1830+ It consists of two paragraphs.

1831+ ...

1832+

1833+Template variables will be set automatically from the metadata. Thus, for

1834+example, in writing HTML, the variable `abstract` will be set to the HTML

1835+equivalent of the markdown in the `abstract` field:

1836+

1837+ <p>This is the abstract.</p>

1838+ <p>It consists of two paragraphs.</p>

1839+

1840+

1841+Backslash escapes

1842+-----------------

1843+

1844+**Extension: `all_symbols_escapable`**

1845+

1846+Except inside a code block or inline code, any punctuation or space

1847+character preceded by a backslash will be treated literally, even if it

1848+would normally indicate formatting. Thus, for example, if one writes

1849+

1850+ *\*hello\**

1851+

1852+one will get

1853+

1854+ <em>*hello*</em>

1855+

1856+instead of

1857+

1858+ <strong>hello</strong>

1859+

1860+This rule is easier to remember than standard markdown's rule,

1861+which allows only the following characters to be backslash-escaped:

1862+

1863+ \`*_{}[]()>#+-.!

1864+

1865+(However, if the `markdown_strict` format is used, the standard markdown rule

1866+will be used.)

1867+

1868+A backslash-escaped space is parsed as a nonbreaking space. It will

1869+appear in TeX output as `~` and in HTML and XML as `\&#160;` or

1870+`\&nbsp;`.

1871+

1872+A backslash-escaped newline (i.e. a backslash occurring at the end of

1873+a line) is parsed as a hard line break. It will appear in TeX output as

1874+`\\` and in HTML as `<br />`. This is a nice alternative to

1875+markdown's "invisible" way of indicating hard line breaks using

1876+two trailing spaces on a line.

1877+

1878+Backslash escapes do not work in verbatim contexts.

1879+

1880+Smart punctuation

1881+-----------------

1882+

1883+**Extension**

1884+

1885+If the `--smart` option is specified, pandoc will produce typographically

1886+correct output, converting straight quotes to curly quotes, `---` to

1887+em-dashes, `--` to en-dashes, and `...` to ellipses. Nonbreaking spaces

1888+are inserted after certain abbreviations, such as "Mr."

1889+

1890+Note: if your LaTeX template uses the `csquotes` package, pandoc will

1891+detect automatically this and use `\enquote{...}` for quoted text.

1892+

1893+Inline formatting

1894+-----------------

1895+

1896+### Emphasis ###

1897+

1898+To *emphasize* some text, surround it with `*`s or `_`, like this:

1899+

1900+ This text is _emphasized with underscores_, and this

1901+ is *emphasized with asterisks*.

1902+

1903+Double `*` or `_` produces **strong emphasis**:

1904+

1905+ This is **strong emphasis** and __with underscores__.

1906+

1907+A `*` or `_` character surrounded by spaces, or backslash-escaped,

1908+will not trigger emphasis:

1909+

1910+ This is * not emphasized *, and \*neither is this\*.

1911+

1912+**Extension: `intraword_underscores`**

1913+

1914+Because `_` is sometimes used inside words and identifiers,

1915+pandoc does not interpret a `_` surrounded by alphanumeric

1916+characters as an emphasis marker. If you want to emphasize

1917+just part of a word, use `*`:

1918+

1919+ feas*ible*, not feas*able*.

1920+

1921+

1922+### Strikeout ###

1923+

1924+**Extension: `strikeout`**

1925+

1926+To strikeout a section of text with a horizontal line, begin and end it

1927+with `~~`. Thus, for example,

1928+

1929+ This ~~is deleted text.~~

1930+

1931+

1932+### Superscripts and subscripts ###

1933+

1934+**Extension: `superscript`, `subscript`**

1935+

1936+Superscripts may be written by surrounding the superscripted text by `^`

1937+characters; subscripts may be written by surrounding the subscripted

1938+text by `~` characters. Thus, for example,

1939+

1940+ H~2~O is a liquid. 2^10^ is 1024.

1941+

1942+If the superscripted or subscripted text contains spaces, these spaces

1943+must be escaped with backslashes. (This is to prevent accidental

1944+superscripting and subscripting through the ordinary use of `~` and `^`.)

1945+Thus, if you want the letter P with 'a cat' in subscripts, use

1946+`P~a\ cat~`, not `P~a cat~`.

1947+

1948+

1949+### Verbatim ###

1950+

1951+To make a short span of text verbatim, put it inside backticks:

1952+

1953+ What is the difference between `>>=` and `>>`?

1954+

1955+If the verbatim text includes a backtick, use double backticks:

1956+

1957+ Here is a literal backtick `` ` ``.

1958+

1959+(The spaces after the opening backticks and before the closing

1960+backticks will be ignored.)

1961+

1962+The general rule is that a verbatim span starts with a string

1963+of consecutive backticks (optionally followed by a space)

1964+and ends with a string of the same number of backticks (optionally

1965+preceded by a space).

1966+

1967+Note that backslash-escapes (and other markdown constructs) do not

1968+work in verbatim contexts:

1969+

1970+ This is a backslash followed by an asterisk: `\*`.

1971+

1972+**Extension: `inline_code_attributes`**

1973+

1974+Attributes can be attached to verbatim text, just as with

1975+[fenced code blocks](#fenced-code-blocks):

1976+

1977+ `<$>`{.haskell}

1978+

1979+Math

1980+----

1981+

1982+**Extension: `tex_math_dollars`**

1983+

1984+Anything between two `$` characters will be treated as TeX math. The

1985+opening `$` must have a character immediately to its right, while the

1986+closing `$` must have a character immediately to its left. Thus,

1987+`$20,000 and $30,000` won't parse as math. If for some reason

1988+you need to enclose text in literal `$` characters, backslash-escape

1989+them and they won't be treated as math delimiters.

1990+

1991+TeX math will be printed in all output formats. How it is rendered

1992+depends on the output format:

1993+

1994+Markdown, LaTeX, Org-Mode, ConTeXt

1995+ ~ It will appear verbatim between `$` characters.

1996+

1997+reStructuredText

1998+ ~ It will be rendered using an interpreted text role `:math:`, as described

1999+ [here](http://www.american.edu/econ/itex2mml/mathhack.rst).

2000+

2001+AsciiDoc

2002+ ~ It will be rendered as `latexmath:[...]`.

2003+

2004+Texinfo

2005+ ~ It will be rendered inside a `@math` command.

2006+

2007+groff man

2008+ ~ It will be rendered verbatim without `$`'s.

2009+

2010+MediaWiki

2011+ ~ It will be rendered inside `<math>` tags.

2012+

2013+Textile

2014+ ~ It will be rendered inside `<span class="math">` tags.

2015+

2016+RTF, OpenDocument, ODT

2017+ ~ It will be rendered, if possible, using unicode characters,

2018+ and will otherwise appear verbatim.

2019+

2020+Docbook

2021+ ~ If the `--mathml` flag is used, it will be rendered using mathml

2022+ in an `inlineequation` or `informalequation` tag. Otherwise it

2023+ will be rendered, if possible, using unicode characters.

2024+

2025+Docx

2026+ ~ It will be rendered using OMML math markup.

2027+

2028+FictionBook2

2029+ ~ If the `--webtex` option is used, formulas are rendered as images

2030+ using Google Charts or other compatible web service, downloaded

2031+ and embedded in the e-book. Otherwise, they will appear verbatim.

2032+

2033+HTML, Slidy, DZSlides, S5, EPUB

2034+ ~ The way math is rendered in HTML will depend on the

2035+ command-line options selected:

2036+

2037+ 1. The default is to render TeX math as far as possible using unicode

2038+ characters, as with RTF, DocBook, and OpenDocument output. Formulas

2039+ are put inside a `span` with `class="math"`, so that they may be

2040+ styled differently from the surrounding text if needed.

2041+

2042+ 2. If the `--latexmathml` option is used, TeX math will be displayed

2043+ between `$` or `$$` characters and put in `<span>` tags with class `LaTeX`.

2044+ The [LaTeXMathML] script will be used to render it as formulas.

2045+ (This trick does not work in all browsers, but it works in Firefox.

2046+ In browsers that do not support LaTeXMathML, TeX math will appear

2047+ verbatim between `$` characters.)

2048+

2049+ 3. If the `--jsmath` option is used, TeX math will be put inside

2050+ `<span>` tags (for inline math) or `<div>` tags (for display math)

2051+ with class `math`. The [jsMath] script will be used to render

2052+ it.

2053+

2054+ 4. If the `--mimetex` option is used, the [mimeTeX] CGI script will

2055+ be called to generate images for each TeX formula. This should

2056+ work in all browsers. The `--mimetex` option takes an optional URL

2057+ as argument. If no URL is specified, it will be assumed that the

2058+ mimeTeX CGI script is at `/cgi-bin/mimetex.cgi`.

2059+

2060+ 5. If the `--gladtex` option is used, TeX formulas will be enclosed

2061+ in `<eq>` tags in the HTML output. The resulting `htex` file may then

2062+ be processed by [gladTeX], which will produce image files for each

2063+ formula and an `html` file with links to these images. So, the

2064+ procedure is:

2065+

2066+ pandoc -s --gladtex myfile.txt -o myfile.htex

2067+ gladtex -d myfile-images myfile.htex

2068+ # produces myfile.html and images in myfile-images

2069+

2070+ 6. If the `--webtex` option is used, TeX formulas will be converted

2071+ to `<img>` tags that link to an external script that converts

2072+ formulas to images. The formula will be URL-encoded and concatenated

2073+ with the URL provided. If no URL is specified, the Google Chart

2074+ API will be used (`http://chart.apis.google.com/chart?cht=tx&chl=`).

2075+

2076+ 7. If the `--mathjax` option is used, TeX math will be displayed

2077+ between `\(...\)` (for inline math) or `\[...\]` (for display

2078+ math) and put in `<span>` tags with class `math`.

2079+ The [MathJax] script will be used to render it as formulas.

2080+

2081+Raw HTML

2082+--------

2083+

2084+**Extension: `raw_html`**

2085+

2086+Markdown allows you to insert raw HTML (or DocBook) anywhere in a document

2087+(except verbatim contexts, where `<`, `>`, and `&` are interpreted

2088+literally). (Techncially this is not an extension, since standard

2089+markdown allows it, but it has been made an extension so that it can

2090+be disabled if desired.)

2091+

2092+The raw HTML is passed through unchanged in HTML, S5, Slidy, Slideous,

2093+DZSlides, EPUB, Markdown, and Textile output, and suppressed in other

2094+formats.

2095+

2096+**Extension: `markdown_in_html_blocks`**

2097+

2098+Standard markdown allows you to include HTML "blocks": blocks

2099+of HTML between balanced tags that are separated from the surrounding text

2100+with blank lines, and start and end at the left margin. Within

2101+these blocks, everything is interpreted as HTML, not markdown;

2102+so (for example), `*` does not signify emphasis.

2103+

2104+Pandoc behaves this way when the `markdown_strict` format is used; but

2105+by default, pandoc interprets material between HTML block tags as markdown.

2106+Thus, for example, Pandoc will turn

2107+

2108+ <table>

2109+ <tr>

2110+ <td>*one*</td>

2111+ <td>[a link](http://google.com)</td>

2112+ </tr>

2113+ </table>

2114+

2115+into

2116+

2117+ <table>

2118+ <tr>

2119+ <td><em>one</em></td>

2120+ <td><a href="http://google.com">a link</a></td>

2121+ </tr>

2122+ </table>

2123+

2124+whereas `Markdown.pl` will preserve it as is.

2125+

2126+There is one exception to this rule: text between `<script>` and

2127+`<style>` tags is not interpreted as markdown.

2128+

2129+This departure from standard markdown should make it easier to mix

2130+markdown with HTML block elements. For example, one can surround

2131+a block of markdown text with `<div>` tags without preventing it

2132+from being interpreted as markdown.

2133+

2134+Raw TeX

2135+-------

2136+

2137+**Extension: `raw_tex`**

2138+

2139+In addition to raw HTML, pandoc allows raw LaTeX, TeX, and ConTeXt to be

2140+included in a document. Inline TeX commands will be preserved and passed

2141+unchanged to the LaTeX and ConTeXt writers. Thus, for example, you can use

2142+LaTeX to include BibTeX citations:

2143+

2144+ This result was proved in \cite{jones.1967}.

2145+

2146+Note that in LaTeX environments, like

2147+

2148+ \begin{tabular}{|l|l|}\hline

2149+ Age & Frequency \\ \hline

2150+ 18--25 & 15 \\

2151+ 26--35 & 33 \\

2152+ 36--45 & 22 \\ \hline

2153+ \end{tabular}

2154+

2155+the material between the begin and end tags will be interpreted as raw

2156+LaTeX, not as markdown.

2157+

2158+Inline LaTeX is ignored in output formats other than Markdown, LaTeX,

2159+and ConTeXt.

2160+

2161+LaTeX macros

2162+------------

2163+

2164+**Extension: `latex_macros`**

2165+

2166+For output formats other than LaTeX, pandoc will parse LaTeX `\newcommand` and

2167+`\renewcommand` definitions and apply the resulting macros to all LaTeX

2168+math. So, for example, the following will work in all output formats,

2169+not just LaTeX:

2170+

2171+ \newcommand{\tuple}[1]{\langle #1 \rangle}

2172+

2173+ $\tuple{a, b, c}$

2174+

2175+In LaTeX output, the `\newcommand` definition will simply be passed

2176+unchanged to the output.

2177+

2178+

2179+Links

2180+-----

2181+

2182+Markdown allows links to be specified in several ways.

2183+

2184+### Automatic links ###

2185+

2186+If you enclose a URL or email address in pointy brackets, it

2187+will become a link:

2188+

2189+ <http://google.com>

2190+ <sam@green.eggs.ham>

2191+

2192+### Inline links ###

2193+

2194+An inline link consists of the link text in square brackets,

2195+followed by the URL in parentheses. (Optionally, the URL can

2196+be followed by a link title, in quotes.)

2197+

2198+ This is an [inline link](/url), and here's [one with

2199+ a title](http://fsf.org "click here for a good time!").

2200+

2201+There can be no space between the bracketed part and the parenthesized part.

2202+The link text can contain formatting (such as emphasis), but the title cannot.

2203+

2204+

2205+### Reference links ###

2206+

2207+An *explicit* reference link has two parts, the link itself and the link

2208+definition, which may occur elsewhere in the document (either

2209+before or after the link).

2210+

2211+The link consists of link text in square brackets, followed by a label in

2212+square brackets. (There can be space between the two.) The link definition

2213+consists of the bracketed label, followed by a colon and a space, followed by

2214+the URL, and optionally (after a space) a link title either in quotes or in

2215+parentheses.

2216+

2217+Here are some examples:

2218+

2219+ [my label 1]: /foo/bar.html "My title, optional"

2220+ [my label 2]: /foo

2221+ [my label 3]: http://fsf.org (The free software foundation)

2222+ [my label 4]: /bar#special 'A title in single quotes'

2223+

2224+The URL may optionally be surrounded by angle brackets:

2225+

2226+ [my label 5]: <http://foo.bar.baz>

2227+

2228+The title may go on the next line:

2229+

2230+ [my label 3]: http://fsf.org

2231+ "The free software foundation"

2232+

2233+Note that link labels are not case sensitive. So, this will work:

2234+

2235+ Here is [my link][FOO]

2236+

2237+ [Foo]: /bar/baz

2238+

2239+In an *implicit* reference link, the second pair of brackets is

2240+empty, or omitted entirely:

2241+

2242+ See [my website][], or [my website].

2243+

2244+ [my website]: http://foo.bar.baz

2245+

2246+Note: In `Markdown.pl` and most other markdown implementations,

2247+reference link definitions cannot occur in nested constructions

2248+such as list items or block quotes. Pandoc lifts this arbitrary

2249+seeming restriction. So the following is fine in pandoc, though

2250+not in most other implementations:

2251+

2252+ > My block [quote].

2253+ >

2254+ > [quote]: /foo

2255+

2256+### Internal links

2257+

2258+To link to another section of the same document, use the automatically

2259+generated identifier (see [Header identifiers in HTML, LaTeX, and

2260+ConTeXt](#header-identifiers-in-html-latex-and-context), below).

2261+For example:

2262+

2263+ See the [Introduction](#introduction).

2264+

2265+or

2266+

2267+ See the [Introduction].

2268+

2269+ [Introduction]: #introduction

2270+

2271+Internal links are currently supported for HTML formats (including

2272+HTML slide shows and EPUB), LaTeX, and ConTeXt.

2273+

2274+Images

2275+------

2276+

2277+A link immediately preceded by a `!` will be treated as an image.

2278+The link text will be used as the image's alt text:

2279+

2280+ 

2281+

2282+ ![movie reel]

2283+

2284+ [movie reel]: movie.gif

2285+

2286+### Pictures with captions ###

2287+

2288+**Extension: `implicit_figures`**

2289+

2290+An image occurring by itself in a paragraph will be rendered as

2291+a figure with a caption.[^5] (In LaTeX, a figure environment will be

2292+used; in HTML, the image will be placed in a `div` with class

2293+`figure`, together with a caption in a `p` with class `caption`.)

2294+The image's alt text will be used as the caption.

2295+

2296+ 

2297+

2298+[^5]: This feature is not yet implemented for RTF, OpenDocument, or

2299+ ODT. In those formats, you'll just get an image in a paragraph by

2300+ itself, with no caption.

2301+

2302+If you just want a regular inline image, just make sure it is not

2303+the only thing in the paragraph. One way to do this is to insert a

2304+nonbreaking space after the image:

2305+

2306+ \

2307+

2308+

2309+Footnotes

2310+---------

2311+

2312+**Extension: `footnotes`**

2313+

2314+Pandoc's markdown allows footnotes, using the following syntax:

2315+

2316+ Here is a footnote reference,[^1] and another.[^longnote]

2317+

2318+ [^1]: Here is the footnote.

2319+

2320+ [^longnote]: Here's one with multiple blocks.

2321+

2322+ Subsequent paragraphs are indented to show that they

2323+ belong to the previous footnote.

2324+

2325+ { some.code }

2326+

2327+ The whole paragraph can be indented, or just the first

2328+ line. In this way, multi-paragraph footnotes work like

2329+ multi-paragraph list items.

2330+

2331+ This paragraph won't be part of the note, because it

2332+ isn't indented.

2333+

2334+The identifiers in footnote references may not contain spaces, tabs,

2335+or newlines. These identifiers are used only to correlate the

2336+footnote reference with the note itself; in the output, footnotes

2337+will be numbered sequentially.

2338+

2339+The footnotes themselves need not be placed at the end of the

2340+document. They may appear anywhere except inside other block elements

2341+(lists, block quotes, tables, etc.).

2342+

2343+**Extension: `inline_notes`**

2344+

2345+Inline footnotes are also allowed (though, unlike regular notes,

2346+they cannot contain multiple paragraphs). The syntax is as follows:

2347+

2348+ Here is an inline note.^[Inlines notes are easier to write, since

2349+ you don't have to pick an identifier and move down to type the

2350+ note.]

2351+

2352+Inline and regular footnotes may be mixed freely.

2353+

2354+

2355+Citations

2356+---------

2357+

2358+**Extension: `citations`**

2359+

2360+Using an external filter, `pandoc-citeproc`, pandoc can automatically generate

2361+citations and a bibliography in a number of styles. Basic usage is

2362+

2363+ pandoc --filter pandoc-citeproc myinput.txt

2364+

2365+In order to use this feature, you will need to specify a bibliography file

2366+using the `bibliography` metadata field in a YAML metadata section.

2367+The bibliography may have any of these formats:

2368+

2369+ Format File extension

2370+ ------------ --------------

2371+ MODS .mods

2372+ BibLaTeX .bib

2373+ BibTeX .bibtex

2374+ RIS .ris

2375+ EndNote .enl

2376+ EndNote XML .xml

2377+ ISI .wos

2378+ MEDLINE .medline

2379+ Copac .copac

2380+ JSON citeproc .json

2381+

2382+Note that `.bib` can generally be used with both BibTeX and BibLaTeX

2383+files, but you can use `.bibtex` to force BibTeX.

2384+

2385+Alternatively you can use a `references` field in the document's YAML

2386+metadata. This should include an array of YAML-encoded references,

2387+for example:

2388+

2389+ ---

2390+ references:

2391+ - id: fenner2012a

2392+ title: One-click science marketing

2393+ author:

2394+ - family: Fenner

2395+ given: Martin

2396+ container-title: Nature Materials

2397+ volume: 11

2398+ URL: 'http://dx.doi.org/10.1038/nmat3283'

2399+ DOI: 10.1038/nmat3283

2400+ issue: 4

2401+ publisher: Nature Publishing Group

2402+ page: 261-263

2403+ type: article-journal

2404+ issued:

2405+ year: 2012

2406+ month: 3

2407+ ...

2408+

2409+(The program `mods2yaml`, which comes with `pandoc-citeproc`, can help produce

2410+these from a MODS reference collection.)

2411+

2412+By default, `pandoc-citeproc` will use a Chicago author-date format for

2413+citations and references. To use another style, you will need to specify

2414+a [CSL] 1.0 style file in the `csl` metadata field. A primer on creating and

2415+modifying CSL styles can be found at

2416+<http://citationstyles.org/downloads/primer.html>. A repository of CSL styles

2417+can be found at <https://github.com/citation-style-language/styles>. See also

2418+<http://zotero.org/styles> for easy browsing.

2419+

2420+Citations go inside square brackets and are separated by semicolons.

2421+Each citation must have a key, composed of '@' + the citation

2422+identifier from the database, and may optionally have a prefix,

2423+a locator, and a suffix. Here are some examples:

2424+

2425+ Blah blah [see @doe99, pp. 33-35; also @smith04, ch. 1].

2426+

2427+ Blah blah [@doe99, pp. 33-35, 38-39 and *passim*].

2428+

2429+ Blah blah [@smith04; @doe99].

2430+

2431+A minus sign (`-`) before the `@` will suppress mention of

2432+the author in the citation. This can be useful when the

2433+author is already mentioned in the text:

2434+

2435+ Smith says blah [-@smith04].

2436+

2437+You can also write an in-text citation, as follows:

2438+

2439+ @smith04 says blah.

2440+

2441+ @smith04 [p. 33] says blah.

2442+

2443+If the style calls for a list of works cited, it will be placed

2444+at the end of the document. Normally, you will want to end your

2445+document with an appropriate header:

2446+

2447+ last paragraph...

2448+

2449+ # References

2450+

2451+The bibliography will be inserted after this header.

2452+

2453+Non-pandoc extensions

2454+---------------------

2455+

2456+The following markdown syntax extensions are not enabled by default

2457+in pandoc, but may be enabled by adding `+EXTENSION` to the format

2458+name, where `EXTENSION` is the name of the extension. Thus, for

2459+example, `markdown+hard_line_breaks` is markdown with hard line breaks.

2460+

2461+**Extension: `lists_without_preceding_blankline`**\

2462+Allow a list to occur right after a paragraph, with no intervening

2463+blank space.

2464+

2465+**Extension: `hard_line_breaks`**\

2466+Causes all newlines within a paragraph to be interpreted as hard line

2467+breaks instead of spaces.

2468+

2469+**Extension: `ignore_line_breaks`**\

2470+Causes newlines within a paragraph to be ignored, rather than being

2471+treated as spaces or as hard line breaks. This option is intended for

2472+use with East Asian languages where spaces are not used between words,

2473+but text is divided into lines for readability.

2474+

2475+**Extension: `tex_math_single_backslash`**\

2476+Causes anything between `\(` and `\)` to be interpreted as inline

2477+TeX math, and anything between `\[` and `\]` to be interpreted

2478+as display TeX math. Note: a drawback of this extension is that

2479+it precludes escaping `(` and `[`.

2480+

2481+**Extension: `tex_math_double_backslash`**\

2482+Causes anything between `\\(` and `\\)` to be interpreted as inline

2483+TeX math, and anything between `\\[` and `\\]` to be interpreted

2484+as display TeX math.

2485+

2486+**Extension: `markdown_attribute`**\

2487+By default, pandoc interprets material inside block-level tags as markdown.

2488+This extension changes the behavior so that markdown is only parsed

2489+inside block-level tags if the tags have the attribute `markdown=1`.

2490+

2491+**Extension: `mmd_title_block`**\

2492+Enables a [MultiMarkdown] style title block at the top of

2493+the document, for example:

2494+

2495+ Title: My title

2496+ Author: John Doe

2497+ Date: September 1, 2008

2498+ Comment: This is a sample mmd title block, with

2499+ a field spanning multiple lines.

2500+

2501+See the MultiMarkdown documentation for details. Note that only title,

2502+author, and date are recognized; other fields are simply ignored by

2503+pandoc. If `pandoc_title_block` or `yaml_metadata_block` is enabled,

2504+it will take precedence over `mmd_title_block`.

2505+

2506+ [MultiMarkdown]: http://fletcherpenney.net/multimarkdown/

2507+

2508+**Extension: `abbreviations`**\

2509+Parses PHP Markdown Extra abbreviation keys, like

2510+

2511+ *[HTML]: Hyper Text Markup Language

2512+

2513+Note that the pandoc document model does not support

2514+abbreviations, so if this extension is enabled, abbreviation keys are

2515+simply skipped (as opposed to being parsed as paragraphs).

2516+

2517+**Extension: `autolink_bare_uris`**\

2518+Makes all absolute URIs into links, even when not surrounded by

2519+pointy braces `<...>`.

2520+

2521+**Extension: `ascii_identifiers`**\

2522+Causes the identifiers produced by `auto_identifiers` to be pure ASCII.

2523+Accents are stripped off of accented latin letters, and non-latin

2524+letters are omitted.

2525+

2526+**Extension: `link_attributes`**\

2527+Parses multimarkdown style key-value attributes on link and image references.

2528+Note that pandoc's internal document model provides nowhere to put

2529+these, so they are presently just ignored.

2530+

2531+**Extension: `mmd_header_identifiers`**\

2532+Parses multimarkdown style header identifiers (in square brackets,

2533+after the header but before any trailing `#`s in an ATX header).

2534+

2535+Markdown variants

2536+-----------------

2537+

2538+In addition to pandoc's extended markdown, the following markdown

2539+variants are supported:

2540+

2541+`markdown_phpextra` (PHP Markdown Extra)

2542+: `footnotes`, `pipe_tables`, `raw_html`, `markdown_attribute`,

2543+ `fenced_code_blocks`, `definition_lists`, `intraword_underscores`,

2544+ `header_attributes`, `abbreviations`.

2545+

2546+`markdown_github` (Github-flavored Markdown)

2547+: `pipe_tables`, `raw_html`, `tex_math_single_backslash`,

2548+ `fenced_code_blocks`, `fenced_code_attributes`, `auto_identifiers`,

2549+ `ascii_identifiers`, `backtick_code_blocks`, `autolink_bare_uris`,

2550+ `intraword_underscores`, `strikeout`, `hard_line_breaks`

2551+

2552+`markdown_mmd` (MultiMarkdown)

2553+: `pipe_tables` `raw_html`, `markdown_attribute`, `link_attributes`,

2554+ `raw_tex`, `tex_math_double_backslash`, `intraword_underscores`,

2555+ `mmd_title_block`, `footnotes`, `definition_lists`,

2556+ `all_symbols_escapable`, `implicit_header_references`,

2557+ `auto_identifiers`, `mmd_header_identifiers`

2558+

2559+`markdown_strict` (Markdown.pl)

2560+: `raw_html`

2561+

2562+Producing slide shows with Pandoc

2563+=================================

2564+

2565+You can use Pandoc to produce an HTML + javascript slide presentation

2566+that can be viewed via a web browser. There are five ways to do this,

2567+using [S5], [DZSlides], [Slidy], [Slideous], or [reveal.js].

2568+You can also produce a PDF slide show using LaTeX [beamer].

2569+

2570+Here's the markdown source for a simple slide show, `habits.txt`:

2571+

2572+ % Habits

2573+ % John Doe

2574+ % March 22, 2005

2575+

2576+ # In the morning

2577+

2578+ ## Getting up

2579+

2580+ - Turn off alarm

2581+ - Get out of bed

2582+

2583+ ## Breakfast

2584+

2585+ - Eat eggs

2586+ - Drink coffee

2587+

2588+ # In the evening

2589+

2590+ ## Dinner

2591+

2592+ - Eat spaghetti

2593+ - Drink wine

2594+

2595+ ------------------

2596+

2597+ 

2598+

2599+ ## Going to sleep

2600+

2601+ - Get in bed

2602+ - Count sheep

2603+

2604+To produce an HTML/javascript slide show, simply type

2605+

2606+ pandoc -t FORMAT -s habits.txt -o habits.html

2607+

2608+where `FORMAT` is either `s5`, `slidy`, `slideous`, `dzslides`, or `revealjs`.

2609+

2610+For Slidy, Slideous, reveal.js, and S5, the file produced by pandoc with the

2611+`-s/--standalone` option embeds a link to javascripts and CSS files, which are

2612+assumed to be available at the relative path `s5/default` (for S5), `slideous`

2613+(for Slideous), `reveal.js` (for reveal.js), or at the Slidy website at

2614+`w3.org` (for Slidy). (These paths can be changed by setting the `slidy-url`,

2615+`slideous-url`, `revealjs-url`, or `s5-url` variables; see `--variable`,

2616+above.) For DZSlides, the (relatively short) javascript and css are included in

2617+the file by default.

2618+

2619+With all HTML slide formats, the `--self-contained` option can be used to

2620+produce a single file that contains all of the data necessary to display the

2621+slide show, including linked scripts, stylesheets, images, and videos.

2622+

2623+To produce a PDF slide show using beamer, type

2624+

2625+ pandoc -t beamer habits.txt -o habits.pdf

2626+

2627+Note that a reveal.js slide show can also be converted to a PDF

2628+by printing it to a file from the browser.

2629+

2630+Structuring the slide show

2631+--------------------------

2632+

2633+By default, the *slide level* is the highest header level in

2634+the hierarchy that is followed immediately by content, and not another

2635+header, somewhere in the document. In the example above, level 1 headers

2636+are always followed by level 2 headers, which are followed by content,

2637+so 2 is the slide level. This default can be overridden using

2638+the `--slide-level` option.

2639+

2640+The document is carved up into slides according to the following

2641+rules:

2642+

2643+ * A horizontal rule always starts a new slide.

2644+

2645+ * A header at the slide level always starts a new slide.

2646+

2647+ * Headers *below* the slide level in the hierarchy create

2648+ headers *within* a slide.

2649+

2650+ * Headers *above* the slide level in the hierarchy create

2651+ "title slides," which just contain the section title

2652+ and help to break the slide show into sections.

2653+

2654+ * A title page is constructed automatically from the document's title

2655+ block, if present. (In the case of beamer, this can be disabled

2656+ by commenting out some lines in the default template.)

2657+

2658+These rules are designed to support many different styles of slide show. If

2659+you don't care about structuring your slides into sections and subsections,

2660+you can just use level 1 headers for all each slide. (In that case, level 1

2661+will be the slide level.) But you can also structure the slide show into

2662+sections, as in the example above.

2663+

2664+Note: in reveal.js slide shows, if slide level is 2, a two-dimensional

2665+layout will be produced, with level 1 headers building horizontally

2666+and level 2 headers building vertically. It is not recommended that

2667+you use deeper nesting of section levels with reveal.js.

2668+

2669+Incremental lists

2670+-----------------

2671+

2672+By default, these writers produces lists that display "all at once."

2673+If you want your lists to display incrementally (one item at a time),

2674+use the `-i` option. If you want a particular list to depart from the

2675+default (that is, to display incrementally without the `-i` option and

2676+all at once with the `-i` option), put it in a block quote:

2677+

2678+ > - Eat spaghetti

2679+ > - Drink wine

2680+

2681+In this way incremental and nonincremental lists can be mixed in

2682+a single document.

2683+

2684+Inserting pauses

2685+----------------

2686+

2687+You can add "pauses" within a slide by including a paragraph containing

2688+three dots, separated by spaces:

2689+

2690+ # Slide with a pause

2691+

2692+ content before the pause

2693+

2694+ . . .

2695+

2696+ content after the pause

2697+

2698+Styling the slides

2699+------------------

2700+

2701+You can change the style of HTML slides by putting customized CSS files

2702+in `$DATADIR/s5/default` (for S5), `$DATADIR/slidy` (for Slidy),

2703+or `$DATADIR/slideous` (for Slideous),

2704+where `$DATADIR` is the user data directory (see `--data-dir`, above).

2705+The originals may be found in pandoc's system data directory (generally

2706+`$CABALDIR/pandoc-VERSION/s5/default`). Pandoc will look there for any

2707+files it does not find in the user data directory.

2708+

2709+For dzslides, the CSS is included in the HTML file itself, and may

2710+be modified there.

2711+

2712+For reveal.js, themes can be used by setting the `theme` variable,

2713+for example:

2714+

2715+ -V theme=moon

2716+

2717+Or you can specify a custom stylesheet using the `--css` option.

2718+

2719+To style beamer slides, you can specify a beamer "theme" or "colortheme"

2720+using the `-V` option:

2721+

2722+ pandoc -t beamer habits.txt -V theme:Warsaw -o habits.pdf

2723+

2724+Note that header attributes will turn into slide attributes

2725+(on a `<div>` or `<section>`) in HTML slide formats, allowing you

2726+to style individual slides. In Beamer, the only header attribute

2727+that affects slides is the `allowframebreaks` class, which sets the

2728+`allowframebreaks` option, causing multiple slides to be created

2729+if the content overfills the frame. This is recommended especially for

2730+bibliographies:

2731+

2732+ # References {.allowframebreaks}

2733+

2734+Literate Haskell support

2735+========================

2736+

2737+If you append `+lhs` (or `+literate_haskell`) to an appropriate input or output

2738+format (`markdown`, `mardkown_strict`, `rst`, or `latex` for input or output;

2739+`beamer`, `html` or `html5` for output only), pandoc will treat the document as

2740+literate Haskell source. This means that

2741+

2742+ - In markdown input, "bird track" sections will be parsed as Haskell

2743+ code rather than block quotations. Text between `\begin{code}`

2744+ and `\end{code}` will also be treated as Haskell code.

2745+

2746+ - In markdown output, code blocks with classes `haskell` and `literate`

2747+ will be rendered using bird tracks, and block quotations will be

2748+ indented one space, so they will not be treated as Haskell code.

2749+ In addition, headers will be rendered setext-style (with underlines)

2750+ rather than atx-style (with '#' characters). (This is because ghc

2751+ treats '#' characters in column 1 as introducing line numbers.)

2752+

2753+ - In restructured text input, "bird track" sections will be parsed

2754+ as Haskell code.

2755+

2756+ - In restructured text output, code blocks with class `haskell` will

2757+ be rendered using bird tracks.

2758+

2759+ - In LaTeX input, text in `code` environments will be parsed as

2760+ Haskell code.

2761+

2762+ - In LaTeX output, code blocks with class `haskell` will be rendered

2763+ inside `code` environments.

2764+

2765+ - In HTML output, code blocks with class `haskell` will be rendered

2766+ with class `literatehaskell` and bird tracks.

2767+

2768+Examples:

2769+

2770+ pandoc -f markdown+lhs -t html

2771+

2772+reads literate Haskell source formatted with markdown conventions and writes

2773+ordinary HTML (without bird tracks).

2774+

2775+ pandoc -f markdown+lhs -t html+lhs

2776+

2777+writes HTML with the Haskell code in bird tracks, so it can be copied

2778+and pasted as literate Haskell source.

2779+

2780+Custom writers

2781+==============

2782+

2783+Pandoc can be extended with custom writers written in [lua]. (Pandoc

2784+includes a lua interpreter, so lua need not be installed separately.)

2785+

2786+To use a custom writer, simply specify the path to the lua script

2787+in place of the output format. For example:

2788+

2789+ pandoc -t data/sample.lua

2790+

2791+Creating a custom writer requires writing a lua function for each

2792+possible element in a pandoc document. To get a documented example

2793+which you can modify according to your needs, do

2794+

2795+ pandoc --print-default-data-file sample.lua

2796+

2797+Authors

2798+=======

2799+

2800+© 2006-2013 John MacFarlane (jgm at berkeley dot edu). Released under the

2801+[GPL], version 2 or greater. This software carries no warranty of

2802+any kind. (See COPYRIGHT for full copyright and warranty notices.)

2803+Other contributors include Recai Oktaş, Paulo Tanimoto, Peter Wang,

2804+Andrea Rossato, Eric Kow, infinity0x, Luke Plant, shreevatsa.public,

2805+Puneeth Chaganti, Paul Rivier, rodja.trappe, Bradley Kuhn, thsutton,

2806+Nathan Gass, Jonathan Daugherty, Jérémy Bobbio, Justin Bogner, qerub,

2807+Christopher Sawicki, Kelsey Hightower, Masayoshi Takahashi, Antoine

2808+Latter, Ralf Stephan, Eric Seidel, B. Scott Michel, Gavin Beatty,

2809+Sergey Astanin, Arlo O'Keeffe, Denis Laxalde, Brent Yorgey, David Lazar,

2810+Jamie F. Olson.

2811+

2812+[markdown]: http://daringfireball.net/projects/markdown/

2813+[reStructuredText]: http://docutils.sourceforge.net/docs/ref/rst/introduction.html

2814+[S5]: http://meyerweb.com/eric/tools/s5/

2815+[Slidy]: http://www.w3.org/Talks/Tools/Slidy/

2816+[Slideous]: http://goessner.net/articles/slideous/

2817+[HTML]: http://www.w3.org/TR/html40/

2818+[HTML 5]: http://www.w3.org/TR/html5/

2819+[XHTML]: http://www.w3.org/TR/xhtml1/

2820+[LaTeX]: http://www.latex-project.org/

2821+[beamer]: http://www.tex.ac.uk/CTAN/macros/latex/contrib/beamer

2822+[ConTeXt]: http://www.pragma-ade.nl/

2823+[RTF]: http://en.wikipedia.org/wiki/Rich_Text_Format

2824+[DocBook]: http://www.docbook.org/

2825+[OPML]: http://dev.opml.org/spec2.html

2826+[OpenDocument]: http://opendocument.xml.org/

2827+[ODT]: http://en.wikipedia.org/wiki/OpenDocument

2828+[Textile]: http://redcloth.org/textile

2829+[MediaWiki markup]: http://www.mediawiki.org/wiki/Help:Formatting

2830+[Haddock markup]: http://www.haskell.org/haddock/doc/html/ch03s08.html

2831+[groff man]: http://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man7/groff_man.7.html

2832+[Haskell]: http://www.haskell.org/

2833+[GNU Texinfo]: http://www.gnu.org/software/texinfo/

2834+[Emacs Org-Mode]: http://orgmode.org

2835+[AsciiDoc]: http://www.methods.co.nz/asciidoc/

2836+[EPUB]: http://www.idpf.org/

2837+[GPL]: http://www.gnu.org/copyleft/gpl.html "GNU General Public License"

2838+[DZSlides]: http://paulrouget.com/dzslides/

2839+[ISO 8601 format]: http://www.w3.org/TR/NOTE-datetime

2840+[Word docx]: http://www.microsoft.com/interop/openup/openxml/default.aspx

2841+[PDF]: http://www.adobe.com/pdf/

2842+[reveal.js]: http://lab.hakim.se/reveal-js/

2843+[FictionBook2]: http://www.fictionbook.org/index.php/Eng:XML_Schema_Fictionbook_2.1

2844+[lua]: http://www.lua.org

2845+

README.mddeleted−244

@@ -1,244 +0,0 @@

1−<!-- Do not edit this file. It is generated automatically from

2−README.template and MANUAL.txt via the command:

3−pandoc --lua-filter tools/update-readme.lua README.template -o README.md

4−-->

5−

6−# Pandoc

7−

8−[![github

9−release](https://img.shields.io/github/release/jgm/pandoc.svg?label=current+release)](https://github.com/jgm/pandoc/releases)

10−[![hackage

11−release](https://img.shields.io/hackage/v/pandoc.svg?label=hackage)](https://hackage.haskell.org/package/pandoc)

12−[](https://formulae.brew.sh/formula/pandoc)

13−[![stackage LTS

14−package](https://stackage.org/package/pandoc/badge/lts)](https://www.stackage.org/lts/package/pandoc-types)

15−[![CI

16−tests](https://github.com/jgm/pandoc/workflows/CI%20tests/badge.svg)](https://github.com/jgm/pandoc/actions)

17−[](https://www.gnu.org/licenses/gpl.html)

18−[![pandoc-discuss on google

19−groups](https://img.shields.io/badge/pandoc-discuss-red.svg?style=social)](https://groups.google.com/forum/#!forum/pandoc-discuss)

20−

21−## The universal markup converter

22−

23−Pandoc is a [Haskell](https://haskell.org) library for converting from

24−one markup format to another, and a command-line tool that uses this

25−library. It can convert *from*

26−

27−<div id="input-formats">

28−

29−- `bibtex` ([BibTeX](https://ctan.org/pkg/bibtex) bibliography)

30−- `biblatex` ([BibLaTeX](https://ctan.org/pkg/biblatex) bibliography)

31−- `commonmark` ([CommonMark](https://commonmark.org) Markdown)

32−- `commonmark_x` ([CommonMark](https://commonmark.org) Markdown with

33− extensions)

34−- `creole` ([Creole 1.0](http://www.wikicreole.org/wiki/Creole1.0))

35−- `csljson` ([CSL

36− JSON](https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html)

37− bibliography)

38−- `csv` ([CSV](https://tools.ietf.org/html/rfc4180) table)

39−- `docbook` ([DocBook](https://docbook.org))

40−- `docx` ([Word docx](https://en.wikipedia.org/wiki/Office_Open_XML))

41−- `dokuwiki` ([DokuWiki markup](https://www.dokuwiki.org/dokuwiki))

42−- `epub` ([EPUB](http://idpf.org/epub))

43−- `fb2`

44− ([FictionBook2](http://www.fictionbook.org/index.php/Eng:XML_Schema_Fictionbook_2.1)

45− e-book)

46−- `gfm` ([GitHub-Flavored

47− Markdown](https://help.github.com/articles/github-flavored-markdown/)),

48− or the deprecated and less accurate `markdown_github`; use

49− [`markdown_github`](https://pandoc.org/MANUAL.html#markdown-variants)

50− only if you need extensions not supported in

51− [`gfm`](https://pandoc.org/MANUAL.html#markdown-variants).

52−- `haddock` ([Haddock

53− markup](https://www.haskell.org/haddock/doc/html/ch03s08.html))

54−- `html` ([HTML](https://www.w3.org/html/))

55−- `ipynb` ([Jupyter

56− notebook](https://nbformat.readthedocs.io/en/latest/))

57−- `jats` ([JATS](https://jats.nlm.nih.gov) XML)

58−- `jira`

59− ([Jira](https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all)/Confluence

60− wiki markup)

61−- `json` (JSON version of native AST)

62−- `latex` ([LaTeX](https://www.latex-project.org/))

63−- `markdown` ([Pandoc’s

64− Markdown](https://pandoc.org/MANUAL.html#pandocs-markdown))

65−- `markdown_mmd`

66− ([MultiMarkdown](https://fletcherpenney.net/multimarkdown/))

67−- `markdown_phpextra` ([PHP Markdown

68− Extra](https://michelf.ca/projects/php-markdown/extra/))

69−- `markdown_strict` (original unextended

70− [Markdown](https://daringfireball.net/projects/markdown/))

71−- `mediawiki` ([MediaWiki

72− markup](https://www.mediawiki.org/wiki/Help:Formatting))

73−- `man` ([roff man](https://man.cx/groff_man(7)))

74−- `muse` ([Muse](https://amusewiki.org/library/manual))

75−- `native` (native Haskell)

76−- `odt` ([ODT](https://en.wikipedia.org/wiki/OpenDocument))

77−- `opml` ([OPML](http://dev.opml.org/spec2.html))

78−- `org` ([Emacs Org mode](https://orgmode.org))

79−- `rst`

80− ([reStructuredText](https://docutils.sourceforge.io/docs/ref/rst/introduction.html))

81−- `t2t` ([txt2tags](https://txt2tags.org))

82−- `textile` ([Textile](https://www.promptworks.com/textile))

83−- `tikiwiki` ([TikiWiki

84− markup](https://doc.tiki.org/Wiki-Syntax-Text#The_Markup_Language_Wiki-Syntax))

85−- `twiki` ([TWiki

86− markup](https://twiki.org/cgi-bin/view/TWiki/TextFormattingRules))

87−- `vimwiki` ([Vimwiki](https://vimwiki.github.io))

88−

89−</div>

90−

91−It can convert *to*

92−

93−<div id="output-formats">

94−

95−- `asciidoc` ([AsciiDoc](https://www.methods.co.nz/asciidoc/)) or

96− `asciidoctor` ([AsciiDoctor](https://asciidoctor.org/))

97−- `beamer` ([LaTeX beamer](https://ctan.org/pkg/beamer) slide show)

98−- `bibtex` ([BibTeX](https://ctan.org/pkg/bibtex) bibliography)

99−- `biblatex` ([BibLaTeX](https://ctan.org/pkg/biblatex) bibliography)

100−- `commonmark` ([CommonMark](https://commonmark.org) Markdown)

101−- `commonmark_x` ([CommonMark](https://commonmark.org) Markdown with

102− extensions)

103−- `context` ([ConTeXt](https://www.contextgarden.net/))

104−- `csljson` ([CSL

105− JSON](https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html)

106− bibliography)

107−- `docbook` or `docbook4` ([DocBook](https://docbook.org) 4)

108−- `docbook5` (DocBook 5)

109−- `docx` ([Word docx](https://en.wikipedia.org/wiki/Office_Open_XML))

110−- `dokuwiki` ([DokuWiki markup](https://www.dokuwiki.org/dokuwiki))

111−- `epub` or `epub3` ([EPUB](http://idpf.org/epub) v3 book)

112−- `epub2` (EPUB v2)

113−- `fb2`

114− ([FictionBook2](http://www.fictionbook.org/index.php/Eng:XML_Schema_Fictionbook_2.1)

115− e-book)

116−- `gfm` ([GitHub-Flavored

117− Markdown](https://help.github.com/articles/github-flavored-markdown/)),

118− or the deprecated and less accurate `markdown_github`; use

119− [`markdown_github`](https://pandoc.org/MANUAL.html#markdown-variants)

120− only if you need extensions not supported in

121− [`gfm`](https://pandoc.org/MANUAL.html#markdown-variants).

122−- `haddock` ([Haddock

123− markup](https://www.haskell.org/haddock/doc/html/ch03s08.html))

124−- `html` or `html5` ([HTML](https://www.w3.org/html/),

125− i.e. [HTML5](https://html.spec.whatwg.org/)/XHTML [polyglot

126− markup](https://www.w3.org/TR/html-polyglot/))

127−- `html4` ([XHTML](https://www.w3.org/TR/xhtml1/) 1.0 Transitional)

128−- `icml` ([InDesign

129− ICML](https://wwwimages.adobe.com/www.adobe.com/content/dam/acom/en/devnet/indesign/sdk/cs6/idml/idml-cookbook.pdf))

130−- `ipynb` ([Jupyter

131− notebook](https://nbformat.readthedocs.io/en/latest/))

132−- `jats_archiving` ([JATS](https://jats.nlm.nih.gov) XML, Archiving

133− and Interchange Tag Set)

134−- `jats_articleauthoring` ([JATS](https://jats.nlm.nih.gov) XML,

135− Article Authoring Tag Set)

136−- `jats_publishing` ([JATS](https://jats.nlm.nih.gov) XML, Journal

137− Publishing Tag Set)

138−- `jats` (alias for `jats_archiving`)

139−- `jira`

140− ([Jira](https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all)/Confluence

141− wiki markup)

142−- `json` (JSON version of native AST)

143−- `latex` ([LaTeX](https://www.latex-project.org/))

144−- `man` ([roff man](https://man.cx/groff_man(7)))

145−- `markdown` ([Pandoc’s

146− Markdown](https://pandoc.org/MANUAL.html#pandocs-markdown))

147−- `markdown_mmd`

148− ([MultiMarkdown](https://fletcherpenney.net/multimarkdown/))

149−- `markdown_phpextra` ([PHP Markdown

150− Extra](https://michelf.ca/projects/php-markdown/extra/))

151−- `markdown_strict` (original unextended

152− [Markdown](https://daringfireball.net/projects/markdown/))

153−- `mediawiki` ([MediaWiki

154− markup](https://www.mediawiki.org/wiki/Help:Formatting))

155−- `ms` ([roff ms](https://man.cx/groff_ms(7)))

156−- `muse` ([Muse](https://amusewiki.org/library/manual)),

157−- `native` (native Haskell),

158−- `odt` ([OpenOffice text

159− document](https://en.wikipedia.org/wiki/OpenDocument))

160−- `opml` ([OPML](http://dev.opml.org/spec2.html))

161−- `opendocument` ([OpenDocument](http://opendocument.xml.org))

162−- `org` ([Emacs Org mode](https://orgmode.org))

163−- `pdf` ([PDF](https://www.adobe.com/pdf/))

164−- `plain` (plain text),

165−- `pptx`

166− ([PowerPoint](https://en.wikipedia.org/wiki/Microsoft_PowerPoint)

167− slide show)

168−- `rst`

169− ([reStructuredText](https://docutils.sourceforge.io/docs/ref/rst/introduction.html))

170−- `rtf` ([Rich Text

171− Format](https://en.wikipedia.org/wiki/Rich_Text_Format))

172−- `texinfo` ([GNU Texinfo](https://www.gnu.org/software/texinfo/))

173−- `textile` ([Textile](https://www.promptworks.com/textile))

174−- `slideous` ([Slideous](https://goessner.net/articles/slideous/) HTML

175− and JavaScript slide show)

176−- `slidy` ([Slidy](https://www.w3.org/Talks/Tools/Slidy2/) HTML and

177− JavaScript slide show)

178−- `dzslides` ([DZSlides](https://paulrouget.com/dzslides/) HTML5 +

179− JavaScript slide show),

180−- `revealjs` ([reveal.js](https://revealjs.com/) HTML5 + JavaScript

181− slide show)

182−- `s5` ([S5](https://meyerweb.com/eric/tools/s5/) HTML and JavaScript

183− slide show)

184−- `tei` ([TEI Simple](https://github.com/TEIC/TEI-Simple))

185−- `xwiki` ([XWiki

186− markup](https://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/Features/XWikiSyntax/))

187−- `zimwiki` ([ZimWiki

188− markup](https://zim-wiki.org/manual/Help/Wiki_Syntax.html))

189−- the path of a custom Lua writer, see [Custom

190− writers](https://pandoc.org/MANUAL.html#custom-writers) below

191−

192−</div>

193−

194−Pandoc can also produce PDF output via LaTeX, Groff ms, or HTML.

195−

196−Pandoc’s enhanced version of Markdown includes syntax for tables,

197−definition lists, metadata blocks, footnotes, citations, math, and much

198−more. See the User’s Manual below under [Pandoc’s

199−Markdown](https://pandoc.org/MANUAL.html#pandocs-markdown).

200−

201−Pandoc has a modular design: it consists of a set of readers, which

202−parse text in a given format and produce a native representation of the

203−document (an *abstract syntax tree* or AST), and a set of writers, which

204−convert this native representation into a target format. Thus, adding an

205−input or output format requires only adding a reader or writer. Users

206−can also run custom pandoc filters to modify the intermediate AST (see

207−the documentation for [filters](https://pandoc.org/filters.html) and

208−[Lua filters](https://pandoc.org/lua-filters.html)).

209−

210−Because pandoc’s intermediate representation of a document is less

211−expressive than many of the formats it converts between, one should not

212−expect perfect conversions between every format and every other. Pandoc

213−attempts to preserve the structural elements of a document, but not

214−formatting details such as margin size. And some document elements, such

215−as complex tables, may not fit into pandoc’s simple document model.

216−While conversions from pandoc’s Markdown to all formats aspire to be

217−perfect, conversions from formats more expressive than pandoc’s Markdown

218−can be expected to be lossy.

219−

220−## Installing

221−

222−Here’s [how to install pandoc](INSTALL.md).

223−

224−## Documentation

225−

226−Pandoc’s website contains a full [User’s

227−Guide](https://pandoc.org/MANUAL.html). It is also available

228−[here](MANUAL.txt) as pandoc-flavored Markdown. The website also

229−contains some [examples of the use of

230−pandoc](https://pandoc.org/demos.html) and a limited [online

231−demo](https://pandoc.org/try).

232−

233−## Contributing

234−

235−Pull requests, bug reports, and feature requests are welcome. Please

236−make sure to read [the contributor guidelines](CONTRIBUTING.md) before

237−opening a new issue.

238−

239−## License

240−

241−© 2006-2021 John MacFarlane (jgm@berkeley.edu). Released under the

242−[GPL](https://www.gnu.org/licenses/old-licenses/gpl-2.0.html "GNU General Public License"),

243−version 2 or greater. This software carries no warranty of any kind.

244−(See COPYRIGHT for full copyright and warranty notices.)

README.templatedeleted−89

@@ -1,89 +0,0 @@

1−<!-- Do not edit this file. It is generated automatically from

2−README.template and MANUAL.txt via the command:

3−pandoc --lua-filter tools/update-readme.lua README.template -o README.md

4−-->

5−

6−Pandoc

7−======

8−

9−[](https://github.com/jgm/pandoc/releases)

10−[](https://hackage.haskell.org/package/pandoc)

11−[](https://formulae.brew.sh/formula/pandoc)

12−[](https://www.stackage.org/lts/package/pandoc-types)

13−[](https://github.com/jgm/pandoc/actions)

14−[](https://www.gnu.org/licenses/gpl.html)

15−[](https://groups.google.com/forum/#!forum/pandoc-discuss)

16−

17−

18−The universal markup converter

19−------------------------------

20−

21−Pandoc is a [Haskell] library for converting from one markup format to

22−another, and a command-line tool that uses this library. It can convert *from*

23−

24−::: {#input-formats}

25−:::

26−

27−It can convert *to*

28−

29−::: {#output-formats}

30−:::

31−

32−Pandoc can also produce PDF output via LaTeX, Groff ms, or HTML.

33−

34−Pandoc's enhanced version of Markdown includes syntax for tables,

35−definition lists, metadata blocks, footnotes, citations, math,

36−and much more. See the User's Manual below under

37−[Pandoc's Markdown](https://pandoc.org/MANUAL.html#pandocs-markdown).

38−

39−Pandoc has a modular design: it consists of a set of readers, which parse

40−text in a given format and produce a native representation of the document

41−(an _abstract syntax tree_ or AST), and a set of writers, which convert

42−this native representation into a target format. Thus, adding an input

43−or output format requires only adding a reader or writer. Users can also

44−run custom pandoc filters to modify the intermediate AST (see

45−the documentation for [filters](https://pandoc.org/filters.html)

46−and [Lua filters](https://pandoc.org/lua-filters.html)).

47−

48−Because pandoc's intermediate representation of a document is less

49−expressive than many of the formats it converts between, one should

50−not expect perfect conversions between every format and every other.

51−Pandoc attempts to preserve the structural elements of a document, but

52−not formatting details such as margin size. And some document elements,

53−such as complex tables, may not fit into pandoc's simple document

54−model. While conversions from pandoc's Markdown to all formats aspire

55−to be perfect, conversions from formats more expressive than pandoc's

56−Markdown can be expected to be lossy.

57−

58−

59−Installing

60−----------

61−

62−Here's [how to install pandoc](INSTALL.md).

63−

64−Documentation

65−-------------

66−

67−Pandoc's website contains a full [User's Guide](https://pandoc.org/MANUAL.html).

68−It is also available [here](MANUAL.txt) as pandoc-flavored Markdown.

69−The website also contains some [examples of the use of

70−pandoc](https://pandoc.org/demos.html) and a limited [online

71−demo](https://pandoc.org/try).

72−

73−Contributing

74−------------

75−

76−Pull requests, bug reports, and feature requests are welcome. Please make

77−sure to read [the contributor guidelines](CONTRIBUTING.md) before opening a

78−new issue.

79−

80−

81−License

82−-------

83−

84−© 2006-2021 John MacFarlane (jgm@berkeley.edu). Released under the

85−[GPL], version 2 or greater. This software carries no warranty of

86−any kind. (See COPYRIGHT for full copyright and warranty notices.)

87−

88−[GPL]: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html "GNU General Public License"

89−[Haskell]: https://haskell.org

RELEASE-CHECKLIST+31−20

@@ -1,21 +1,32 @@

1−[ ] use 'policeman' to check API changes and version update

2−[ ] make README.md and commit if needed

3−[ ] make man/pandoc.1 and commit if needed

4−[ ] Finalize changelog

5−[ ] push release candidate branch rc/VERSION and (if it builds

6− successfully) download artifacts

7−[ ] run tools/build-arm.sh to create and download arm64 linux package

8−[ ] download macos artifacts from CircleCI

9−[ ] Use 'make' in macos and windows artifacts to sign code

10−[ ] make update-website

11−[ ] make trypandoc

12−[ ] Tag release in git

13−[ ] make pandoc-templates

14− cd ../pandoc-templates

15− git tag REL

16− git push

17− git push --tags

18−[ ] Add release on github (use 'make changes_github' and upload files)

19−[ ] stack upload .

20−[ ] Announce on pandoc-announce, pandoc-discuss

1+_ Test, on linux, windows, mac (inc. website demos)

2+

3+_ Finalize changelog

4+

5+_ Tag release in git

6+

7+_ Tag templates

8+

9+_ 'make sdist' to generate tarball

10+

11+_ Generate Windows package and copy to directory.

12+

13+_ Generate Mac OSX package.

14+

15+_ Upload to Google Code (googlecode-upload.sh)

16+

17+_ Go to Google code and deprecate the old versions

18+

19+- Add release on github

20+

21+_ Upload to HackageDB

22+

23+_ Update website, including short description of changes

24+

25+_ Announce on pandoc-announce, pandoc-discuss

26+

27+_ recompile trypandoc

28+

29+_ recompile pandoc-dingus

30+

31+_ recompile gitit

2132

SECURITY.mddeleted−12

@@ -1,12 +0,0 @@

1−# Security Policy

2−

3−## Supported Versions

4−

5−Only the most recent version of pandoc is supported with security updates.

6−

7−## Reporting a Vulnerability

8−

9−To report a vulnerability, email the maintainer, jgm@berkeley.edu.

10−But first please read the section of the manual entitled

11−[A note on security](https://pandoc.org/MANUAL.html#a-note-on-security),

12−which describes some security guarantees pandoc does NOT make.

Setup.hs+70−1

@@ -1,2 +1,71 @@

1+{-# LANGUAGE CPP #-}

2+

13import Distribution.Simple

2−main = defaultMain

4+import Distribution.Simple.PreProcess

5+import Distribution.Simple.Setup

6+ (copyDest, copyVerbosity, fromFlag, installVerbosity, BuildFlags(..))

7+import Distribution.PackageDescription (PackageDescription(..), Executable(..))

8+import Distribution.Simple.LocalBuildInfo

9+ (LocalBuildInfo(..), absoluteInstallDirs)

10+import Distribution.Verbosity ( Verbosity, silent )

11+import Distribution.Simple.InstallDirs (mandir, CopyDest (NoCopyDest))

12+import Distribution.Simple.Utils (installOrdinaryFiles, info)

13+import Prelude hiding (catch)

14+import System.Process ( rawSystem )

15+import System.FilePath ( (</>) )

16+import System.Directory ( findExecutable )

17+import System.Exit

18+

19+main :: IO ()

20+main = do

21+ defaultMainWithHooks $ simpleUserHooks {

22+ postBuild = makeManPages

23+ , postCopy = \ _ flags pkg lbi ->

24+ installManpages pkg lbi (fromFlag $ copyVerbosity flags)

25+ (fromFlag $ copyDest flags)

26+ , postInst = \ _ flags pkg lbi ->

27+ installManpages pkg lbi (fromFlag $ installVerbosity flags) NoCopyDest

28+ , copyHook = \pkgdescr ->

29+ (copyHook simpleUserHooks) pkgdescr{ executables =

30+ [x | x <- executables pkgdescr, exeName x /= "make-pandoc-man-pages"] }

31+ , instHook = \pkgdescr ->

32+ (instHook simpleUserHooks) pkgdescr{ executables =

33+ [x | x <- executables pkgdescr, exeName x /= "make-pandoc-man-pages"] }

34+ , hookedPreProcessors = [ppBlobSuffixHandler]

35+ }

36+ exitWith ExitSuccess

37+

38+-- | Build man pages from markdown sources in man/

39+makeManPages :: Args -> BuildFlags -> PackageDescription -> LocalBuildInfo -> IO ()

40+makeManPages _ flags _ lbi = do

41+ let verbosity = fromFlag $ buildVerbosity flags

42+ let args = ["--verbose" | verbosity /= silent]

43+ rawSystem (buildDir lbi </> "make-pandoc-man-pages" </> "make-pandoc-man-pages")

44+ args >>= exitWith

45+

46+manpages :: [FilePath]

47+manpages = ["man1" </> "pandoc.1"

48+ ,"man5" </> "pandoc_markdown.5"]

49+

50+manDir :: FilePath

51+manDir = "man"

52+

53+installManpages :: PackageDescription -> LocalBuildInfo

54+ -> Verbosity -> CopyDest -> IO ()

55+installManpages pkg lbi verbosity copy =

56+ installOrdinaryFiles verbosity (mandir (absoluteInstallDirs pkg lbi copy))

57+ (zip (repeat manDir) manpages)

58+

59+ppBlobSuffixHandler :: PPSuffixHandler

60+ppBlobSuffixHandler = ("hsb", \_ _ ->

61+ PreProcessor {

62+ platformIndependent = True,

63+ runPreProcessor = mkSimplePreProcessor $ \infile outfile verbosity ->

64+ do info verbosity $ "Preprocessing " ++ infile ++ " to " ++ outfile

65+ hsb2hsPath <- findExecutable "hsb2hs"

66+ case hsb2hsPath of

67+ Just p -> rawSystem p [infile, infile, outfile]

68+ Nothing -> error "hsb2hs is needed to build this program: cabal install hsb2hs"

69+ return ()

70+

71+ })

app/pandoc.hsdeleted−20

@@ -1,20 +0,0 @@

1−{- |

2− Module : Main

3− Copyright : Copyright (C) 2006-2021 John MacFarlane

4− License : GNU GPL, version 2 or above

5−

6− Maintainer : John MacFarlane <jgm@berkeley@edu>

7− Stability : alpha

8− Portability : portable

9−

10−Parses command-line options and calls the appropriate readers and

11−writers.

12−-}

13−module Main where

14−import qualified Control.Exception as E

15−import Text.Pandoc.App (convertWithOpts, defaultOpts, options, parseOptions)

16−import Text.Pandoc.Error (handleError)

17−

18−main :: IO ()

19−main = E.catch (parseOptions options defaultOpts >>= convertWithOpts)

20− (handleError . Left)

benchmark/benchmark-pandoc.hs+32−96

@@ -1,103 +1,39 @@

1−{-# LANGUAGE OverloadedStrings #-}

2−{-

3−Copyright (C) 2012-2021 John MacFarlane <jgm@berkeley.edu>

4−

5−This program is free software; you can redistribute it and/or modify

6−it under the terms of the GNU General Public License as published by

7−the Free Software Foundation; either version 2 of the License, or

8−(at your option) any later version.

9−

10−This program is distributed in the hope that it will be useful,

11−but WITHOUT ANY WARRANTY; without even the implied warranty of

12−MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

13−GNU General Public License for more details.

14−

15−You should have received a copy of the GNU General Public License

16−along with this program; if not, write to the Free Software

17−Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

18−-}

191import Text.Pandoc

20−import Text.Pandoc.MIME

21−import Control.DeepSeq (force)

22−import Control.Monad.Except (throwError)

23−import qualified Text.Pandoc.UTF8 as UTF8

24−import qualified Data.ByteString as B

25−import qualified Data.Text as T

26−import Test.Tasty.Bench

27−-- import Gauge

28−import qualified Data.ByteString.Lazy as BL

29−import Data.Maybe (mapMaybe)

30−import Data.List (sortOn)

2+import Criterion.Main

3+import Criterion.Config

4+import System.Environment (getArgs)

5+import Data.Monoid

316

327readerBench :: Pandoc

33− -> T.Text

34− -> Maybe Benchmark

35−readerBench _ name

36− | name `elem` ["bibtex", "biblatex", "csljson"] = Nothing

37−readerBench doc name = either (const Nothing) Just $

38− runPure $ do

39− (rdr, rexts) <- getReader name

40− (wtr, wexts) <- getWriter name

41− case (rdr, wtr) of

42− (TextReader r, TextWriter w) -> do

43− inp <- w def{ writerWrapText = WrapAuto

44− , writerExtensions = wexts } doc

45− return $ bench (T.unpack name) $

46− nf (either (error . show) id . runPure . r def) inp

47− (ByteStringReader r, ByteStringWriter w) -> do

48− tmpl <- Just <$> compileDefaultTemplate name

49− inp <- w def{ writerWrapText = WrapAuto

50− , writerExtensions = wexts

51− , writerTemplate = tmpl } doc

52− return $ bench (T.unpack name) $

53− nf (either (error . show) id .

54− runPure . r def{readerExtensions = rexts}) inp

55− _ -> throwError $ PandocSomeError $ "text/bytestring format mismatch: "

56− <> name

8+ -> (String, ReaderOptions -> String -> IO Pandoc)

9+ -> Benchmark

10+readerBench doc (name, reader) =

11+ let writer = case lookup name writers of

12+ Just (PureStringWriter w) -> w

13+ _ -> error $ "Could not find writer for " ++ name

14+ inp = writer def{ writerWrapText = True } doc

15+ -- we compute the length to force full evaluation

16+ getLength (Pandoc (Meta _) d) = length d

17+ in bench (name ++ " reader") $ whnfIO $ getLength `fmap`

18+ (reader def{ readerSmart = True }) inp

5719

58−getImages :: IO [(FilePath, MimeType, BL.ByteString)]

59−getImages = do

60− ll <- B.readFile "test/lalune.jpg"

61− mv <- B.readFile "test/movie.jpg"

62− return [("lalune.jpg", "image/jpg", BL.fromStrict ll)

63− ,("movie.jpg", "image/jpg", BL.fromStrict mv)]

64−

65−writerBench :: [(FilePath, MimeType, BL.ByteString)]

66− -> Pandoc

67− -> T.Text

68− -> Maybe Benchmark

69−writerBench _ _ name

70− | name `elem` ["bibtex", "biblatex", "csljson"] = Nothing

71−writerBench imgs doc name = either (const Nothing) Just $

72− runPure $ do

73− (wtr, wexts) <- getWriter name

74− case wtr of

75− TextWriter writerFun ->

76− return $ bench (T.unpack name)

77− $ nf (\d -> either (error . show) id $

78− runPure $ do

79− mapM_ (\(fp,mt,bs) -> insertMedia fp (Just mt) bs) imgs

80− writerFun def{ writerExtensions = wexts} d)

81− doc

82− ByteStringWriter writerFun ->

83− return $ bench (T.unpack name)

84− $ nf (\d -> either (error . show) id $

85− runPure $ do

86− mapM_ (\(fp,mt,bs) -> insertMedia fp (Just mt) bs) imgs

87− writerFun def{ writerExtensions = wexts} d)

88− doc

20+writerBench :: Pandoc

21+ -> (String, WriterOptions -> Pandoc -> String)

22+ -> Benchmark

23+writerBench doc (name, writer) = bench (name ++ " writer") $ nf

24+ (writer def{ writerWrapText = True }) doc

8925

9026main :: IO ()

9127main = do

92− inp <- UTF8.toText <$> B.readFile "test/testsuite.txt"

93− let opts = def

94− let doc = either (error . show) force $ runPure $ readMarkdown opts inp

95− defaultMain

96− [ env getImages $ \imgs ->

97− bgroup "writers" $ mapMaybe (writerBench imgs doc . fst)

98− (sortOn fst

99− writers :: [(T.Text, Writer PandocPure)])

100− , bgroup "readers" $ mapMaybe (readerBench doc . fst)

101− (sortOn fst

102− readers :: [(T.Text, Reader PandocPure)])

103− ]

28+ args <- getArgs

29+ (conf,_) <- parseArgs defaultConfig{ cfgSamples = Last $ Just 20 } defaultOptions args

30+ inp <- readFile "README"

31+ inp2 <- readFile "tests/testsuite.txt"

32+ let opts = def{ readerSmart = True }

33+ let doc = readMarkdown opts $ inp ++ unlines (drop 3 $ lines inp2)

34+ let readerBs = map (readerBench doc)

35+ $ filter (\(n,_) -> n /="haddock") readers

36+ let writers' = [(n,w) | (n, PureStringWriter w) <- writers]

37+ defaultMainWith conf (return ()) $

38+ map (writerBench doc) writers' ++ readerBs

39+

cabal.projectdeleted−13

@@ -1,13 +0,0 @@

1−packages: pandoc.cabal

2−tests: True

3−flags: +embed_data_files

4−

5−source-repository-package

6− type: git

7− location: https://github.com/jgm/doctemplates

8− tag: 428c26d5303cf7a2b1051fe1ffd9aafe9ba71c81

9−

10−source-repository-package

11− type: git

12− location: https://github.com/jgm/citeproc

13− tag: 4ce0501cd6f9c86eee087afcf878c256e49b9615

changelognew file+5952

@@ -0,0 +1,5952 @@

1+pandoc (1.12.0.2)

2+

3+ * Removed `stringable` dependency.

4+

5+pandoc (1.12.0.1)

6+

7+ * Allow `--metadata` to be repeated for the same key to form a list.

8+ This also has the effect that `--bibliography` can be repeated,

9+ as before.

10+

11+ * Handle boolean values in `--metadata`. Note that anything not parseable

12+ as a YAML boolean or string is treated as a literal string.

13+ You can get a string value with "yes", or any of the strings interpretable

14+ as booleans, by quoting it:

15+

16+ -M boolvalue=yes -M stringvalue='"yes"'

17+

18+ * LaTeX writer: Don't print references if `--natbib` or `--biblatex`

19+ option used.

20+

21+ * DOCX writer: Add `settings.xml` to the zip container. Fixes a bug

22+ in which docx files could not be read by some versions of Word

23+ and LibreOffice (#990).

24+

25+ * Fixed a regression involving slide shows with bibliographies.

26+ The Div container around references messed up the procedure for carving

27+ a document into slides. So we now remove the surrounding Div in

28+ `prepSlides`.

29+

30+ * More informative error message when a filter is not found in path.

31+

32+ * Depend on pandoc-types 1.12.1. This provide `ToJSONFilter`

33+ instances for `Data a => a -> [a]` and `Data a => a -> IO [a]`.

34+

35+ * Don't use unicode_collation in building OSX package:

36+ it adds something like 50MB of dependencies to the package.

37+

38+ * Declare alex and happy as build-tools (#986).

39+

40+pandoc (1.12)

41+

42+ [new features]

43+

44+ * Much more flexible metadata, including arbitrary fields and structured

45+ values. Metadata can be specified flexibly in pandoc markdown using

46+ YAML metadata blocks, which may occur anywhere in the document:

47+

48+ ---

49+ title: Here is my title.

50+ abstract: |

51+ This is the abstract.

52+

53+ 1. It can contain

54+ 2. block content

55+ and *inline markup*

56+

57+ tags: [cat, dog, animal]

58+ ...

59+

60+ Metadata fields automatically populate template variables.

61+

62+ * Added `opml` (OPML) as input and output format. The `_note` attribute,

63+ used in OmniOutliner and supported by multimarkdown, is supported.

64+ We treat the contents as markdown blocks under a section header.

65+

66+ * Added `haddock` (Haddock markup) as input format (David Lazar).

67+

68+ * Added `revealjs` output format, for reveal.js HTML 5 slide shows.

69+ (Thanks to Jamie F. Olson for the initial patch.)

70+ Nested vertical stacks are used for hierarchical structure.

71+ Results for more than one level of nesting may be odd.

72+

73+ * Custom writers can now be written in lua.

74+

75+ pandoc -t data/sample.lua

76+

77+ will load the script sample.lua and use it as a custom writer.

78+ (For a sample, do `pandoc --print-default-data-file sample.lua`.)

79+ Note that pandoc embeds a lua interpreter, so lua need not be

80+ installed separately.

81+

82+ * New `--filter/-F` option to make it easier to run "filters"

83+ (Pandoc AST transformations that operate on JSON serializations).

84+ Filters are always passed the name of the output format, so their

85+ behavior can be tailored to it. The repository

86+ <https://github.com/jgm/pandocfilters> contains

87+ a python module for writing pandoc filters in python, with

88+ a number of examples.

89+

90+ * Added `--metadata/-M` option.

91+ This is like `--variable/-V`, but actually adds to metadata, not

92+ just variables.

93+

94+ * Added `--print-default-data-file` option, which allows printing

95+ of any of pandoc's data files. (For example,

96+ `pandoc --print-default-data-file reference.odt` will print

97+ `reference.odt`.)

98+

99+ * Added syntax for "pauses" in slide shows:

100+

101+ This gives

102+

103+ . . .

104+

105+ me pause.

106+

107+ * New markdown extensions:

108+

109+ + `ignore_line_breaks`: causes intra-paragraph line breaks to be ignored,

110+ rather than being treated as hard line breaks or spaces. This is useful

111+ for some East Asian languages, where spaces aren't used between words,

112+ but text is separated into lines for readability.

113+ + `yaml_metadata_block`: Parse YAML metadata blocks. (Default.)

114+ + `ascii_identifiers`: This will force `auto_identifiers` to use ASCII

115+ only. (Default for `markdown_github`.) (#807)

116+ + `lists_without_preceding_blankline`: Allow lists to start without

117+ preceding blank space. (Default for `markdown_github`.) (#972)

118+

119+ [behavior changes]

120+

121+ * `--toc-level` no longer implies `--toc`.

122+ Reason: EPUB users who don't want a visible TOC may still want

123+ to set the TOC level for in the book navigation.

124+

125+ * `--help` now prints in and out formats in alphabetical order, and

126+ says something about PDF output (#720).

127+

128+ * `--self-contained` now returns less verbose output (telling you

129+ which URLs it is fetching, but not giving the full header). In

130+ addition, there are better error messages when fetching a URL fails.

131+

132+ * Citation support is no longer baked in to core pandoc. Users who

133+ need citations will need to install and use a separate filter

134+ (`--filter pandoc-citeproc`). This filter will take `bibliography`,

135+ `csl`, and `citation-abbreviations` from the metadata, though it

136+ may still be specified on the command line as before.

137+

138+ * A `Cite` element is now created in parsing markdown whether or not

139+ there is a matching reference.

140+

141+ * The `pandoc-citeproc` script will put the bibliography at the

142+ end of the document, as before. However, it will be put inside a `Div`

143+ element with class "references", allowing users some control

144+ over the styling of references. A final header, if any, will

145+ be included in the `Div`.

146+

147+ * The markdown writer will not print a bibliography if the

148+ `citations` extension is enabled. (If the citations are formatted

149+ as markdown citations, it is redundant to have a bibliography,

150+ since one will be generated automatically.)

151+

152+ * Previously we used to store the directory of the first input file,

153+ even if it was local, and used this as a base directory for finding

154+ images in ODT, EPUB, Docx, and PDF. This has been confusing to many

155+ users. So we now look for images relative to the current

156+ working directory, even if the first file argument is in another

157+ directory. Note that this change may break some existing workflows.

158+ If you have been assuming that relative links will be interpreted

159+ relative to the directory of the first file argument, you'll need

160+ to make that the current directory before running pandoc. (#942)

161+

162+ * Better error reporting in some readers, due to changes in `readWith`:

163+ the line in which the error occured is printed, with a caret pointing

164+ to the column.

165+

166+ * All slide formats now support incremental slide view for definition lists.

167+

168+ * Parse `\(..\)` and `\[..\]` as math in MediaWiki reader.

169+ Parse `:<math>...</math>` as display math. These notations are used with

170+ the MathJax MediaWiki extension.

171+

172+ * All writers: template variables are set automatically from metadata

173+ fields. However, variables specified on the command line with

174+ `--variable` will completely shadow metadata fields.

175+

176+ * If `--variable` is used to set many variables with the same name,

177+ a list is created.

178+

179+ * Man writer: The `title`, `section`, `header`, and `footer` can now

180+ all be set individually in metadata. The `description` variable has been

181+ removed. Quotes have been added so that spaces are allowed in the

182+ title. If you have a title that begins

183+

184+ COMMAND(1) footer here | header here

185+

186+ pandoc will still parse it into a title, section, header, and

187+ footer. But you can also specify these elements explicitly (#885).

188+

189+ * Markdown reader

190+

191+ + Added support for YAML metadata blocks, which can come anywhere

192+ in the document (not just at the beginning). A document can contain

193+ multiple YAML metadata blocks.

194+ + HTML span and div tags are parsed as pandoc Span and Div elements.

195+

196+ * Markdown writer

197+

198+ + Allow simple tables to be printed as grid tables,

199+ if other table options are disabled. This means you can do

200+ `pandoc -t markdown-pipe_tables-simple_tables-multiline_tables`

201+ and all tables will render as grid tables.

202+ + Support YAML title block (render fields in alphabetical order

203+ to make output predictable).

204+

205+ [API changes]

206+

207+ * `Meta` in `Text.Pandoc.Definition` has been changed to allow

208+ structured metadata. (Note: existing code that pattern-matches

209+ on `Meta` will have to be revised.) Metadata can now contain

210+ indefinitely many fields, with content that can be a string,

211+ a Boolean, a list of `Inline` elements, a list of `Block`

212+ elements, or a map or list of these.

213+

214+ * A new generic block container (`Div`) has been added to `Block`,

215+ and a generic inline container (`Span`) has been added to `Inline`.

216+ These can take attributes. They will render in HTML, Textile,

217+ MediaWiki, Org, RST and and Markdown (with `markdown_in_html`

218+ extension) as HTML `<div>` and `<span>` elements; in other formats

219+ they will simply pass through their contents. But they can be

220+ targeted by scripts.

221+

222+ * `Format` is now a newtype, not an alias for String.

223+ Equality comparisons are case-insensitive.

224+

225+ * Added `Text.Pandoc.Walk`, which exports hand-written tree-walking

226+ functions that are much faster than the SYB functions from

227+ `Text.Pandoc.Generic`. These functions are now used where possible

228+ in pandoc's code. (`Tests.Walk` verifies that `walk` and `query`

229+ match the generic traversals `bottomUp` and `queryWith`.)

230+

231+ * Added `Text.Pandoc.JSON`, which provides `ToJSON` and `FromJSON`

232+ instances for the basic pandoc types. They use GHC generics and

233+ should be faster than the old JSON serialization using

234+ `Data.Aeson.Generic`.

235+

236+ * Added `Text.Pandoc.Process`, exporting `pipeProcess`.

237+ This is a souped-up version of `readProcessWithErrorcode` that

238+ uses lazy bytestrings instead of strings and allows setting

239+ environment variables. (Used in `Text.Pandoc.PDF`.)

240+

241+ * New module `Text.Pandoc.Readers.OPML`.

242+

243+ * New module `Text.Pandoc.Writers.OPML`.

244+

245+ * New module `Text.Pandoc.Readers.Haddock` (David Lazar).

246+ This is based on Haddock's own lexer/parser.

247+

248+ * New module `Text.Pandoc.Writers.Custom`.

249+

250+ * In `Text.Pandoc.Shared`, `openURL` and `fetchItem` now return an

251+ Either, for better error handling.

252+

253+ * Made `stringify` polymorphic in `Text.Pandoc.Shared`.

254+

255+ * Removed `stripTags` from `Text.Pandoc.XML`.

256+

257+ * `Text.Pandoc.Templates`:

258+

259+ + Simplified `Template` type to a newtype.

260+ + Removed `Empty`.

261+ + Changed type of `renderTemplate`: it now takes a JSON context

262+ and a compiled template.

263+ + Export `compileTemplate`.

264+ + Export `renderTemplate'` that takes a string instead of a compiled

265+ template.

266+ + Export `varListToJSON`.

267+

268+ * `Text.Pandoc.PDF` exports `makePDF` instead of `tex2pdf`.

269+

270+ * `Text.Pandoc`:

271+

272+ + Made `toJsonFilter` an alias for `toJSONFilter` from `Text.Pandoc.JSON`.

273+ + Removed `ToJsonFilter` typeclass. `ToJSONFilter` from

274+ `Text.Pandoc.JSON` should be used instead. (Compiling against

275+ pandoc-types instead of pandoc will also produce smaller executables.)

276+ * Removed the deprecated `jsonFilter` function.

277+ + Added `readJSON`, `writeJSON` to the API (#817).

278+

279+ * `Text.Pandoc.Options`:

280+

281+ + Added `Ext_lists_without_preceding_blankline`,

282+ `Ext_ascii_identifiers`, `Ext_ignore_line_breaks`,

283+ `Ext_yaml_metadataBlock` to `Extension`.

284+ + Changed `writerSourceDirectory` to `writerSourceURL` and changed the

285+ type to a `Maybe`. `writerSourceURL` is set to 'Just url' when the

286+ first command-line argument is an absolute URL. (So, relative links

287+ will be resolved in relation to the first page.) Otherwise, 'Nothing'.

288+ + All bibliography-related fields have been removed from

289+ `ReaderOptions` and `WriterOptions`: `writerBiblioFiles`,

290+ `readerReferences`, `readerCitationStyle`.

291+

292+ * The `Text.Pandoc.Biblio` module has been removed. Users of the

293+ pandoc library who want citation support will need to use

294+ `Text.CSL.Pandoc` from `pandoc-citeproc`.

295+

296+

297+ [bug fixes]

298+

299+ * In markdown, don't autolink a bare URI that is followed by `</a>`

300+ (#937).

301+

302+ * `Text.Pandoc.Shared`

303+

304+ + `openURL` now follows redirects (#701), properly handles `data:`

305+ URIs, and prints diagnostic output to stderr rather than stdout.

306+ + `readDefaultDataFile`: normalize the paths. This fixes bugs in

307+ `--self-contained` on pandoc compiled with `embed_data_files` (#833).

308+ + Fixed `readDefaultDataFile` so it works on Windows.

309+ + Better error messages for `readDefaultDataFile`. Instead of

310+ listing the last path tried, which can confuse people who are

311+ using `--self-contained`, so now we just list the data file name.

312+ + URL-escape pipe characters. Even though these are legal, `Network.URI`

313+ doesn't regard them as legal in URLs. So we escape them first (#535).

314+

315+ * Mathjax in HTML slide shows: include explicit "Typeset" call.

316+ This seems to be needed for some formats (e.g. slideous) and won't

317+ hurt in others (#966).

318+

319+ * `Text.Pandoc.PDF`

320+

321+ + On Windows, create temdir in working directory, since the system

322+ temp directory path may contain tildes, which can cause

323+ problems in LaTeX (#777).

324+ + Put temporary output directory in `TEXINPUTS` (see #917).

325+ + `makePDF` tries to download images that are not found locally,

326+ if the first argument is a URL (#917).

327+ + If compiling with `pdflatex` yields an encoding error, offer

328+ the suggestion to use `--latex-engine=xelatex`.

329+

330+ * Produce automatic header identifiers in parsing textile, RST,

331+ and LaTeX, unless `auto_identifiers` extension is disabled (#967).

332+

333+ * `Text.Pandoc.SelfContained`: Strip off fragment, query of relative URL

334+ before treating as a filename. This fixes `--self-contained` when used

335+ with CSS files that include web fonts using the method described here:

336+ <http://paulirish.com/2009/bulletproof-font-face-implementation-syntax/>

337+ (#739). Handle `src` in `embed`, `audio`, `source`, `input` tags.

338+

339+ * `Text.Pandoc.Parsing`: `uri` parser no longer treats punctuation before

340+ percent-encoding, or a `+` character, as final punctuation.

341+

342+ * `Text.Pandoc.ImageSize`: Handle EPS (#903). This change will make

343+ EPS images properly sized on conversion to Word.

344+

345+ * Slidy: Use slidy.js rather than slidy.js.gz.

346+ Reason: some browsers have trouble with the gzipped js file,

347+ at least on the local file system (#795).

348+

349+ * Markdown reader

350+

351+ + Properly handle blank line at beginning of input (#882).

352+ + Fixed bug in unmatched reference links. The input

353+ `[*infile*] [*outfile*]` was getting improperly parsed:

354+ "infile" was emphasized, but "*outfile*" was literal (#883).

355+ + Allow internal `+` in citation identifiers (#856).

356+ + Allow `.` or `)` after `#` in ATX headers if no `fancy_lists`.

357+ + Do not generate blank title, author, or date metadata elements.

358+ Leave these out entirely if they aren't present.

359+ + Allow backtick code blocks not to be preceded by blank line (#975).

360+

361+ * Textile reader:

362+

363+ + Correctly handle entities.

364+ + Improved handling of `<pre>` blocks (#927). Remove internal HTML tags

365+ in code blocks, rather than printing them verbatim. Parse attributes

366+ on `<pre>` tag for code blocks.

367+

368+ * HTML reader: Handle non-simple tables (#893). Column widths are read from

369+ `col` tags if present, otherwise divided equally.

370+

371+ * LaTeX reader

372+

373+ + Support alltt environment (#892).

374+ + Support `\textasciitilde`, `\textasciicircum` (#810).

375+ + Treat `\textsl` as emphasized text reader (#850).

376+ + Skip positional options after `\begin{figure}`.

377+ + Support `\v{}` for hacek (#926).

378+ + Don't add spurious ", " to citation suffixes.

379+ This is added when needed in pandoc-citeproc.

380+ + Allow spaces in alignment spec in tables, e.g. `{ l r c }`.

381+ + Improved support for accented characters (thanks to Scott Morrison).

382+ + Parse label after section command and set id (#951).

383+

384+ * RST reader:

385+

386+ + Don't insert paragraphs where docutils doesn't.

387+ `rst2html` doesn't add `<p>` tags to list items (even when they are

388+ separated by blank lines) unless there are multiple paragraphs in the

389+ list. This commit changes the RST reader to conform more closely to

390+ what docutils does (#880).

391+ + Improved metadata. Treat initial field list as metadata when

392+ standalone specified. Previously ALL fields "title", "author",

393+ "date" in field lists were treated as metadata, even if not at

394+ the beginning. Use `subtitle` metadata field for subtitle.

395+ + Fixed 'authors' metadata parsing in reST. Semicolons separate

396+ different authors.

397+

398+ * MediaWiki reader

399+

400+ + Allow space before table rows.

401+ + Fixed regression for `<ref>URL</ref>`.

402+ `<` is no longer allowed in URLs, according to the uri parser

403+ in `Text.Pandoc.Parsing`. Added a test case.

404+ + Correctly handle indented preformatted text without preceding

405+ or following blank line.

406+ + Fixed `|` links inside table cells. Improved attribute parsing.

407+ + Skip attributes on table rows. Previously we just crashed if

408+ rows had attributes, now we ignore them.

409+ + Ignore attributes on headers.

410+ + Allow `Image:` for images (#971).

411+ + Parse an image with caption in a paragraph by itself as a figure.

412+

413+ * LaTeX writer

414+

415+ + Don't use ligatures in escaping inline code.

416+ + Fixed footnote numbers in LaTeX/PDF tables. This fixes a bug

417+ wherein notes were numbered incorrectly in tables (#827).

418+ + Always create labels for sections. Previously the labels were only

419+ created when there were links to the section in the document (#871).

420+ + Stop escaping `|` in LaTeX math.

421+ This caused problems with array environments (#891).

422+ + Change `\` to `/` in paths. `/` works even on Windows in LaTeX.

423+ `\` will cause major problems if unescaped.

424+ + Write id for code block to label attribute in LaTeX when listings

425+ is used (thanks to Florian Eitel).

426+ + Scale LaTeX tables so they don't exceed columnwidth.

427+ + Avoid problem with footnotes in unnumbered headers (#940).

428+

429+ * Beamer writer: when creating beamer slides, add `allowframebreaks` option

430+ to the slide if it is one of the header classes. It is recommended

431+ that your bibliography slide have this attribute:

432+

433+ # References {.allowframebreaks}

434+

435+ This causes multiple slides to be created if necessary, depending

436+ on the length of the bibliography.

437+

438+ * ConTeXt writer: Properly handle tables without captions. The old output

439+ only worked in MkII. This should work in MkIV as well (#837).

440+

441+ * MediaWiki writer: Use native mediawiki tables instead of HTML (#720).

442+

443+ * HTML writer:

444+

445+ + Fixed `--no-highlight` (Alexander Kondratskiy).

446+ + Don't convert to lowercase in email obfuscation (#839).

447+ + Ensure proper escaping in `<title>` and `<meta>` fields.

448+

449+ * AsciiDoc writer:

450+

451+ + Support `--atx-headers` (Max Rydahl Andersen).

452+ + Don't print empty identifier blocks `([[]])` on headers (Max

453+ Rydahl Andersen).

454+

455+ * ODT writer:

456+

457+ + Fixing wrong numbered-list indentation in open document format

458+ (Alexander Kondratskiy) (#369).

459+ + `reference.odt`: Added pandoc as "generator" in `meta.xml`.

460+ + Minor changes for ODF 1.2 conformance (#939). We leave the

461+ nonconforming `contextual-spacing` attribute, which is provided by

462+ LibreOffice itself and seems well supported.

463+

464+ * Docx writer:

465+

466+ + Fixed rendering of display math in lists.

467+ In 1.11 and 1.11.1, display math in lists rendered as a new list

468+ item. Now it always appears centered, just as outside of lists,

469+ and in proper display math style, no matter how far indented the

470+ containing list item is (#784).

471+ + Use `w:br` with `w:type` `textWrapping` for linebreaks.

472+ Previously we used `w:cr` (#873).

473+ + Use Compact style for Plain block elements, to

474+ differentiate between tight and loose lists (#775).

475+ + Ignore most components of `reference.docx`.

476+ We take the `word/styles.xml`, `docProps/app.xml`,

477+ `word/theme/theme1.xml`, and `word/fontTable.xml` from

478+ `reference.docx`, ignoring everything else. This should help

479+ with the corruption problems caused when different versions of

480+ Word resave the reference.docx and reorganize things.

481+ + Made `--no-highlight` work properly.

482+

483+ * EPUB writer

484+

485+ + Don't add `dc:creator` tags if present in EPUB metadata.

486+ + Add `id="toc-title"` to `h1` in `nav.xhtml` (#799).

487+ + Don't put blank title page in reading sequence.

488+ Set `linear="no"` if no title block. Addresses #797.

489+ + Download webtex images and include as data URLs.

490+ This allows you to use `--webtex` in creating EPUBs.

491+ Math with `--webtex` is automatically made self-contained.

492+ + In `data/epub.css`, removed highlighting styles (which

493+ are no longer needed, since styles are added by the HTML

494+ writer according to `--highlighting-style`). Simplified

495+ margin fields.

496+ + If resource not found, skip it, as in Docx writer (#916).

497+

498+ * RTF writer:

499+

500+ + Properly handle characters above the 0000-FFFF range.

501+ Uses surrogate pairs. Thanks to Hiromi Ishii for the patch.

502+ + Fixed regression with RTF table of contents.

503+ + Only autolink absolute URIs. This fixes a regression, #830.

504+

505+ * Markdown writer:

506+

507+ + Only autolink absolute URIs. This fixes a regression, #830.

508+ + Don't wrap attributes in fenced code blocks.

509+ + Write full metadata in MMD style title blocks.

510+ + Put multiple authors on separate lines in pandoc titleblock.

511+ Also, don't wrap long author entries, as new lines get treated

512+ as new authors.

513+

514+ * `Text.Pandoc.Templates`:

515+

516+ + Fixed bug retrieving default template for markdown variants.

517+ + Templates can now contain "record lookups" in variables;

518+ for example, `author.institution` will retrieve the `institution`

519+ field of the `author` variable.

520+ + More consistent behavior of `$for$`. When `foo` is not a list,

521+ `$for(foo)$...$endfor$` should behave like $if(foo)$...$endif$.

522+ So if `foo` resolves to "", no output should be produced.

523+ See pandoc-templates#39.

524+

525+ * Citation processing improvements (now part of pandoc-citeproc):

526+

527+ + Fixed `endWithPunct` The new version correctly sees a sentence

528+ ending in '.)' as ending with punctuation. This fixes a bug which

529+ led such sentences to receive an extra period at the end: '.).'.

530+ Thanks to Steve Petersen for reporting.

531+ + Don't interfere with Notes that aren't citation notes.

532+ This fixes a bug in which notes not generated from citations were

533+ being altered (e.g. first letter capitalized) (#898).

534+ + Only capitalize footnote citations when they have a prefix.

535+ + Changes in suffix parsing. A suffix beginning with a digit gets 'p'

536+ inserted before it before passing to citeproc-hs, so that bare numbers

537+ are treated as page numbers by default. A suffix not beginning with

538+ punctuation has a space added at the beginning (rather than a comma and

539+ space, as was done before for not-author-in-text citations).

540+ The result is that `\citep[23]{item1}` in LaTeX will be interpreted

541+ properly, with '23' treated as a locator of type 'page'.

542+ + Many improvements to citation rendering, due to fixes in citeproc-hs

543+ (thanks to Andrea Rossato).

544+ + Warnings are issued for undefined citations, which are rendered

545+ as `???`.

546+ + Fixed hanging behavior when locale files cannot be found.

547+

548+ [template changes]

549+

550+ * DocBook: Use DocBook 4.5 doctype.

551+

552+ * Org: '#+TITLE:' is inserted before the title.

553+ Previously the writer did this.

554+

555+ * LaTeX: Changes to make mathfont work with xelatex.

556+ We need the mathspec library, not just fontspec, for this.

557+ We also need to set options for setmathfont (#734).

558+

559+ * LaTeX: Use `tex-ansi` mapping for `monofont`.

560+ This ensures that straight quotes appear as straight, rather than

561+ being treated as curly. See #889.

562+

563+ * Made `\includegraphics` more flexible in LaTeX template.

564+ Now it can be used with options, if needed. Thanks to Bernhard Weichel.

565+

566+ * LaTeX/Beamer: Added `classoption` variable.

567+ This is intended for class options like `oneside`; it may

568+ be repeated with different options. (Thanks to Oliver Matthews.)

569+

570+ * Beamer: Added `fonttheme` variable. (Thanks to Luis Osa.)

571+

572+ * LaTeX: Added `biblio-style` variable (#920).

573+

574+ * DZSlides: title attribute on title section.

575+

576+ * HTML5: add meta tag to allow scaling by user (Erik Evenson)

577+

578+ [under-the-hood improvements]

579+

580+ * Markdown reader:Improved strong/emph parsing, using the strategy of

581+ <https://github.com/jgm/Markdown>. The new parsing algorithm requires

582+ no backtracking, and no keeping track of nesting levels. It will give

583+ different results in some edge cases, but these should not affect normal

584+ uses.

585+

586+ * Added `Text.Pandoc.Compat.Monoid`.

587+ This allows pandoc to compile with `base` < 4.5, where `Data.Monoid`

588+ doesn't export `<>`. Thanks to Dirk Ullirch for the patch.

589+

590+ * Added `Text.Pandoc.Compat.TagSoupEntity`.

591+ This allows pandoc to compile with `tagsoup` 0.13.x.

592+ Thanks to Dirk Ullrich for the patch.

593+

594+ * Most of `Text.Pandoc.Readers.TeXMath` has been moved to the

595+ `texmath` module (0.6.4). (This allows `pandoc-citeproc` to

596+ handle simple math in bibliography fields.)

597+

598+ * Added `Text.Pandoc.Writers.Shared` for shared functions used

599+ only in writers. `metaToJSON` is used in writers to create a

600+ JSON object for use in the templates from the pandoc metadata

601+ and variables. `getField`, `setField`, and `defField` are

602+ for working with JSON template contexts.

603+

604+ * Added `Text.Pandoc.Asciify` utility module.

605+ This exports functions to create ASCII-only versions of identifiers.

606+

607+ * `Text.Pandoc.Parsing`

608+

609+ + Generalized state type on `readWith` (API change).

610+ + Specialize readWith to `String` input. (API change).

611+ + In `ParserState`, replace `stateTitle`, `stateAuthors`, `stateDate`

612+ with `stateMeta` and `stateMeta'`.

613+

614+ * `Text.Pandoc.UTF8`: use strict bytestrings in reading. The use of lazy

615+ bytestrings seemed to cause problems using pandoc on 64-bit Windows

616+ 7/8 (#874).

617+

618+ * Factored out `registerHeader` from markdown reader, added to

619+ `Text.Pandoc.Parsing`.

620+

621+ * Removed `blaze_html_0_5` flag, require `blaze-html` >= 0.5.

622+ Reason: < 0.5 does not provide a monoid instance for Attribute,

623+ which is now needed by the HTML writer (#803).

624+

625+ * Added `http-conduit` flag, which allows fetching https resources.

626+ It also brings in a large number of dependencies (`http-conduit`

627+ and its dependencies), which is why for now it is an optional flag

628+ (#820).

629+

630+ * Added CONTRIBUTING.md.

631+

632+ * Improved INSTALL instructions.

633+

634+ * `make-windows-installer.bat`: Removed explicit paths for executables.

635+

636+ * `aeson` is now used instead of `json` for JSON.

637+

638+ * Set default stack size to 16M. This is needed for some large

639+ conversions, esp. if pandoc is compiled with 64-bit ghc.

640+

641+ * Various small documentation improvements.

642+ Thanks to achalddave and drothlis for patches.

643+

644+ * Removed comment that chokes recent versions of CPP (#933).

645+

646+ * Removed support for GHC version < 7.2, since pandoc-types now

647+ requires at least GHC 7.2 for GHC generics.

648+

649+

650+pandoc (1.11.1)

651+

652+ * Markdown reader:

653+

654+ + Fixed regression in which parentheses were lost in link URLs.

655+ Added tests. Closes #786.

656+ + Better handling of unmatched double quotes in `--smart` mode.

657+ These occur frequently in fiction, since it is customary not to

658+ close quotes in dialogue if the speaker does not change between

659+ paragraphs. The unmatched quotes now get turned into literal

660+ left double quotes. (No `Quoted` inline is generated, however.)

661+ Closes #99 (again).

662+

663+ * HTML writer: Fixed numbering mismatch between TOC and sections.

664+ `--number-offset` now affects TOC numbering as well

665+ as section numbering, as it should have all along. Closes #789.

666+

667+ * Markdown writer: Reverted 1.11 change that caused citations to be rendered

668+ as markdown citations, even if `--bibliography` was specified, unless

669+ `citation` extension is disabled. Now, formatted citations are always

670+ printed if `--bibliography` was specified. If you want to reformat

671+ markdown keeping pandoc markdown citations intact, don't use

672+ `--bibliography`. Note that citations parsed from LaTeX documents will

673+ be rendered as pandoc markdown citations when `--bibliography` is not

674+ specified.

675+

676+ * ODT writer: Fixed regression leading to corrupt ODTs.

677+ This was due to a change in the `Show` instance for

678+ `Text.Pandoc.Pretty.Doc`. Closes #780.

679+

680+ * Fixed spacing bugs involving code block attributes in

681+ RST reader and Markdown writer. Closes #763.

682+

683+ * Windows package: Various improvements due to Fyodor Sheremetyev.

684+

685+ + Automatically set installation path (Program Files or Local App Data).

686+ + Set system PATH environment variable when installing for all users.

687+ + Pandoc can installed for all users using the following command.

688+ `msiexec /i pandoc-1.11.msi ALLUSERS=1`.

689+

690+ * Bumped QuickCheck version bound.

691+

692+pandoc (1.11)

693+

694+ * Added `--number-offset` option. (See README for description.)

695+

696+ * Added `--default-image-extension` option. (See README for description.)

697+

698+ * `--number-sections` behavior change: headers with class `unnumbered`

699+ will not be numbered.

700+

701+ * `--version` now reports the default data directory.

702+

703+ * `Text.Pandoc.Parsing` is no longer exposed. (API change.)

704+

705+ * `Text.Pandoc.Highlighting` is no longer exposed. (API change.)

706+

707+ * `Text.Pandoc.Shared`: Changed type of `Element`. `Sec` now includes

708+ a field for `Attr` rather than just `String`. (API change.)

709+

710+ * Added `markdown_github` as input format. This was an accidental

711+ omission in 1.10.

712+

713+ * Added `readerDefaultImageExtension` field to `ReaderOptions`. (API

714+ change.)

715+

716+ * Added `writerNumberOffset` field in `WriterOptions`. (API change.)

717+

718+ * Beamer template:

719+

720+ + Fixed captions with longtable. Thanks to Joost Kremers.

721+ + Provide `\Oldincludegraphics` as in LaTeX template (Benjamin Bannier).

722+

723+ * LaTeX template:

724+

725+ + Load microtype after fonts. Microtype needs to know

726+ what fonts are being used. Thanks to dfc for the patch.

727+ + Set `secnumdepth` to 5 if `--number-sections` specified.

728+ This yields behavior equivalent to the other writers, numbering

729+ level 4 and 5 headers too. Closes #753.

730+

731+ * HTML reader:

732+

733+ + Handle `<colgroup>` tag.

734+ + Preserve all header attributes.

735+

736+ * LaTeX reader:

737+

738+ + Parse `\hrule` as `HorizontalRule`. Closes #746.

739+ + Parse starred variants of `\section` etc. as headers with

740+ attribute `unnumbered`.

741+ + Read optional attributes in `lstlisting` and `Verbatim` environments.

742+ We convert these to pandoc standard names, e.g. `numberLines`

743+ for `numbers=left`, `startFrom=100` from `firstnumber=100`.

744+ + Handle language attribute for lstlistings.

745+ + Better support for Verbatim and minted environments. Closes #763.

746+

747+ * Markdown reader:

748+

749+ + `-` in an attribute context = `.unnumbered`. The point of this

750+ is to provide a way to specify unnumbered headers in non-English

751+ documents.

752+ + Fixed bug parsing key/value attributes. Parsing failed if you

753+ had an unquoted attribute immediately before the final '}'.

754+ + Make backslash escape work in attributes.

755+ + Fix title block parsing. Now if `mmd_title_blocks` is specified,

756+ pandoc will parse a MMD title block if it sees one, even if

757+ `pandoc_title_blocks` is enabled.

758+ + Refactoring: `litChar` now includes entities, so we don't need

759+ to use `fromEntities` e.g. on titles.

760+ + Allow spaces around borders in pipe tables. Closes #772.

761+ + Allow all punctuation in angle-bracket autolinks. Previously

762+ things like `----` were disallowed, because the uri parser

763+ treated them as trailing punctuation. Closes #768.

764+ + Make `implicit_header_references` work properly when

765+ headers are given explicit identifiers.

766+ + Check for tables before line blocks. Otherwise some pipe

767+ tables get treated as line blocks.

768+ + Allow `&` in emails (for entities).

769+ + Properly handle entities in titles and links. A markdown link

770+ `<http://g&ouml;ogle.com>` should be a link to `http://göogle.com`.

771+ Closes #723.

772+

773+ * Textile reader:

774+

775+ + Handle attributes on headers.

776+

777+ * LaTeX reader:

778+

779+ + Add `fig:` as title for images with captions.

780+ This is needed for them to be rendered as figures. Closes #766.

781+ + Never emit an empty paragraph. See #761.

782+ + Handle `\caption` for images in figures. Closes #766.

783+ + Parse `\section*`, etc. as unnumbered sections.

784+

785+ * HTML writer:

786+

787+ + Support header attributes. The attributes go on

788+ the enclosing `section` or `div` tag if `--section-divs` is specified.

789+ + Fixed a regression (only now noticed) in html+lhs output.

790+ Previously the bird tracks were being omitted.

791+

792+ * LaTeX writer:

793+

794+ + Omit lists with no items to avoid LaTeX errors.

795+ + Support line numbering with `--listings`.

796+ If `numberLines` class is present, we add `numbers=left`;

797+ if `startFrom` is present, we add `firstnumber=`. (#763)

798+

799+ * ConTeXt writer:

800+

801+ + Removed `\placecontent`. This produced a duplicate toc,

802+ in conjunction with `\placelist`.

803+ + Use `\title`, `\subject` etc. for headers with

804+ `unnumbered` class.

805+

806+ * Textile writer:

807+

808+ + Support header attributes.

809+

810+ * Markdown writer:

811+

812+ + Use grid tables when needed, and if enabled. Closes #740.

813+ + Render citations as pandoc-markdown citations.

814+ Previously citations were rendered as citeproc-formatted citations

815+ by default. Now we render them as pandoc citations, e.g. `[@item1]`,

816+ unless the `citations` extension is disabled.

817+ If you still want formatted citations in your markdown output,

818+ use `pandoc -t markdown-citations`.

819+

820+ * RST writer:

821+

822+ + Support `:number-lines:` in code blocks.

823+

824+ * Docx writer:

825+

826+ + Better treatment of display math. Display math inside a

827+ paragraph is now put in a separate paragraph, so it will render

828+ properly (centered and without extra blank lines around it).

829+ Partially addresses #742.

830+ + Content types and document rels xml files are now created from

831+ scratch, rather than being taken over from `reference.docx`.

832+ This fixes problems that arise when you edit the `reference.docx`

833+ with Word.

834+ + We also now encode mime types for each individual image rather

835+ than using defaults. This should allow us to handle a wider

836+ range of image types (including PDF). Closes #414.

837+ + Changed style names in `reference docx`.

838+ `FootnoteReference` -> `FootnoteRef`, `Hyperlink` -> `Link`.

839+ The old names got changed by Word when the `reference.docx` was

840+ edited. Closes #414.

841+

842+ * EPUB writer:

843+

844+ + Fix section numbering. Previously the numbering restarted from 1

845+ in each chapter (with `--number-sections`), though the numbers in

846+ the table of contents were correct.

847+ + Headers with "unnumbered" attribute are not numbered. (Nor do they

848+ cause an increment in running numbering.) Section numbers now work

849+ properly, even when there is material before the first numbered section.

850+ + Include HTML TOC, even in epub2. The TOC is included in `<spine>`,

851+ but `linear` is set to `no` unless the `--toc` option is specified.

852+ Include `<guide>` element in OPF. This should allow the TOC to

853+ be useable in Kindles when converted with kindlegen. Closes #773.

854+

855+ * `Text.Pandoc.Parsing`: Optimized `oneOfStringsCI`.

856+ This dramatically reduces the speed penalty that comes from enabling the

857+ `autolink_bare_uris` extension. The penalty is still substantial (in one

858+ test, from 0.33s to 0.44s), but nowhere near what it used to be.

859+ The RST reader is also much faster now, as it autodetects URIs.

860+

861+ * `Text.Pandoc.Shared`: `hierarchicalize` will not number section

862+ with class "unnumbered". Unnumbered sections get `[]` for their

863+ section number.

864+

865+ * `Text.Pandoc.Pretty`:

866+

867+ + Fixed `chomp` so it works inside `Prefixed` elements.

868+ + Changed `Show` instance so it is better for debugging.

869+

870+ * `Text.Pandoc.ImageSize`: Added `Pdf` to `ImageType`.

871+

872+ * `Text.Pandoc.UTF8`: Strip off BOM if present. Closes #743.

873+

874+ * Windows installer improvements:

875+

876+ + The installer is now signed with a certificate (thanks to

877+ Fyodor Sheremetyev).

878+ + WiX is used instead of InnoSetup. The installer is now a

879+ standard msi file.

880+ + The version number is now auto-detected, and need not be

881+ updated separately.

882+

883+ * OSX installer improvements:

884+

885+ + The package and pandoc executable are now signed with a

886+ certificate (thanks to Fyodor Sheremetyev).

887+ + RTF version of license is used.

888+ + Use full path for sysctl in `InstallationCheck` script (jonahbull).

889+ Closes #580.

890+

891+ * Converted COPYING to markdown.

892+

893+ * pandoc.cabal: Require latest versions of highlighting-kate,

894+ texmath, citeproc-hs, zip-archive.

895+

896+pandoc (1.10.1)

897+

898+ * Markdown reader: various optimizations, leading to a

899+ significant performance boost.

900+

901+ * RST reader: Allow anonymous form of inline links:

902+ `` `hello <url>`__ `` Closes #724.

903+

904+ * Mediawiki reader: Don't require newlines after tables.

905+ Thanks to jrunningen for the patch. Closes #733.

906+

907+ * Fixed LaTeX macro parsing. Now LaTeX macro definitions are preserved

908+ when output is LaTeX, and applied when it is another format.

909+ Partially addresses #730.

910+

911+ * Markdown and RST readers: Added parser to `block` that skips blank

912+ lines. This fixes a subtle regression involving grid tables with

913+ empty cells. Also added test for grid table with empty cells.

914+ Closes #732.

915+

916+ * RST writer: Use `.. code:: language` for code blocks with language.

917+ Closes #721.

918+

919+ * DocBook writer: Fixed output for hard line breaks, adding a newline

920+ between `<literallayout>` tags.

921+

922+ * Markdown writer: Use an autolink when link text matches url.

923+ Previously we also checked for a null title, but this

924+ test fails for links produced by citeproc-hs in bibliographies.

925+ So, if the link has a title, it will be lost on conversion

926+ to an autolink, but that seems okay.

927+

928+ * Markdown writer: Set title, author, date variables as before.

929+ These are no longer used in the default template, since we use

930+ titleblock, but we set them anyway for those who use custom templates.

931+

932+ * LaTeX writer: Avoid extra space at start/end of table cell.

933+ Thanks to Nick Bart for the suggestion of using @{}.

934+

935+ * `Text.Pandoc.Parsing`:

936+

937+ + More efficient version of `anyLine`.

938+ + Type of `macro` has changed; the parser now returns `Blocks`

939+ instead of `Block`.

940+

941+ * Relaxed old-time version bound, allowing 1.0.*.

942+

943+ * Removed obsolete `hsmarkdown` script. Those who need `hsmarkdown`

944+ should create a symlink as described in the README.

945+

946+pandoc (1.10.0.5)

947+

948+ * Markdown reader: Try `lhsCodeBlock` before `rawTeXBlock`. Otherwise

949+ `\begin{code}...\end{code}` isn't handled properly in markdown+lhs.

950+ Thanks to Daniel Miot for noticing the bug and suggesting the fix.

951+

952+ * Markdown reader: Fixed bug with headerless grid tables.

953+ The 1.10 code assumed that each table header cell contains exactly one

954+ block. That failed for headerless tables (0) and also for tables with

955+ multiple blocks in a header cell. The code is fixed and tests provided.

956+ Thanks to Andrew Lee for pointing out the bug.

957+

958+ * Markdown reader: Fixed regressions in fenced code blocks. Closes #722.

959+

960+ + Tilde code fences can again take a bare language string

961+ (`~~~ haskell`), not just curly-bracketed attributes

962+ (`~~~ {.haskell}`).

963+ + Backtick code blocks can take the curly-bracketed attributes.

964+ + Backtick code blocks don't *require* a language.

965+ + Consolidated code for the two kinds of fenced code blocks.

966+

967+ * LaTeX template: Use `\urlstyle{same}` to avoid monospace URLs.

968+

969+ * Markdown writer: Use proportional font for email autolinks with

970+ obfuscation. Closes #714.

971+

972+ * Corrected name of `blank_before_blockquote` in README. Closes #718.

973+

974+ * `Text.Pandoc.Shared`: Fixed bug in `uri` parser.

975+ The bug prevented an autolink at the end of a string (e.g.

976+ at the end of a line block line) from counting as a link. Closes #711.

977+

978+ * Use the `hsb2hs` preprocessor instead of TH for embed_data_files.

979+ This should work on Windows, unlike the TH solution with

980+ file-embed.

981+

982+ * Eliminated use of TH in test suite.

983+

984+ * Added `Text.Pandoc.Data` (non-exported) to hold the association

985+ list of embedded data files, if the `embed_data_files` flag is selected.

986+ This isolates the code that needs special treatment with file-embed or

987+ `hsb2hs`.

988+

989+ * Changes to `make-windows-installer.bat`.

990+

991+ + Exit batch file if any of the cabal-dev installs fail.

992+ + There's no longer any need to reinstall `highlighting-kate`.

993+ + Don't start with a `cabal update`; leave that to the user.

994+ + Force reinstall of pandoc.

995+

996+ * Fixed EPUB writer so it builds with blaze-html 0.4.x. Thanks to

997+ Jens Petersen.

998+

999+pandoc (1.10.0.4)

1000+

1001+ * Fixed bug with escaped % in LaTeX reader. Closes #710.

1002+

1003+pandoc (1.10.0.3)

1004+

1005+ * Added further missing fb2 tests to cabal file.

1006+

1007+pandoc (1.10.0.2)

1008+

1009+ * Added fb2 tests to cabal file's extra-source-files.

1010+

1011+pandoc (1.10.0.1)

1012+

1013+ * Bump version bounds on test-framework packages.

1014+

1015+pandoc (1.10)

1016+

1017+ [new features]

1018+

1019+ * New input formats: `mediawiki` (MediaWiki markup).

1020+

1021+ * New output formats: `epub3` (EPUB v3 with MathML),

1022+ `fb2` (FictionBook2 ebooks).

1023+

1024+ * New `--toc-depth` option, specifying how many levels of

1025+ headers to include in a table of contents.

1026+

1027+ * New `--epub-chapter-level` option, specifying the header

1028+ level at which to divide EPUBs into separate files.

1029+ Note that this normally affects only performance, not the

1030+ visual presentation of the EPUB in a reader.

1031+

1032+ * Removed the `--strict` option. Instead of using `--strict`,

1033+ one can now use the format name `markdown_strict` for either input

1034+ or output. This gives more fine-grained control that `--strict`

1035+ did, allowing one to convert from pandoc's markdown to strict

1036+ markdown or vice versa.

1037+

1038+ * It is now possible to enable or disable specific syntax

1039+ extensions by appending them (with `+` or `-`) to the writer

1040+ or reader name. For example,

1041+

1042+ pandoc -f markdown-footnotes+hard_line_breaks

1043+

1044+ disables footnotes and enables treating newlines as hard

1045+ line breaks. The literate Haskell extensions are now implemented

1046+ this way as well, using either `+lhs` or `+literate_haskell`.

1047+ For a list of extension names, see the README under

1048+ "Pandoc's Markdown."

1049+

1050+ * The following aliases have been introduced for specific

1051+ combinations of markdown extensions: `markdown_phpextra`,

1052+ `markdown_github`, `markdown_mmd`, `markdown_strict`. These aliases

1053+ work just like regular reader and writer names, and can be modified

1054+ with extension modifiers as described above. (Note that conversion

1055+ from one markdown dialect to another does not work perfectly,

1056+ because there are differences in markdown parsers besides

1057+ just the extensions, and because pandoc's internal document model is

1058+ not rich enough to capture all of the extensions.)

1059+

1060+ * New `--html-q-tags` option. The previous default was to use `<q>`

1061+ tags for smart quotes in HTML5. But `<q>` tags are also valid HTML4.

1062+ Moreover, they are not a robust way of typesetting quotes, since

1063+ some user agents don't support them, and some CSS resets (e.g.

1064+ bootstrap) prevent pandoc's quotes CSS from working properly.

1065+ We now just insert literal quote characters by default in both

1066+ `html` and `html5` output, but this option is provided for

1067+ those who still want `<q>` tags.

1068+

1069+ * The markdown reader now prints warnings (to stderr) about

1070+ duplicate link and note references. Closes #375.

1071+

1072+ * Markdown syntax extensions:

1073+

1074+ + Added pipe tables. Thanks to François Gannaz for the initial patch.

1075+ These conform to PHP Markdown Extra's pipe table syntax. A subset

1076+ of org-mode table syntax is also supported, which means that you can

1077+ use org-mode's nice table editor to create tables.

1078+

1079+ + Added support for RST-style line blocks. These are

1080+ useful for verse and addresses.

1081+

1082+ + Attributes can now be specified for headers, using the same

1083+ syntax as in code blocks. (However, currently only the

1084+ identifier has any effect in most writers.) For example,

1085+

1086+ # My header {#foo}

1087+

1088+ See [the header above](#foo).

1089+

1090+ + Pandoc will now act as if link references have been defined

1091+ for all headers without explicit identifiers.

1092+ So, you can do this:

1093+

1094+ # My header

1095+

1096+ Link to [My header].

1097+ Another link to [it][My header].

1098+

1099+ Closes #691.

1100+

1101+ * LaTeX reader:

1102+

1103+ + Command macros now work everywhere, including non-math.

1104+ Environment macros still not supported.

1105+ + `\input` now works, as well as `\include`. TEXINPUTS is used.

1106+ Pandoc looks recursively into included files for more included files.

1107+

1108+ [behavior changes]

1109+

1110+ * The Markdown reader no longer puts the text of autolinks in a

1111+ `Code` inline. This means that autolinks will no longer appear

1112+ in a monospace font.

1113+

1114+ * The character `/` can now appear in markdown citation keys.

1115+

1116+ * HTML blocks in strict_markdown are no longer required to begin

1117+ at the left margin. Technically this is required, according to

1118+ the markdown syntax document, but `Markdown.pl` and other markdown

1119+ processors are more liberal.

1120+

1121+ * The `-V` option has been changed so that if there are duplicate

1122+ variables, those specified later on the command line take precedence.

1123+

1124+ * Tight lists now work in LaTeX and ConTeXt output.

1125+

1126+ * The LaTeX writer no longer relien on the `enumerate` package.

1127+ Instead, it uses standard LaTeX commands to change the list numbering

1128+ style.

1129+

1130+ * The LaTeX writer now uses `longtable` instead of `ctable`. This allows

1131+ tables to be split over page boundaries.

1132+

1133+ * The RST writer now uses a line block to render paragraphs containing

1134+ linebreaks (which previously weren't supported at all).

1135+

1136+ * The markdown writer now applies the `--id-prefix` to footnote IDs.

1137+ Closes #614.

1138+

1139+ * The plain writer no longer uses backslash-escaped line breaks

1140+ (which are not very "plain").

1141+

1142+ * `Text.Pandoc.UTF8`: Better error message for invalid UTF8.

1143+ Read bytestring and use `Text`'s decodeUtf8 instead of using

1144+ `System.IO.hGetContents`. This way you get a message saying

1145+ "invalid UTF-8 stream" instead of "invalid byte sequence."

1146+ You are also told which byte caused the problem.

1147+

1148+ * Docx, ODT, and EPUB writers now download images specified by a URL

1149+ instead of skipping them or raising an error.

1150+

1151+ * EPUB writer:

1152+

1153+ + The default CSS now left-aligns headers by default, instead of

1154+ centering. This is more consistent with the rest of the writers.

1155+ + A proper multi-level table of contents is now used in `toc.ncx`.

1156+ There is no longer a subsidiary table of contents at the beginning

1157+ of each chapter.

1158+ + Code highlighting now works by default.

1159+ + Section divs are used by default for better semantic markup.

1160+ + The title is used instead of "Title Page" in the table of contents.

1161+ Otherwise we have a hard-coded English string, which looks

1162+ strange in ebooks written in other languages. Closes #572.

1163+

1164+ * HTML writer:

1165+

1166+ + Put mathjax in span with class "math". Closes #562.

1167+ + Put citations in a span with class "citation." In HTML5, also include

1168+ a `data-cite` attribute with a space-separated list of citation

1169+ keys.

1170+

1171+ * `Text.Pandoc.UTF8`: use universalNewlineMode in reading.

1172+ This treats both `\r\n` and `\n` as `\n` on input, no matter

1173+ what platform we're running on.

1174+

1175+ * Citation processing is now done in the Markdown and LaTeX

1176+ readers, not in `pandoc.hs`. This makes it easier for library users

1177+ to use citations.

1178+

1179+ [template changes]

1180+

1181+ * HTML: Added css to template to preserve spaces in `<code>` tags.

1182+ Thanks to Dirk Laurie.

1183+

1184+ * Beamer: Remove English-centric strings in section pages.

1185+ Section pages used to have "Section" and a number as well as the

1186+ section title. Now they just have the title. Similarly for part

1187+ and subsection. Closes #566.

1188+

1189+ * LaTeX, ConTeXt: Added papersize variable.

1190+

1191+ * LaTeX, Beamer templates: Use longtable instead of ctable.

1192+

1193+ * LaTeX, Beamer templates: Don't require 'float' package for tables.

1194+ We don't actually seem to use the '[H]' option.

1195+

1196+ * LaTeX: Use `upquote` package if it is available. This fixes

1197+ straight quotes in verbatim environments.

1198+

1199+ * Markdown, plain: Fixed titleblock so it is just a single string.

1200+ Previously separate title, author, and date variables were used,

1201+ but this didn't allow different kinds of title blocks.

1202+

1203+ * EPUB:

1204+

1205+ + Rationalized templates. Previously there were three different

1206+ templates involved in epub production. There is now just one

1207+ template, `default.epub` or `default.epub3`. It can now be

1208+ overridden using `--template`, just like other templates.

1209+ The titlepage is now folded into the default template.

1210+ A `titlepage` variable selects it.

1211+ + UTF-8, lang tag, meta tags, title element.

1212+

1213+ * Added scale-to-width feature to beamer template

1214+

1215+ [API changes]

1216+

1217+ * `Text.Pandoc.Definition`: Added `Attr` field to `Header`.

1218+ Previously header identifers were autogenerated by the writers.

1219+ Now they are added in the readers (either automatically or explicitly).

1220+

1221+ * `Text.Pandoc.Builder`:

1222+

1223+ + `Inlines` and `Blocks` are now synonyms for `Many Inline` and

1224+ `Many Block`. `Many` is a newtype wrapper around `Seq`, with

1225+ custom Monoid instances for `Many Inline` and `Many Block. This

1226+ allows `Many` to be made an instance of `Foldable` and `Traversable`.

1227+ + The old `Listable` class has been removed.

1228+ + The module now exports `isNull`, `toList`, `fromList`.

1229+ + The old `Read` and `Show` instances have been removed; derived

1230+ instances are now used.

1231+ + Added `headerWith`.

1232+

1233+ * The readers now take a `ReaderOptions` rather than a `ParserState`

1234+ as a parameter. Indeed, not all parsers use the `ParserState` type;

1235+ some have a custom state. The motivation for this change was to separate

1236+ user-specifiable options from the accounting functions of parser state.

1237+

1238+ * New module `Text.Pandoc.Options`. This includes the `WriterOptions`

1239+ formerly in `Text.Pandoc.Shared`, and its associated

1240+ data types. It also includes a new type `ReaderOptions`, which

1241+ contains many options formerly in `ParserState`, and its associated

1242+ data types:

1243+

1244+ + `ParserState.stateParseRaw` -> `ReaderOptions.readerParseRaw`.

1245+ + `ParserState.stateColumns` -> `ReaderOptions.readerColumns`.

1246+ + `ParserState.stateTabStop` -> `ReaderOptions.readerTabStop`.

1247+ + `ParserState.stateOldDashes` -> `ReaderOptions.readerOldDashes`.

1248+ + `ParserState.stateLiterateHaskell` -> `ReaderOptions.readerLiterateHaskell`.

1249+ + `ParserState.stateCitations` -> `ReaderOptions.readerReferences`.

1250+ + `ParserState.stateApplyMacros` -> `ReaderOptions.readerApplyMacros`.

1251+ + `ParserState.stateIndentedCodeClasses` ->

1252+ `ReaderOptions.readerIndentedCodeClasses`.

1253+ + Added `ReaderOptions.readerCitationStyle`.

1254+

1255+ * `WriterOptions` now includes `writerEpubVersion`, `writerEpubChapterLevel`,

1256+ `writerEpubStylesheet`, `writerEpubFonts`, `writerReferenceODT`,

1257+ `writerReferenceDocx`, and `writerTOCDepth`. `writerEPUBMetadata` has

1258+ been renamed `writerEpubMetadata` for consistency.

1259+

1260+ * Changed signatures of `writeODT`, `writeDocx`, `writeEPUB`, since they no

1261+ longer stylesheet, fonts, reference files as separate parameters.

1262+

1263+ * Removed `writerLiterateHaskell` from `WriterOptions`, and

1264+ `readerLiterateHaskell` from `ReaderOptions`. LHS is now handled

1265+ by an extension (`Ext_literate_haskell`).

1266+

1267+ * Removed deprecated `writerXeTeX`.

1268+

1269+ * Removed `writerStrict` from `WriterOptions`. Added `writerExtensions`.

1270+ Strict is now handled through extensions.

1271+

1272+ * `Text.Pandoc.Options` exports `pandocExtensions`, `strictExtensions`,

1273+ `phpMarkdownExtraExtensions`, `githubMarkdownExtensions`,

1274+ and `multimarkdownExtensions`, as well as the `Extensions` type.

1275+

1276+ * New `Text.Pandoc.Readers.MediaWiki` module, exporting

1277+ `readMediaWiki`.

1278+

1279+ * New `Text.Pandoc.Writers.FB2` module, exporting `writeFB2`

1280+ (thanks to Sergey Astanin).

1281+

1282+ * `Text.Pandoc`:

1283+

1284+ + Added `getReader`, `getWriter` to `Text.Pandoc`.

1285+ + `writers` is now an association list `(String, Writer)`.

1286+ A `Writer` can be a `PureStringWriter`, an `IOStringWriter`, or

1287+ an `IOByteStringWriter`. ALL writers are now in the 'writers'

1288+ list, including the binary writers and FB2 writer. This allows

1289+ code in `pandoc.hs` to be simplified.

1290+ + Changed type of `readers`, so all readers are in IO.

1291+ Users who want pure readers can still get them form the reader

1292+ modules; this just affects the function `getReader` that looks up

1293+ a reader based on the format name. The point of this change is to

1294+ make it possible to print warnings from the parser.

1295+

1296+ * `Text.Pandoc.Parsing`:

1297+

1298+ + `Text.Parsec` now exports all Parsec functions used in pandoc code.

1299+ No other module directly imports Parsec. This will make it easier

1300+ to change the parsing backend in the future, if we want to.

1301+ + `Text.Parsec` is used instead of `Text.ParserCombinators.Parsec`.

1302+ + Export the type synonym `Parser`.

1303+ + Export `widthsFromIndices`, `NoteTable'`, `KeyTable'`, `Key'`, `toKey'`,

1304+ `withQuoteContext`, `singleQuoteStart`, `singleQuoteEnd`,

1305+ `doubleQuoteStart`, `doubleQuoteEnd`, `ellipses`, `apostrophe`,

1306+ `dash`, `nested`, `F(..)`, `askF`, `asksF`, `runF`, `lineBlockLines`.

1307+ + `ParserState` is no longer an instance of `Show`.

1308+ + Added `stateSubstitutions` and `stateWarnings` to `ParserState`.

1309+ + Generalized type of `withQuoteContext`.

1310+ + Added `guardEnabled`, `guardDisabled`, `getOption`.

1311+ + Removed `failIfStrict`.

1312+ + `lookupKeySrc` and `fromKey` are no longer exported.

1313+

1314+ * `Data.Default` instances are now provided for `ReaderOptions`,

1315+ `WriterOptions`, and `ParserState`. `Text.Pandoc` re-exports `def`.

1316+ Now you can use `def` (which is re-exported by `Text.Pandoc`) instead

1317+ of `defaultWriterOptions` (which is still defined). Closes #546.

1318+

1319+ * `Text.Pandoc.Shared`:

1320+

1321+ + Added `safeRead`.

1322+ + Renamed `removedLeadingTrailingSpace` to `trim`,

1323+ `removeLeadingSpace` to `triml`, and `removeTrailingSpace` to `trimr`.

1324+ + Count `\r` as space in `trim` functions.

1325+ + Moved `renderTags'` from HTML reader and `Text.Pandoc.SelfContained`

1326+ to `Shared`.

1327+ + Removed `failUnlessLHS`.

1328+ + Export `compactify'`, formerly in Markdown reader.

1329+ + Export `isTightList`.

1330+ + Do not export `findDataFile`.

1331+ + `readDataFile` now returns a strict ByteString.

1332+ + Export `readDataFileUTF8` which returns a String, like the

1333+ old `readDataFile`.

1334+ + Export `fetchItem` and `openURL`.

1335+

1336+ * `Text.Pandoc.ImageSize`: Use strict, not lazy bytestrings.

1337+ Removed `readImageSize`.

1338+

1339+ * `Text.Pandoc.UTF8`: Export `encodePath`, `decodePath`,

1340+ `decodeArg`, `toString`, `fromString`, `toStringLazy`,

1341+ `fromStringLazy`.

1342+

1343+ * `Text.Pandoc.UTF8` is now an exposed module.

1344+

1345+ * `Text.Pandoc.Biblio`:

1346+

1347+ + csl parameter now a `String` rather than a `FilePath`.

1348+ + Changed type of `processBiblio`. It is no longer in the IO monad.

1349+ It now takes a `Maybe Style` argument rather than parameters for CSL

1350+ and abbrev filenames. (`pandoc.hs` now calls the functions to parse

1351+ the style file and add abbreviations.)

1352+

1353+ * Markdown reader now exports `readMarkdownWithWarnings`.

1354+

1355+ * `Text.Pandoc.RTF` now exports `writeRTFWithEmbeddedImages` instead of

1356+ `rtfEmbedImage`.

1357+

1358+ [bug fixes]

1359+

1360+ * Make `--ascii` work properly with `--self-contained`. Closes #568.

1361+

1362+ * Markdown reader:

1363+

1364+ + Fixed link parser to avoid exponential slowdowns. Closes #620.

1365+ Previously the parser would hang on input like this:

1366+

1367+ [[[[[[[[[[[[[[[[[[hi

1368+

1369+ We fixed this by making the link parser parser characters

1370+ between balanced brackets (skipping brackets in inline code spans),

1371+ then parsing the result as an inline list. One change is that

1372+

1373+ [hi *there]* bud](/url)

1374+

1375+ is now no longer parsed as a link. But in this respect pandoc behaved

1376+ differently from most other implementations anyway, so that seems okay.

1377+

1378+ + Look for raw html/latex blocks before tables.

1379+ Otherwise the following gets parsed as a table:

1380+

1381+ \begin{code}

1382+ --------------

1383+ -- My comment.

1384+ \end{code}

1385+

1386+ Closes #578.

1387+

1388+ * RST reader:

1389+

1390+ + Added support for `:target:` on `.. image::` blocks

1391+ and substitutions.

1392+ + Field list fixes:

1393+

1394+ - Fixed field lists items with body beginning after a new line

1395+ (Denis Laxalde).

1396+ - Allow any char but ':' in names of field lists in RST reader

1397+ (Denis Laxalde).

1398+ - Don't allow line breaks in field names.

1399+ - Require whitespace after field list field names.

1400+ - Don't create empty definition list for metadata field lists.

1401+ Previously a field list consisting only of metadata fields (author,

1402+ title, date) would be parsed as an empty DefinitionList, which is

1403+ not legal in LaTeX and not needed in any format.

1404+

1405+ + Don't recognize inline-markup starts inside words.

1406+ For example, `2*2 = 4*1` should not contain an emphasized

1407+ section. Added test case for "Literal symbols". Closes #569.

1408+ + Allow dashes as separator in simple tables. Closes #555.

1409+ + Added support for `container`, `compound`, `epigraph`,

1410+ `rubric`, `highlights`, `pull-quote`.

1411+ + Added support for `.. code::`.

1412+ + Made directive labels case-insensitive.

1413+ + Removed requirement that directives begin at left margin.

1414+ This was (correctly) not in earlier releases; docutils doesn't

1415+ make the requirement.

1416+ + Added support for `replace::` and `unicode::` substitutions.

1417+ + Ignore unknown interpreted roles.

1418+ + Renamed image parser to `subst`, since it now handles all

1419+ substitution references.

1420+

1421+ * Textile reader:

1422+

1423+ + Allow newlines before pipes in table. Closes #654.

1424+ + Fixed bug with list items containing line breaks.

1425+ Now pandoc correctly handles hard line breaks inside list items.

1426+ Previously they broke list parsing.

1427+ + Implemented comment blocks.

1428+ + Fixed bug affected words ending in hyphen.

1429+ + Properly handle links with surrounding brackets.

1430+ Square brackets need to be used when the link isn't surrounded by

1431+ spaces or punctuation, or when the URL ending may be ambiguous.

1432+ Closes #564.

1433+ + Removed nullBlock. Better to know about parsing problems than

1434+ to skip stuff when we get stuck.

1435+ + Allow ID attributes on headers.

1436+ + Textile reader: Avoid parsing dashes as strikeout.

1437+ Previously the input

1438+

1439+ text--

1440+ text--

1441+ text--

1442+ text--

1443+

1444+ would be parsed with strikeouts rather than dashes. This fixes

1445+ the problem by requiring that a strikeout delimiting - not be

1446+ followed by a -. Closes #631.

1447+ + Expanded list of `stringBreakers`.

1448+ This fixes a bug on input like "(_hello_)" which should

1449+ be a parenthesized emphasized "hello".

1450+ The new list is taken from the PHP source of textile 2.4.

1451+ + Fixed autolinks. Previously the textile reader and writer

1452+ incorrectly implented RST-style autolinks for URLs and email

1453+ addresses. This has been fixed. Now an autolink is done this way:

1454+ `"$":http://myurl.com`.

1455+ + Fixed footnotes bug in textile. This affected notes occuring

1456+ before punctuation, e.g. `foo[1].`. Closes #518.

1457+

1458+ * LaTeX reader:

1459+

1460+ + Better handling of citation commands.

1461+ + Better handling of `\noindent`.

1462+ + Added a 'try' in rawLaTeXBlock, so we can handle `\begin` without `{`.

1463+ Closes #622.

1464+ + Made `rawLaTeXInline` try to parse block commands as well. This

1465+ is usually what we want, given how `rawLaTeXInline` is used in

1466+ the markdown and textile readers. If a block-level LaTeX command

1467+ is used in the middle of a paragraph (e.g. `\subtitle` inside a title),

1468+ we can treat it as raw inline LaTeX.

1469+ + Handle \slash command. Closes #605.

1470+ + Basic `\enquote` support.

1471+ + Fixed parsing of paragraphs beginning with a group. Closes #606.

1472+ + Use curly quotes for bare straight quotes.

1473+ + Support obeylines environment. Closes #604.

1474+ + Guard against "begin", "end" in inlineCommand and

1475+ blockCommand.

1476+ + Better error messages for environments. Now it should tell you that

1477+ it was looking for \end{env}, instead of giving "unknown parse error."

1478+

1479+ * HTML reader:

1480+

1481+ + Added HTML 5 tags to list of block-level tags.

1482+ + HTML reader: Fixed bug in `htmlBalanced`, which

1483+ caused hangs in parsing certain markdown input using

1484+ strict mode.

1485+ + Parse `<q>` as `Quoted DoubleQuote`.

1486+ + Handle nested `<q>` tags properly.

1487+ + Modified `htmlTag` for fewer false positives.

1488+ A tag must start with `<` followed by `!`,`?`, `/`, or a letter.

1489+ This makes it more useful in the wikimedia and markdown parsers.

1490+

1491+ * DocBook reader: Support title in "figure" element. Closes #650.

1492+

1493+ * MediaWiki writer:

1494+

1495+ + Remove newline after `<br/>` in translation of `LineBreak`

1496+ There's no particular need for a newline (other than making the

1497+ generated MediaWiki source look nice to a human), and in fact

1498+ sometimes it is incorrect: in particular, inside an enumeration, list

1499+ items cannot have embedded newline characters. (Brent Yorgey)

1500+ + Use `<code>` not `<tt>` for Code.

1501+

1502+ * Man writer: Escape `-` as `\-`.

1503+ Unescaped `-`'s become hyphens, while `\-`'s are left as ascii minus

1504+ signs. That is preferable for use with command-line options. See

1505+ <http://lintian.debian.org/tags/hyphen-used-as-minus-sign.html>. Thanks

1506+ to Andrea Bolognani for bringing the issue to our attention.

1507+

1508+ * RST writer:

1509+

1510+ + Improved line block output. Use nonbreaking spaces for

1511+ initial indent (otherwise lost in HTML and LaTeX).

1512+ Allow multiple paragraphs in a single line block.

1513+ Allow soft breaks w continuations in line blocks.

1514+ + Properly handle images with no alt text. Closes #678.

1515+ + Fixed bug with links with duplicate text. We now (a) use anonymous

1516+ links for links with inline URLs, and (b) use an inline link instead

1517+ of a reference link if the reference link would require a label that

1518+ has already been used for a different link. Closes #511.

1519+ + Fixed hyperlinked images. Closes #611. Use `:target:`

1520+ field when you have a simple linked image.

1521+ + Don't add `:align: center` to figures.

1522+

1523+ * Texinfo writer: Fixed internal cross-references.

1524+ Now we insert anchors after each header, and use `@ref` instead of `@uref`

1525+ for links. Commas are now escaped as `@comma{}` only when needed;

1526+ previously all commas were escaped. (This change is needed, in part,

1527+ because `@ref` commands must be followed by a real comma or period.) Also

1528+ insert a blank line in from of `@verbatim` environments.

1529+

1530+ * DocBook writer:

1531+

1532+ + Made --id-prefix work in DocBook as well as HTML.

1533+ Closes #607.

1534+ + Don't include empty captions in figures. Closes #581.

1535+

1536+ * LaTeX writer:

1537+

1538+ + Use `\hspace*` for nonbreaking space after line break,

1539+ since `~` spaces after a line break are just ignored.

1540+ Closes #687.

1541+ + Don't escape `_` in URLs or hyperref identifiers.

1542+ + Properly escape strings inside \url{}. Closes #576.

1543+ + Use `[fragile]` only for slides containing code rendered

1544+ using listings. Closes #649.

1545+ + Escape `|` as `\vert` in LaTeX math. This avoids a clash with

1546+ highlighting-kate's macros, which redefine `|` as a short verbatim

1547+ delimiter. Thanks to Björn Peemöller for raising this issue.

1548+ + Use minipage rather than parbox for block containers in tables.

1549+ This allows verbatim code to be included in grid tables.

1550+ Closes #663.

1551+ + Prevent paragraphs containing only linebreaks or spaces.

1552+

1553+ * HTML writer:

1554+

1555+ + Included `highlighting-css` for code spans, too.

1556+ Previously it was only included if used in a code block. Closes #653.

1557+ + Improved line breaks with `<dd>` tags. We now put a newline between

1558+ `</dd>` and `<dd>` when there are multiple definitions.

1559+ + Changed mathjax cdn url so it doesn't use https. (This caused

1560+ problems when used with `--self-contained`.) See #609.

1561+

1562+ * EPUB writer:

1563+

1564+ + `--number-sections` now works properly.

1565+ + Don't strip meta and link elements in epub metadata.

1566+ Patch from aberrancy. Closes #589.

1567+ + Fixed a couple validation bugs.

1568+ + Use ch001, ch002, etc. for chapter filenames. This improves sorting

1569+ of chapters in some readers, which apparently sort ch2 after ch10.

1570+ Closes #610.

1571+

1572+ * ODT writer: properly set title property (Arlo O'Keeffe).

1573+

1574+ * Docx writer:

1575+

1576+ + Fixed bug with nested lists. Previously a list like

1577+

1578+ 1. one

1579+ - a

1580+ - b

1581+ 2. two

1582+

1583+ would come out with a bullet instead of "2."

1584+ Thanks to Russell Allen for reporting the bug.

1585+ + Use `w:cr` in `w:r` instead of `w:br` for linebreaks.

1586+ This seems to fix a problem viewing pandoc-generated

1587+ docx files in LibreOffice.

1588+ + Use integer ids for bookmarks. Closes #626.

1589+ + Added nsid to abstractNum elements. This helps when merging

1590+ word documents with numbered or bulleted lists. Closes #627.

1591+ + Use separate footnotes.xml for notes.

1592+ This seems to help LibreOffice convert the file, even though

1593+ it was valid docx before. Closes #637.

1594+ + Use rIdNN identifiers for r:embed in images.

1595+ + Avoid reading image files again when we've already processed them.

1596+ + Fixed typo in `referenc.docx` that prevented image captions from

1597+ working. Thanks to Huashan Chen.

1598+

1599+ * `Text.Pandoc.Parsing`:

1600+

1601+ + Fixed bug in `withRaw`, which didn't correctly handle the case

1602+ where nothing is parsed.

1603+ + Made `emailAddress` parser more correct. Now it is based on RFC 822,

1604+ though it still doesn't implement quoted strings in email addresses.

1605+ + Revised URI parser. It now allows many more schemes, allows

1606+ uppercase URIs, and better handles trailing punctuation and

1607+ trailing slashes in bare URIs. Added many tests.

1608+ + Simplified and improved singleQuoteStart. This makes `'s'`, `'l'`,

1609+ etc. parse properly. Formerly we had some English-centric heuristics,

1610+ but they are no longer needed. Closes #698.

1611+

1612+ * `Text.Pandoc.Pretty`: Added wide punctuation range to `charWidth`.

1613+ This fixes bug with Chinese commas in markdown and reST tables, and

1614+ a bug that caused combining characters to be dropped.

1615+

1616+ * `Text.Pandoc.MIME`: Added MIME types for .wof and .eot. Closes #640.

1617+

1618+ * `Text.Pandoc.Biblio`:

1619+

1620+ + Run `mvPunc` and `deNote` on metadata too.

1621+ This fixed a bug with notes on titles using footnote styles.

1622+ + Fixed bug in fetching CSL files from CSL data directory.

1623+

1624+ * `pandoc.hs`: Give correct value to `writerSourceDirectory` when a URL

1625+ is provided. It should be the URL up to the path.

1626+

1627+ * Fixed/simplified diff output for tests.

1628+ Biblio: Make sure mvPunc and deNote run on metadata too.

1629+ This fixed a bug with notes on titles using footnote styles.

1630+

1631+ [under the hood improvements]

1632+

1633+ * We no longer depend on `utf8-string`. Instead we use functions

1634+ defined in `Text.Pandoc.UTF8` that use `Data.Text`'s conversions.

1635+

1636+ * Use `safeRead` instead of using `reads` directly (various modules).

1637+

1638+ * "Implicit figures" (images alone in a paragraph) are now handled

1639+ differently. The markdown reader gives their titles the prefix `fig:`; the

1640+ writers look for this before treating the image as a figure. Though this

1641+ is a bit of a hack, it has two advantages: (i) implicit figures can be

1642+ limited to the markdown reader, and (ii) they can be deactivated by turning

1643+ off the `implicit_figures` extension.

1644+

1645+ * `catch` from `Control.Exception` is now used instead of the

1646+ old Preface `catch`.

1647+

1648+ * `Text.Pandoc.Shared`: Improved algorithm for `normalizeSpaces`

1649+ and `oneOfStrings` (which is now non-backtracking).

1650+

1651+ * `Text.Pandoc.Biblio`: Remove workaround for `toCapital`.

1652+ Now citeproc-hs is fixed upstream, so this is no longer needed.

1653+ Closes #531.

1654+

1655+ * Textile reader: Improved speed of `hyphenedWords`.

1656+ This speeds up the textile reader by about a factor of 4.

1657+

1658+ * Use `Text.Pandoc.Builder` in RST reader, for more flexibility,

1659+ better performance, and automatic normalization.

1660+

1661+ * Major rewrite of markdown reader:

1662+

1663+ + Use `Text.Pandoc.Builder` instead of lists. This also

1664+ means that everything is normalized automatically.

1665+ + Move to a one-pass parsing strategy, returning values in the reader

1666+ monad, which are then run (at the end of parsing) against the final

1667+ parser state.

1668+

1669+ * In HTML writer, we now use `toHtml` instead of pre-escaping.

1670+ We work around the problem that blaze-html unnecessarily escapes `'`

1671+ by pre-escaping just the `'` characters, instead of the whole string.

1672+ If blaze-html later stops escaping `'` characters, we can simplify

1673+ `strToHtml` to `toHtml`. Closes #629.

1674+

1675+ * Moved code for embedding images in RTFs from `pandoc.hs` to the

1676+ RTF writer (which now exports `writeRTFWithEmbeddedImages`).

1677+

1678+ * Moved citation processing from `pandoc.hs` into the readers.

1679+ This makes things more convenient for library users.

1680+

1681+ * The man pages are now built by an executable `make-pandoc-man-pages`,

1682+ which has its own stanza in the cabal file so that dependencies can be

1683+ handled by Cabal. Special treatment in `Setup.hs` ensures that this

1684+ executable never gets installed; it is only used to create the man pages.

1685+

1686+ * The cabal file has been modified so that the pandoc library is used

1687+ in building the pandoc executable. (This required moving `pandoc.hs`

1688+ from `src` to `.`.) This cuts compile time in half.

1689+

1690+ * `-O2` is no longer used in building pandoc. The performance improvement

1691+ it yields is so slight that it is not worth it. (Measured with

1692+ benchmarks on ghc 7.4.)

1693+

1694+ * The `executable` and `library` flags have been removed.

1695+

1696+ * `-threaded` has been removed from ghc-options.

1697+

1698+ * Version bounds of dependencies have been raised, and the

1699+ `blaze_html_0_5` flag now defaults to True. Pandoc now compiles on

1700+ GHC 7.6.

1701+

1702+ * We now require base >= 4.2.

1703+

1704+ * Integrated the benchmark program into cabal. One can now do:

1705+

1706+ cabal configure --enable-benchmarks && cabal build

1707+ cabal bench --benchmark-option='markdown' --benchmark-option='-s 20'

1708+

1709+ The benchmark now uses README + testsuite, so benchmark results

1710+ from older versions aren't comparable.

1711+

1712+ * Integrated test suite with cabal.

1713+ To run tests, configure with `--enable-tests`, then `cabal test`.

1714+ You can specify particular tests using `--test-options='-t markdown'`.

1715+ No output is shown unless tests fail. The Haskell test modules

1716+ have been moved from `src/` to `tests/`.

1717+

1718+ * Moved all data files and templates to the `data/` subdirectory.

1719+

1720+ * Added an `embed_data_files` cabal flag. This causes all

1721+ data files to be embedded in the binary, so that the binary

1722+ is self-sufficient and can be relocated anywhere, copied on

1723+ a USB key, etc. The Windows installer now uses this.

1724+ (Since we no longer have the option to build the executable

1725+ without the library, this is the only way to get a relocatable

1726+ binary on Windows.)

1727+

1728+ * Removed pcre3.dll from windows package.

1729+ It isn't needed unless highlighting-kate is compilled with the

1730+ `pcre-light` flag. By default, regex-prce-builtin is used.

1731+

1732+

1733+pandoc (1.9.4.2)

1734+

1735+ * Don't encode/decode file paths if base >= 4.4.

1736+ Prior to base 4.4, filepaths and command line arguments were treated

1737+ as unencoded lists of bytes, not unicode strings, so we had to work

1738+ around that by encoding and decoding them. This commit adds CPP

1739+ checks for the base version that intelligibly enable encoding/decoding

1740+ when needed. Fixes a bug with multilingual filenames when pandoc was

1741+ compiled with ghc 7.4 (#540).

1742+

1743+ * Don't generate an empty H1 after hrule slide breaks.

1744+ We now use a slide-level header with contents `[Str "\0"]` to mark

1745+ an hrule break. This avoids creation of an empty H1 in these

1746+ contexts. Closes #484.

1747+

1748+ * Docbook reader: Added support for "bold" emphasis. Thanks to mb21.

1749+

1750+ * In make_osx_package.sh, ensure citeproc-hs is built with the

1751+ embed_data_files flag.

1752+

1753+ * MediaWiki writer: Avoid extra blank lines after sublists (Gavin Beatty).

1754+

1755+ * ConTeXt writer: Don't escape `&`, `^`, `<`, `>`, `_`,

1756+ simplified escapes for `}` and `{` to `\{` and `\}` (Aditya Mahajan).

1757+

1758+ * Fixed handling of absolute URLs in CSS imports with `--self-contained`.

1759+ Closes #535.

1760+

1761+ * Added webm to mime types. Closes #543.

1762+

1763+ * Added some missing exports and tests to the cabal file

1764+ (Alexander V Vershilov).

1765+

1766+ * Compile with `-rtsopts` and `-threaded` by default.

1767+

1768+pandoc (1.9.4.1)

1769+

1770+ * Markdown reader: Added `cf.` and `cp.` to list of likely abbreviations.

1771+

1772+ * LaTeX template: Added `linkcolor`, `urlcolor` and `links-as-notes`

1773+ variables. Make TOC links black.

1774+

1775+ * LaTeX template improvements.

1776+

1777+ + Don't print date unless one is given explicitly in the document.

1778+ + Simplified templates.

1779+ + Use fontenc [T1] by default, and lmodern.

1780+ + Use microtype if available.

1781+

1782+ * Biblio:

1783+

1784+ + Add comma to beginning of bare suffix, e.g. `@item1 [50]`.

1785+ Motivation: `@item1 [50]` should be as close as possible to

1786+ `[@item1, 50]`.

1787+ + Added workaround for a bug in citeproc-hs 0.3.4 that causes footnotes

1788+ beginning with a citation to be empty. Closes #531.

1789+

1790+ * Fixed documentation on mixed lists. Closes #533.

1791+

1792+pandoc (1.9.4)

1793+

1794+ * Simplified `Text.Pandoc.Biblio` and fixed bugs with citations inside

1795+ footnotes and captions. We now handle note citations by inserting

1796+ footnotes during initial citation processing, and doing a separate

1797+ pass later to remove notes inside notes.

1798+

1799+ * Added 'zenburn' highlight style from highlighting-kate.

1800+

1801+ * Added Slideous writer. Slideous is an HTML + javascript slide show

1802+ format, similar to Slidy, but works with IE 7. (Jonas Smedegaard)

1803+

1804+ * LaTeX writer:

1805+

1806+ + Ensure we don't have extra blank lines at ends of cells.

1807+ This can cause LaTeX errors, as they are interpreted as new paragraphs.

1808+ + More consistent interblock spacing.

1809+ + Require highlighting-kate >= 0.5.1, for proper highlighted inline

1810+ code in LaTeX. Closes #527.

1811+ + Ensure that a Verbatim at the end of a footnote is followed by

1812+ a newline. (Fixes a regression in the previous version.)

1813+ + In default template, use black for internal links and TOC.

1814+ Added commented-out code to use footnotes for links, as would

1815+ be suitable in print output.

1816+

1817+ * Beamer writer: When `--incremental` is used, lists inside

1818+ a block quote should appear all at once. (This makes Beamer

1819+ output consistent with the HTML slide show formats.)

1820+

1821+ * ConTeXt writer:

1822+

1823+ + Escape `%` as `\letterpercent{}` not `\letterpercent `,

1824+ to avoid gobbling spaces after the `%` sign.

1825+ + Ensure space after `\stopformula`.

1826+

1827+ * Markdown writer:

1828+

1829+ + Use `:` form instead of `~` in definition lists, for better

1830+ compatibility with other markdown implementations.

1831+ + Don't wrap the term, because it breaks definition lists.

1832+ + Use a nonzero space to prevent false recognition

1833+ of list marker in ordered lists. Closes #516.

1834+

1835+ * Org writer: Add space before language name. Closes #523.

1836+

1837+ * Docx writer: Simplified bullet characters so they work properly

1838+ with Word 2007. Closes #520.

1839+

1840+ * LaTeX reader: Support `\centerline`.

1841+

1842+ * RST reader: handle figures. Closes #522.

1843+

1844+ * Textile reader: fix for `<notextile>` and `==`. Closes #517.

1845+ (Paul Rivier)

1846+

1847+pandoc (1.9.3)

1848+

1849+ * Fixed bug in `fromEntities`. The previous version would turn

1850+ `hi & low you know;` into `hi &`.

1851+

1852+ * HTML reader:

1853+

1854+ + Don't skip nonbreaking spaces.

1855+ Previously a paragraph containing just `&nbsp;` would be rendered

1856+ as an empty paragraph. Thanks to Paul Vorbach for pointing out the bug.

1857+ + Support `<col>` and `<caption>` in tables. Closes #486.

1858+

1859+ * Markdown reader:

1860+

1861+ + Don't recognize references inside delimited code blocks.

1862+ + Allow list items to begin with lists.

1863+

1864+ * Added basic docbook reader (John MacFarlane and Mauro Bieg).

1865+

1866+ * LaTeX reader:

1867+

1868+ + Handle `\bgroup`, `\egroup`, `\begingroup`, `\endgroup`.

1869+ + Control sequences can't be followed by a letter.

1870+ This fixes a bug where `\begingroup` was parsed as `\begin`

1871+ followed by `group`.

1872+ + Parse 'dimension' arguments to unknown commands. e.g. `\parindent0pt`

1873+ + Make `\label` and `\ref` sensitive to `--parse-raw`.

1874+ If `--parse-raw` is selected, these will be parsed as raw latex

1875+ inlines, rather than bracketed text.

1876+ + Don't crash on unknown block commands (like `\vspace{10pt}`)

1877+ inside `\author`; just skip them. Closes #505.

1878+

1879+ * Textile reader:

1880+

1881+ + Implemented literal escapes with `==` and `<notextile>`. Closes #473.

1882+ + Added support for LaTeX blocks and inlines (Paul Rivier).

1883+ + Better conformance to RedCloth inline parsing (Paul Rivier).

1884+ + Parse '+text+' as emphasized (should be underlined, but this

1885+ is better than leaving literal plus characters in the output.

1886+

1887+ * Docx writer: Fixed multi-paragraph list items. Previously they each

1888+ got a list marker. Closes #457.

1889+

1890+ * LaTeX writer:

1891+

1892+ + Added `--no-tex-ligatures` option to avoid replacing

1893+ quotation marks and dashes with TeX ligatures.

1894+ + Use `fixltx2e` package to provide '\textsubscript'.

1895+ + Improve spacing around LaTeX block environments:

1896+ quote, verbatim, itemize, description, enumerate.

1897+ Closes #502.

1898+ + Use blue instead of pink for URL links in latex/pdf output.

1899+

1900+ * ConTeXt writer: Fixed escaping of `%`.

1901+ In text, `%` needs to be escaped as `\letterpercent`, not `\%`

1902+ Inside URLs, `%` needs to be escaped as `\%`

1903+ Thanks to jmarca and adityam for the fix. Closes #492.

1904+

1905+ * Texinfo writer: Escape special characters in node titles.

1906+ This fixes a problem pointed out by Joost Kremers. Pandoc used

1907+ to escape an '@' in a chapter title, but not in the corresponding

1908+ node title, leading to invalid texinfo.

1909+

1910+ * Fixed document encoding in texinfo template.

1911+ Resolves Debian Bug #667816.

1912+

1913+ * Markdown writer:

1914+

1915+ + Don't force delimited code blocks to be flush left.

1916+ Fixes bug with delimited code blocks inside lists etc.

1917+ + Escape `<` and `$`.

1918+

1919+ * LaTeX writer: Use `\hyperref[ident]{text}` for internal links.

1920+ Previously we used `\href{\#ident}{text}`, which didn't work on

1921+ all systems. Thanks to Dirk Laurie.

1922+

1923+ * RST writer: Don't wrap link references. Closes #487.

1924+

1925+ * Updated to use latest versions of blaze-html, mtl.

1926+

1927+

1928+pandoc (1.9.2)

1929+

1930+ * LaTeX reader:

1931+

1932+ + Made `lstlisting` work as a proper verbatim environment.

1933+ + Fixed bug parsing LaTeX tables with one column.

1934+

1935+ * LaTeX writer:

1936+

1937+ + Use `{}` around `ctable` caption, so that formatting can be used.

1938+ + Don't require eurosym package unless document has a €.

1939+

1940+ * LaTeX template: Added variables for `geometry`, `romanfont`,

1941+ `sansfont`, `mathfont`, `mainfont` so users can more easily

1942+ customize fonts.

1943+

1944+ * PDF writer:

1945+

1946+ + Run latex engine at least two times, to ensure

1947+ that PDFs will have hyperlinked bookmarks.

1948+ + Added PDF metadata (title,author) in LaTeX standalone + PDF output.

1949+

1950+ * Texinfo writer: retain directories in image paths. (Peter Wang)

1951+

1952+ * RST writer: Better handling of inline formatting, in accord

1953+ with docutils' "inline markup recognition rules" (though we don't

1954+ implement the unicode rules fully). Now `hi*there*hi` gets

1955+ rendered properly as `hi\ *there*\ hi`, and unnecessary

1956+ `\ ` are avoided around `:math:`, `:sub:`, `:sup:`.

1957+

1958+ * RST reader:

1959+

1960+ + Parse `\ ` as null, not escaped space.

1961+ + Allow `` :math:`...` `` even when not followed by blank

1962+ or `\`. This does not implement the complex rule docutils follows,

1963+ but it should be good enough for most purposes.

1964+ + Add support for the rST default-role directive. (Greg Maslov)

1965+

1966+ * Text.Pandoc.Parsing: Added `stateRstDefaultRole` field to `ParserState`.

1967+ (Greg Maslov)

1968+

1969+ * Markdown reader: Properly handle citations nested in other inline

1970+ elements.

1971+

1972+ * Markdown writer: don't replace empty alt in image with "image".

1973+

1974+ * DZSlides: Updated template.html and styles in default template.

1975+ Removed bizarre CSS for `q` in dzslides template.

1976+

1977+ * Avoid repeated `id` attribute in section and header in HTML slides.

1978+

1979+ * README improvements: new instructions on internal links,

1980+ removed misleading note on reST math.

1981+

1982+ * Build system:

1983+

1984+ + Fixed Windows installer so that dzslides works.

1985+ + Removed stripansi.sh.

1986+ + Added .travis.yml for Travis continuous integration support..

1987+ + Fixed upper bound for zlib (Sergei Trofimovich).

1988+ + Fixed upper bound for test-framework.

1989+ + Updated haddocks for haddock-2.10 (Sergei Trofimovich).

1990+

1991+pandoc (1.9.1.2)

1992+

1993+ * Added `beamer+lhs` as output format.

1994+

1995+ * Don't escape `<` in `<style>` tags with `--self-contained`.

1996+ This fixes a bug which prevented highlighting from working

1997+ when using `--self-contained`.

1998+

1999+ * PDF: run latex engine three times if `--toc` specified.

2000+ This fixes page numbers in the table of contents.

2001+

2002+ * Docx writer: Added TableNormal style to tables.

2003+

2004+ * LaTeX math environment fixes. `aligned` is now used instead of

2005+ the nonexistent `aligned*`. `multline` instead of the nonexistent

2006+ `multiline`.

2007+

2008+ * LaTeX writer: Use `\textasciitilde` for literal `~`.

2009+

2010+ * HTML writer: Don't escape contents of EQ tags with --gladtex.

2011+ This fixes a regression from 1.8.

2012+

2013+ * Use `<q>` tags for Quoted items for HTML5 output.

2014+ The quote style can be changed by modifying the template

2015+ or including a css file. A default quote style is included.

2016+

2017+ * LaTeX reader: Fixed accents (\~{a}, `\c{c}`).

2018+ Correctly handle \^{}. Support "minted" as a LaTeX verbatim block.

2019+

2020+ * Updated LaTeX template for better language support.

2021+ Use `polyglossia` instead of `babel` with xetex.

2022+ Set `lang` as documentclass option.

2023+ `\setmainlanguage` will use the last of a comma-separated

2024+ list of languages. Thanks to François Gannaz.

2025+

2026+ * Fixed default LaTeX template so `\euro` and `€` work. The

2027+ `eurosym` package is needed if you are using pdflatex.

2028+

2029+ * Fixed escaping of period in man writer (thanks to Michael Thompson).

2030+

2031+ * Fixed list label positions in beamer.

2032+

2033+ * Set `mainlang` variable in context writer.

2034+ This parallels behavior of latex writer. `mainlang` is the last

2035+ of a comma-separated list of languages in lang.

2036+

2037+ * EPUB language metadat: convert e.g. `en_US` from locale to `en-US`.

2038+

2039+ * Changed `-V` so that you can specify a key without a value.

2040+ Such keys get the value `true`.

2041+

2042+ * Fixed permissions on installed man pages - thanks Magnus Therning.

2043+

2044+ * Windows installer: require XP or higher. The installer is

2045+ now compiled on a Windows 7 machine, which fixes a problem

2046+ using citation functions on Windows 7.

2047+

2048+ * OSX package: Check for 64-bit Intel CPU before installing.

2049+

2050+pandoc (1.9.1.1)

2051+

2052+ * Better handling of raw latex environments in markdown. Now

2053+

2054+ \begin{equation}

2055+ a_1

2056+ \end{equation}

2057+

2058+ turns into a raw latex block as expected.

2059+

2060+ * Improvements to LaTeX reader:

2061+

2062+ + Skip options after block commands.

2063+ + Correctly handle `{\\}` in braced.

2064+ + Added a needed 'try'.

2065+ + Citations: add `, ` to suffix if it doesn't start with space or

2066+ punctuation. Otherwise we get no space between the year and the

2067+ suffix in author-date styles.

2068+

2069+ * Added two needed data files for S5. This fixes a problem with

2070+ `pandoc -t s5 --self-contained`. Also removed `slides.min.js`,

2071+ which was no longer being used.

2072+

2073+ * Fixed some minor problems in `reference.docx`:

2074+ name on "Date" style, `xCs` instead of `xIs`.

2075+

2076+ * Fixed a problem creating docx files using a reference docx

2077+ modified using Word. The problem seems to be that Word

2078+ modifies `_rels/.rels`, changing the Type of the Relationship to

2079+ `docProps/core.xml`. Pandoc now changes this back to the correct

2080+ value if it has been altered, fixing the problem.

2081+

2082+ * Fixed html5 template so it works properly with highlighting.

2083+

2084+pandoc (1.9.1)

2085+

2086+ * LaTeX reader:

2087+

2088+ + Fixed regression in 1.9; properly handle escaped $ in latex math.

2089+ + Put LaTeX verse environments in blockquotes.

2090+

2091+ * Markdown reader:

2092+

2093+ + Limit nesting of strong/emph. This avoids exponential lookahead

2094+ in parasitic cases, like `a**a*a**a*a**a*a**a*a**a*a**a*a**a*a**`.

2095+ + Improved attributes syntax (inn code blocks/spans):

2096+ (1) Attributes can contain line breaks. (2) Values in key-value

2097+ attributes can be surrounded by either double or single quotes, or

2098+ left unquoted if they contain no spaces.

2099+

2100+ * Don't wrap headers in markdown or RST writers.

2101+

2102+ * Added `stateMaxNestingLevel` to `ParserState`.

2103+ We set this to 6, so you can still have `Emph` inside `Emph`,

2104+ just not indefinitely.

2105+

2106+ * More efficient implementation of `nowrap` in `Text.Pandoc.Pretty`.

2107+

2108+ * `Text.Pandoc.PDF`: Only run latex twice if `\tableofcontents`

2109+ is present.

2110+

2111+ * Require highlighting-kate >= 0.5.0.2, texmath >= 0.6.0.2.

2112+

2113+pandoc (1.9.0.5)

2114+

2115+ * Changed cabal file so that build-depends for the test program

2116+ are not required unless the tests flag is used.

2117+

2118+ * LaTeX writer: insert `{}` between adjacent hyphens so they don't

2119+ form ligatures (dashes) in code spans.

2120+

2121+pandoc (1.9.0.4)

2122+

2123+ * Raised version bound on test-framework to avoid problems

2124+ compiling tests on GHC 7.4.1.

2125+

2126+ * LaTeX reader: Use raw LaTeX as fallback inline text for Cites,

2127+ so citations don't just disappear unless you process with

2128+ citeproc. Ignore `\bibliographystyle`, `\nocite`.

2129+

2130+ * Simplified tex2pdf; it will always run latex twice to

2131+ resolve table of contents and hyperrefs.

2132+

2133+pandoc (1.9.0.3)

2134+

2135+ * Require Cabal >= 1.10.

2136+ * Tweaked cabal file to meet Cabal 1.10 requirements.

2137+

2138+pandoc (1.9.0.2)

2139+

2140+ * Allow build with json 0.4 or 0.5. Otherwise we can't build with

2141+ ghc 6.12.

2142+

2143+pandoc (1.9)

2144+

2145+ [new features]

2146+

2147+ * Added a Microsoft Word `docx` writer. The writer includes support

2148+ for highlighted code and for math (which is converted from TeX to OMML,

2149+ Office's native math markup language, using texmath's new OMML module).

2150+ A new option `--reference-docx` allows the user to customize the

2151+ styles.

2152+

2153+ * Added an `asciidoc` writer (<http://www.methods.co.nz/asciidoc/>).

2154+

2155+ * Better support for slide shows:

2156+

2157+ + Added a `dzslides` writer. DZSlides is a lightweight HTML5/javascript

2158+ slide show format due to Paul Rouget (<http://paulrouget.com/dzslides/>).

2159+

2160+ + Added a LaTeX `beamer` writer. Beamer is a LaTeX package for creating

2161+ slide presentations.

2162+

2163+ + New, flexible rules for dividing documents into sections and slides

2164+ (see the "Structuring the slide show" in the User's Guide). These

2165+ are backward-compatible with the old rules, but they allow slide

2166+ shows to be organized into sections and subsections containing

2167+ multiple slides.

2168+

2169+ + A new `--slide-level` option allows users to override defaults

2170+ and select a slide level below the first header level with content.

2171+

2172+ * A new `--self-contained` option produces HTML output that does not

2173+ depend on an internet connection or the presence of any external

2174+ files. Linked images, CSS, and javascript is downloaded (or fetched

2175+ locally) and encoded in `data:` URIs. This is useful for making portable

2176+ `HTML slide shows. The --offline` option has been deprecated and is now

2177+ `treated as a synonym or --self-contained`.

2178+

2179+ * Support for PDF output:

2180+

2181+ + Removed the old `markdown2pdf`.

2182+ + `pandoc` can now create PDFs (assuming you have latex and a set of

2183+ appropriate packages installed): just specify an output file with the

2184+ `.pdf` extension.

2185+ + A new option `--latex-engine` allows you to specify `pdflatex`,

2186+ `xelatex`, or `lualatex` as the processor.

2187+

2188+ * Highlighting changes:

2189+

2190+ + Syntax highlighting is now a standard feature; the `highlighting`

2191+ flag is no longer needed when compiling.

2192+ + A new `--no-highlight` option allows highlighting to be disabled.

2193+ + Highlighting now works in `docx`, `latex`, and `epub`, as well as

2194+ `html`, `html5`, `dzslides`, `s5`, and `slidy`.

2195+ + A new `--highlight-style` option selects between various highlighting

2196+ color themes.

2197+

2198+ * Internal links to sections now work in ConTeXt and LaTeX as well as HTML.

2199+

2200+ * LaTeX `\include` and `\usepackage` commands are now processed,

2201+ provided the files are in the working directory.

2202+

2203+ * EPUB improvements:

2204+

2205+ + Internal and external links now work in EPUB.

2206+ + Raw HTML is allowed.

2207+ + New `--epub-embed-font` option.

2208+ + Customizable templates for EPUB pages offer more control over

2209+ formatting: `epub-page.html`, `epub-coverimage.html`,

2210+ `epub-titlepage.html`.

2211+

2212+ * `--mathml` now works with DocBook.

2213+

2214+ * Added support for math in RST reader and writer. Inline math uses the

2215+ `` :math:`...` `` construct. Display math uses

2216+

2217+ .. math:: ...

2218+

2219+ or if the math is multiline,

2220+

2221+ .. math::

2222+

2223+ ...

2224+

2225+ These constructions are now supported now by `rst2latex.py`.

2226+

2227+ * Github syntax for fenced code blocks is supported in pandoc's

2228+ markdown. You can now write

2229+

2230+ ```ruby

2231+ x = 2

2232+ ```

2233+

2234+ instead of

2235+

2236+ ~~~ {.ruby}

2237+ x = 2

2238+ ~~~~

2239+

2240+ * Easier scripting: a new `toJsonFilter` function makes it easier to

2241+ write Haskell scripts to manipulate the Pandoc AST.

2242+

2243+ [behavior changes]

2244+

2245+ * Fixed parsing of consecutive lists in markdown.

2246+ Pandoc previously behaved like Markdown.pl for consecutive

2247+ lists of different styles. Thus, the following would be parsed

2248+ as a single ordered list, rather than an ordered list followed

2249+ by an unordered list:

2250+

2251+ 1. one

2252+ 2. two

2253+

2254+ - one

2255+ - two

2256+

2257+ This change makes pandoc behave more sensibly, parsing this as

2258+ two lists. Any change in list type (ordered/unordered) or in

2259+ list number style will trigger a new list. Thus, the following

2260+ will also be parsed as two lists:

2261+

2262+ 1. one

2263+ 2. two

2264+

2265+ a. one

2266+ b. two

2267+

2268+ Since we regard this as a bug in Markdown.pl, and not something

2269+ anyone would ever rely on, we do not preserve the old behavior

2270+ even when `--strict` is selected.

2271+

2272+ * Dashes work differently with `--smart`: `---` is always em-dash,

2273+ and `--` is always en-dash. Pandoc no longer tries to guess when

2274+ `-` should be en-dash. *Note:* This may change how existing documents

2275+ look when processed with pandoc. A new option, `--old-dashes`,

2276+ is provided for legacy documents.

2277+

2278+ * The markdown writer now uses setext headers for levels 1-2.

2279+ The old behavior (ATX headers for all levels) can be restored

2280+ using the new `--atx-headers` option.

2281+

2282+ * Links are now allowed in markdown image captions. They are also

2283+ allowed in links, but will appear there as regular text. So,

2284+

2285+ [link with [link](/url)](/url)

2286+

2287+ will turn into

2288+

2289+ <p><a href="/url">link with link</a></p>

2290+

2291+ * Improved handling of citations using `citeproc-hs-0.3.4`.

2292+ Added `--citation-abbreviations` option.

2293+

2294+ * Citation keys can no longer end with a punctuation character.

2295+ This means that `@item1.` will be parsed as a citation with key

2296+ 'item1', followed by a period, instead of a citation with key

2297+ 'item1.', as was the case previously.

2298+

2299+ * In HTML output, citations are now put in a span with class `citation`.

2300+

2301+ * The markdown reader now recognizes DocBook block and inline tags.

2302+ It was always possible to include raw DocBook tags in a markdown

2303+ document, but now pandoc will be able to distinguish block from

2304+ inline tags and behave accordingly. Thus, for example,

2305+

2306+ <sidebar>

2307+ hello

2308+ </sidebar>

2309+

2310+ will not be wrapped in `<para>` tags.

2311+

2312+ * The LaTeX parser has been completely rewritten; it is now much more

2313+ accurate, robust, and extensible. However, there are two important

2314+ changes in how it treats unknown LaTeX. (1) Previously, unknown

2315+ environments became BlockQuote elements; now, they are treated

2316+ as "transparent", so `\begin{unknown}xyz\end{unknown}` is the

2317+ same as `xyz`. (2) Previously, arguments of unknown commands

2318+ were passed through with their braces; now the braces are stripped

2319+ off.

2320+

2321+ * `--smart` is no longer selected automatically with `man` output.

2322+

2323+ * The deprecated `--xetex` option has been removed.

2324+

2325+ * The `--html5`/`-5` option has been deprecated. Use `-t html5`

2326+ instead. `html5` and `html5+lhs` are now separate output formats.

2327+

2328+ * Single quotes are no longer escaped in HTML output. They do not

2329+ need to be escaped outside of attributes.

2330+

2331+ * Pandoc will no longer transform leading newlines in code

2332+ blocks to `<br/>` tags.

2333+

2334+ * The ODT writer now sizes images appropriately, using the image

2335+ size and DPI information embedded in the image.

2336+

2337+ * `--standalone` is once again implicitly for a non-text output format

2338+ (ODT, EPUB). You can again do `pandoc test.txt -o test.odt`

2339+ and get a standalone ODT file.

2340+

2341+ * The Docbook writer now uses `<sect1>`, `<sect2>`, etc. instead of

2342+ `<section>`.

2343+

2344+ * The HTML writer now uses `<del>` for strikeout.

2345+

2346+ * In HTML output with `--section-divs`, the classes `section` and

2347+ `level[1,2,..6]` are put on the `div` tags so they can be styled.

2348+ In HTML 5 output with `--section-divs`, the classes

2349+ `level[1,2,...6]` are put on `section` tags.

2350+

2351+ * EPUB writer changes:

2352+

2353+ + The `lang` variable now sets the language

2354+ in the metadata (if it is not set, we default to the locale).

2355+ + EPUB: UTF-8 is used rather than decimal entities.

2356+

2357+ * Added `titleslide` class to title slide in S5 template.

2358+

2359+ * In HTML, EPUB, and docx metadata, the date is normalized into

2360+ YYYY-MM-DD format if possible. (This is required for validation.)

2361+

2362+ * Attributes in highlighted code blocks are now preserved in HTML.

2363+ The container element will have the classes, id, and key-value attributes

2364+ you specified in the delimited code block. Previously these were stripped

2365+ off.

2366+

2367+ * The reference backlink in the HTML writer no longer has a special

2368+ `footnoteBacklink` class.

2369+

2370+ * The HTML template has been split into `html` and `html5` templates.

2371+

2372+ * Author and date are treated more consistently in HTML templates.

2373+ Authors are now `<h2>`, date `<h3>`.

2374+

2375+ * URLs are hyphenated in the ConTeXt writer (B. Scott Michel).

2376+

2377+ * In `Text.Pandoc.Builder`, `+++` has been replaced by `<>`.

2378+

2379+ [bug fixes]

2380+

2381+ * Better support for combining characters and East Asian wide characters

2382+ in markdown and reST.

2383+

2384+ * Better handling of single quotes with `--smart`.

2385+ Previously `D'oh l'*aide*` would be parsed with left and right single

2386+ quotes instead of apostrophes. This kind of error is now fixed.

2387+

2388+ * Highlighting: Use `reads` instead of `read` for better error handling.

2389+ Fixes crash on `startNum="abc"`.

2390+

2391+ * Added blank comment after directives in rst template.

2392+

2393+ * Unescape entities in citation `refId`. The `refId`s coming

2394+ from citeproc contain XML numeric entities, and these don't match with the

2395+ citation keys parsed by pandoc. Solution is to unescape them.

2396+

2397+ * HTML reader: Fixed bug parsing tables with both thead and tbody.

2398+

2399+ * Markdown reader:

2400+

2401+ + Better handling of escapes in link URLs and titles.

2402+ + Fixed backslash escapes in reference links.

2403+ + Fixed bug in table/hrule parsing, by checking that the top

2404+ line of a table is not followed by a blank line. This bug caused

2405+ slowdowns on some files with hrules and tables, as pandoc tried to

2406+ interpret the hrules as the tops of multiline tables.

2407+ + Fixed bug in code block attribute parser. Previously the ID attribute

2408+ got lost if it didn't come first. Now attributes can come in any order.

2409+

2410+ * RST reader: allow footnotes followed by newline without space characters.

2411+

2412+ * LaTeX reader:

2413+

2414+ + Ignore empty groups {}, { }.

2415+ + LaTeX reader: Handle \@.

2416+ + LaTeX reader: Don't crash on commands like `\itemsep`.

2417+ + LaTeX reader: Better handling of letter environments.

2418+

2419+ * RST writer: Fixed bug involving empty table cells. isSimple was being

2420+ calculated in a way that assumed there were no non-empty cells.

2421+

2422+ * ConTeXt writer:

2423+

2424+ + Made `--toc` work even without `--number-sections`.

2425+ + Escape # in link URLs.

2426+ + Use buffering for footnotes containing code blocks.

2427+ + Changed 'descr' to 'description', fixed alignment.

2428+

2429+ * LaTeX writer:

2430+

2431+ + Escape euro character.

2432+ + Don't escape ~ inside href{...}.

2433+ + Escape # in href URLs.

2434+ + Improved detection of book classes. We now check the

2435+ `documentclass` variable, and if that is not set, we look through

2436+ the template itself. Also, we have added the KOMA classes scrreprt

2437+ and scrbook. You can now make a book using

2438+ `pandoc -V documentclass:book mybook.txt -o mybook.pdf`

2439+ + LHS files now set the "listings" variable, so that the definition

2440+ of the `code` environment will be included in the template.

2441+ + Links are colored blue by default (this can be changed by

2442+ modifying `hyperref` settings in the template).

2443+ + Added `lang` variable to LaTeX template.

2444+

2445+ * HTML writer:

2446+

2447+ + Fixed bug in HTML template with html5 and mathml.

2448+ + Don't use self-closing img, br, hr tags for HTML5.

2449+ + Use `<section>` for footnotes if HTML5.

2450+ + Update HTML templates to use Content-Style-Type meta tag.

2451+ + Use separate variables for meta-date, meta-author.

2452+ This makes footnotes work in author and date fields.

2453+ + Use 'vertical-align:middle' in WebTeX math for better alignment.

2454+

2455+ * S5/slidy writer: Make footnotes appear on separate slide at end.

2456+

2457+ * MIME: Added 'layout-cache' to getMimeType. This ensures that the

2458+ META-INF/manifest.xml for ODT files will have everything it needs, so

2459+ that ODT files modified by LibreOffice can be used as `--reference-odt`.

2460+

2461+ * `Text.Pandoc.Templates`: Return empty string for json template.

2462+

2463+ * `Text.Pandoc.Biblio`:

2464+

2465+ + Expand citations recursively inside nested inlines.

2466+ + Treat `\160` as space when parsing locator and suffix.

2467+ This fixes a bug with "p. 33" when `--smart` is used. Previously

2468+ the whole "p. 33" would be included in the suffix, with no locator.

2469+ + Put whole author-in-text citation in a Cite. Previously just the

2470+ date and other info went in the Cite.

2471+ + Don't add comma+space to prefix if it ends in punctuation.

2472+

2473+ * Updated chicago-author-date.csl. The old version did not work

2474+ properly for edited volumes with no author.

2475+

2476+ * EPUB writer:

2477+

2478+ + Add date to EPUB titlepage and metadata.

2479+ + Added TOC identifier in EPUB page template.

2480+ + Don't generate superfluous file `cover-image.jpg`.

2481+

2482+ [under the hood improvements]

2483+

2484+ * Modified `make_osx_package.sh` to use cabal-dev.

2485+ Items are no longer installed as root.

2486+ Man pages are zipped and given proper permissions.

2487+

2488+ * Modified windows installer generater to use cabal-dev.

2489+

2490+ * Setup: Making man pages now works with cabal-dev (at least on OSX). In

2491+ Setup.hs we now invoke 'runghc' in a way that points it to the correct

2492+ package databases, instead of always falling back to the default user

2493+ package db.

2494+

2495+ * Updated to work with GHC 7.4.1.

2496+

2497+ * Removed dependency on old-time.

2498+

2499+ * Removed dependency on dlist.

2500+

2501+ * New slidy directory for "self-contained."

2502+

2503+ * TeXMath writer: Use unicode thin spaces for thin spaces.

2504+

2505+ * Markdown citations: don't strip off initial space in locator.

2506+

2507+ [API changes]

2508+

2509+ * Removed `Apostrophe`, `EmDash`, `EnDash`, and `Ellipses`

2510+ from the native `Inline` type in pandoc-types. Now we use `Str`

2511+ elements with unicode.

2512+

2513+ * Improvements to `Text.Pandoc.Builder`:

2514+

2515+ + `Inlines` and `Blocks` are now newtypes (not synonyms for

2516+ sequences).

2517+ + Instances are defined for `IsString`, `Show`, `Read`, `Monoid`,

2518+ and a new `Listable` class, which allows these to be manipulated

2519+ to some extent like lists. Monoid append includes automatic

2520+ normalization.

2521+ + `+++` has been replaced by `<>` (mappend).

2522+

2523+ * Use blaze-html instead of xhtml for HTML generation.

2524+ This changes the type of `writeHtml`.

2525+

2526+ * `Text.Pandoc.Shared`:

2527+

2528+ + Added `warn` and `err`.

2529+ + Removed `unescapeURI`, modified `escapeURI`.

2530+ (See under [behavior changes], above.)

2531+

2532+ * Changes in URI escaping: Previously the readers escaped URIs by

2533+ converting unicode characters to octets and then percent encoding.

2534+ Now unicode characters are left as they are, and `escapeURI` only

2535+ percent-encodes space characters. This gives more readable

2536+ URIs, and works well with modern user agents. URIs are no longer unescaped

2537+ at all on conversion to `markdown`, `asciidoc`, `rst`, `org`.

2538+

2539+ * New module `Text.Pandoc.SelfContained`.

2540+

2541+ * New module `Text.Pandoc.Docx`.

2542+

2543+ * New module `Text.Pandoc.PDF`.

2544+

2545+ * Added `writerBeamer` to `WriterOptions`.

2546+

2547+ * Added `normalizeDate` to `Text.Pandoc.Shared`.

2548+

2549+ * Added `splitStringWithIndices` in `Text.Pandoc.Shared`.

2550+ This is like `splitWithIndices`, but it is sensitive to distinctions

2551+ between wide, combining, and regular characters.

2552+

2553+ * `Text.Pandoc.Pretty`:

2554+

2555+ + Added `chomp` combinator.

2556+ + Added `beforeNonBreak` combinator. This allows you to include

2557+ something conditionally on it being before a nonblank.

2558+ Used for RST inline math.

2559+ + Added `charWidth` function. All characters marked W or F in the unicode

2560+ spec EastAsianWidth.txt get width 2.

2561+ + Added `realLength`, based on `charWidth`. `realLength` is now

2562+ used in calculating offsets.

2563+

2564+ * New module `Text.Pandoc.Slides`, for common functions for breaking

2565+ a document into slides.

2566+

2567+ * Removed `Text.Pandoc.S5`, which is no longer needed.

2568+

2569+ * Removed `Text.Pandoc.CharacterReferences`. Moved

2570+ `characterReference` to `Text.Pandoc.Parsing`.

2571+ `decodeCharacterReferences` is replaced by `fromEntities`

2572+ in `Text.Pandoc.XML`.

2573+

2574+ * Added `Text.Pandoc.ImageSize`. This is intened for use

2575+ in `docx` and `odt` writers, so the size and dpi of images

2576+ can be calculated.

2577+

2578+ * Removed `writerAscii` in `WriterOptions`.

2579+

2580+ * Added `writerHighlight` to `WriterOptions`.

2581+

2582+ * Added `DZSlides` to `HTMLSlideVariant`.

2583+

2584+ * `writeEPUB` has a new argument for font files to embed.

2585+

2586+ * Added `stateLastStrPos` to `ParserState`. This lets us keep track

2587+ of whether we're parsing the position immediately after a regular

2588+ (non-space, non-symbol) string, which is useful for distinguishing

2589+ apostrophes from single quote starts.

2590+

2591+ * `Text.Pandoc.Parsing`:

2592+

2593+ + `escaped` now returns a `Char`.

2594+ + Removed `charsInBalanced'`, added a character parser as

2595+ a parameter of `charsInBalanced`. This is needed for

2596+ proper handling of escapes, etc.

2597+ + Added `withRaw`.

2598+

2599+ * Added `toEntities` to `Text.Pandoc.XML`.

2600+

2601+ * `Text.Pandoc.Readers.LaTeX`:

2602+

2603+ + Export `handleIncludes`.

2604+ + Export `rawLaTeXBlock` instead of `rawLaTeXEnvironment'`.

2605+

2606+ * Added `ToJsonFilter` class and `toJsonFilter` function to

2607+ `Text.Pandoc`, deprecating the old `jsonFilter` function.

2608+

2609+ * `Text.Pandoc.Highlighting`:

2610+

2611+ + Removed `highlightHtml`, `defaultHighlightingCss`.

2612+ + Export `formatLaTeXInline`, `formatLaTeXBlock`, and `highlight`, plus

2613+ key functions from highlighting-kate.

2614+ + Changed types of highlighting function. `highlight` returns a

2615+ `Maybe`, not an `Either`.

2616+

2617+pandoc (1.8.2.1)

2618+

2619+ * Relaxed cabal consntraints for test-framework (S. Trofimovich).

2620+

2621+ * Relaxed cabal constraints for pandoc-types.

2622+

2623+ * Adjusted Arbitrary instance to help avoid timeouts in tests.

2624+

2625+ * Added `Tests.Writers.Markdown` to cabal file.

2626+

2627+pandoc (1.8.2)

2628+

2629+ * Added script to produce OS X package.

2630+

2631+ * Made `templates` directory a git submodule. This should make it

2632+ easier for people to revise their custom templates when the default

2633+ templates change.

2634+

2635+ * Changed template naming scheme: `FORMAT.template` -> `default.FORMAT`.

2636+ **Note:** If you have existing templates in `~/.pandoc/templates`, you

2637+ must rename them to conform to the new scheme!

2638+

2639+ * Fixed smart quotes bug, now handling `'...hi'` properly.

2640+

2641+ * RST reader:

2642+

2643+ + Partial support for labeled footnotes.

2644+ + Improved accuracy of `simpleReferenceName` parser.

2645+

2646+ * HTML reader:

2647+

2648+ + Substitute correct unicode characters for

2649+ characters in the 128..159 range, which are often found even in

2650+ HTML that purports to be UTF-8.

2651+

2652+ * LaTeX reader: Handle `\subtitle` command (a subtitle is added

2653+ to the title, after a colon and linebreak). Closes #280.

2654+

2655+ * Leaner `reference.odt`.

2656+

2657+ * Added unexported module `Text.Pandoc.MIME` for use in

2658+ the ODT writer.

2659+

2660+ * ODT writer: Construct `manifest.xml` based on archive contents.

2661+ This fixes a bug in ODTs containing images. Recent versions of

2662+ LibreOffice would reject these as corrupt, because `manifest.xml`

2663+ did not contain a reference to the image files.

2664+

2665+ * LaTeX writer:

2666+

2667+ + Make verbatim environments flush to avoid spurious

2668+ blank lines. Closes #277.

2669+ + Use `\texttt` and escapes insntead of `\verb!...!`, which

2670+ is too fragile (doesn't work in command arguments).

2671+ + Use `\enquote{}` for quotes if the template includes

2672+ the `csquotes` package. This provides better support for

2673+ local quoting styles. (Thanks to Andreas Wagner for the idea.)

2674+

2675+ * ConTeXt writer: Make `\starttyping`/`\stoptyping` flush with

2676+ margin, preventing spurious blank lines.

2677+

2678+ * Slidy writer:

2679+

2680+ + Use non-minimized version of `slidy.css` with `--offline`

2681+ option, so users can more easily edit it.

2682+ + Also fixed a bug in the CSS that prevented proper centering

2683+ of title (now reported and fixed upstream).

2684+

2685+ * S5 writer:

2686+

2687+ + Replaced `s5/default/slides.js.{comment,packed}` with

2688+ new compressed `s5/default/slides.min.js`.

2689+ + Use `data:` protocol to embed S5 CSS in `<link>` tags,

2690+ when `--offline` is specified. Using inline CSS didn't

2691+ work with Chrome or Safari. This fixes offline

2692+ S5 on those browsers.

2693+

2694+ * HTML writer: Removed English title on footnote backlinks.

2695+ This is incongrous in non-English documents.

2696+

2697+ * Docbook writer:

2698+

2699+ + Use CALS tables. (Some older docbook software does not work

2700+ well with XHTML tables.) Closes #77.

2701+ + Use `programlisting` tags (instead of `screen`) for code blocks.

2702+

2703+ * `markdown2pdf`:

2704+

2705+ + Calls latex with `-halt-on-error -interaction nonstopmode` instead

2706+ of `-interaction=batchmode`, which essentially just ignored errors,

2707+ leading to bad results. Better to know when something is wrong.

2708+ + Fixed issues with non-UTF-8 output of `pdflatex`.

2709+ + Better error reporting.

2710+

2711+ * `--mathjax` now takes an optional URL argument. If it is not

2712+ provided, pandoc links directly to the (secure) mathjax CDN,

2713+ as now recommended (thanks to dsanson).

2714+

2715+ * Deprecated `--xetex` option in `pandoc`. It is no longer needed,

2716+ since the LaTeX writer now produces a file that can be processed by

2717+ `latex`, `pdflatex`, `lualatex`, or `xelatex`.

2718+

2719+ * Introduced `--luatex` option to `markdown2pdf`. This causes `lualatex`

2720+ to be used to create the PDF.

2721+

2722+ * If a template specified with `--template` is not found, look for it

2723+ in `datadir`. Also, if no extension is provided, supply one based

2724+ on the writer. So now you can put your `special.latex` template in

2725+ `~/.pandoc/templates`, and use it from any directory via

2726+ `pandoc -t latex --template special`.

2727+

2728+ * Default template improvements:

2729+

2730+ + HTML: Display author and date after title.

2731+ + HTML: Made table of contents more customizable. The container

2732+ for the TOC is now in the template, so users can insert a header

2733+ or other styling. (Thanks to Bruce D'Arcus for the suggestion.)

2734+ + HTML, Slidy, S5: Enclose scripts in CDATA tags.

2735+ + Slidy, S5: Added `s5-url` and `slidy-url` variables, instead of

2736+ hard-coding. If you want to put your slidy files in the slidy

2737+ subdirectory, for example, you can do

2738+ `pandoc -t slidy -V slidy-url=slidy -s`.

2739+ + LaTeX: Use `\and` to separate authors in LaTeX documents (reader

2740+ & writer). Closes #279.

2741+ + LaTeX: Use different `hyperref` options for `xetex`, fixing

2742+ problems with unicode bookmarks (thanks to CircleCode).

2743+ + LaTeX: Removed `ucs` package, use `utf8` rather than `utf8x`

2744+ with `inputenc`. This covers fewer characters but is more

2745+ robust with other packages, and `ucs` is unmaintained. Users

2746+ who need better unicode support should use xelatex or lualatex.

2747+

2748+pandoc (1.8.1.2)

2749+

2750+ * Added `--epub-cover-image` option.

2751+

2752+ * Documented `--biblatex` and `--natbib` options.

2753+

2754+ * Allow `--section-divs` with slidy output. Resolves Issue #296.

2755+

2756+ * Disallow notes within notes in reST and markdown.

2757+ These previously caused infinite looping and stack overflows.

2758+ For example:

2759+

2760+ [^1]

2761+

2762+ [^1]: See [^1]

2763+

2764+ Note references are allowed in reST notes, so this isn't a full

2765+ implementation of reST. That can come later. For now we need to

2766+ prevent the stack overflows. Partially resolves Issue #297.

2767+

2768+ * EPUB writer: Allow non-plain math methods.

2769+

2770+ * Forbid ()s in citation item keys. Resolves Issue #304: problems with

2771+ `(@item1; @item2)` because the final paren was being parsed as part of

2772+ the item key.

2773+

2774+ * Changed URI parser so it doesn't include trailing punctuation.

2775+ So, in RST, `http://google.com.` should be parsed as a link followed by a

2776+ period. The parser is smart enough to recognize balanced parentheses, as

2777+ often occur in wikipedia links: `http://foo.bar/baz_(bam)`.

2778+

2779+ * Markdown+lhs reader: Require space after inverse bird tracks, so that

2780+ HTML tags can be used freely at the left margin of a markdown+lhs document.

2781+ Thanks to Conal Elliot for the suggestion.

2782+

2783+ * Markdown reader:

2784+

2785+ + Improved emph/strong parsing; fixes bug found by Perry Wagle.

2786+ + Fixed bug in footnote order (reported by CircleCode).

2787+

2788+ * RST reader:

2789+ + Fixed bug in in field lists with multi-line items at the

2790+ end of the list.

2791+ + Added parentheses to RST `specialChars`, so

2792+ `(http://google.com)` will be parsed as a link in parens.

2793+ Resolves Issue #291.

2794+ + Allow `|` followed by newline in RST line block.

2795+

2796+ * LaTeX reader:

2797+ + Support `\dots`.

2798+ + Gobble option & space after linebreak `\\[10pt]`.

2799+

2800+ * Textile reader:

2801+ + Make it possible to have colons after links. (qerub)

2802+ + Make it possible to have colons after links. (Christoffer Sawicki)

2803+

2804+ * HTML reader:

2805+ + Skip spaces after `<b>`, `<emph>`, etc.

2806+ + Handle tbody, thead in simple tables. Closes #274.

2807+ + Implicit `Para`s instead of `Plains` in some contexts.

2808+

2809+ * OpenDocument writer: Use special `First paragraph` style for

2810+ first paragraph after most non-paragraph blocks. This allows users to

2811+ specify e.g. that only paragraphs after the first paragraph of a block are

2812+ to be indented. Thanks to Andrea Rossato for the patch. Closes #20.

2813+

2814+ * LaTeX writer: use `deVerb` on table and picture captions.

2815+ Otherwise LaTeX complains about `\verb` inside command argument.

2816+ Thanks to bbanier for reporting the bug.

2817+

2818+ * Markdown writer: Insert HTML comment btw list and indented code block.

2819+ This prevents the code block from being interpreted as part of the list.

2820+

2821+ * EPUB writer: Add a meta element specify the cover.

2822+ Some EPUB e-readers, such as the Nook, require a meta element inside the

2823+ OPF metadata block to ensure the cover image is properly displayed.

2824+ (Kelsey Hightower)

2825+

2826+ * HTML writer: Use embed tag for images with non-image extensions.

2827+ (e.g. PDFs). Closes #264.

2828+

2829+ * LaTeX writer: Improved tables.

2830+

2831+ + More space between lines, top-align cells.

2832+ + Use ctable package, which allows footnotes and

2833+ provides additional options.

2834+ + Made cell alignments work in multiline tables.

2835+ + Closes #271, #272.

2836+

2837+ * Un-URI-escape image filenames in LaTeX, ConTeXt, RTF, Texinfo.

2838+ Also do this when copying image files into EPUBs and ODTs.

2839+ Closes #263.

2840+

2841+ * Changed to github issue tracker.

2842+

2843+ * Added failing emph/strong markdown test case due to Perry Wagle.

2844+

2845+ * Slidy improvements:

2846+ + Updated to use Slidy2.

2847+ + Fixed bug, unclosed div tag.

2848+ + Added `duration` variable in template.

2849+ Setting this activates the timer.

2850+ + Use 'titlepage' instead of 'cover' for title div.

2851+

2852+pandoc (1.8.1.1)

2853+

2854+ * `markdown2pdf`: Removed some debugging lines accidentally included

2855+ in the 1.8.1 release. With those lines, the temp directory is created

2856+ in the working directory, and it is not deleted. This fix restores

2857+ the original behavior.

2858+

2859+pandoc (1.8.1)

2860+

2861+ * Added `--ascii` option. Currently supported only in HTML writer,

2862+ which it causes to use numerical entities instead of UTF-8.

2863+

2864+ * EPUB writer: `--toc` now works to provide a table of contents

2865+ at the beginning of each chapter.

2866+

2867+ * LaTeX writer: Change figure defaults to `htbp`.

2868+ This prevents "too many unprocessed floats." Resolves

2869+ Issue #285.

2870+

2871+ * `Text.Pandoc.UTF8`: Encode filenames even when using recent

2872+ base.

2873+

2874+ * `markdown2pdf`: Fixed filename encoding issues. With help from Paulo

2875+ Tanimoto. Resolves Issue #286.

2876+

2877+ * HTML writer: Put line breaks in section divs.

2878+

2879+ * `Text.Pandoc.Shared`: Make `writerSectionDivs` default to False.

2880+

2881+pandoc (1.8.0.3)

2882+

2883+ * Fixed Source-repository stanza in cabal file.

2884+

2885+pandoc (1.8.0.2)

2886+

2887+ * HTML writer:

2888+

2889+ + Stringify alt text instead of converting to HTML.

2890+ + Break lines after block elements, not inside tags.

2891+ HTML output now closely resembles that of tidy. Resolves Issue #134.

2892+

2893+ * Markdown reader: Fixed bug in footnote block parser (pointed out

2894+ by Jesse Rosenthal). The problem arose when the blank line

2895+ at the end of a footnote block contained indenting spaces.

2896+

2897+ * Shared: Improved 'normalize' function so it normalizes Spaces too.

2898+ In normal form, Space elements only occur to separate two non-Space

2899+ elements. So, we never have [Space], or [, ..., Space].

2900+

2901+ * Tests:

2902+

2903+ + Improved Arbitrary instance.

2904+ + Added timeout for test instances.

2905+

2906+ * README:

2907+

2908+ + Added section on four-space rule for lists. Resolves Issue #283.

2909+ + Clarified optional arguments on math options.

2910+

2911+ * markdown2pdf: Fixed bug with output file extensions.

2912+ Previously `markdown2pdf test.txt -o test.en.pdf` would produce

2913+ `test.pdf`, not `test.en.pdf`. Thanks to Paolo Tanimoto for the fix.

2914+

2915+pandoc (1.8.0.1)

2916+

2917+ * Revised Interact.hs so that it works with the CPP macros

2918+ in the UTF8 module.

2919+

2920+ * Revised Setup.hs so that we don't call MakeManPage.hs unless

2921+ the man pages are out of date.

2922+

2923+pandoc (1.8)

2924+

2925+ [new features]

2926+

2927+ * Support for citations using Andrea Rossato's `citeproc-hs` 0.3.

2928+ You can now write, for example,

2929+

2930+ Water is wet [see @doe99, pp. 33-35; also @smith04, ch. 1].

2931+

2932+ and, when you process your document using `pandoc`, specifying

2933+ a citation style using `--csl` and a bibliography using `--bibliography`,

2934+ the citation will be replaced by an appropriately formatted

2935+ citation, and a list of works cited will be added to the end

2936+ of the document.

2937+

2938+ This means that you can switch effortlessly between different citation

2939+ and bibliography styles, including footnote, numerical, and author-date

2940+ formats. The bibliography can be in any of the following formats: MODS,

2941+ BibTeX, BibLaTeX, RIS, EndNote, EndNote XML, ISI, MEDLINE, Copac, or JSON.

2942+ See the README for further details.

2943+

2944+ Citations are supported in the markdown reader, using a special

2945+ syntax, and in the LaTeX reader, using natbib or biblatex syntax.

2946+ (Thanks to Nathan Gass for the natbib and biblatex support.)

2947+

2948+ * New `textile` reader and writer. Thanks to Paul Rivier for contributing

2949+ the `textile` reader, an almost complete implementation of the textile

2950+ syntax used by the ruby [RedCloth library](http://redcloth.org/textile).

2951+ Resolves Issue #51.

2952+

2953+ * New `org` writer, for Emacs Org-mode, contributed by Puneeth Chaganti.

2954+

2955+ * New `json` reader and writer, for reading and writing a JSON

2956+ representation of the native Pandoc AST. These are much faster

2957+ than the `native` reader and writer, and should be used for

2958+ serializing Pandoc to text. To convert between the JSON representation

2959+ and native Pandoc, use `encodeJSON` and `decodeJSON` from

2960+ `Text.JSON.Generic`.

2961+

2962+ * A new `jsonFilter` function in `Text.Pandoc` makes it easy

2963+ to write scripts that transform a JSON-encoded pandoc document.

2964+ For example:

2965+

2966+ -- removelinks.hs - removes links from document

2967+ import Text.Pandoc

2968+ main = interact $ jsonFilter $ bottomUp removeLink

2969+ where removeLink (Link xs _) = Emph xs

2970+ removeLink x = x

2971+

2972+ To use this to remove links while translating markdown to LaTeX:

2973+

2974+ pandoc -t json | runghc removelinks.hs | pandoc -f json -t latex

2975+

2976+ * Attributes are now allowed in inline `Code` elements, for example:

2977+

2978+ In this code, `ulist ! [theclass "special"] << elts`{.haskell} is...

2979+

2980+ The attribute syntax is the same as for delimited code blocks.

2981+ `Code` inline has an extra argument place for attributes, just like

2982+ `CodeBlock`. Inline code will be highlighted in HTML output, if pandoc

2983+ is compiled with highlighting support. Resolves Issue #119.

2984+

2985+ * New `RawBlock` and `RawInline` elements (replacing `RawHtml`,

2986+ `HtmlInline`, and `TeX`) provide lots of flexibility in writing

2987+ scripts to transform Pandoc documents. Scripts can now change

2988+ how each element is rendered in each output format.

2989+

2990+ * You can now define LaTeX macros in markdown documents, and pandoc

2991+ will apply them to TeX math. For example,

2992+

2993+ \newcommand{\plus}[2]{#1 + #2}

2994+ $\plus{3}{4}$

2995+

2996+ yields `3+4`. Since the macros are applied in the reader, they

2997+ will work in every output format, not just LaTeX.

2998+

2999+ * LaTeX macros can also be used in LaTeX documents (both in math

3000+ and in non-math contexts).

3001+

3002+ * A new `--mathjax` option has been added for displaying

3003+ math in HTML using MathJax. Resolves issue #259.

3004+

3005+ * Footnotes are now supported in the RST reader. (Note, however,

3006+ that unlike docutils, pandoc ignores the numeral or symbol used in

3007+ the note; footnotes are put in an auto-numbered ordered list.)

3008+ Resolves Issue #258.

3009+

3010+ * A new `--normalize` option causes pandoc to normalize the AST

3011+ before writing the document. This means that, for example,

3012+ `*hi**there*` will be rendered as `<em>hithere</em>`

3013+ instead of `<em>hi</em><em>there</em>`. This is not the default,

3014+ because there is a significant performance penalty.

3015+

3016+ * A new `--chapters` command-line option causes headers

3017+ in DocBook, LaTeX, and ConTeXt to start with "chapter" (level one).

3018+ Resolves Issue #265.

3019+

3020+ * In DocBook output, `<chapter>` is now used for top-level

3021+ headers if the template contains `<book>`. Resolves Issue #265.

3022+

3023+ * A new `--listings` option in `pandoc` and `markdown2pdf` causes

3024+ the LaTeX writer to use the listings package for code blocks.

3025+ (Thanks to Josef Svennigsson for the pandoc patch, and Etienne

3026+ Millon for the markdown2pdf patch.)

3027+

3028+ * `markdown2pdf` now supports `--data-dir`.

3029+

3030+ * URLs in autolinks now have class "url" so they can be styled.

3031+

3032+ * Improved prettyprinting in most formats. Lines will be wrapped

3033+ more evenly and duplicate blank lines avoided.

3034+

3035+ * New `--columns` command-line option sets the column width for

3036+ line wrapping and relative width calculations for tables.

3037+

3038+ * Made `--smart` work in HTML, RST, and Textile readers, as well

3039+ as markdown.

3040+

3041+ * Added `--html5` option for HTML5 output.

3042+

3043+ * Added support for listings package in LaTeX reader

3044+ (Puneeth Chaganti).

3045+

3046+ * Added support for simple tables in the LaTeX reader.

3047+

3048+ * Added support for simple tables in the HTML reader.

3049+

3050+ * Significant performance improvements in many readers and writers.

3051+

3052+ [API and program changes]

3053+

3054+ * Moved `Text.Pandoc.Definition` from the `pandoc` package to a new

3055+ auxiliary package, `pandoc-types`. This will make it possible for other

3056+ programs to supply output in Pandoc format, without depending on the whole

3057+ pandoc package.

3058+

3059+ * Added `Attr` field to `Code`.

3060+

3061+ * Removed `RawHtml`, `HtmlInline`, and `TeX` elements; added generic

3062+ `RawBlock` and `RawInline`.

3063+

3064+ * Moved generic functions to `Text.Pandoc.Generic`. Deprecated

3065+ `processWith`, replacing it with two functions, `bottomUp` and `topDown`.

3066+ Removed previously deprecated functions `processPandoc` and `queryPandoc`.

3067+

3068+ * Added `Text.Pandoc.Builder`, for building `Pandoc` structures.

3069+

3070+ * `Text.Pandoc` now exports association lists `readers` and `writers`.

3071+

3072+ * Added `Text.Pandoc.Readers.Native`, which exports `readNative`.

3073+ `readNative` can now read full pandoc documents, block lists, blocks,

3074+ inline lists, or inlines. It will interpret `Str "hi"`

3075+ as if it were `Pandoc (Meta [] [] []) [Plain [Str "hi"]]`.

3076+ This should make testing easier.

3077+

3078+ * Removed deprecated `-C/--custom-header` option.

3079+ Use `--template` instead.

3080+

3081+ * `--biblio-file` has been replaced by `--bibliography`.

3082+ `--biblio-format` has been removed; pandoc now guesses the format

3083+ from the file extension (see README).

3084+

3085+ * pandoc will treat an argument as a URI only if it has an

3086+ `http(s)` scheme. Previously pandoc would treat some

3087+ Windows pathnames beginning with `C:/` as URIs.

3088+

3089+ * The `--sanitize-html` option and the `stateSanitize` field in

3090+ `ParserState` have been removed. Sanitization is better done in the

3091+ resulting HTML using `xss-sanitize`, which is based on pandoc's

3092+ sanitization, but improved.

3093+

3094+ * pandoc now adds a newline to the end of its output in fragment

3095+ mode (= not `--standalone`).

3096+

3097+ * Added support for `lang` in `html` tag in the HTML template,

3098+ so you can do `pandoc -s -V lang=es`, for example.

3099+

3100+ * `highlightHtml` in `Text.Pandoc.Highlighting` now takes

3101+ a boolean argument that selects between "inline" and

3102+ "block" HTML.

3103+

3104+ * `Text.Pandoc.Writers.RTF` now exports `rtfEmbedImage`.

3105+ Images are embedded in RTF output when possible (png, jpeg).

3106+ Resolves Issue #275.

3107+

3108+ * Added `Text.Pandoc.Pretty`. This is better suited for pandoc than the

3109+ `pretty` package. Changed all writers that used

3110+ `Text.PrettyPrint.HughesPJ` to use `Text.Pandoc.Pretty` instead.

3111+

3112+ * Rewrote `writeNative` using the new prettyprinting module. It is

3113+ now much faster. The output has been made more consistent and compressed.

3114+ `writeNative` is also now sensitive to writerStandalone`, and will simply

3115+ `print a block list if writerStandalone` is False.

3116+

3117+ * Removed `Text.Pandoc.Blocks`. `Text.Pandoc.Pretty` allows you to define

3118+ blocks and concatenate them, so a separate module is no longer needed.

3119+

3120+ * `Text.Pandoc.Shared`:

3121+

3122+ + Added `writerColumns`, `writerChapters`, and `writerHtml5` to

3123+ `WriterOptions`.

3124+ + Added `normalize`.

3125+ + Removed unneeded prettyprinting functions:

3126+ `wrapped`, `wrapIfNeeded`, `wrappedTeX`, `wrapTeXIfNeeded`, `hang'`,

3127+ `BlockWrapper`, `wrappedBlocksToDoc`.

3128+ + Made `splitBy` take a test instead of an element.

3129+ + Added `findDataFile`, refactored `readDataFile`.

3130+ + Added `stringify`. Rewrote `inlineListToIdentifier` using `stringify`.

3131+ + Fixed `inlineListToIdentifier` to treat '\160' as ' '.

3132+

3133+ * `Text.Pandoc.Readers.HTML`:

3134+

3135+ + Removed `rawHtmlBlock`, `anyHtmlBlockTag`, `anyHtmlInlineTag`,

3136+ `anyHtmlTag`, `anyHtmlEndTag`, `htmlEndTag`, `extractTagType`,

3137+ `htmlBlockElement`, `htmlComment`

3138+ + Added `htmlTag`, `htmlInBalanced`, `isInlineTag`, `isBlockTag`,

3139+ `isTextTag`

3140+

3141+ * Moved `smartPunctuation` from `Text.Pandoc.Readers.Markdown`

3142+ to `Text.Pandoc.Readers.Parsing`, and parameterized it with

3143+ an inline parser.

3144+

3145+ * Added `nonspaceChar` to `Text.Pandoc.Parsing`.

3146+

3147+ * Ellipses are no longer allowed to contain spaces.

3148+ Previously we allowed '. . .', ' . . . ', etc. This caused

3149+ too many complications, and removed author's flexibility in

3150+ combining ellipses with spaces and periods.

3151+

3152+ * Allow linebreaks in URLs (treat as spaces). Also, a string of

3153+ consecutive spaces or tabs is now parsed as a single space. If you have

3154+ multiple spaces in your URL, use `%20%20`.

3155+

3156+ * `Text.Pandoc.Parsing`:

3157+

3158+ + Removed `refsMatch`.

3159+ + Hid `Key` constructor.

3160+ + Removed custom `Ord` and `Eq` instances for `Key`.

3161+ + Added `toKey` and `fromKey` to convert between `Key` and `[Inline]`.

3162+ + Generalized type on `readWith`.

3163+

3164+ * Small change in calculation of relative widths of table columns.

3165+ If the size of the header > the specified column width, use

3166+ the header size as 100% for purposes of calculating

3167+ relative widths of columns.

3168+

3169+ * Markdown writer now uses some pandoc-specific features when `--strict`

3170+ is not specified: `\` newline is used for a hard linebreak instead of

3171+ two spaces then a newline. And delimited code blocks are used when

3172+ there are attributes.

3173+

3174+ * HTML writer: improved gladTeX output by setting ENV appropriately

3175+ for display or inline math (Jonathan Daugherty).

3176+

3177+ * LaTeX writer: Use `\paragraph`, `\subparagraph` for level 4,5 headers.

3178+

3179+ * LaTeX reader:

3180+

3181+ + `\label{foo}` and `\ref{foo}` now become `{foo}` instead of `(foo)`.

3182+ + `\index{}` commands are skipped.

3183+

3184+ * Added `fontsize` variable to default LaTeX template.

3185+ This makes it easy to set the font size using `markdown2pdf`:

3186+ `markdown2pdf -V fontsize=12pt input.txt`.

3187+

3188+ * Fixed problem with strikeout in LaTeX headers when using

3189+ hyperref, by adding a command to the default LaTeX template

3190+ that disables `\sout` inside pdf strings. Thanks to Joost Kremers

3191+ for the fix.

3192+

3193+ * The `COLUMNS` environment variable no longer has any effect.

3194+

3195+ [under-the-hood improvements]

3196+

3197+ * Pandoc now compiles with GHC 7. (This alone leads to a

3198+ significant performance improvement, 15-20%.)

3199+

3200+ * Completely rewrote HTML reader using tagsoup as a lexer. The

3201+ new reader is faster and more accurate. Unlike the

3202+ old reader, it does not get bogged down on some input

3203+ (Issues #277, 255). And it handles namespaces in tags

3204+ (Issue #274).

3205+

3206+ * Replaced `escapeStringAsXML` with a faster version.

3207+

3208+ * Rewrote `spaceChar` and some other parsers in Text.Pandoc.Parsing

3209+ for a significant performance boost.

3210+

3211+ * Improved performance of all readers by rewriting parsers.

3212+

3213+ * Simplified Text.Pandoc.CharacterReferences by using

3214+ entity lookup functions from TagSoup.

3215+

3216+ * `Text.Pandoc.UTF8` now uses the unicode-aware IO functions

3217+ from `System.IO` if base >= 4.2. This gives support for

3218+ windows line endings on windows.

3219+

3220+ * Remove duplications in documentation by generating the

3221+ pandoc man page from README, using `MakeManPage.hs`.

3222+

3223+ * README now includes a full description of markdown syntax,

3224+ including non-pandoc-specific parts. A new `pandoc_markdown`

3225+ man page is extracted from this, so you can look up markdown

3226+ syntax by doing `man pandoc_markdown`.

3227+

3228+ * Completely revised test framework (with help from Nathan Gass).

3229+ The new test framework is built when the `tests` Cabal flag is set. It

3230+ includes the old integration tests, but also some new unit and quickcheck

3231+ tests. Test output has been much improved, and you can now specify a glob

3232+ pattern after `cabal test` to indicate which tests should be run;

3233+ for example `cabal test citations` will run all the citation tests.

3234+

3235+ * Added a shell script, `stripansi.sh`, for filtering ANSI control

3236+ sequences from test output: `cabal test | ./stripansi.sh > test.log`.

3237+

3238+ * Added `Interact.hs` to make it easier to use ghci while developing.

3239+ `Interact.hs` loads `ghci` from the `src` directory, specifying

3240+ all the options needed to load pandoc modules (including

3241+ specific package dependencies, which it gets by parsing

3242+ dist/setup-config).

3243+

3244+ * Added `Benchmark.hs`, testing all readers + writers using criterion.

3245+

3246+ * Added `stats.sh`, to make it easier to collect and archive

3247+ benchmark and lines-of-code stats.

3248+

3249+ * Added upper bounds to all cabal dependencies.

3250+

3251+ * Include man pages in extra-source-files. This allows users to

3252+ install pandoc from the tarball without needing to build the man

3253+ pages.

3254+

3255+ [bug fixes]

3256+

3257+ * Filenames are encoded as UTF8. Resolves Issue #252.

3258+

3259+ * Handle curly quotes better in `--smart` mode. Previously, curly quotes

3260+ were just parsed literally, leading to problems in some output formats.

3261+ Now they are parsed as `Quoted` inlines, if `--smart` is specified.

3262+ Resolves Issue #270.

3263+

3264+ * Text.Pandoc.Parsing: Fixed bug in grid table parser.

3265+ Spaces at end of line were not being stripped properly,

3266+ resulting in unintended LineBreaks.

3267+

3268+ * Markdown reader:

3269+

3270+ + Allow HTML comments as inline elements in markdown.

3271+ So, `aaa <!-- comment --> bbb` can be a single paragraph.

3272+ + Fixed superscripts with links: `^[link](/foo)^` gets

3273+ recognized as a superscripted link, not an inline note followed by

3274+ garbage.

3275+ + Fixed regression, making markdown reference keys case-insensitive again.

3276+ Resolves Issue #272.

3277+ + Properly handle abbreviations (like `Mr.`) at the end of a line.

3278+ + Better handling of intraword underscores, avoiding exponential

3279+ slowdowns in some cases. Resolves Issue #182.

3280+ + Fixed bug in alignments in tables with blank rows in the header.

3281+

3282+ * RST reader:

3283+

3284+ + Field lists now allow spaces in field names, and

3285+ block content in field values. (Thanks to Lachlan Musicman

3286+ for pointing out the bug.)

3287+ + Definition list items are now always `Para` instead of

3288+ `Plain`, matching behavior of `rst2xml.py`.

3289+ + In image blocks, the description is parsed properly and

3290+ used for the alt attribute, not also the title.

3291+ + Skip blank lines at beginning of file. Resolves

3292+ Debian #611328.

3293+

3294+ * LaTeX reader:

3295+

3296+ + Improved parsing of preamble.

3297+ Previously you'd get unexpected behavior on a document that

3298+ contained `\begin{document}` in, say, a verbatim block.

3299+ + Allow spaces between `\begin` or `\end` and `{`.

3300+ + Support `\L` and `\l`.

3301+ + Skip comments inside paragraphs.

3302+

3303+ * LaTeX writer:

3304+

3305+ + Escape strings in `\href{..}`.

3306+ + In nonsimple tables, put cells in `\parbox`.

3307+

3308+ * OpenDocument writer: don't print raw TeX.

3309+

3310+ * Markdown writer:

3311+

3312+ + Fixed bug in `Image`. URI was getting unescaped twice!

3313+ + Avoid printing extra blank lines at the end if there are

3314+ no notes or references.

3315+

3316+ * LaTeX and ConTeXt: Escape `[` and `]` as `{[}` and `{]}`.

3317+ This avoids unwanted interpretation as an optional argument.

3318+

3319+ * ConTeXt writer: Fixed problem with inline code. Previously

3320+ `}` would be rendered `\type{}}`. Now we check the string for '}' and '{'.

3321+ If it contains neither, use `\type{}`; otherwise use `\mono{}`

3322+ with an escaped version of the string.

3323+

3324+ * `:` now allowed in HTML tags. Resolves Issue #274.

3325+

3326+pandoc (1.6)

3327+

3328+ [ John MacFarlane ]

3329+

3330+ * New EPUB and HTML Slidy writers. (Issue #122)

3331+

3332+ - EPUB is a standard ebook format, used in Apple's iBooks for

3333+ the iPad and iPhone, Barnes and Noble's nook reader, the Sony

3334+ reader, and many other devices.

3335+ - Slidy, like S5, is a system for producing HTML+javascript slide

3336+ shows.

3337+

3338+ * All input is assumed to be UTF-8, no matter what the locale and ghc

3339+ version, and all output is UTF-8. This reverts to pre-1.5 behavior.

3340+ Also, a BOM, if present, is stripped from the input.

3341+

3342+ * Markdown now supports grid tables, whose cells can contain

3343+ arbitrary block elements. (Issue #43)

3344+

3345+ * Sequentially numbered example lists in markdown with `@` marker.

3346+

3347+ * Markdown table captions can begin with a bare colon and no longer need

3348+ to include the English word "table." Also, a caption can now occur

3349+ either before or after the table. (Issue #227)

3350+

3351+ * New command-line options:

3352+

3353+ - `--epub-stylesheet` allows you to specify a CSS file that will

3354+ be used to style your ebook.

3355+ - `--epub-metadata` allows you to specify metadata for the ebook.

3356+ - `--offline` causes the generated HTML slideshow to include all

3357+ needed scripts and stylesheets.

3358+ - `--webtex` causes TeX math to be converted to images using the

3359+ Google Charts API (unless a different URL is specified).

3360+ - `--section-divs` causes div tags to be added around each section

3361+ in an HTML document. (Issue #230, 239)

3362+

3363+ * Default behavior of S5 writer in standalone mode has changed:

3364+ previously, it would include all needed scripts and stylesheets

3365+ in the generated HTML; now, only links are included unless

3366+ the `--offline` option is used.

3367+

3368+ * Default behavior of HTML writer has changed. Between 1.2 and 1.5,

3369+ pandoc would enclose sections in div tags with identifiers on the

3370+ div tags, so that the sections can be manipulated in javascript.

3371+ This caused undesirable interactions with raw HTML div tags. So,

3372+ starting with 1.6, the default is to put the identifiers directly

3373+ on the header tags, and not to include the divs. The `--section-divs`

3374+ option selects the 1.2-1.5 behavior.

3375+

3376+ * API changes:

3377+

3378+ - `HTMLMathMethod`: Added `WebTeX`, removed `MimeTeX`.

3379+ - `WriterOptions`: Added `writerUserDataDir`, `writerSourceDirectory`,

3380+ `writerEPUBMetadata` fields. Removed `writerIncludeBefore`,

3381+ `writerIncludeAfter`.

3382+ - Added `headerShift` to `Text.Pandoc.Shared`.

3383+ - Moved parsing code and `ParserState` from `Text.Pandoc.Shared`

3384+ to a new module, `Text.Pandoc.Parsing`.

3385+ - Added `stateHasChapters` to `ParserState`.

3386+ - Added `HTMLSlideVariant`.

3387+ - Made `KeyTable` a map instead of an association list.

3388+ - Added accessors for `Meta` fields (`docTitle`, `docAuthors`,

3389+ `docDate`).

3390+ - `Pandoc`, `Meta`, `Inline`, and `Block` have been given `Ord`

3391+ instances.

3392+ - Reference keys now have a type of their own (`Key`), with its

3393+ own `Ord` instance for case-insensitive comparison.

3394+ - Added `Text.Pandoc.Writers.EPUB`.

3395+ - Added `Text.Pandoc.UUID`.

3396+ - Removed `Text.Pandoc.ODT`, added `Text.Pandoc.Writers.ODT`.

3397+ Removed `saveOpenDocumentAsODT`, added `writeODT`.

3398+ - Added `Text.Pandoc.Writers.Native` and `writeNative`.

3399+ Removed `prettyPandoc`.

3400+ - Added `Text.Pandoc.UTF8` for portable UTF8 string IO.

3401+ - Removed `Text.Pandoc.Writers.S5` and the `writeS5` function.

3402+ Moved `s5Includes` to a new module, `Text.Pandoc.S5`.

3403+ To write S5, you now use `writeHtml` with `writerSlideVariant`

3404+ set to `S5Slides` or `SlidySlides`.

3405+

3406+ * Template changes. If you use custom templates, please update them,

3407+ particularly if you use syntax highlighting with pandoc. The old HTML

3408+ templates hardcoded highlighting CSS that will no longer work with

3409+ the most recent version of highlighting-kate.

3410+

3411+ - HTML template: avoid empty meta tag if no date.

3412+ - HTML template: Use default highlighting CSS from highlighting-kate

3413+ instead of hard-coding the CSS into the template.

3414+ - HTML template: insert-before text goes before the title, and

3415+ immediately after the <body> tag, as documented. (Issue #241)

3416+ - Added slidy and s5 templates.

3417+ - Added amssymb to preamble of latex template. (github Issue 1)

3418+

3419+ * Removed excess newlines at the end of output. Note: because output

3420+ will not contain an extra newline, you may need to make adjustments

3421+ if you are inserting pandoc's output into a template.

3422+

3423+ * In S5 and slidy, horizontal rules now cause a new slide, so you

3424+ are no longer limited to one slide per section.

3425+

3426+ * Improved handling of code in man writer. Inline code is now monospace,

3427+ not bold, and code blocks now use .nf (no fill) and .IP (indented para).

3428+

3429+ * HTML reader parses `<tt>` as Code. (Issue #247)

3430+

3431+ * html+lhs output now contains bird tracks, even when compiled without

3432+ highlighting support. (Issue #242)

3433+

3434+ * Colons are now no longer allowed in autogenerated XML/HTML identifiers,

3435+ since they have a special meaning in XML.

3436+

3437+ * Code improvements in ODT writer. Remote images are now replaced with

3438+ their alt text rather than a broken link.

3439+

3440+ * LaTeX reader improvements:

3441+

3442+ - Made latex `\section`, `\chapter` parsers more forgiving of

3443+ whitespace.

3444+ - Parse `\chapter{}` in latex.

3445+ - Changed `rawLaTeXInline` to accept `\section`, `\begin`, etc.

3446+ - Use new `rawLaTeXInline'` in LaTeX reader, and export `rawLaTeXInline`

3447+ for use in markdown reader.

3448+ - Fixes bug wherein `\section{foo}` was not recognized as raw TeX

3449+ in markdown document.

3450+

3451+ * LaTeX writer: images are automatically shrunk if they would extend

3452+ beyond the page margin.

3453+

3454+ * Plain, markdown, RST writers now use unicode for smart punctuation.

3455+

3456+ * Man writer converts math to unicode when possible, as in other writers.

3457+

3458+ * `markdown2pdf` can now recognize citeproc options.

3459+

3460+ * Command-line arguments are converted to UTF-8. (Issue #234)

3461+

3462+ * `Text.Pandoc.TeXMath` has been rewritten to use texmath's parser.

3463+ This allows it to handle a wider range of formulas. Also, if a formula

3464+ cannot be converted, it is left in raw TeX; formulas are no longer

3465+ partially converted.

3466+

3467+ * Unicode curly quotes are left alone when parsing smart quotes. (Issue

3468+ #143)

3469+

3470+ * Cabal file changes:

3471+

3472+ - Removed parsec < 3 restriction.

3473+ - Added 'threaded' flag for architectures where GHC lacks a threaded

3474+ runtime.

3475+ - Use 'threaded' only for markdown2pdf; it is not needed for pandoc.

3476+ - Require highlighting-kate 0.2.7.

3477+

3478+ * Use explicit imports from `Data.Generics`. Otherwise we have a

3479+ conflict with the 'empty' symbol, introduced in syb >= 0.2. (Issue #237)

3480+

3481+ * New data files: slidy/slidy.min.js, slidy/slidy.min.css, epub.css.

3482+

3483+pandoc (1.5.1.1)

3484+

3485+ [ John MacFarlane ]

3486+

3487+ * Fixed uniqueIdent in Shared so that header identifiers work as

3488+ advertized in the README and are are valid XHTML names.

3489+

3490+pandoc (1.5.1)

3491+

3492+ [ John MacFarlane ]

3493+

3494+ * Fixed treatment of unicode characters in URIs.

3495+ + Shared now exports escapeURI and unescapeURI. These handle

3496+ UTF8 encoding and decoding as well as URI escaping/unescaping.

3497+ + Shared: uri and emailAddress now return a pair of the original

3498+ parsed text and the escaped URI (in the latter case, with

3499+ the mailto: prefix).

3500+ + HTML reader: unsanitaryURI has been modified to allow unicode

3501+ high characters in a URI.

3502+ + Readers: All link and image URIs are now escaped using

3503+ escapeURI.

3504+ + Markdown and RST writers: unescapeURI is used so that URIs

3505+ in these formats are human-readable.

3506+

3507+ * Setup.hs: Don't assume that the build directory is "dist".

3508+ Instead, get it from localBuildInfo.

3509+

3510+ * OpenDocument writer: Use a Map for stTextStyleAttr.

3511+ This avoids duplicates (and invalid xml). Resolves Issue #222.

3512+

3513+pandoc (1.5.0.1)

3514+

3515+ [ John MacFarlane ]

3516+

3517+ * HTML writer: Fixed error in math writer (with MathML option)

3518+ that caused an infinite loop for unparsable MathML.

3519+

3520+pandoc (1.5)

3521+

3522+ [ John MacFarlane ]

3523+

3524+ * Added --mathml option. When this is selected, pandoc will convert

3525+ TeX math into MathML.

3526+ + Added data/MathMLinHTML.js, which is included when no URL is

3527+ provided for --mathml. This allows MathML to be displayed (in

3528+ better browsers) as text/html.

3529+ + Removed Text.Pandoc.LaTeXMathML. The module was no longer

3530+ necessary; it was replaced by two lines in pandoc.hs.

3531+ + Replaced LaTeXMathML.js.commend and LaTeXMathML.js.packed with a

3532+ single combined file, LaTeXMathML.js.

3533+

3534+ * Added --data-dir option.

3535+ This specifies a user data directory. If not specified, will default

3536+ to ~/.pandoc on unix or Application Data\pandoc on Windows.

3537+ Files placed in the user data directory will override system default

3538+ data files.

3539+

3540+ * Added Maybe datadir parameter to readDataFile, saveOpenDocumentAsODT,

3541+ latexMathMLScript, s5HeaderIncludes, and getDefaultTemplate. If

3542+ Nothing, no user directory is searched for an override.

3543+

3544+ * Added 'plain' output format. This is similar to markdown, but

3545+ removes links, pictures, inline formatting, and most anything that

3546+ looks even vaguely markupish. The function writePlain is exported by

3547+ Text.Pandoc.Writers.Markdown, with which it shares most of its code.

3548+

3549+ * Allow multi-line titles and authors in meta block.

3550+ Titles may span multiple lines, provided continuation lines

3551+ begin with a space character. Separate authors may be put on

3552+ multiple lines, provided each line after the first begins with

3553+ a space character. Each author must fit on one line. Multiple

3554+ authors on a single line may still be separated by a semicolon.

3555+ Based on a patch by Justin Bogner.

3556+

3557+ * When given an absolute URI as parameter, pandoc will try to fetch

3558+ the content via HTTP. So you can do:

3559+ 'pandoc -r html -w markdown http://www.fsf.org'

3560+ Adds dependency on HTTP.

3561+

3562+ * Made HTML reader much more forgiving.

3563+ + Incorporated idea (from HXT) that an element can be closed

3564+ by an open tag for another element.

3565+ + Javascript is partially parsed to make sure that a <script>

3566+ section is not closed by a </script> in a comment or string.

3567+ + More lenient non-quoted attribute values.

3568+ Now we accept anything but a space character, quote, or <>.

3569+ This helps in parsing e.g. www.google.com!

3570+ + Bare & signs are now parsed as a string. This is a common

3571+ HTML mistake.

3572+ + Skip a bare < in malformed HTML.

3573+

3574+ * Removed html2markdown and hsmarkdown.

3575+ + html2markdown is no longer needed, since you can now pass URI

3576+ arguments to pandoc and directly convert web pages. (Note,

3577+ however, that pandoc assumes the pages are UTF8. html2markdown

3578+ made an attempt to guess the encoding and convert them.)

3579+ + hsmarkdown is pointless -- a large executable that could be

3580+ replaced by 'pandoc --strict'.

3581+

3582+ * In most writers, an image in a paragraph by itself is now rendered

3583+ as a figure, with the alt text as the caption. (Texinfo, HTML, RST,

3584+ MediaWiki, Docbook, LaTeX, ConTeXt, HTML.) Other images are

3585+ rendered inline.

3586+

3587+ * Depend on extensible-exceptions. This allows pandoc to be compiled

3588+ on GHC 6.8.

3589+

3590+ * Added --base-header-level option. For example, --base-header-level=2

3591+ will change level 1 headers to level 2, level 2 to level 3, etc.

3592+ Closes Debian #563416.

3593+

3594+ * Incomplete support for RST tables (simple and grid).

3595+ Thanks to Eric Kow. Colspans and rowspans not yet supported.

3596+

3597+ * Added accessors (docTitle, docAuthors, docDate) to Meta type.

3598+

3599+ * MediaWiki writer: format links with relative URLs as wikilinks.

3600+ The new rule: If the link target is an absolute URL, an external

3601+ link is created. Otherwise, a wikilink is created.

3602+

3603+ * Text.Pandoc.Shared: Export uniqueIdent, and don't allow tilde in

3604+ identifier. Note: This may break links to sections that involve

3605+ tildes.

3606+

3607+ * Markdown(+lhs) reader: handle "inverse bird tracks."

3608+ Inverse bird tracks (<) are used for haskell example code that is not

3609+ part of the literate Haskell program. Resolves Issue #211.

3610+

3611+ * LaTeX reader:

3612+ + Recognize '\ ' (interword space).

3613+ + Recognize nonbreaking space '~'.

3614+ + Ignore \section, \pdfannot, \pdfstringdef. Ignore alt title in

3615+ section headers. Don't treat \section as inline LaTeX.

3616+ Resolves Issue #202.

3617+ + LaTeX reader: allow any special character to be escaped.

3618+ Resolves Issue #221.

3619+ + LaTeX reader: treat \paragraph and \subparagraph as level 4, 5

3620+ headers. Resolves Issue #207.

3621+

3622+ * Use template variables for include-before/after.

3623+ + These options now imply -s; previously they worked also in fragment

3624+ mode.

3625+ + Users can now adjust position of include-before and include-after

3626+ text in the templates.

3627+ + Default position of include-before moved back (as it was before 1.4)

3628+ before table of contents.

3629+ + Resolves Issue #217.

3630+

3631+ * Don't print an empty table header: (all writers).

3632+ Resolves Issue #210.

3633+

3634+ * HTML, Docbook writer: Use tbody, thead, and cols in tables.

3635+

3636+ * HTML writer: Don't include TOC div if table of contents is empty.

3637+

3638+ * Markdown writer: Fixed citations.

3639+ Previously the markdown writer printed raw citation codes, e.g.

3640+ [geach1970], rather than the expanded citations provided by

3641+ citeproc, e.g. (Geach 1970). Now it prints the expanded citations.

3642+ This means that the document produced can be processed as a markdown

3643+ document without citeproc. Thanks to dsanson for reporting, and

3644+ Andrea Rossato for the patch.

3645+

3646+ * Improved and simplified title block in context template.

3647+ Previously it caused an error if there was no title.

3648+ This method should also be easier for users to customize.

3649+

3650+ * Markdown reader:

3651+ + Treat p., pp., sec., ch., as abbreviations in smart mode.

3652+ + Disallow blank lines in inline code span.

3653+ + Allow footnotes to be indented < 4 spaces.

3654+ This fixes a regression. A test case has been added.

3655+ + Escape spaces in URLs as %20. Previously they were incorrectly

3656+ escaped as +, which is appropriate only for the query part of

3657+ a URL. Resolves Issue #220.

3658+ + Require two spaces after capital letter + period for list item.

3659+ Otherwise "E. coli" starts a list. This might change the semantics

3660+ of some existing documents, since previously the two-space

3661+ requirement was only enforced when the second word started

3662+ with a capital letter. But it is consistent with the existing

3663+ documentation and follows the principle of least surprise.

3664+ Resolves Issue #212.

3665+

3666+ * LaTeX template: redefine labelwidth when using enumerate package.

3667+ Otherwise the list labels (numbers) often extend past the left

3668+ margin, which looks bad.

3669+

3670+ * Mediawiki writer: Don't print a "== Notes ==" header before

3671+ references. This is too English-centric. Writers can provide their

3672+ own header at the end of the document.

3673+

3674+ * Promoted mediawiki headers. '= head =' is now level 1, '== head =='

3675+ level 2, etc. This seems to be correct; it's only by convention

3676+ that wikipedia articles have level 2 headers at most.

3677+ Patch due to Eric Kow.

3678+

3679+ * RunTests.hs: Set LANG to a UTF-8 locale. Use 'pandoc --data-dir=' so

3680+ data files don't need to have been installed. This removes the need to

3681+ set HOME.

3682+

3683+ * HTML reader:

3684+ + Handle spaces before <html>. Resolves Issue #216.

3685+ + Be forgiving in parsing a bare list within a list.

3686+ The following is not valid xhtml, but the intent is clear:

3687+ <ol>

3688+ <li>one</li>

3689+ <ol><li>sub</li></ol>

3690+ <li>two</li>

3691+ </ol>

3692+ We'll treat the <ol> as if it's in a <li>. Resolves Issue #215.

3693+

3694+ * Updated INSTALL instructions. cabal method is now promoted.

3695+

3696+ * Updated markdown2pdf man page. It no longer says all pandoc options

3697+ are accepted.

3698+

3699+ * README/man pages: Removed advice to pipe through tidy before HTML

3700+ reader. This is obsolete, now that we have a forgiving HTML parser.

3701+

3702+ * LaTeX writer: set numbersections template variable, so

3703+ the section numbering options work again.

3704+

3705+ * Removed obsolete Makefile.

3706+

3707+ * Website: renamed index.txt.in -> index.txt.

3708+

3709+ * New batch file to make-windows-installer.

3710+ + Removed old Makefile.windows

3711+ + Added make-windows-installer.bat

3712+ + Modified default installer name in pandoc-setup.iss

3713+

3714+ * Removed freebsd and macports directories.

3715+ They are no longer up to date.

3716+

3717+ * Setup.hs:

3718+ + Made man page building sensitive to build verbosity.

3719+ + Improved detection of highlighting support in test hook.

3720+ + Install wrapper scripts into cabal bin directory.

3721+ + Also simplified installManpages.

3722+ + Setup.hs: install manpages to mandir. Code borrowed from darcs.

3723+

3724+ * Changed default of writerXeTeX to False.

3725+

3726+ * HTML writer: don't include empty UL if --toc but no sections.

3727+ Resolves Issue #199.

3728+

3729+ * LaTeX writer:

3730+

3731+ + If book, report, or memoir documentclass, use \chapter{}

3732+ for first-level headers. Otherwise use \section{}.

3733+ + Removed stLink, link template variable. Reason: we now always

3734+ include hyperref in the template.

3735+

3736+ * LaTeX template:

3737+

3738+ + Only show \author if there are some.

3739+ + Always include hyperref package. It is used not just for links but

3740+ for toc, section heading bookmarks, footnotes, etc. Also added

3741+ unicode=true on hyperref options.

3742+

3743+ * markdown2pdf: always do at least two runs. hyperref bookmarks

3744+ require this.

3745+

3746+ * cabal file: Removed unneeded dependency on template-haskell.

3747+

3748+ * Windows installer - fixed bug in data file locations.

3749+ Resolves Issue #197.

3750+

3751+ * Deprecated --custom-header in documentation.

3752+ Removed old "Custom Headers" section in README.

3753+

3754+pandoc (1.4)

3755+

3756+ [ John MacFarlane ]

3757+

3758+ * Pandoc will now compile with either GHC 6.10 or 6.12.

3759+ + Don't use System.IO.UTF8 when compiling with 6.12

3760+ + Use -fno-warn-unused-do-bind option when compiling with 6.12

3761+

3762+ * Replaced old headers with templates. Now users have much more

3763+ control over the way documents appear in --standalone mode,

3764+ and writer code is simplified. Resolves Issues #59, 147.

3765+ Every effort has been made to retain backwards compatibilty.

3766+ So, the --custom-header option should still work as before.

3767+

3768+ + Added Text.Pandoc.Templates. This provides functions for

3769+ retrieving default templates and for rendering templates.

3770+ + System templates (in the pandoc data directory) can be

3771+ overridden by user templates in $HOME/.pandoc/templates.

3772+ + Removed Text.Pandoc.DefaultHeaders.

3773+ + Removed data/headers directory.

3774+ + Added templates directory.

3775+ + Added writerTemplate and writerVariables fields to WriterOptions.

3776+ + Removed writerTitlePrefix, writerHeader fields from WriterOptions.

3777+ + Changed --print-default-header to --print-default-template.

3778+ + Added --template option.

3779+ + Added -V/--variable option to set custom template variables.

3780+

3781+ * Pandoc no longer requires Template Haskell. Resolves Issue #186.

3782+

3783+ + Removed need for TH in ODT module. Instead get reference.odt from

3784+ data file at run time.

3785+ + Removed TH dependency from S5 module. S5 module now exports

3786+ s5HeaderIncludes, which pandoc.hs includes if writer is s5 and

3787+ standalone.

3788+ + Refactored LaTeXMathML not to use TH.

3789+

3790+ * Meta is now Meta [Inline] [[Inline]] [Inline] rather than

3791+ Meta [Inline] [String] String. Authors and date in Meta are now lists

3792+ of Inline elements rather than raw strings. This means that they can

3793+ be formatted and can include footnotes. NOTE: This may be a breaking

3794+ change for those using pandoc as a library.

3795+

3796+ * Added readDataFile to Text.Pandoc.Shared. This retrieves

3797+ a data file from the user pandoc data directory (~/.pandoc

3798+ on unix), or, if not found there, from the system data

3799+ directory ($CABALDIR/shared/pandoc-VERSION/). All data

3800+ files, including templates, LaTeXMathML.js, s5 styles,

3801+ and reference.odt, can be overridden by the user.

3802+

3803+ * s5 files moved from data/ui/default to s5/default.

3804+

3805+ * Use unicode instead of entities in HTML and XML output. Resolves

3806+ Issue #163.

3807+

3808+ * Prettier HTML footnote references: put anchor inside sup,

3809+ instead of other way. Resolves Issue #191. Thanks to

3810+ infinity0x.

3811+

3812+ * Added --xetex option to pandoc and markdown2pdf.

3813+ If --xetex is specified, pandoc produces latex suitable for

3814+ processing by xelatex, and markdown2pdf uses xelatex to create

3815+ the PDF. Resolves Issue #185.

3816+

3817+ * RTF writer: multiple authors now occupy multiple paragraphs rather

3818+ than using a line break.

3819+

3820+ * Man writer: now the "--after-body" will come after the "AUTHORS"

3821+ section, whereas before it would come before it. This is a

3822+ slight break from backwards compatibility.

3823+

3824+ * Added --reference-odt option, so users may customize the styles

3825+ used in pandoc-generated ODT files. Users may also place a

3826+ default reference.odt in the ~\.pandoc directory.

3827+

3828+ * ODT writer:

3829+ + Indented and line-broke styles.xml so it can be modified more easily.

3830+ + Omitted some unnecessary style declarations.

3831+ + Don't wrap text in OpenDocument writer. The tags are too long, making

3832+ wrapping ugly and pointless.

3833+

3834+ * LaTeX reader: use \\ to separate multiple authors.

3835+

3836+ * Markdown reader: use ; as separator between authors.

3837+ This allows you to use ',' within author names: e.g. "John Jones, Jr."

3838+

3839+ * S5 writer: use linebreak to separate authors in title page.

3840+

3841+ * RST reader: Allow :: before lhs code block. The RST spec requires the

3842+ :: before verbatim blocks. This :: should not be treated as literal

3843+ colons. Resolves Issue #189.

3844+

3845+ * Documented pandoc 1.3's new definition list syntax in README.

3846+ (An oversight in the last release.)

3847+

3848+ * markdown2pdf.hs:

3849+ + interpret ! in a log as an error line.

3850+ + --toc now works properly.

3851+

3852+ * Changes in RunTests.hs:

3853+ + Use the Diff library rather than a local copy of Diff.hs.

3854+ (This vastly increases performance.) This change means that 'cabal

3855+ test' presupposes that the Diff library is installed.

3856+ + Removed tests/Diff.hs from cabal file.

3857+ + Changed RunTests to use local environment. We need at least HOME, so

3858+ pandoc can find its data directory.

3859+

3860+ * Updated windows installer to install data files in the app directory.

3861+

3862+ * Windows installer now installs portable wrappers hsmarkdown and

3863+ markdown2pdf.

3864+

3865+pandoc (1.3)

3866+

3867+ [ John MacFarlane ]

3868+

3869+ * Added --id-prefix option (Issue #41). This adds a prefix to all

3870+ automatically generated HTML identifiers, which helps prevent

3871+ duplicate identifiers when you're generating a fragment (say a blog

3872+ post).

3873+

3874+ * Added --indented-code-classes option. This specifies classes

3875+ to use for indented code blocks. (Patch due to buttock; Issue #87.)

3876+

3877+ * --number-sections now affects HTML output as well as ConTeXt and LaTeX

3878+ (Issue #150).

3879+

3880+ * Improved syntax for markdown definition lists (Issue #24).

3881+ Definition lists are now more compatible with PHP Markdown Extra.

3882+ + You can have multiple definitions for a term (but still not

3883+ multiple terms).

3884+ + Multi-block definitions no longer need a column before each block

3885+ (indeed, this will now cause multiple definitions).

3886+ + The marker no longer needs to be flush with the left margin,

3887+ but can be indented at or two spaces. Also, ~ as well as :

3888+ can be used as the marker (this suggestion due to David

3889+ Wheeler.)

3890+ + There can now be a blank line between the term and the

3891+ definitions.

3892+

3893+ * Better looking simple tables. Resolves Issue #180.

3894+ + Markdown reader: simple tables are now given column widths of 0.

3895+ + Column width of 0 is interpreted as meaning: use default column width.

3896+ + Writers now include explicit column width information only

3897+ for multiline tables. (Exception: RTF writer, which requires

3898+ column widths. In this case, columns are given equal widths,

3899+ adding up to the text width.)

3900+ + Simple tables should now look better in most output formats.

3901+

3902+ * Allow markdown tables without headers (Issue #50).

3903+ The new syntax is described in README. Also allow optional line of

3904+ dashes at bottom of simple tables.

3905+

3906+ * Compensate for width of final table column (Issue #144).

3907+

3908+ * Treat a backslash followed by a newline as a hard line break

3909+ in markdown. Resolves Issue #154. This is a nice alternative

3910+ to markdown's "invisible" way of indicating hardline breaks

3911+ using lines that end with two spaces.

3912+

3913+ * Improved performance of markdown reader by ~10% by eliminating the

3914+ need for a separate parsing pass for notes. Raw notes are now stored

3915+ on the first pass (which parses references), then parsed when the

3916+ note is inserted into the AST. The stateNotes field in ParserState

3917+ is now a list of [(String, String)] pairs instead of [(String,

3918+ [Block])].

3919+

3920+ * In markdown reader, treat 4 or more * or _ in a row as literal

3921+ text. (Trying to parse long strings of * or _ as strong or emph

3922+ leads to exponential performance problems.)

3923+

3924+ * Markdown reader: Use + rather than %20 for spaces in URLs.

3925+

3926+ * Fixed htmlComment parser, adding a needed 'try'.

3927+

3928+ * Don't print raw HTML in man output.

3929+

3930+ * Allow . _ and ~ in header identifiers.

3931+

3932+ * Specially mark code blocks that were "literate" in the input.

3933+ They can then be treated differently in the writers. This allows

3934+ authors to distinguish bits of the literate program they are writing

3935+ from source code examples, even if the examples are marked as

3936+ Haskell for highlighting. (Issue #174.)

3937+

3938+ * Modified html+lhs output to use "haskell" highlighter instead

3939+ of "literateHaskell". The highlighting module now adds bird tracks

3940+ after highlighting (for HTML output), if the code block has the

3941+ "literate" class. This gives better results, because kate's

3942+ haskell highlighter is much better than the literateHaskell

3943+ highlighter.

3944+

3945+ * Fixed handling of footnotes in titles (HTML) and headers (LaTeX).

3946+ (Issue #137.)

3947+

3948+ * Support for "..code-block" directive in RST reader. Not core

3949+ RST, but used in Sphinx for code blocks annotated with syntax

3950+ information. Thanks to Luke Plant for the patch.

3951+

3952+ * Added "head" to list of block-level HTML tags. Resolves

3953+ Issue #108.

3954+

3955+ * Added stripTags to Text.Pandoc.XML. This is used in the HTML writer.

3956+

3957+ * Set utf-8 encoding in texinfo headers.

3958+

3959+ * Docbook writer: add ids to sections. Use link for internal links.

3960+ (Issue #60.)

3961+

3962+ * Blank lines after lists in MediaWiki writer.

3963+

3964+ * Properly handle commented-out list items in markdown.

3965+ Resolves Issue #142. Example:

3966+

3967+ - a

3968+ <!--

3969+ - b

3970+ -->

3971+ - c

3972+

3973+ * Changed heuristic in compactify. compactify has to decide whether a

3974+ Para that ends a list is a Para intentionally, or just because of

3975+ the blank lines at the end of every list. In the latter case the

3976+ Para is turned to a Plain. The old heuristic was: change final Para

3977+ to Plain iff the other items all end in Plain. This produces bad

3978+ results when, for example, an item contains just a Plain and an HTML

3979+ comment, as it does in the list above. The new heuristic: change

3980+ final Para to Plain iff the other items don't contain a Para.

3981+

3982+ * Added % as an rst underline character. Resolves Issue #173.

3983+

3984+ * Fix inline math parser so that \$ is allowed in math.

3985+ Resolves Issue #169.

3986+

3987+ * Translate \int (integral) into unicode when using unicode math

3988+ method. Resolves Issue #177.

3989+

3990+ * markdown2pdf.hs improvements:

3991+ + Use System.IO.UTF8.

3992+ + Print error messages on last attempt.

3993+ + Do not create a backup when overwriting a PDF (Issue #166).

3994+ + Accept --longopt=val options.

3995+ + Added man/man1/markdown2pdf.1 to extra-tmp-files in cabal, so that

3996+ it is properly cleaned.

3997+

3998+ * Added haddock comments warning that readers assume \n line endings.

3999+

4000+ * Updated COPYRIGHT file.

4001+

4002+ * Makefile: Changed EXECSBASE so it doesn't pull in hsmarkdown &

4003+ markdown2pdf. Otherwise strip tries to strip shell scripts when you

4004+ install using 'make'.

4005+

4006+ * Changed Makefile so it doesn't build Haskell wrappers.

4007+

4008+ * Fixed Makefile so it doesn't try to build man pages in build-doc.

4009+

4010+ * Install pcre3.dll in Windows install script; this allows us to

4011+ package a version of pandoc with highlighting support.

4012+

4013+pandoc (1.2.1)

4014+

4015+ [ John MacFarlane ]

4016+

4017+ * Fixed regression with --preserveTabs. Brought back optPreserveTabs.

4018+ The trick of setting tabStop to 0 to mean "preserve tabs" had a bad

4019+ side effect: strings of 0 spaces were interpreted as indentation.

4020+ So, with --preserve-tabs, unindented paragraphs were treated as

4021+ code. Resolves Issue #138.

4022+

4023+ * HTML writer: wrap sections in divs. Resolves Issue #70.

4024+

4025+ + hierarchicalize has been rationalized; it builds a hierarchical

4026+ representation of the document from the headers, and simultaneously

4027+ gives each section a unique identifier based on the heading title.

4028+ + Identifiers are now attached to the divs rather than

4029+ to the headers themselves.

4030+ + Table of content backlinks go to the beginning of the table, rather

4031+ than to the section reference that was clicked.

4032+ + Code for constructing identifiers has been moved to Text.Pandoc.Shared

4033+ from the HTML writer, since it is now consumed only by

4034+ hierarchicalize.

4035+ + In --strict mode, pandoc just prints bare headings, as before

4036+ (unless --toc has been specified).

4037+ + In s5 output, it does not wrap sections in divs, as that seems to

4038+ confuse the s5 javascript.

4039+

4040+ * Man writer: break lines at end of each sentence. groff expects this

4041+ and treats '.' and '?' differently when followed by line ending as

4042+ opposed to ordinary space. Also, don't escape periods. Instead, use

4043+ zero-width character \& to avoid unwanted interpretation of periods

4044+ at start of line. Resolves Issue #148.

4045+

4046+ * Markdown writer: Added '#' and '>' to list of characters to be

4047+ escaped in markdown output. Removed '<', as it is not an officially

4048+ escapable character. This partially resolves Issue #96.

4049+

4050+ * Make --smart the default for man output format. Otherwise we have

4051+ trouble dividing lists of endlines into sentences.

4052+

4053+ * DocBook writer: Use language attribute to indicate source language

4054+ in code blocks.

4055+

4056+ * RST reader:

4057+

4058+ + Allow # to continue list, even if the list was started with an

4059+ explicit marker. For example:

4060+

4061+ A. my list

4062+ #. continued

4063+

4064+ Resolves Issue #140.

4065+ + Allow continuation lines in line blocks. Also added test cases for

4066+ line blocks for RST reader. Resolves Issue #149.

4067+ + Allow explicit links with spaces in URL: `link <to this>`_

4068+

4069+ * Improved LaTeX reader's coverage of math modes. Remove displaymath*

4070+ (which is not in LaTeX) and recognize all the amsmath environments

4071+ that are alternatives to eqnarray, namely equation, equation*,

4072+ gather, gather*, gathered, multline, multline*, align, align*,

4073+ alignat, alignat*, aligned, alignedat, split. Resolves Issue #103.

4074+ Thanks to shreevatsa.public for the patch.

4075+

4076+ * Markdown reader:

4077+

4078+ + Allow -, _, :, . in markdown attribute names. These are legal in

4079+ XML attribute names.

4080+ + Use non-breaking spaces in abbreviations.

4081+ + Markdown reader: improved efficiency of abbreviation parsing.

4082+ Instead of a separate abbrev parser, we just check for

4083+ abbreviations each time we parse a string. This gives a huge

4084+ performance boost with -S. Resolves Issue #141.

4085+

4086+ * Improved efficiency of shared parsers: hexNum, htmlComment,

4087+ whitespace, indentSpaces.

4088+

4089+ * Export HTMLMathMethod in Text.Pandoc.

4090+

4091+ * Export languagesByExtension in Text.Pandoc.Highlighting.

4092+

4093+ * Added new Haskell version of markdown2pdf, due to

4094+ Paulo Tanimoto. This should be more portable than the old

4095+ shell script.

4096+

4097+ * Made 'pandoc -v' more explicit about compiler options.

4098+ Resolves Issue #139.

4099+

4100+ * pandoc.hs: Made --strict compatible with --standalone, --toc.

4101+

4102+ * Use Paths_pandoc to get version number, instead of hard-coding it

4103+ into Text/Pandoc.hs.

4104+

4105+pandoc (1.2)

4106+

4107+ [ John MacFarlane ]

4108+

4109+ * Added support for literate Haskell. lhs support is triggered by

4110+ '+lhs' suffixes in formats. For example, 'latex+lhs' is literate

4111+ Haskell LaTeX. '.lhs' files are treated by default as literate

4112+ markdown.

4113+

4114+ + Added stateLiterateHaskell to parser state.

4115+ + Added parser for lhsCodeBlock to Markdown, RST, LaTeX readers.

4116+ + Added parser for |inline lhs| to LaTeX reader.

4117+ + Added writerLiterateHaskell to WriterOptions.

4118+ + Added lhs support to Markdown, RST, LaTeX, HTML writers.

4119+ + Added definition of code environment to LaTeX header.

4120+ + Added tests (run only if highlighting support compiled in).

4121+ + Documented lhs features in man page and README.

4122+

4123+ * In Text.Pandoc.Definition, added processWith, processWithM,

4124+ and queryWith, and deprecated processPandoc and queryPandoc

4125+ for these more general functions.

4126+

4127+ * Fixed bug in mediawiki writer: improper closing tags in tables.

4128+ Thanks to Benct Philip Jonsson for reporting the bug.

4129+

4130+ * Added --email-obfuscation option.

4131+

4132+ + Added writer option for email obfuscation.

4133+ + Implemented email obfuscation options in HTML writer.

4134+ + Added option to option parser.

4135+ + Documented in README and pandoc man page.

4136+ + Resolves Issue #97.

4137+

4138+ * LaTeX writer: fixed bug with empty table cells.

4139+ Resolves Issue #107. Thanks to rodja.trappe for the patch.

4140+

4141+ * Fixed bug with header spacing in Markdown and RST writers.

4142+ A null header (Meta [] [] []) should not cause a blank line

4143+ at the beginning of output. But a blank line is needed between

4144+ a non-null header and the main text.

4145+

4146+ * Markdown reader: Relax spacing rules for $$ in display math. Now

4147+ space and newlines are allowed after the opening $$ and before the

4148+ closing $$. However, the display math cannot contain an entirely

4149+ blank line. Resolves Issue #105.

4150+

4151+ * Markdown reader: Gobble space after Plain blocks containing only

4152+ raw html inline. Otherwise following header blocks are not parsed

4153+ correctly, since the parser sees blank space before them. Resolves

4154+ Issue #124.

4155+

4156+ * Markdown reader: Allow " as well as '' to end a latex double-quote.

4157+

4158+ * Conditionally depend on syb and base >= 4 if ghc >= 6.10.

4159+ Resolves Issue #109.

4160+

4161+ * Fixed problems in RST and markdown output due to bug in pretty-1.0.1.0

4162+

4163+ + Added hang' function to Text.Pandoc.Shared; this will be used instead

4164+ of hang, which doesn't work properly in pretty-1.0.1.0. When pretty

4165+ is upgraded, we can go back to hang.

4166+ See http://article.gmane.org/gmane.comp.lang.haskell.general/16687

4167+ + Use hang' (and some different techniques) in RST and markdown writers.

4168+ Some output is now a bit different.

4169+

4170+ * Brought citeproc support up to date for citeproc-hs-0.2.

4171+ (Patch by Andrea Rossato.)

4172+

4173+ * Moved all haskell source to src subdirectory. Renamed Main.hs to

4174+ pandoc.hs.

4175+

4176+ * Rewrote hsmarkdown in Haskell for portability (src/hsmarkdown.hs).

4177+ For now, keeping the old shell script too.

4178+

4179+ * Added TemplateHaskell to Extensions for executable, removed

4180+ -threaded for library. Thanks to duncan.coutts for the bug report.

4181+ Resolves Issue #121.

4182+

4183+ * Moved some Extra-Source-Files to Data-Files.

4184+

4185+ * Moved tabFilter to Shared.

4186+

4187+ * In pandoc.hs, removed optPreserveTabs; instead, tabstop of 0 means

4188+ preserve tabs.

4189+

4190+ * Minor code cleanup based on hlint suggestions.

4191+

4192+pandoc (1.1)

4193+

4194+ [ John MacFarlane ]

4195+

4196+ * Main.hs:

4197+

4198+ + Changed date on copyright message in Main.hs.

4199+ + Have the '-v' option print syntax highlighting languages

4200+ separated by commas, and wrapped in lines, instead of in five

4201+ columns as before.

4202+

4203+ * Added --jsmath option. Resolves Issue #68.

4204+

4205+ + Added --jsmath option to Main.hs

4206+ + Added JsMath to HTMLMathMethod in Text.Pandoc.Shared.

4207+ + Handle math appropriately in HTML writer when JsMath selected.

4208+ + Documented the option in README and man page.

4209+

4210+ * Text.Pandoc.Shared: Changed compactify to use a better heuristic

4211+ for tight and loose lists. Final Para is changed to Plain if all

4212+ other list items *end* with a Plain block. Addresses Issue #99.

4213+

4214+ * HTML reader:

4215+

4216+ + Added colons to protocols in unsanitaryURI. Closes Issue #88.

4217+ + HTML reader: Don't interpret contents of <pre> blocks as markdown.

4218+ Added rawVerbatimBlock parser. Resolves Issue #94.

4219+

4220+ * Markdown reader:

4221+

4222+ + Allow URLs with spaces in them in links and references, but escape

4223+ them as "%20".

4224+ + Allow blank space at the end of horizontal rules.

4225+

4226+ * RST reader: Modified 'unknownDirective' parser to handle comment

4227+ blocks correctly, and added tests for comment blocks. Resolves Issue

4228+ #86. Closes Debian Bug #500662.

4229+

4230+ * HTML writer:

4231+

4232+ + Include classes on tr elements in HTML output:

4233+ "header", "odd", "even". This allows tables to be styled with

4234+ lines in alternating colors. Resolves Issue #91.

4235+ + Enclose all LaTeXMathML bits in <span class="LaTeX">.

4236+ This prevents parts of the document that are not math from being

4237+ interpreted as math by LaTeXMathML.js.

4238+

4239+ * OpenDocument and ODT writers: Added support for HorizontalRule elements,

4240+ which were formerly ignored. Resolves Issue #95.

4241+

4242+ * Text.Pandoc.Shared: Modified wrappedTeX to eliminate the line break

4243+ between a footnote and immediately following nonspace characters in

4244+ LaTeX and ConTeXt output. (This gets interpreted as a space, which

4245+ is not desired in cases like "text^[note]---".) Resolves Issue #93.

4246+

4247+ * Windows installer: Don't require admin privileges to run

4248+ installer. Modified pandoc-setup.iss, and changed modpath.iss to

4249+ modify HKCU path if user lacks admin privileges. Also fixed case

4250+ where oldpath is empty (previously this led to the new path

4251+ beginning with a semicolon).

4252+

4253+ * Updated INSTALL instructions for Arch packages and OS X install using

4254+ cabal-install.

4255+

4256+ * Removed the (now unneeded) debian directory.

4257+ Removed empty Codec and System directories.

4258+

4259+ * Moved odt-styles/ to data/. Removed unneeded variable in Makefile.

4260+

4261+ * Modified Setup.hs so that the "test" target returns an error status

4262+ when tests fail, and "build" returns a success status if

4263+ the build succeeds. Resolves Issue #100.

4264+

4265+ * Added BUGS to files in tarball.

4266+

4267+

4268+pandoc (1.0.0.1)

4269+

4270+ [ John MacFarlane ]

4271+

4272+ * Removed spurious reference to pdf output format from pandoc(1) man page.

4273+

4274+pandoc (1.0)

4275+

4276+ [ Andrea Rossato ]

4277+

4278+ * Added new OpenDocument writer.

4279+

4280+ * Added support for SmallCaps inline element.

4281+

4282+ * Added support for integrating pandoc with citeproc-hs.

4283+

4284+ + Added Cite element to definition and writers.

4285+ + Added Text.Pandoc.Biblio module

4286+ + Note: This support is included only if the 'citeproc'

4287+ Cabal configuration flag is set.

4288+

4289+ * Made Pandoc data structure an instance of Typeable.

4290+ Added new processPandoc and queryPandoc functions, to query

4291+ or transform matching elements in a Pandoc structure.

4292+

4293+ [ Peter Wang ]

4294+

4295+ * Added new Texinfo writer.

4296+

4297+ [ John MacFarlane ]

4298+

4299+ * Changes to Texinfo writer:

4300+

4301+ + No space between paragraph and following @verbatim (provides more

4302+ pleasing appearance in text formats)

4303+ + Blank line consistently after list environments.

4304+ + Removed deVerb.

4305+ + Use @code instead of @verb for inline code (this solves the character

4306+ escaping problem for texi2dvi and texi2pdf).

4307+ + Added news of Texinfo writer to README.

4308+ + Added Texinfo to list of formats in man page, and removed extra 'groff'.

4309+ + Added texi & texinfo extensions to Main.hs, and fixed bug in determining

4310+ default output extension.

4311+ + Modified disallowedInNode in Texinfo writer to correct list of disallowed characters.

4312+

4313+ * Added tests for OpenDocument writer.

4314+

4315+ * Added ODT writer (using zip-archive library to package output of

4316+ OpenDocument writer). Added odt-styles directory with default ODT styles.

4317+

4318+ * Added new mediawiki writer and tests.

4319+

4320+ * Markdown reader: Added support for delimited code blocks, with optional

4321+ syntax highlighting using highlighting-kate (if the 'highlighting'

4322+ configuration option is selected).

4323+

4324+ + Currently highlighting is supported only in the HTML writer.

4325+ + Delimited code blocks can have attributes; using the language name as

4326+ class triggers highlighting.

4327+ + New Attributes parameter in CodeBlock structure.

4328+ + --version now indicates whether syntax highlighting support is compiled

4329+ in, and prints a list of supported languages

4330+

4331+ * Removed debian directory. Pandoc is no longer a native debian package.

4332+

4333+ * Changes to build process: pandoc can now be built from the repository

4334+ using Cabal. No unix tools are needed (so, pandoc can be built on Windows

4335+ without Cygwin).

4336+

4337+ + Include shell scripts themselves in repo, rather than generating from wrappers.

4338+ Removed wrappers directory and wrappers Makefile target.

4339+ + Text/Pandoc/ASCIIMathML.hs, Text/Pandoc/DefaultHeaders.hs,

4340+ and Text/Pandoc/Writers/S5.hs are no longer built in Makefile

4341+ from templates in the templates/ directory. Instead, they use template

4342+ haskell to read data at compile time from the relevant files in data/.

4343+ Template haskell functions go in a new module, Text.Pandoc.TH.

4344+ + man pages are now generated in Setup.hs hook, not by Makefile

4345+ + Makefile 'tarball' target now calls Cabal's 'sdist'

4346+ + Added "Extra-Source-Files" to pandoc.cabal, so sdist contains everything needed

4347+ + Added "Build-Type" field to pandoc.cabal to avoid warning.

4348+ + Added to "Extra-source-files" and "Extra-tmp-files" in pandoc.cabal,

4349+ so 'sdist' and 'clean' will work properly.

4350+ + Setup.hs now generates man pages in a postbuild hook.

4351+ + Added dependency-checking to Setup.hs, so it only rebuilds things

4352+ that need rebuilding.

4353+ + Added 'library' and 'executable' configuration flags.

4354+ Cabal can now be told to build just the library or just the executable.

4355+ + CABALOPTS may now be specified with 'make' to pass Cabal configuration flags.

4356+ For example: CABALOPTS=-fhighlighting make

4357+

4358+ * Rewrote test suite so it doesn't depend on perl or unix tools.

4359+

4360+ + Replaced old runtests.pl with a Haskell script RunTests.hs.

4361+ + Added Diff.hs module to be used by RunTests.hs instead of unix 'diff'.

4362+ + Added test hook to Setup.hs, so tests may be run from cabal.

4363+ + Changed Makefile's 'test' target to run tests via cabal.

4364+ + Removed old generate.sh.

4365+ + Since we no longer have 'sed' to filter out raw HTML sections

4366+ from the docbook writer test, or raw LaTeX sections from the

4367+ context writer test, we now just include these sections.

4368+ They can be taken out if it is necessary to process the files.

4369+ + Updated latex and context writer tests to remove extra spaces

4370+ after '\\item'

4371+ + Added a markdown table reader test.

4372+ + Added markdown-reader-more.txt to test suite, for additional test cases

4373+ for raw ConTeXt environments and more.

4374+

4375+ * Compatibility fixes for CPP, Cabal, and haddock:

4376+

4377+ + Use CPP in "Extensions" field in pandoc.cabal.

4378+ + Removed use of backslash string continuations in source files.

4379+

4380+ * Removed pandoc.cabal.ghc66. We now require Cabal >= 1.2, GHC >= 6.8,

4381+ base >= 3.

4382+

4383+ * Require parsec < 3.

4384+ The compatibility module in parsec 3.0.0 gives far worse performance than

4385+ parsec 2.1. Eventually pandoc will be upgraded to use the new bytestring

4386+ version of parsec, and then we'll go to parsec 3.0.0.

4387+

4388+ * Removed Text.Regex dependencies by rewriting using plain Haskell

4389+ (Text.Pandoc.Writers.RTF, Text.Pandoc.Writers.HTML, Main.hs)

4390+

4391+ * Moved Text.Pandoc.Writers.DefaultHeaders -> Text.Pandoc.DefaultHeaders.

4392+

4393+ * Makefile:

4394+

4395+ + Added 'configure' as dependency of 'uninstall-all'.

4396+ (It uses the Cabal build program.)

4397+ + Makefile: only use --with-hc-pkg if GHC_PKG is defined.

4398+ Note that Cabal will automatically choose the ghc-pkg appropriate

4399+ for the compiler selected, so normally specifying GHC by itself

4400+ is sufficient.

4401+

4402+ * Removed Text.Pandoc.UTF8 module; instead, depend on utf8-string and use

4403+ its IO and conversion functions.

4404+

4405+ * Added -Wall to ghc-options in pandoc.cabal. Cleaned up modules so that

4406+ everything is -Wall clean.

4407+

4408+ + Added pragma to HTML writer to avoid deprecation warning for use of "start" attribute.

4409+ + Added pragma to Text/Pandoc/Shared.hs to get rid of "orphan instance" warnings.

4410+ (These are caused by the Lift instance for ByteString.)

4411+

4412+ * Changed the comment used to replace unsafe HTML if sanitize-html option

4413+ selected.

4414+

4415+ * Made -c/--css option repeatable on the command line (like -H, -A, -B).

4416+

4417+ * Moved XML-formatting functions to new unexported module Text.Pandoc.XML.

4418+

4419+ * Escape '\160' as "&#160;", not "&nbsp;" in XML.

4420+ "nbsp" isn't a predefined XML entity.

4421+

4422+ * Fixed bug in RST reader, which would choke on: "p. one\ntwo\n".

4423+ Added some try's in ordered list parsers.

4424+

4425+ * Man writer: don't escape " as \".

4426+

4427+ * Allow newline before URL in markdown link references. Resolves Issue #81.

4428+ Added tests for this issue in new "markdown-reader-more" tests.

4429+ Changed RunTests.hs to run these tests.

4430+

4431+ * Support for display math. Resolves Issue #47.

4432+

4433+ + Added a DisplayMath/InlineMath selector to Math inlines.

4434+ + Markdown parser yields DisplayMath for $$...$$.

4435+ + LaTeX parser yields DisplayMath when appropriate. Removed

4436+ mathBlock parsers, since the same effect is achieved by the math

4437+ inline parsers, now that they handle display math.

4438+ + Writers handle DisplayMath as appropriate for the format.

4439+ + Modified tests accordingly; added new tests for display math.

4440+

4441+ * Use LaTeXMathML instead of ASCIIMathML. LaTeXMathML is closer

4442+ to LaTeX in its display of math, and supports many non-math LaTeX environments.

4443+

4444+ + Changed -m option to use LaTeXMathML rather than ASCIIMathML.

4445+ + Modified HTML writer to print raw TeX when LaTeXMathML is

4446+ being used instead of suppressing it.

4447+ + Removed ASCIIMathML files from data/ and added LaTeXMathML.

4448+ + Replaced ASCIIMathML with LaTeXMathML in source files.

4449+ + Modified README and pandoc man page source.

4450+ + Added --latexmathml option (kept --asciimathml as a synonym

4451+ for backwards compatibility)

4452+

4453+ * Markdown reader: Parse setext headers before atx headers.

4454+ Test case:

4455+ # hi

4456+ ====

4457+ parsed by Markdown.pl as an H1 header with contents "# hi".

4458+

4459+ * Markdown reader: Treat "mixed" lists the same way as Markdown.pl does.

4460+ The marker on the first list item determines the type of the whole

4461+ list. Thus, a list like

4462+ 1. one

4463+ - two

4464+ * three

4465+ gets parsed as a single ordered list. (Previous versions of pandoc

4466+ treated this as an ordered list with an unordered sublist.)

4467+

4468+ * Markdown smart typography:

4469+

4470+ + Em dashes no longer eat surrounding whitespace. Resolves Issue #69.

4471+ + Use nonbreaking spaces after known abbreviations in markdown parser.

4472+ Thus, for example, "Mr. Brown" comes out as "Mr.~Brown" in LaTeX, and does

4473+ not produce a sentence-separating space. Resolves Issue #75.

4474+

4475+ * Markdown writer: Print unicode \160 literally, rather than as &nbsp;.

4476+

4477+ * Treat '\ ' in (extended) markdown as nonbreaking space.

4478+ Print nonbreaking space appropriately in each writer (e.g. ~ in LaTeX).

4479+

4480+ * The '--sanitize-html' option now examines URIs in markdown links

4481+ and images, and in HTML href and src attributes. If the URI scheme

4482+ is not on a whitelist of safe schemes, it is rejected. The main point

4483+ is to prevent cross-site scripting attacks using 'javascript:' URIs.

4484+ See http://www.mail-archive.com/markdown-discuss@six.pairlist.net/msg01186.html

4485+ and http://ha.ckers.org/xss.html. Resolves Issue #62.

4486+

4487+ * HTML writer:

4488+

4489+ + Override Text.XHtml's stringToHtml function,

4490+ so that characters below 0xff are not converted to numerical entity

4491+ references. Also convert '\160' to "&nbsp;". This should aid readability

4492+ and editability of the HTML source. It does presuppose that the HTML

4493+ will be served as UTF-8.

4494+ + In code blocks, change leading newlines to <br /> tags.

4495+ (Some browsers ignore them.) Resolves Issue #71.

4496+ See http://six.pairlist.net/pipermail/markdown-discuss/2008-May/001297.html

4497+ + Use style attributes rather than css classes for strikethrough

4498+ and ordered list styles. This works better when fragments, rather than

4499+ standalone documents, are generated.

4500+

4501+ * HTML reader: Count anything that isn't a known block (HTML) tag as an

4502+ inline tag (rather than the other way around). Added "html", "head", and

4503+ "body" to list of block tags. Resolves Issue #66, allowing

4504+ <lj> to count as an inline tag.

4505+

4506+ * RTF writer: Fixed bug. Extra spaces were being printed after emphasized,

4507+ boldface, and other inline elements. Resolves Issue #64.

4508+

4509+ * LaTeX reader: improvements in raw LaTeX parsing.

4510+

4511+ + "loose punctuation" (like {}) parsed as Space

4512+ + Para elements must contain more than Str "" and Space elements

4513+ + Added parser for "\ignore" command used in literate haskell.

4514+ + Reworked unknownCommand and rawLaTeXInline: when not in "parse raw"

4515+ mode, these parsers simply strip off the command part and allow

4516+ the arguments to be parsed normally. So, for example,

4517+ \blorg{\emph{hi}} will be parsed as Emph "hi" rather than

4518+ Str "{\\emph{hi}}".

4519+ + Parse lhs "code" environments as verbatim.

4520+ Refactored parsers for verbatim environments.

4521+ + Removed specialEnvironment parser.

4522+ + parse '{}', if present, after \textless, \textgreater,

4523+ \textbar, \textbackslash, \ldots.

4524+ + Parse unescaped special characters verbatim rather than

4525+ changing them to spaces. This way arguments of unknown

4526+ commands will appear in braces.

4527+

4528+ * Parse raw ConTeXt environments as TeX in markdown reader.

4529+ Resolves Issue #73.

4530+

4531+ * Moved BlockWrapper and wrappedBlocksToDoc from ConTeXt writer to Shared.

4532+

4533+ * Made some structural changes to parsing of raw LaTeX environments.

4534+ Previously there was a special block parser for LaTeX environments.

4535+ It returned a Para element containing the raw TeX inline. This has

4536+ been removed, and the raw LaTeX environment parser is now used in the

4537+ rawLaTeXInline parser. The effect is exactly the same, except that we

4538+ can now handle consecutive LaTeX and ConTeXt environments not separated

4539+ by spaces. This new flexibility is required by the example in

4540+ Issue #73:

4541+

4542+ \placeformula \startformula

4543+ L_{1} = L_{2}

4544+ \stopformula

4545+

4546+ API change: The LaTeX reader now exports rawLaTeXEnvironment' (which

4547+ returns a string) rather than rawLaTeXEnvironment (which returns a block

4548+ element). This is more likely to be useful in other applications.

4549+

4550+ * Use \textsubscr instead of \textsubscript for LaTeX subscript macro.

4551+ \textsubscript conflicts with a definition in the memoir class.

4552+ Resolves Issue #65.

4553+

4554+ * Removed unneeded space after "\\item" in LaTeX and ConTeXt output.

4555+

4556+ * Added amsmath package to default LaTeX header. Resolves Issue #48.

4557+

4558+ * Added \setupitemize[autointro] to ConTeXt header, to prevent orphaned

4559+ list introduction lines.

4560+

4561+ * Changed Float to Double in definition of Table element.

4562+ (Double is more efficient in GHC.)

4563+

4564+ * Fixed bug in Markdown parser: regular $s triggering math mode.

4565+ For example: "shoes ($20) and socks ($5)."

4566+ The fix consists in two new restrictions:

4567+

4568+ + the $ that ends a math span may not be directly followed by a digit.

4569+ + no blank lines may be included within a math span.

4570+

4571+ Thanks to Joseph Reagle for noticing the bug.

4572+

4573+ * Use Data.List's 'intercalate' instead of custom 'joinWithSep'.

4574+ Removed 'joinWithSep' from Text.Pandoc.Shared.

4575+

4576+ * Updated README and man pages. Acknowledge contributors in README.

4577+ Added paragraph to README about producing S5 with separate CSS/javascript.

4578+

4579+ * Updated INSTALL to reflect new build system (including configuration

4580+ options) and document new dependencies. Added note to INSTALL that

4581+ Cabal >= 1.2 is required for build. Resolves Issue #74.

4582+

4583+ * Fixed some haddock documentation errors.

4584+

4585+ * Small fix to markdown2pdf man page: only input needs to be piped through iconv.

4586+

4587+pandoc (0.46) unstable; urgency=low

4588+

4589+ [ John MacFarlane ]

4590+

4591+ * Made -H, -A, and -B options cumulative: if they are specified

4592+ multiple times, multiple files will be included.

4593+

4594+ * Added optional HTML sanitization using a whitelist.

4595+ When this option is specified (--sanitize-html on the command line),

4596+ unsafe HTML tags will be replaced by HTML comments, and unsafe HTML

4597+ attributes will be removed. This option should be especially useful

4598+ for those who want to use pandoc libraries in web applications, where

4599+ users will provide the input.

4600+

4601+ + Main.hs: Added --sanitize-html option.

4602+

4603+ + Text.Pandoc.Shared: Added stateSanitizeHTML to ParserState.

4604+

4605+ + Text.Pandoc.Readers.HTML:

4606+ - Added whitelists of sanitaryTags and sanitaryAttributes.

4607+ - Added parsers to check these lists (and state) to see if a given

4608+ tag or attribute should be counted unsafe.

4609+ - Modified anyHtmlTag and anyHtmlEndTag to replace unsafe tags

4610+ with comments.

4611+ - Modified htmlAttribute to remove unsafe attributes.

4612+ - Modified htmlScript and htmlStyle to remove these elements if

4613+ unsafe.

4614+

4615+ + Modified README and man pages to document new option.

4616+

4617+ * Improved handling of email addresses in markdown and reStructuredText.

4618+ Consolidated uri and email address parsers. (Resolves Issue #37.)

4619+

4620+ + New emailAddress and uri parsers in Text.Pandoc.Shared.

4621+ - uri parser uses parseURI from Network.URI.

4622+ - emailAddress parser properly handles email addresses with periods

4623+ in them.

4624+

4625+ + Removed uri and emailAddress parsers from Text.Pandoc.Readers.RST

4626+ and Text.Pandoc.Readers.Markdown.

4627+

4628+ * Markdown reader:

4629+

4630+ + Fixed emph parser so that "*hi **there***" is parsed as a Strong

4631+ nested in an Emph. (A '*' is only recognized as the end of the

4632+ emphasis if it's not the beginning of a strong emphasis.)

4633+

4634+ + Moved blockQuote parser before list parsers for performance.

4635+

4636+ + Modified 'source' parser to allow backslash-escapes in URLs.

4637+ So, for example, [my](/url\(1\)) yields a link to /url(1).

4638+ Resolves Issue #34.

4639+

4640+ + Disallowed links within links. (Resolves Issue #35.)

4641+ - Replaced inlinesInBalanced with inlinesInBalancedBrackets, which

4642+ instead of hard-coding the inline parser takes an inline parser

4643+ as a parameter.

4644+ - Modified reference and inlineNote to use inlinesInBalancedBrackets.

4645+ - Removed unneeded inlineString function.

4646+ - Added inlineNonLink parser, which is now used in the definition of

4647+ reference.

4648+ - Added inlineParsers list and redefined inline and inlineNonLink parsers

4649+ in terms of it.

4650+ - Added failIfLink parser.

4651+

4652+ + Better handling of parentheses in URLs and quotation marks in titles.

4653+ - 'source' parser first tries to parse URL with balanced parentheses;

4654+ if that doesn't work, it tries to parse everything beginning with

4655+ '(' and ending with ')'.

4656+ - source parser now uses an auxiliary function source'.

4657+ - linkTitle parser simplified and improved, under assumption that it

4658+ will be called in context of source'.

4659+

4660+ + Make 'block' conditional on strictness state, instead of using

4661+ failIfStrict in block parsers. Use a different ordering of parsers

4662+ in strict mode (raw HTML block before paragraph) for performance.

4663+ In non-strict mode use rawHtmlBlocks instead of htmlBlock.

4664+ Simplified htmlBlock, since we know it's only called in strict

4665+ mode.

4666+

4667+ + Improved handling of raw HTML. (Resolves Issue #36.)

4668+ - Tags that can be either block or inline (e.g. <ins>) should

4669+ be treated as block when appropriate and as inline when

4670+ appropriate. Thus, for example,

4671+ <ins>hi</ins>

4672+ should be treated as a paragraph with inline <ins> tags, while

4673+ <ins>

4674+ hi

4675+ </ins>

4676+ should be treated as a paragraph within <ins> tags.

4677+ - Moved htmlBlock after para in list of block parsers. This ensures

4678+ that tags that can be either block or inline get parsed as inline

4679+ when appropriate.

4680+ - Modified rawHtmlInline' so that block elements aren't treated as

4681+ inline.

4682+ - Modified para parser so that paragraphs containing only HTML tags and

4683+ blank space are not allowed. Treat these as raw HTML blocks instead.

4684+

4685+ + Fixed bug wherein HTML preceding a code block could cause it to

4686+ be parsed as a paragraph. The problem is that the HTML parser

4687+ used to eat all blank space after an HTML block, including the

4688+ indentation of the code block. (Resolves Issue #39.)

4689+ - In Text.Pandoc.Readers.HTML, removed parsing of following space

4690+ from rawHtmlBlock.

4691+ - In Text.Pandoc.Readers.Markdown, modified rawHtmlBlocks so that

4692+ indentation is eaten *only* on the first line after the HTML

4693+ block. This means that in

4694+ <div>

4695+ foo

4696+ <div>

4697+ the foo won't be treated as a code block, but in

4698+ <div>

4699+

4700+ foo

4701+

4702+ </div>

4703+ it will. This seems the right approach for least surprise.

4704+

4705+ * RST reader:

4706+

4707+ + Fixed bug in parsing explicit links (resolves Issue #44).

4708+ The problem was that we were looking for inlines until a '<' character

4709+ signaled the start of the URL; so, if you hit a reference-style link,

4710+ it would keep looking til the end of the document. Fix: change

4711+ inline => (notFollowedBy (char '`') >> inline). Note that this won't

4712+ allow code inlines in links, but these aren't allowed in resT anyway.

4713+

4714+ + Cleaned up parsing of reference names in key blocks and links.

4715+ Allow nonquoted reference links to contain isolated '.', '-', '_', so

4716+ so that strings like 'a_b_' count as links.

4717+

4718+ + Removed unnecessary check for following link in str.

4719+ This is unnecessary now that link is above str in the definition of

4720+ 'inline'.

4721+

4722+ * HTML reader:

4723+

4724+ + Modified rawHtmlBlock so it parses </html> and </body> tags.

4725+ This allows these tags to be handled correctly in Markdown.

4726+ HTML reader now uses rawHtmlBlock', which excludes </html> and </body>,

4727+ since these are handled in parseHtml. (Resolves Issue #38.)

4728+

4729+ + Fixed bug (emph parser was looking for `<IT>` tag, not `<I>`).

4730+

4731+ + Don't interpret contents of style tags as markdown.

4732+ (Resolves Issue #40.)

4733+ - Added htmlStyle, analagous to htmlScript.

4734+ - Use htmlStyle in htmlBlockElement and rawHtmlInline.

4735+ - Moved "script" from the list of tags that can be either block or

4736+ inline to the list of block tags.

4737+

4738+ + Modified rawHtmlBlock to use anyHtmlBlockTag instead of anyHtmlTag

4739+ and anyHtmlEndTag. This fixes a bug in markdown parsing, where

4740+ inline tags would be included in raw HTML blocks.

4741+

4742+ + Modified anyHtmlBlockTag to test for (not inline) rather than

4743+ directly for block. This allows us to handle e.g. docbook in

4744+ the markdown reader.

4745+

4746+ * LaTeX reader: Properly recognize --parse-raw in rawLaTeXInline.

4747+ Updated LaTeX reader test to use --parse-raw.

4748+

4749+ * HTML writer:

4750+

4751+ + Modified rules for automatic HTML header identifiers to

4752+ ensure that identifiers begin with an alphabetic character.

4753+ The new rules are described in README. (Resolves Issue #33.)

4754+

4755+ + Changed handling of titles in HTML writer so you don't get

4756+ "titleprefix - " followed by nothing.

4757+

4758+ * ConTeXt writer: Use wrappers around Doc elements to ensure proper

4759+ spacing. Each block element is wrapped with either Pad or Reg.

4760+ Pad'ed elements are guaranteed to have a blank line in between.

4761+

4762+ * RST writer:

4763+

4764+ + Refactored RST writer to use a record instead of a tuple for state,

4765+ and to include options in state so it doesn't need to be passed as

4766+ a parameter.

4767+

4768+ + Use an interpreted text role to render math in restructuredText.

4769+ See http://www.american.edu/econ/itex2mml/mathhack.rst for the

4770+ strategy.

4771+

4772+ [ Recai Oktaş ]

4773+

4774+ * Debian packaging changes:

4775+

4776+ + Remove the empty 'include' directory in -dev package, which lintian

4777+ complains about.

4778+ + Bump Standarts-Version to 3.7.3.

4779+ + Use new 'Homepage:' field to specify the upstream URL on suggestion of

4780+ lintian.

4781+

4782+ -- Recai Oktaş <roktas@debian.org> Tue, 08 Jan 2008 05:13:31 +0200

4783+

4784+pandoc (0.45) unstable; urgency=low

4785+

4786+ [ John MacFarlane ]

4787+

4788+ * Simplified parsing of reference keys and notes in markdown and RST

4789+ readers: The Reference data structure from Text.Pandoc.Shared is no

4790+ longer needed, since referenceKey and noteBlock parses return strings

4791+ (as many blank lines as were occupied by the key or note) and update

4792+ state themselves. getPosition and setPosition are now used to ensure

4793+ that error messages will give the correct line number. This yields

4794+ cleaner (and slightly faster) code, with more accurate parsing error

4795+ messages.

4796+

4797+ * Added new Math inline element:

4798+

4799+ + Markdown and LaTeX readers now convert TeX math into Math elements,

4800+ not TeX.

4801+ + This allows math to be treated differently from raw TeX in output.

4802+ TeX elements are no longer printed in output formats other than

4803+ Markdown, LaTeX, and ConTeXt. But Math elements are always printed.

4804+

4805+ * New default handling of math in writers:

4806+

4807+ + New module Text.Pandoc.Readers.TeXMath exports readTeXMath, which

4808+ parses raw TeX math and outputs a string of Pandoc inlines that

4809+ tries to render it as far as possible using unicode characters,

4810+ lapsing into literal TeX when needed.

4811+ + readTeXMath is now used for default HTML output in HTML, S5, RTF,

4812+ and Docbook, if no other method for displaying math in HTML is

4813+ specified. Enclosing $'s are no longer printed by default.

4814+ + By default, math is put inside `<span class="math">`. This way it can be

4815+ distinguished from the surrounding text, e.g. put in a different

4816+ font.

4817+

4818+ * New --gladtex and --mimetex options for display of math in HTML:

4819+

4820+ + If --gladtex is specified, math is output between `<eq>` tags, so

4821+ it can be processed by gladTeX.

4822+ + If --mimetex is specified, math is put in `<img>` tags with a link

4823+ to the mimetex CGI script (or any other script that takes TeX math

4824+ as input and outputs an image). The URL of the script may be

4825+ specified, but defaults to /cgi-bin/mimetex.cgi.

4826+ + HTMLMathMethod structure in WriterOptions keeps track of how to

4827+ display math in HTML output.

4828+ + Updated README with a description of the four options for displaying

4829+ math in HTML.

4830+

4831+ * HTML reader:

4832+

4833+ + Fixed bug: parser for minimized attributes should not swallow

4834+ trailing spaces.

4835+ + Simplified HTML attribute parsing.

4836+ + Changed parsing of code blocks in HTML reader: `<code>` tag is no

4837+ longer needed. `<pre>` suffices. All HTML tags in the code block

4838+ (e.g. for syntax highlighting) are skipped, because they are not

4839+ portable to other output formats. A `<code>...</code>` block not

4840+ surrounded by `<pre>` now counts as inline HTML, not a code block.

4841+ + Remove just one leading and one trailing newline from contents of

4842+ `<pre>...</pre>` in codeBlock parser.

4843+

4844+ * Markdown reader:

4845+

4846+ + Removed support for box-style block quotes.

4847+ + Require space before title in links and references.

4848+ This fixes a bug in parsing URLs like http://silly/url(withparen).

4849+ + Improved and simplified setextHeader parser.

4850+ + Fixed logic in smart quote parsing, adding some needed 'try'

4851+ statements.

4852+ + Fixed smart quote parsing so that unicode characters 8216 and 8217

4853+ are recognized as single quotes, and 8220 and 8221 as double quotes.

4854+

4855+ * RST reader:

4856+

4857+ + Fixed bug in parsing of code blocks. Previously a full tab indent

4858+ was required, but RST allows code to be indented any amount.

4859+ Resolves Issue #27.

4860+ + Allow field lists to be indented.

4861+ + Parse the contents of field lists instead of treating as a raw string.

4862+ + Represent field lists as definition lists instead of blockquotes.

4863+ + Fixed bug in which metadata would be overridden if the document

4864+ contained multiple field lists.

4865+ + Parse fields associated with '.. image::' blocks, and use 'alt'

4866+ field, if given, for image alt and title attributes.

4867+

4868+ * LaTeX reader:

4869+

4870+ + Modified specialChar so that '"' characters are parsed.

4871+ + Fixed a bug in parsing of \[ \] math blocks (thanks to Mark Kalderon).

4872+

4873+ * HTML writer:

4874+

4875+ + Changes in handling of math (see above).

4876+ + Don't produce HTML for table of contents if there are

4877+ no headers. (This would be an empty list, which is invalid XHTML.)

4878+

4879+ * Markdown writer:

4880+

4881+ + Don't print title attribute if title is empty. (This differs from

4882+ the behavior of Markdown.pl, and agrees with PHP Markdown. But John

4883+ Gruber has indicated that he prefers this behavior.) Adjusted test

4884+ suite accordingly.

4885+ + Fixed incorrect line wrapping in paragraphs including hard line

4886+ breaks. Resolves Issue #25.

4887+ + Fixed bug in markdown writer: If an ordered list item began with

4888+ a marker greater than 3 characters in width, and the item took more

4889+ than one line, it would appear on the line after the list marker,

4890+ e.g.:

4891+

4892+ (12)

4893+ My list item.

4894+ Multiline.

4895+

4896+ Now it works as follows:

4897+

4898+ (12) My list item.

4899+ Multiline.

4900+

4901+ * RST writer

4902+

4903+ + Fixed bug in RST writer's handling of ordered lists. Previously,

4904+ list items with multiple lines would not always line up with

4905+ single-line list items. Now, list items are nested the length of

4906+ the list marker + 1. This looks better and ensures that list items

4907+ all line up. (Note that list markers are padded to the length of

4908+ the longest list marker in the series.)

4909+ + Use 3-space indent for unordered lists.

4910+ + If label for a link reference contains a colon, surround it by `

4911+ signs so it won't be interpreted as the end of the link label.

4912+

4913+ * LaTeX writer:

4914+

4915+ + Cleaner output for footnotes. Footnotes now always begin on a new

4916+ line, and the final } is on a line by itself only when it needs to

4917+ be (i.e. only when the note ends with a Verbatim environment).

4918+ + Added writer options to state, so state doesn't need to be passed as

4919+ a parameter.

4920+ + Text wrapping now provided, using wrapTeXIfNeeded.

4921+

4922+ * ConTeXt writer: many improvements for more idiomatic ConTeXt output

4923+ (thanks to Idris Samawi Hamid for suggestions).

4924+

4925+ + PrettyPrint module now used for output.

4926+ + Writer options are now in state, so they don't have to be passed as

4927+ a parameter.

4928+ + Text wrapping now provided, using wrapTeXIfNeeded.

4929+ + Better treatment of footnotes: footnotes are always on lines by

4930+ themselves, and the final } is on a line by itself only when

4931+ it needs to be (after \stoptyping).

4932+ + Use \subject, \subsubject, ... or \section, \subsection, ... for headings,

4933+ depending on whether --number-sections option is selected.

4934+ + Extra blank line inserted after \stopitemize

4935+ + Use new, "official" definition of blockquote environment. Also, use

4936+ blank line after \startblockquote to balance blank line at the end.

4937+ + Both itemized and enumerated lists are now generated using

4938+ \start-stopitemize, with appropriate options. Removed definitions

4939+ of ltxenum and ltxitem, which are no longer needed. Provided

4940+ defaults for itemized lists in the preamble. State keeps track of

4941+ ordered list level, so that when default numbering is specified,

4942+ the appropriate scheme can be used.

4943+ + Changed \useurl to \useURL.

4944+ + Changed link color from red to blue.

4945+ + Use \subsubsubsubsection etc., since these are supported

4946+ (up to at least sub x 5).

4947+

4948+ * Text.Pandoc.Shared:

4949+

4950+ + Save and restore position in parseFromString, so that accurate

4951+ error messages can be given.

4952+ + Improved efficiency of romanNumeral parser.

4953+ + Added wrappedTeX and wrapTeXIfNeeded functions. These ensure

4954+ that footnotes occur on lines by themselves (to make them

4955+ easier to see and move) and do not screw up line wrapping.

4956+

4957+ * Text.Pandoc.UTF8: modified fromUTF8 to strip out the BOM

4958+ if present. Windows Notepad and other applications insert a

4959+ BOM at the beginning of a UTF8 file.

4960+

4961+ * Main.hs (tabFilter): Treat '\r' at end of line as newline (in

4962+ addition to "\r\n" and '\n').

4963+

4964+ * Added a writer option for wrapped text and a command-line option

4965+ '--no-wrap', which disables text wrapping and minimizes whitespace

4966+ in HTML. (Resolves Issue #26.)

4967+

4968+ + Added support for '--no-wrap' to Main.hs.

4969+ + Added wrapIfNeeded function to Text.Pandoc.Shared.

4970+ + Use wrapIfNeeded instead of wrapped in the RST, Man, Docbook, and

4971+ Markdown writers.

4972+ + Added render and renderFragment helpers to HTML writer.

4973+

4974+ * Modified html2markdown to run tidy only if the HTML cannot be

4975+ parsed. Previously html2markdown piped all input through tidy

4976+ before passing it to pandoc. This caused problems on certain pages

4977+ (e.g. http://daringfireball.com/markdown) which have well-formed

4978+ XHTML that causes tidy to choke. The solution is to pipe through

4979+ tidy only if pandoc cannot parse the input by itself. This means

4980+ that a temp file is now always used, even when input comes from a

4981+ local file or standard input.

4982+

4983+ * Removed 'version' constant from Main.hs; added 'pandocVersion' to

4984+ Text.Pandoc library.

4985+

4986+ * pandoc.cabal:

4987+

4988+ + Modified to work with GHC 6.8 and Cabal configurations. (For GHC

4989+ 6.8, pretty and containers must be added to Build-Depends, and it

4990+ is desirable to use the -O2 compiler option.) Cabal configurations

4991+ allows one to select options depending on the compiler version.

4992+ For GHC 6.6, the splitBase option can be disabled.

4993+ + pandoc.cabal.ghc66 is provided for users with older versions of

4994+ Cabal, which do not support configurations.

4995+ + Use Ghc-Prof-Options to ensure that '-auto-all' is used when

4996+ '--enable-(executable|library)-profiling' is specified. Updated

4997+ PROFILING instructions accordingly.

4998+

4999+ * Makefile:

5000+

5001+ + Makefile now checks GHC version. If GHC is 6.6, pandoc.cabal.ghc66

5002+ is copied to pandoc.cabal, and the old pandoc.cabal is copied

5003+ to pandoc.cabal.orig. Otherwise, pandoc.cabal is copied to

5004+ pandoc.cabal.orig but otherwise unmodified. This way, the Makefile

5005+ will work properly with either GHC 6.6 or 6.8.

5006+ + Changed BUILDCONF to point to dist/setup-config, not .setup-config.

5007+ This is where current versions of Cabal put it.

5008+ + Added $(BUILDCMD) target, so setup doesn't get compiled every time.

5009+ + Removed dependency of templates on ./templates, which is circular

5010+ now that templates is a subdirectory of the top-level.

5011+

5012+ * MacPorts Portfile:

5013+

5014+ + Modified to install the pandoc library in addition to programs.

5015+ + Installation must be done manually rather than using Makefile's

5016+ install-all.

5017+ + Note that the library must be registered in the activate phase,

5018+ after the library files have been copied out of the destroot.

5019+ Cabal generates a 'register.sh' script that will do this.

5020+

5021+ * debian/control: Added libghc6-network-dev, libghc6-xhtml-dev, and

5022+ libghc6-mtl-dev as dependencies for libghc6-pandoc-dev.

5023+ Closes: #445235

5024+

5025+ * debian/rules: Converted to UTF-8.

5026+

5027+ * Changed pandoc home page to http://johnmacfarlane.net/pandoc/.

5028+

5029+ * Updated ASCIIMathML.js to latest version.

5030+

5031+ * Directory structure:

5032+

5033+ + Moved everything from src into the top-level directory.

5034+ + Changed references to source directory in Makefile and

5035+ pandoc.cabal.*.

5036+ + Moved ASCIIMathML.js, headers, and ui into templates directory.

5037+ + Modified fillTemplates.pl to reflect new paths.

5038+

5039+ [ Recai Oktaş ]

5040+

5041+ * Makefile: Fixed the issue of having two copies of the library

5042+ documentation under some usage scenarios.

5043+

5044+ * Replaced 'ghc' with '$(GHC)' in Makefile, and made GHC

5045+ and GHC_PKG configurable through the environment, to support

5046+ unusual ghc installations. For example:

5047+ GHC=/opt/ghc/bin/ghc GHC_PKG=/opt/ghc/bin/ghc-pkg make

5048+

5049+ -- Recai Oktaş <roktas@debian.org> Sun, 07 Oct 2007 20:51:43 +0300

5050+

5051+pandoc (0.44) unstable; urgency=low

5052+

5053+ [ John MacFarlane ]

5054+

5055+ * Fixed bug in HTML writer: when --toc was used, anchors were put around

5056+ headers, which is invalid XHTML (block content within inline element).

5057+ Now the anchors are put inside the header tags. Resolves Issue #23.

5058+

5059+ * Added xmlns attribute to html element in html writer tests.

5060+ This attribute is added by more recent versions of the

5061+ xhtml library (>= 3000), and is required for valid XHTML.

5062+

5063+ [ Recai Oktaş ]

5064+

5065+ * On configure, compile 'Setup.hs' to 'setup' and use 'setup' as the build

5066+ command instead of 'runhaskell', which, on some platforms (such as s390,

5067+ alpha, m68k), throws the following error:

5068+

5069+ runhaskell Setup.hs configure --prefix=/usr

5070+ ghc-6.6.1: not built for interactive use

5071+

5072+ This causes a serious FTBFS bug. Closes: #440668.

5073+

5074+ -- Recai Oktaş <roktas@debian.org> Mon, 03 Sep 2007 18:24:02 +0300

5075+

5076+pandoc (0.43) unstable; urgency=low

5077+

5078+ [ John MacFarlane ]

5079+

5080+ * The focus of this release is performance. The markdown parser

5081+ is about five times faster than in 0.42, based on benchmarks

5082+ with the TextMate manual.

5083+

5084+ * Main.hs: Replaced CRFilter and tabFilter with single function

5085+ tabFilter, which operates on the whole string rather than breaking

5086+ it into lines, and handles dos-style line-endings as well as tabs.

5087+

5088+ * Added separate LaTeX reader and native reader tests; removed

5089+ round-trip tests.

5090+

5091+ * Text.Pandoc.Shared:

5092+

5093+ + Removed tabsToSpaces and tabsInLine (they were used only in Main.hs.)

5094+ + General code cleanup (to elimante warnings when compiling with -Wall.)

5095+ + Added 'wrapped' function, which helps wrap text into paragraphs,

5096+ using the prettyprinting library.

5097+ + Rewrote charsInBalanced and charsInBalanced'.

5098+ - Documented restriction: open and close must be distinct characters.

5099+ - Rearranged options for greater efficiency.

5100+ - Bug fix: Changed inner call to charsInBalanced inside

5101+ charsInBalanced' to charsInBalanced'.

5102+ + anyLine now requires that the line end with a newline (not eof).

5103+ This is a harmless assumption, since we always add newlines to the

5104+ end of a block before parsing with anyLine, and it yields a 10% speed

5105+ boost.

5106+ + Removed unnecessary 'try' in anyLine.

5107+ + Removed unneeded 'try' from romanNumeral parser.

5108+ + Use notFollowedBy instead of notFollowedBy' in charsInBalanced.

5109+ + Removed unneeded 'try' in parseFromString.

5110+ + Removed unneeded 'try' from stringAnyCase. (Now it behaves

5111+ like 'string'.)

5112+ + Changed definition of 'enclosed' in Text.Pandoc.Shared so that

5113+ 'try' is not automatically applied to the 'end' parser. Added

5114+ 'try' in calls to 'enclosed' where needed. Slight speed increase.

5115+

5116+ * Writers:

5117+

5118+ + Replaced individual wrapping routines in RST, Man, and Markdown

5119+ writers with 'wrapped' from Text.Pandoc.Shared.

5120+ + Rewrote LaTeX writer to use the prettyprinting library,

5121+ so we get word wrapping, etc.

5122+ + Modified latex writer tests for new latex writer using prettyprinter.

5123+ + Fixed bug in LaTeX writer: autolinks would not cause

5124+ '\usepackage{url}' to be put in the document header. Also, changes

5125+ to state in enumerated list items would be overwritten.

5126+ + In Markdown writer, escape paragraphs that begin with ordered list

5127+ markers, so they don't get interpreted as ordered lists.

5128+

5129+ * Text.Pandoc.Reades.LaTeX:

5130+

5131+ + Fixed bug in LaTeX reader, which wrongly assumed that the roman

5132+ numeral after "enum" in "setcounter" would consist entirely of

5133+ "i"s. 'enumiv' is legitimate.

5134+ + LaTeX command and environment names can't contain numbers.

5135+ + Rearranged order of parsers in inline for slight speed improvement.

5136+ + Added '`' to special characters and 'unescapedChar'.

5137+

5138+ * Text.Pandoc.Readers.RST:

5139+

5140+ + Removed unneeded try's in RST reader; also minor code cleanup.

5141+ + Removed tabchar.

5142+ + Rearranged parsers in inline (doubled speed).

5143+

5144+ * Text.Pandoc.Readers.Markdown:

5145+

5146+ + Skip notes parsing if running in strict mode. (This yields a nice

5147+ speed improvement in strict mode.)

5148+ + Simplify autolink parsing code, using Network.URI to test for

5149+ URIs. Added dependency on network library to debian/control and

5150+ pandoc.cabal.

5151+ + More perspicuous definition of nonindentSpaces.

5152+ + Removed unneeded 'try' in 'rawLine'.

5153+ + Combined linebreak and whitespace into a new whitespace parser, to

5154+ avoid unnecessary reparsing of space characters.

5155+ + Removed unnecessary 'try' in 'codeBlock', 'ellipses', 'noteMarker',

5156+ 'multilineRow', 'dashedLine', 'rawHtmlBlocks'.

5157+ + Use lookAhead in parsers for setext headers and definition lists

5158+ to see if the next line begins appropriately; if not, don't waste

5159+ any more time parsing.

5160+ + Don't require blank lines after code block. (It's sufficient to

5161+ end code block with a nonindented line.)

5162+ + Changed definition of 'emph': italics with '_' must not

5163+ be followed by an alphanumeric character. This is to help

5164+ prevent interpretation of e.g. `[LC_TYPE]: my_type` as

5165+ `[LC<em>TYPE]:my</em>type`.

5166+ + Improved Markdown.pl-compatibility in referenceLink: the two parts

5167+ of a reference-style link may be separated by one space, but not

5168+ more... [a] [link], [not] [a link].

5169+ + Fixed markdown inline code parsing so it better accords with

5170+ Markdown.pl: the marker for the end of the code section is a clump

5171+ of the same number of `'s with which the section began, followed

5172+ by a non-` character. So, for example,

5173+ ` h ``` i ` -> `<code>h ``` i</code>`.

5174+ + Split 'title' into 'linkTitle' and 'referenceTitle', since the

5175+ rules are slightly different.

5176+ + Rewrote 'para' for greater efficiency.

5177+ + Rewrote link parsers for greater efficiency.

5178+ + Removed redundant 'referenceLink' in definition of inline (it's

5179+ already in 'link').

5180+ + Refactored escapeChar so it doesn't need 'try'.

5181+ + Refactored hrule for performance in Markdown reader.

5182+ + More intelligent rearranging of 'inline' so that most frequently

5183+ used parsers are tried first.

5184+ + Removed tabchar parser, as whitespace handles tabs anyway.

5185+

5186+ * Text.Pandoc.CharacterReferences:

5187+

5188+ + Refactored.

5189+ + Removed unnecessary 'try's for a speed improvement.

5190+ + Removed unnecessary '&' and ';' from the entity table.

5191+

5192+ * Build process:

5193+

5194+ + Makefile: Get VERSION from cabal file, not Main.hs.

5195+ + Modified MacPorts Portfile:

5196+ - Depend on haddock

5197+ - Build and install libraries and library documentation in

5198+ addition to pandoc executable

5199+ - Added template item for md5 sum in Portfile.in.

5200+ - Incorporated changes from MacPorts repository (r28278).

5201+ + FreeBSD port: Don't try to generate distinfo in Makefile.

5202+ It can be made using 'make makesum' in FreeBSD.

5203+ + Make both freebsd and macports targets depend on tarball.

5204+

5205+ * Website and documentation:

5206+

5207+ + Updated INSTALL instructions.

5208+ + Added pandocwiki demo to website.

5209+ + Removed local references to Portfile, since pandoc is now in the

5210+ MacPorts repository.

5211+

5212+ -- Recai Oktaş <roktas@debian.org> Sun, 02 Sep 2007 15:50:11 +0300

5213+

5214+pandoc (0.42) unstable; urgency=low

5215+

5216+ [ John MacFarlane ]

5217+

5218+ * Main.hs: Use utf8 conversion on the extra files loaded with

5219+ the -H, -C, -B, and -A options. This fixes problems with unicode

5220+ characters in these files.

5221+

5222+ * Exposed Text.Pandoc.ASCIIMathML, since it is imported in

5223+ Text.Pandoc.Readers.HTML and without it we get a linking error when

5224+ using the library.

5225+

5226+ * Markdown reader:

5227+

5228+ + Added new rule for enhanced markdown ordered lists: if the list

5229+ marker is a capital letter followed by a period (including a

5230+ single-letter capital roman numeral), then it must be followed by

5231+ at least two spaces. The point of this is to avoid accidentally

5232+ treating people's initials as list markers: a paragraph might begin,

5233+ "B. Russell was an English philosopher," and this shouldn't be

5234+ treated as a list. Documented change in README.

5235+ + Blocks that start with "p. " and a digit are no longer treated

5236+ as ordered lists (it's a page number).

5237+ + Added a needed 'try' to listItem.

5238+ + Removed check for a following setext header in endline.

5239+ A full test is too inefficient (doubles benchmark time), and the

5240+ substitute we had before is not 100% accurate.

5241+ + Don't use Code elements for autolinks if --strict specified.

5242+

5243+ * LaTeX writer: When a footnote ends with a Verbatim environment, the

5244+ close } of the footnote cannot occur on the same line or an error occurs.

5245+ Fixed this by adding a newline before the closing } of every footnote.

5246+

5247+ * HTML writer:

5248+ + Removed incorrect "{}" around style information in HTML tables.

5249+ Column widths now work properly in HTML.

5250+ + If --strict option is specified (and --toc is not), don't include

5251+ identifiers in headers, for better Markdown compatibility.

5252+

5253+ * Build process:

5254+

5255+ + Separated $(web_dest) and website targets.

5256+ + In website, index.txt is now constructed from template index.txt.in.

5257+ + Added freebsd target to Markefile. This creates the freebsd Makefile

5258+ from Makefile.in, and creates distinfo. Removed Makefile and distinfo

5259+ from the repository.

5260+ + Added macport target to Makefile. Portfile is built from template

5261+ Portfile.in.

5262+ + Removed OSX package targets. (Too many difficulties involving

5263+ dependencies on dynamic libraries.)

5264+ + More complete INSTALL instructions for all architectures.

5265+

5266+ * Website:

5267+ + Added a programming demo, pandocwiki.

5268+

5269+ [ Recai Oktaş ]

5270+

5271+ * Do not forget to close pandoc's ITP. Closes: #391666

5272+

5273+ -- Recai Oktaş <roktas@debian.org> Sun, 26 Aug 2007 22:51:32 +0300

5274+

5275+pandoc (0.41) unstable; urgency=low

5276+

5277+ [ John MacFarlane ]

5278+

5279+ * Fixed bugs in HTML reader:

5280+ + Skip material at end *only if* `</html>` is present (previously,

5281+ only part of the document would be parsed if an error was

5282+ found; now a proper error message is given).

5283+ + Added new constant eitherBlockOrInline with elements that may

5284+ count either as block-level or as inline. Modified isInline and

5285+ isBlock to take this into account.

5286+ + Modified rawHtmlBlock to accept any tag (even an inline tag):

5287+ this is innocuous, because rawHtmlBlock is tried only if a regular

5288+ inline element can't be parsed.

5289+ + Added a necessary 'try' in definition of 'para'.

5290+

5291+ * Fixed bug in markdown ordered list parsing. The problem was that

5292+ anyOrderedListStart did not check for a space following the

5293+ ordered list marker. So in 'A.B. 2007' the parser would be

5294+ expecting a list item, but would not find one, causing an error.

5295+ Fixed a similar bug in the RST reader. Resolves Issue #22.

5296+

5297+ * Refactored RST and Markdown readers using parseFromString.

5298+

5299+ * LaTeX reader will now skip anything after \end{document}.

5300+

5301+ * Fixed blockquote output in markdown writer: previously, block

5302+ quotes in indented contexts would be indented only in the first

5303+ line.

5304+

5305+ * Added note to INSTALL about variations in versions of the xhtml

5306+ library that can lead to failed tests (thanks to Leif LeBaron).

5307+

5308+ -- Recai Oktaş <roktas@debian.org> Sun, 19 Aug 2007 23:26:07 +0300

5309+

5310+pandoc (0.4) unstable; urgency=low

5311+

5312+ [ John MacFarlane ]

5313+

5314+ * Added two new output formats: groff man pages and ConTeXt. By

5315+ default, output files with extensions ".ctx" and ".context" are

5316+ assumed to be ConTeXt, and output files with single-digit extensions

5317+ are assumed to be man pages.

5318+

5319+ * Enhanced ordered lists (documented in README, under Lists):

5320+ + The OrderedList block element now stores information about

5321+ list number style, list number delimiter, and starting number.

5322+ + The readers parse this information when possible.

5323+ + The writers use this information to style ordered lists.

5324+ + The enhancement can be disabled using the --strict option.

5325+

5326+ * Added support for tables (with a new Table block element). Two kinds

5327+ of tables are supported: a simple table with one-line rows, and a

5328+ more complex variety with multiline rows. All output formats are

5329+ supported, but only markdown tables are parsed at the moment. The

5330+ syntax is documented in README.

5331+

5332+ * Added support for definition lists (with a new DefinitionList block

5333+ element). All output and input formats are supported. The syntax is

5334+ documented in README.

5335+

5336+ * Added support for superscripts and subscripts (with new Superscript

5337+ and Subscript inline elements). All input and output

5338+ formats. The syntax is documented in README.

5339+

5340+ * Added support for strikeout (with a new Strikeout inline element).

5341+ All input and output formats are supported. Thanks to Bradley Kuhn,

5342+ who contributed a patch. The syntax is documented in README. Resolves

5343+ Issue #18.

5344+

5345+ * Added a --toc|--table-of-contents option. This causes an automatically

5346+ generated table of contents (or an instruction that creates one) to

5347+ be inserted at the beginning of the document. Not supported in S5,

5348+ DocBook, or man page writers.

5349+

5350+ * Modified the -m|--asciimathml option:

5351+

5352+ + If an optional URL argument is provided, a link is inserted

5353+ instead of the contents of the ASCIIMathML.js script.

5354+ + Nothing is inserted unless the document actually contains

5355+ LaTeX math.

5356+

5357+ * Removed Blank block element as unnecessary.

5358+

5359+ * Removed Key and Note blocks from the Pandoc data structure. All

5360+ links are now stored as explicit links, and note contents are

5361+ stored with the (inline) notes.

5362+

5363+ + All link Targets are now explicit (URL, title) pairs; there

5364+ is no longer a 'Ref' target.

5365+ + Markdown and RST parsers now need to extract data from key and

5366+ note blocks and insert them into the relevant inline elements.

5367+ Other parsers have been simplified, since there is no longer any need

5368+ to construct separate key and note blocks.

5369+ + Markdown, RST, and HTML writers need to construct lists of

5370+ notes; Markdown and RST writers need to construct lists of link

5371+ references (when the --reference-links option is specified); and

5372+ the RST writer needs to construct a list of image substitution

5373+ references. All writers have been rewritten to use the State monad

5374+ when state is required.

5375+ + Several functions (generateReference, keyTable,

5376+ replaceReferenceLinks, replaceRefLinksBlockList, and some auxiliaries

5377+ used by them) have been removed from Text.Pandoc.Shared, since

5378+ they are no longer needed. New functions and data structures

5379+ (Reference, isNoteBlock, isKeyBlock, isLineClump) have been

5380+ added. The functions inTags, selfClosingTag, inTagsSimple, and

5381+ inTagsIndented have been moved to the DocBook writer, since that

5382+ is now the only module that uses them. NoteTable is now exported

5383+ in Text.Pandoc.Shared.

5384+ + Added stateKeys and stateNotes to ParserState; removed stateKeyBlocks,

5385+ stateKeysUsed, stateNoteBlocks, stateNoteIdentifiers, stateInlineLinks.

5386+ + Added writerNotes and writerReferenceLinks to WriterOptions.

5387+

5388+ * Added Text.Pandoc module that exports basic readers, writers,

5389+ definitions, and utility functions. This should export everything

5390+ needed for most uses of Pandoc libraries. The haddock documentation

5391+ includes a short example program.

5392+

5393+ * Text.Pandoc.ASCIIMathML is no longer an exported module.

5394+

5395+ * Added Text.Pandoc.Blocks module to help in printing markdown

5396+ and RST tables. This module provides functions for working with

5397+ fixed-width blocks of text--e.g., placing them side by side, as

5398+ in a table row.

5399+

5400+ * Refactored to avoid reliance on Haskell's Text.Regex library, which

5401+ (a) is slow, and (b) does not properly handle unicode. This fixed

5402+ some strange bugs, e.g. in parsing S-cedilla, and improved performance.

5403+

5404+ + Replaced 'gsub' with a general list function 'substitute'

5405+ that does not rely on Text.Regex.

5406+ + Rewrote extractTagType in HTML reader so that it doesn't use

5407+ regexs.

5408+ + In Markdown reader, replaced email regex test with a custom email

5409+ autolink parser (autoLinkEmail). Also replaced selfClosingTag regex

5410+ with a custom function isSelfClosingTag.

5411+ + Modified Docbook writer so that it doesn't rely on Text.Regex for

5412+ detecting 'mailto' links.

5413+ + Removed escapePreservingRegex and reamped entity-handling

5414+ functions in Text.Pandoc.Shared and Text.Pandoc.CharacterReferences to

5415+ avoid reliance on Text.Regex (see below on character reference

5416+ handling changes).

5417+

5418+ * Renamed Text.Pandoc.Entities as Text.Pandoc.CharacterReferences.

5419+

5420+ * Changed handling of XML entities. Entities are now parsed (and unicode

5421+ characters returned) in the Markdown and HTML readers, rather than being

5422+ handled in the writers. In HTML and Docbook writers, UTF-8 is now used

5423+ instead of entities for characters above 128. This makes the HTML and

5424+ DocBook output much more readable and more easily editable.

5425+

5426+ + Removed sgmlHexEntity, sgmlDecimalEntity, sgmlNamedEntity, and

5427+ sgmlCharacterEntity regexes from Text.Pandoc.Shared.

5428+ + Renamed escapeSGMLChar to escapeCharForXML. Added escapeStringForXML.

5429+ Moved both functions to Text.Pandoc.Writers.Docbook.

5430+ + Added characterReference parser to Text.Pandoc.CharacterReferences.

5431+ This parses a string and return a unicode character.

5432+ + Rewrote decodeCharacterReferences to use the new parser instead of

5433+ Text.Regex.

5434+ + Added new charRef parser for Markdown and HTML, which replaces the

5435+ old 'entity' parser. Added '&' as a special character in Markdown reader.

5436+ + Modified HTML and Markdown readers to call decodeEntities on all raw

5437+ strings (e.g. authors, dates, link titles), to ensure that no

5438+ unprocessed entities are included in the native representation of

5439+ the document. (In the HTML reader, most of this work is done by a

5440+ change in extractAttributeName.)

5441+ + In XML and Markdown output, escape unicode nonbreaking space as '&nbsp;',

5442+ since a unicode non-breaking space is impossible to distinguish visually

5443+ from a regular space. (Resolves Issue #3.)

5444+ + Removed encodeEntitiesNumerical.

5445+ + Use Data.Map for entityTable and (new) reverseEntityTable, for a

5446+ slight performance boost over the old association list.

5447+ + Removed unneeded decodeEntities from 'str' parser in HTML and

5448+ Markdown readers.

5449+

5450+ * Text.Pandoc.UTF8: Renamed encodeUTF8 to toUTF8, decodeUTF8 to

5451+ fromUTF8, for clarity.

5452+

5453+ * Replaced old haskell98 module names replaced by hierarchical module

5454+ names, e.g. List by Data.List. Removed haskell98 from dependencies

5455+ in pandoc.cabal, and added mtl (needed for state monad). Substituted

5456+ xhtml for html.

5457+

5458+ * Refactored and cleaned up character escaping in writers, using

5459+ backslashEscapes and escapeStringUsing functions.

5460+

5461+ * Instead of adding "\n\n" to the end of an input string in Main.hs,

5462+ this is now done in the readers. This makes the libraries behave

5463+ the way you'd expect from the pandoc program. Resolves Issue #10.

5464+

5465+ * URLs and email addresses in autolinks are now typeset as Code.

5466+

5467+ * In Main.hs, changed putStr to putStrLn -- mainly because MacOS X

5468+ doesn't display the whole output unless there's a line ending.

5469+

5470+ * Major code cleanup in all modules, for greater consistency, concision,

5471+ and readability.

5472+

5473+ * HTML reader:

5474+

5475+ + Fixed several bugs (extractTagType, attribute parsing).

5476+ + Remove Null blocks in lists of blocks when possible.

5477+ + Allow HTML comments as raw HTML inline.

5478+

5479+ * Markdown reader:

5480+

5481+ + Ordered list items may no longer begin with uppercase letters, or

5482+ letters greater than 'n'. (This prevents first initials and page

5483+ reference, e.g. 'p. 400', from being parsed as beginning lists.)

5484+ Also, numbers beginning list items may no longer end with ')',

5485+ which is now allowed only after letters. Note: These changes

5486+ may cause documents to be parsed differently. Users should take

5487+ care in upgrading.

5488+ + Changed autoLink parsing to conform better to Markdown.pl's

5489+ behavior. `<google.com>` is not treated as a link, but

5490+ `<http://google.com>`, `<ftp://google.com>`, and

5491+ `<mailto:google@google.com>` are.

5492+ + Cleaned up handling of embedded quotes in link titles. Now these are

5493+ stored as a '"' character, not as '&quot;'.

5494+ + Use lookAhead parser for the 'first pass' (looking for reference keys),

5495+ instead of parsing normally, then using setInput to reset input. This

5496+ yields a slight performance boost.

5497+ + Fixed several bugs in smart quote recognition.

5498+ + Fixed bug in indentSpaces (which didn't properly handle

5499+ cases with mixed spaces and tabs).

5500+ + Consolidated 'text', 'special', and 'inline' into 'inline'.

5501+ + Fixed bug which allowed URL and title to be separated by multiple blank

5502+ lines in links and reference keys. They can be on separate lines but

5503+ can't have blank lines between them.

5504+ + Correctly handle bracketed text inside inline footnotes and links,using

5505+ new function inlinesInBalanced. Resolves Issue #14.

5506+ + Fixed bug in footnotes: links in footnotes were not being

5507+ processed. Solution: three-stage parse. First, get all the

5508+ reference keys and add information to state. Next, get all the

5509+ notes and add information to state. (Reference keys may be needed

5510+ at this stage.) Finally, parse everything else.

5511+ + Replaced named constants like 'emphStart' with literals.

5512+ + Removed an extra occurance of escapedChar in definition of inline.

5513+

5514+ * RST reader:

5515+

5516+ + Allow the URI in a RST hyperlink target to start on the line

5517+ after the reference key.

5518+ + Added 'try' in front of 'string', where needed, or used a different

5519+ parser. This fixes a bug where ````` would not be correctly parsed as

5520+ a verbatim `.

5521+ + Fixed slow performance in parsing inline literals in RST reader. The

5522+ problem was that ``#`` was seen by 'inline' as a potential link or image.

5523+ Fix: inserted 'notFollowedBy (char '`')' in link parsers.

5524+ Resolves Issue #8.

5525+ + Use lookAhead instead of getInput/setInput in RST reader. Removed

5526+ unneeded getState call, since lookAhead automatically saves and

5527+ restores the parser state.

5528+ + Allow hyperlink target URIs to be split over multiple lines, and

5529+ to start on the line after the reference. Resolves Issue #7.

5530+ + Fixed handling of autolinks.

5531+

5532+ * LaTeX reader:

5533+

5534+ + Replaced 'choice [(try (string ...), ...]' idiom with 'oneOfStrings',

5535+ for clarity.

5536+ + Added clauses for tilde and caret. Tilde is \ensuremath{\sim}, and

5537+ caret is \^{}, not \^ as before.

5538+ + Added parsing for \url.

5539+ + Parse \texttt{} as code, provided there's nothing fancy inside.

5540+

5541+ * HTML writer:

5542+

5543+ + Modified HTML writer to use the Text.XHtml library. This results

5544+ in cleaner, faster code, and it makes it easier to use Pandoc in

5545+ other projects, like wikis, which use Text.XHtml. Two functions are

5546+ now provided, writeHtml and writeHtmlString: the former outputs an

5547+ Html structure, the latter a rendered string. The S5 writer is also

5548+ changed, in parallel ways (writeS5, writeS5String).

5549+ + The Html header is now written programmatically, so it has been

5550+ removed from the 'headers' directory. The S5 header is still

5551+ needed, but the doctype and some of the meta declarations have

5552+ been removed, since they are written programatically. This change

5553+ introduces a new dependency on the xhtml package.

5554+ + Fixed two bugs in email obfuscation involving improper escaping

5555+ of '&' in the `<noscript>` section and in `--strict` mode. Resolves

5556+ Issue #9.

5557+ + Fixed another bug in email obfuscation: If the text to be obfuscated

5558+ contains an entity, this needs to be decoded before obfuscation.

5559+ Thanks to thsutton for the patch. Resolves Issue #15.

5560+ + Changed the way the backlink is displayed in HTML footnotes.

5561+ Instead of appearing on a line by itself, it now generally

5562+ appears on the last line of the note. (Exception: when the

5563+ note does not end with a Plain or Para block.) This saves space

5564+ and looks better.

5565+ + Added automatic unique identifiers to headers:

5566+ - The identifier is derived from the header via a scheme

5567+ documented in README.

5568+ - WriterState now includes a list of header identifiers and a table

5569+ of contents in addition to notes.

5570+ - The function uniqueIdentifiers creates a list of unique identifiers

5571+ from a list of inline lists (e.g. headers).

5572+ - This list is part of WriterState and gets consumed by blockToHtml

5573+ each time a header is encountered.

5574+ + Include CSS for .strikethrough class in header only if strikethrough

5575+ text appears in the document.

5576+ + If the 'strict' option is specified, elements that do not appear in

5577+ standard markdown (like definition lists) are passed through as

5578+ raw HTML.

5579+ + Simplified treatment of autolinks, using pattern matching instead of

5580+ conditionals.

5581+

5582+ * Markdown writer:

5583+

5584+ + Links in markdown output are now printed as inline links by default,

5585+ rather than reference links. A --reference-links option has been added

5586+ that forces links to be printed as reference links. Resolves Issue #4.

5587+ + Use autolinks when possible. Instead of `[site.com](site.com)`,

5588+ use `<site.com>`.

5589+

5590+ * LaTeX writer:

5591+

5592+ + Rewrote to use the State monad. The preamble now includes only those

5593+ packages that are actually required, given the document's content.

5594+ Thus, for example, if strikeout is not used, ulem is not required.

5595+ Modified LaTeXHeader accordingly.

5596+ + Modified LaTeX writer to insert '\,' between consecutive quotes.

5597+ + Removed unused function tableRowColumnWidths.

5598+ + Simplified code for escaping special characters.

5599+ + Leave extra blank line after \maketitle.

5600+ + Include empty '\author{}' when no author specified to avoid LaTeX

5601+ errors.

5602+ + Include fancyvrb code in header only if needed -- that is, only

5603+ if there is actually code in a footnote.

5604+ + Use \url{} for autolinks.

5605+ + Include [mathletters] option in ucs package, so that basic unicode

5606+ Greek letters will work correctly.

5607+

5608+ * RST writer: Force blank line before lists, so that sublists will

5609+ be handled correctly.

5610+

5611+ * Docbook writer: Fixed a bug: email links with text, like

5612+ [foo](me@bar.baz), were being incorrectly treated as autolinks.

5613+

5614+ * Removed Text.ParserCombinators.Pandoc and moved all its functions to

5615+ Text.Pandoc.Shared.

5616+

5617+ * Text.Pandoc.Shared:

5618+

5619+ + Added defaultWriterOptions.

5620+ + Added writerTableOfContents to WriterOptions.

5621+ + Added writerIgnoreNotes option to WriterOptions. This is needed

5622+ for processing header blocks for a table of contents, since notes on

5623+ headers should not appear in the TOC.

5624+ + Added prettyprinting for native Table format.

5625+ + Removed some unneeded imports.

5626+ + Moved escape and nullBlock parsers from

5627+ Text.ParserCombinators.Pandoc, since the latter is for

5628+ general-purpose parsers that don't depend on Text.Pandoc.Definition.

5629+ + Moved isHeaderBlock from Text.Pandoc.Writers.HTML.

5630+ + Moved Element, headerAtLeast, and hierarchicalize from Docbook

5631+ writer, because HTML writer now uses these in constructing a table

5632+ of contents.

5633+ + Added clauses for new inline elements (Strikeout, Superscript,

5634+ Subscript) to refsMatch.

5635+ + Removed backslashEscape; added new functions escapeStringUsing and

5636+ backslashEscapes.

5637+ + Moved failIfStrict from markdown reader, since it is now used also

5638+ by the HTML reader.

5639+ + Added a 'try' to the definition of indentSpaces.

5640+ + In definition of 'reference', added check to make sure it's not a note

5641+ reference.

5642+ + Added functions: camelCaseToHyphenated, toRomanNumeral,

5643+ anyOrderedListMarker, orderedListmarker, orderedListMarkers,

5644+ charsInBalanced', withHorizDisplacement, romanNumeral

5645+ + Fixed a bug in the anyLine parser. Previously it would parse an empty

5646+ string "", but it should fail on an empty string, or we get an error

5647+ when it is used inside "many" combinators.

5648+ + Removed followedBy' parser, replacing it with the lookAhead parser from

5649+ Parsec.

5650+ + Added some needed 'try's before multicharacter parsers, especially in

5651+ 'option' contexts.

5652+ + Removed the 'try' from the 'end' parser in 'enclosed', so that

5653+ 'enclosed' behaves like 'option', 'manyTill', etc.

5654+ + Added lineClump parser, which parses a raw line block up to and

5655+ including any following blank lines.

5656+ + Renamed parseFromStr to parseFromString.

5657+ + Added a 'try' to the 'end' parser in 'enclosed'. This makes errors in

5658+ the use of 'enclosed' less likely. Removed some now-unnecessary 'try's

5659+ in calling code.

5660+ + Removed unneeded 'try' in blanklines.

5661+ + Removed endsWith function and rewrote calling functions to use

5662+ isSuffixOf instead.

5663+ + Added >>~ combinator.

5664+ + Fixed bug in normalizeSpaces: Space:Str "":Space should compress to

5665+ Space.

5666+

5667+ * Refactored runtests.pl; added separate tests for tables.

5668+

5669+ * Shell scripts:

5670+

5671+ + Added -asxhtml flag to tidy in html2markdown. This will

5672+ perhaps help the parser, which expects closing tags.

5673+ + Modified markdown2pdf to run pdflatex a second time if --toc or

5674+ --table-of-contents was specified; otherwise the table of

5675+ contents won't appear.

5676+ + Modified markdown2pdf to print a helpful message if the 'ulem'

5677+ LaTeX package is required and not found.

5678+

5679+ * Changes to build process:

5680+

5681+ + Dropped support for compilation with GHC 6.4. GHC 6.6 or higher

5682+ is now required.

5683+ + Removed cabalize and Pandoc.cabal.in. The repository now contains

5684+ pandoc.cabal itself.

5685+ + Pandoc.cabal has been changed to pandoc.cabal, because HackageDB

5686+ likes the cabal file to have the same name as the tarball.

5687+ + Expanded and revised the package description in pandoc.cabal.

5688+ Revised the package synopsis.

5689+ + The tarball built by 'make tarball' now contains files built from

5690+ templates (including man pages and shell scripts), so pandoc can

5691+ be built directly using Cabal tools, without preprocessing.

5692+ + Executable binaries are now stripped before installing.

5693+ + Man pages are now generated from markdown sources, using pandoc's

5694+ man page writer.

5695+ + Use HTML version of README (instead of RTF) in Mac OS X installer.

5696+ + Instead of testing for the existence of a pandoc symlink in build-exec,

5697+ use ln -f.

5698+

5699+ * Documentation:

5700+

5701+ + Updated README and man pages with information on new features.

5702+ + Updated INSTALL instructions with some useful clarifications and

5703+ links.

5704+ + Updated web content.

5705+

5706+ * Added FreeBSD port.

5707+

5708+ [ Recai Oktaş ]

5709+

5710+ * debian/control:

5711+

5712+ + Changed pandoc's Build-Depends to include libghc6-mtl-dev and

5713+ libghc6-xhtml-dev. Removed libghc6-html-dev.

5714+ + Suggest texlive-latex-recommended | tetex-extra instead of

5715+ tetex-bin. This brings in fancyvrb and unicode support.

5716+

5717+ -- Recai Oktaş <roktas@debian.org> Tue, 16 Jan 2007 00:37:21 +0200

5718+

5719+pandoc (0.3) unstable; urgency=low

5720+

5721+ [ John MacFarlane ]

5722+

5723+ * Changes in pandoc options:

5724+

5725+ + Allow options to follow or precede arguments.

5726+ + Changed '--smartypants' to '--smart' and adjusted symbols accordingly.

5727+ + Added '--strict' option.

5728+ + Added '-o/--output' option.

5729+ + Added '--dump-args' and '--ignore-args' options (for use in wrappers).

5730+ + Modified '-v' and '-h' output to go to STDERR, not STDOUT, and return

5731+ error conditions. This is helpful for writing wrappers.

5732+ + Added copyright message to '-v' output, modeled after FSF messages.

5733+ + Reformatted usage message so that it doesn't wrap illegibly.

5734+ + Removed extra blanks after '-h' and '-D' output.

5735+

5736+ * Added docbook writer.

5737+

5738+ * Added implicit setting of default input and output format based

5739+ on input and output filename extensions. These defaults are

5740+ overridden if explicit input and output formats are specified using

5741+ '-t', '-f', '-r', or '-w' options. Documented in pandoc(1) man page

5742+ and README.

5743+

5744+ * Allow ordered list items to begin with (single) letters, as well

5745+ as numbers. The list item marker may now be terminated either by

5746+ '.' or by ')'. This extension to standard markdown is documented

5747+ in README.

5748+

5749+ * Revised footnote syntax. (See README for full details.) The

5750+ '[^1]' format now standard in markdown extensions is supported,

5751+ as are inline footnotes with this syntax: '^[My note.]'.

5752+ The earlier footnote syntax '^(1)' is no longer supported.

5753+

5754+ * Improved HTML representation of footnotes. All footnotes

5755+ are now auto-numbered and appear in an ordered list at the

5756+ end of the HTML document. Since the default appearance is now

5757+ acceptable, the old footnote styles have been removed from the

5758+ HTML header.

5759+

5760+ * Bug fixes:

5761+

5762+ + Fixed a serious bug in the markdown, LaTeX, and RST readers.

5763+ These readers ran 'runParser' on processed chunks of text to handle

5764+ embedded block lists in lists and quotation blocks. But then

5765+ any changes made to the parser state in these chunks was lost,

5766+ as the state is local to the parser. So, for example, footnotes

5767+ didn't work in quotes or list items. The fix: instead of calling

5768+ runParser on some raw text, use setInput to make it the input, then

5769+ parse it, then use setInput to restore the input to what it was

5770+ before. This is shorter and more elegant, and it fixes the problem.

5771+ + Fixed bug in notFollowedBy' combinator (adding 'try' before

5772+ 'parser'). Adjusted code that uses this combinator accordingly.

5773+ + Fixed bug in RTF writer that caused improper indentation on

5774+ footnotes occurring in indented blocks like lists.

5775+ + Fixed parsing of metadata in LaTeX reader. Now the title, author,

5776+ and date are parsed correctly. Everything else in the preamble

5777+ is skipped.

5778+ + Modified escapedChar in LaTeX reader to allow a '\' at the end of a

5779+ line to count as escaped whitespace.

5780+ + Modified LaTeX reader to produce inline links rather than reference

5781+ links. Otherwise, links in footnotes aren't handled properly.

5782+ + Fixed handling of titles in links in Markdown reader, so that

5783+ embedded quotation marks are now handled properly.

5784+ + Fixed Markdown reader's handling of embedded brackets in links.

5785+ + Fixed Markdown reader so that it only parses bracketed material

5786+ as a reference link if there is actually a corresponding key.

5787+ + Revised inline code parsing in Markdown reader to conform to

5788+ markdown standard. Now any number of `s can begin inline code,

5789+ which will end with the same number of `s. For example, to

5790+ have two backticks as code, write ``` `` ```. Modified Markdown

5791+ writer accordingly.

5792+ + Fixed bug in text-wrapping routine in Markdown and RST writers.

5793+ Now LineBreaks no longer cause wrapping problems.

5794+ + Supported hexadecimal numerical entity references as well as

5795+ decimal ones.

5796+ + Fixed bug in Markdown reader's handling of underscores and other

5797+ inline formatting markers inside reference labels: for example,

5798+ in '[A_B]: /url/a_b', the material between underscores was being

5799+ parsed as emphasized inlines.

5800+ + Changed Markdown reader's handling of backslash escapes so that

5801+ only non-alphanumeric characters can be escaped. Strict mode

5802+ follows Markdown.pl in only allowing a select group of punctuation

5803+ characters to be escaped.

5804+ + Modified HTML reader to skip a newline following a `<br>` tag.

5805+ Otherwise the newline will be treated as a space at the beginning

5806+ of the next line.

5807+

5808+ * Made handling of code blocks more consistent. Previously, some

5809+ readers allowed trailing newlines, while others stripped them.

5810+ Now, all readers strip trailing newlines in code blocks. Writers

5811+ insert a newline at the end of code blocks as needed.

5812+

5813+ * Modified readers to make spacing at the end of output more consistent.

5814+

5815+ * Minor improvements to LaTeX reader:

5816+

5817+ + '\thanks' now treated like a footnote.

5818+ + Simplified parsing of LaTeX command arguments and options.

5819+ commandArgs now returns a list of arguments OR options (in

5820+ whatever order they appear). The brackets are included, and

5821+ a new stripFirstAndLast function is provided to strip them off

5822+ when needed. This fixes a problem in dealing with \newcommand

5823+ and \newenvironment.

5824+

5825+ * Revised RTF writer:

5826+

5827+ + Default font is now Helvetica.

5828+ + An '\f0' is added to each '\pard', so that font resizing works

5829+ correctly.

5830+

5831+ * Moved handling of "smart typography" from the writers to the Markdown

5832+ and LaTeX readers. This allows great simplification of the writers

5833+ and more accurate smart quotes, dashes, and ellipses. DocBook can

5834+ now use `<quote>`. The '--smart' option now toggles an option in

5835+ the parser state rather than a writer option. Several new kinds

5836+ of inline elements have been added: Quoted, Ellipses, Apostrophe,

5837+ EmDash, EnDash.

5838+

5839+ * Changes in HTML writer:

5840+

5841+ + Include title block in header even when title is null.

5842+ + Made javascript obfuscation of emails even more obfuscatory,

5843+ by combining it with entity obfuscation.

5844+

5845+ * Changed default ASCIIMathML text color to black.

5846+

5847+ * Test suite:

5848+

5849+ + Added --strip-trailing-cr option to diff in runtests.pl, for

5850+ compatibility with Windows.

5851+ + Added regression tests with footnotes in quote blocks and lists.

5852+

5853+ * Makefile changes:

5854+

5855+ + osx-pkg target creates a Mac OS X package (directory). New osx

5856+ directory contains files needed for construction of the package.

5857+ + osx-dmg target creates a compressed disk image containing the package.

5858+ + win-pkg target creates Windows binary package.

5859+ + tarball target creates distribution source tarball.

5860+ + website target generates pandoc's website automatically, including

5861+ demos. New 'web' directory containts files needed for construction

5862+ of the website (which will be created as the 'pandoc' subdirectory

5863+ of 'web').

5864+ + Makefile checks to see if we're running Windows/Cygwin; if so,

5865+ a '.exe' extension is added to each executable in EXECS.

5866+

5867+ * Removed all wrappers except markdown2pdf and html2markdown.

5868+

5869+ * Added new wrapper hsmarkdown, to be used as a drop-in replacement

5870+ for Markdown.pl. hsmarkdown calls pandoc with the '--strict'

5871+ option and disables other options.

5872+

5873+ * Added code to html2markdown that tries to determine the character

5874+ encoding of an HTML file, by parsing the "Content-type" meta tag.

5875+

5876+ + If the encoding can't be determined, then if the content is local,

5877+ the local encoding is used; if it comes from a URL, UTF-8 is used

5878+ by default.

5879+ + If input is from STDIN, don't try to determine character encoding.

5880+ + Encoding can be specified explicitly using '-e' option.

5881+

5882+ * Improved warning messages in wrappers:

5883+

5884+ + Print warning if iconv not available

5885+ + More user-friendly error messages in markdown2pdf, when

5886+ pdflatex fails.

5887+

5888+ * Code cleanup:

5889+

5890+ + Renamed 'Text/Pandoc/HtmlEntities' module to

5891+ 'Text/Pandoc/Entities'. Also changed function names so as

5892+ not to be HTML-specific.

5893+ + Refactored SGML string escaping functions from HTML and Docbook

5894+ writers into Text/Pandoc/Shared. (escapeSGML, stringToSGML)

5895+ + Removed 'BlockQuoteContext' from ParserContext, as it isn't

5896+ used anywhere.

5897+ + Removed splitBySpace and replaced it with a general, polymorphic

5898+ splitBy function.

5899+ + Refactored LaTeX reader for clarity (added isArg function).

5900+ + Converted some CR's to LF's in src/ui/default/print.css.

5901+ + Added license text to top of source files.

5902+ + Added module data for haddock to source files.

5903+ + Reformatted code for consistency.

5904+

5905+ * Rewrote documentation and man pages. Split README into INSTALL

5906+ and README.

5907+

5908+ * Split LICENSE into COPYING and COPYRIGHT.

5909+

5910+ * Removed TODO, since we now maintain ToDo on the wiki.

5911+

5912+ * Made COPYRIGHT in top level a symlink to debian/copyright, to avoid

5913+ duplication.

5914+

5915+ [ Recai Oktaş ]

5916+

5917+ * Revamped build process to conform to debian standards and created

5918+ a proper debian package. Closes: #391666.

5919+

5920+ * Modified build process to support GHC 6.6.

5921+

5922+ + The package can still be compiled using GHC 6.4.2, though because

5923+ of dependencies the "make deb" target works only with GHC 6.6+.

5924+ + The script 'cabalize' is used to create an appropriate

5925+ 'Pandoc.cabal' from 'Pandoc.cabal.in', depending on the GHC and

5926+ Cabal versions.

5927+

5928+ * Refactored template processing (fillTemplates.pl).

5929+

5930+ * Modified wrapper scripts to make them more robust and portable.

5931+ To avoid code duplication and ensure consistency, wrappers are

5932+ generated via a templating system from templates in src/wrappers.

5933+

5934+ + Wrappers now accept multiple filenames, when appropriate.

5935+ + Spaces and tabs allowed in filenames.

5936+ + getopts shell builtin is used for portable option parsing.

5937+ + Improved html2markdown's web grabber code, making it more robust,

5938+ configurable and verbose. Added '-e', '-g' options.

5939+

5940+ -- Recai Oktaş <roktas@debian.org> Fri, 05 Jan 2007 09:41:19 +0200

5941+

5942+pandoc (0.2) unstable; urgency=low

5943+

5944+ * Fixed unicode/utf-8 translation

5945+

5946+ -- John MacFarlane <jgm@berkeley.edu> Mon, 14 Aug 2006 00:00:00 -0400

5947+

5948+pandoc (0.1) unstable; urgency=low

5949+

5950+ * Initial creation of debian package

5951+

5952+ -- John MacFarlane <jgm@berkeley.edu> Mon, 14 Aug 2006 00:00:00 -0400

changelog.mddeleted−20339

This diff is too big to show here.

citeproc/biblatex-localization/.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/UKenglish.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/USenglish.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/american.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/australian.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/austrian.lbx.stringsdeleted−1

This diff is too big to show here.

citeproc/biblatex-localization/brazil.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/brazilian.lbx.stringsdeleted−233

This diff is too big to show here.

citeproc/biblatex-localization/british.lbx.stringsdeleted−3

This diff is too big to show here.

citeproc/biblatex-localization/bulgarian.lbx.stringsdeleted−28

This diff is too big to show here.

citeproc/biblatex-localization/canadian.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/catalan.lbx.stringsdeleted−158

This diff is too big to show here.

citeproc/biblatex-localization/croatian.lbx.stringsdeleted−214

This diff is too big to show here.

citeproc/biblatex-localization/czech.lbx.stringsdeleted−91

This diff is too big to show here.

citeproc/biblatex-localization/danish.lbx.stringsdeleted−106

This diff is too big to show here.

citeproc/biblatex-localization/dutch.lbx.stringsdeleted−23

This diff is too big to show here.

citeproc/biblatex-localization/english.lbx.stringsdeleted−254

This diff is too big to show here.

citeproc/biblatex-localization/estonian.lbx.stringsdeleted−178

This diff is too big to show here.

citeproc/biblatex-localization/finnish.lbx.stringsdeleted−254

This diff is too big to show here.

citeproc/biblatex-localization/french.lbx.stringsdeleted−245

This diff is too big to show here.

citeproc/biblatex-localization/galician.lbx.stringsdeleted−28

This diff is too big to show here.

citeproc/biblatex-localization/german.lbx.stringsdeleted−28

This diff is too big to show here.

citeproc/biblatex-localization/greek.lbx.stringsdeleted−9

This diff is too big to show here.

citeproc/biblatex-localization/hungarian.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/icelandic.lbx.stringsdeleted−7

This diff is too big to show here.

citeproc/biblatex-localization/italian.lbx.stringsdeleted−9

This diff is too big to show here.

citeproc/biblatex-localization/latvian.lbx.stringsdeleted−75

This diff is too big to show here.

citeproc/biblatex-localization/lithuanian.lbx.stringsdeleted−31

This diff is too big to show here.

citeproc/biblatex-localization/magyar.lbx.stringsdeleted−29

This diff is too big to show here.

citeproc/biblatex-localization/naustrian.lbx.stringsdeleted−2

This diff is too big to show here.

citeproc/biblatex-localization/newzealand.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/ngerman.lbx.stringsdeleted−1

This diff is too big to show here.

citeproc/biblatex-localization/norsk.lbx.stringsdeleted−98

This diff is too big to show here.

citeproc/biblatex-localization/nswissgerman.lbx.stringsdeleted−2

This diff is too big to show here.

citeproc/biblatex-localization/nynorsk.lbx.stringsdeleted−28

This diff is too big to show here.

citeproc/biblatex-localization/polish.lbx.stringsdeleted−100

This diff is too big to show here.

citeproc/biblatex-localization/portuges.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/portuguese.lbx.stringsdeleted−95

This diff is too big to show here.

citeproc/biblatex-localization/russian.lbx.stringsdeleted−102

This diff is too big to show here.

citeproc/biblatex-localization/serbian.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/serbianc.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/slovak.lbx.stringsdeleted−82

This diff is too big to show here.

citeproc/biblatex-localization/slovene.lbx.stringsdeleted−28

This diff is too big to show here.

citeproc/biblatex-localization/slovenian.lbx.stringsdeleted

No changes to the content.

citeproc/biblatex-localization/spanish.lbx.stringsdeleted−190

This diff is too big to show here.

citeproc/biblatex-localization/swedish.lbx.stringsdeleted−9

This diff is too big to show here.

citeproc/biblatex-localization/swissgerman.lbx.stringsdeleted−1

This diff is too big to show here.

citeproc/biblatex-localization/turkish.lbx.stringsdeleted−157

This diff is too big to show here.

citeproc/biblatex-localization/ukrainian.lbx.stringsdeleted−102

This diff is too big to show here.

data/LaTeXMathML.jsnew file+198

This diff is too big to show here.

data/MathMLinHTML.jsnew file+70

This diff is too big to show here.

data/abbreviationsdeleted−80

This diff is too big to show here.

data/bash_completion.tpldeleted−82

This diff is too big to show here.

data/default.csldeleted−658

This diff is too big to show here.

data/docx/[Content_Types].xmldeleted−2

This diff is too big to show here.

data/docx/_rels/.relsdeleted−3

This diff is too big to show here.

data/docx/docProps/app.xmldeleted−18

This diff is too big to show here.

data/docx/docProps/core.xmldeleted−2

This diff is too big to show here.

data/docx/docProps/custom.xmldeleted−2

This diff is too big to show here.

data/docx/word/_rels/document.xml.relsdeleted−2

This diff is too big to show here.

data/docx/word/_rels/footnotes.xml.relsdeleted−2

This diff is too big to show here.

data/docx/word/comments.xmldeleted−2

This diff is too big to show here.

data/docx/word/document.xmldeleted−398

This diff is too big to show here.

data/docx/word/fontTable.xmldeleted−52

This diff is too big to show here.

data/docx/word/footnotes.xmldeleted−7

This diff is too big to show here.

data/docx/word/numbering.xmldeleted−2

This diff is too big to show here.

data/docx/word/settings.xmldeleted−37

This diff is too big to show here.

data/docx/word/styles.xmldeleted−468

This diff is too big to show here.

data/docx/word/theme/theme1.xmldeleted−2

This diff is too big to show here.

data/docx/word/webSettings.xmldeleted−5

This diff is too big to show here.

data/dzslides/template.html+30−128

This diff is too big to show here.

data/epub.css+4−22

This diff is too big to show here.

data/init.luadeleted−3

This diff is too big to show here.

data/odt/Configurations2/accelerator/current.xmldeleted

No changes to the content.

data/odt/META-INF/manifest.xmldeleted−12

This diff is too big to show here.

data/odt/Thumbnails/thumbnail.pngdeleted

Binary file not shown.

data/odt/content.xmldeleted−2

This diff is too big to show here.

data/odt/manifest.rdfdeleted−18

This diff is too big to show here.

data/odt/meta.xmldeleted−18

This diff is too big to show here.

data/odt/mimetypedeleted−1

This diff is too big to show here.

data/odt/settings.xmldeleted−2

This diff is too big to show here.

data/odt/styles.xmldeleted−1108

This diff is too big to show here.

data/pandoc.List.luadeleted−142

This diff is too big to show here.

data/pandoc.luadeleted−1169

This diff is too big to show here.

data/pptx/[Content_Types].xmldeleted−2

This diff is too big to show here.

data/pptx/_rels/.relsdeleted−2

This diff is too big to show here.

data/pptx/docProps/app.xmldeleted−2

This diff is too big to show here.

data/pptx/docProps/core.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/_rels/presentation.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/notesMasters/_rels/notesMaster1.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/notesMasters/notesMaster1.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/notesSlides/_rels/notesSlide1.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/notesSlides/_rels/notesSlide2.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/notesSlides/notesSlide1.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/notesSlides/notesSlide2.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/presProps.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/presentation.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout1.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout10.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout11.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout2.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout3.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout4.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout5.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout6.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout7.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout8.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/_rels/slideLayout9.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout1.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout10.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout11.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout2.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout3.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout4.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout5.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout6.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout7.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout8.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideLayouts/slideLayout9.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slideMasters/_rels/slideMaster1.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slideMasters/slideMaster1.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slides/_rels/slide1.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slides/_rels/slide2.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slides/_rels/slide3.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slides/_rels/slide4.xml.relsdeleted−2

This diff is too big to show here.

data/pptx/ppt/slides/slide1.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slides/slide2.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slides/slide3.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/slides/slide4.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/tableStyles.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/theme/theme1.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/theme/theme2.xmldeleted−2

This diff is too big to show here.

data/pptx/ppt/viewProps.xmldeleted−2

This diff is too big to show here.

data/reference.docxnew file

Binary file not shown.

data/reference.odtnew file

Binary file not shown.

data/s5/default/blank.gifnew file

Binary file not shown.

test/bodybg.gif → data/s5/default/bodybg.gifrenamed

Binary file not shown.

data/s5/default/framing.cssnew file+23

This diff is too big to show here.

data/s5/default/iepngfix.htcnew file+42

This diff is too big to show here.

data/s5/default/opera.cssnew file+7

This diff is too big to show here.

data/s5/default/outline.cssnew file+15

This diff is too big to show here.

data/s5/default/pretty.cssnew file+86

This diff is too big to show here.

data/s5/default/print.cssnew file+24

This diff is too big to show here.

data/s5/default/s5-core.cssnew file+9

This diff is too big to show here.

data/s5/default/slides.cssnew file+3

This diff is too big to show here.

data/s5/default/slides.jsnew file+553

This diff is too big to show here.

data/sample.lua+50−89

This diff is too big to show here.

data/slideous/slideous.cssnew file+95

This diff is too big to show here.

data/slideous/slideous.jsnew file+321

This diff is too big to show here.

data/slidy/graphics/fold-dim.gifnew file

Binary file not shown.

data/slidy/graphics/fold.gifnew file

Binary file not shown.

data/slidy/graphics/nofold-dim.gifnew file

Binary file not shown.

data/slidy/graphics/unfold-dim.gifnew file

Binary file not shown.

data/slidy/graphics/unfold.gifnew file

Binary file not shown.

data/slidy/scripts/slidy.jsnew file+3016

This diff is too big to show here.

data/slidy/styles/slidy.cssnew file+405

This diff is too big to show here.

data/templatesnew file+1

This diff is too big to show here.

data/templates/affiliations.jatsdeleted−38

This diff is too big to show here.

data/templates/article.jats_publishingdeleted−211

This diff is too big to show here.

data/templates/default.asciidocdeleted−38

This diff is too big to show here.

data/templates/default.asciidoctordeleted−41

This diff is too big to show here.

data/templates/default.biblatexdeleted−10

This diff is too big to show here.

data/templates/default.bibtexdeleted−10

This diff is too big to show here.

data/templates/default.commonmarkdeleted−21

This diff is too big to show here.

data/templates/default.contextdeleted−179

This diff is too big to show here.

data/templates/default.docbook4deleted−32

This diff is too big to show here.

data/templates/default.docbook5deleted−37

This diff is too big to show here.

data/templates/default.dokuwikideleted−13

This diff is too big to show here.

data/templates/default.dzslidesdeleted−192

This diff is too big to show here.

data/templates/default.epub2deleted−67

This diff is too big to show here.

data/templates/default.epub3deleted−68

This diff is too big to show here.

data/templates/default.haddockdeleted−1

This diff is too big to show here.

data/templates/default.html4deleted−64

This diff is too big to show here.

data/templates/default.html5deleted−67

This diff is too big to show here.

data/templates/default.icmldeleted−43

This diff is too big to show here.

data/templates/default.jats_archivingdeleted−7

This diff is too big to show here.

data/templates/default.jats_articleauthoringdeleted−93

This diff is too big to show here.

data/templates/default.jats_publishingdeleted−7

This diff is too big to show here.

data/templates/default.jiradeleted−9

This diff is too big to show here.

data/templates/default.latexdeleted−549

This diff is too big to show here.

data/templates/default.mandeleted−30

This diff is too big to show here.

data/templates/default.markdowndeleted−21

This diff is too big to show here.

data/templates/default.mediawikideleted−13

This diff is too big to show here.

data/templates/default.msdeleted−118

This diff is too big to show here.

data/templates/default.musedeleted−44

This diff is too big to show here.

data/templates/default.opendocumentdeleted−165

This diff is too big to show here.

data/templates/default.opmldeleted−11

This diff is too big to show here.

data/templates/default.orgdeleted−24

This diff is too big to show here.

data/templates/default.plaindeleted−21

This diff is too big to show here.

data/templates/default.revealjsdeleted−318

This diff is too big to show here.

data/templates/default.rstdeleted−46

This diff is too big to show here.

data/templates/default.rtfdeleted−30

This diff is too big to show here.

data/templates/default.s5deleted−83

This diff is too big to show here.

data/templates/default.slideousdeleted−91

This diff is too big to show here.

data/templates/default.slidydeleted−75

This diff is too big to show here.

data/templates/default.teideleted−51

This diff is too big to show here.

data/templates/default.texinfodeleted−42

This diff is too big to show here.

data/templates/default.textiledeleted−9

This diff is too big to show here.

data/templates/default.xwikideleted−13

This diff is too big to show here.

data/templates/default.zimwikideleted−16

This diff is too big to show here.

data/templates/styles.htmldeleted−180

This diff is too big to show here.

data/translations/am.yamldeleted−20

This diff is too big to show here.

data/translations/ar.yamldeleted−20

This diff is too big to show here.

data/translations/bg.yamldeleted−19

This diff is too big to show here.

data/translations/bn.yamldeleted−21

This diff is too big to show here.

data/translations/ca.yamldeleted−21

This diff is too big to show here.

data/translations/cs.yamldeleted−21

This diff is too big to show here.

data/translations/da.yamldeleted−21

This diff is too big to show here.

data/translations/de.yamldeleted−22

This diff is too big to show here.

data/translations/el.yamldeleted−21

This diff is too big to show here.

data/translations/en.yamldeleted−22

This diff is too big to show here.

data/translations/eo.yamldeleted−20

This diff is too big to show here.

data/translations/es.yamldeleted−21

This diff is too big to show here.

data/translations/et.yamldeleted−20

This diff is too big to show here.

data/translations/eu.yamldeleted−21

This diff is too big to show here.

data/translations/fa.yamldeleted−21

This diff is too big to show here.

data/translations/fi.yamldeleted−21

This diff is too big to show here.

data/translations/fr.yamldeleted−20

This diff is too big to show here.

data/translations/he.yamldeleted−22

This diff is too big to show here.

data/translations/hi.yamldeleted−20

This diff is too big to show here.

data/translations/hr.yamldeleted−21

This diff is too big to show here.

data/translations/hu.yamldeleted−21

This diff is too big to show here.

data/translations/is.yamldeleted−21

This diff is too big to show here.

data/translations/it.yamldeleted−21

This diff is too big to show here.

data/translations/km.yamldeleted−21

This diff is too big to show here.

data/translations/ko.yamldeleted−17

This diff is too big to show here.

data/translations/lo.yamldeleted−21

This diff is too big to show here.

data/translations/lt.yamldeleted−21

This diff is too big to show here.

data/translations/lv.yamldeleted−20

This diff is too big to show here.

data/translations/nl.yamldeleted−21

This diff is too big to show here.

data/translations/no.yamldeleted−21

This diff is too big to show here.

data/translations/pl.yamldeleted−21

This diff is too big to show here.

data/translations/pt.yamldeleted−21

This diff is too big to show here.

data/translations/rm.yamldeleted−21

This diff is too big to show here.

data/translations/ro.yamldeleted−21

This diff is too big to show here.

data/translations/ru.yamldeleted−20

This diff is too big to show here.

data/translations/sk.yamldeleted−21

This diff is too big to show here.

data/translations/sl.yamldeleted−21

This diff is too big to show here.

data/translations/sq.yamldeleted−18

This diff is too big to show here.

data/translations/sr-cyrl.yamldeleted−21

This diff is too big to show here.

data/translations/sr.yamldeleted−21

This diff is too big to show here.

data/translations/sv.yamldeleted−21

This diff is too big to show here.

data/translations/th.yamldeleted−20

This diff is too big to show here.

data/translations/tr.yamldeleted−22

This diff is too big to show here.

data/translations/uk.yamldeleted−21

This diff is too big to show here.

data/translations/ur.yamldeleted−22

This diff is too big to show here.

data/translations/vi.yamldeleted−21

This diff is too big to show here.

data/translations/zh-Hans.yamldeleted−22

This diff is too big to show here.

data/translations/zh-Hant.yamldeleted−22

This diff is too big to show here.

default.nixdeleted−13

This diff is too big to show here.

doc/customizing-pandoc.mddeleted−168

This diff is too big to show here.

doc/epub.mddeleted−163

This diff is too big to show here.

doc/faqs.mddeleted−128

This diff is too big to show here.

doc/filters.mddeleted−512

This diff is too big to show here.

doc/getting-started.mddeleted−318

This diff is too big to show here.

doc/jats.mddeleted−414

This diff is too big to show here.

doc/libraries.mddeleted−63

This diff is too big to show here.

doc/lua-filters.mddeleted−3692

This diff is too big to show here.

doc/org.mddeleted−379

This diff is too big to show here.

doc/using-the-pandoc-api.mddeleted−476

This diff is too big to show here.

googlecode-upload.shnew file+5

This diff is too big to show here.

linux/control.indeleted−26

This diff is too big to show here.

linux/make_artifacts.shdeleted−84

This diff is too big to show here.

macos/Makefiledeleted−35

This diff is too big to show here.

macos/distribution.xml.indeleted−30

This diff is too big to show here.

macos/uninstall-pandoc.pldeleted−79

This diff is too big to show here.

make_osx_package.shnew file+76

This diff is too big to show here.

man/make-pandoc-man-pages.hsnew file+102

This diff is too big to show here.

man/man1/pandoc.1.templatenew file+16

This diff is too big to show here.

man/man5/pandoc_markdown.5.templatenew file+11

This diff is too big to show here.

man/manfilter.luadeleted−22

This diff is too big to show here.

man/pandoc.1deleted−7723

This diff is too big to show here.

man/pandoc.1.afterdeleted−3

This diff is too big to show here.

man/pandoc.1.beforedeleted−2

This diff is too big to show here.

osx-resources/InstallationChecknew file+14

This diff is too big to show here.

osx-resources/InstallationCheck.stringsnew file+3

This diff is too big to show here.

pandoc.cabal+344−764

This diff is too big to show here.

pandoc.hsnew file+1170

This diff is too big to show here.

prelude/Prelude.hsdeleted−15

This diff is too big to show here.

relann1.6new file+170

This diff is too big to show here.

release.nixdeleted−4

This diff is too big to show here.

shell.nixdeleted−106

This diff is too big to show here.

src/Text/Pandoc.hs+277−29

This diff is too big to show here.

src/Text/Pandoc/App.hsdeleted−392

This diff is too big to show here.

src/Text/Pandoc/App/CommandLineOptions.hsdeleted−1092

This diff is too big to show here.

src/Text/Pandoc/App/FormatHeuristics.hsdeleted−90

This diff is too big to show here.

src/Text/Pandoc/App/Opt.hsdeleted−747

This diff is too big to show here.

src/Text/Pandoc/App/OutputSettings.hsdeleted−256

This diff is too big to show here.

src/Text/Pandoc/Asciify.hs+409−15

This diff is too big to show here.

src/Text/Pandoc/CSS.hsdeleted−56

This diff is too big to show here.

src/Text/Pandoc/CSV.hsdeleted−81

This diff is too big to show here.

src/Text/Pandoc/Citeproc.hsdeleted−661

This diff is too big to show here.

src/Text/Pandoc/Citeproc/BibTeX.hsdeleted−1476

This diff is too big to show here.

src/Text/Pandoc/Citeproc/CslJson.hsdeleted−37

This diff is too big to show here.

src/Text/Pandoc/Citeproc/Data.hsdeleted−32

This diff is too big to show here.

src/Text/Pandoc/Citeproc/Locator.hsdeleted−295

This diff is too big to show here.

src/Text/Pandoc/Citeproc/MetaValue.hsdeleted−255

This diff is too big to show here.

src/Text/Pandoc/Citeproc/Util.hsdeleted−70

This diff is too big to show here.

src/Text/Pandoc/Class.hsdeleted−29

This diff is too big to show here.

src/Text/Pandoc/Class/CommonState.hsdeleted−83

This diff is too big to show here.

src/Text/Pandoc/Class/IO.hsdeleted−231

This diff is too big to show here.

src/Text/Pandoc/Class/PandocIO.hsdeleted−74

This diff is too big to show here.

src/Text/Pandoc/Class/PandocMonad.hsdeleted−711

This diff is too big to show here.

src/Text/Pandoc/Class/PandocPure.hsdeleted−218

This diff is too big to show here.

src/Text/Pandoc/Compat/Monoid.hsnew file+20

This diff is too big to show here.

src/Text/Pandoc/Compat/TagSoupEntity.hsnew file+15

This diff is too big to show here.

src/Text/Pandoc/Data.hsdeleted−32

This diff is too big to show here.

src/Text/Pandoc/Data.hsbnew file+7

This diff is too big to show here.

src/Text/Pandoc/Emoji.hsdeleted−24

This diff is too big to show here.

src/Text/Pandoc/Error.hsdeleted−207

This diff is too big to show here.

src/Text/Pandoc/Extensions.hsdeleted−623

This diff is too big to show here.

src/Text/Pandoc/Filter.hsdeleted−100

This diff is too big to show here.

src/Text/Pandoc/Filter/JSON.hsdeleted−80

This diff is too big to show here.

src/Text/Pandoc/Filter/Lua.hsdeleted−47

This diff is too big to show here.

src/Text/Pandoc/Filter/Path.hsdeleted−35

This diff is too big to show here.

src/Text/Pandoc/Highlighting.hs+102−169

This diff is too big to show here.

src/Text/Pandoc/Image.hsdeleted−37

This diff is too big to show here.

src/Text/Pandoc/ImageSize.hs+118−329

This diff is too big to show here.

src/Text/Pandoc/Logging.hsdeleted−416

This diff is too big to show here.

src/Text/Pandoc/Lua.hsdeleted−23

This diff is too big to show here.

src/Text/Pandoc/Lua/ErrorConversion.hsdeleted−61

This diff is too big to show here.

src/Text/Pandoc/Lua/Filter.hsdeleted−253

This diff is too big to show here.

src/Text/Pandoc/Lua/Global.hsdeleted−89

This diff is too big to show here.

src/Text/Pandoc/Lua/Init.hsdeleted−103

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling.hsdeleted−19

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/AST.hsdeleted−378

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/AnyValue.hsdeleted−24

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/CommonState.hsdeleted−102

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/Context.hsdeleted−28

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/List.hsdeleted−43

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/MediaBag.hsdeleted−73

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/PandocError.hsdeleted−65

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/ReaderOptions.hsdeleted−79

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/SimpleTable.hsdeleted−59

This diff is too big to show here.

src/Text/Pandoc/Lua/Marshaling/Version.hsdeleted−154

This diff is too big to show here.

src/Text/Pandoc/Lua/Module/MediaBag.hsdeleted−103

This diff is too big to show here.

src/Text/Pandoc/Lua/Module/Pandoc.hsdeleted−133

This diff is too big to show here.

src/Text/Pandoc/Lua/Module/System.hsdeleted−33

This diff is too big to show here.

src/Text/Pandoc/Lua/Module/Types.hsdeleted−68

This diff is too big to show here.

src/Text/Pandoc/Lua/Module/Utils.hsdeleted−175

This diff is too big to show here.

src/Text/Pandoc/Lua/Packages.hsdeleted−60

This diff is too big to show here.

src/Text/Pandoc/Lua/PandocLua.hsdeleted−141

This diff is too big to show here.

src/Text/Pandoc/Lua/Util.hsdeleted−145

This diff is too big to show here.

src/Text/Pandoc/Lua/Walk.hsdeleted−158

This diff is too big to show here.

src/Text/Pandoc/MIME.hs+41−90

This diff is too big to show here.

src/Text/Pandoc/MediaBag.hsdeleted−112

This diff is too big to show here.

src/Text/Pandoc/Options.hs+266−270

This diff is too big to show here.

src/Text/Pandoc/PDF.hs+111−484

This diff is too big to show here.

src/Text/Pandoc/Parsing.hs+520−1127

This diff is too big to show here.

src/Text/Pandoc/Pretty.hsnew file+524

This diff is too big to show here.

src/Text/Pandoc/Process.hs+66−73

This diff is too big to show here.

src/Text/Pandoc/Readers.hsdeleted−188

This diff is too big to show here.

src/Text/Pandoc/Readers/BibTeX.hsdeleted−77

This diff is too big to show here.

src/Text/Pandoc/Readers/CSV.hsdeleted−48

This diff is too big to show here.

src/Text/Pandoc/Readers/CommonMark.hsdeleted−118

This diff is too big to show here.

src/Text/Pandoc/Readers/Creole.hsdeleted−294

This diff is too big to show here.

src/Text/Pandoc/Readers/CslJson.hsdeleted−54

This diff is too big to show here.

src/Text/Pandoc/Readers/DocBook.hs+274−633

This diff is too big to show here.

src/Text/Pandoc/Readers/Docx.hsdeleted−754

This diff is too big to show here.

src/Text/Pandoc/Readers/Docx/Combine.hsdeleted−188

This diff is too big to show here.

src/Text/Pandoc/Readers/Docx/Fields.hsdeleted−74

This diff is too big to show here.

src/Text/Pandoc/Readers/Docx/Lists.hsdeleted−208

This diff is too big to show here.

src/Text/Pandoc/Readers/Docx/Parse.hsdeleted−1157

This diff is too big to show here.

src/Text/Pandoc/Readers/Docx/Parse/Styles.hsdeleted−322

This diff is too big to show here.

src/Text/Pandoc/Readers/Docx/Util.hsdeleted−70

This diff is too big to show here.

src/Text/Pandoc/Readers/DokuWiki.hsdeleted−516

This diff is too big to show here.

src/Text/Pandoc/Readers/EPUB.hsdeleted−302

This diff is too big to show here.

src/Text/Pandoc/Readers/FB2.hsdeleted−462

This diff is too big to show here.

src/Text/Pandoc/Readers/HTML.hs+497−958

This diff is too big to show here.

src/Text/Pandoc/Readers/HTML/Parsing.hsdeleted−225

This diff is too big to show here.

src/Text/Pandoc/Readers/HTML/Table.hsdeleted−283

This diff is too big to show here.

src/Text/Pandoc/Readers/HTML/TagCategories.hsdeleted−78

This diff is too big to show here.

src/Text/Pandoc/Readers/HTML/Types.hsdeleted−97

This diff is too big to show here.

src/Text/Pandoc/Readers/Haddock.hs+24−164

This diff is too big to show here.

src/Text/Pandoc/Readers/Haddock/Lex.xnew file+171

This diff is too big to show here.

src/Text/Pandoc/Readers/Haddock/Parse.ynew file+178

This diff is too big to show here.

src/Text/Pandoc/Readers/Ipynb.hsdeleted−230

This diff is too big to show here.

src/Text/Pandoc/Readers/JATS.hsdeleted−531

This diff is too big to show here.

src/Text/Pandoc/Readers/Jira.hsdeleted−203

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX.hs+1094−1174

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX/Citation.hsdeleted−210

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX/Inline.hsdeleted−397

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX/Lang.hsdeleted−234

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX/Macro.hsdeleted−184

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX/Math.hsdeleted−221

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX/Parsing.hsdeleted−1004

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX/SIunitx.hsdeleted−434

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX/Table.hsdeleted−378

This diff is too big to show here.

src/Text/Pandoc/Readers/LaTeX/Types.hsdeleted−50

This diff is too big to show here.

src/Text/Pandoc/Readers/Man.hsdeleted−520

This diff is too big to show here.

src/Text/Pandoc/Readers/Markdown.hs+1114−1472

This diff is too big to show here.

src/Text/Pandoc/Readers/MediaWiki.hs+262−356

This diff is too big to show here.

src/Text/Pandoc/Readers/Metadata.hsdeleted−200

This diff is too big to show here.

src/Text/Pandoc/Readers/Muse.hsdeleted−989

This diff is too big to show here.

src/Text/Pandoc/Readers/Native.hs+50−30

This diff is too big to show here.

src/Text/Pandoc/Readers/OPML.hs+55−72

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt.hsdeleted−97

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/Arrows/State.hsdeleted−139

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/Arrows/Utils.hsdeleted−213

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/Base.hsdeleted−22

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/ContentReader.hsdeleted−942

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/Generic/Fallible.hsdeleted−104

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/Generic/Namespaces.hsdeleted−45

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/Generic/SetMap.hsdeleted−30

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/Generic/Utils.hsdeleted−116

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/Generic/XMLConverter.hsdeleted−784

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/Namespaces.hsdeleted−93

This diff is too big to show here.

src/Text/Pandoc/Readers/Odt/StyleReader.hsdeleted−639

This diff is too big to show here.

src/Text/Pandoc/Readers/Org.hsdeleted−46

This diff is too big to show here.

src/Text/Pandoc/Readers/Org/BlockStarts.hsdeleted−131

This diff is too big to show here.

src/Text/Pandoc/Readers/Org/Blocks.hsdeleted−924

This diff is too big to show here.

src/Text/Pandoc/Readers/Org/DocumentTree.hsdeleted−408

This diff is too big to show here.

src/Text/Pandoc/Readers/Org/ExportSettings.hsdeleted−190

This diff is too big to show here.

src/Text/Pandoc/Readers/Org/Inlines.hsdeleted−919

This diff is too big to show here.

src/Text/Pandoc/Readers/Org/Meta.hsdeleted−296

This diff is too big to show here.

src/Text/Pandoc/Readers/Org/ParserState.hsdeleted−292

This diff is too big to show here.

src/Text/Pandoc/Readers/Org/Parsing.hsdeleted−218

This diff is too big to show here.

src/Text/Pandoc/Readers/Org/Shared.hsdeleted−80

This diff is too big to show here.

src/Text/Pandoc/Readers/RST.hs+471−1041

This diff is too big to show here.

src/Text/Pandoc/Readers/Roff.hsdeleted−728

This diff is too big to show here.

src/Text/Pandoc/Readers/TWiki.hsdeleted−492

This diff is too big to show here.

src/Text/Pandoc/Readers/TeXMath.hsnew file+42

This diff is too big to show here.

src/Text/Pandoc/Readers/Textile.hs+298−412

This diff is too big to show here.

src/Text/Pandoc/Readers/TikiWiki.hsdeleted−656

This diff is too big to show here.

src/Text/Pandoc/Readers/Txt2Tags.hsdeleted−596

This diff is too big to show here.

src/Text/Pandoc/Readers/Vimwiki.hsdeleted−671

This diff is too big to show here.

src/Text/Pandoc/RoffChar.hsdeleted−421

This diff is too big to show here.

src/Text/Pandoc/SelfContained.hs+115−237

This diff is too big to show here.

src/Text/Pandoc/Shared.hs+509−818

This diff is too big to show here.

src/Text/Pandoc/Slides.hs+25−12

This diff is too big to show here.

src/Text/Pandoc/Sources.hsdeleted−195

This diff is too big to show here.

src/Text/Pandoc/Templates.hs+305−106

This diff is too big to show here.

src/Text/Pandoc/Translations.hsdeleted−121

This diff is too big to show here.

src/Text/Pandoc/UTF8.hs+67−86

This diff is too big to show here.

src/Text/Pandoc/UUID.hs+35−19

This diff is too big to show here.

src/Text/Pandoc/Writers.hsdeleted−221

This diff is too big to show here.

src/Text/Pandoc/Writers/AnnotatedTable.hsdeleted−323

This diff is too big to show here.

src/Text/Pandoc/Writers/AsciiDoc.hs+202−415

This diff is too big to show here.

src/Text/Pandoc/Writers/BibTeX.hsdeleted−61

This diff is too big to show here.

src/Text/Pandoc/Writers/CommonMark.hsdeleted−17

This diff is too big to show here.

src/Text/Pandoc/Writers/ConTeXt.hs+197−418

This diff is too big to show here.

src/Text/Pandoc/Writers/CslJson.hsdeleted−91

This diff is too big to show here.

src/Text/Pandoc/Writers/Custom.hs+192−169

This diff is too big to show here.

src/Text/Pandoc/Writers/Docbook.hs+212−386

This diff is too big to show here.

src/Text/Pandoc/Writers/Docx.hs+568−1112

This diff is too big to show here.

src/Text/Pandoc/Writers/Docx/StyleMap.hsdeleted−47

This diff is too big to show here.

src/Text/Pandoc/Writers/Docx/Table.hsdeleted−227

This diff is too big to show here.

src/Text/Pandoc/Writers/Docx/Types.hsdeleted−185

This diff is too big to show here.

src/Text/Pandoc/Writers/DokuWiki.hsdeleted−522

This diff is too big to show here.

src/Text/Pandoc/Writers/EPUB.hs+397−1350

This diff is too big to show here.

src/Text/Pandoc/Writers/FB2.hs+376−326

This diff is too big to show here.

src/Text/Pandoc/Writers/GridTable.hsdeleted−157

This diff is too big to show here.

src/Text/Pandoc/Writers/HTML.hs+586−1404

This diff is too big to show here.

src/Text/Pandoc/Writers/Haddock.hsdeleted−283

This diff is too big to show here.

src/Text/Pandoc/Writers/ICML.hsdeleted−635

This diff is too big to show here.

src/Text/Pandoc/Writers/Ipynb.hsdeleted−239

This diff is too big to show here.

src/Text/Pandoc/Writers/JATS.hsdeleted−579

This diff is too big to show here.

src/Text/Pandoc/Writers/JATS/References.hsdeleted−164

This diff is too big to show here.

src/Text/Pandoc/Writers/JATS/Table.hsdeleted−268

This diff is too big to show here.

src/Text/Pandoc/Writers/JATS/Types.hsdeleted−57

This diff is too big to show here.

src/Text/Pandoc/Writers/Jira.hsdeleted−339

This diff is too big to show here.

src/Text/Pandoc/Writers/LaTeX.hs+568−838

This diff is too big to show here.

src/Text/Pandoc/Writers/LaTeX/Caption.hsdeleted−47

This diff is too big to show here.

src/Text/Pandoc/Writers/LaTeX/Citation.hsdeleted−181

This diff is too big to show here.

src/Text/Pandoc/Writers/LaTeX/Lang.hsdeleted−192

This diff is too big to show here.

src/Text/Pandoc/Writers/LaTeX/Notes.hsdeleted−34

This diff is too big to show here.

src/Text/Pandoc/Writers/LaTeX/Table.hsdeleted−307

This diff is too big to show here.

src/Text/Pandoc/Writers/LaTeX/Types.hsdeleted−83

This diff is too big to show here.

src/Text/Pandoc/Writers/LaTeX/Util.hsdeleted−275

This diff is too big to show here.

src/Text/Pandoc/Writers/Man.hs+212−185

This diff is too big to show here.

src/Text/Pandoc/Writers/Markdown.hs+632−669

This diff is too big to show here.

src/Text/Pandoc/Writers/Markdown/Inline.hsdeleted−616

This diff is too big to show here.

src/Text/Pandoc/Writers/Markdown/Types.hsdeleted−81

This diff is too big to show here.

src/Text/Pandoc/Writers/Math.hsdeleted−53

This diff is too big to show here.

src/Text/Pandoc/Writers/MediaWiki.hs+273−964

This diff is too big to show here.

src/Text/Pandoc/Writers/Ms.hsdeleted−614

This diff is too big to show here.

src/Text/Pandoc/Writers/Muse.hsdeleted−720

This diff is too big to show here.

src/Text/Pandoc/Writers/Native.hs+44−59

This diff is too big to show here.

src/Text/Pandoc/Writers/ODT.hs+79−224

This diff is too big to show here.

src/Text/Pandoc/Writers/OOXML.hsdeleted−99

This diff is too big to show here.

src/Text/Pandoc/Writers/OPML.hs+66−55

This diff is too big to show here.

src/Text/Pandoc/Writers/OpenDocument.hs+323−681

This diff is too big to show here.

src/Text/Pandoc/Writers/Org.hs+150−338

This diff is too big to show here.

src/Text/Pandoc/Writers/Powerpoint.hsdeleted−43

This diff is too big to show here.

src/Text/Pandoc/Writers/Powerpoint/Output.hsdeleted−1922

This diff is too big to show here.

src/Text/Pandoc/Writers/Powerpoint/Presentation.hsdeleted−1004

This diff is too big to show here.

src/Text/Pandoc/Writers/RST.hs+243−578

This diff is too big to show here.

src/Text/Pandoc/Writers/RTF.hs+229−293

This diff is too big to show here.

src/Text/Pandoc/Writers/Roff.hsdeleted−125

This diff is too big to show here.

src/Text/Pandoc/Writers/Sable.hsnew file+427

This diff is too big to show here.

src/Text/Pandoc/Writers/Shared.hs+106−487

This diff is too big to show here.

src/Text/Pandoc/Writers/TEI.hsdeleted−305

This diff is too big to show here.

src/Text/Pandoc/Writers/Texinfo.hs+187−219

This diff is too big to show here.

src/Text/Pandoc/Writers/Textile.hs+204−260

This diff is too big to show here.

src/Text/Pandoc/Writers/XWiki.hsdeleted−267

This diff is too big to show here.

src/Text/Pandoc/Writers/ZimWiki.hsdeleted−393

This diff is too big to show here.

src/Text/Pandoc/XML.hs+63−471

This diff is too big to show here.

src/Text/Pandoc/XML/Light.hsdeleted−89

This diff is too big to show here.

src/Text/Pandoc/XML/Light/Output.hsdeleted−234

This diff is too big to show here.

src/Text/Pandoc/XML/Light/Proc.hsdeleted−139

This diff is too big to show here.

src/Text/Pandoc/XML/Light/Types.hsdeleted−193

This diff is too big to show here.

stack.yamldeleted−22

This diff is too big to show here.

test/Tests/Command.hsdeleted−136

This diff is too big to show here.

test/Tests/Helpers.hsdeleted−151

This diff is too big to show here.

test/Tests/Lua.hsdeleted−242

This diff is too big to show here.

test/Tests/Lua/Module.hsdeleted−37

This diff is too big to show here.

test/Tests/Old.hsdeleted−343

This diff is too big to show here.

test/Tests/Readers/Creole.hsdeleted−298

This diff is too big to show here.

test/Tests/Readers/Docx.hsdeleted−474

This diff is too big to show here.

test/Tests/Readers/DokuWiki.hsdeleted−321

This diff is too big to show here.

test/Tests/Readers/EPUB.hsdeleted−86

This diff is too big to show here.

test/Tests/Readers/FB2.hsdeleted−39

This diff is too big to show here.

test/Tests/Readers/HTML.hsdeleted−127

This diff is too big to show here.

test/Tests/Readers/JATS.hsdeleted−145

This diff is too big to show here.

test/Tests/Readers/Jira.hsdeleted−204

This diff is too big to show here.

test/Tests/Readers/LaTeX.hsdeleted−429

This diff is too big to show here.

test/Tests/Readers/Man.hsdeleted−144

This diff is too big to show here.

test/Tests/Readers/Markdown.hsdeleted−528

This diff is too big to show here.

test/Tests/Readers/Muse.hsdeleted−1653

This diff is too big to show here.

test/Tests/Readers/Odt.hsdeleted−185

This diff is too big to show here.

test/Tests/Readers/Org.hsdeleted−27

This diff is too big to show here.

test/Tests/Readers/Org/Block.hsdeleted−213

This diff is too big to show here.

test/Tests/Readers/Org/Block/CodeBlock.hsdeleted−205

This diff is too big to show here.

test/Tests/Readers/Org/Block/Figure.hsdeleted−75

This diff is too big to show here.

test/Tests/Readers/Org/Block/Header.hsdeleted−272

This diff is too big to show here.

test/Tests/Readers/Org/Block/List.hsdeleted−279

This diff is too big to show here.

test/Tests/Readers/Org/Block/Table.hsdeleted−186

This diff is too big to show here.

test/Tests/Readers/Org/Directive.hsdeleted−359

This diff is too big to show here.

test/Tests/Readers/Org/Inline.hsdeleted−385

This diff is too big to show here.

test/Tests/Readers/Org/Inline/Citation.hsdeleted−230

This diff is too big to show here.

test/Tests/Readers/Org/Inline/Note.hsdeleted−97

This diff is too big to show here.

test/Tests/Readers/Org/Inline/Smart.hsdeleted−57

This diff is too big to show here.

test/Tests/Readers/Org/Meta.hsdeleted−292

This diff is too big to show here.

test/Tests/Readers/Org/Shared.hsdeleted−41

This diff is too big to show here.

test/Tests/Readers/RST.hsdeleted−214

This diff is too big to show here.

test/Tests/Readers/Txt2Tags.hsdeleted−465

This diff is too big to show here.

test/Tests/Shared.hsdeleted−112

This diff is too big to show here.

test/Tests/Writers/AnnotatedTable.hsdeleted−253

This diff is too big to show here.

test/Tests/Writers/AsciiDoc.hsdeleted−63

This diff is too big to show here.

test/Tests/Writers/ConTeXt.hsdeleted−163

This diff is too big to show here.

test/Tests/Writers/Docbook.hsdeleted−406

This diff is too big to show here.

test/Tests/Writers/Docx.hsdeleted−196

This diff is too big to show here.

test/Tests/Writers/FB2.hsdeleted−34

This diff is too big to show here.

test/Tests/Writers/HTML.hsdeleted−93

This diff is too big to show here.

test/Tests/Writers/JATS.hsdeleted−164

This diff is too big to show here.

test/Tests/Writers/Jira.hsdeleted−124

This diff is too big to show here.

test/Tests/Writers/LaTeX.hsdeleted−176

This diff is too big to show here.

test/Tests/Writers/Markdown.hsdeleted−269

This diff is too big to show here.

test/Tests/Writers/Ms.hsdeleted−35

This diff is too big to show here.

test/Tests/Writers/Muse.hsdeleted−658

This diff is too big to show here.

test/Tests/Writers/Native.hsdeleted−22

This diff is too big to show here.

test/Tests/Writers/OOXML.hsdeleted−187

This diff is too big to show here.

test/Tests/Writers/Org.hsdeleted−60

This diff is too big to show here.

test/Tests/Writers/Plain.hsdeleted−23

This diff is too big to show here.

test/Tests/Writers/Powerpoint.hsdeleted−132

This diff is too big to show here.

test/Tests/Writers/RST.hsdeleted−178

This diff is too big to show here.

test/Tests/Writers/TEI.hsdeleted−43

This diff is too big to show here.

test/command/01.csvdeleted−4

This diff is too big to show here.

test/command/1126.mddeleted−28

This diff is too big to show here.

test/command/1166.mddeleted−48

This diff is too big to show here.

test/command/1279.mddeleted−19

This diff is too big to show here.

test/command/1390.mddeleted−20

This diff is too big to show here.

test/command/1592.mddeleted−70

This diff is too big to show here.

test/command/1608.mddeleted−41

This diff is too big to show here.

test/command/1629.mddeleted−10

This diff is too big to show here.

test/command/168.mddeleted−43

This diff is too big to show here.

test/command/1710.mddeleted−85

This diff is too big to show here.

test/command/1718.mddeleted−11

This diff is too big to show here.

test/command/1745.mddeleted−13

This diff is too big to show here.

test/command/1762.mddeleted−18

This diff is too big to show here.

test/command/1773.mddeleted−6

This diff is too big to show here.

test/command/1841.mddeleted−42

This diff is too big to show here.

test/command/1881.mddeleted−87

This diff is too big to show here.

test/command/1905.mddeleted−30

This diff is too big to show here.

test/command/2103.mddeleted−8

This diff is too big to show here.

test/command/2118.mddeleted−11

This diff is too big to show here.

test/command/2228.mddeleted−6

This diff is too big to show here.

test/command/2378.mddeleted−27

This diff is too big to show here.

test/command/2397.mddeleted−9

This diff is too big to show here.

test/command/2434.mddeleted−59

This diff is too big to show here.

test/command/2549.mddeleted−38

This diff is too big to show here.

test/command/2552.mddeleted−14

This diff is too big to show here.

test/command/256.mddeleted−12

This diff is too big to show here.

test/command/2602.mddeleted−18

This diff is too big to show here.

test/command/2606.mddeleted−58

This diff is too big to show here.

test/command/262.mddeleted−26

This diff is too big to show here.

test/command/2649.mddeleted−108

This diff is too big to show here.

test/command/2662.mddeleted−11

This diff is too big to show here.

test/command/2834.mddeleted−29

This diff is too big to show here.

test/command/2874.mddeleted−14

This diff is too big to show here.

test/command/2994.mddeleted−10

This diff is too big to show here.

test/command/3113.mddeleted−13

This diff is too big to show here.

test/command/3123.mddeleted−13

This diff is too big to show here.

test/command/3236.mddeleted−9

This diff is too big to show here.

test/command/3257.mddeleted−13

This diff is too big to show here.

test/command/3309.mddeleted−52

This diff is too big to show here.

test/command/3314.mddeleted−34

This diff is too big to show here.

test/command/3324.mddeleted−18

This diff is too big to show here.

test/command/3337.mddeleted−13

This diff is too big to show here.

test/command/3348.mddeleted−30

This diff is too big to show here.

test/command/3401.mddeleted−19

This diff is too big to show here.

test/command/3407.mddeleted−13

This diff is too big to show here.

test/command/3422.mddeleted−9

This diff is too big to show here.

test/command/3432.mddeleted−289

This diff is too big to show here.

test/command/3432a.mddeleted−19

This diff is too big to show here.

test/command/3450.mddeleted−12

This diff is too big to show here.

test/command/3475.mddeleted−45

This diff is too big to show here.

test/command/3487.mddeleted−11

This diff is too big to show here.

test/command/3494.mddeleted−40

This diff is too big to show here.

test/command/3497.mddeleted−51

This diff is too big to show here.

test/command/3499.mddeleted−18

This diff is too big to show here.

test/command/3510-export.latexdeleted−1

This diff is too big to show here.

test/command/3510-src.hsdeleted−1

This diff is too big to show here.

test/command/3510-subdoc.orgdeleted−5

This diff is too big to show here.

test/command/3510.mddeleted−20

This diff is too big to show here.

test/command/3511.mddeleted−46

This diff is too big to show here.

test/command/3512.mddeleted−13

This diff is too big to show here.

test/command/3516.mddeleted−81

This diff is too big to show here.

test/command/3518.mddeleted−6

This diff is too big to show here.

test/command/3523.mddeleted−31

This diff is too big to show here.

test/command/3526.mddeleted−14

This diff is too big to show here.

test/command/3529.mddeleted−15

This diff is too big to show here.

test/command/3530.mddeleted−19

This diff is too big to show here.

test/command/3531.mddeleted−20

This diff is too big to show here.

test/command/3533-rst-csv-tables.csvdeleted−4

This diff is too big to show here.

test/command/3533-rst-csv-tables.mddeleted−108

This diff is too big to show here.

test/command/3534.mddeleted−45

This diff is too big to show here.

test/command/3537.mddeleted−28

This diff is too big to show here.

test/command/3539.mddeleted−45

This diff is too big to show here.

test/command/3558.mddeleted−12

This diff is too big to show here.

test/command/3568.mddeleted−16

This diff is too big to show here.

test/command/3570.mddeleted−6

This diff is too big to show here.

test/command/3577.mddeleted−35

This diff is too big to show here.

test/command/3585.mddeleted−16

This diff is too big to show here.

test/command/3587.mddeleted−147

This diff is too big to show here.

test/command/3596.mddeleted−59

This diff is too big to show here.

test/command/3615.mddeleted−18

This diff is too big to show here.

test/command/3619.mddeleted−28

This diff is too big to show here.

test/command/3630.mddeleted−8

This diff is too big to show here.

test/command/3667.mddeleted−13

This diff is too big to show here.

test/command/3674.mddeleted−39

This diff is too big to show here.

test/command/3675.mddeleted−15

This diff is too big to show here.

test/command/3681.mddeleted−27

This diff is too big to show here.

test/command/3690.mddeleted−8

This diff is too big to show here.

test/command/3701.mddeleted−60

This diff is too big to show here.

test/command/3706.mddeleted−65

This diff is too big to show here.

test/command/3708.mddeleted−28

This diff is too big to show here.

test/command/3715.mddeleted−15

This diff is too big to show here.

test/command/3716.mddeleted−6

This diff is too big to show here.

test/command/3730.mddeleted−21

This diff is too big to show here.

test/command/3733.mddeleted−13

This diff is too big to show here.

test/command/3734.mddeleted−32

This diff is too big to show here.

test/command/3736.mddeleted−22

This diff is too big to show here.

test/command/3752.mddeleted−60

This diff is too big to show here.

test/command/3755.mddeleted−23

This diff is too big to show here.

test/command/3771.mddeleted−14

This diff is too big to show here.

test/command/3773.mddeleted−14

This diff is too big to show here.

test/command/3779.mddeleted−28

This diff is too big to show here.

test/command/3792.mddeleted−13

This diff is too big to show here.

test/command/3794.mddeleted−7

This diff is too big to show here.

test/command/3803.mddeleted−10

This diff is too big to show here.

test/command/3804.mddeleted−6

This diff is too big to show here.

test/command/3816.mddeleted−32

This diff is too big to show here.

test/command/3824.mddeleted−14

This diff is too big to show here.

test/command/3840.mddeleted−15

This diff is too big to show here.

test/command/3853.mddeleted−26

This diff is too big to show here.

test/command/3880.mddeleted−6

This diff is too big to show here.

test/command/3880.txtdeleted−1

This diff is too big to show here.

test/command/3916.mddeleted−11

This diff is too big to show here.

test/command/3937.mddeleted−13

This diff is too big to show here.

test/command/3947.mddeleted−11

This diff is too big to show here.

test/command/3958.mddeleted−20

This diff is too big to show here.

test/command/3968.mddeleted−10

This diff is too big to show here.

test/command/3971.mddeleted−9

This diff is too big to show here.

test/command/3971b.texdeleted−2

This diff is too big to show here.

test/command/3974.mddeleted−6

This diff is too big to show here.

test/command/3978.mddeleted−6

This diff is too big to show here.

test/command/3983.mddeleted−29

This diff is too big to show here.

test/command/3989.mddeleted−7

This diff is too big to show here.

test/command/4007.mddeleted−23

This diff is too big to show here.

test/command/4012.mddeleted−8

This diff is too big to show here.

test/command/4016.mddeleted−42

This diff is too big to show here.

test/command/4019.mddeleted−8

This diff is too big to show here.

test/command/4038.mddeleted−6

This diff is too big to show here.

test/command/4054.mddeleted−14

This diff is too big to show here.

test/command/4056.mddeleted−35

This diff is too big to show here.

test/command/4061.mddeleted−14

This diff is too big to show here.

test/command/4062.mddeleted−6

This diff is too big to show here.

test/command/4063.mddeleted−29

This diff is too big to show here.

test/command/4068.mddeleted−9

This diff is too big to show here.

test/command/4091.mddeleted−6

This diff is too big to show here.

test/command/4113.mddeleted−12

This diff is too big to show here.

test/command/4119.mddeleted−32

This diff is too big to show here.

test/command/4125.mddeleted−6

This diff is too big to show here.

test/command/4134.mddeleted−25

This diff is too big to show here.

test/command/4156.mddeleted−10

This diff is too big to show here.

test/command/4159.mddeleted−8

This diff is too big to show here.

test/command/4162.mddeleted−10

This diff is too big to show here.

test/command/4164.mddeleted−31

This diff is too big to show here.

test/command/4171.mddeleted−34

This diff is too big to show here.

test/command/4172.mddeleted−29

This diff is too big to show here.

test/command/4183.mddeleted−32

This diff is too big to show here.

test/command/4186.mddeleted−60

This diff is too big to show here.

test/command/4193.mddeleted−10

This diff is too big to show here.

test/command/4199.mddeleted−6

This diff is too big to show here.

test/command/4208.mddeleted−18

This diff is too big to show here.

test/command/4235.mddeleted−12

This diff is too big to show here.

test/command/4240.mddeleted−33

This diff is too big to show here.

test/command/4253.mddeleted−8

This diff is too big to show here.

test/command/4254.mddeleted−12

This diff is too big to show here.

test/command/4280.mddeleted−7

This diff is too big to show here.

test/command/4281.mddeleted−18

This diff is too big to show here.

test/command/4284.mddeleted−40

This diff is too big to show here.

test/command/4306.mddeleted−10

This diff is too big to show here.

test/command/4320.mddeleted−29

This diff is too big to show here.

test/command/4374.mddeleted−7

This diff is too big to show here.

test/command/4382.mddeleted−10

This diff is too big to show here.

test/command/4420.mddeleted−11

This diff is too big to show here.

test/command/4424.mddeleted−10

This diff is too big to show here.

test/command/4442.mddeleted−9

This diff is too big to show here.

test/command/4454.mddeleted−9

This diff is too big to show here.

test/command/4465.mddeleted−15

This diff is too big to show here.

test/command/4499.mddeleted−87

This diff is too big to show here.

test/command/4513.mddeleted−20

This diff is too big to show here.

test/command/4527.mddeleted−36

This diff is too big to show here.

test/command/4528.mddeleted−156

This diff is too big to show here.

test/command/4529.mddeleted−36

This diff is too big to show here.

test/command/4545.mddeleted−20

This diff is too big to show here.

test/command/4550.mddeleted−7

This diff is too big to show here.

test/command/4553.mddeleted−15

This diff is too big to show here.

test/command/4576.mddeleted−6

This diff is too big to show here.

test/command/4578.mddeleted−14

This diff is too big to show here.

test/command/4579.mddeleted−30

This diff is too big to show here.

test/command/4589.mddeleted−14

This diff is too big to show here.

test/command/4594.mddeleted−24

This diff is too big to show here.

test/command/4598.mddeleted−10

This diff is too big to show here.

test/command/4624.mddeleted−30

This diff is too big to show here.

test/command/4635.mddeleted−31

This diff is too big to show here.

test/command/4637.mddeleted−6

This diff is too big to show here.

test/command/4639.mddeleted−10

This diff is too big to show here.

test/command/4653.mddeleted−8

This diff is too big to show here.

test/command/4667.mddeleted−20

This diff is too big to show here.

test/command/4669.mddeleted−29

This diff is too big to show here.

test/command/4677.mddeleted−8

This diff is too big to show here.

test/command/4690.mddeleted−26

This diff is too big to show here.

test/command/4715.mddeleted−16

This diff is too big to show here.

test/command/4722.mddeleted−34

This diff is too big to show here.

test/command/4742.mddeleted−29

This diff is too big to show here.

test/command/4743.mddeleted−25

This diff is too big to show here.

test/command/4748.mddeleted−16

This diff is too big to show here.

test/command/4768.mddeleted−7

This diff is too big to show here.

test/command/4781.mddeleted−22

This diff is too big to show here.

test/command/4794.mddeleted−17

This diff is too big to show here.

test/command/4805-beamer-columns-alignment.mddeleted−40

This diff is too big to show here.

test/command/4811.mddeleted−48

This diff is too big to show here.

test/command/4817.mddeleted−10

This diff is too big to show here.

test/command/4819.mddeleted−50

This diff is too big to show here.

test/command/4832.mddeleted−21

This diff is too big to show here.

test/command/4833.mddeleted−20

This diff is too big to show here.

test/command/4842.mddeleted−6

This diff is too big to show here.

test/command/4845.mddeleted−6

This diff is too big to show here.

test/command/4848.mddeleted−59

This diff is too big to show here.

test/command/4860.mddeleted−9

This diff is too big to show here.

test/command/4877.mddeleted−13

This diff is too big to show here.

test/command/4880.mddeleted−7

This diff is too big to show here.

test/command/4885.mddeleted−8

This diff is too big to show here.

test/command/4908.mddeleted−16

This diff is too big to show here.

test/command/4913.mddeleted−34

This diff is too big to show here.

test/command/4919.mddeleted−14

This diff is too big to show here.

test/command/4928.mddeleted−48

This diff is too big to show here.

test/command/4933.mddeleted−6

This diff is too big to show here.

test/command/4960.mddeleted−22

This diff is too big to show here.

test/command/5010.mddeleted−21

This diff is too big to show here.

test/command/5014.mddeleted−30

This diff is too big to show here.

test/command/5039.mddeleted−27

This diff is too big to show here.

test/command/5050.mddeleted−7

This diff is too big to show here.

test/command/5053.mddeleted−14

This diff is too big to show here.

test/command/5072.mddeleted−14

This diff is too big to show here.

test/command/5079.mddeleted−25

This diff is too big to show here.

test/command/5080.mddeleted−13

This diff is too big to show here.

test/command/5099.mddeleted−13

This diff is too big to show here.

test/command/5107.mddeleted−23

This diff is too big to show here.

test/command/5119.mddeleted−9

This diff is too big to show here.

test/command/512.mddeleted−42

This diff is too big to show here.

test/command/5121.mddeleted−12

This diff is too big to show here.

test/command/5128.mddeleted−26

This diff is too big to show here.

test/command/5177.mddeleted−12

This diff is too big to show here.

test/command/5178.mddeleted−41

This diff is too big to show here.

test/command/5182.mddeleted−6

This diff is too big to show here.

test/command/5182.txtdeleted−5

This diff is too big to show here.

test/command/5195.mddeleted−7

This diff is too big to show here.

test/command/5233.mddeleted−9

This diff is too big to show here.

test/command/5241.mddeleted−12

This diff is too big to show here.

test/command/5271.mddeleted−12

This diff is too big to show here.

test/command/5285.mddeleted−32

This diff is too big to show here.

test/command/5304.mddeleted−24

This diff is too big to show here.

test/command/5321.mddeleted−24

This diff is too big to show here.

test/command/5340.mddeleted−14

This diff is too big to show here.

test/command/5360.mddeleted−19

This diff is too big to show here.

test/command/5367.mddeleted−43

This diff is too big to show here.

test/command/5368.mddeleted−23

This diff is too big to show here.

test/command/5369.mddeleted−7

This diff is too big to show here.

test/command/5407.mddeleted−14

This diff is too big to show here.

test/command/5410.mddeleted−7

This diff is too big to show here.

test/command/5416.mddeleted−13

This diff is too big to show here.

test/command/5420.mddeleted−6

This diff is too big to show here.

test/command/5439.mddeleted−6

This diff is too big to show here.

test/command/5446.mddeleted−6

This diff is too big to show here.

test/command/5474-figures.mddeleted−15

This diff is too big to show here.

test/command/5474-tables.mddeleted−63

This diff is too big to show here.

test/command/5476.mddeleted−12

This diff is too big to show here.

test/command/5495.mddeleted−18

This diff is too big to show here.

test/command/5519.mddeleted−14

This diff is too big to show here.

test/command/5529.mddeleted−10

This diff is too big to show here.

test/command/5540.mddeleted−8

This diff is too big to show here.

test/command/5541-localLink.mddeleted−149

This diff is too big to show here.

test/command/5541-nesting.mddeleted−98

This diff is too big to show here.

test/command/5541-urlLink.mddeleted−112

This diff is too big to show here.

test/command/5543.mddeleted−8

This diff is too big to show here.

test/command/5549.mddeleted−9

This diff is too big to show here.

test/command/5565.mddeleted−6

This diff is too big to show here.

test/command/5566.mddeleted−6

This diff is too big to show here.

test/command/5574.mddeleted−8

This diff is too big to show here.

test/command/5619.mddeleted−10

This diff is too big to show here.

test/command/5620.mddeleted−9

This diff is too big to show here.

test/command/5627.mddeleted−83

This diff is too big to show here.

test/command/5635.mddeleted−23

This diff is too big to show here.

test/command/5642.mddeleted−8

This diff is too big to show here.

test/command/5650.mddeleted−22

This diff is too big to show here.

test/command/5654.mddeleted−6

This diff is too big to show here.

test/command/5655.mddeleted−14

This diff is too big to show here.

test/command/5682.mddeleted−8

This diff is too big to show here.

test/command/5684.mddeleted−6

This diff is too big to show here.

test/command/5686.mddeleted−9

This diff is too big to show here.

test/command/5690.mddeleted−16

This diff is too big to show here.

test/command/5700-metadata-file-1.ymldeleted−1

This diff is too big to show here.

test/command/5700-metadata-file-2.ymldeleted−2

This diff is too big to show here.

test/command/5700.mddeleted−6

This diff is too big to show here.

test/command/5705.mddeleted−11

This diff is too big to show here.

test/command/5708.mddeleted−22

This diff is too big to show here.

test/command/5711.mddeleted−22

This diff is too big to show here.

test/command/5714.mddeleted−13

This diff is too big to show here.

test/command/5740.mddeleted−9

This diff is too big to show here.

test/command/5753.mddeleted−15

This diff is too big to show here.

test/command/5795.mddeleted−20

This diff is too big to show here.

test/command/5797.mddeleted−20

This diff is too big to show here.

test/command/5805.mddeleted−20

This diff is too big to show here.

test/command/5813.mddeleted−6

This diff is too big to show here.

test/command/5819.mddeleted−18

This diff is too big to show here.

test/command/5836.mddeleted−27

This diff is too big to show here.

test/command/5845.mddeleted−16

This diff is too big to show here.

test/command/5846.mddeleted−170

This diff is too big to show here.

test/command/5849-prefix.mddeleted−31

This diff is too big to show here.

test/command/5857.mddeleted−11

This diff is too big to show here.

test/command/5878.mddeleted−7

This diff is too big to show here.

test/command/5881.mddeleted−14

This diff is too big to show here.

test/command/5885.mddeleted−20

This diff is too big to show here.

test/command/5898.mddeleted−36

This diff is too big to show here.

test/command/5899.mddeleted−51

This diff is too big to show here.

test/command/5904.mddeleted−10

This diff is too big to show here.

test/command/5918.mddeleted−6

This diff is too big to show here.

test/command/5936.mddeleted−40

This diff is too big to show here.

test/command/5967.mddeleted−15

This diff is too big to show here.

test/command/5986.mddeleted−17

This diff is too big to show here.

test/command/6009.mddeleted−18

This diff is too big to show here.

test/command/6026.mddeleted−19

This diff is too big to show here.

test/command/6030.mddeleted−96

This diff is too big to show here.

test/command/6033.mddeleted−91

This diff is too big to show here.

test/command/6034.mddeleted−11

This diff is too big to show here.

test/command/6043.mddeleted−8

This diff is too big to show here.

test/command/6062.mddeleted−6

This diff is too big to show here.

test/command/6107.mddeleted−27

This diff is too big to show here.

test/command/6114.mddeleted−7

This diff is too big to show here.

test/command/6119.mddeleted−10

This diff is too big to show here.

test/command/6133.mddeleted−12

This diff is too big to show here.

test/command/6137.mddeleted−47

This diff is too big to show here.

test/command/6194.mddeleted−14

This diff is too big to show here.

test/command/6265.mddeleted−6

This diff is too big to show here.

test/command/6288.mddeleted−8

This diff is too big to show here.

test/command/6296.mddeleted−14

This diff is too big to show here.

test/command/6308.mddeleted−18

This diff is too big to show here.

test/command/6324.mddeleted−17

This diff is too big to show here.

test/command/6360.mddeleted−6

This diff is too big to show here.

test/command/6385.mddeleted−18

This diff is too big to show here.

test/command/6388.mddeleted−16

This diff is too big to show here.

test/command/645.mddeleted−12

This diff is too big to show here.

test/command/6481.mddeleted−38

This diff is too big to show here.

test/command/6541.mddeleted−27

This diff is too big to show here.

test/command/6549.mddeleted−26

This diff is too big to show here.

test/command/6620.mddeleted−18

This diff is too big to show here.

test/command/6658.mddeleted−75

This diff is too big to show here.

test/command/6675.mddeleted−134

This diff is too big to show here.

test/command/6699.mddeleted−13

This diff is too big to show here.

test/command/6709.mddeleted−11

This diff is too big to show here.

test/command/6719.mddeleted−18

This diff is too big to show here.

test/command/6723.mddeleted−32

This diff is too big to show here.

test/command/6739.mddeleted−21

This diff is too big to show here.

test/command/6740.mddeleted−7

This diff is too big to show here.

test/command/6741.mddeleted−145

This diff is too big to show here.

test/command/6752.mddeleted−36

This diff is too big to show here.

test/command/6755.mddeleted−11

This diff is too big to show here.

test/command/6765.mddeleted−31

This diff is too big to show here.

test/command/6768.mddeleted−21

This diff is too big to show here.

test/command/6774.mddeleted−63

This diff is too big to show here.

test/command/6783.mddeleted−26

This diff is too big to show here.

test/command/6791.mddeleted−32

This diff is too big to show here.

test/command/6792.mddeleted−66

This diff is too big to show here.

test/command/6796.mddeleted−16

This diff is too big to show here.

test/command/6802.mddeleted−9

This diff is too big to show here.

test/command/6836.mddeleted−17

This diff is too big to show here.

test/command/6837.mddeleted−29

This diff is too big to show here.

test/command/6844.mddeleted−27

This diff is too big to show here.

test/command/6855.mddeleted−12

This diff is too big to show here.

test/command/6858.mddeleted−52

This diff is too big to show here.

test/command/6869.mddeleted−6

This diff is too big to show here.

test/command/6873.mddeleted−7

This diff is too big to show here.

test/command/6890.mddeleted−36

This diff is too big to show here.

test/command/6925.mddeleted−34

This diff is too big to show here.

test/command/6948.mddeleted−31

This diff is too big to show here.

test/command/6951.mddeleted−18

This diff is too big to show here.

test/command/6958.mddeleted−10

This diff is too big to show here.

test/command/6993.mddeleted−21

This diff is too big to show here.

test/command/7003.mddeleted−37

This diff is too big to show here.

test/command/7006.mddeleted−20

This diff is too big to show here.

test/command/7009.mddeleted−8

This diff is too big to show here.

test/command/7016.mddeleted−48

This diff is too big to show here.

test/command/7041.mddeleted−23

This diff is too big to show here.

test/command/7042.mddeleted−146

This diff is too big to show here.

test/command/7058.mddeleted−6

This diff is too big to show here.

test/command/7064.mddeleted−32

This diff is too big to show here.

test/command/7067.mddeleted−90

This diff is too big to show here.

test/command/7080.mddeleted−8

This diff is too big to show here.

test/command/7092.mddeleted−8

This diff is too big to show here.

test/command/7099.mddeleted−18

This diff is too big to show here.

test/command/7112.mddeleted−15

This diff is too big to show here.

test/command/7129.mddeleted−27

This diff is too big to show here.

test/command/7132.mddeleted−10

This diff is too big to show here.

test/command/7134.mddeleted−16

This diff is too big to show here.

test/command/7145.mddeleted−12

This diff is too big to show here.

test/command/7155.mddeleted−15

This diff is too big to show here.

test/command/7173.mddeleted−137

This diff is too big to show here.

test/command/7208.mddeleted−6

This diff is too big to show here.

test/command/7214.mddeleted−28

This diff is too big to show here.

test/command/7216.mddeleted−19

This diff is too big to show here.

test/command/7266.mddeleted−10

This diff is too big to show here.

test/command/7272.mddeleted−27

This diff is too big to show here.

test/command/7278.mddeleted−38

This diff is too big to show here.

test/command/7282.mddeleted−7

This diff is too big to show here.

test/command/7288.mddeleted−40

This diff is too big to show here.

test/command/7299.mddeleted−23

This diff is too big to show here.

test/command/7321.mddeleted−24

This diff is too big to show here.

test/command/7323.mddeleted−29

This diff is too big to show here.

test/command/7324.mddeleted−25

This diff is too big to show here.

test/command/7339.mddeleted−11

This diff is too big to show here.

test/command/7340.mddeleted−6

This diff is too big to show here.

test/command/7376.mddeleted−16

This diff is too big to show here.

test/command/7394.mddeleted−85

This diff is too big to show here.

test/command/7397.mddeleted−14

This diff is too big to show here.

test/command/7400.mddeleted−9

This diff is too big to show here.

test/command/7416.mddeleted−19

This diff is too big to show here.

test/command/853.mddeleted−18

This diff is too big to show here.

test/command/934.mddeleted−12

This diff is too big to show here.

test/command/982.mddeleted−11

This diff is too big to show here.

test/command/987.mddeleted−12

This diff is too big to show here.

test/command/A.txtdeleted−1

This diff is too big to show here.

test/command/B.txtdeleted−1

This diff is too big to show here.

test/command/C.txtdeleted−1

This diff is too big to show here.

test/command/D.txtdeleted−1

This diff is too big to show here.

test/command/SVG_logo-without-xml-declaration.svgdeleted−32

This diff is too big to show here.

test/command/SVG_logo.svgdeleted−33

This diff is too big to show here.

test/command/abbrevsdeleted−2

This diff is too big to show here.

test/command/adjacent_latex_blocks.mddeleted−9

This diff is too big to show here.

test/command/advanced-optical-materials.csldeleted−155

This diff is too big to show here.

test/command/annales.csldeleted−334

This diff is too big to show here.

test/command/apa.csldeleted−474

This diff is too big to show here.

test/command/archeologie-medievale.csldeleted−291

This diff is too big to show here.

test/command/ascii.mddeleted−89

This diff is too big to show here.

test/command/averroes.bibdeleted−95

This diff is too big to show here.

test/command/bar.texdeleted−1

This diff is too big to show here.

test/command/biblatex-266.mddeleted−34

This diff is too big to show here.

test/command/biblatex-aksin.mddeleted−78

This diff is too big to show here.

test/command/biblatex-almendro.mddeleted−71

This diff is too big to show here.

test/command/biblatex-angenendt.mddeleted−66

This diff is too big to show here.

test/command/biblatex-aristotle-anima.mddeleted−62

This diff is too big to show here.

test/command/biblatex-aristotle-physics.mddeleted−63

This diff is too big to show here.

test/command/biblatex-aristotle-poetics.mddeleted−65

This diff is too big to show here.

test/command/biblatex-aristotle-rhetoric.mddeleted−80

This diff is too big to show here.

test/command/biblatex-article.mddeleted−128

This diff is too big to show here.

test/command/biblatex-augustine.mddeleted−56

This diff is too big to show here.

test/command/biblatex-averroes-bland.mddeleted−85

This diff is too big to show here.

test/command/biblatex-averroes-hannes.mddeleted−84

This diff is too big to show here.

test/command/biblatex-averroes-hercz.mddeleted−85

This diff is too big to show here.

test/command/biblatex-baez-article.mddeleted−76

This diff is too big to show here.

test/command/biblatex-baez-online.mddeleted−69

This diff is too big to show here.

test/command/biblatex-basic.mddeleted−71

This diff is too big to show here.

test/command/biblatex-bertram.mddeleted−66

This diff is too big to show here.

test/command/biblatex-bibstring-resolution.mddeleted−20

This diff is too big to show here.

test/command/biblatex-book-averroes.mddeleted−129

This diff is too big to show here.

test/command/biblatex-book-coleridge.mddeleted−59

This diff is too big to show here.

test/command/biblatex-book-title-maintitle-series.mddeleted−39

This diff is too big to show here.

test/command/biblatex-book-vazques-de-parga.mddeleted−48

This diff is too big to show here.

test/command/biblatex-brandt.mddeleted−88

This diff is too big to show here.

test/command/biblatex-britannica.mddeleted−85

This diff is too big to show here.

test/command/biblatex-chiu.mddeleted−77

This diff is too big to show here.

test/command/biblatex-cicero.mddeleted−82

This diff is too big to show here.

test/command/biblatex-cms.mddeleted−81

This diff is too big to show here.

test/command/biblatex-coleridge.mddeleted−86

This diff is too big to show here.

test/command/biblatex-companion.mddeleted−70

This diff is too big to show here.

test/command/biblatex-cotton.mddeleted−69

This diff is too big to show here.

test/command/biblatex-crossref-inbook-mvbook.mddeleted−58

This diff is too big to show here.

test/command/biblatex-crossref-nested.mddeleted−100

This diff is too big to show here.

test/command/biblatex-ctan.mddeleted−73

This diff is too big to show here.

test/command/biblatex-dates.mddeleted−162

This diff is too big to show here.

test/command/biblatex-doody.mddeleted−101

This diff is too big to show here.

test/command/biblatex-edtf-date.mddeleted−72

This diff is too big to show here.

test/command/biblatex-escapedquotes.mddeleted−51

This diff is too big to show here.

test/command/biblatex-formatting.mddeleted−23

This diff is too big to show here.

test/command/biblatex-gaonkar-in.mddeleted−62

This diff is too big to show here.

test/command/biblatex-gaonkar.mddeleted−59

This diff is too big to show here.

test/command/biblatex-geer.mddeleted−70

This diff is too big to show here.

test/command/biblatex-gerhardt.mddeleted−64

This diff is too big to show here.

test/command/biblatex-gillies.mddeleted−69

This diff is too big to show here.

test/command/biblatex-glashow.mddeleted−51

This diff is too big to show here.

test/command/biblatex-gonzalez.mddeleted−62

This diff is too big to show here.

test/command/biblatex-hammond.mddeleted−63

This diff is too big to show here.

test/command/biblatex-herrmann.mddeleted−70

This diff is too big to show here.

test/command/biblatex-hyman.mddeleted−79

This diff is too big to show here.

test/command/biblatex-iliad.mddeleted−68

This diff is too big to show here.

test/command/biblatex-inbook-title-booktitle-maintitle-series-2.mddeleted−48

This diff is too big to show here.

test/command/biblatex-inbook-title-booktitle-maintitle-series.mddeleted−44

This diff is too big to show here.

test/command/biblatex-inbook.mddeleted−147

This diff is too big to show here.

test/command/biblatex-incollection-2.mddeleted−98

This diff is too big to show here.

test/command/biblatex-incollection.mddeleted−130

This diff is too big to show here.

test/command/biblatex-inproceedings.mddeleted−88

This diff is too big to show here.

test/command/biblatex-issue288.mddeleted−35

This diff is too big to show here.

test/command/biblatex-itzhaki.mddeleted−82

This diff is too big to show here.

test/command/biblatex-jaffe.mddeleted−82

This diff is too big to show here.

test/command/biblatex-jcg.mddeleted−54

This diff is too big to show here.

test/command/biblatex-kant-kpv.mddeleted−90

This diff is too big to show here.

test/command/biblatex-kant-ku.mddeleted−82

This diff is too big to show here.

test/command/biblatex-kastenholz.mddeleted−126

This diff is too big to show here.

test/command/biblatex-knuth-ct-a.mddeleted−78

This diff is too big to show here.

test/command/biblatex-knuth-ct-b.mddeleted−70

This diff is too big to show here.

test/command/biblatex-knuth-ct-c.mddeleted−69

This diff is too big to show here.

test/command/biblatex-knuth-ct-d.mddeleted−71

This diff is too big to show here.

test/command/biblatex-knuth-ct-e.mddeleted−66

This diff is too big to show here.

test/command/biblatex-knuth-ct-related.mddeleted−72

This diff is too big to show here.

test/command/biblatex-knuth-ct.mddeleted−66

This diff is too big to show here.

test/command/biblatex-kowalik.mddeleted−68

This diff is too big to show here.

test/command/biblatex-kullback-related.mddeleted−62

This diff is too big to show here.

test/command/biblatex-kullback-reprint.mddeleted−71

This diff is too big to show here.

test/command/biblatex-kullback.mddeleted−52

This diff is too big to show here.

test/command/biblatex-laufenberg.mddeleted−109

This diff is too big to show here.

test/command/biblatex-loh.mddeleted−65

This diff is too big to show here.

test/command/biblatex-malinowski.mddeleted−67

This diff is too big to show here.

test/command/biblatex-manual.mddeleted−51

This diff is too big to show here.

test/command/biblatex-markey.mddeleted−65

This diff is too big to show here.

test/command/biblatex-maron.mddeleted−70

This diff is too big to show here.

test/command/biblatex-massa.mddeleted−56

This diff is too big to show here.

test/command/biblatex-moore-related.mddeleted−66

This diff is too big to show here.

test/command/biblatex-moore.mddeleted−56

This diff is too big to show here.

test/command/biblatex-moraux.mddeleted−94

This diff is too big to show here.

test/command/biblatex-murray.mddeleted−105

This diff is too big to show here.

test/command/biblatex-nietzsche-historie.mddeleted−100

This diff is too big to show here.

test/command/biblatex-nietzsche-ksa.mddeleted−89

This diff is too big to show here.

test/command/biblatex-nietzsche-ksa1.mddeleted−95

This diff is too big to show here.

test/command/biblatex-online.mddeleted−64

This diff is too big to show here.

test/command/biblatex-options-url-false-doi-false.mddeleted−57

This diff is too big to show here.

test/command/biblatex-padhye.mddeleted−117

This diff is too big to show here.

test/command/biblatex-patent.mddeleted−158

This diff is too big to show here.

test/command/biblatex-periodical.mddeleted−31

This diff is too big to show here.

test/command/biblatex-piccato.mddeleted−59

This diff is too big to show here.

test/command/biblatex-pines.mddeleted−77

This diff is too big to show here.

test/command/biblatex-quotes.mddeleted−44

This diff is too big to show here.

test/command/biblatex-reese.mddeleted−71

This diff is too big to show here.

test/command/biblatex-report.mddeleted−119

This diff is too big to show here.

test/command/biblatex-salam.mddeleted−69

This diff is too big to show here.

test/command/biblatex-sarfraz.mddeleted−65

This diff is too big to show here.

test/command/biblatex-shore.mddeleted−66

This diff is too big to show here.

test/command/biblatex-sigfridsson.mddeleted−106

This diff is too big to show here.

test/command/biblatex-sorace.mddeleted−65

This diff is too big to show here.

test/command/biblatex-spiegelberg.mddeleted−74

This diff is too big to show here.

test/command/biblatex-springer.mddeleted−58

This diff is too big to show here.

test/command/biblatex-strings.mddeleted−46

This diff is too big to show here.

test/command/biblatex-test-case-conversion.mddeleted−73

This diff is too big to show here.

test/command/biblatex-textnormal.mddeleted−17

This diff is too big to show here.

test/command/biblatex-thesis.mddeleted−68

This diff is too big to show here.

test/command/biblatex-title-and-shorttitle.mddeleted−76

This diff is too big to show here.

test/command/biblatex-vangennep-related.mddeleted−69

This diff is too big to show here.

test/command/biblatex-vangennep-trans.mddeleted−69

This diff is too big to show here.

test/command/biblatex-vangennep.mddeleted−61

This diff is too big to show here.

test/command/biblatex-vazques-de-parga-mvbook.mddeleted−75

This diff is too big to show here.

test/command/biblatex-vazques-de-parga.mddeleted−74

This diff is too big to show here.

test/command/biblatex-video.mddeleted−19

This diff is too big to show here.

test/command/biblatex-vizedom-related.mddeleted−68

This diff is too big to show here.

test/command/biblatex-wassenberg.mddeleted−83

This diff is too big to show here.

test/command/biblatex-weinberg.mddeleted−52

This diff is too big to show here.

test/command/biblatex-westfahl-frontier.mddeleted−60

This diff is too big to show here.

test/command/biblatex-westfahl-space.mddeleted−106

This diff is too big to show here.

test/command/biblatex-wilde.mddeleted−65

This diff is too big to show here.

test/command/biblatex-worman.mddeleted−60

This diff is too big to show here.

test/command/biblatex-yoon.mddeleted−67

This diff is too big to show here.

test/command/biblio.bibdeleted−26

This diff is too big to show here.

test/command/bibtex-basic.mddeleted−71

This diff is too big to show here.

test/command/bioethics.csldeleted−226

This diff is too big to show here.

test/command/chap1/spider.pngdeleted

Binary file not shown.

test/command/chap1/text.mddeleted−17

This diff is too big to show here.

test/command/chap2/spider.pngdeleted

Binary file not shown.

test/command/chap2/text.mddeleted−5

This diff is too big to show here.

test/command/chicago-annotated-bibliography.csldeleted−1207

This diff is too big to show here.

test/command/chicago-author-date-with-original-date-and-status.csldeleted−575

This diff is too big to show here.

test/command/chicago-fullnote-bibliography.csldeleted−1430

This diff is too big to show here.

test/command/chicago-note-bibliography.csldeleted−1005

This diff is too big to show here.

test/command/chinese-gb7714-2005-numeric.csldeleted−213

This diff is too big to show here.

test/command/cite-in-inline-note.mddeleted−6

This diff is too big to show here.

test/command/citeproc-17.mddeleted−17

This diff is too big to show here.

test/command/citeproc-20.mddeleted−25

This diff is too big to show here.

test/command/citeproc-7a.mddeleted−42

This diff is too big to show here.

test/command/citeproc-7b.mddeleted−36

This diff is too big to show here.

test/command/citeproc-author-in-text-suffix.mddeleted−6

This diff is too big to show here.

test/command/corrupt.svgdeleted−5

This diff is too big to show here.

test/command/csv.mddeleted−46

This diff is too big to show here.

test/command/defaults-inheritance-1.mddeleted−6

This diff is too big to show here.

test/command/defaults-inheritance-2.mddeleted−5

This diff is too big to show here.

test/command/defaults-inheritance-3.mddeleted−6

This diff is too big to show here.

test/command/defaults1.yamldeleted−1

This diff is too big to show here.

test/command/defaults2.yamldeleted−4

This diff is too big to show here.

test/command/defaults3.yamldeleted−4

This diff is too big to show here.

test/command/defaults4.yamldeleted−3

This diff is too big to show here.

test/command/defaults5.yamldeleted−2

This diff is too big to show here.

test/command/defaults6.yamldeleted−2

This diff is too big to show here.

test/command/defaults7.yamldeleted−2

This diff is too big to show here.

test/command/defaults8.yamldeleted−2

This diff is too big to show here.

test/command/defaults9.yamldeleted−1

This diff is too big to show here.

test/command/din-1505-2.csldeleted−406

This diff is too big to show here.

test/command/docbook-bibliography.mddeleted−20

This diff is too big to show here.

test/command/dots.mddeleted−12

This diff is too big to show here.

test/command/duplicate_attributes.mddeleted−7

This diff is too big to show here.

test/command/emoji.mddeleted−27

This diff is too big to show here.

test/command/empty_paragraphs.mddeleted−93

This diff is too big to show here.

test/command/gfm.mddeleted−166

This diff is too big to show here.

test/command/harvard-university-of-kent.csldeleted−253

This diff is too big to show here.

test/command/hspace.mddeleted−56

This diff is too big to show here.

test/command/html-read-figure.mddeleted−45

This diff is too big to show here.

test/command/html-trim-definition-list-terms.mddeleted−17

This diff is too big to show here.

test/command/hyphenat.mddeleted−49

This diff is too big to show here.

test/command/ieee.csldeleted−339

This diff is too big to show here.

test/command/ifstrequal.mddeleted−9

This diff is too big to show here.

test/command/indented-fences.mddeleted−20

This diff is too big to show here.

test/command/inkscape-cube.svgdeleted−119

This diff is too big to show here.

test/command/issue160.csldeleted−28

This diff is too big to show here.

test/command/issue437.csldeleted−26

This diff is too big to show here.

test/command/issue58.csldeleted−553

This diff is too big to show here.

test/command/jats.csldeleted−208

This diff is too big to show here.

test/command/latex-center.mddeleted−13

This diff is too big to show here.

test/command/latex-color.mddeleted−127

This diff is too big to show here.

test/command/latex-command-comment.mddeleted−7

This diff is too big to show here.

test/command/latex-fontawesome.mddeleted−13

This diff is too big to show here.

test/command/latex-tabular-column-specs.mddeleted−45

This diff is too big to show here.

test/command/le-tapuscrit-note.csldeleted−496

This diff is too big to show here.

test/command/lettrine.mddeleted−9

This diff is too big to show here.

test/command/lists-inside-definition.mddeleted−67

This diff is too big to show here.

test/command/locators.csldeleted−68

This diff is too big to show here.

test/command/lstlisting.mddeleted−25

This diff is too big to show here.

test/command/lua-pandoc-state.luadeleted−11

This diff is too big to show here.

test/command/lua-pandoc-state.mddeleted−14

This diff is too big to show here.

test/command/macro-defs-in-preamble.mddeleted−16

This diff is too big to show here.

test/command/macros.mddeleted−125

This diff is too big to show here.

test/command/make-section-column-divs.mddeleted−28

This diff is too big to show here.

test/command/md-abbrevs.mddeleted−20

This diff is too big to show here.

test/command/mmd-metadata.mddeleted−20

This diff is too big to show here.

test/command/modern-humanities-research-association.csldeleted−445

This diff is too big to show here.

test/command/multiple-metadata-blocks.mddeleted−15

This diff is too big to show here.

test/command/nested-table-to-asciidoc-6942.mddeleted−82

This diff is too big to show here.

test/command/newif.mddeleted−55

This diff is too big to show here.

test/command/oscola.csldeleted−680

This diff is too big to show here.

test/command/pandoc-citeproc-118.mddeleted−28

This diff is too big to show here.

test/command/pandoc-citeproc-119.mddeleted−38

This diff is too big to show here.

test/command/pandoc-citeproc-13.mddeleted−29

This diff is too big to show here.

test/command/pandoc-citeproc-136.mddeleted−23

This diff is too big to show here.

test/command/pandoc-citeproc-14.mddeleted−77

This diff is too big to show here.

test/command/pandoc-citeproc-152.mddeleted−63

This diff is too big to show here.

test/command/pandoc-citeproc-160.mddeleted−44

This diff is too big to show here.

test/command/pandoc-citeproc-175.mddeleted−43

This diff is too big to show here.

test/command/pandoc-citeproc-197.mddeleted−31

This diff is too big to show here.

test/command/pandoc-citeproc-213.mddeleted−33

This diff is too big to show here.

test/command/pandoc-citeproc-25.mddeleted−30

This diff is too big to show here.

test/command/pandoc-citeproc-250.mddeleted−21

This diff is too big to show here.

test/command/pandoc-citeproc-27.mddeleted−38

This diff is too big to show here.

test/command/pandoc-citeproc-292.mddeleted−43

This diff is too big to show here.

test/command/pandoc-citeproc-301.mddeleted−25

This diff is too big to show here.

test/command/pandoc-citeproc-307.mddeleted−31

This diff is too big to show here.

test/command/pandoc-citeproc-31.mddeleted−48

This diff is too big to show here.

test/command/pandoc-citeproc-312.mddeleted−171

This diff is too big to show here.

test/command/pandoc-citeproc-320.mddeleted−254

This diff is too big to show here.

test/command/pandoc-citeproc-320a.mddeleted−87

This diff is too big to show here.

test/command/pandoc-citeproc-322.mddeleted−35

This diff is too big to show here.

test/command/pandoc-citeproc-325.mddeleted−30

This diff is too big to show here.

test/command/pandoc-citeproc-327.mddeleted−51

This diff is too big to show here.

test/command/pandoc-citeproc-338.mddeleted−35

This diff is too big to show here.

test/command/pandoc-citeproc-351.mddeleted−27

This diff is too big to show here.

test/command/pandoc-citeproc-356.mddeleted−20

This diff is too big to show here.

test/command/pandoc-citeproc-360.mddeleted−35

This diff is too big to show here.

test/command/pandoc-citeproc-361.mddeleted−80

This diff is too big to show here.

test/command/pandoc-citeproc-365.mddeleted−39

This diff is too big to show here.

test/command/pandoc-citeproc-371.mddeleted−40

This diff is too big to show here.

test/command/pandoc-citeproc-38.mddeleted−29

This diff is too big to show here.

test/command/pandoc-citeproc-386.mddeleted−35

This diff is too big to show here.

test/command/pandoc-citeproc-392.mddeleted−29

This diff is too big to show here.

test/command/pandoc-citeproc-399.mddeleted−45

This diff is too big to show here.

test/command/pandoc-citeproc-401.mddeleted−59

This diff is too big to show here.

test/command/pandoc-citeproc-408.mddeleted−39

This diff is too big to show here.

test/command/pandoc-citeproc-416.mddeleted−60

This diff is too big to show here.

test/command/pandoc-citeproc-437.mddeleted−23

This diff is too big to show here.

test/command/pandoc-citeproc-47.mddeleted−112

This diff is too big to show here.

test/command/pandoc-citeproc-51.mddeleted−45

This diff is too big to show here.

test/command/pandoc-citeproc-53.mddeleted−56

This diff is too big to show here.

test/command/pandoc-citeproc-57.mddeleted−37

This diff is too big to show here.

test/command/pandoc-citeproc-58.mddeleted−32

This diff is too big to show here.

test/command/pandoc-citeproc-61.mddeleted−77

This diff is too big to show here.

test/command/pandoc-citeproc-64.mddeleted−24

This diff is too big to show here.

test/command/pandoc-citeproc-65.mddeleted−38

This diff is too big to show here.

test/command/pandoc-citeproc-68.mddeleted−56

This diff is too big to show here.

test/command/pandoc-citeproc-7.mddeleted−31

This diff is too big to show here.

test/command/pandoc-citeproc-70.mddeleted−73

This diff is too big to show here.

test/command/pandoc-citeproc-75.mddeleted−67

This diff is too big to show here.

test/command/pandoc-citeproc-76.mddeleted−64

This diff is too big to show here.

test/command/pandoc-citeproc-77.mddeleted−67

This diff is too big to show here.

test/command/pandoc-citeproc-82.mddeleted−39

This diff is too big to show here.

test/command/pandoc-citeproc-87.mddeleted−156

This diff is too big to show here.

test/command/pandoc-citeproc-chicago-author-date.mddeleted−109

This diff is too big to show here.

test/command/pandoc-citeproc-chicago-fullnote-bibliography.mddeleted−134

This diff is too big to show here.

test/command/pandoc-citeproc-ieee.mddeleted−113

This diff is too big to show here.

test/command/pandoc-citeproc-locators-delimited.mddeleted−127

This diff is too big to show here.

test/command/pandoc-citeproc-locators-integrated.mddeleted−159

This diff is too big to show here.

test/command/pandoc-citeproc-move-period-inside-quote.mddeleted−52

This diff is too big to show here.

test/command/pandoc-citeproc-no-author.mddeleted−73

This diff is too big to show here.

test/command/pandoc-citeproc-number-of-volumes.mddeleted−29

This diff is too big to show here.

test/command/pandoc-citeproc-page-range.mddeleted−32

This diff is too big to show here.

test/command/parse-raw.mddeleted−27

This diff is too big to show here.

test/command/refs.mddeleted−97

This diff is too big to show here.

test/command/rst-links.mddeleted−18

This diff is too big to show here.

test/command/sage-harvard.csldeleted−202

This diff is too big to show here.

test/command/science.csldeleted−245

This diff is too big to show here.

test/command/section-divs.mddeleted−25

This diff is too big to show here.

test/command/setext-fenced-div.mddeleted−9

This diff is too big to show here.

test/command/shift-heading-level-by.mddeleted−32

This diff is too big to show here.

test/command/sloppypar.mddeleted−23

This diff is too big to show here.

test/command/smart.mddeleted−45

This diff is too big to show here.

test/command/style399.csldeleted−12

This diff is too big to show here.

test/command/sub-file-chapter-1.texdeleted−8

This diff is too big to show here.

test/command/sub-file-chapter-2.texdeleted−8

This diff is too big to show here.

test/command/svg.mddeleted−134

This diff is too big to show here.

test/command/table-with-cell-align.mddeleted−82

This diff is too big to show here.

test/command/table-with-column-span.mddeleted−276

This diff is too big to show here.

test/command/tabularx.mddeleted−185

This diff is too big to show here.

test/command/tasklist.mddeleted−113

This diff is too big to show here.

test/command/tex-group.mddeleted−12

This diff is too big to show here.

test/command/toc.mddeleted−47

This diff is too big to show here.

test/command/translations.mddeleted−29

This diff is too big to show here.

test/command/unicode-collation.mddeleted−130

This diff is too big to show here.

test/command/vancouver.csldeleted−351

This diff is too big to show here.

test/command/vars-and-metadata.md−15

This diff is too big to show here.

test/command/video-audio.md−19

This diff is too big to show here.

test/command/write18.md−14

This diff is too big to show here.

test/command/yaml-metadata-blocks.md−63

This diff is too big to show here.

test/command/yaml-metadata.yaml−4

This diff is too big to show here.

test/command/yaml-with-chomp.md−12

This diff is too big to show here.

test/command/zeitschrift-fur-kunstgeschichte.csl−346

This diff is too big to show here.

test/creole-reader.native−132

This diff is too big to show here.

test/creole-reader.txt−137

This diff is too big to show here.

test/docbook-chapter.docbook−30

This diff is too big to show here.

test/docbook-chapter.native−17

This diff is too big to show here.

test/docbook-reader.native−583

This diff is too big to show here.

test/docbook-xref.docbook−70

This diff is too big to show here.

test/docbook-xref.native−29

This diff is too big to show here.

test/docx/0_level_headers.docx

This diff is too big to show here.

test/docx/0_level_headers.native−52

This diff is too big to show here.

test/docx/adjacent_codeblocks.docx

This diff is too big to show here.

test/docx/adjacent_codeblocks.native−6

This diff is too big to show here.

test/docx/already_auto_ident.docx

This diff is too big to show here.

test/docx/already_auto_ident.native−2

This diff is too big to show here.

test/docx/alternate_document_path.docx

This diff is too big to show here.

test/docx/alternate_document_path.native−3

This diff is too big to show here.

test/docx/block_quotes.docx

This diff is too big to show here.

test/docx/block_quotes_parse_indent.native−8

This diff is too big to show here.

test/docx/char_styles.docx

This diff is too big to show here.

test/docx/char_styles.native−4

This diff is too big to show here.

test/docx/codeblock.docx

This diff is too big to show here.

test/docx/codeblock.native−3

This diff is too big to show here.

test/docx/comments.docx

This diff is too big to show here.

test/docx/comments.native−4

This diff is too big to show here.

test/docx/comments_no_comments.native−4

This diff is too big to show here.

test/docx/comments_warning.docx

This diff is too big to show here.

test/docx/compact-style-removal.docx

This diff is too big to show here.

test/docx/compact-style-removal.native−5

This diff is too big to show here.

test/docx/custom-style-no-styles.native−4

This diff is too big to show here.

test/docx/custom-style-preserve.native−15

This diff is too big to show here.

test/docx/custom-style-reference.docx

This diff is too big to show here.

test/docx/custom-style-roundtrip-end.native−5

This diff is too big to show here.

test/docx/custom-style-with-styles.native−7

This diff is too big to show here.

test/docx/custom_style.native−5

This diff is too big to show here.

test/docx/deep_normalize.docx

This diff is too big to show here.

test/docx/deep_normalize.native−6

This diff is too big to show here.

test/docx/definition_list.docx

This diff is too big to show here.

test/docx/definition_list.native−7

This diff is too big to show here.

test/docx/document-properties-short-desc.native−2

This diff is too big to show here.

test/docx/document-properties.native−2

This diff is too big to show here.

test/docx/drop_cap.docx

This diff is too big to show here.

test/docx/drop_cap.native−4

This diff is too big to show here.

test/docx/dummy_item_after_list_item.docx

This diff is too big to show here.

test/docx/dummy_item_after_list_item.native−3

This diff is too big to show here.

test/docx/dummy_item_after_paragraph.docx

This diff is too big to show here.

test/docx/dummy_item_after_paragraph.native−3

This diff is too big to show here.

test/docx/enumerated_headings.docx

This diff is too big to show here.

test/docx/enumerated_headings.native−4

This diff is too big to show here.

test/docx/german_styled_lists.docx

This diff is too big to show here.

test/docx/german_styled_lists.native−6

This diff is too big to show here.

test/docx/golden/block_quotes.docx

This diff is too big to show here.

test/docx/golden/codeblock.docx

This diff is too big to show here.

test/docx/golden/comments.docx

This diff is too big to show here.

test/docx/golden/custom_style_no_reference.docx

This diff is too big to show here.

test/docx/golden/custom_style_preserve.docx

This diff is too big to show here.

test/docx/golden/custom_style_reference.docx

This diff is too big to show here.

test/docx/golden/definition_list.docx

This diff is too big to show here.

test/docx/golden/document-properties-short-desc.docx

This diff is too big to show here.

test/docx/golden/document-properties.docx

This diff is too big to show here.

test/docx/golden/headers.docx

This diff is too big to show here.

test/docx/golden/image.docx

This diff is too big to show here.

test/docx/golden/inline_code.docx

This diff is too big to show here.

test/docx/golden/inline_formatting.docx

This diff is too big to show here.

test/docx/golden/inline_images.docx

This diff is too big to show here.

test/docx/golden/link_in_notes.docx

This diff is too big to show here.

test/docx/golden/links.docx

This diff is too big to show here.

test/docx/golden/lists.docx

This diff is too big to show here.

test/docx/golden/lists_continuing.docx

This diff is too big to show here.

test/docx/golden/lists_multiple_initial.docx

This diff is too big to show here.

test/docx/golden/lists_restarting.docx

This diff is too big to show here.

test/docx/golden/nested_anchors_in_header.docx

This diff is too big to show here.

test/docx/golden/notes.docx

This diff is too big to show here.

test/docx/golden/raw-blocks.docx

This diff is too big to show here.

test/docx/golden/raw-bookmarks.docx

This diff is too big to show here.

test/docx/golden/table_one_row.docx

This diff is too big to show here.

test/docx/golden/table_with_list_cell.docx

This diff is too big to show here.

test/docx/golden/tables-default-widths.docx

This diff is too big to show here.

test/docx/golden/tables.docx

This diff is too big to show here.

test/docx/golden/track_changes_deletion.docx

This diff is too big to show here.

test/docx/golden/track_changes_insertion.docx

This diff is too big to show here.

test/docx/golden/track_changes_move.docx

This diff is too big to show here.

test/docx/golden/track_changes_scrubbed_metadata.docx

This diff is too big to show here.

test/docx/golden/unicode.docx

This diff is too big to show here.

test/docx/golden/verbatim_subsuper.docx

This diff is too big to show here.

test/docx/hanging_indent.docx

This diff is too big to show here.

test/docx/hanging_indent.native−3

This diff is too big to show here.

test/docx/headers.docx

This diff is too big to show here.

test/docx/headers.native−13

This diff is too big to show here.

test/docx/i18n_blocks.docx

This diff is too big to show here.

test/docx/i18n_blocks.native−8

This diff is too big to show here.

test/docx/image.docx

This diff is too big to show here.

test/docx/image_no_embed.native−2

This diff is too big to show here.

test/docx/image_no_embed_writer.native−2

This diff is too big to show here.

test/docx/image_vml.docx

This diff is too big to show here.

test/docx/image_vml.native−4

This diff is too big to show here.

test/docx/image_vml_as_object.docx

This diff is too big to show here.

test/docx/image_vml_as_object.native−2

This diff is too big to show here.

test/docx/image_writer_test.native−8

This diff is too big to show here.

test/docx/inline_code.docx

This diff is too big to show here.

test/docx/inline_code.native−1

This diff is too big to show here.

test/docx/inline_formatting.docx

This diff is too big to show here.

test/docx/inline_formatting.native−6

This diff is too big to show here.

test/docx/inline_formatting_writer.native−5

This diff is too big to show here.

test/docx/inline_images.docx

This diff is too big to show here.

test/docx/inline_images.native−2

This diff is too big to show here.

test/docx/inline_images_writer.native−2

This diff is too big to show here.

test/docx/inline_images_writer_test.native−2

This diff is too big to show here.

test/docx/instrText_hyperlink.docx

This diff is too big to show here.

test/docx/instrText_hyperlink.native−1

This diff is too big to show here.

test/docx/link_in_notes.docx

This diff is too big to show here.

test/docx/link_in_notes.native−1

This diff is too big to show here.

test/docx/links.docx

This diff is too big to show here.

test/docx/links.native−7

This diff is too big to show here.

test/docx/links_writer.native−6

This diff is too big to show here.

test/docx/lists-compact.docx

This diff is too big to show here.

test/docx/lists-compact.native−5

This diff is too big to show here.

test/docx/lists.docx

This diff is too big to show here.

test/docx/lists.native−18

This diff is too big to show here.

test/docx/lists_continuing.docx

This diff is too big to show here.

test/docx/lists_continuing.native−7

This diff is too big to show here.

test/docx/lists_level_override.docx

This diff is too big to show here.

test/docx/lists_level_override.native−37

This diff is too big to show here.

test/docx/lists_multiple_initial.native−8

This diff is too big to show here.

test/docx/lists_restarting.docx

This diff is too big to show here.

test/docx/lists_restarting.native−8

This diff is too big to show here.

test/docx/lists_sublist_reset.docx

This diff is too big to show here.

test/docx/lists_sublist_reset.native−8

This diff is too big to show here.

test/docx/lists_writer.native−17

This diff is too big to show here.

test/docx/metadata.docx

This diff is too big to show here.

test/docx/metadata.native−2

This diff is too big to show here.

test/docx/metadata_after_normal.docx

This diff is too big to show here.

test/docx/metadata_after_normal.native−7

This diff is too big to show here.

test/docx/nested_anchors_in_header.docx

This diff is too big to show here.

test/docx/nested_anchors_in_header.native−15

This diff is too big to show here.

test/docx/nested_sdt.docx

This diff is too big to show here.

test/docx/nested_sdt.native−3

This diff is too big to show here.

test/docx/nested_smart_tags.docx

This diff is too big to show here.

test/docx/nested_smart_tags.native−7

This diff is too big to show here.

test/docx/normalize.docx

This diff is too big to show here.

test/docx/normalize.native−2

This diff is too big to show here.

test/docx/notes.docx

This diff is too big to show here.

test/docx/notes.native−2

This diff is too big to show here.

test/docx/numbered_header.docx

This diff is too big to show here.

test/docx/numbered_header.native−1

This diff is too big to show here.

test/docx/overlapping_targets.docx

This diff is too big to show here.

test/docx/overlapping_targets.native−3

This diff is too big to show here.

test/docx/paragraph_insertion_deletion.docx

This diff is too big to show here.

test/docx/paragraph_insertion_deletion_accept.native−2

This diff is too big to show here.

test/docx/paragraph_insertion_deletion_all.native−3

This diff is too big to show here.

test/docx/paragraph_insertion_deletion_reject.native−2

This diff is too big to show here.

test/docx/raw-blocks.native−6

This diff is too big to show here.

test/docx/raw-bookmarks.native−3

This diff is too big to show here.

test/docx/sdt_elements.docx

This diff is too big to show here.

test/docx/sdt_elements.native−24

This diff is too big to show here.

test/docx/sdt_in_footnote.docx

This diff is too big to show here.

test/docx/sdt_in_footnote.native−1

This diff is too big to show here.

test/docx/special_punctuation.docx

This diff is too big to show here.

test/docx/special_punctuation.native−2

This diff is too big to show here.

test/docx/table_captions_no_field.docx

This diff is too big to show here.

test/docx/table_captions_no_field.native−34

This diff is too big to show here.

test/docx/table_captions_with_field.docx

This diff is too big to show here.

test/docx/table_captions_with_field.native−54

This diff is too big to show here.

test/docx/table_header_rowspan.docx

This diff is too big to show here.

test/docx/table_header_rowspan.native−189

This diff is too big to show here.

test/docx/table_one_header_row.docx

This diff is too big to show here.

test/docx/table_one_header_row.native−18

This diff is too big to show here.

test/docx/table_one_row.docx

This diff is too big to show here.

test/docx/table_one_row.native−18

This diff is too big to show here.

test/docx/table_variable_width.docx

This diff is too big to show here.

test/docx/table_variable_width.native−40

This diff is too big to show here.

test/docx/table_with_list_cell.docx

This diff is too big to show here.

test/docx/table_with_list_cell.native−25

This diff is too big to show here.

test/docx/tables-default-widths.native−92

This diff is too big to show here.

test/docx/tables.docx

This diff is too big to show here.

test/docx/tables.native−92

This diff is too big to show here.

test/docx/tabs.docx

This diff is too big to show here.

test/docx/tabs.native−2

This diff is too big to show here.

test/docx/track_changes_deletion.docx

This diff is too big to show here.

test/docx/track_changes_deletion_accept.native−1

This diff is too big to show here.

test/docx/track_changes_deletion_all.native−1

This diff is too big to show here.

test/docx/track_changes_deletion_reject.native−1

This diff is too big to show here.

test/docx/track_changes_insertion.docx

This diff is too big to show here.

test/docx/track_changes_insertion_accept.native−1

This diff is too big to show here.

test/docx/track_changes_insertion_all.native−1

This diff is too big to show here.

test/docx/track_changes_insertion_reject.native−1

This diff is too big to show here.

test/docx/track_changes_move.docx

This diff is too big to show here.

test/docx/track_changes_move_accept.native−3

This diff is too big to show here.

test/docx/track_changes_move_all.native−4

This diff is too big to show here.

test/docx/track_changes_move_reject.native−3

This diff is too big to show here.

test/docx/track_changes_scrubbed_metadata.docx

This diff is too big to show here.

test/docx/track_changes_scrubbed_metadata.native−9

This diff is too big to show here.

test/docx/trailing_spaces_in_formatting.docx

This diff is too big to show here.

test/docx/trailing_spaces_in_formatting.native−1

This diff is too big to show here.

test/docx/trim_last_inline.docx

This diff is too big to show here.

test/docx/trim_last_inline.native−2

This diff is too big to show here.

test/docx/unicode.docx

This diff is too big to show here.

test/docx/unicode.native−1

This diff is too big to show here.

test/docx/unused_anchors.docx

This diff is too big to show here.

test/docx/unused_anchors.native−3

This diff is too big to show here.

test/docx/verbatim_subsuper.docx

This diff is too big to show here.

test/docx/verbatim_subsuper.native−8

This diff is too big to show here.

test/dokuwiki_external_images.dokuwiki−1

This diff is too big to show here.

test/dokuwiki_external_images.native−1

This diff is too big to show here.

test/dokuwiki_inline_formatting.dokuwiki−14

This diff is too big to show here.

test/dokuwiki_inline_formatting.native−7

This diff is too big to show here.

test/dokuwiki_multiblock_table.dokuwiki−5

This diff is too big to show here.

test/dokuwiki_multiblock_table.native−41

This diff is too big to show here.

test/epub/epub2_cover.epub

This diff is too big to show here.

test/epub/epub2_no_cover.epub

This diff is too big to show here.

test/epub/epub2_picture.epub

This diff is too big to show here.

test/epub/features.epub

This diff is too big to show here.

test/epub/features.native−93

This diff is too big to show here.

test/epub/formatting.epub

This diff is too big to show here.

test/epub/formatting.native−402

This diff is too big to show here.

test/epub/img.epub

This diff is too big to show here.

test/epub/img_no_cover.epub

This diff is too big to show here.

test/epub/wasteland.epub

This diff is too big to show here.

test/epub/wasteland.native−938

This diff is too big to show here.

test/fb2/basic.fb2−73

This diff is too big to show here.

test/fb2/images-embedded.fb2−2

This diff is too big to show here.

test/fb2/images.fb2−2

This diff is too big to show here.

test/fb2/math.fb2−2

This diff is too big to show here.

test/fb2/meta.fb2−3

This diff is too big to show here.

test/fb2/meta.markdown−7

This diff is too big to show here.

test/fb2/reader/emphasis.fb2−11

This diff is too big to show here.

test/fb2/reader/emphasis.native−6

This diff is too big to show here.

test/fb2/reader/epigraph.fb2−18

This diff is too big to show here.

test/fb2/reader/epigraph.native−9

This diff is too big to show here.

test/fb2/reader/meta.fb2−26

This diff is too big to show here.

test/fb2/reader/meta.native−2

This diff is too big to show here.

test/fb2/reader/notes.fb2−19

This diff is too big to show here.

test/fb2/reader/notes.native−4

This diff is too big to show here.

test/fb2/reader/poem.fb2−28

This diff is too big to show here.

test/fb2/reader/poem.native−14

This diff is too big to show here.

test/fb2/reader/titles.fb2−18

This diff is too big to show here.

test/fb2/reader/titles.native−8

This diff is too big to show here.

test/fb2/test.jpg

This diff is too big to show here.

test/fb2/titles.fb2−3

This diff is too big to show here.

test/fb2/titles.markdown−6

This diff is too big to show here.

test/haddock-reader.native−31

This diff is too big to show here.

test/html-reader.native−837

This diff is too big to show here.

test/ipynb/simple.in.native−15

This diff is too big to show here.

test/ipynb/simple.ipynb−86

This diff is too big to show here.

test/ipynb/simple.out.native−15

This diff is too big to show here.

test/jats-reader.native−671

This diff is too big to show here.

test/jats-reader.xml−1161

This diff is too big to show here.

test/jira-reader.jira−284

This diff is too big to show here.

test/jira-reader.native−185

This diff is too big to show here.

test/lhs-test-markdown.native−8

This diff is too big to show here.

test/lhs-test.html−231

This diff is too big to show here.

test/lhs-test.html+lhs−231

This diff is too big to show here.

test/lhs-test.latex−121

This diff is too big to show here.

test/lhs-test.latex+lhs−86

This diff is too big to show here.

test/lhs-test.native−8

This diff is too big to show here.

test/lua/attr-test.lua−6

This diff is too big to show here.

test/lua/block-count.lua−11

This diff is too big to show here.

test/lua/blocks-filter.lua−8

This diff is too big to show here.

test/lua/hello-world-doc.lua−10

This diff is too big to show here.

test/lua/implicit-doc-filter.lua−6

This diff is too big to show here.

test/lua/inlines-filter.lua−19

This diff is too big to show here.

test/lua/markdown-reader.lua−12

This diff is too big to show here.

test/lua/math.lua−10

This diff is too big to show here.

test/lua/meta.lua−6

This diff is too big to show here.

test/lua/metatable-catch-all.lua−20

This diff is too big to show here.

test/lua/module/pandoc-list.lua−160

This diff is too big to show here.

test/lua/module/pandoc-mediabag.lua−72

This diff is too big to show here.

test/lua/module/pandoc-path.lua−44

This diff is too big to show here.

test/lua/module/pandoc-types.lua−111

This diff is too big to show here.

test/lua/module/pandoc-utils.lua−159

This diff is too big to show here.

test/lua/module/pandoc.lua−253

This diff is too big to show here.

test/lua/plain-to-para.lua−6

This diff is too big to show here.

test/lua/require-file.lua−2

This diff is too big to show here.

test/lua/script-name.lua−3

This diff is too big to show here.

test/lua/single-to-double-quoted.lua−10

This diff is too big to show here.

test/lua/smallcaps-title.lua−12

This diff is too big to show here.

test/lua/smart-constructors.lua−10

This diff is too big to show here.

test/lua/strmacro.lua−11

This diff is too big to show here.

test/lua/undiv.lua−3

This diff is too big to show here.

test/lua/uppercase-header.lua−9

This diff is too big to show here.

test/man-reader.man−391

This diff is too big to show here.

test/man-reader.native−300

This diff is too big to show here.

test/markdown-citations.native−17

This diff is too big to show here.

test/markdown-reader-more.native−311

This diff is too big to show here.

test/media/rId25.jpg

This diff is too big to show here.

test/media/rId26.jpg

This diff is too big to show here.

test/media/rId27.jpg

This diff is too big to show here.

test/mediawiki-reader.native−418

This diff is too big to show here.

test/odt/markdown/bold.md−1

This diff is too big to show here.

test/odt/markdown/citation.md−1

This diff is too big to show here.

test/odt/markdown/endnote.md−3

This diff is too big to show here.

test/odt/markdown/externalLink.md−1

This diff is too big to show here.

test/odt/markdown/footnote.md−3

This diff is too big to show here.

test/odt/markdown/formula.md−1

This diff is too big to show here.

test/odt/markdown/headers.md−9

This diff is too big to show here.

test/odt/markdown/horizontalRule.md−1

This diff is too big to show here.

test/odt/markdown/image.md−1

This diff is too big to show here.

test/odt/markdown/imageIndex.md−6

This diff is too big to show here.

test/odt/markdown/imageWithCaption.md−1

This diff is too big to show here.

test/odt/markdown/italic.md−1

This diff is too big to show here.

test/odt/markdown/listBlocks.md−6

This diff is too big to show here.

test/odt/markdown/paragraph.md−5

This diff is too big to show here.

test/odt/markdown/strikeout.md−1

This diff is too big to show here.

test/odt/markdown/trackedChanges.md−1

This diff is too big to show here.

test/odt/markdown/underlined.md−1

This diff is too big to show here.

test/odt/native/blockquote.native−1

This diff is too big to show here.

test/odt/native/image.native−1

This diff is too big to show here.

test/odt/native/imageIndex.native−1

This diff is too big to show here.

test/odt/native/imageWithCaption.native−1

This diff is too big to show here.

test/odt/native/inlinedCode.native−1

This diff is too big to show here.

test/odt/native/orderedListMixed.native−1

This diff is too big to show here.

test/odt/native/orderedListRoman.native−1

This diff is too big to show here.

test/odt/native/orderedListSimple.native−1

This diff is too big to show here.

test/odt/native/referenceToChapter.native−1

This diff is too big to show here.

test/odt/native/referenceToListItem.native−1

This diff is too big to show here.

test/odt/native/referenceToText.native−1

This diff is too big to show here.

test/odt/native/simpleTable.native−1

This diff is too big to show here.

test/odt/native/simpleTableWithCaption.native−1

This diff is too big to show here.

test/odt/native/tab.native−1

This diff is too big to show here.

test/odt/native/tableWithContents.native−1

This diff is too big to show here.

test/odt/native/textMixedStyles.native−5

This diff is too big to show here.

test/odt/native/unicode.native−1

This diff is too big to show here.

test/odt/native/unorderedList.native−1

This diff is too big to show here.

test/odt/odt/blockquote.odt

This diff is too big to show here.

test/odt/odt/bold.odt

This diff is too big to show here.

test/odt/odt/citation.odt

This diff is too big to show here.

test/odt/odt/endnote.odt

This diff is too big to show here.

test/odt/odt/expression.odt

This diff is too big to show here.

test/odt/odt/expressionUnevaluated.odt

This diff is too big to show here.

test/odt/odt/externalLink.odt

This diff is too big to show here.

test/odt/odt/footnote.odt

This diff is too big to show here.

test/odt/odt/formula.odt

This diff is too big to show here.

test/odt/odt/headers.odt

This diff is too big to show here.

test/odt/odt/hiddenTextByStyle.odt

This diff is too big to show here.

test/odt/odt/hiddenTextByVariable.odt

This diff is too big to show here.

test/odt/odt/horizontalRule.odt

This diff is too big to show here.

test/odt/odt/image.odt

This diff is too big to show here.

test/odt/odt/imageIndex.odt

This diff is too big to show here.

test/odt/odt/imageWithCaption.odt

This diff is too big to show here.

test/odt/odt/inlinedCode.odt

This diff is too big to show here.

test/odt/odt/italic.odt

This diff is too big to show here.

test/odt/odt/listBlocks.odt

This diff is too big to show here.

test/odt/odt/orderedListMixed.odt

This diff is too big to show here.

test/odt/odt/orderedListRoman.odt

This diff is too big to show here.

test/odt/odt/orderedListSimple.odt

This diff is too big to show here.

test/odt/odt/paragraph.odt

This diff is too big to show here.

test/odt/odt/referenceAllInOne.odt

This diff is too big to show here.

test/odt/odt/referenceToChapter.odt

This diff is too big to show here.

test/odt/odt/referenceToListItem.odt

This diff is too big to show here.

test/odt/odt/referenceToText.odt

This diff is too big to show here.

test/odt/odt/simpleTable.odt

This diff is too big to show here.

test/odt/odt/simpleTableWithCaption.odt

This diff is too big to show here.

test/odt/odt/strikeout.odt

This diff is too big to show here.

test/odt/odt/tab.odt

This diff is too big to show here.

test/odt/odt/table.odt

This diff is too big to show here.

test/odt/odt/tableWithCaption.odt

This diff is too big to show here.

test/odt/odt/tableWithContents.odt

This diff is too big to show here.

test/odt/odt/textMixedStyles.odt

This diff is too big to show here.

test/odt/odt/trackedChanges.odt

This diff is too big to show here.

test/odt/odt/underlined.odt

This diff is too big to show here.

test/odt/odt/unicode.odt

This diff is too big to show here.

test/odt/odt/unorderedList.odt

This diff is too big to show here.

test/odt/odt/variable.odt

This diff is too big to show here.

test/org-select-tags.native−7

This diff is too big to show here.

test/org-select-tags.org−17

This diff is too big to show here.

test/pipe-tables.native−326

This diff is too big to show here.

test/pipe-tables.txt−82

This diff is too big to show here.

test/pptx/code-custom.pptx

This diff is too big to show here.

test/pptx/code-custom_templated.pptx

This diff is too big to show here.

test/pptx/code.native−21

This diff is too big to show here.

test/pptx/code.pptx

This diff is too big to show here.

test/pptx/code_templated.pptx

This diff is too big to show here.

test/pptx/document-properties-short-desc.native−2

This diff is too big to show here.

test/pptx/document-properties-short-desc.pptx

This diff is too big to show here.

test/pptx/document-properties-short-desc_templated.pptx

This diff is too big to show here.

test/pptx/document-properties.native−2

This diff is too big to show here.

test/pptx/document-properties.pptx

This diff is too big to show here.

test/pptx/document-properties_templated.pptx

This diff is too big to show here.

test/pptx/endnotes.native−2

This diff is too big to show here.

test/pptx/endnotes.pptx

This diff is too big to show here.

test/pptx/endnotes_templated.pptx

This diff is too big to show here.

test/pptx/endnotes_toc.pptx

This diff is too big to show here.

test/pptx/endnotes_toc_templated.pptx

This diff is too big to show here.

test/pptx/images.native−5

This diff is too big to show here.

test/pptx/images.pptx

This diff is too big to show here.

test/pptx/images_templated.pptx

This diff is too big to show here.

test/pptx/inline_formatting.native−5

This diff is too big to show here.

test/pptx/inline_formatting.pptx

This diff is too big to show here.

test/pptx/inline_formatting_templated.pptx

This diff is too big to show here.

test/pptx/lists.native−18

This diff is too big to show here.

test/pptx/lists.pptx

This diff is too big to show here.

test/pptx/lists_templated.pptx

This diff is too big to show here.

test/pptx/raw_ooxml.native−3

This diff is too big to show here.

test/pptx/raw_ooxml.pptx

This diff is too big to show here.

test/pptx/raw_ooxml_templated.pptx

This diff is too big to show here.

test/pptx/reference_depth.pptx

This diff is too big to show here.

test/pptx/remove_empty_slides.native−5

This diff is too big to show here.

test/pptx/remove_empty_slides.pptx

This diff is too big to show here.

test/pptx/remove_empty_slides_templated.pptx

This diff is too big to show here.

test/pptx/slide_breaks.native−7

This diff is too big to show here.

test/pptx/slide_breaks.pptx

This diff is too big to show here.

test/pptx/slide_breaks_slide_level_1.pptx

This diff is too big to show here.

test/pptx/slide_breaks_slide_level_1_templated.pptx

This diff is too big to show here.

test/pptx/slide_breaks_templated.pptx

This diff is too big to show here.

test/pptx/slide_breaks_toc.pptx

This diff is too big to show here.

test/pptx/slide_breaks_toc_templated.pptx

This diff is too big to show here.

test/pptx/speaker_notes.native−17

This diff is too big to show here.

test/pptx/speaker_notes.pptx

This diff is too big to show here.

test/pptx/speaker_notes_after_metadata.native−5

This diff is too big to show here.

test/pptx/speaker_notes_after_metadata.pptx

This diff is too big to show here.

test/pptx/speaker_notes_after_metadata_templated.pptx

This diff is too big to show here.

test/pptx/speaker_notes_afterheader.native−3

This diff is too big to show here.

test/pptx/speaker_notes_afterheader.pptx

This diff is too big to show here.

test/pptx/speaker_notes_afterheader_templated.pptx

This diff is too big to show here.

test/pptx/speaker_notes_afterseps.native−63

This diff is too big to show here.

test/pptx/speaker_notes_afterseps.pptx

This diff is too big to show here.

test/pptx/speaker_notes_afterseps_templated.pptx

This diff is too big to show here.

test/pptx/speaker_notes_templated.pptx

This diff is too big to show here.

test/pptx/start_numbering_at.native−9

This diff is too big to show here.

test/pptx/start_numbering_at.pptx

This diff is too big to show here.

test/pptx/start_numbering_at_templated.pptx

This diff is too big to show here.

test/pptx/tables.native−95

This diff is too big to show here.

test/pptx/tables.pptx

This diff is too big to show here.

test/pptx/tables_templated.pptx

This diff is too big to show here.

test/pptx/two_column.native−9

This diff is too big to show here.

test/pptx/two_column.pptx

This diff is too big to show here.

test/pptx/two_column_templated.pptx

This diff is too big to show here.

test/s5-fancy.html−64

This diff is too big to show here.

test/tables-rstsubset.native−301

This diff is too big to show here.

test/tables.asciidoc−67

This diff is too big to show here.

test/tables.asciidoctor−67

This diff is too big to show here.

test/tables.context−230

This diff is too big to show here.

test/tables.custom−200

This diff is too big to show here.

test/tables.docbook4−432

This diff is too big to show here.

test/tables.dokuwiki−46

This diff is too big to show here.

test/tables.fb2−15

This diff is too big to show here.

test/tables.haddock−90

This diff is too big to show here.

test/tables.html5−204

This diff is too big to show here.

test/tables.icml−757

This diff is too big to show here.

test/tables.jats_archiving−226

This diff is too big to show here.

test/tables.jats_articleauthoring−226

This diff is too big to show here.

test/tables.jats_publishing−226

This diff is too big to show here.

test/tables.jira−43

This diff is too big to show here.

test/tables.latex−134

This diff is too big to show here.

test/tables.mediawiki−145

This diff is too big to show here.

test/tables.ms−311

This diff is too big to show here.

test/tables.muse−59

This diff is too big to show here.

test/tables.native−293

This diff is too big to show here.

test/tables.org−51

This diff is too big to show here.

test/tables.rst−82

This diff is too big to show here.

test/tables.rtf−359

This diff is too big to show here.

test/tables.tei−159

This diff is too big to show here.

test/tables.xwiki−45

This diff is too big to show here.

test/tables.zimwiki−55

This diff is too big to show here.

test/tables/nordics.html4−59

This diff is too big to show here.

test/tables/nordics.html5−59

This diff is too big to show here.

test/tables/nordics.jats_archiving−58

This diff is too big to show here.

test/tables/nordics.latex−42

This diff is too big to show here.

test/tables/nordics.native−73

This diff is too big to show here.

test/tables/planets.html4−133

This diff is too big to show here.

test/tables/planets.html5−133

This diff is too big to show here.

test/tables/planets.jats_archiving−128

This diff is too big to show here.

test/tables/planets.latex−30

This diff is too big to show here.

test/tables/planets.native−241

This diff is too big to show here.

test/tables/students.html4−55

This diff is too big to show here.

test/tables/students.html5−55

This diff is too big to show here.

test/tables/students.jats_archiving−56

This diff is too big to show here.

test/tables/students.latex−31

This diff is too big to show here.

test/tables/students.native−54

This diff is too big to show here.

test/test-pandoc.hs−118

This diff is too big to show here.

test/textile-reader.native−243

This diff is too big to show here.

test/tikiwiki-reader.native−212

This diff is too big to show here.

test/tikiwiki-reader.tikiwiki−148

This diff is too big to show here.

test/twiki-reader.native−250

This diff is too big to show here.

test/twiki-reader.twiki−221

This diff is too big to show here.

test/txt2tags.native−968

This diff is too big to show here.

test/txt2tags.t2t−797

This diff is too big to show here.

test/vimwiki-reader.native−449

This diff is too big to show here.

test/vimwiki-reader.wiki−435

This diff is too big to show here.

test/writer.asciidoctor−649

This diff is too big to show here.

test/writer.custom−782

This diff is too big to show here.

test/writer.docbook4−1422

This diff is too big to show here.

test/writer.docbook5−1398

This diff is too big to show here.

test/writer.dokuwiki−649

This diff is too big to show here.

test/writer.fb2−758

This diff is too big to show here.

test/writer.haddock−657

This diff is too big to show here.

test/writer.html5−684

This diff is too big to show here.

test/writer.icml−3206

This diff is too big to show here.

test/writer.jats_archiving−902

This diff is too big to show here.

test/writer.jats_articleauthoring−874

This diff is too big to show here.

test/writer.jats_publishing−902

This diff is too big to show here.

test/writer.jira−537

This diff is too big to show here.

test/writer.ms−1011

This diff is too big to show here.

test/writer.muse−722

This diff is too big to show here.

test/writer.opendocument−1924

This diff is too big to show here.

test/writer.opml−72

This diff is too big to show here.

test/writer.rtf−443

This diff is too big to show here.

test/writer.tei−859

This diff is too big to show here.

test/writer.xwiki−650

This diff is too big to show here.

test/writer.zimwiki−619

This diff is too big to show here.

test/writers-lang-and-dir.context−126

This diff is too big to show here.

test/writers-lang-and-dir.latex−158

This diff is too big to show here.

test/writers-lang-and-dir.native−23

This diff is too big to show here.

tests/MarkdownTest_1.0.3/MarkdownTest.pl+176

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Amps and angle encoding.html+17

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Amps and angle encoding.text+21

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Auto links.html+18

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Auto links.text+13

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Backslash escapes.html+118

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Backslash escapes.text+120

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Blockquotes with code blocks.html+15

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Blockquotes with code blocks.text+11

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Code Blocks.html+18

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Code Blocks.text+14

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Code Spans.html+6

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Code Spans.text+6

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Hard-wrapped paragraphs with list-like lines.html+8

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Hard-wrapped paragraphs with list-like lines.text+8

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Horizontal rules.html+71

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Horizontal rules.text+67

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Inline HTML (Advanced).html+15

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Inline HTML (Advanced).text+15

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Inline HTML (Simple).html+72

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Inline HTML (Simple).text+69

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Inline HTML comments.html+13

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Inline HTML comments.text+13

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Links, inline style.html+11

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Links, inline style.text+12

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Links, reference style.html+52

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Links, reference style.text+71

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Links, shortcut references.html+9

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Links, shortcut references.text+20

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Literal quotes in titles.html+3

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Literal quotes in titles.text+7

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Markdown Documentation - Basics.html+314

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Markdown Documentation - Basics.text+306

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Markdown Documentation - Syntax.html+942

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Markdown Documentation - Syntax.text+888

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Nested blockquotes.html+9

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Nested blockquotes.text+5

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Ordered and unordered lists.html+148

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Ordered and unordered lists.text+131

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Strong and em together.html+7

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Strong and em together.text+7

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Tabs.html+25

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Tabs.text+21

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Tidyness.html+8

This diff is too big to show here.

tests/MarkdownTest_1.0.3/Tests/Tidyness.text+5

This diff is too big to show here.

tests/Tests/Arbitrary.hs+193

This diff is too big to show here.

tests/Tests/Helpers.hs+85

This diff is too big to show here.

tests/Tests/Old.hs+235

This diff is too big to show here.

tests/Tests/Readers/LaTeX.hs+177

This diff is too big to show here.

tests/Tests/Readers/Markdown.hs+214

This diff is too big to show here.

tests/Tests/Readers/RST.hs+71

This diff is too big to show here.

tests/Tests/Shared.hs+26

This diff is too big to show here.

tests/Tests/Walk.hs+47

This diff is too big to show here.

tests/Tests/Writers/ConTeXt.hs+70

This diff is too big to show here.

tests/Tests/Writers/HTML.hs+43

This diff is too big to show here.

tests/Tests/Writers/LaTeX.hs+52

This diff is too big to show here.

tests/Tests/Writers/Markdown.hs+34

This diff is too big to show here.

tests/Tests/Writers/Native.hs+21

This diff is too big to show here.

tests/bodybg.gif

This diff is too big to show here.

tests/docbook-reader.docbook+12−142

This diff is too big to show here.

tests/docbook-reader.native+386

This diff is too big to show here.

tests/fb2.basic.fb2+2

This diff is too big to show here.

tests/fb2.basic.markdown

This diff is too big to show here.

tests/fb2.images-embedded.fb2+2

This diff is too big to show here.

tests/fb2.images-embedded.html

This diff is too big to show here.

tests/fb2.images.fb2+2

This diff is too big to show here.

tests/fb2.images.markdown+2−2

This diff is too big to show here.

tests/fb2.math.fb2+2

This diff is too big to show here.

tests/fb2.math.markdown

This diff is too big to show here.

tests/fb2.test-small.png

This diff is too big to show here.

tests/fb2.test.jpg

This diff is too big to show here.

tests/fb2.titles.fb2+2

This diff is too big to show here.

tests/fb2.titles.markdown+10

This diff is too big to show here.

tests/haddock-reader.haddock+10−10

This diff is too big to show here.

tests/haddock-reader.native+31

This diff is too big to show here.

tests/html-reader.html+2−362

This diff is too big to show here.

tests/html-reader.native+306

This diff is too big to show here.

tests/insert

This diff is too big to show here.

tests/lalune.jpg

This diff is too big to show here.

tests/latex-reader.latex+10−4

This diff is too big to show here.

tests/latex-reader.native+77−118

This diff is too big to show here.

tests/lhs-test-markdown.native+8

This diff is too big to show here.

tests/lhs-test.fragment.html+lhs

This diff is too big to show here.

tests/lhs-test.html+42

This diff is too big to show here.

tests/lhs-test.html+lhs+42

This diff is too big to show here.

tests/lhs-test.latex+98

This diff is too big to show here.

tests/lhs-test.latex+lhs+77

This diff is too big to show here.

tests/lhs-test.markdown+4−4

This diff is too big to show here.

tests/lhs-test.markdown+lhs+2−2

This diff is too big to show here.

tests/lhs-test.native+8

This diff is too big to show here.

tests/lhs-test.rst+5−5

This diff is too big to show here.

tests/lhs-test.rst+lhs+2−2

This diff is too big to show here.

tests/markdown-citations.native+17

This diff is too big to show here.

tests/markdown-citations.txt

This diff is too big to show here.

tests/markdown-reader-more.native+139

This diff is too big to show here.

tests/markdown-reader-more.txt+1−84

This diff is too big to show here.

tests/mediawiki-reader.native+249

This diff is too big to show here.

tests/mediawiki-reader.wiki+4−23

This diff is too big to show here.

tests/movie.jpg

This diff is too big to show here.

tests/opml-reader.native+2−2

This diff is too big to show here.

tests/opml-reader.opml

This diff is too big to show here.

tests/pipe-tables.native+70

This diff is too big to show here.

tests/pipe-tables.txt+42

This diff is too big to show here.

tests/rst-reader.native+94−214

This diff is too big to show here.

tests/rst-reader.rst+1−53

This diff is too big to show here.

tests/s5.basic.html+6−16

This diff is too big to show here.

tests/s5.fancy.html+255

This diff is too big to show here.

tests/s5.fragment.html+1−1

This diff is too big to show here.

tests/s5.inserts.html+2−10

This diff is too big to show here.

tests/s5.native

This diff is too big to show here.

tests/tables-rstsubset.native+117

This diff is too big to show here.

tests/tables.asciidoc+71

This diff is too big to show here.

tests/tables.context+175

This diff is too big to show here.

tests/tables.docbook+7−7

This diff is too big to show here.

tests/tables.fb2+2

This diff is too big to show here.

tests/tables.html+23−29

This diff is too big to show here.

tests/tables.latex+169

This diff is too big to show here.

tests/tables.man+7−7

This diff is too big to show here.

tests/tables.markdown+2

This diff is too big to show here.

tests/tables.mediawiki+146

This diff is too big to show here.

tests/tables.native+114

This diff is too big to show here.

tests/tables.opendocument+101−101

This diff is too big to show here.

tests/tables.org+52

This diff is too big to show here.

tests/tables.plain+6−4

This diff is too big to show here.

tests/tables.rst+91

This diff is too big to show here.

tests/tables.rtf+359

This diff is too big to show here.

tests/tables.texinfo+3−3

This diff is too big to show here.

tests/tables.textile+56−10

This diff is too big to show here.

tests/tables.txt+1

This diff is too big to show here.

tests/test-pandoc.hs+41

This diff is too big to show here.

tests/testsuite.native+63−86

This diff is too big to show here.

tests/testsuite.txt+8−15

This diff is too big to show here.

tests/textile-reader.native+167

This diff is too big to show here.

tests/textile-reader.textile+21−37

This diff is too big to show here.

tests/writer.asciidoc+177−138

This diff is too big to show here.

tests/writer.context+130−158

This diff is too big to show here.

tests/writer.docbook+1432

This diff is too big to show here.

tests/writer.fb2+2

This diff is too big to show here.

tests/writer.html+58−171

This diff is too big to show here.

tests/writer.latex+148−180

This diff is too big to show here.

tests/writer.man+165−127

This diff is too big to show here.

tests/writer.markdown+128−143

This diff is too big to show here.

tests/writer.mediawiki+41−21

This diff is too big to show here.

tests/writer.native+63−86

This diff is too big to show here.

tests/writer.opendocument+1619

This diff is too big to show here.

tests/writer.opml+72

This diff is too big to show here.

tests/writer.org+284−310

This diff is too big to show here.

tests/writer.plain+71−53

This diff is too big to show here.

tests/writer.rst+140−124

This diff is too big to show here.

tests/writer.rtf+451

This diff is too big to show here.

tests/writer.texinfo+35−40

This diff is too big to show here.

tests/writer.textile+38−21

This diff is too big to show here.

tools/build-arm.sh−110

This diff is too big to show here.

tools/changelog-helper.sh−30

This diff is too big to show here.

tools/changes_template.html−6

This diff is too big to show here.

tools/diff-zip.sh−33

This diff is too big to show here.

tools/extract-changes.hs−15

This diff is too big to show here.

tools/github-upload.sh−18

This diff is too big to show here.

tools/pandoc-template-mode.el−64

This diff is too big to show here.

tools/parseTimings.pl−33

This diff is too big to show here.

tools/update-readme.lua−28

This diff is too big to show here.

trypandoc/Makefile−14

This diff is too big to show here.

trypandoc/index.html−190

This diff is too big to show here.

trypandoc/trypandoc.hs−76

This diff is too big to show here.

windows/AdvancedWelcomeEulaDlg_Custom.wxs−90

This diff is too big to show here.

windows/Makefile−10

This diff is too big to show here.

windows/Pandoc-en-us.wxl−14

This diff is too big to show here.

windows/WixUI_Advanced_Custom.wxs−142

This diff is too big to show here.

windows/make-windows-installer.bat+36

This diff is too big to show here.

windows/pandoc.wxs+126−186

This diff is too big to show here.