| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Using `map toUpper` to capitalise text is wrong, as e.g.
“Straße” should be converted to “STRASSE”, which is 1 character
longer. This commit adds a `capitalize` function and replaces
2 identical implementations in different modules (`toCaps` and
`capitalize`) with it.
|
|
(This fixes a bug introduced a couple commits back.)
|
|
Strip a fragment like `?#iefix` from the extension before doing
the mime lookup.
|
|
* More consistent logic: absolute URIs are fetched from the net;
other things are treated as relative URIs if sourceURL is a Just,
otherwise as file paths.
* We escape characters that are not allowed in URIs before trying
to parse them (e.g. '|', which often occurs in the wild).
* When treating relative paths as local file paths, we drop
any fragment or query. This is useful e.g. when you've downloaded
web fonts locally, but your source still contains the original
relative URLs.
Together with the previous commit, this should close #1477.
|
|
* mkSelfContained now takes just two arguments, WriterOptions and
the string.
* It no longer looks in data files. This only made sense when we
had copies of slidy and S5 code there.
* Shared.fetchItem' is used instead of the nearly duplicate getItem.
|
|
All other underlines are ignored.
|
|
Moved `MediaBag` definition and functions from Shared:
`lookupMedia`, `mediaDirectory`, `insertMedia`, `extractMediaBag`.
Removed `emptyMediaBag`; use `mempty` instead, since `MediaBag`
is a Monoid.
|
|
Shared now exports functions for interacting with a MediaBag:
- `emptyMediaBag`
- `lookuMedia`
- `insertMedia`
- `mediaDirectory`
- `extractMediaBag`
|
|
|
|
This is handled by readerExtensions now.
|
|
Get latest modification time.
|
|
Added a parameter to makeSelfContained (API change).
|
|
Use calculated sizes.
|
|
|
|
The MediaBag is thread through from the reader, with no need
to extract to files.
|
|
|
|
|
|
|
|
This will allow us to put a MediaBag in WriterOptions.
|
|
API change.
|
|
|
|
|
|
Image data will not be put in a media bag map, which will be output
along with the pandoc output.
|
|
Closes #1445. Escapes can still be used with `<code>`
and `<pre>`.
|
|
Use Subtitle style.
See #1451.
|
|
Closes #1464.
|
|
Make metadata out of styled pars
|
|
This will make paragraphs styled with `Author`, `Title`, `Subtitle`,
`Date`, and `Abstract` into pandoc metavalues, rather than text. The
implementation only takes those elements from the beginning of the
document (ignoring empty paragraphs).
Multiple paragraphs in the `Author` style will be made into a metaList,
one paragraph per item. Hard linebreaks (shift-return) in the paragraph
will be maintained, and can be used for institution, email, etc.
|
|
|
|
Closes #1458.
|
|
Math now appears in unicode if possible, without the distracting
italics around identifiers.
Blank lines around headers are more consistent.
Footnotes appear in regular [n] style.
|
|
This ensures a certain number of blanklines (and no more) in output.
|
|
We now largely follow the style of Project Gutenberg.
Emphasis is rendered with `_underscores_`, strong with ALL CAPS.
The appearance of horizontal rules has changed (even in regular
markdown) to a line across the whole page.
Headings are rendered differently, using space to set them off.
|
|
They now behave like the new reader does. The old behavior
can be activated with the `compact_definition_lists` extension.
|
|
|
|
Addresses docx part of #1451.
|
|
Generalised more in Parsing.hs to enable the use of custom state
|
|
|
|
|
|
|
|
|
|
http://txt2tags.org/
There are two points which currently do not match the official
implementation.
1. In the official implementation lists can not be nested like the
following but the reader would interpret this as a bullet list with the
first item being a numbered list.
```
- + This is not a list
```
2. The specification describes how URIs automatically becomes links.
Unfortunately as is often the case, their definitiong of URI is not
clear. I tried three solutions but was unsure about which to adopt.
* Using isURI from Network.URI, this matches far too many strings and is
therefore unsuitable
* Using uri from Text.Pandoc.Shared, this doesn't match all strings that
the reference implementation matches
* Try to simulate the regex which is used in the native code
I went with the third approach but it is not perfect, for example
trailing punctuation is captured in Urls.
|
|
|
|
Closes #1452. Added test.
|
|
Of course, we can't include structure in the code block, but
this way we at least preserve the text. Closes #1449.
|
|
|
|
|
|
sections."
This reverts commit 2a46042661a088096ac54097db5cd3674438bb63.
|
|
They were previously numbered, starting from the previous numbered
section, which was wrong.
|
|
Or a blockquote or header. Closes #1013.
|
