Category: Education

On-line Index at the Thesaurus Linguae Latinae

The bulk of the Thesaurus Linguae Latinae, as it appears on the shelf, consists of articles about Latin words themselves: an entry for nam, another for ponere, and so forth. In addition to these volumes that chronicle Latin’s many words, the Thesaurus also publishes an Index, a reference work for the various abbreviations used in Thesaurus articles and (more importantly) for the editions and sources of texts cited in the dictionary. As the preface to the Index explains:

The Index should enable every user of the Thesaurus to identify and locate all passages cited. Its abbreviations have been adopted by a large number of publications in the field of ancient philology. As an added benefit, the Index offers a concise overview of nearly all available Latin texts of antiquity, from both literary and non-literary sources. It may be useful, therefore, to consult the Index even independently of the Thesaurus itself.

The first edition of the Index was published in 1904. The present on-line version is based on the revised printed edition of 1990, edited by C. G. van Leijenhorst and D. Krömer. Here newly available texts have been and will continue to be incorporated, as will changes in any of the abbreviations used in citing works (you can also download the Addenda Indici here). New editions which do not require any changes in these abbreviations will normally not be mentioned in the Index. It is assumed that the reader is aware of them.

This summer, the editors of the Thesaurus have produced an on-line version of the Index, which has the double benefit of allowing easier updates and of facilitating access to this great resource. As the text above states, the Index is indispensable for deciphering the Thesaurus, but it can also be helpful to consult if you’re just looking for, say, a reliable edition of Apuleius or a quick summary of the works of St. Ambrose.

As is the case with the Thesaurus, the Index takes some getting used to: it uses its own conventions for alphabetizing, numbering, and so forth. (You can read an in-depth explanation of these conventions at the Thesaurus website.) To help scholars excavate its information, I’ve written up some basic tips here along with an example explanation of how to read the Index’s listings for Vergil, shown in the screenshot below:

The Index presents information five columns. The first three columns provide basic data about authors and their works: the first columns gives dates (if known), the second gives the name of an author or text as written in Thesaurus articles, and the third gives alternative naming conventions (in the case of changes during the compilation of the Thesaurus). For Vergil, the first column shows his birth in the year 70 (signified by the asterisk) and his death in the year 14 (signified by the dagger/obelisk). Using the information from the second column, we might cite a line from the Aeneid as VERG. Aen. 4, 134 or one from the Georgics as VERG. georg. 3, 13. (Note: Your browser may not have rendered the author’s name in small capitals. Also, the numbers provided in the second column of the Index are the final line/paragraph/locus of that particular work — e.g., the last line of the Aeneid is 12, 952.)

For those getting into the nitty-gritty of a particular text or author, the fourth and fifth columns may be of interest. In the fourth, one finds explanations of the sources and other relevant information about the texts, for example that the eclogae of Vergil are also called the bucolica and that the fragmentary text of the epistulae ad imp. Augustum is preserved in Macrobius’ Saturnalia. And in the fifth column, one finds information about the various (and most reliable) editions.

Like the Thesaurus itself, the Index conveys lots of specialized information for several authors, including cross-references to the Beuron Vetus Latina citations and relevant translations to and from ancient Greek works. To learn more about this more technical material and to see a list of abbreviations for frequently cited editions, consult the extended “Directions for Use.” But the simplified instructions above should give you a decent grasp of the Index and help you use it as an authoritative and comprehensive reference for the available Latin texts from antiquity.

news feed versus seminar table

I find nearly all editorial writing about waves of unruly campus activism frustrating because even the most regrettable and objectionable episodes are ultimately isolated events. Blips on the radar of American higher education, a system that includes twenty-plus million students attending nearly five thousand degree-granting institutions. Over at Crooked Timber, Corey Robin seems to share these frustrations about essays of this genre and their limited, un-representative subjects:

I’ve tended to stay out of these debates of late, in part because they mostly don’t speak to my experience of campus free speech. Our challenge at Brooklyn College has never really been how to keep speakers off campus; it has almost always been how to get them on campus.

I’m writing some thoughts about the topic here only because one recent essay spoke directly to my own anecdotal experience as a university educator. In an op-ed at the Wall Street Journal, Heather Mac Donald cites the Facebook protestations of Columbia students against the university’s Contemporary Civilization course as examples of the “tantrums” and “victimology complex” at the center of campus activism. Having taught four sections of this very class during my doctoral work at Columbia, I am struck by the disconnect between the vitriolic language of this virtual shouting and the unfailing civility of each and every student I ever taught in my analog, low-tech classroom. These outraged Facebook posts, in other words, in no way reflect the consistently mature, critical, intelligent discussions I witnessed among my Columbia undergraduates.

Perhaps this rift shouldn’t surprise me. It is obvious to anyone who has ever read Facebook, Twitter, or even the comments on Mac Donald’s essay that the technological ease and pseudo-anonymity of on-line writing brings out our least charitable selves. I imagine the hostility on campus catalyzed by social media is a phenomenon parallel to the technology-enabled “smug style” that pervades America’s mutually incomprehensible political parties.

Connecting the dots, Nicholas Carr explains in a recent essay at the Boston Globe how Facebook’s goal of “universal self-expression”

reinforces the idea, long prevalent in American culture, that technological progress is sufficient to ensure social progress. If we get the engineering right, our better angels will triumph. It’s a pleasant thought, but it’s a fantasy. Progress toward a more amicable world will require not technological magic but concrete, painstaking, and altogether human measures: negotiation and compromise, a renewed emphasis on civics and reasoned debate, a citizenry able to appreciate contrary perspectives. At a personal level, we may need less self-expression and more self-examination.

Civics and reasoned debate. Appreciating contrary perspectives. Self-examination. The well-honed, time-tested technology for effecting these outcomes is the seminar table, not the news feed.

But those who write fiery op-eds denouncing the excesses of campus culture continue to blame studious humanities seminars—rather than algorithmic feeds that reward bombast—as the engine of campus incivility. Mac Donald, with Columbia in her crosshairs, demands that professors “start defending the Enlightenment legacy of reason and civil debate.” What more, really, can we ask of the very educators who are already teaching Mill’s On Liberty, Plato’s Republic, and Tocqueville’s Democracy in America to over a thousand Columbia undergraduates every year? If the caustic Facebook posts she cites and my own intellectually robust classroom sessions are any indication, perhaps she should demand more defense of civil debate not from faculty but instead from Mark Zuckberburg and Jack Dorsey.

practicum: plain text notes and handouts

A recently sent some tips to a colleague about using plain text for typing up everything from lecture notes to seminar handouts to dissertations, and I thought it would be wise to re-post some of those tips here for other academics. While some of this advice will sound very techy—and admittedly, it is to a certain degree—it may be helpful for you if you share my frustration with Microsoft Word. Bearing that techno-disclaimer in mind, I write the following advice from the perspective of a humanist whose primary task is writing prose efficiently, whether for myself or others.

  • In my last two years of graduate school, I made a habit of writing all my teaching notes in plain text—that is, in a .txt file without any formatting. You can make such a .txt file by typing something up in Windows Notepad or NotePad++ instead of, say, MS Word or Apple’s Pages. Perhaps the most significant advantage of using plain text files is that any device can reliably read and edit them: your new laptop, the clunky desktop next to your department’s printer, your phone, your parents’ dusty Bondi Blue iMac. In New York, for example, it was very useful to be able to review and revise teaching notes on my phone whether on the subway, in the park, or waiting in line at the supermarket. This kind of portability is not possible with PDFs or even Word files.1

  • While your phone can handle .txt files much better than it can handle, say, a .doc or PDF, there will come a time when you’d like to distribute a document in a format more handsome than the Courier New typeface allows. That is, you’ll want to share files as Word files or PDFs. To help you here, you’ll want to download Pandoc, an incredibly useful piece of software written by John MacFarlane of Berkeley’s Philosophy Department. This software lets you convert pretty much any document type (text, Word, ePub, HTML, you name it) to pretty much any other document type.

  • Converting your .txt file to a Word document (for example) is straightforward. Open Terminal/PowerShell, move to the folder where you saved your .txt file, and run the following command:2

[code lang=text]
pandoc YourDocument.txt -o DocumentOutput.docx
[/code]

  • And you’re done! You should have a Word Document version of your original text file in the same folder.

  • A little bit of computer sorcery in these next tips, but: I love using LaTeX, a piece of software that produces beautiful academic documents even when faced with complex citations, strange typefaces (like Polytonic Greek), or mathematical formulas. If you’re familiar with LaTeX and already have it installed on your system, you can use Pandoc to create very nice PDFs quickly from your plain text files. For example, I produced this PDF of paper-writing guidelines for undergraduates from a plain text file with the help of Pandoc.

  • The section headers and footnotes in the above PDF were formatted with Pandoc’s extension of Markdown. Even if you are making a Word Document or HTML file instead of a PDF, Markdown is helpful for formatting your text with bold or italic characters (for example) using only the text editor on your phone or old computer.

  • To convert my text file of paper-writing tips into the PDF linked above, I include the following specifications at the top of my text file (including triple-dashes)…3

[code lang=text]

title: How to Write a Paper for Contemporary Civilization
author: Charles J. McNamara, Columbia University, cm@charlesmcnamara.com
date: July 2016
geometry: margin=1in
mainfont: Linux Libertine O

[/code]

… and then run the following command:4

[code lang=text]
pandoc document.md –latex-engine=xelatex -o document.pdf
[/code]

  • This is as complicated as I let things get for my own work. Again, the point is to facilitate writing and reviewing prose, whether notes or handouts, with whatever technology you have on hand. For more information on writing full academic articles with Pandoc and tweaking the appearance of your documents, see Kieran Healy’s extensive documentation at http://plain-text.co/.

  1. It’s helpful to keep these text files in Dropbox or some other cloud storage folder so that you can access them from anywhere. 
  2. The “-o” stands for “output,” and when you end the “DocumentOutput.docx” filename with .docx, pandoc automatically knows to make a Word Document. If you were to use “-o DocumentOutput.html” instead, pandoc would know to make an HTML file. Pandoc’s website has a detailed manual about the various options you can use. 
  3. The header here just passes arguments and variables to LaTeX. By including “geometry: margin=1in” you can force LaTeX to use the whole page. The title/author/date variables are responsible for the document header seen on the first page of the PDF. 
  4. I use the .md extension is for Markdown files, and any device (Grandma’s computer, your phone) that can read text files will be able to read Markdown files, too. –latex-engine=xelatex is important for rendering certain fonts (e.g., Polytonic Greek). I almost always use the Linux Libertine font (which you can read about on my Resources page).