5,020 reputation
2834
bio website
location England
age
visits member for 1 year, 11 months
seen 3 hours ago

I've been using LaTeX since I started university 6 years ago, and grateful to everyone ever involved in the kernel, or in the various packages, distributions and websites, those who introduced me to it and those who answer related questions!

I'm following with interest the developments on LaTeX3 and also the alternative engines, which I hope to one-day be able to exploit more!


May
1
awarded  Nice Answer
Apr
11
comment Disabling backref in secondary multibib bibliography with natbib
Happy to help. Perhaps now you'd like to edit your question so that the focus is on the 'bonus' part, as it is still an interesting question?
Apr
10
comment Disabling backref in secondary multibib bibliography with natbib
Adding \renewcommand{\backrefcitedsinglestring}[1]{} \renewcommand{\backrefcitedmultistring}[1]{} between your \begingroup...\endgroup for the Publications part (but before \bibliographypublications) seems to solve the first (easiest) part of your question.
Apr
5
comment Installation/usage of latexdiff on Windows 7
@KevinC: Your error message, if it is to be trusted, does indicate that it is looking for the file with a .pl extension (and possibly in a different subfolder?), so it might be worth copying the script to there to see if it helps. However, before you do that, I wonder if it is worth trying to update the part of your MiKTeX distribution that contains latexdiff.exe (probably called a MiKTeX bin package or something), through the MiKTeX Update (admin) application (or just update everything that has an update available there).
Apr
4
comment Installation/usage of latexdiff on Windows 7
The latexdiff.exe is just a MiKTeX executable that is either supposed to prompt to install the latexdiff perl script (part of the latexdiff MiKTeX package) or to execute said perl script if already installed. As you say you do not have the perl script (but note it may not have the .pl extension), it seems like the latexdiff package is not installed, though it is odd that you are not prompted to install it automatically. Try launching the MiKTeX package manager directly (in Admin mode?) and selecting the latexdiff package for installation.
Apr
3
awarded  Enlightened
Apr
3
awarded  Nice Answer
Apr
2
comment How to use \section*{something} without removing it from the Table of Contents?
See also my answer to No section numbers, but still have PDF bookmarks with hyperref. There, the use of hyperref is optional and omitting it results in all unnumbered sections still appearing in the ToC.
Mar
25
comment Incompatibility of the ocg-p package with the ocgcolorlinks option of the hyperref package
I have edited your question to include what I consider to be a minimal working example (MWE) that illustrates your problem. In future, please try to do this yourself. Also, we don't usually put a greeting or a "thank you" in our posts. While this might seem strange at first, it is not a sign of lack of politeness, but rather part of our trying to keep everything very concise. Accepting and upvoting answers is the preferred way here to say "thank you" to users who helped you.
Mar
25
revised Incompatibility of the ocg-p package with the ocgcolorlinks option of the hyperref package
removed thanks, added an MWE
Mar
15
awarded  Revival
Mar
15
revised Make backrefs invisible in hardcopy
propogated update from the base answer by diabonas
Mar
12
comment Hyperref jumps to the wrong equation if the equation has a \tag and cleveref is used
@mafp: Glad it was of some help. I'm afraid it was a case of examining the various source files for each of the packages involved. Probably the issues with the interactions were never anticipated hence not documented or resolved.
Feb
27
comment Embed distributed LaTeX file/code to the PDF?
Maybe this is helpful: Create list of all external files used by master LaTeX document?
Feb
3
answered How to find out where a macro is defined?
Feb
2
comment handling href when importing separate standalone latex documents and assembling them into one document
@MartinScharrer: Fantastic. Thanks for that. I have edited my posts slightly to refer to the new version, and deleted previous comments.
Feb
2
revised handling href when importing separate standalone latex documents and assembling them into one document
change in light of currfile's new support for import
Feb
2
revised handling href when importing separate standalone latex documents and assembling them into one document
change intro in light of currfile's new support for import
Jan
28
answered handling href when importing separate standalone latex documents and assembling them into one document
Jan
27
answered handling href when importing separate standalone latex documents and assembling them into one document