Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pandoc support #4987

Closed
SilleBille opened this issue Dec 11, 2018 · 7 comments
Closed

Pandoc support #4987

SilleBille opened this issue Dec 11, 2018 · 7 comments
Labels
Feature New feature Needed: design decision A core team decision is required

Comments

@SilleBille
Copy link

SilleBille commented Dec 11, 2018

Details

  • Read the Docs project URL:
  • Build URL (if applicable):
  • Read the Docs username (if applicable):

Expected Result

This request may be turned down. But, giving my shot

I'm pretty new to readthedocs and I was impressed by the features. Thanks for this awesome project!
While researching, I came across pandoc which isn't supported by readthedocs (or at least, I don't find it in the tutorial).

I am trying to achieve the following:
A set of markdown files that:
a. is generated in the form of linux man pages
b. is generated into HTML

With the help of pandoc, I'm able to achieve the above 2. However, I am not able to host it on readthedocs. Is there a possiblity to add support for pandoc?

Actual Result

No way to build with pandoc and deploy to readthedocs

@humitos humitos added Feature New feature Needed: design decision A core team decision is required labels Dec 11, 2018
@humitos
Copy link
Member

humitos commented Dec 11, 2018

Hi @SilleBille! Read the Docs currently achieve 2 -- generate HTML from Markdown.

Also, Sphinx -- the builder that RTD uses -- has the ability to generate man pages but we are not doing that currently. Although, there is an issue already open for that #4458

Would it be enough for you to enable man page generation for Sphinx builder?

@SilleBille
Copy link
Author

SilleBille commented Dec 11, 2018

@humitos thanks for the reply! To summarize my needs with a simplified diagram:

image

  • javadoc is generated using the official javadoc package
  • man pages are currently processed using pandoc
  • Documentation can also be converted to HTML by pandoc. Using sphinx/mkdocs for just this workflow makes the pipeline complicated.

I want to keep the pipeline as simplified as possible.

To answer your question, though sphinx supports all the above, as per your previous comment, it seems rtfd doesn't provide support for man pages? Yes, I can switch over to sphinx if man pages can be generated in both roff and HTML formats

@humitos
Copy link
Member

humitos commented Dec 11, 2018

Thanks for the explanation.

I think this is a very fair feature request considering that we support sphinx and mkdocs. Why not pandoc also?

I don't have too much experience with pandoc (I've only used it to convert files between formats and it's great) and I don't know how much complicated it would be, but I'm sure that it's not an easy feature to add to our platform. On the other hand, considering our current roadmap, I don't think that this will happen soon, unfortunately.

I marked this issue as Needed: design decision so other core developers can write their thoughts here.

To answer your question, though sphinx supports all the above, as per your previous comment, it seems rtfd doesn't provide support for man pages? Yes, I can switch over to sphinx if man pages can be generated in both roff and HTML formats

Currently, we are not generating man pages. So, I'd say that it's not supported. The discussion for this will happen in #4458

@SilleBille
Copy link
Author

@humitos Thanks for an optimistic reply. The main concern for me is that I don't want my team to follow different formats to write down the documentation. I want them to follow consistent formatting across all the docs they write.

@humitos
Copy link
Member

humitos commented Jan 23, 2019

I'm assuming that we won't implement this at a Read the Docs level as another builder for the documentation. Instead, we will probably put more effort on allowing #1083, so the user can build the documentation using the custom workflow needed and then upload the docs already built.

@humitos
Copy link
Member

humitos commented Apr 27, 2019

I'm going to close this issue since it's not going to happen soon, unfortunately. We can revisit later if we consider valuable to add another builder. Thanks!

@Jacob-Stevens-Haas
Copy link

Jacob-Stevens-Haas commented Apr 7, 2023

Adding a link here because I found this issue before the relevant, older one, but it looks like readthedocs has pandoc support already: #579 (comment).

Sphinx uses a conf.py, which "itself can be an extension; for that, you only need to provide a setup() function in it". (ref1, ref2). This can include calls to the pandoc python wrappers..

If you need a different version of pandoc binaries, you can specify it in your readthedocs.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature Needed: design decision A core team decision is required
Projects
None yet
Development

No branches or pull requests

3 participants