I built a CV using the kjh-vita LaTeX template (based on memoir and the template's custom stylings). I use(d) extensively end-notes via the enotez package. Then, I derive(d) a short version without the end-notes (all commented out, manually of course). Every now and then, I retouch various details either in the "full" version, or in the short one.

It'll be smart to keep one source from which to derive different versions (in the current case, the "full" and a short version, though I could make use of an option for a third version at some point).

The packages I use in the full version are:

\usepackage{org-preamble-xelatex} % as per the original template
\usepackage{fontawesome,marvosym,url} % \Mobilefone looks better than \faMobile
\usepackage{lastpage} % use in header for full version
\usepackage{multicol} % end-notes in two-columns

Now, in the short version I'd like not to use some of the above, notably fnpct, enotez, multicol and footmisc. I'd like to silence all occurences of end-note markers (in-text and in the end). There are (and might be even) more changes (to come) that concern the content (text) itself (as asked/demonstrated in Multiple output pdfs with limited info in one).

Obviously, this is not a new question! Searching and reading the following related Q&As:

However, this information is a lot to read carefully. Any suggestions on where to start as a beginner?


Just for the matter of completeness, I use http://www.scons.org/ and the following SConstruct for compiling the documents. It works straightforward (see also: https://tex.stackexchange.com/a/26573/8272).

# make sure scons finds tex executables:
import os
environment = Environment(ENV=os.environ)

# xelatex
environment['PDFLATEX'] = 'xelatex'

# target and source:
pdf_short_cv = environment.PDF(target='cv_nikalexandris_short.pdf', source='short_cv.tex')
pdf_full_cv = environment.PDF(target='cv_nikalexandris_full.pdf', source='full_cv.tex')

# make sure that the pdf is reloaded properly (e.g., in Skim)
  • 1
    Read the first one you can understand carefully. See what you can now do. If you need more, read the next one. Repeat. You will be able to skim increasing amounts of information as you proceed, because you will find similar strategies and ideas. – cfr Oct 10 '15 at 22:38
  • @cfr Thank you. I find this tex.stackexchange.com/a/245616/8272 somewhat interesting. It hasn't attracted the eyes of many, it seems. Why so? – Nikos Alexandris Oct 10 '15 at 23:51
  • I wouldn't read much into the vote count, if that's what you mean. The best answers and questions often get few votes, and poor questions and, sometimes, answers often get lots of votes. In this particular case, the answer is 'late' (i.e. a loooonnng time after the question was asked) and there were already several answers, including an accepted one, with significant numbers of votes. So to see that one, people have to scroll a long way. And would-be answerers are less likely to view a question with an accepted answer. And... Well, just how the site works, really ;(. – cfr Oct 10 '15 at 23:59
  • Plus it uses make which will put a lot of people off immediately because it is a tool from outside the TeX ecosystem. – cfr Oct 11 '15 at 0:01
  • Why not csquotes in the short version? I strongly recommend babel (unless everything is in English), csquotes, and biblatex for a CV. Programming around having access to csquotes commands is likely to be more trouble than it's worth. And I need to ask: endnotes in a CV?!?? What's up with that? – jon Oct 11 '15 at 0:33

Here's a schematic answer, since you seem as eager to learn the principles involved as you are in getting an answer.

For CVs, I like to break each section into discrete files, which you can then \input or not as needed. You could combine this with some boolean logic to determine if things get included or not. In the example below, you can see how to add the conditional clause into a macro definition and how to operate with \if-constructions directly.

So you need some "sections" in independ files:

% cv-associations.tex

% cv-contact.tex
\section{Contact Info}

% cv-education.tex

% cv-outreach.tex

% cv-presentation.tex

% cv-publications.tex

% cv-teaching.tex

Then you need the masterfile:

\RequirePackage{etoolbox}% etoolbox's \bool*-related commands work with normal \if-related commands
\providebool{fullCV}% default: false

% An example of how you might conditionally load packages

\usepackage{lipsum}% just for dummy text

% for things you sometimes want to \input

% conditionally include \endnotes


% regular \input files will always be included



% \cvinput files will only be included if \fullCVtrue is active






Now you can compile the file directly and simply uncomment the \booltrue line as needed. But the reason it's set up this way above the \documentclass line is so you can use the command line to compile both files with one command. Something like this, for example (assuming the filename is multioutputCV.tex):

xelatex -jobname=CVfull "\newif\iffullCV\fullCVtrue\input{multioutputCV.tex}" && xelatex -jobname=CVshort "\newif\iffullCV\fullCVfalse\input{multioutputCV.tex}"

(Compile twice, though, to get the endnotes in place for the full version.)

Should result in two files: CVshort.pdf and CVfull.pdf. You could now write a Makefile if you liked, but that is somewhat beyond the scope of this question.

  • Very well explained and demonstrated. I am learning. – Nikos Alexandris Oct 12 '15 at 22:44
  • @NikosAlexandris -- Glad it is useful. Cheers. – jon Oct 12 '15 at 23:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.