On Sat, 10 Aug 2013, Hannes Magnusson wrote: > Keep in mind, no matter what format we choose we do need to roll our > own engine. > > > It would also be a big transition from docbook to another format. > > We'd definitely need a translation tool to help us. I'm not sure > > what is out there, but I can definitely say what is not out there: a > > docbook to our-custom-markdown formatter. That's another thing to > > keep in mind. > > Any off-the-shelf docbook->ascidoc/rST/markdown/whatever is not going > to work anyway, so it doesn't matter what is out there :)
Hmm, sortof not. I have been using rST for ages, and all my articles are written in it: https://github.com/derickr/derickrethans-articles It has some custom things, such as the meta data, support for vimeo etc as rST allows for you own definitions. I use Zeta Components' converter to get from rST to XHTML and have written some modifications. It also helps that the same stack allows rST->docbook and docbook->rST. And the stack allows for easy enough modifications... cheers, Derick
