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

Should the book be in Markdown? Is LaTeX too scary? #2

Open
tlhunter opened this issue Aug 9, 2014 · 3 comments
Open

Should the book be in Markdown? Is LaTeX too scary? #2

tlhunter opened this issue Aug 9, 2014 · 3 comments
Labels

Comments

@tlhunter
Copy link
Owner

tlhunter commented Aug 9, 2014

It might be beneficial to convert the content of the book to Markdown, then implement some sort of Markdown to LaTeX converter, allowing people to write content in a familiar language.

The only problem is the book loses it's awesome formatting and inter-content hyperlinking.

@rshipp
Copy link

rshipp commented Aug 12, 2014

You might consider reStructuredText as a sort of middle ground. It's more familiar and "Markdownish" than LaTeX, but would allow you to keep the inter-content hyperlinking and formatting as well.

@mmontone
Copy link

If you use reStructuredText and Sphinx you can get very high-quality nice looking output, both in HTML and PDF. I'm using it for documenting my projects.

@xiaohanyu
Copy link

Hi, I'm reading your book to get some feel about how to design my first restful api and I found it really helps and awesome.

For markdown, I think it is really a better choice over LaTeX. and I recommend pandoc(http://johnmacfarlane.net/pandoc/) for you. Pandoc is really awesome and it converts everything to anything.

If you want to do this convert, I can provide some help, I'm sure I'm an expert in this field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants