> Lies, we haven't discussed the colour yet. (Blue please, I would like
> it to look like a Haynes manual)
> ----- Original Message -----
> > From: "tom" <bollocks...@gmail.com>
> > To: email@example.com
> > Sent: Thursday, 1 November, 2012 11:11:46 AM
> > Subject: Re: [london-hack-space] Re: New member manual
> > Congratulations, we have achieved peak-bikeshed!
> > On Thursday, November 1, 2012 11:09:09 AM UTC, Evan Davey wrote:
> > Images are handled fine in normal markdown and pandoc normally wraps
> > them up nicely in the latex output. Usually, I convert from markdown
> > to tex which just outputs the content which I then include in a
> > wrapper file that has the main document structure e.g.: class etc.
> > Additionally, I normally do stuff with the 'meta' data of my source
> > files eg: title, author etc. (which requires using multimarkdown
> > rather than pandoc first due to the better meta handling).
> > My approach has been to build anything complex into the latex
> > templates (manipulating what pandoc outputs) but it is also possible
> > to intersperse latex and plain text in the source if necessary - e.g.:
> > calling a QR code generation macro
> > On Wednesday, 31 October 2012 08:10:47 UTC, Dave (DMI) Ingram wrote:
> > On 30/10/12 23:07, Evan Davey wrote:
> > > I'd recommend http://johnmacfarlane.net/pandoc/ . That way the text
> > > can be kept in plain text as Markdown which is much friendly to edit
> > > than latex directly. I use this framework for creating all my
> > > business presentations, reports and I'm now working on a brochure
> > > (each have custom latex templates). The other advantage is that you
> > > can easily convert to other formats eg. HTML
> > I'll have to look into how much control Pandoc gives you over the
> > formatting, as I will want more than just basic text (e.g. vector
> > images, in-LaTeX QR code generation, image floats, etc). But it might
> > be an interesting start.
> > D