Yes but I want to generate what I want from the document tree. So may be using the pier syntax is better since we should have the tree doc and all the infrastructure. I could even write a markdown outputter. We could use the pier syntax for the internal doc and as a pharo pivot documentation language. Damien we should check that because everything is there since we used it for the seaside book. Stef On Jul 29, 2012, at 10:55 AM, Douglas Brebner wrote:
On 26/07/2012 09:58, Camillo Bruni wrote:
markdown / pandoc work pretty well for that :)
http://johnmacfarlane.net/pandoc/
I use it for all non-paper text. Plus you can simply output a .tex file and put it into a real latex document if needed.
It also outputs ePub which is handy.
BTW, as a thought for the future, since ePub3 will support javascript it may be possible to embed Amber smalltalk in a standard ebook. Which could be very useful for making truly live documentation.