| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* Markdown writer now includes a blank line at the end
of the row in a single-row multiline table, to prevent it from being
interpreted as a simple table. Closes #4578.
* Markdown reader does a better job computing the relative width of
the last column in a multiline table, so we can round-trip tables
without constantly shrinking the last column.
|
|
Previously we used an odd mix of 3- and 4-space indentation.
Now we use 3-space indentation, except for ordered lists,
where indentation must depend on the width of the list marker.
Closes #4563.
|
|
|
|
This gives better results for styles that put ordered list
markers in boxes or circles.
Closes #4556.
|
|
|
|
|
|
|
|
* Use `\f[R]` rather than `\f[]` to reset. The latter
returns to the previous font, which gives unintended
results in some cases.
* Use `\f[BI]` and `\f[CB]` in headers, instead of `\f[I]` and `\f[C]`,
since the header font is automatically bold.
* Use `\f[CB]` rather than `\f[BC]` for monospace bold.
Closes #4552.
|
|
|
|
+ Create pdf anchor for a Div with an identifier.
+ Escape `/` character in anchor ids.
+ Improve escaping for anchor ids: we now use _uNNN_ instead of uNNN
to avoid ambiguity.
This is intended to help with #4515; however, in my tests, the
link to the reference does not seem to work. I'm not sure why.
|
|
Closes #4550.
|
|
> should be escaped only when it can start verse, i.e., at the beginning of the line.
|
|
|
|
|
|
|
|
Previously all links were turned into footnotes with unclickable URLs inside.
|
|
Closes: #4532
|
|
HorizontalRule corresponds to <hr> element in the default output
format, HTML. Current HTML standard defines <hr> element as
"paragraph-level thematic break". In typography it is often
represented by extra space or centered asterism ("⁂"), but since
FB2 does not support text centering, empty line (similar to extra space)
is the only solution.
Line breaks, on the other hand, don't generate <empty-line />
anymore. Previously line breaks generated <empty-line /> element
inside paragraph, which is not allowed. So, this commit addresses
issue #2424 ("FB2 produced by pandoc doesn't validate").
FB2 does not have a way to represent line breaks inside paragraphs.
They are replaced with LF character, which is not rendered by
FB2 readers, but at least preserves some information.
|
|
|
|
|
|
Issue #4527.
|
|
Only <p> and <empty-line /> are allowed in titles,
but <p> has the same type as an ordinary paragraphs.
Therefore, there is no need to remove emphasis from titles.
Also, don't intersperse paragraph with empty lines.
|
|
|
|
|
|
See https://github.com/melmothx/text-amuse/issues/39
|
|
It includes cases when they can be mistaken for footnotes
and links, as well as inside link description.
|
|
|
|
Since we're using mapM_ instead of mapM, we can get rid of the return
statement. We also don't need the `unless` statement anymore.
|
|
Closes #4489.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also reduced amount of <verbatim> tags in output to avoid escaping every "-" and word that ends in a full stop.
|
|
|
|
Test more cases when span has or hasn't anchor, class and contents in different combinations.
|
|
Separate spans may have different semantics, for example if spans indicate syllables in a word.
|
|
There were some artifact code blocks around from before
`reference-doc` functionality was implemented. This led to ignoring
the reference-doc in places. Though I fixed this, I kept the old
hacked-up functions instead of replacing them with
`parseXml` (imported from Writers.OOXML) which does this in a
consistent manner. This commit corrects that oversight.
|
|
|
|
This reverts commit 99fa850a37cc3e56b415754c70ea2d98da709584.
|
|
There were a few layouts where we were still just checking the built
in pptx doc, instead of the supplied reference doc.
|
|
This was causing headers to be misaligned when some templates were used.
|
|
even when structured titles are used.
This prevents spurious warnings about empty title elements.
Closes #4486.
|
|
We now pull the filtered blocks and speaker notes out at the top of
the `blocksToSlide` function, and then make SpeakerNotes into a
parameter of the `blocksToSlide'` subfunction. The output is the same,
but the logic should be easier to follow now.
|
|
We used to keep a map of the slideId-to-notes for each slide. Since we
now extract them at the slide level, this is overcomplicated, and we
can just extract them before converting a slide and then clear the
state after.
|
|
Previously, we had treated it as a `Maybe`. But there is no difference
between not having speaker notes and having empty speaker notes. So we
make the SpeakerNotes newtype into a monoid, and test for memptiness
instead of testing for Just/Nothing.
|
|
It leads to problems with round-trip test,
because aligned line blocks can't be read back.
|
