aboutsummaryrefslogtreecommitdiff
path: root/src/Text/Pandoc
AgeCommit message (Collapse)AuthorFilesLines
2015-02-25Docbook writer: don't print empty id attributes.John MacFarlane1-1/+2
Thanks to Steve Horne for reporting.
2015-02-24Comment out unused functions to make CI happyNikolay Yakimov1-8/+8
2015-02-24Treat some ambiguous styles as custom for nowNikolay Yakimov1-11/+10
* Author * Abstract * Compact * ImageCaption * TableCaption * DefinitionTerm * Definition * FirstParagraph
2015-02-23Do not lookup custom stylesNikolay Yakimov1-9/+13
2015-02-23Also skip SourceCode style if existsNikolay Yakimov1-9/+12
2015-02-22If --no-highlight is set, remove *Tok styles.Nikolay Yakimov1-2/+10
2015-02-22Prototype fix for #1872Nikolay Yakimov1-4/+7
2015-02-21Initial stab at more involved fix for #1607Nikolay Yakimov1-64/+86
This patch attempts to build a style name -> style id mapping based on styles.xml from reference doc, and changes pStyle and rStyle to accept style name as a parameter instead of styleId. There is a fallback mechanic that removes spaces from style name and returns it as style id, but it likely won't help much. Style names are matched lower-case, since headings and `footnote text` have lowercase names.
2015-02-21Docx reader: Minor cleanup.Jesse Rosenthal1-3/+4
The previous commits had some code repetition. This just makes it a bit easier to read.
2015-02-21Docx reader: allow sub/superscript verbatims.Jesse Rosenthal1-1/+6
Verbatim usually shuts off all other run styles, but we don't want it to shut off sub/superscript.
2015-02-20LaTeX Writer: Don't use listings in headersMatthew Pickering1-3/+4
Fixes #1963
2015-02-19Docx reader: Allow numbering in the style file.Jesse Rosenthal1-21/+33
This allows inherited styles with numbering (lists). It works like this: 1. check to see if the style has numbering info. 2. if the paragraph has explicit numbering info in the doc that takes precedence. 3. if not we use the numbering info in the style, if it's there. 4. otherwise normal paragraph. We no longer assume it's not a numbering element if it doesn't have an explicit level---we just set that level to 1. (In the style files, the examples I've seen don't have that explicit level.)
2015-02-18Move utility error functions to Text.Pandoc.SharedMatthew Pickering4-11/+13
2015-02-18Update haddocks and copyright noticesMatthew Pickering1-2/+34
2015-02-18Make safeRead safe.Matthew Pickering1-3/+3
Fixes #1801
2015-02-18Change return type of Txt2Tags readerMatthew Pickering1-2/+3
2015-02-18Change return type of Textile readerMatthew Pickering1-1/+2
2015-02-18Change return type of TWiki readerMatthew Pickering1-2/+3
2015-02-18Change return type of RST readerMatthew Pickering1-2/+4
2015-02-18Change return type of Org readerMatthew Pickering1-4/+6
2015-02-18Change return type of OPML readerMatthew Pickering1-20/+28
2015-02-18Change return type of Native readerMatthew Pickering1-26/+14
2015-02-18Change return type of Mediawiki readerMatthew Pickering1-5/+5
2015-02-18Change return type of Markdown readerMatthew Pickering1-25/+33
2015-02-18Change return type of LaTeX readerMatthew Pickering1-7/+4
2015-02-18Change return type of Haddock readerMatthew Pickering1-3/+5
2015-02-18Change return type of HTML readerMatthew Pickering1-5/+12
2015-02-18Change return type of EPUB readerMatthew Pickering1-17/+20
2015-02-18Change return type of Docx readerMatthew Pickering1-8/+11
2015-02-18Change return type of DocBook readerMatthew Pickering1-11/+16
2015-02-18Add Text.Pandoc.Error module with PandocError typeMatthew Pickering2-13/+45
2015-02-18Remove partial function from PrettyMatthew Pickering1-7/+11
2015-02-18Remove landmine from ImageSizeMatthew Pickering1-30/+37
2015-02-18Factor out "returnState" into Parsing moduleMatthew Pickering3-15/+7
2015-02-18HLint changesMatthew Pickering1-82/+76
2015-02-18Remove F Monad from Markdown readerMatthew Pickering1-312/+307
2015-02-18Generalise signature of addWarningMatthew Pickering1-1/+1
2015-02-18Add check to see whether in a footnote to ParserState (to avoid circular ↵Matthew Pickering1-2/+4
footnotes)
2015-02-18Remove F monad from ParsingMatthew Pickering2-26/+3
2015-02-18Changed parseWithWarnings to the more general returnWarnings parser transformerMatthew Pickering2-7/+6
2015-02-18Remove F monad from Org Reader.Matthew Pickering1-227/+212
2015-02-18Added generalize function which can be used to lift specialised parsers.Matthew Pickering1-0/+4
Monad m => Parsec s st a -> Parsec T s st m a
2015-02-17ICML writer: Better handling of raw blocks and inlines.John MacFarlane1-4/+6
Previously these were always escaped and printed verbatim. Now they are ignored unless the format is "icml", in which case they are passed through unescaped. Closes #1951.
2015-02-13Allow wildcards in `--epub-embed-font` arguments.John MacFarlane1-2/+9
Closes #1939.
2015-02-13Improved building of data URIs in SelfContained.John MacFarlane1-8/+15
Now base64 is used except for 'text/*' mime types. Closes #1940.
2015-02-13Docx reader: Handle lists correctly inside table cells.Jesse Rosenthal1-1/+3
Previously we didn't transform lists inside table cells.
2015-02-12Docx writer: Add footnotes id -1 and 0.Jesse Rosenthal1-1/+17
Word uses, by default, footnotes with id -1 and 0 for separators. If a user modifies reference.docx, they will end up with a settings.xml file that references these footnotes, but no such footnotes in the document. This will produce a corruption error. Here we add these to the document and settings.xml file, so future modifications won't break the file.
2015-02-11Docx Writer: Add "BodyText" StyleJesse Rosenthal1-9/+11
We apply a "BodyText" style to all unstyled paragraphs. This is, essentially, the same as "Normal" up until now -- except that since not everything inherits from "BodyText" (the metadata won't, for example, or the headers or footnote numbers) we can change the text in the body without having to make exceptions for everything. This will still inherit from Normal, so if we want to change *everything*, we can do it through "Normal".
2015-02-10Docx Writer: Use FirstParagraph style at beginning.Jesse Rosenthal1-1/+1
Before we had used `FirstParagraph` style after Headings, BlockQuotes, and other blocks a user might not want an indentation after. We hadn't actually used it for the first paragraph -- i.e. the opening of the body. This makes sure the first body paragraph gets that style.
2015-02-09Docx Writer: Implement FirstParagraph StyleJesse Rosenthal1-15/+39
Following the odt writer, we make the first text paragraph following an image, blockquote, table, or heading into a "FirstParagraph" style. This allows it to be styled differently, if the user wishes. The default is for it to be the same as "Normal"
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-13 23:52:17 +0000