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

[WIP] adding HARKmanual in markdown to RTD #500

Closed
wants to merge 2 commits into from

Conversation

sbenthall
Copy link
Contributor

Getting the HARKmanual into sphinx/readthedocs, with markdown source, as per #409.

For me, simply converting the LaTeX version of the manual into markdown with pandoc resulted in a corrupted markdown file that could only be partially read by Sphinx.

So I've started working at a different way: using pandoc to turn the available, complete HARKmanual.html into a markdown file.

The generated markdown has [line breaks in its image tags](https://github.com/sphinx-doc/sphinx/issues/6797). I've worked these out by hand.

There are still an unknown number of issues preventing the file from being parsed and formatted by sphinx.

@sbenthall sbenthall changed the title adding HARKmanual in markdown to RTD. Needs more hand-editing. #409 [WIP] adding HARKmanual in markdown to RTD Feb 9, 2020
@llorracc
Copy link
Collaborator

llorracc commented Feb 9, 2020 via email

@sbenthall
Copy link
Contributor Author

sbenthall commented Feb 9, 2020

Chris, I was going on the discussion on issue #409, which was active in November.

There, you persuaded me that it's best to use markdown for a temporary RTD version of the manual.
#409 (comment)

@sbenthall
Copy link
Contributor Author

With the manual now hosted online at

http://econ-ark.github.io/HARK/Documentation/HARKmanual/

we seem to have punted on the problem of getting the manual into either Markdown or RST into RTD.

Unless somebody would like to reopen that discussion, I'll close this PR soon to clean up the issue tracker.

@llorracc
Copy link
Collaborator

I know you made a link somewhere to the new manual. If you have verified that there are no references anywhere to the markdown version anywhere else, go ahead and close this.

PS. Eventually probably we should have a unified system/structure for the documentation, rather than having a LaTeX -> HTML -> gh-pages procedure for HARKmanual and something else (RST or Markdown) for the rest. But I see no urgency to that.

@sbenthall sbenthall closed this Feb 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants