If, like me, you're working on a SoCG submission, and this is the first time you've tried using the LIPIcs format that SoCG is now using, you may run into some minor formatting issues (no worse than the issues with the LNCS or ACM formats, but new and different). Here are the ones I've encountered, with workarounds where I have them:

  • The LIPIcs format automatically includes several standard LaTeX packages including babel, amsmath, amsthm, amssymb, and hyperref. So there's no point in including them yourself and (if you specify incompatible options) it may cause an error to include them yourself. I haven't needed to change the hyperref options, but if you do, see here.

  • You may like to use the lineno package so that, when reviewers give you comments on your submission, they can tell you more accurately which line they're referring to. If you try this with the LIPIcs format, you will notice that you don't get line numbers in the last paragraph of a proof, nor in a paragraph that contains a displayed equation (even if you correctly delimit the equation with \[...\] instead of using the obsolete $$...$$, which can also cause problems with lineno). The solution to the proof problem is to change the proof termination symbol (a triangle instead of the usual Halmos box) to use an explicit $...$ instead of \ensuremath):

    \renewcommand\qedsymbol{\textcolor{darkgray}{$\blacktriangleleft$}}

    The solution to the displayed equation problem is more complicated, but is given in this blog post from 2007 (the update near the start of that post). Why this incompatibility hasn't been fixed in the last seven years is a different question.

  • If you use the numberwithinsect document class option (pronounced "number with insect"), then the LIPIcs format numbers theorems, lemmas, etc by what section they are in: Lemma 2.1 for the first lemma in Section 2, etc. But if you also run past the page limit and use appendices, you may notice that the lemmas are being given numbers that re-use previously used numbers, because although the appendices have letters rather than numbers the lemmas use numbers: the first lemma in Appendix B is also called Lemma 2.1. The problem is that the LIPIcs style expands the \thesection macro (the one that gives the number or letter of the current section) at the time it defines \thetheorem (the one that gives the name of the current theorem or lemma). So when you use \appendix (or \begin{appendix} if you like to pretend that non-environment commands are really environments), \thesection gets changed but it's too late to make a difference to \thetheorem. The fix is to add the following lines after \appendix:

    \makeatletter
    \edef\thetheorem{\expandafter\noexpand\thesection\@thmcountersep\@thmcounter{theorem}}
    \makeatother
  • I've already written about the problems with using the \autoref command of the hyperref package: because LIPIcs wants to use a shared numeric sequence for theorems, lemmas, etc., \autoref thinks they are all theorems. Someone else also recently asked about this problem. This is a more general incompatibilty between amsthm and hyperref, but LIPIcs also includes some of its own code for theorem formatting, which seems to be causing the fixes one can find for amsthm not to work. The solution is to fall back to the non-hyperref way of doing things: Lemma~\ref{lem:my-lemma-name} etc.

  • Speaking of theorems: if you use \newtheorem, you probably want to have a previous line \theoremstyle{definition} so that whatever you're defining looks like the other theorems and lemmas.

  • On the first page of a LIPIcs paper, the last line of text may be uncomfortably close to the Creative Commons licencing icon. I haven't found a direct workaround for this (although probably it's possible) but you can obtain better spacing by having a footnote (for instance one listing your grant acknowledgements) or a bottom figure on that page.

  • If you're used to trying to fit things into a page limit with LNCS format, you may have learned to use \paragraph as a trick to save space over subsections. That doesn't work very well in LIPIcs, for two reasons. First, because it will give you an ugly paragraph number like 6.0.0.1 (the first numbered paragraph in an un-numbered subsubsection of an un-numbered subsection of section 6). You can work around this by using \paragraph*. But second, because unlike in LNCS the paragraph heading won't be folded into the paragraph that follows it, so you save a lot less space. I don't want to try to work around this one. And fortunately I haven't yet seen my coauthors adding code like \noindent{\bfseries Paragraph heading.} Paragraph text... (or worse \bf ...). Solution: find different tricks for your space-saving efforts. Like maybe write more tersely.

Anyone else have any timely tips?





Comments:

q_pheevr:
2014-11-25T14:06:09Z
(pronounced "number with insect")

Is that a feature, or a bug?

ext_2893121: For the paragraph issue...
2014-11-25T15:30:59Z
For the paragraph issue, I use:
\InNotSoCGVer{
   \newcommand{\myparagraph}[1]{\paragraph*{#1}}
}
\InSoCGVer{
   \newcommand{\myparagraph}[1]{\bigskip\noindent{\textbf{#1}}}
}
Its a bit clanky, because you have to make sure there is no empty line. So I do:
\myparagraph{Bogi.} %
%
bla bal bla
The advantage is that one can replace \bigskip with \smallskip or \medskip, depending on much space one wants.
11011110: RE: For the paragraph issue...
2014-11-25T17:22:43Z
On the G+ post, there's a suggestion to use \subparagraph.
ext_2893121: RE: For the paragraph issue...
2014-11-25T17:31:20Z
You dont get the spacing control. I use this whenever I need to compress a little bit more text into the page limit.
None: RE: For the paragraph issue...
2016-01-15T08:19:51Z
You should use \subparagraph*{<heading>.}
ext_2893863:
2014-11-26T03:29:28Z
Like like like the last sentence of the final bullet item (but perhaps I might have said "concisely" rather than "tersely" since I think the latter has a bit of a negative connotation).