summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* LaTeX writer: change braced backtick to \textasciigrave{}Jesse Rosenthal2016-09-20
| | | | | | | Backticks in verbatim environments are converted to open-single-quotes. This change makes them appear as backticks. This corresponds to how we treat `'' in verbatim environments (with \textquotesingle{}).
* LaTeX writer: enclose backtick in `{}` in verbatimJesse Rosenthal2016-09-19
| | | | | | | We don't want ligatures like ` ?` ` (which produces `¿`) inside `\texttt{}` environments, so we enclose the backtick in braces. This fixes #3121
* DocBook writer: include an anchor element when a div or span has an id.John MacFarlane2016-09-06
| | | | | This closes #3102. Note that DocBook does not have a class attribute, but at least this provides an anchor for internal links.
* Remove http-client CPP conditionals.Jesse Rosenthal2016-09-03
| | | | | Our lower bound on http-client is 0.5, and both of these min_version tests are less than 0.5, so they will always pass.
* Remove blaze-html CPP conditional.Jesse Rosenthal2016-09-03
| | | | | | | | This tests for a min value >= 0.5. But we have a lower bound of 0.5 in pandoc.cabal, so the test will always pass. (If we bump the lower bound to 0.5.1, we can remove a conditional in the HTML writer as well.)
* Add EOL note to time compat module.Jesse Rosenthal2016-09-03
| | | | | | Because time 1.4 is a boot library for GHC 7.8, we will support the compatibility module as long as we support 7.8. But we should be clear about when we will no longer need it.
* Remove TagSoup compatJesse Rosenthal2016-09-02
| | | | | | | We already lower-bound tagsoup at 0.13.7, which means we were always running the compatibility layer (it was conditional on min value 0.13). Better to just use `lookupEntity` from the library directly, and convert a string to a char if need be.
* Remove unnecessary CPP condition in UTF8Jesse Rosenthal2016-09-02
| | | | Base 4.4 is ghc 7.2, so we don't have to worry about getting a lower version.
* Actually remove T/P/Compat/Except.Jesse Rosenthal2016-09-02
|
* Remove directory compatJesse Rosenthal2016-09-02
| | | | | directory 1.1 depends on base 4.5 (ghc 7.4) which we are no longer supporting. So we don't have to use a compatibility layer for it.
* Remove Text.Pandoc.Compat.ExceptJesse Rosenthal2016-09-02
|
* Fix grouping of imports.Jesse Rosenthal2016-09-02
| | | | | | Some source files keep imports in tidy groups. Changing `Text.Pandoc.Compat.Monoid` to `Data.Monoid` could upset that. This restores tidiness.
* Remove an inline monad compatibility macro.Jesse Rosenthal2016-09-02
|
* Remove Compat.MonoidJesse Rosenthal2016-09-02
| | | | | This was only necessary for GHC versions with base below 4.5 (i.e., ghc < 7.4).
* PDF: Don't crash with nonexistent image.John MacFarlane2016-09-02
| | | | | | | | | | Instead, emit the alt text, emphasized. This accords with what the ODT writer currently does. The user will still get a warning about a nonexistent image, but will no longer get a LaTeX crash. Closes #3100.
* Merge pull request #3091 from wilx/master-narrow-no-break-spaceJohn MacFarlane2016-09-02
|\ | | | | Translate NARROW NO-BREAK SPACE into LaTeX.
| * Translate NARROW NO-BREAK SPACE into LaTeX.Vaclav Zeman2016-08-27
| | | | | | | | Translate NARROW NO-BREAK SPACE into LaTeX' `\,`.
* | Org reader: respect unnumbered header propertyAlbert Krewinkel2016-08-30
| | | | | | | | | | | | | | | | | | | | | | Sections the `unnumbered` property should, as the name implies, be excluded from the automatic numbering of section provided by some output formats. The Pandoc convention for this is to add an "unnumbered" class to the header. The reader treats properties as key-value pairs per default, so a special case is added to translate the above property to a class instead. Closes #3095.
* | Docx reader: make all compilers happy with traversable.Jesse Rosenthal2016-08-29
| | | | | | | | | | The last attempt to make 7.8 happy made 7.10 unhappy. So we need some conditional logic to appease all versions.
* | Docx reader: Import traverse for ghc 7.8Jesse Rosenthal2016-08-29
| | | | | | | | The GHC 7.8 build was erroring without it.
* | Docx reader: clean up function with `traverse`Jesse Rosenthal2016-08-29
| |
* | Merge branch 'org-meta-handling'Albert Krewinkel2016-08-29
|\ \
| * | Org reader: respect `creator` export optionAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `creator` option controls whether the creator meta-field should be included in the final markup. Setting `#+OPTIONS: creator:nil` will drop the creator field from the final meta-data output. Org-mode recognizes the special value `comment` for this field, causing the creator to be included in a comment. This is difficult to translate to Pandoc internals and is hence interpreted the same as other truish values (i.e. the meta field is kept if it's present).
| * | Org reader: respect `email` export optionAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | | | | The `email` option controls whether the email meta-field should be included in the final markup. Setting `#+OPTIONS: email:nil` will drop the email field from the final meta-data output.
| * | Org reader: respect `author` export optionAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | | | | The `author` option controls whether the author should be included in the final markup. Setting `#+OPTIONS: author:nil` will drop the author from the final meta-data output.
| * | Org reader: read HTML_head as header-includesAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | | | | HTML-specific head content can be defined in `#+HTML_head` lines. They are parsed as format-specific inlines to ensure that they will only show up in HTML output.
| * | Org reader: set classoption meta from LaTeX_class_optionsAlbert Krewinkel2016-08-29
| | |
| * | Org reader: set documentclass meta from LaTeX_classAlbert Krewinkel2016-08-29
| | |
| * | Org reader: read LaTeX_header as header-includesAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | | | | LaTeX-specific header commands can be defined in `#+LaTeX_header` lines. They are parsed as format-specific inlines to ensure that they will only show up in LaTeX output.
| * | Org reader: give precedence to later meta linesAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | | | | The last meta-line of any given type is the significant line. Previously the value of the first line was kept, even if more lines of the same type were encounterd.
| * | Org reader: allow multiple, comma-separated authorsAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | Multiple authors can be specified in the `#+AUTHOR` meta line if they are given as a comma-separated list.
| * | Org reader: read markup only for special meta keysAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | Most meta-keys should be read as normal string values, only a few are interpreted as marked-up text.
| * | Org reader: extract meta parsing code to moduleAlbert Krewinkel2016-08-29
| | | | | | | | | | | | | | | Parsing of meta-data is well separable from other block parsing tasks. Moving into new module to get small files and clearly arranged code.
* | | Docx reader: update copyright.Jesse Rosenthal2016-08-28
| | |
* | | Docx reader: use all anchor spans for header ids.Jesse Rosenthal2016-08-28
| | | | | | | | | | | | | | | | | | | | | | | | Previously we only used the first anchor span to affect header ids. This allows us to use all the anchor spans in a header, whether they're nested or not. Along with 62882f97, this closes #3088.
* | | Docx reader: Let headers use exisiting id.Jesse Rosenthal2016-08-28
| | | | | | | | | | | | | | | | | | Previously we always generated an id for headers (since they wouldn't bring one from Docx). Now we let it use an existing one if possible. This should allow us to recurs through anchor spans.
* | | Docx reader: Handle anchor spans with content in headers.Jesse Rosenthal2016-08-28
| |/ |/| | | | | | | | | | | | | | | Previously, we would only be able to figure out internal links to a header in a docx if the anchor span was empty. We change that to read the inlines out of the first anchor span in a header. This still leaves another problem: what to do if there are multiple anchor spans in a header. That will be addressed in a future commit.
* | Man writer: allow section numbers that are not a single digit.John MacFarlane2016-08-27
|/ | | | Closes #3089.
* Org writer: translate language identifiersAlbert Krewinkel2016-08-20
| | | | | | | Pandoc and Org-mode use different programming language identifiers. An additional translation between those identifiers is added to avoid unexpected behavior. This fixes a problem where language specific source code would sometimes be output as example code.
* Org writer: ensure link targets are paths or URLsAlbert Krewinkel2016-08-18
| | | | | | Org-mode treats links as document internal searches unless the link target looks like a URL or file path, either relative or absolute. This change ensures that this is always the case.
* Org writer: ensure blank line after figureAlbert Krewinkel2016-08-18
| | | | | | An Org-mode figure should be surrounded by blank lines. The figure would be recognized regardless, but images in the following line would unintentionally be treated as figures as well.
* Org writer: remove blank line after figure captionAlbert Krewinkel2016-08-18
| | | | | Org-mode only treats an image as a figure if it is directly preceded by a caption.
* Docx Writer: change dynamic style keyJesse Rosenthal2016-08-15
| | | | | Use "custom-style" instead of "docx-style." This allows it to be used in other formats like ODT in the future.
* Docx writer: Inject text properties as well.Jesse Rosenthal2016-08-15
|
* Docx Writer: Keep track of dynamic text props too.Jesse Rosenthal2016-08-15
|
* Docx writer: Allow dynamic styles on spans.Jesse Rosenthal2016-08-15
| | | | | | This enables dynamic styling on spans. It uses the same prefix as we used on divs ("docx-style" for the moment). It does not yet inject the style into styles.xml.
* Docx writer: Inject new paragraph propertiesJesse Rosenthal2016-08-15
| | | | | This injects new dynamic paragraph properties to be into the style file. Nothing occurs if the prop already exists in the style file.
* StyleMap: export functions on StyleMap instancesJesse Rosenthal2016-08-15
| | | | We're going to want `getMap` in the Docx Writer.
* Docx Writer: Have state keep track of dynamic styles.Jesse Rosenthal2016-08-15
| | | | We want to be able to inject these into our styles.xml.
* Docx Writer: Implement user-defined styles.Jesse Rosenthal2016-08-13
| | | | | Divs with a "docx-style" key in the attributes will apply the corresponding key to the contained blocks.