LaTeX Best Practices

 

ACM Logo

 

Advancing Computing as a Science & Profession

 

Best Practices for Submitting the LaTeX Paper/Article

to the acm publishing system (TAPS)

ACM wants to make the submission process as smooth as possible for authors, so we have developed a set of best practices which you should follow to ensure that the submission and conversion process goes as smoothly as possible.

Before submitting your LaTeX source files to TAPS (for proceedings articles) or through the existing journal production process, we encourage authors to review the following points for confirming the smooth processing of your paper:

 
  • ACM has transitioned to a new authoring template. The new ACM Master Article LaTeX template consolidates the previous eight individual ACM journal and proceedings templates. The templates are updated to the latest LaTeX distribution versions, developed to enable accessibility features, and they use a new font set.

The new LaTeX package incorporates updated versions of the following ACM templates:

o   ACM Journals: ACM Small, ACM Large, ACM and TOG (also for SIGGRAPH authors publishing in TOG)

o   ACM proceedings templates: ACM Standard, SIGCHI, SIGCHI abstracts, and SIGPLAN

All journals use acmsmall with the following exceptions:

o   acmlarge - Large single column format, used for JOCCH, TAP

o   acmtog - Large double column format, used for TOG

Note: Most proceedings authors will use the "sigconf" proceedings template. If you are unsure which template variant to use, please request clarification from your event or publication contact.

 
  • Use the standard LaTeX code while preparing your manuscript as seen within ACM’s sample template files:
 

For ACM Conferences

For ACM Journals

sample-sigconf.tex

sample-acmsmall.tex

sample-sigplan.tex

sample-acmlarge.tex

sample-sigchi.tex

sample-acmtog.tex

sample-sigchi-a.tex

 

 

ACM recommends the authors to check/refer the respective sample TeX file while preparing their papers and use the required option sigconf | sigchi | sigchi-a | sigplan accordingly and finalize their work.

 

Important information regarding submission versions for review: After finalizing the formatting of your paper you must use the option “manuscript” with \documentclass[manuscript]{acmart} command. This will generate the output in single column review format which is required. Accepted manuscripts will be transformed during production to produce properly formatted output accord to the publication specifications.  Authors will be provided the opportunity to review and approve the formatted output before the article is published to the ACM Digital Library.

 

  •  Avoiding redefining/custom codes for standard LaTeX command. Local Definitions are allowed but special fonts and characters are not allowed. Don’t use unnecessary local definitions that may overlap standard LaTeX commands.

\def\beq{\begin{equation}}

Red X:  Incorrect use of LaTeX coding for TAPS

\def\eeq{\end{equation}}

\def\myfigure#1#2{

  \begin{figure}[t]\centering

  \includegraphics*[width=\linewidth]{\figurePath#1}

  \caption{#2}\label{fig:#1}\vspace{-5pt}

  \end{figure}}

\def\mycharacter{\char’<Character Position>}

 

\def\rM{\ensurement{\mathrm{M}}}

Green Check: Correct use of LaTeX coding for TAPS

 

  • Modifications to the standard page length/layout and other related dimensions that are governed by “acmart” template are not allowed and will be returned for correction. Here are a few examples of commands which must not be used:
 

\renewcommand{\baselinestretch}{<factor>}

Red X:  Incorrect use of LaTeX coding for TAPS

\linespread{<factor>}

\setstretch{<factor>} from “setspace” package

 
  • The use of \vspace, should only be used to provide space above/below surrounding objects. It is not recommended to disturb the default vertical/horizontal spacing generated by “acmart.cls”.
 
  • Please code all the authors in individual \author{Author Name}, \affiliation{…} and \email{…} commands: Following correct block of code need to available for all respective authors individually:
 

\author{Craig Rodkin, Bernadette Shade, Laura Lander}
\affiliation{%
   \institution{ACM}
   \city{New York City}
   \state{NY}
   \country{USA}}
\email{ firstname.lastname@hq.acm.org }

Red X:  Incorrect use of LaTeX coding for TAPS

 

\author{Craig Rodkin}
\affiliation{%
   \institution{ACM}
   \city{New York City}
   \state{NY}
   \country{USA}}
\email{rodkin@hq.acm.org}Green Check: Correct use of LaTeX coding for TAPS

\author{Bernadette Shade}
\affiliation{%
   \institution{ACM}
   \city{New York City}
   \state{NY}
   \country{USA}}
\email{shade@hq.acm.org}Green Check: Correct use of LaTeX coding for TAPS

\author{Laura Lander}
\affiliation{%
   \institution{ACM}
   \city{New York City}
   \state{NY}
   \country{USA}}
\email{lander@hq.acm.org}
Green Check: Correct use of LaTeX coding for TAPS

For more information on recommended practices for coding author information please check here.

 
  • Full length manuscripts must contain following information:

CCS Concepts and Keywords

 
  • Abstract, Poster, and other short manuscripts of 2 pages or less may omit CCS Concepts and Keywords
 
  • When submitting manuscripts for publication, the manuscript must contain the ACM Rights Text and Bibstrip data. You will receive correct data to insert into your LaTeX document from ACM’s rights management system via email after completing the ACM eRights form. Here is an example of a proceedings submission:

 

% ACM License Text
\setcopyright{acmcopyright}

% DOI
\acmDOI{10.475/123_4}

% ISBN
\acmISBN{123-4567-24-567/08/06}

%Conference Details
\acmConference[WOODSTOCK'19]{ACM Woodstock conference}{July 2019}{El Paso, Texas USA}

% Year
\acmYear{2019}

% Copyright Year
\copyrightyear{2019}

PDF output of the mentioned LaTeX code:

Sample ACM permission statement 

 
  •   Figures and tables: The new ACM styles use the standard LaTeX interface for figures and tables.  There are some important items to be aware of, however.

o   The captions for figures must be entered after the figure bodies and for tables before the table bodies.

o   There must be an image within figure environment. Tables are not recommended within figure environment.

o   The ACM uses the standard types for figures and tables and adds several new ones.  In total there are the following types:

figure, table: a standard figure or table taking a full text width in one-column formats and one column width in two-column formats.

figure*, table* in two-column formats, a special figure or table taking a full text width.

teaserfigure: a special figure before maketitle.

sidebar, marginfigure, margintable: in the |sigchi-a| format, special sidebars, tables and figures in the margin.

 
  • How to use multiple part image files within a single figure environment: User can use standard subfigure package for this requirement; following is an example:

\begin{figure}
\subfigure{\includegraphics[height=1in,width=1in]{fly1}}  \subfigure{\includegraphics[height=1in,width=1in]{fly2}}
\caption{…}
\label{fig:three}
\end{figure}

Sample Image file of pair of flies

For adding labels to the individual images use can add “[]” (optional argument) with the \subfigure command; for example:

\subfigure[]{\includegraphics[height=1in, width=1in]{fly1}}

 

  • Expand your audience. ACM is committed to publishing in an accessible friendly format (https://www.acm.org/accessibility) that permits all its readers to have the content presented to them in a thorough and useful way. ACM needs the assistance of its authors to help achieve this goal. Authors are strongly encouraged to provide “alt text” (alternate text) for floats (images, tables, etc.), in their content so that those with disabilities can be given descriptive information for these figures that are important to the work. Some readers of ACM publications might be visually challenged. The descriptive text will be displayed in place of an image if an image cannot be loaded, and the alt text provides in-depth float descriptions to search engine crawlers, which helps to properly index the images. It is important to provide them a description of each image used in the paper. The command \Description[<short description>]{<long description>} should be placed inside every float (Figure/Table).

 

  • Math environment: AMS math commands are recommended when inserting math equations into your manuscript. We take advantage of the AMS math commands within the newly developed HTML output in the ACM Digital Library. We’ve integrated MathJax into the HTML, which not only renders the math correctly, but offers readers the ability to extract the math from the HTML document for reuse.

 

  • References should be organized and formatted with the BibTeX software package, and included in your LaTeX source as follows:

\bibliographystyle{ACM-Reference-Format}

\bibliography{<NAME OF BIBTEX FILE>}

Authors' first names should be spelled out, not abbreviated. Sources should be clearly identified: title, year, volume, number, pages, etc.

 

  • Authors of approved papers will receive an email from rightsreview@acm.org to complete the ACM eRights form. Please complete the form in a timely manner so not to delay publication of your paper. After completion of the ACM eRights form, you will receive another email from rightsreview@acm.org which contains the commands that need to be inserted into your final LaTeX file in order to generate the proper rights statement and Bibstrip data.

 

  • After above step you are required to either submit your files to TAPS (The ACM Publishing System) or to your proceedings production contact for submission processing. You will need to package your files in the following way:


You will receive a notification email from TAPS, in which system will ask you to submit your manuscript file and provide a unique link through which you can access TAPS (your specific author dashboard). In the top of your author dashboard TAPS provides the information about “Proceeding Acronym”, “Paper ID” and “Title of Paper”. You can upload a zip file in TAPS for further processing and the ZIP file naming should be like: <Proceeding Acronym>-<Paper ID>.zip


The ZIP file can contain 3 folders, following is the folder structure inside ZIP file:

 

pdf: This folder contains the PDF output of your manuscript. It’s not mandatory to provide this folder.
source: This folder contains final source files MS-Word or LaTeX. This folder should contain all necessary files/resources which are required to generate the final output.  It’s mandatory to provide this folder.
supplements: This folder contains the supplementary material which need to available at the time of web publishing. The content of this folder will not appear in PDF output. It’s not mandatory to provide this folder.

You can also check the in information available under “General Instruction and Information” at your TAPS author dashboard. Make sure that your package contains all figures, macros and LaTeX files you used in your paper.

  • If your manuscript uses multiple TeX files then make sure that only one TeX file should contain the \documentclass[<options>]{acmart}. In the case of multiple files having this command, TAPS will show a validation error message and ask you to update it accordingly.
  • If you are submitting to TAPS, will receive an email notification from TAPS with the unique link for accessing and depositing your package for processing.
Last updated Februart 10, 2020 by C. Rodkin

Why I Belong to ACM

Hear from Bryan Cantrill, vice president of engineering at Joyent, Ben Fried chief information officer at Google, and Theo Schlossnagle, OmniTI founder on why they are members of ACM.

The DevOps Phenomenon

ACM Queue’s “Research for Practice” serves up expert-curated guides to the best of computing research, and relates these breakthroughs to the challenges that software engineers face every day. This installment, “The DevOps Phenomenon” by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald and Helmut Krcmar, gives an overview of stories from across the industry about software organizations overcoming early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between software and operations teams, faster delivery times for new software features, and achieving higher levels of stability.
https://www.acm.org/publications/taps/latex-best-practices
www.acm.org
crawl=CC-MAIN-2020-16
110184
application/http; msgtype=response
sha1:WSCIJCNHPYP3RZPWL2TIYT2EQ6OB4FS6
<urn:uuid:ce11eea6-e8a0-4e61-8b57-43450ff5c32c>
2020-04-10T14:08:44Z
5.79.89.115
text/html
sha1:7GJK6JZGLMAAUVOJSVPGZOQY2GDSOGOU
<urn:uuid:e6b344da-68ad-44c0-a53a-29ddb79a8cd6>
https://www.acm.org/publications/taps/latex-best-practices
response
<urn:uuid:061044f3-e644-4c23-a67e-23f85f152cff>
isPartOf: CC-MAIN-2020-16
publisher: Common Crawl
description: Wide crawl of the web for March/April 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-202.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/