## Popularity

TeX and LaTeX continue to attract attention, as you can see from the list of TeX-related blogs on TeXample.net. I don’t know how many hits each of those sites get, but I do know how popular my blog is and have some idea about a few other places. So I thought it might be worth a quick look at the numbers.

In a typical day, ‘Some TeX Developments’ gets around 200 hits. That varies a bit, depending on whether I post something. There are also occasional spikes, with the CV mini-series getting me over 500 hits a day for four days, and my thoughts on a LaTeX3 roadmap attracting over 2000 hits that day! By way of comparison, the TeX.sx community blog gets around 100 hits per day when there is not a post, rising to 300 to 400 on days when a post is added. The UK-TUG website gets around 60 hits per day, mainly for the templates. (It’s not really a blog, although we do use it for announcements.)

The TeXample.net site features both the community aggregator and the very useful set of TikZ examples. As you’d expect, this combination gains it a lot more hits than a blog: I believe about 2500 per day.

Then there’s TeX.sx, which has grown rapidly in the last year to become a great place to find TeX answers. Hits-per-day have been rising steadily there, and are now well over 20,000 per day. There are usually at lest 40 new questions and 70 new answers driving this growth, which I think bodes well for TeX.

So over all the picture is of a range of sites getting a good number of hits. I’ve no idea how that compares with other typesetting systems or programming languages, but I’d like to feel it is a good sign for the future.

## Font schemes and LaTeX3

There was a question recently on the TeX.sx site about font selection and LaTeX3. At the moment, there is not a LaTeX3 font system set up, and there are issues outstanding, so this is not something with a single answer. What I can do, though, is look at what seems likely and what some of the areas to consider are.

## (New) Font Selection Scheme

TeX’s font mechanism is pretty basic. There is no relationship between one text font and another: they are all simply set up using the \font primitive. So with plain TeX

{\bf Some {\it text}}

will have ‘Some’ in bold, but ‘text’ in mid-weight italics. LaTeX2e introduced the ‘New Font Selection Scheme’ (NFSS), which provides a method for managing fonts in a way that is likely to be more logical for the user. Thus

{\bfseries Some {\itshape text}}

will have the inner text both bold and italic. At the same time, the NFSS provides a system for loading font files in an organised way and substituting fonts when a particular shape combination is unavailable.

Over all, the NFSS is one the key successes of LaTeX2e compared with LaTeX2.09. There are also a lot of existing .fd files about for using fonts with LaTeX2e, and supporting those is important. So something like the NFSS is definitely needed: the ‘New’ is rather anachronistic nowadays, so the working title is just FSS.

The NFSS is not perfect, and so LaTeX3’s FSS cannot be simply a clone of NFSS. Perhaps the most common complaint about the NFSS is that \textsc is treated as a shape, which makes it impossible to combine it with \itshape to have italic small caps. Other areas which need addressing are for example flexible sizing and proportional/fixed width numbers for tables. This is all evolutionary, and so the plan is to port the existing NFSS first, tidy it up to fit better with LaTeX3 coding approaches, then add new abilities.

The second area to think about is loading fonts in the first place. The traditional LaTeX2e approach to this to set up a small(ish) package to select a font family, for example lmodern or mathptmx, which will then use the NFSS to load the appropriate TeX font files. For users of XeTeX or LuaTeX, the standard method is to use the fontspec package, which provides an interface between the extended \font primitives in these engines and the NFSS.

There are a few things to think about here. First, while XeTeX and LuaTeX can load system fonts directly, pdfTeX cannot. Secondly, even if you are using XeTeX or LuaTeX access to traditional TeX fonts cannot be ignored. There is a lot of MetaFont material on CTAN which is not available in any other format, so simply dropping support for these is not an option.

What I feel we need is a single font-loading interface at the user level which is capable of dealing with these requirements. Clearly, fontspec is going to provide inspiration on how to proceed, but some mechanism for working with pdfTeX will also be needed. My personal take on this is we’ll need a mapping layer, which will mean that at the user level you choose a font by name (as you would in a GUI application), and which then does the appropriate translation to the engine layer.

There are also math mode fonts to worry about. OpenType maths fonts are very much in development, but that doesn’t help with pdfTeX and again does not cover all cases. So again we need to continue to support TeX’s traditional math mode fonts. That will probably be the last part of this particular jigsaw to be tackled, simply because it’s the one with the least clear path at present.

## TeX on Windows: MiKTeX or TeX Live

Around two years ago, I wrote a short post comparing MiKTeX and TeX Live for Windows-based TeX users. Looking at my log files, this topic is perhaps the most common search term that brings people here. As such, I think it’s time to revisit the question and bring what I said before up to date.

On Windows, there are two actively-developed TeX systems with similar coverage: MiKTeX and TeX Live. Before I look at the comparison, a reminder that they are not the only choices. W32TeX is popular in the far east, and as well as being a TeX system in its own right is the source of the Windows binaries for TeX Live. There are also the commercial BaKoMa and VTeX systems (although whether anyone can get hold of the supplier of the latter is another question). However, for most users it comes down to a choice between the ‘big two’.

The good news is that there is a lot of similarity between the two systems, so for most users both systems are equally usable. However, there are differences and depending on what you need these might be important.

• The standard settings install everything for TeX Live, but only a minimal set of packages for MiKTeX. MiKTeX will then install extra packages ‘on the fly’, while TeX Live does not (there is a package to do that in TeX Live, but it’s aimed at Linux). Install-on-the-fly is useful if space is limited, but is more problematic on server set ups. So this is very much a feature who’s usefulness depends on your circumstances. Of course, there is nothing to stop you using MiKTeX and installing everything.
• The xindy program is only available in TeX Live. For those of you not familiar with it, xindy is an index-processor, and is much more capable of dealing with multi-lingual situations than MakeIndex. If you need xindy, TeX Live really is the way to go.
• MiKTeX is very much a Windows tool set, while TeX Live comes from a Unix background. This shows up from time to time in the way TeX Live is administered, and the fact that the TeX Live GUI is written based on Perl rather than as a ‘native’ Windows application.
• As TeX Live is the basis of MacTeX, and is the TeX system for Unix, if you work cross-platform and want an identical system on all of your machines, then TeX Live is the way to go.

## siunitx v2.4 beta

Development of the next release of siunitx has gone quite smoothly: I’ve added a few new features, and there is now nothing outstanding for v2.4. So it is time to ask for some volunteers to test the code.

In terms of new features, I have added the a choice of rounding modes modes the ability to compress down exponents in ranges and lists, both long-standing feature requests. In response to a recent TeX.sx question, siunitx can now also turn exponents into unit prefixes. At a lower level, I’ve also altered some of the options internally so fewer of the assume math mode.

To test, please download the ready to install TDS-style .zip file and install it locally. You should then be good to go. Feedback as a bug report or by e-mail welcome, as always. Assuming there are no problems, I’d expect to upload to CTAN by the end of the month.

## Writing a curriculum vitae in LaTeX: Part 4

I’ve looked over the last few days at some issues centring on writing a CV in LaTeX, first looking at the wider picture, then at creating a CV using custom macros and most recently at including a list of publications. To round things off, I’m going to create a short example: the source of my own CV cut down to a blog post. Before I do that, I’d point out that everyone’s CV is different, and while my approach makes sense for me it should be seen very much as something to pick up ideas from more than any form of template.

I’ll start as before by loading the article class and setting up some fonts. To allow a bit of flexibility, here I’ve made LuaLaTeX optional, so that the file can be processed, for example, using TeX4ht. As far as possible, the look will be the same with pdfLaTeX or LuaLaTeX (as I said earlier, I use LuaLaTeX for my CV as it makes some aspects of the real thing easier).

\documentclass[11pt]{article}

\usepackage{ifluatex}
\ifluatex
\usepackage{fontspec}
\setmainfont[Ligatures = TeX,Numbers = OldStyle]{TeX Gyre Pagella}
\setsansfont[Ligatures = TeX]{TeX Gyre Adventor}
\setmonofont[Ligatures = TeX]{Inconsolata}
\else
\usepackage[T1]{fontenc}
\usepackage{tgpagella}
\usepackage{inconsolata}
\fi

The next phase is to load the rest of the support needed, with hyperref last as this is usually the best idea.

\usepackage{array,etaremune,geometry,fixltx2e,microtype,pifont}
\usepackage{ragged2e,titlesec,xcolor}
\usepackage{hyperref}

Setting up hyperref is easy, so that is done next.

\hypersetup
{
hidelinks = true             ,
pdfauthor = Joseph Wright    ,
pdftitle  = Curriculum Vitae
}

Now there is some adjustment of the appearance. The page size is adjusted, and as I described in part 2 I set up a custom appearance for sections and subsections. I also miss out page numbers (which should not really be needed in a two page CV), and alter spacing a little.

\geometry
{
a4paper         ,
nofoot          ,
hmargin = 1.5cm ,
vmargin = 2cm
}

\titleformat{\section}{\Large\bfseries\sffamily}{}{0 em}
{%
\begingroup
\color{gray!30}%
\titleline{\leaders\hrule height 0.6 em\hfill\kern 0 pt\relax}%
\endgroup
\nobreak
\vspace{-1.2 em}%
\nobreak
}

\titleformat{\subsection}{\large\itshape}{}{0 em}{}

\renewcommand*\arraystretch{1.4}
\pagestyle{empty}
\frenchspacing

## Specialist macros

Now comes some custom code, first for publications as I described in part 3.

\newcommand*{\paper}[2]
{\item \href{http://dx.doi.org/#1}{\ignorespaces#2\unskip.}}
\newcommand*{\papertitle}[1]
{%
\begingroup
\ifluatex
\fi
\emph{#1}%
\endgroup
}

Next is the set up for the tabular nature of the CV. The text used here sets the width of the left-hand column, so may need to be adjusted to suite whatever is the widest thing you actually use!

\newlength{\sidewidth}
\newlength{\mainwidth}
\AtBeginDocument
{%
\settowidth{\sidewidth}{\textbf{Professional bodies}\hspace{0.75 em}}%
\setlength{\mainwidth}{\dimexpr\linewidth - \sidewidth\relax}%
}

Finally for the preamble, the macros which actually go into the body of the CV.

\newcommand*{\headline}[1]
{%
\hbox{%
\llap{\ding{72}\hspace*{0.2 em}}%
\textbf{#1}%
}%
}
\newenvironment{CVtable}
{%
\begin{tabular}
{@{}>{\bfseries}p{\sidewidth}@{}>{\RaggedRight}p{\mainwidth}@{}}%
}
{\end{tabular}}

## The document body

There is not so much you can say about the body of the CV! As described before, I start of with some general contact details.

\begin{document}

% Title block
\begin{raggedleft}
\textbf{Joseph Wright}    \\
School of Chemistry       \\
University of East Anglia \\
Norwich NR4 7TJ           \\
Tel.: 01603 592902        \\
Mobile: 0797 414 8180     \\
\href{mailto:joseph.wright@uea.ac.uk}
{\texttt{joseph.wright@uea.ac.uk}} \\
\end{raggedleft}

\begin{center}
\Huge\bfseries\sffamily
Joseph Alexander Wright
\end{center}

The first of several sections. Here, I’ve taken one which also has subsections, which work in the normal way.

\section{Employment history}

\subsection{Current position}

\begin{CVtable}
2008-- &
\headline{PDRA -- University of East Anglia} \par
Supervisor Prof.~C.~J.~Pickett \par
Studies on [Fe]- and [FeFe]-hydrogenase active sites mimics \par
Synthesis of novel ligands and model compounds \par
Mechanistic studies using stopped-flow UV and IR spectroscopies
\\
\end{CVtable}

\subsection{Previous positions}

\begin{CVtable}
2007--2008 &
\headline{Senior Demonstrator -- University of East Anglia} \par
Teaching degree level chemistry:
tutorials and laboratory classes \par
Preparation of M.~Chem.~third year practical course in
organic chemistry
\end{CVtable}

\dots

Several more sections would now follow, but I’ll leave this to the imagination.

\section{Academic history}

\dots

I find that it’s best to start a publication list on a new page, as I have quite a lot. In the UK, this list does not count as part of the general CV, so is allowed to go beyond two pages. As I said in part 3 of the series, it’s often useful to have this list as a separate file.

\newpage

\section{List of Publications}

\begin{etaremune}[start = 45] % Remember to adjust this
\paper{10.1021/ja2087536}{
\papertitle{Paramagnetic Bridging Hydrides of Relevance to Catalytic
Hydrogen Evolution at Metallosulfur Centers}, A.~Jablonskyt{\.e},
J.\,A.~Wright, S.\,A.~Fairhurst, J.\,N.\,T.~Peck, S.\,K.~Ibrahim,
V.\,S.~Oganesyan, and C.\,J.~Pickett, \emph{J.~Am. Chem. Soc.},
in press
}

\paper{10.1039/c1cc11320h}{
\papertitle{The role of CN and CO ligands in the vibrational relaxation
dynamics of model compounds of the [FeFe]-\break hydrogenase enzyme},
S.~Kaziannis, J.\,A.~Wright, M.~Candelaresi, R.~Kania, G.\,M.~Greetham,
A.\,W.~Parker, C.\,J.~Pickett and N.\,T.~Hunt
\emph{Phys. Chem. Chem. Phys.}, 2011, \textbf{13}, 10295--10305
}

\end{etaremune}

\dots

\end{document}


## Writing a curriculum vitae in LaTeX: Part 3

I work in a university, so an important part of my CV is a list of my publications. In part 2, I described how I put together the bulk of my CV using some custom macros: here, I’ll focus on publications.

## BibTeX?

The obvious approach to setting up a publication list is to use a BibTeX database. I have all of my publications in one, so that does suggest itself as an easy way to go. As with the balance between pre-built styles and custom macros, I’ve decided that for a CV the task is sufficiently specialised that doing it by hand is actually easier. There are a few reasons.

Usually, you give your publications in date order, newest first. That won’t quite come out correctly if you simply order by year, so using BibTeX it’s best to \nocite the keys in the order you want. No big deal, but it does mean you can’t just dump them all in one go.

There are a couple of style differences between what I want in my CV and what I’d usually use in a publication. We chemists don’t normally include article titles in citations, but for a CV it makes sense to add these. At the same time, I like to add hyperlinks to my publications in my CV using the DOI system. These can both be added to a standard BibTeX style (indeed, my own biblatex-chem style already has a switch for titles), but of course it’s another thing to sort out.

The inclusion of article titles brings me to perhaps the biggest reason that I’m not using BibTeX for my CV. Chemistry titles tend to contain lots of awkward material, such as formulae, which are hard to line break well. So there is a bit of work to do by hand to get things looking right. If I only ever used the publication list in my CV, with one set of formatting rules, then that would be fine. However, I use it in a few ways, and so manually adjusting line breaks via BibTeX is more awkward than simply including the text directly.

## A little structure

While usually my publication list is part of my CV, I sometimes need it as a stand-alone document. So I have the list itself as a separate file, and \input it into the main CV source. So all I have to do for a stand-alone list of publications is write a short wrapper around the list (again as a separate file).

Whether you use BibTeX or not, you’ll need to do is set up a reverse-enumerated environment, so that the most recent publication has the highest number. I do that using the etaremune package, which provides a suitable environment. The package needs to know how many items to enumerate, so either two LaTeX runs or a known starting value are needed. As I work by hand, I go with the latter approach

\begin{etaremune}[start  = 45] % Update when you add a publication
...
\end{etaremune}

It’s then just a question of filling in the items. I use a couple of custom macros for this. First, to let me quickly wrap up each entire item in a hyperlink, I define

\newcommand*{\paper}[2]{%
% Standard style
\item \href{http://dx.doi.org/#1}{\ignorespaces#2\unskip.}
% Including DOI
%\item \href{http://dx.doi.org/#1}
%  {\ignorespaces#2\unskip.\\\textsc{doi}: \texttt{#1}}
}

which takes the text as #1 and the DOI as #2. As you can see from the comments, this lets me quickly decide whether I want to include the DOI in the printed output or to just use it to create a link.

The second custom macro is one for the paper title

\newcommand*{\papertitle}[1]{%
\begingroup
\emph{#1}%
\endgroup
}

There are a couple of reasons for having a macro here. The first is that lining numbers seem to work better in chemical formulae than lower case ones do: of course this is my opinion! The second reason is that it makes it easy to quickly omit the title entirely if I need a short version of the publication list.

## Putting it all together

I’ve covered a few different ideas for creating a CV in LaTeX. Each one is I hope pretty simple, and as I’ve said most people want a CV that’s in a style they have chosen. But it’s always nice to have something complete to start from. So in the final part of this short series, I’ll put the various ideas together into an example.

## Date for the diary: TUG 2012

The dust has only just settled on TUG 2011, but I see that there is already a date set for TUG 2012. The meeting is planned for the 16th to the 18th of July next year, in Boston (US). For those of us who find that clashes happen, it’s probably worth penciling this one in.

Now, the next step is to raise the money to go …

## Writing a curriculum vitae in LaTeX: Part 2

In part 1, I looked at some general ideas about writing CVs, and said that my approach is to ‘roll my own’ format based on the standard article class. Here, I want to look at the process in a bit more detail. Most of this is about using LaTeX, and so the ideas I use apply to many other cases.

I make use of quite a few packages to get the appearance as I want. Rather than list all of them at once, I’ll take about the effects I’m aiming for, and include the package names as I go.

## Setting up the appearance

Starting from the article class, the first thing to address is the overall appearance of the CV. The standard Computers Modern font is well designed, but I guess says ‘LaTeX’ in a may that many people don’t want for a CV. With the availability of XeTeX and LuaTeX, using system fonts is easy (using fontspec, of course), and that’s particularly useful if like me you have some non-Latin characters that you’d like to include in the CV but keep visually ‘matching’ everything else.  For me, LuaTeX turns out to be a better choice than XeTeX (I want fully-functional microtypography as it helps with typesetting chemical names), so my CV starts off with

% !TeX program = LuaLaTeX
\documentclass[11pt,draft]{article}

% Font set up
\usepackage{fontspec}
\setmainfont[Ligatures = TeX,Numbers = OldStyle]{TeX Gyre Pagella}
\setsansfont[Ligatures = TeX]{TeX Gyre Adventor}
\setmonofont[Ligatures = TeX]{Inconsolata}

Here, as well as loading the fonts I like, I’ve set up to use lower case (old style) numbers as recommend by Bringhurst. I’ve also included a ‘magic’ comment to let my editor know to use LuaLaTeX. You might wonder about the draft option: I’ll come back to that later.

As I say, I want microtypography set up, so do

\usepackage[final]{microtype}

(Using the final option here will override the draft one set for the document class.)

That sets up the fonts, but what about page layout? Well, the standard here is to use the geometry package

\usepackage[a4paper,nohead,nofoot,hmargin=1.5cm,vmargin=2cm]{geometry}

I have pretty small margins, as for a CV this seems to make the most sense. I’m also not going to use a header or footer (so set \pagestyle{empty}), and so remove the space normally reserved for those.

Before looking at the content of the CV, I’ll mention hyperlinks as these come up throughout. My CV usually gets sent electronically, and I want to be able to include links for my e-mail address and publications. So I have

\usepackage[final]{hyperref}

\hypersetup
{
hidelinks = true ,
pdfauthor = Joseph Wright ,
pdftitle = Curriculum Vitae
}

at the end of my package-loading section. The hyperref package deals with the links, while the set up makes them blend in to the text and adds my name to the PDF information.

A very common way to start a CV is with basic contact details: what I’m going to call an ‘address block’. I do this very simply

\begin{document}

% Title block
\begin{raggedleft}
\textbf{Joseph Wright}    \\
School of Chemistry       \\
University of East Anglia \\
Norwich NR4 7TJ           \\
Tel.: 01603 592902        \\
Mobile: 0797 414 8180     \\
\href{mailto:joseph.wright@uea.ac.uk}
{\texttt{joseph.wright@uea.ac.uk}} \\
\end{raggedleft}

This therefore sits at the top of the first page, and comes out (to my mind) in a very pleasing style.

Also as part of the lead-off, it’s normal to have your name (never ‘Curriculum Vitae’), which again I do in a very straightforward way

\begin{center}
\Huge\bfseries\sffamily
Joseph Alexander Wright
\end{center}

## Sections and subsections

A CV needs several sections, for example ‘Employment history’, ‘Skills’ and so on. The standard LaTeX \section is the best choice of logical mark up for these, but the appearance is going to be wrong without adjustment. Taking some inspiration from the CurVe class, and using the abilities of titlesec and xcolor, the output can be customised to give something much more pleasing for a CV. I use

% Create some nice looking section dividers without too much fuss
\titleformat\section{\Large\bfseries\sffamily}{}{0 em}
{%
% This is put in _before_ the text so that an overlap is possible
\begingroup
\color{gray!30}%
\titleline{\leaders\hrule height 0.6 em\hfill\kern 0 pt\relax}%
\endgroup
\nobreak
\vspace{-1.2 em}%
\nobreak
}

which inserts a grey bar across the page, and places the name of the section (with no number) partially overlapping the bar.

For subsections, I go for a much lower visual impact

\titleformat{\subsection}{\large\itshape}{}{0 em}{}

which is enough to make them stand out from the body text, but keeps things flowing.

## The main body: lots of tables

The normal layout for the body of a CV is to use something based on a table, with ‘entries’ on the left and ‘information’ on the right. This can be done in lots of ways, but the approach I take is to set up a fixed column width in the preamble, then apply this to all of the CV. That requires a bit of set up

% Semi-automatically set up the table width
\newlength\sidewidth
\newlength\mainwidth
\AtBeginDocument{%
\settowidth\sidewidth{\textbf{Professional bodies}\hspace{0.75 em}}%
\setlength\mainwidth{\dimexpr\linewidth - \sidewidth\relax}%
}

Here, I’m setting two lengths to control the tables, with the only hard-coded part being the text I use to set the left-hand side width. I use the longest entry I’m going to use: in my case this is ‘Professional bodies’.

I then need the tables themselves. As they are all the same, it makes sense to set them up as a new kind of environment

\newenvironment{CVtable}
{%
\begin{tabular}
{@{}>{\bfseries}p{\sidewidth}@{}>{\RaggedRight}p{\mainwidth}@{}}%
}
{\end{tabular}}

(this uses the array package). I also \renewcommand*\arraystretch{1.4}, as this spreads the tables out a bit and I think makes things look less crowded.

The new environment is then used for each (sub)section, and contains the body of the CV, for example

\section{Employment history}

\subsection{Current position}

\begin{CVtable}
2008-- &
\headline{PDRA -- University of East Anglia} \par
Supervisor Prof.~C.~J.~Pickett \par
Studies on [Fe]- and [FeFe]-hydrogenase active sites mimics \par
Synthesis of novel ligands and model compounds \par
Mechanistic studies using stopped-flow UV and IR spectroscopies
\\
\end{CVtable}

\subsection{Previous positions}

\begin{CVtable}
2007--2008 &
\headline{Senior Demonstrator -- University of East Anglia} \par
Teaching degree level chemistry:
tutorials and laboratory classes \par
Preparation of M.~Chem.~third year practical course in
organic chemistry
\\

2005--2008 &
\headline{PDRA -- University of East Anglia} \par
Supervisor Prof.~M.~Bochmann \par
Use of zirconium phosphonates as heterogeneous catalyst supports \par
Synthesis of novel ligand systems for early transition metals
\\

2003--2004 &
\headline{PDRA -- University of Southampton} \par
Supervisor Dr A.\,A.~Danopoulos \par
Synthesis of novel N-heterocyclic carbene complexes \par
Catalytic testing on novel systems
\\
\end{CVtable}

You’ll notice the \headline macro here: it’s another formatting shortcut. It’s for making effectively subsubsections within my CV table, and is defined as

\newcommand*\headline[1]{%
\hbox{%
\llap{\ding{72}\hspace*{0.2 em}}%
\textbf{#1}%
}%
}

making use of the pifont package to provide a nice-looking star for each entry. You’ll see in the above example that I use it for things like marking up each job I’ve had in the table of employment history.

## Other refinements

As I mentioned in part 1, one of the advantages of using LaTeX is that you can store information in your CV as comments. That might be as simple as commenting-out lines that you want to miss out for a particular job, but you might also want to deal with longer optional sections. The comment package is ideal for this, as it lets you mark up sections for inclusion or exclusion in a pretty rapid way.

I mentioned earlier that I set the draft option for my CV, then override it on a package-by-package basis. The reason is that this will always include bars for overfull boxes: useful as you want to check for these.

In the academic area, a list of publications is an important part of a CV (it’s probably the most important part, actually). I’ve got a few things to say about that area, but this post is already long enough, so it will wait for the next part!

## Writing a curriculum vitae in LaTeX: Part 1

Writing a curriculum vitae (what Americans would call a résumé) is something that most of us have to do when applying for jobs. LaTeX users will naturally want to do this using LaTeX. Beyond the technical detail, there’s also the question of the wider requirements for a CV: while these are not LaTeX-related, they do form an important part of the process. So here I’d like to look first at the big picture, and then at some of the LaTeX approaches available.

## What is a CV?

Before we look at writing a CV, it’s important to be clear on what its for. Broadly, a CV is a condensed and (hopefully) easy-to-read summary of your qualifications and job experience. Most people want their CV to look good, but it’s important to remember that most employers have a tick list of items to find, and the look is probably of marginal importance in most cases. Of course, LaTeX users will still want to take the time to get a great visual result. (If you are applying for a job with a heavy dependence on visual design, then appearance may be the key!)

The other thing to bear in mind is that the requirements for a CV are dependent on the country and subject area you are in. Here in the UK, the normal advice is that a CV should only be two pages long. For academic jobs (like mine), a list of publications will often make the CV longer, while for industrial positions statements about your abilities, non-work activities and so forth are common. There’s also a strong feeling against having a photograph, both here in the UK and in the US, for equal opportunities reasons. On the other hand, several other countries have very different conventions, so before you start it’s important to check on what is needed.

Each job you apply for is different, and that means each CV you send of should be targeted to that job if possible. So while the basic structure will vary slowly, you should consider what to emphasise in each application. That’s an area where LaTeX’s ability to comment out lines can be a real bonus.

## Classes

As a CV is a specialist type of document, it’s no surprise that CTAN features a number of dedicated classes. I’m seen a few questions recently about moderncv, while in the past I used CurVe. In these and other cases, the idea is to use a mix of standard mark up and specialist macros to construct the output. In most cases, there is some form of tabular-like appearance generated along with the necessary headings and so on.

There are advantages and disadvantages to using one of these classes. Most obviously, someone else provides both the mechanisms you need and (hopefully) a good example to start from. The problem tends to be that altering the layout can be a bit awkward. As I said, while CV appearance may not actually be vital, most of us want to make our CV ‘personal’, which means altering the appearance.

## Roll-your-own

The alternative to using a pre-built class is to construct your CV yourself, setting up a structure that makes sense to you. Now, there is a bit of effort needed to do this, but it does allow you to decide on exactly how things will look. For my own CV, I used to use CurVe, but in the end decided this was actually making my life more, not less, complex. So the current source is based on the standard article, using some custom macros.

Most of what I’ve done in my CV is pretty simple, but it’s always nice to have documented examples. That would probably make this post a little too long, so I’ll return to look at the detail in my next post.