aboutsummaryrefslogtreecommitdiff
path: root/src/Text
AgeCommit message (Collapse)AuthorFilesLines
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"
2015-02-07Merge pull request #1927 from freephile/masterJohn MacFarlane1-2/+2
update syntax for Images/Media files in MediaWiki
2015-02-07Merge branch 'patch/fixTexinfoWrap' of https://github.com/timtylin/scholdoc ↵John MacFarlane1-1/+1
into timtylin-patch/fixTexinfoWrap Conflicts: src/Text/Pandoc/Writers/Texinfo.hs
2015-02-06Texinfo writer: fix wrapping by using breakable spacesTim Lin1-1/+1
2015-02-05update syntax for Images/Media files in MediaWikiGreg Rundlett1-2/+2
The preferred syntax for Images and other media is [[File:Foo.jpg]] in MediaWiki since v1.14 (2008). [[Image:Foo.jpg]] is deprecated but still works as an alias to the File namespace. I don't think this would break any existing wikis since talk of switching the syntax/namespace for images started back in 2002 (https://phabricator.wikimedia.org/T2044). NS_FILE became the new namespace for Files in v 1.14 in late 2008. (https://www.mediawiki.org/wiki/Release_notes/1.14) There is still a namespace alias so '[[Image:]]' still works today. It's just that MediaWiki supports other media as well, and so the name and syntax used in documentation (see https://www.mediawiki.org/wiki/Help:Images) has long been '[[File:foo.jpg]]'
2015-02-04Append newline to the LineBreak of various writersTim Lin6-6/+7
This change improves output formatting of content with a large amount of force line breaks, such as line-blocks. The following writers are affected: * Dokuwiki * HTML * EPUB (via HTML) * LaTeX * MediaWiki * OpenDocument * Texinfo This commit resolves #1924
2015-02-02Textile reader: table improvements.John MacFarlane1-16/+14
* Handle newlines in cells. * Handle empty cells. * Closes #1919.
2015-02-01LaTeX writer: Don't escape $ in URL. Closes #1913.John MacFarlane1-1/+1
2015-02-01HTML writer: Add "inline" or "display" class to math spans.John MacFarlane1-57/+60
This allows inline and display math to be styled differently. Closes #1914.
2015-01-29Refactored `if x then [] else y` to `[y | not x]`Konstantin Zudov1-6/+2
2015-01-29Do not ommit missing `alt` attribute on `img` tagKonstantin Zudov1-4/+1
Fixes #1131
2015-01-27Fixed list-style-type for numbered example lists.John MacFarlane1-1/+3
Should be "decimal," not "example." Closes #1902.
2015-01-25Merge pull request #1885 from mb21/html-reader-tablesJohn MacFarlane1-11/+22
fixes HTML Reader: tables
2015-01-25fixes #1859 HTML Reader table parsingmb211-11/+22
2015-01-22LaTeX reader: don't limit includes to .tex extension.John MacFarlane1-2/+8
Previously `\input` and `\include` would only work if the included files had the extension `.tex`. This change relaxes that restriction, though if the extension is not `.tex`, it must be given explicitly in the `\input` or `\include`. Closes #1882.
2015-01-21Docx: Parse images in deprecated vml format.Jesse Rosenthal1-0/+10
Some older versions of word use vml (vector markup language) and put their images in a "v:imagedata" tag inside a "w:pict". We read those as we read the more modern "blip" inside a "w:drawing". Note that this does not mean the reader knows anything about vml. It just looks for a `v:imagdata`. It's possible that, with more complicated uses of images in vml, it won't do the right thing.
2015-01-19Use CPP to avoid unneeded import warning for blaze-markup >= 0.6.3.John MacFarlane1-0/+3
See https://github.com/jgm/pandoc/pull/1888#issuecomment-70470409
2015-01-18Custom writer: Raise `PandocLuaException` instead of using 'error'.John MacFarlane1-2/+9
Eventually we'll change the return type so that no exception is involved, but at least this can be trapped.
2015-01-18Custom writer: raise error if loadstring returns an error status.John MacFarlane1-1/+6
This will make debugging custom scripts much easier.
2015-01-17EPUB writer: properly handle internal links to IDs in spans, divs.John MacFarlane1-11/+18
Closes #1884.
2015-01-11don't log Try xelatex if xelatex already in use, closes #1832mb211-2/+3
2015-01-05ghc 7.10.1 RC1 requires specifying the type of String literals ↵Mark Wright1-1/+1
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
2015-01-05ghc 7.10.1 RC1 requires specifying the type of String literals ↵Mark Wright1-3/+3
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
2015-01-05ghc 7.10.1 RC1 requires FlexibleContexts ↵Mark Wright1-1/+1
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#Inferredtype-signaturesnowmayrequiretoenableFlexibleContextsGADTsorTypeFamilies
2015-01-05ghc 7.10.1 RC1 requires specifying the type of String literals ↵Mark Wright1-6/+6
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
2015-01-05ghc 7.10.1 RC1 requires specifying the type of String literals ↵Mark Wright1-1/+1
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
2015-01-05ghc 7.10.1 RC1 requires FlexibleContexts ↵Mark Wright1-1/+1
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#Inferredtype-signaturesnowmayrequiretoenableFlexibleContextsGADTsorTypeFamilies
2015-01-05ghc 7.10.1 RC1 requires FlexibleContexts ↵Mark Wright1-1/+1
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#Inferredtype-signaturesnowmayrequiretoenableFlexibleContextsGADTsorTypeFamilies
2015-01-05ghc 7.10.1 RC1 requires specifying the type of String literals ↵Mark Wright1-1/+1
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
2015-01-05ghc 7.10.1 RC1 requires specifying the type of String literals ↵Mark Wright1-2/+2
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
2015-01-05ghc 7.10.1 RC1 requires FlexibleContexts ↵Mark Wright1-1/+1
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#Inferredtype-signaturesnowmayrequiretoenableFlexibleContextsGADTsorTypeFamilies
2015-01-05ghc 7.10.1 RC1 requires FlexibleContexts ↵Mark Wright1-1/+2
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#Inferredtype-signaturesnowmayrequiretoenableFlexibleContextsGADTsorTypeFamilies ; ghc 7.10.1 RC1 requires specifying the type of String literals https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
2015-01-05ghc 7.10.1 RC1 requires FlexibleContexts ↵Mark Wright1-3/+4
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#Inferredtype-signaturesnowmayrequiretoenableFlexibleContextsGADTsorTypeFamilies ; ghc 7.10.1 RC1 requires specifying the type of String literals https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-02 17:56:12 +0000