2

What's the shortest abbreviation for a full date (day, month, and year) recommended by the Chicago Manual of Style?

I know CMOS recommends against all-numeral dates, so I'd rather not use those. (I know that it says that, when absolutely required, one should follow the ISO standard: "YYYY-MM-DD".)

I've seen it recommend "Mon. D, YYYY" (e.g. "Jan. 1, 2014"), but I'm not sure if that's the shortest date format it recommends. For computer usage, it can still be pretty long.

  • @Mick There seem to be various questions pertaining to style manuals here: english.stackexchange.com/questions/tagged/… . Is there a better place for it? Where? It should be noted that this is about representing dates in English, not in general. – Tin Man Nov 23 '17 at 11:20
  • Sorry. I read CMOS as Complemetary Metal-Oxide on Silicon (i.e. storing dates in computer memory). Close vote retracted. – Mick Nov 23 '17 at 11:25
  • Even if one does the research and finds an answer (if one is available), it's a matter of opinion whether CMOS trumps or is trumped by other style guides. – Edwin Ashworth Nov 23 '17 at 21:51
  • @EdwinAshworth I'm asking about CMOS specifically because it's the style guide I'm following. – Tin Man Nov 24 '17 at 8:16
  • I'd say that the proper place to ask about CMOS recommendations is at CMOS. – Edwin Ashworth Nov 24 '17 at 11:13
3

The Chicago Manual of Style's treatment of abbreviated dates addresses two aspects of the subject: informality and ambiguity. The guideline in the sixteenth edition (2010) that you allude to in your question mentions both of these aspects, but it focuses primarily on ambiguity:

6.106 Slashes with dates. Slashes (or periods or hyphens) are used informally in all-numerical dates (e.g., 3/10/02), but this device should be avoided in formal publications to prevent ambiguity: Americans usually put the month first, but other countries do not (e.g., Canadians and Europeans put the day first). If an all-numeral format must be used, use the ISO standard date format (year, month, date, in the form YYYY-MM-DD; [cross reference omitted]).

Evidently, Chicago views the all-numerical slash style of date writing as being informal—which may or may not create a problem in tone, depending on how formal the surrounding text is—but the more serious problem from CMOS's perspective is that readers may not be able to tell whether (for example) 4/5/2017 refers to April 5, 2017, or to May 4, 2017.

A subsequent CMOS guideline suggests the ISO format (again) but also other unambiguous short forms:

9.36 All-numerical dates and other brief forms. ... When quoting letters or other material dated, say, 5/10/03, a writer must first ascertain and then make it clear to readers whether May 10 or October 5 is meant (not to mention 1903 or 2003). In text, therefore, the full date should always be spelled out [cross reference omitted]. In documentation and in tables, if numerous dates occur, months may be abbreviated, and the day-month-year form, requiring no punctuation may be neater (e.g., 5 Oct 2003).

In this guideline, although the imperative to avoid ambiguity again receives attention, the governing idea seems to shift to formality versus informality. After all, there is nothing ambiguous about the date 5 Oct 2003—and yet CMOS endorses its use only "in documentation and in tables" while insisting that in main text the full date always be spelled out in full. The "therefore" that CMOS inserts before making its formality-based recommendation is, therefore, clearly specious. Nevertheless, it is CMOS's advice, so if you are following that style guide, you had best reconcile yourself to spelling out dates in main text and limiting your use of short forms of the type "5 Oct 2003" to notes, tables, and bibliographical entries.

Finally, CMOS identifies three alternative short forms for the months of the year, as follows:

Jan., Feb., Mar., Apr., May, June, July, Aug., Sept., Oct., Nov., Dec.

Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec

Ja, F, Mr, Ap, My, Je, Jl, Ag, S, O, N, D

CMOS offers the following assessment of these three systems:

10.40 Months. Where space restrictions require that the names of months be abbreviated, on of the [three preceding] systems is often used.The second and third, which take no periods, are used respectively in computer systems and indexes of periodical literature. In formal prose, Chicago prefers the first.

Once again, opposition to perceived informality (not ambiguity) leads Chicago to oppose using abbreviated months in main text and, indeed, anywhere else not excused from the normal rule owing to "space restrictions" (which in practice usually refers to tables, charts, infographic labels, footnotes, and bibliographies).

To return to your original question, CMOS offers the following style guidelines for handling dates:

1. In main text, always spell out the month and all four digits of the year: January 1, 2014.

2. If you must use an all-numerical date format, follow the ISO standard YYYY-MM-DD format: 2014-01-01.

3. If space restrictions (in tables, charts, notes, etc.) require you to abbreviate the month, you may use 1 Jan. 2014, 1 Jan 2014, or 1 Ja 2014—but Chicago prefers the first of these styles.

It is worth emphasizing that Chicago cites (at 10.40) the periodless "1 Jan 2014" format as the one favored "in computer systems"—so if you are using dates in the context of computers, you might follow CMOS's hint and adopt the "1 Jan 2014" format as more appropriate to your particular context than the "1 Jan. 2014" format would be.

  • Am I right in saying that CMOS doesn't allow two-digit years? E.g. if I wrote "Apr 4, '17", it wouldn't be right? – Tin Man Jan 9 '18 at 8:53
  • 1
    @TinMan: Chicago, 16th ed., offers this guideline: "9.31 The year abbreviated. In informal contexts, the first two digits of a particular year are often replaced by an apostrophe (not an opening single quotation mark). [Examples:] the spirit of '76 [and] the class of '06[.]" However, I imagine that you aren't keen to introduce a string of informal-sounding three-character years of the form '01, '02, '03, '04, ... when you could have a full and formally acceptable years of the form 2001, 2002, 2003, 2004, ... by adding just one more character to each character string. – Sven Yargs Jan 10 '18 at 2:12
  • Thanks for that. In fact, I might actually go this route. It's for use in computer systems and, believe it or not, every pixel counts. It's also not just about character count, but rather character width—an apostrophe is much narrower than a numeral. – Tin Man Jan 10 '18 at 19:38
  • @TinMan: You should be safe for the next 81 years, anyway. I have vivid memories of the turmoil as the year 2000 approached, when countless computer date fields that limited the year designation to two digits couldn't properly handle the shift from ... [19]97, [19]98, [19]99 to [20]00. But obviously 2100 is far, far away. – Sven Yargs Jan 10 '18 at 20:36
  • Thanks. That's not gonna be a problem for this particular use case. – Tin Man Jan 10 '18 at 21:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.