quarto-dev / quarto-dev/quarto-cli

Quarto should incorporate Asciidoc rendering facilities

Open
#4,003 18 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Bug description

Quarto is a far bigger platform than R markdown. But, this is limited to only rendering markdown or its flavours with R or the like code sequences only.

Asciidoc is simpler and has only one flavour with distinct features for writings very good books, articles and what not?

Therefore, I request its developer's to incorporate rendering facilities for Asciidoc documents to be written in Asciidoc quarto.

First, I raised this issue at RStudio.com community forum. But, andresrcs (the Sustainer) suggested me to raise Quarto related issues at this forum.

So, I would like to clarify it further that Quarto does provide one format option of "Asciidoc". But, that feature, in fact converts the document written in Quarto Markdown (Pandoc Markdown) to Asciidoc format with asciidoc codes, which should be rendered elsewhere. And what I mean is that the input file of quarto document should contain asciidoc codes, which can be rendered by Quarto to an output file, not with asciidoc codes, but a file rendered into html, pdf or docx.

To be more clear, what I am expecting from Quarto is that we should be able to write the document, along with R scripts in RStudio in .asciidoc (or .adoc) codes, instead of Rmarkdown or Markdown, which could be rendered to html, pdf, docx or docbook.

Wishing all the best hopefully,

Dr. A.K Singh

Checklist
  • Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
  • Please format your issue so it is easier for us to read the bug report.
  • Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
  • Please document the operating system you're running. If on Linux, please provide the specific distribution.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the requested .asciidoc or .adoc input alongside the single .qmd reproducible-example checklist. Determine how Quarto should render Asciidoc containing R scripts to HTML, PDF, DOCX, or DocBook rather than converting Quarto Markdown to Asciidoc. Done means the requested input and output workflow is supported and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown, r
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.