YES!
I would also love to see a publishing workflow that could render IPython Notebooks for print on dead trees.
I would also love to see a publishing workflow that could render IPython Notebooks for print on dead trees.
One thing I'm hoping to figure out is a way to transform IPython Notebooks into PDFs that satisfy my university's dissertation formatting guidelines (one inch margins, 12pt times, etc).
[1] https://github.com/ipython/ipython/tree/master/IPython/nbcon...
O'Reilly does use docbook internally as part of the toolchain, but asciidoc is coming into style as well. I've done most of my work in docbook with a docbook editor, but did some of my latest boook in asciidoc, which was much easier. Just use a standard text editor of choice (like Vim) and get right to it. Much easier for me, anyway.
One thing I'd really like to see is ipynb supporting asciidoc instead of or in addition to markdown. You can go to/from asciidoc and docbook in a lossless way, IIRC.
[1] http://asciidoctor.org/news/2013/05/21/asciidoctor-js-render...
[2]https://github.com/scholmd/scholmd/wiki
[3]http://blog.martinfenner.org/2013/06/19/citations-in-scholar...
[4]http://www.codinghorror.com/blog/2012/10/the-future-of-markd...
What an awesome idea -- I can think of some sociologists/biologists who had to suffer through MS Word equation editor with excel charts who would love something like this. The internal hyperlinks would be awesome too.
For now, at least you can "decode" ipynb to LaTeX and use the %%latex magic.