OrangeToucan
OrangeToucan
I had always imagined they'd be transcribed as-is using ASCII art. I've counted the width of some of them and they fit within the 70 character width. I suppose it...
Asking may be best but I don't know any blind people myself.
And other books (I assume the goal is to work on preserving them all?) have things such as footnotes, which are also not directly supported in GitHub's version of Markdown.
Page numbers are really only useful with a printed book though. They're not so useful for an online copy which can just link to sections from a table of contents....
Finishing the transcription in GitHub's version of Markdown and then returning to the language question means that some formatting & style decisions will have already been made (like the table...
Maybe Pandoc's version of markdown would work? http://pandoc.org/MANUAL.html#pandocs-markdown It seems very similar to GitHub's version of Markdown. I imagine it would require little to no changes to the current stuff,...
With Sphinx you can do http://blockdiag.com/en/ which sort of touches on issue #19 for the diagrams. The downside is that moving to Sphinx would mean re-writing everything?
If HTML can be included in Markdown as you mention then that perhaps solves both problems, from pull request #21 and from issue #19. Diagrams can be made with a...
This sound interesting, yes.