summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Markdown Reader: add attributes for autolink (#3183)Daniele D'Orazio2016-10-26
|
* reveal.js: don't change slide title to level 1 header.John MacFarlane2016-10-25
| | | | | | This also affects other HTML slide show formats. Closes #2221.
* Export Text.Pandoc.Error in Text.Pandoc.John MacFarlane2016-10-24
| | | | [API change]
* Tighten up parsing of raw email addresses.John MacFarlane2016-10-23
| | | | | | | | | | Technically `**@user` is a valid email address, but if we allow things like this, we get bad results in markdown flavors that autolink raw email addresses. (See #2940.) So we exclude a few valid email addresses in order to avoid these more common bad cases. Closes #2940.
* fix example in documentation (#3176)Thomas Weißschuh2016-10-23
| | | Errors are encountered while reading, not writing
* ICML writer: replace partial function (!!) in table handling (#3175)Mauro Bieg2016-10-23
|
* Added `angle_brackets_escapable` extension.John MacFarlane2016-10-22
| | | | | | | | This is needed because github flavored Markdown has a slightly different set of escapable symbols than original Markdown; it includes angle brackets. Closes #2846.
* EPUB reader: don't add root path to data: URIs.John MacFarlane2016-10-22
| | | | | | Closes #3150. Thanks to @lep for the bug report and patch.
* Merge pull request #3108 from tarleb/partJohn MacFarlane2016-10-19
|\ | | | | Add command line option allowing to set type of top-level divisions
| * Add option for top-level division typeAlbert Krewinkel2016-10-19
| | | | | | | | | | | | | | | | | | | | The `--chapters` option is replaced with `--top-level-division` which allows users to specify the type as which top-level headers should be output. Possible values are `section` (the default), `chapter`, or `part`. The formats LaTeX, ConTeXt, and Docbook allow `part` as top-level division, TEI only allows to set the `type` attribute on `div` containers. The writers are altered to respect this option in a sensible way.
| * TEI writer: remove heuristic to detect book templateAlbert Krewinkel2016-09-13
| | | | | | | | | | TEI doesn't have `<book>` elements but only generic `<divN>` division elements. Checking the template for a trailing `</book>` is nonsensical.
| * Add --parts command line option to LaTeX writer.Oliver Matthews2016-09-06
| | | | | | | | | | | | | | Add --parts command line argument. This only effects LaTeX writer, and only for non-beamer output formats. It changes the output levels so the top level is 'part', the next 'chapter' and then into sections.
* | Image with a caption needs special formattingHubert Plociniczak2016-10-19
|/ | | | | Latex Writer only handles captions if the image's title is prefixed with 'fig:'.
* Merge pull request #3166 from hubertp-lshift/bug/3134John MacFarlane2016-10-18
|\ | | | | Issue 3143: Don't duplicate text for anchors
| * Issue 3143: Don't duplicate text for anchorsHubert Plociniczak2016-10-18
| | | | | | | | | | When creating an anchor element we were adding its representation as well as the original content, leading to text duplication.
* | Merge pull request #3165 from hubertp-lshift/feature/odt-imageJohn MacFarlane2016-10-18
|\ \ | | | | | | [odt] images parser
| * | Use bind function instead of pattern matchingHubert Plociniczak2016-10-17
| | |
| * | Minor refactoringHubert Plociniczak2016-10-17
| | |
| * | Infer caption from the text following the imgHubert Plociniczak2016-10-17
| | | | | | | | | | | | | | | | | | | | | Frame can contain other frames with the text boxes. This is something that has not been considered before and meant that the whole construction of images was broken in those cases. Also the captions were fixed/ignored.
| * | Basic support for images in ODT documentsHubert Plociniczak2016-10-12
| |/ | | | | | | | | Highly influenced by the docx support, refactored some code to avoid DRY.
* | Better fix for the problem with ghc 7.8.John MacFarlane2016-10-18
| |
* | Try to fix build error on ghc 7.8.John MacFarlane2016-10-18
| | | | | | | | | | | | | | | | | | @tarleb this is an interesting one, see the build log in https://travis-ci.org/jgm/pandoc/jobs/168612017 It only failed on ghc 7.8; I think this must have to do with the change making Monad a superclass of Applicative, hence this change.
* | Org writer: drop space before footnote markersAlbert Krewinkel2016-10-17
| | | | | | | | | | | | The writer no longer adds an extra space before footnote markers. Fixes: #3162
* | RST reader: skip whitespace before note.Jesse Rosenthal2016-10-17
| | | | | | | | | | | | | | | | | | | | RST requires a space before a footnote marker. We discard those spaces so that footnotes will be adjacent to the text that comes before it. This is in line with what rst2latex does. rst2html does not discard the space, but its html output is different than pandoc's, so this seems the most semantically correct approach. Closes #3163
* | Org reader: allow figure with empty captionAlbert Krewinkel2016-10-14
| | | | | | | | | | | | | | | | | | A `#+CAPTION` attribute before an image is enough to turn an image into a figure. This wasn't the case because the `parseFromString` function, which processes the caption value, would fail on empty values. Adding a newline character to the caption value fixes this. Fixes: #3161
* | Merge pull request #3146 from hubertp-lshift/feature/odt-list-start-valueJohn MacFarlane2016-10-14
|\ \ | | | | | | [ODT Parser] Include list's starting value
| * | 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.
* | 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.
* | 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.
* | 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.
* Merge pull request #3159 from jkr/refsJohn MacFarlane2016-10-12
|\ | | | | Specify location for footnotes (and reference links) in MD output
| * 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.
* removed mmd raw_tex in src/Text/Pandoc/Options.hsKolenCheung2016-10-09
|
* 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.
* 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-28 08:19:10 +0000