Writing technical reports

Intro

This document is really a collection of things that I should remember when I'm writing reports myself. If someone else thinks it's useful then they can use it but this is all just guesswork really, based on what I find easiest to read and the main mistakes I find myself making. As with everything, it's a work in progress — and I'll be very welcoming of comments or additions.

More complete/official references on good writing style are, for example, "The Chicago Manual of Style" (for technical matters) and George Orwell's famous "The Politics of the English Language" for good advice on prose stylings. The little Penguin reference book "Mind The Gaffe" is an entertainingly source of English language obscurities.

Good/correct English

It's a sad truth that not enough people know how to write good English. I won't claim any particular aptitude for it myself, but here's a few collected aspects of the language which are reasonably non-subjective:

Mathematical specialities

Mathematical variables should be typeset in italic text. Anything else (a label on a variable, or text for example) should be typeset in roman (upright) text. Operators are often set in a calligraphic font but this is largely left to the discretion of the author. Group names are set in an upright mathematical font and set names are often in ``blackboard bold'', a style which uses doubled vertical struts.

Scientific specialities

In high energy physics applications, particle names should be typeset in an upright font --- unless the particle is being used in an equation in a context equivalent to a variable. Most of the time, they are not variables, so don't italicise them!

That's all, folks

If you've got any comments, please address them to Andy Buckley via www.insectnation.org.