Why the Book of Job Proves So Difficult to Translate

Having just finished rendering the book of Job into English, Edward Greenstein explains the great challenges it poses for translators, and the reasons for its obscure vocabulary and difficult syntax. Greenstein distinguishes the book’s framing prose narrative (the book’s first two chapters and its final eleven verses) from the poetic “core” in the middle, made up mostly of the conversations between Job and his friends:

[E]ven a cursory reading by a competent Hebraist will reveal that the book is composed overall in a peculiar Hebrew. The poet or poets responsible for the dialogical core of the work make frequent use of foreign language in order to lend verisimilitude to the conceit that the speakers are not Israelites but Transjordanians.

[Both] the prose writer of the frame tale [and] the poet (who may be one and the same) seek to set the story and dialogue in the period of the Hebrew patriarchs, and so they make use of terms and names associated with the biblical literature conveying that era and certain archaic or pseudo-archaic linguistic forms. The poet invents Hebrew words and features, sometimes to project an aura of Aramaic and sometimes because, like Shakespeare and other virtuosos, he likes to play with language.

Job is [also] a highly intertextual work, in which the interpretation of a word, phrase, or image may depend on the identification of a source—usually from the Hebrew scriptures we know and often from an earlier passage in the book of Job itself. The poet not only cross-references phraseology in the course of the back-and-forth among the interlocutors, but he twists the meaning of phrases through parody and deconstruction.

Read more at Ancient Near East Today

More about: Biblical Hebrew, Hebrew Bible, Job, Translation

How Columbia Failed Its Jewish Students

While it is commendable that administrators of several universities finally called upon police to crack down on violent and disruptive anti-Israel protests, the actions they have taken may be insufficient. At Columbia, demonstrators reestablished their encampment on the main quad after it had been cleared by the police, and the university seems reluctant to use force again. The school also decided to hold classes remotely until the end of the semester. Such moves, whatever their merits, do nothing to fix the factors that allowed campuses to become hotbeds of pro-Hamas activism in the first place. The editors of National Review examine how things go to this point:

Since the 10/7 massacre, Columbia’s Jewish students have been forced to endure routine calls for their execution. It shouldn’t have taken the slaughter, rape, and brutalization of Israeli Jews to expose chants like “Globalize the intifada” and “Death to the Zionist state” as calls for violence, but the university refused to intervene on behalf of its besieged students. When an Israeli student was beaten with a stick outside Columbia’s library, it occasioned little soul-searching from faculty. Indeed, it served only as the impetus to establish an “Anti-Semitism Task Force,” which subsequently expressed “serious concerns” about the university’s commitment to enforcing its codes of conduct against anti-Semitic violators.

But little was done. Indeed, as late as last month the school served as host to speakers who praised the 10/7 attacks and even “hijacking airplanes” as “important tactics that the Palestinian resistance have engaged in.”

The school’s lackadaisical approach created a permission structure to menace and harass Jewish students, and that’s what happened. . . . Now is the time finally to do something about this kind of harassment and associated acts of trespass and disorder. Yale did the right thing when police cleared out an encampment [on Monday]. But Columbia remains a daily reminder of what happens when freaks and haters are allowed to impose their will on campus.

Read more at National Review

More about: Anti-Semitism, Columbia University, Israel on campus