I’m using small caps to mark up acronyms. Many style guides recommend this to make the acronyms stand out less among the lower-case letters.
However, I didn’t find good advice of what to do with mixed-case acronyms, such as “OpenMP”. For consistency, I’m currently setting them in small caps as well, e.g. \textsc{OpenMP}
.
However, I feel that this defeats the original purpose of the small caps, and indeed it makes the abbreviation stand out disproportionately from the surrounding text, causing disruption. But all the other alternatives seem to have disadvantages as well.
For reference, these are the alternatives that I can think of.
-
\textsc{OpenMP}
, as mentioned above. Consistent with other abbreviations, in that it uses small caps all through. Inconsistent in that it makes minuscules into small caps and preserves majuscules. -
\textsc{o}pen\textsc{mp}
, only small-cap the capitals, logically the most consistent with the other abbreviations, but looks prohibitive. -
OpenMP
, normal font.
Am I missing something? What is the best alternative? What rationale can you offer for your decision?
Furthermore, I am currently defining my abbreviations via a convenient macro:
\newacronyms{api, cpu, dna, oop, OpenMP, …}
Which defines macros \api
, \cpu
, … \OpenMP
etc.
If possible, I’d like to preserve this style. I’m not sure how I could achieve such a convenient mechanism for methods 2 and 3 above. How would this be implemented?
Best Answer
Not really a compelling rationale, but I would go with method 2 because that's what The Economist does:
(The Economist, November 6th 2010)