A Classical Dictionary

November 1, 2022

Thanks to the volunteers at Distributed Proofreaders, the 1904 edition of A Classical Dictionary by John Lemprière is now available in the Project Gutenberg library. The complete title, A Classical Dictionary containing a copious account of all the proper names mentioned in ancient authors with tables of coins, weights, and measures used among the Greeks and Romans and a chronological table, shows just how comprehensive it is.

Bust of Homer (c. 1st Century A.D.), Musée du Louvre

Lemprière (1765-1824) began work on the Classical Dictionary in 1786 while a student at Pembroke College, Oxford, possibly inspired by the ground-breaking Dictionary of the English Language compiled by fellow Pembroke graduate Samuel Johnson. Lemprière published the completed work in 1788 under the title Bibliotheca Classica. For over 200 years, it has been an essential reference work, not just for teachers and students of the ancient Greek and Roman classics, but also for novelists, journalists, playwrights, and poets. John Keats – whose poetry is filled with classical allusions – is said to have known the book almost by heart.

The study of classical literature has long been considered a fundamental requirement to understanding the development of our modern Western culture. The lack of classical studies in recent years leaves many feeling inadequate to the reading or study of classical literature. A Classical Dictionary is the perfect companion for those who are interested in a self-study of classical authors like Homer, Aeschylus, Aristophanes, Euripides, or Sophocles. When I prepared the e-book version, with the bountiful help of fellow DP volunteer Stephen Rowland, I took the liberty of expanding most name and title abbreviations to their full commonly known names, and changed many Latin abbreviations for books, chapters, lines, etc., to their common English abbreviations, to improve ease of reading.

A Classical Dictionary identifies and explains the plethora of Greek and Roman deities with their alleged authority and powers and the myths surrounding them. Names of rivers, cities, and regions are identified, when possible, with 19th-Century names and descriptions.

With this dictionary, you can travel along with Jason and the Argonauts in the Argonautica of Apollonius of Rhodes; learn how Helen of Troy’s abduction sparked the Trojan War in Homer’s Iliad; or follow Odysseus on his 10-year journey home after the Trojan War in Homer’s Odyssey. It will bring to life for you the Greek tragedies of King Agamemnon, Orestes, and others, or enable you to study the Roman histories by Julius Caesar, Josephus, Tacitus, and many more. Open your horizons now to these ancient works that have had such an impact on the development of today’s society.

This post was contributed by Rich Hulse (BookBuff), a Distributed Proofreaders volunteer who post-processed the e-book version of A Classical Dictionary.


Čħāṛᾀςŧέř ♭ῧįłďĭñġ (Character Building)

June 1, 2021

Editor’s Note: This post contains some uncommon Unicode characters, some of which may not display properly on older systems.

In May 2020 the Distributed Proofreaders (DP) site moved over to using the Unicode UTF-8 character base. “This is a very major change,” said General Manager Linda Hamilton. “This move has been a long-term objective for many years.” (For more information on this huge improvement, see the DP Wiki article Site conversion to Unicode.) Now, instead of being limited to about 200 assorted letters, numbers, and squiggles, DP has over a million to choose from.

We started modestly, providing a very few extra characters, such as the “œ” ligature often found in older books in words like Œdipus or cœlacanth. Soon though, DP site developers were picking up the pace, providing more and more additional character suites that Project Managers can assign to their projects. We rolled out three character suites for different European languages – with letters like ĝ, Đ, or ł; Basic Greek and Polytonic Greek character suites; and one for characters found in medieval books such as Ƿ or ȳ. In addition, Project Managers can now add individual Unicode characters to a project where they’re needed. These characters, which can include less familiar specimens such as ŧ ꝓ ᴚ ♅ ◘, show up in a “Custom” character suite on the proofreading screen.

All Greek to us

How does this really benefit our work in DP? Mainly, the Unicode-based encoding allows us to support languages that use characters outside the “Latin-1” character suite, which was what we had available before then.

Let’s take one important example: Ancient Greek. Why important? Because many of the books we work on, from the 19th century or before, do contain Greek words or whole passages in Greek. The writers of the time took it for granted that readers of the more scholarly type of book would have learnt Greek (along with Latin) as part of their education.

We reported here a few months ago about how DP handled Grote’s History of Greece, a monumental work with thousands of footnotes containing Greek text. Much of the work there fell to the Post-Processor, the person who prepares a project for final publication after it has all been proofread. With Unicode, the proofreaders can have a share of the fun!

Formerly, the proofreaders didn’t have the use of Greek characters. To represent the text during proofreading, a roundabout process was necessary in which proofreaders produced a transliterated version of the Greek written in our familiar Roman alphabet, like [Greek: mêde nein mêde grammata], to be transformed back into the original Greek – μηδὲ νεῖν μηδὲ γράμματα – by the Post-Processor. But now, the proofreaders can produce a correct text, drawing on a complete set of Greek characters. This is how the relevant part of the proofreading screen looks for a project that includes a Greek character set:

Asking proofreaders to work with Greek letters is also more practicable now that Optical Character Recognition (OCR) software has become better at reading Greek. Take a look at what OCR made of a page of Greek in 2005:

Looks like the book was written in Klingon doesn’t it? Now compare this, from 2020:

Still far from perfect, but good enough that proofreaders don’t have to retype the whole thing from scratch. Using the expanded character set, they can now correct the Greek text coming from OCR, just as they correct text in their own language.

The Mercury goes up

It’s the same with other types of characters. If proofreaders meet an unfamiliar letter in a medieval book, instead of typing [yogh] (for example), they can now input the actual letter ȝ. And we continue to add more character sets to meet the needs of our varied projects. Among recent ones is a set of characters used in Romanized forms of languages such as Arabic, Hebrew, and Sanskrit, so we can reproduce accurate transliterations of names such as ʿAlaʾuddīn or Mahābhārata or Viṣṇu (which previously had to be proofed as Vi[s.][n.]u). There’s also a “symbols collection,” including astronomical, zodiac, apothecary, and music symbols. With this collection, if we’re proofreading an astrological book, instead of [Mercury] we can now simply add ☿. Recipe for a bygone apothecary’s potion? Not [**ounce], but ℥. And so on.

So with Unicode, proofreaders know that someone else won’t need to come along and change all the awkward symbols later. Now they can do the whole job and produce a precise digital version of the original page, no matter what characters are on it!

This post was contributed by Neil M., a Distributed Proofreaders volunteer.


%d bloggers like this: