# Tag Info

3

This has been encountered before, see also: \includegraphics and \includepdf both remove all copy (text) from my (R outputted) pdf graphs, using pdfTeX So as I was suspecting it's a font problem. You can compile your document using XeLaTeX (or XeTeX), not pdflatex. \documentclass{standalone} \usepackage{graphics} \begin{document} ...

4

The error is ; after the \usepackage{...} statements, but I have no idea how this can be prevented in pandoc if there is some automatic generation If LaTeX encounters typesetting material (such as text, interpunctuation characters) in the preamble it will issue the error message missing document, since this content is not allowed in the preamble. ...

1

This is described in the tex faq: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxcmds An expl3-variant to show the internal command (which ends with a space as David mentioned): \documentclass{article} \usepackage{hyperref,expl3} \begin{document} \ExplSyntaxOn\cs_show:c{autoref~}\ExplSyntaxOff \end{document}

4

That is the code for \autoref if you want to see the code for the internal command \autoref_ (with a space) then {\let\protect\show\autoref} works > \autoref =macro: ->\leavevmode \@ifstar {\HyRef@autoref \@gobbletwo }{\HyRef@autoref \hyper@@lin k }. \autoref ->\protect \autoref l.4 {\let\protect\show\autoref }

2

@d2dp As noted above you needed a \bibliographystyle line. I removed the American from the class options as it is not used in report. Finally you can surf for bibtex styles. Here is a typical find: http://homepage.stat.uiowa.edu/~rlenth/ALPHA/bibstylescompared.pdf \begin{filecontents}{references.tex} \renewcommand\bibname{references} ...

2

It seems that, by default, the flushend package activates the debug option. Use, in the class, \RequirePackage[nodebug]{flushend} instead of loading it without options. Here's what I get from \PassOptionsToPackage{nodebug}{flushend} \documentclass{actaspartae} \usepackage{hyperref} \begin{document} \subjectarea{Science} \title[Short Title For this ...

0

I have continued to look for a solution and found a "dirty" fix. Since I have spent 10+ hours in total, I just wanted to publish my solution in the hope that one day it may help someone. However, I still do want to see a proper solution, so I am not going to accept my solution. Please do write if you have a better solution or an explanation of the underlying ...

Top 50 recent answers are included