summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | | Added tests and a corner case for starting numberHubert Plociniczak2016-10-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Review revealed that we didn't handle the case when the starting point is an empty string. While this is not a valid .odt file, we simply added a special case to deal with it. Also added tests for the new feature.
| * | | [ODT Parser] Include list's starting valueHubert Plociniczak2016-10-12
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | Previously the starting value of the lists' items has been hardcoded to 1. In reality ODT's list style definition can provide a new starting value in one of its attributes. Writers already handle the modified start value so no need to change anything in that area.
* | | Travis: test with lts-7 not lts-6.John MacFarlane2016-10-14
| | |
* | | Use latest pandoc-types in windows/stack.yaml.John MacFarlane2016-10-13
| | |
* | | Use newest pandoc-types from repo.John MacFarlane2016-10-13
| | |
* | | Markdown writer: Abstract out note/ref function.Jesse Rosenthal2016-10-13
| | | | | | | | | | | | | | | We do basically the same thing every time we insert notes, so let's cut down on code duplication.
* | | Use latest pandoc-citeproc in stack.yamls.John MacFarlane2016-10-13
| | |
* | | Update stack.yaml files.John MacFarlane2016-10-13
| | |
* | | Allow http-client 0.4.30, which is the version in stackage lts.John MacFarlane2016-10-13
| | | | | | | | | | | | | | | Previously we required 0.5. Remove CPP conditionals for earlier versions.
* | | Revert "Remove http-client CPP conditionals."John MacFarlane2016-10-13
| | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 3f82471355286d33f2d73329c29a51c47bf76ad7. We might want to revert the requirement of http-client 0.5, as this is not yet in Stackage and that is starting to cause problems. I can't recall why it is there.
* | | Document `biblio-title` variable in MANUAL.txt.John MacFarlane2016-10-13
| | | | | | | | | | | | Cloess #258.
* | | Updated stack.yaml and windows/stack.yaml to use latest pandoc-types.John MacFarlane2016-10-13
| | |
* | | Merge pull request #3072 from tarleb/lineblockJohn MacFarlane2016-10-13
|\ \ \ | |/ / |/| | Read and write LineBlock elements
| * | Bump required pandoc-types version to 1.17Albert Krewinkel2016-10-13
| | |
| * | Allow empty lines when parsing line blocksAlbert Krewinkel2016-10-13
| | | | | | | | | | | | | | | | | | Line blocks are allowed to contain empty lines and should be parsed as a single block in that case. Previously an empty (line block) line would have terminated parsing of the line block element.
| * | Parse line-oriented markup as LineBlockAlbert Krewinkel2016-10-13
| | | | | | | | | | | | | | | | | | | | | | | | Markup-features focusing on lines as distinctive part of the markup are read into `LineBlock` elements. This currently means line blocks in reStructuredText and Markdown (the latter only if the `line_block` extension is enabled), the `linegroup`/`line` combination from the Docbook 5.1 working draft, and Org-mode `VERSE` blocks.
| * | Add support for the LineBlock element to writersAlbert Krewinkel2016-10-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following markup features are used to output the lines of the `LineBlock` element: - AsciiDoc: a `[verse]` block, - ConTeXt: text surrounded by `\startlines` and `\endlines`, - HTML: `div` with an per-element style setting to interpret the content as pre-wrapped, - Markdown: line blocks if the `line_blocks` extension is enabled, a simple paragraph with hard linebreaks otherwise, - Org: VERSE block, - RST: a line block, and - all other formats: a paragraph, containing hard linebreaks between lines. Custom lua writers should be updated to use the `LineBlock` element.
| * | Shared: add function combining lines using LineBreakAlbert Krewinkel2016-10-13
|/ / | | | | | | | | | | | | The `linesToBlock` function takes a list of lines and combines them by appending a hard `LineBreak` to each line and concatenating the result, putting the result it into a `Para`. This is most useful when dealing when converting `LineBlock` elements.
* | MANUAL: Made formatting of arguments with several options consistent.John MacFarlane2016-10-12
| |
* | Note on --reference-links about --reference-location.John MacFarlane2016-10-12
| |
* | Merge pull request #3159 from jkr/refsJohn MacFarlane2016-10-12
|\ \ | | | | | | Specify location for footnotes (and reference links) in MD output
| * | MANUAL.txt: document --reference-location.Jesse Rosenthal2016-10-11
| | |
| * | Markdown writer: add test for note placement.Jesse Rosenthal2016-10-11
| | |
| * | Add reference-location options to executable.Jesse Rosenthal2016-10-11
| | |
| * | Markdown writer: Allow footnotes/refs at the end of blocks, sectionsJesse Rosenthal2016-10-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows footnotes and refs to be placed at the end of blocks and sections. Note that we only place them at the end of blocks that are at the top level and before headers that are the top level. We add an environment variable to keep track of this. Because we clear the footnotes and refs when we use them, we also add a state variable to keep track of the starting number. Finally, note that we still add any remaining footnotes at the end. This takes care of the final section, if we are placing at the end of a section, and will always come after a final block as well.
| * | Add ReaderT monad for environment variables.Jesse Rosenthal2016-10-11
| | | | | | | | | | | | This will make it easier to keep track of what level of block we are at.
| * | Options: Add references location.Jesse Rosenthal2016-10-11
| | | | | | | | | | | | | | | This will be used by the markdown writer for deciding where to put links and footnotes.
* | | Org reader: trim verse lines properlyAlbert Krewinkel2016-10-10
|/ / | | | | | | An empty verse line should not result in `Str ""` but in `mempty`.
* | More checks for Ext_raw_html when rendering HTML in Markdown.John MacFarlane2016-10-10
| | | | | | | | | | | | | | | | | | | | | | | | | | Previously we'd emit raw HTML tables even if the `raw_html` extension was disabled. Now we just emit `[TABLE]` if no table formats are enabled and raw HTML is not enabled. We also check for the `raw_html` extension before emiting a raw HTML block. Closes #3154.
* | Merge pull request #3156 from ickc/removing-googlecodeJohn MacFarlane2016-10-10
|\ \ | |/ |/| Delete googlecode-upload.sh
| * Delete googlecode-upload.shickc2016-10-09
|/
* remove temporary checklistKolenCheung2016-10-09
|
* update manual accordinglyKolenCheung2016-10-09
|
* removed mmd raw_tex in src/Text/Pandoc/Options.hsKolenCheung2016-10-09
|
* add a temp file to keep track of all files involving markdown_mmd and ↵KolenCheung2016-10-09
| | | | multimarkdownExtensions
* Added a small clarification on --webtex with Markdown output.John MacFarlane2016-10-06
| | | | Thanks to @ickc.
* fix typoKolenCheung2016-10-06
|
* Replace Google Chart API by CodeCogsKolenCheung2016-10-06
|
* Docx writer: Move one more env var to Reader monadJesse Rosenthal2016-10-05
| | | | | | PrintWidth is set at the beginning and stays the same throughout the document writing, so we just set it as an env variable in the Reader monad.
* Docx writer: code legibility fixups.Jesse Rosenthal2016-10-05
| | | | More meaningful variable name, and explanatory comment.
* Docx writer: Clean up and streamline RTL behaviorJesse Rosenthal2016-10-04
| | | | | | | | | | | | Now RTL is turned and off by a general function, `withDirection` wrapping `inlineToOpenXML` and `blockToOpenXML`. This acts according to the `envRTL` variable. This means we can just set the environment at the outset, and change the environment with `local` as need be. Note that this requires making the `inlineToOpenXML` and `blockToOpenXML` functions into wrappers around primed-versions (`{inline,block}ToOpenXML`) where the real work takes place.
* Docx writer: move a couple more vars to ReaderTJesse Rosenthal2016-10-04
| | | | | | | | | | | | | | | In general, we want things that are either: 1. unchanging environment variables, or 2. environment variables that will change for a the scope of a function and then pop back to be in the reader monad. This is safer for (1), since we won't accidentally change it, and easier for (2), since we can use `local` instad of setting the old value and then resetting. We keep the StateT monad for values that we will want to accumulate or change and then use later.
* Merge pull request #3141 from ickc/masterJohn MacFarlane2016-10-04
|\ | | | | Update KaTeX to v0.6.0
| * Update KaTeX to v0.6.0KolenCheung2016-10-03
|/
* Clean up commented-out codeJesse Rosenthal2016-10-03
| | | | | A few commented out functions were left in the code during the conversion from StateT to ReaderT. This removes them.
* Remove bool on setRTL.Jesse Rosenthal2016-10-03
| | | | | | | We had to use this because we set the env, which means that setRTL wouldn't do anything at the top level. We now don't set the env (it will always be false at the outset), which means the toplevel setRTL will work if necessary.
* Filter text/para props correctly.Jesse Rosenthal2016-10-03
| | | | We only filter on the name, not the prefix.
* Add a boolean flag to the setRTL function.Jesse Rosenthal2016-10-03
| | | | At the toplevel we don't check to see if RTL is already set.
* Test for "dir" metadata.Jesse Rosenthal2016-10-03
|
* Add setRTL and setLTR functions.Jesse Rosenthal2016-10-03
|