Skip to content
#

pandoc

Here are 672 public repositories matching this topic...

nedvedikd
nedvedikd commented Apr 6, 2020

Hi,

I'm using pandoc (version 2.9.2.1) to convert documents to dokuwiki format.
I ran into a problem using this command:

pandoc input.html -f html -t dokuwiki -o output_dokuwiki.txt --preserve-tabs

Input:

<strong>bold</strong>
<em>italic</em>
<u>underline</u>

Output:

**bold** //italic// underline

Expected output:

**bol
gtaifu
gtaifu commented Mar 19, 2020

Thank the authors for their wonderful job at first! I really appreciate this extension and like it quite a lot. I am using it heavily to write docs. At the same time, I found the available documentation is a bit limited.

While I am trying to define my own style.css, I found that the documentation in this page only give s

nettoyoussef
nettoyoussef commented Oct 11, 2019

This is not an issue, but a recommendation.

I would like to suggest that in the docs available in the Rmarkdown book you include two examples in chapter 15 (parameterized reports):

  • passing parameters as raw markdown text for the parameterized reports.
  • setting the title using a parameter

This information is available in other parts of the book,

David96
David96 commented Feb 20, 2019

Hey,

so I usually use a format like that for my yaml frontmatter:

---
title: Some Title
author: me
date: 12.12.2018
toc: true
toc-own-page: true
nocite: "@*"
references:
- id: source1
  type: webpage
  URL: https://foo
  title: Some other title
- id: source2
  type: webpage
  title: Title
  URL: https://bar
---

That works perfectly fine using pandoc-citeproc. Now I w

alpianon
alpianon commented Jun 13, 2019

When using pandoc-crossref to generate, f.e., legal texts, if would be very useful to have a syntax to reference also section titles and not only section numbers, like f.e. as follows:

## Term and Termination {#sec:termination}

...

...as stated in @sec:termination ('@sec-title:termination'), there is...

in order to get the following output:

... as stated in Section 1.5 ('Ter

oscarcarlsson
oscarcarlsson commented May 9, 2015

When converting from markdown to LaTeX I noticed that an unsupported command was used in the itemize environment.

Given the following input (in Markdown):

Test:

 - One
 - Two
 - Three

The following LaTeX was produced:

Test:

\begin{itemize}
\tightlist
\item
  One
\item
  Two
\item
  Three
\end{itemize}

The \tightlist command is most likely from the memoir class which i

agitter
agitter commented Oct 19, 2017

As I noted in greenelab/meta-review#18, bioRxiv references show Cold Spring Harbor Laboratory instead of bioRxiv in the reference list. This is because the JSON file from CrossRef has "container-title":[].

I presume bioRxiv supplies the citation information for the DOI. Would it be worthwhile to contact them to see if we can correct the references by fixing the upstream data?

jongreig
jongreig commented May 17, 2019

I had a question about one part of your guide, though I don't know if this is pertinent specifically to Scrivomatic. I imported the compile/styles preset from your guide, and while it works well, for block quote-styled sections of my paper (e.g.), the prefixed > character in each block quote-styled paragraph gets escaped as \> . I currently have the 'escape characters' option set here:

<im

Improve this page

Add a description, image, and links to the pandoc topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the pandoc topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.