You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
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.
The text was updated successfully, but these errors were encountered: