Age | Commit message (Collapse) | Author | Files | Lines |
|
Now base64 is used except for 'text/*' mime types. Closes #1940.
|
|
|
|
Previously we didn't transform lists inside table cells.
|
|
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.
|
|
Since blockquote derives from BodyText, we just want to specify by
default that it won't indent, regardless of what BodyText does. Note
that this will not produce any visible difference in the default
configuration.
|
|
This updates reference.docx to make BodyText a quick style, and inherit
from it appropriately.
|
|
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".
|
|
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.
|
|
|
|
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"
|
|
|
|
update syntax for Images/Media files in MediaWiki
|
|
Update travis file (for GHC 7.10)
|
|
|
|
into timtylin-patch/fixTexinfoWrap
Conflicts:
src/Text/Pandoc/Writers/Texinfo.hs
|
|
Append newline to the LineBreak of various writers
|
|
|
|
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]]'
|
|
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.
|
|
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
|
|
* Handle newlines in cells.
* Handle empty cells.
* Closes #1919.
|
|
|
|
|
|
This allows inline and display math to be styled differently.
Closes #1914.
|
|
Fixed issue #1131 + small refactoring
|
|
|
|
Fixes #1131
|
|
Should be "decimal," not "example." Closes #1902.
|
|
This should help with warnings from Ubuntu 14.04 Software Center.
See #1900.
|
|
fixes HTML Reader: tables
|
|
|
|
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.
|
|
Since images are often visually (not structurally) placed on the page,
people might not always get the results they're looking for here.
|
|
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.
|
|
The minified versions no longer ship with the library.
|
|
See https://github.com/jgm/pandoc/pull/1888#issuecomment-70470409
|
|
Eventually we'll change the return type so that no exception
is involved, but at least this can be trapped.
|
|
This will make debugging custom scripts much easier.
|
|
Better warning when trying to read multiple binary files
|
|
|
|
Closes #1884.
|
|
This is added automatically by the docx writer.
If it's in the template, we'll get two copies.
See #1872.
|
|
Don't log "Try xelatex..." if xelatex already in use
|
|
|
|
Allow compilation with ghc 7.10.1 RC1 and haddock-library 1.2
|
|
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
|
|
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
|
|
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#Inferredtype-signaturesnowmayrequiretoenableFlexibleContextsGADTsorTypeFamilies
|
|
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
|
|
https://ghc.haskell.org/trac/ghc/wiki/Migration/7.10#GHCsaysNoinstanceforFoldable...arisingfromtheuseof...
|