Further to answer #4 above (this won't fit as a comment) some notes to help those trying to address this issue and using as ACM's acmart
package. (As I write, I'm trying to write better docs due to author's complaints in the ACM Conference where I submit—so this on my desk right now)
Sadly the ACM style is poorly documented. The basic style page doesn't explain the part of a reference and conflicts with the supposed BibTeX versions. The cited items differ and some BibTeX code either won't compile or used the wrong field for `acmart'. At the same time, DL.ACM doesn't appear to use ACM styles (as per the style guide) or the attendant BibTeX.
Though acmart
can be configured (by an expert user) to use BibLaTeX
processing, it uses natbib
by default—and the documents seems to assume that too. The acmart
BST file defines a custom @periodical
type, though ACM style pages do not document the approved output style of that (I've not tested how the ACM and BiBLaTeX @periodical
do/don't align).
Asking for a citation of Communications of The ACM Volume 50, Issue 1, DL.ACM's offered BibTeX is this:
@article{10.1145/1188913,
year = {2007},
issue_date = {January 2007},
publisher = {Association for Computing Machinery},
volume = {50},
number = {1},
issn = {0001-0782},
journal = {Commun. ACM}
}
which compiles with errors (missing fields) and is the wrong type anyway. Using the acmart
@periodical and dumping fields unused for actual referencing we get:
@periodical{jcacm,
year = {2007},
volume = {50},
number = {1},
journal = {Commun. ACM}
}
That errors on compile (I'm using Overleaf and acmart
1.9.2) for having no title and for no editor or organization. This does work:
@periodical{jcacm,
year = {2007},
organization = {Association for Computing Machinery},
editor = {Diane Crawford},
volume = {50},
number = {1},
title = {January 2007},
journal = {Commun. ACM}
}
Note that if both editor and organization are supplied, only editor is used. I had to trawl the magazine's front-matter to find the editor: most people might want to just use the org name instead, being less effort.
Now, at last, the point about styling the issue number. The default ACM-supplied code is:
volume = {50},
number = {1},
or we can substitute an 'issue' field for 'number'
volume = {50},
issue = {1},
or leverage the fact (uncodumented formally) the 'volume' data is used verbatim
volume = {50 Issue 1},
This, on order as above, output like:
Diane Crawford (Ed.). 2007. January 2007. Commun. ACM 50, 1 (2007).
Diane Crawford (Ed.). 2007. January 2007. Commun. ACM 50 (2007).
Diane Crawford (Ed.). 2007. January 2007. Commun. ACM 50 Issue 1 (2007).
So whilst an 'issue' field works in some types, it doesn't get used at all in ACM's version of @pereiodical
.
Now, compare this with the first two lines of content on the Issue's page at DL.ACM. Line #1 uses "Vol. 50, No. 1" and line #2 uses "Volume 50, Issue 1". The first is akin to variant #1 above, and the second to variant #3. Going with variant #1 makes most sense as it doesn't need editing of the 'volume' field which might mess up use of the same code for other output (publisher) styles.
So unless/until the ACM steadies on a stated preference, close enough is probably good enough for referencing. Sigh.
One other ACM BibTeX 'gotcha' is access dates for online references. natbib pre-dates the we so has no notion of URL-based online resources. acmart
maps @online
to @misc
type but doesn't support the now general use of the urldate
field for the access data. Instead, ACM accepts such dates only a custom field lastaccessed
. An alternative hack is to put the access dates in the 'note' field.
Hopefully that saves some others a lot of wasted time trying to fix their BibTeX for ACM submissions.
@Book
entry.@article
or@proceedings
for this entry@proceedings
won't help here, since it also is formatted as a book volume, and disallows both volume and number inabbrvnat.bst
. And@article
isn't ideal either, since it expects an author field, not an editor field.