| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|\
| |
| | |
LaTeX writer: Make Horizontal Rules more flexible
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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}"
```
|
|\ \
| | |
| | |
| | | |
jlduran-ugly-tables
|
| | |
| | |
| | |
| | | |
See: http://tex.stackexchange.com/questions/34971
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- [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 `\\`.
|
|\ \
| | |
| | | |
Plain cells
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
|\ \
| |/
|/| |
DokuWiki cleanup
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Docx writer: write track changes.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
These have default authors and dates of "unknown" and timestamp-zero,
respectively.
|
|\ \
| |/
|/| |
Org exampleLine parser accepts indented example lines!
|
|/
|
|
| |
the start of the line.
|
| |
|
| |
|
|
|
|
|
|
| |
Build dependencies of the trypandoc executable are required, regardless of the
trypandoc flag was set to either True or False. Correct package description
to make them truly optional.
|
|
|
|
| |
Closes #1559.
|
|
|
|
|
| |
Previously C:\foo.js was being wrongly interpreted as a URI.
Closes #1558.
|
|\
| |
| | |
Txt2Tags reader: Header is now parsed only if standalone flag is set
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
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`.
|
| | |
|
| |
| |
| |
| | |
This addresses the split of network and network-uri.
|
| | |
|
|/ |
|
|
|
|
| |
Closes #1549. Thanks to lemzwerg.
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
| |
| |
| |
| | |
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).
|
| |
| |
| |
| |
| |
| |
| |
| | |
Two points here: (1) We're going bottom-up, from styles not based on
anything, to avoid circular dependencies or any other sort of
maliciousness/incompetence. And (2) each style points to its
parent. That way, we don't need the whole tree to pass a style over to
Docx.hs
|
| | |
|
| |
| |
| |
| |
| | |
This will make it easier to build the style map from the bottom up (to
avoid any infinite references).
|
| |
| |
| |
| | |
Just discards info at the moment, so at least it works the same.
|
| |
| |
| |
| |
| |
| | |
We want to be able to read user-defined styles. Eventually we'll be able
to figure out styles in terms of inheritance as well. The actual
cascading will happen in the docx reader.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|