| Age | Commit message (Collapse) | Author |
|---|
|
|
|
[API change]
|
|
New input format: endnotexml
New reader module: Text.Pandoc.Readers.EndNote, exporting
readEndNoteXML. [API change]
This reader is still a bit rudimentary, but it should get
be good enough to be helpful.
|
|
See #7757.
|
|
See #7798.
|
|
Attribute key-value pairs are marshaled as AttributeList, i.e., as a
userdata type that behaves both like a list and a map. This allows to
preserve the order of key-value pairs.
Closes: #7489
|
|
This allows for some code simplification and improves stability.
|
|
Fixes: #7871
|
|
If a file path does not exist relative to the working directory, but
it does exist relative to the user data directory, and it exists outside
of the user data directory, do not read it. This applies to readDataFile
and readMetadataFile in PandocMonad and, by extension, any module that
uses these by passing them relative paths.
|
|
As an example, prior to this commit, "../../file" would evaluate to
"file", when it should be unchanged.
|
|
to a beamer frame, using the frameoptions attribute.
Updated manual.
See #7869.
|
|
Closes #7869.
|
|
For some reason we were skipping arbitrary blocks before `\item`.
This is now changed to "skip whitespace and comments."
|
|
Closes #7863.
|
|
Adding a pair of braces around the second argument of `\def`
prevents LaTeX from an emergency stop with: Closes #6096.
```
pandoc -f markdown -o test.pdf
\newif\ifepub
\epubtrue
\ifepub
hi
\fi
^D
```
|
|
If files specified with `--metadata-file` are not found in the working
directory, look in `$DATADIR/metadata`.
Expose new `readMetadataFile` function from Text.Pandoc.Class
[API change].
Expose new `PandocCouldNotFindMetadataFileError` constructor for
`PandocError` from Text.Pandoc.Error [API change].
Closes #5876.
|
|
This was causing serious problems with `newif` commands.
See #6096. And it didn't seem to make any difference for
the tests; I assume that, unless there's some untested
behavior, this is something that has now become unnecessary.
|
|
If speaker notes (a Div with class 'notes') occur right
after a section heading, but above slide level, the
resulting `\note{..}` caommand should not be wrapped in
a frame, as that will cause a spurious blank slide.
Closes #7857.
|
|
With the new (default) line wrapping of HTML, in
conjunction with the default CSS which includes
`code { whitespace: pre-wrap; }`, spurious line
breaks could be introduced into inline code.
Closes #7858.
|
|
Otherwise we'll sometimes get two copies of things, one
from the `citationPrefix` or `citationSuffix` and another
from the embedded fallback text.
When there is no fallback text, we'll get no content.
However, it really isn't an alternative to just rely
on the result of running `query` on the embedded `Citation`s;
this will result in a jumble of text rather than anything
structured.
Closes #7855.
|
|
as FieldInfo.
|
|
So far this just adds a constructor for FieldInfo;
we'll need to adjust the rest of the reader code to
parse the JSON and do something with it.
See #7840.
|
|
If a table has explicit column width information *and* the
content extends beyond the `--columns` width, we need to
adjust the widths of the pipe separators to encode this width
information.
Closes #7847.
|
|
Adjacent docx tables need to be separated by an empty paragraph. If
there's a RawBlock between tables which renders to nothing, be sure to
still insert the empty paragraph so that they will not collapse
together.
Fixes #7724
|
|
|
|
Previously we would (also) search the default user data directory
for a defaults file, even if a different user data directory
was specified using `--data-dir`. This was a mistake; if
`--data-dir` is used, the default user data directory should
not be searched.
|
|
If the XDG data directory is not defined (e.g. because
it's not supported in the OS or HOME isn't defined), we
return the empty string instead of raising an exception.
Closes #7842.
|
|
PagedJS is a polyfill and supports the Paged Media standards by the W3C.
<https://www.pagedjs.org/>
|
|
The checklist syntax (similar to `task_list` in markdown) seems to be
an asciidoctor-only addition.
Co-authored-by: ricnorr <[email protected]>
|
|
The V font is defined conditionally, so that it renders
like CB in output formats that support that, and like B
in those that don't (e.g. the terminal).
We could just redefine C, but this would affect code
blocks, too, and putting them all in boldface looks ugly,
I think.
Possible drawback: fragments created by pandoc's man
writer will presuppose a nonstandard V font.
Closes #7506.
Supersedes 253467a549dcc22384be96041fd6f886c4a7a935.
|
|
Closes #7506.
This also allows us to get rid of some special casing
on definition lists that ensured that options in code
spans would be boldface. (If this change is ever reverted,
we'll need that again.)
|
|
Make the first param of `tokenize` a SourcePos instead of
SourceName, and use it instead of `totoks`.
|
|
This line signals the end of a YAML document.
This restores the behavior we got with HsYaml.
yaml complains about content past this line.
See https://github.com/jgm/pandoc/issues/4627#issuecomment-1012438765
|
|
with numerical styles that use superscripts (e.g.
american-medical-association.csl), as well as with
note styles. The default setting of `notes-after-punctuation`
is true for note styles and false otherwise.
This restores a behavior of pandoc-citeproc that wasn't properly
carried over to Citeproc.
Closes #7826.
See also jgm/pandoc-citeproc#384.
|
|
Make sure that we only create one bullet per list item in docx. In
particular, when a div is a list item, its contained paragraphs will
now no longer wrongly get individual bullets.
This is accomplished by making sure that for each list, we only use
the associated numId once. Any repeated use would add incorrect
bullets to the document.
Closes #7689
|
|
and other similar tags. This seems to accord with what
the docbook toolchain does.
Closes #7821.
|
|
|
|
The commit 7a9832166e36f77402d5e0259647e9f5c7ba4e58
had the effect that blank lines would be collapsed
in HTML attributes.
We also roll back a change that collapsed multiple
spaces into one.
|
|
* Add localized title "abstract", unless `abstract-title` variable
is set.
* Add `abstract-title` div to abstract CSS.
* Move abstract CSS out of CSL conditional.
* Ensure that abstract is aligned left but indented on all sides.
* Use smaller font for abstract.
Improves #7588.
|
|
This adds support for alphabetical lists in org by enabling the
extension Ext_fancy_lists, mimicking the behaviour of Org Mode when
org-list-allow-alphabetical is enabled.
Enabling Ext_fancy_lists will also make Pandoc differentiate between the
delimiters of ordered lists (periods or closing parentheses). Org does
this differentiation by default when exporting to some formats (e.g.
plain text) but does not in others (e.g. html and latex), so I decided
to copy Pandoc's markdown reader behaviour.
|
|
or other non-paragraph content.
Closes #7810.
|
|
T.P.Writers.Shared `endsWithPlain` now returns True if
the list ends with a list which ends with a Plain.
See #7810.
|
|
See #7810 (2).
|
|
Addresses issue 2 from #7810.
|
|
The code to do this was apparently copied over from the RST
writer, but these blank lines aren't necessary or desirable
in org. See #7810 comment 3.
|
|
Closes #7819 (problem with spaces in image filenames when creating
PDFs).
|
|
We want to do a case-insensitive comparison when parsing
locators, so that e.g. both `Chap.` and `chap.` work.
Previously we lowercase terms when doing the lookup,
but they weren't lowercased in the map itself, which
led to locator-detection breaking for German (where the
terms have uppercase letters).
See
https://groups.google.com/d/msgid/pandoc-discuss/1dd44886-7b79-4e5f-97ec-57b91113df36n%40googlegroups.com
|
|
|
|
Closes #7813.
|
|
This complements #7806 by supporting writing Org ordered lists that
start at a specific number.
|
