Thursday, July 11, 2019

typography - Font overload in academic documents



I'm a researcher in cryptography and regularly read and write acedemic papers which are, to say the least, not objects of great beauty. Recently I've noticed that the guideline not to use more than two or maybe three fonts in a document is regularly flouted and wonder how much this has to do with it.


Here's an example of mine (content is of course irrelevant):


sample of how academics use fonts


The done thing seems to be to have different fonts for different categories of things:



  • Serif for body text, same in bold for headings, italics for emphasis.

  • Sans-Serif or monospace for algorithm names (the "KeyGen" etc. in the example).

  • Italics (but in a slightly different font I think) for inline math.

  • sans-serif, bold or small caps for names of security notions (small caps in the example above).

  • "blackboard bold", "calligraphic", "fraktur" etc. (the different options available in LaTeX) for different classes of things like collections of algorithms, participants in a protocol.


  • and so on ...


My questions are:



  • The above example looks a bit chaotic to me. Is it mainly the number of fonts, or am I missing any other key design principle (like not using fonts that go well together or bad spacing)?

  • Is there any point from a design perspective in using different fonts in a techinical or academic document to denote different categories of things or would it be better to just to use the same font for all?

  • The argument for "one font per category" seems to be something like making it easier for the reader to recognise at a glancce what kind of thing I'm referring to - is there any justification for this? Or a better way to achieve the same?

  • I've read this GD topic, any more pointers to how I can make my academic papers look better?



Answer




As you identify, there are a number of issues and they all stem from your implementation of (or possibly how you're using) TeX.


For a bald list, I cite



  • the use of a Scotch Roman face

  • poor letter spacing

  • lines too closely-spaced

  • poor mixing of fonts (sans and script)


TeX's Scotch Roman face is old-fashioned and fussy. All those serifs! It's this fussiness which needs a greater leading. It's not helped by poor spacing between letters: some are a great deal more cramped than others. Look at the word ciphertext. The small caps are not real small caps: they are simply reduced in size keeping the proportions the same. Small-caps don't do that. The sans and script fonts are a poor mix, because they do not have the same optical density as the main font. It's fine using sans for the algorithm names, but they don't have to stand out in that context.


Here's a reset example of your text. The main font is Calluna, and the software I used can't cope with fi or ffi ligatures, and I had a limited range of fonts available for the symbols. Nor does it do small-caps natively: I set "small-caps" and then increased their width to 115% so that they looked like real small caps (it keeps the main strokes the same width). The end result is an even distribution of ink.



Leading is increased as that helps with the mixing of symbols and retaining readability. The italics are well-designed and don't alter the overall blackness of their text. The sans words are set in Calluna Sans Light. This is derived from Calluna so the letter-shapes are very similar (and the same size!) and using the Light variant again keeps the optical density even so they don't stick out. This helps your head-words to be headings.


There would certainly be scope to add more space between paragraphs as others have suggested, but if this is a list of small items it might break it up too much. Allowing more light into the page with increased leading generally would be sufficient for a list; larger, "real" paragraphs might benefit from an extra half-line of whitespace.


Reset text


No comments:

Post a Comment

technique - How credible is wikipedia?

I understand that this question relates more to wikipedia than it does writing but... If I was going to use wikipedia for a source for a res...