| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Still to do: prefix, suffix, locator.
|
|
|
|
instead of readEndNoteXMLReferences. This is the function
we'll need in the docx reader.
We still need to implement locator, prefix, and suffix.
|
|
|
|
New input format: endnotexml
New reader module: Text.Pandoc.Readers.EndNote, exporting
`readEndNoteXML` and `readEndNoteXMLReferences`. [API change]
This reader is still a bit rudimentary, but it should get
be good enough to be helpful.
|
|
These are supported in the same way as Zotero citations,
using the same code. As with Zotero, enable the `citations`
extension on `docx` to parse these as native citations.
Closes #7840.
|
|
Previously we used System.FilePath's isRelative to
determine when paths are relative (since absolute
paths need to get a new name based on the sha1 hash).
But this has an OS-specific behavior and actually
returns True on Windows for paths like `/media/file.png`.
This ought to fix #7881.
|
|
This reverts commit 3dcb526b9b084976bfb5ef2f02a6bf009fd78750.
|
|
PReviously if the directory argument ended in slash,
we'd get a doubled slash in the path. This may help
with #7881.
|
|
Bibliographic data embedded in citation items is added
to the `references` metadata field.
Closes #7840.
|
|
|
|
When enabled, Zotero citations are parsed as native pandoc
citations. (When disabled, the Zotero-generated citation
text is passed through as regular text.) In addition, the
Zotero-generated bibliography is suppressed.
Locators still need some work.
|
|
This gives us what we ned for #7840, except adding
to the references in metadata.
|
|
This fixes problems with --webtex and markdown output,
when display math starts or ends with a newline.
Closes #7892.
|
|
|
|
- Add docxReferences to state, so we can accumulate
references for metadata.
- Add a clause for ZoteroItem to parPartToInlines'.
So far it doesn't do anything except add a surrounding Cite element.
See #7840.
|
|
|
|
Closes #7883.
|
|
|
|
This reverts commit 545c0911aa5d7d91280c5213c6d57b3e634ef1e5.
Fixes regression in 2.17.1.
The original commit was completely misguided, and caused
problems finding defaults files in the default user data
directory.
|
|
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.
|
