Here are the commands I used in the FOSS4G2007 QGIS workshop document: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % my commands %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \newcommand{\button}[1]{\cornersize{0.1}\ovalbox{\textsf{\scriptsize#1}}} \newcommand{\classname}[1]{\textsf{\textbf{#1}}} \newcommand{\fieldname}[1]{\textsl{#1}} \renewcommand{\filename}[1]{\texttt{#1}} \newcommand{\keystroke}[1]{\fbox{\textsf{\scriptsize#1}}} \newcommand{\menuopt}[1]{\textsf{#1}} \newcommand{\method}[1]{\textsf{\textit{#1}}} \newcommand{\server}[1]{\textit{#1}} \newcommand{\sqltable}[1]{\textsf{\textbf{#1}}} \newcommand{\toolbtn}[1]{\cornersize{7mm}\Ovalbox{\textsf{\scriptsize#1}}} \newcommand{\usertext}[1]{\texttt{#1}} So you would markup a tool button like this: \toolbtn{Add Vector Layer} This in turn is converted according to the command definition, resulting in an oval outline of the text in sans-serif scriptsize font. Of course you can tweak the commands as the team sees fit. The obvious advantage is you can consistently apply the same markup to the same items and easily change the style at any time by editing the commands in the preamble of the document.