| Age | Commit message (Collapse) | Author |
|
Not technically an API change, since these are still unreleased.
Remove the `ExtensionsConf` in the return value, and added an 'ExtensionsDiff'
parameter.
|
|
T.P.Extensions [API change]:
+ Add CustomExtension constructor to Extension.
+ Remove Bounded, Enum instances for Extension.
+ Add `extensionsToList` function.
+ Revise `readExtension` so it can handle CustomExtension, and so
that it returns a Text rather than Maybe Text.
+ Add `showExtension`.
T.P.Format:
+ Revise error checking to handle CustomExtension.
|
|
`SOURCE_DATE_EPOCH` environment variable if set. (`getTimestamp` was
already sensitive.) This ensures that EPUB builds are reproducible.
Closes #7093.
|
|
This was only used in one place, and can be replaced with simpler
code.
|
|
|
|
This is just `nubOrd` from Data.Containers.ListUtils.
|
|
This is just a synonym for Bifunctor.first.
|
|
|
|
|
|
This new module exports `pandocVersion` and `pandocVersionText`,
which are no longer exported from Text.Pandoc.Shared. [API change]
Also, we now set the `pandoc-version` variable centrally rather
than in the writers. One effect is the man writer now emits
a comment with the pandoc version (this was intended before,
judging from the template, but it didn't happen because the
vairable wasn't set).
|
|
These are now exported by Text.Pandoc.URI, and removing
them from Shared helps make module structure more straightforward.
|
|
|
|
strict and lazy ByteString. [API change]
|
|
|
|
This reverts commit e5fbddd3b6c0c7a3b76b313edbe55242e3b138fc.
|
|
This reverts commit 20492d523c8324e36781cfbbc8092c796f94b151.
|
|
This reverts commit eff82cfe4de44a111250ce9ce3ecee2fd4d99924.
|
|
We previously avoided generating a duplicate with another automatically
generated identifier; now we also avoid duplicates with explicit
identifiers that occur before the header for which an identifier
is being generated. (Collisions are still possible for identifiers
that occur after the header.)
T.P.Shared: `makeSections` is also modified so it doesn't give
bad results when the enclosing Div has a different identifier
from the header, as may now happen.
|
|
[API change]
Use this in the HTML reader to register identifiers to avoid
duplicates created by `auto_identifiers`.
|
|
with `auto_identifiers`.
Closes #8383.
|
|
This reverts commit 1e7b57e1e888575ec772fa30381a9edc9577a406.
|
|
Henceforth we just use `PandocParseError`.
T.P.Parsing now exports `fromParsecError`, which can be used
to turn a parsec ParseError into a regular PandocParseError
(the appearance to the user should be unchanged in every case).
[API change]
Closes #8382.
|
|
Closes #8383.
Previously when converting HTML with headings nested under
section elements, pandoc would produce HTML div tags and
a span with an identifier duplicating the one on the div.
It seems better just to omit the superstructure of section
divs, so that's what this commit does, yielding more
normal MediaWiki output.
|
|
|
|
[API change]
|
|
We were exporting Parser, ParserT as synonyms of Parsec, ParsecT.
There is no good reason for this and it can cause confusion.
Also, when possible, we replace imports of Text.Parsec with
T.P.Parsing. The idea is to make it easier, at some point,
to switch to megaparsec or another parsing engine if we want to.
T.P.Parsing new exports: Stream(..), updatePosString, SourceName,
Parsec, ParsecT [API change].
Removed exports: Parser, ParserT [API change].
|
|
Also a small performance optimization.
Closes #8380.
|
|
|
|
Custom writers can define a default template via a global `Template`
function; the data directory is no longer searched for a default
template.
Writer authors can restore the old lookup behavior with
``` lua
Template = function ()
local template
return template.compile(template.default(PANDOC_SCRIPT_FILE))
end
```
|
|
This implementation would allow us (if we wanted) to add
an extensible Ext_custom Text constructor.
|
|
|
|
Rolls back 0ab014ed1e5890e338792fab98aecc45cd889f99.
We don't need this because we aren't needing to print the Lua
version in options any more; we're handling `--version` now at
the pandoc-cli level.
|
|
Like custom readers, like writers, can define the set of supported
extensions by setting a global. E.g.:
``` lua
reader_extensions = {
smart = true,
citations = false,
}
```
|
|
The default template of a custom writer `/path/to/my-writer.lua` is
expected in the `templates/default.my-writer.lua` data file. Note that
templates are *not* applied automatically to the output of custom
writers; custom writer authors must ensure that the template is applied
if one is present in the writer options.
Closes: #8137
|
|
The function `getDefaultTemplate` no longer splits off extension
modifers from the given format, as that conflicts with using custom
writers as formats. Haskell library users should use `getDefaultTemplate
<=< (fmap formatName . parseFlavoredFormat)` if the input format can
still contain extensions. The same is true for `compileDefaultTemplate`,
which calls `getDefaultTemplate` internally.
|
|
|
|
Custom writers can define the extensions that they support via the
global `writer_extensions`. The variable's value must be a table with
all supported extensions as keys, and their default status as values.
E.g., the below specifies that the writer support the extensions `smart`
and `sourcepos`, but only the `smart` extension is enabled by default:
writer_extensions = {
smart = true,
sourcepos = false,
}
|
|
So far, `orgStateLastPreCharPos` wasn't updated appropriately after each
parsing to native Str (by the parser `str`). In addition to solving
this, the guard `notAfterString` in `emphasisStart` is removed to allow
emphasis after Str at the first place.
|
|
|
|
|
|
Previously we got two separate `class` attributes in the `p`
tag. Closes #8363.
|
|
The functions now take a `FlavoredFormat` instead of a text argument.
|
|
The module provides functions and types for format spec parsing and
processing.
The function `parseFormatSpec` was moved from Text.Pandoc.Extensions to
the new module and renamed to `parseFlavoredFormat`. It now operates in
a PandocMonad and is based on the updated types.
|
|
The new error is used to report problems with input or output format
specifications.
The use of PandocAppError is now limited to code in T.P.App and
T.P.Citeproc.
|
|
The function tries to read an extension from a string.
|
|
The writer uses features from the longtable package to define the table
foot. Furthermore, the table's bottom rule is now part of the foot,
where it previously was given as part of the body.
|
|
`doc-biblioentry` -> `listitem`
`doc-bibliography` -> `list`
Closes #8354.
|
|
Closes: #8352
|
|
|
|
|