Copy‐editing the LaTeX files - ESTS-Variants/varianTeX GitHub Wiki

After adding compatible .tex files to your LaTeX project, referencing them in your main.tex file, and recompiling your PDF document, you will likely want to fix some formatting issues. The following methods can be used to make the contribution conform to the layout of the Variants journal.

If the author didn't use Heading templates, (sub)section titles will just be treated as formatting. They still need to be manually changed into \section{}, \subsection{}, etc. where appropriate. Don't forget the asterix if sections have no section numbers (e.g. \section*{TITLE}).

When authors want to use dashes to break up their sentences, use a single em-dash character (—), surrounded by spaces. Do not use double or triple dashes — be they hyphens (-) or en-dashes (–). Combinations of these may look the same in different fonts (and it will be difficult to distinguish them here, on GitHub), but they behave differently in PDF compilation, pandoc conversion, and HTML representation.

For example, format the text as follows:

I want to explore the possibilities — and limitations — of collective genetic critical projects here.

(corrected version of a phrase in Wiens 2024)

To type an em-dash:

• on MacOS, press: Option+Shift+-
• on Windows, use an Alt Code: Alt+0151

• \sout{} renders text as struck out. Peer reviewed full papers in Variants start with a few words in small caps.
• \textsc{} renders text in 'small caps'.
• \textit{} renders text in italics.
• \textbf{} renders text in bold.
• \underline{} underlines text.
• \textsuperscript{} renderst text in ^superscript.
• \textsubscript{} renders text in _subscript.
• \hspace{1em} provides a horizontal space of 1em in size. Adjust the number to provide make the space longer or shorter.
• \ldots should be used to write three consecutive dots, as in an ellipsis. For example, [\ldots] becomes [...].