| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This allows us to emphasize at the beginning of a new paragraph (or, in
general, after blank lines).
|
|
There could be new top-level headers after making lists, so we have to
rewrite links after that.
|
|
When users number their headers, Word understands that as a single item
enumerated list. We make the assumption that such a list is, in fact, a header.
|
|
Previously we included it in the spine with `linear="no"`, leading
to odd results in some readers.
Closes #1593.
|
|
Closes #1595.
|
|
|
|
Item fix
|
|
Added docTitle'.
|
|
Because of the built-in line skip, LaTeX can't handle a section header
as the first element in a list item. (To be precise, it can't handle it
if the list immediately follows a section header, but the instance is
rare enough that we can afford to be a bit more general). This puts a
non-breaking space before the header to solve this problem. We won't see
this space, since the header skips a line before printing anyway.
The output is ugly in LaTeX and this structure seems like it should
probably be avoided. But it is valid HTML and native pandoc, so we
should have some sort of typesettable representation in LaTeX.
|
|
Previously text that ended a div would be parsed as Plain
unless there was a blank line before the closing div tag.
Test case:
<div class="first">
This is a paragraph.
This is another paragraph.
</div>
Closes #1591.
|
|
It is not supported and epubcheck complains.
|
|
Closes #1590.
|
|
Also cleaned up crufty code and added tests.
|
|
Closes #1566.
|
|
We can now handle all different alignment types, for simple
tables only (no captions, no relative widths, cell contents just
plain inlines). Other tables are still handled using raw HTML.
Addresses #1585 as far as it can be addresssed, I believe.
|
|
See #1582.
|
|
Conflicts:
src/Text/Pandoc/Writers/Docx.hs
|
|
DokuWiki writer: Backslash newlines in table cells
|
|
Write out strings in table cells with backslash linebreaks in place of
newlines. We also want to remove the first two spaces of an indent in lists.
|
|
LaTeX writer: Make Horizontal Rules more flexible
|
|
jlduran-ugly-tables
|
|
See: http://tex.stackexchange.com/questions/34971
|
|
This makes to docx reader's native output fit with the way the markdown
reader understands its markdown output. Ie, as far as table cells go:
docx -> native == docx -> native -> markdown -> native
(This identity isn't true for other things outside of table cells, of
course).
|
|
Currently, pandoc has hard-coded the following in order to make horizontal
rules in LaTeX:
```hs
"\\begin{center}\\rule{3in}{0.4pt}\\end{center}"
```
Which is fine, but does not allow customizations. It also does not take into
consideration the current line width.
I'm proposing this change:
```diff
@@ In Writers/LaTeX.hs:
-"\\begin{center}\\rule{3in}{0.4pt}\\end{center}"
+"\\begin{center}\\rule{0.5\\linewidth}{\\linethickness}\\end{center}"
```
|
|
- [x] Fix a bug introduced in 66378062b622b0815a1a2ddce5d557e3ad13330c, which
causes the table caption to repeat across all pages
- [x] Address the issues discussed
[here](https://groups.google.com/forum/#!msg/pandoc-discuss/qMu6_5lYy0o/ZAU7lzAIKw0J)
regarding the extra vertical space.
- [ ] NOTE: This will cause multiline table cells to appear unpadded. See
http://tex.stackexchange.com/questions/34971
- [x] Use [`\tabularnewline`](http://tex.stackexchange.com/questions/78796)
instead of `\\`.
|
|
|
|
|
|
|
|
Docx writer: write track changes.
|
|
the start of the line.
|
|
|
|
|
|
These have default authors and dates of "unknown" and timestamp-zero,
respectively.
|
|
|
|
Closes #1559.
|
|
Previously C:\foo.js was being wrongly interpreted as a URI.
Closes #1558.
|
|
|
|
|
|
The header is now parsed as meta information. The first line is the
`title`, the second is the `author` and third line is the `date`.
|
|
|
|
Also, if page-progression-direction not specified in metadata,
don't include the attribute even in EPUB3; not including it is
the same as including it with the value "default", as we did before.
Closes #1550.
|
|
Docx reader: parsing styles
|
|
Previously a section like this would be enclosed in a paragraph,
with RawInline for the video tags (since video is a tag that can
be either block or inline):
<video controls="controls">
<source src="../videos/test.mp4" type="video/mp4" />
<source src="../videos/test.webm" type="video/webm" />
<p>
The videos can not be played back on your system.<br/>
Try viewing on Youtube (requires Internet connection):
<a href="http://youtu.be/etE5urBps_w">Relative Velocity on
Youtube</a>.
</p>
</video>
This change will cause the video and source tags to be parsed
as RawBlock instead, giving better output.
The general change is this: when we're parsing a "plain" sequence
of inlines, we don't parse anything that COULD be a block-level tag.
|
|
|
|
We no longer need the explicit lists since we're deriving them from the
ground up.
|
|
This is the only one so far. We'll add others as they show up.
|
|
We now no longer check against explicit styles.
|
|
We always favor an explicit positive or negative in a style in a
descendent, and only turn to the ancestor if nothing is set.
We also introduce an (empty) list of styles that are black-listed. We
won't check them. (Think underlines in hyperlinks).
|
|
Add row width to tables in Docx XML
|
|
Docx reader: Change behavior of Super/Subscript
|
