The journal PLoS ONE, says in the FAQ
When submitting your revision, you will need to include the following new files:
[...] A ‘clean’ copy of your revised manuscript.
A revised manuscript with tracked changes. [...]
I'm using soul
's \hl
to highlight changes. So, I also need a version that doesn't highlight changes. To accomplish this, I added the following code. The \renewcommand{\hl}[1]{#1}
is intended as a no-op. So the "clean" version
would use \highlightfalse
and the version with tracked changes would use \highlighttrue
.
This appears to work, but I'm wondering if there are any problems with this approach, or better ways to do it.
\newif\ifhighlight
% COMMENT OUT \highlighttrue or \highlightfalse
\highlighttrue % or
%\highlightfalse
\ifhighlight
\else
\renewcommand{\hl}[1]{#1}
\fi
soul
?trackchanges
on this site also brings up changes. Can anyone comment on either of these?changes
doesn't usesoul
, which might be a plus, since it is unmaintained and buggy. And the most recent update ofchanges
is in 2011.soul
, then this approach seems fine to me (except that you example is missing the\newif\ifhighlight
). Depending on how you compile your file, Passing parameters to a document (or any of its near-duplicates) could be of interest.latexdiff
yet.