Age | Commit message (Collapse) | Author | Files | Lines |
|
* Headers with "unnumbered" attribute are not numbered.
(Nor do they cause an increment in running numbering.)
* Section numbers now work properly, even when there is
material before the first numbered section.
|
|
Changed toChunks to toChapters.
|
|
With this change, `--number-sections` won't work. This will
be fixed later.
|
|
We add 0s to the end of the list if it's shorter than needed.
|
|
Also `writerNumberFrom` -> `writeNumberOffset`.
The offset is a list of numbers (0 by default).
These are added to the section, subsection, etc.
numbers that would have been generated automatically.
|
|
* If we need to add an initial section, make it unnumbered.
* Don't add extra space before unnumbered section titles in TOC.
|
|
|
|
|
|
In this case \title, \subject are used instead of \chapter,
\section.
|
|
Otherwise we get LaTeX errors.
|
|
Previously the numbering restarted from 1 in each chapter
(with `--number-sections`), though the numbers in the table
of contents were correct.
Note that this fix is a bit hackish and possibly fragile:
if the rendering of section numbers in HTML changes in the
future, it may break. But it works, without needing
changes in other modules.
|
|
|
|
Starred variants of section commands used when header
has "unnumbered" class.
|
|
Note: The attributes go on the enclosing section or div
if `--section-divs` is specified.
Also fixed a regression (only now noticed) in html+lhs output.
Previously the bird tracks were being omitted.
|
|
Unnumbered sections get [] for their section number.
So far only the HTML writer has been adjusted to be sensitive
to this.
If we keep this change, all the writers will need to be changed
either (a) to directly check for the "unnumbered" class, if they
do section numbering themselves, or (b) to check for a null section
number, if they use hierarchicalize.
|
|
|
|
Sec now includes a field for Attr rather than just String
(the identifier).
Note, this is an API change.
|
|
This reverts commit d46f434d4b8906ae3b983e568549213de94fd1a2.
|
|
* Citations will work in markdown even if `--biblio` isn't
specified. Note: this may cause unexpected behavior for people
who use strings of the form `@foo` that are not citations!
* If `--biblio` isn't used, the markdown writer will write markdown
citations rather than CSL-rendered citations.
* This means, for example, that you can do `pandoc -f latex -t markdown`
and convert biblatex or natbib citations into pandoc citations.
|
|
Closes #725.
|
|
Thanks to Nick Bart for the suggestion of using @{}.
|
|
These are no longer used in the default template, since we use
titleblock, but we set them anyway for nondefault template users.
|
|
Closes #721.
Also fixed whitespace in lhs tests.
|
|
Previously we also checked for a null title, but this
test fails for links produced by citeproc-hs in bibliographies.
So, if the link has a title, it will be lost on conversion
to an autolink, but that seems okay.
|
|
|
|
|
|
blaze-html/blaze-markup-0.5 has Text.Blaze.Html.Renderer.Utf8
whereas blaze-html-0.4 has Text.Blaze.Renderer.Utf8.
So this needs to be conditional on the version for pandoc
still be with blaze-html-0.4.x
|
|
Closes #714.
|
|
This contains a space-separated list of citation IDs.
|
|
* RTF writer: Export writeRTFWithEmbeddedImages instead of
rtfEmbedImage.
* Text.Pandoc: Use writeRTFWithEmbeddedImages for RTF.
* Moved code for embedding images in RTF out of pandoc.hs.
|
|
if --listings is used.
Closes #704.
|
|
|
|
|
|
|
|
The previous default was to use `<q>` tags in HTML5.
But `<q>` tags are also valid HTML4, and they are not very
robust in HTML5. Some user agents don't support them,
and some CSS resets prevent pandoc's quotes CSS from working
properly (e.g. bootstrap). It seems a better default just
to insert quote characters, but the option is provided for
those who have gotten used to using `<q>` tags.
|
|
Revises 1a4b47e93368bfbd31daccdfedbd9527ee740201
|
|
* In markdown reader, add a '\1' character to the beginning
of the title of an image that is alone in its paragraph,
if implicit_figures extension is selected.
* In writers, check for Para [Image alt (src,'\1':tit)] and treat
it as a figure if possible.
* Updated tests.
This is a bit of a hack, but it allows us to make implicit_figures
an extension of the markdown reader, rather than the writers.
|
|
We now (a) use anonymous links for links with inline URLs, and
(b) use an inline link instead of a reference link if the
reference link would require a label that has already been
used for a different link.
Closes #511.
|
|
Closes #678.
|
|
|
|
Previously linebreaks weren't supported in RST, since RST
has no native linebreak construct.
|
|
|
|
This avoids a clash with highlighting-kate's macros, which
redefine | as a short verbatim delimiter. Thanks to
Björn Peemöller for raising this issue.
|
|
This seems to match the spacing of ~ exactly.
|
|
Since `~` spaces after a line break are just ignored.
Closes #687.
|
|
We need to ensure that all headers have attributes, since
this is no longer guaranteed by hierarchicalize.
Explicitly given headers remain the same.
|
|
|
|
* Shared now exports fetchItem (instead of getItem) and openURL
* fetchItem has different parameters than getItem and includes
some logic formerly in the ODT and Docx writers
* getItem still used in SelfContained
|
|
These images are now downloaded instead of being ignored (as
used to happen in the docx reader) or causing an error (as
used to happen in the odt reader).
|
|
Avoid reading image files again when we've already processed them.
|