Almighty God! The children of a democratic nation raise their pretty damn-well armed hands to you from every quarter of the world (some of them just keep inexplicably exiting the country). They cry to you from great plains and snow-capped peaks, from rising waterways and sinking dessicate valleys. By the blood of our people fallen in battles for liberty and justice, deliver us O Lord!From the profane little hands of fools, deliver us O Lord!From the darkness of ignorant minds, deliver us O Lord!From the superficial inanity of wealth without depth of character, deliver us O Lord!From intolerance and hatred bred of xenophobic fear, deliver us O Lord!From two-faced reactionary hypocrisy, deliver us O Lord!From intemperate rhetorical ineptitude, deliver us O Lord!From silly narcissitic speachifying, deliver us O Lord!From sexist pus*-grabbing boasters, deliver us O Lord!
There does not appear to be any English idiom “to scare sparrows,” which is in all the existing English translations that I have been able to have a look at & something that the U-man says he was doing as a government clerk in the very first section of Part I. I am still trying to figure out whether there was an idiomatic expression to that effect (as he puts it пугать воробьёв напрасно) in Russian 150 or so years ago. One Facebook friend suggested гонять голубей, but it seems not to be a metaphor and is merely what pigeon owners do when they let them fly and then direct their circling and swooping in formation, by means of whistling, hand waving, or some other form of signaling.
At first I was bothered by the “in vain” idea, but now I understand that as the opposite of chasing them away for a particular purpose, as in they are eating my garden so I need to frighten them. In this case, he was just doing it because he got some pleasure out of it and was consoling himself by means of it. I am just a tiny bit tempted by the idea of inserting a definite article before the word sparrows, which would give the entire passage a very different sense.
My friend Val Vinokur points out that in his Brothers Karamazov, Dostoevsky has one of the boys throw rocks at sparrows at Iliusha’s funeral. I find the idea that the two passages might be distantly related by means of a species of bird, the sparrow no less, quite appealing.
The whole passage, trimmed a bit for clarity, goes
…сознавал в себе, что я … только воробьев пугаю напрасно и себя этим тешу.
Another Facebook friend did a yandex search (“because this is just so interesting”) and found not a set phrase but lots of entries for “как отпугнуть воробьев” (how to scare away sparrows). She also notes that “воробьиное пугало” translates as a scarecrow. This makes me wonder if maybe “scaring crows in vain” might not be a good option. It is definitely more concrete, and the tie-in to the scarecrow is rather nice. But crows are large and a bit scary, while sparrows are little and cute, even if they’re annoying when they’re devouring your blueberries.
My colleague Maria Shardakova, Director of Russian Language Instruction at Indiana University, hears in this expression echoes of a whole class of idioms:
Стрелять из пушек по воробьям = firing at sparrows with a cannon (overkill)Старый воробей and, later in the 19th century, Стреляный воробей = a rigid, uncompromising person and/or an experienced person, someone you can’t fool [Стреляного воробья на мякине не проведешь]
We’ve obviously stumbled onto a rich source of metaphorical expression, and Dostoevsky’s usage must be resonating within a larger aura of “the word,” as Bakhtin would later put it, except that here it is rather the bird.
It also occurs to me that we might have come to accept this scaring sparrows phrase at least in part because of the widespread availability of this work and the consistency with which translators have rendered this phrase, even if “I was just scaring sparrows in vain” is not immediately understandable in English and might even strike someone unfamiliar with the text as a rather odd notion. Perhaps this speaks to the power of translation in shaping the reception of a work along certain lines and with certain attitudes and ideas associated with it. I’ve toyed with chasing pigeons (the phrase I mean), and someone suggested cow tipping as an option, but while this last expression implicitly conveys petty maliciousness, it is far too deliberate and intricate to stand in for chasing little birds, which has something quite childish about it, an impression re-enforced by the next line in the text.
Here’s what I’ve decided to go with for now:
I was aware at every instant, and even at moments of the bitterest bile recognized inside me with shame, that I was not only not a malicious person, I wasn’t even an embittered one, and I was merely frightening sparrows to make myself feel better. I would be frothing at the mouth, but just bring me some kind of doll, give me a little tea with sugar, and I’d likely calm down.
I turned in the manuscript. I TURNED IN THE MANUSCRIPT!!! It clocked in at a bit over 400,000 words. I’m not sure what that will mean in terms of pages. Probably more than a thousand. This will depend on the editing process. But the main part is done.
I got a haircut on Saturday, and Ally asked me if I had done anything to celebrate. The question was natural but also a little unexpected. Well, no, nothing at all. Nor do I think any single thing–a dinner? a weekend vacation?–would adequately mark having completed the work. Turning it in feels good of course, but it doesn’t feel like the end at all. There’s editing and promotion work to do, the latter being the sort of thing that really never ends, and there are so many projects that have been simmering while this one was on the front burner. I am anxious to get back to them.
First up is breathing and stretching, which feels right at the moment. But while I breathe and stretch, I’m also thinking about the next two presentations I’ll be doing, in about a month at the annual AWP conference in Tampa, Florida. One panel is on word play in translation, and I’ll likely use examples from the just completed thing I worked on, for which examples are ready. The other is on the theme of translation and exile, and there I’m considering a brief exploration of the sort of self-othering, internal travel, ethno-linguistic exile from one’s “own” language that takes place when one translates, especially when one translates a lot, many short works, fewer long ones, or one big monster of a book. I suspect this is something that happens to people who learn to love a foreign culture and begin to feel estranged from their “own.” Non-translators must also know it, so figuring out what is specific to translation in this scenario will be a question to answer.
Playing with words is part of this, too, of course, so the two topics are likely to be connected in my presentations. I plan to practice them here in a few preparatory posts, so anyone who ends up being there may end up knowing what I will say before I actually say it. The AWP format does not really allow much room for expansion, and while the entire conference is focused on writing and writers, actually writing one’s comments and thoughts down and reading them to the audience is discouraged. Maybe this is ironic.
First, however, I’ll be trying to catch up on the many things I’ve let myself get behind on. And stretching and breathing of course. I invite you to join me.
I’m in the revisions stage now, and going back through an earlier section, I found a parenthetical note to myself that says: “no way, samovoz,” and then the page number in the hard copy.
The English passage in question is this:
No one saw him as he was leaving, and no one knew when did so. But he left in time, when it was still possible to take one’s own car to Zagreb and onward, to who knows where.
The time in question is approximately 1944. The “he” in question is a high ranking Home Guard officer from Croatia, stationed in Sarajevo, which means he was watching the political landscape carefully to figure out when he would need to escape, as the Independent State of Croatia began to collapse. The word samovoz is where I’ve got “one’s own car,” which is not much of an attempt, I realize, to convey all the nuance of the Croatian word. The problem is that it was a neologism for car under that particular regime, created probably around 1941, as the Independent State of Croatia itself came into being.
I have toyed with three or four different possible ways of sneaking more of the ideological content in somehow. While it was probably a German car, calling it a “fascist car” seems odd and might create more confusion than it’s worth. Creating some sort of Orwellian neologism in English might be fun, but that too would likely put too much emphasis on what is, in effect, a subtle passing comment by the narrator-author, which serves to situate the text historically. It could also imply a bit of the officer’s own viewpoint through the use of the word he might have used.
This is one I think I may have to let go.
I was once accused by a translator colleague of bringing down the going rate for translation by doing it when I had another job. This person had no idea what I charged or did not charge for doing the work, and perhaps she was angry about something else, but I remember distinctly that her comment had come after I made a statement in some online forum—this was over a decade ago and I no longer remember what the forum might have been—about my being able to choose the work I wanted to do and generally take my time in doing it. What she apparently intimated from this was that I was somehow taking the work away from someone else by agreeing to do it for less because I had a steady job as a university professor.
This is rather a sore spot among translators, more so, I think, than among fiction writers or poets, who generally understand that it is not really possible for emerging authors in those genres to make a living on the basis of the writing alone. Even after fiction writers have published a couple of books, unless they magically begin to sell many many copies, which is impossible to predict and also rare, they will almost always still need to keep their teaching job or whatever other job they’ve got to pay the bills. Translators tend to think about this differently, however.
There are actually two parts to this sort of criticism from freelance translators towards those of us who have academic jobs. Translation for us, so the criticism goes, can be part of our academic dossiers, our promotion files, our curricula (plural) vitae. We can engage in it without caring about the money we get paid for it because it is part of this other domain and we’re being compensated on a very different basis, not for the work itself but for having done the work, a bit like the future anterior tense, which skips over the present and time travels to some future moment for accomplishments that have yet to be attained, all without ever leaving the present. “When I will have completed all these things, I will be a successful academic,” and so on.
This sort of imagined reward for translations performed in the academy may or may not be true in all cases. Much depends on the institution and the nature of the dossier, but it is true that in some institutions and for some faculty members, artistic translation can form a part of such a dossier and be counted somehow, whether as scholarly or as creative work, or perhaps as something in between. And so, in our protected and self-serving manner, to go back to the criticism, we are expanding our research profile all while taking work away from those who really need it and are devoted to it. This is the criticism, not always stated in such a bald form, but implied or merely suspected, for the most part politely (translators are nice).
I suspect that this quiet criticism, which has lurked in the back of my mind ever since it was directed so uncharacteristically directly at me many years ago, has tended to make me shy away from projects that might in fact be appealing to and needed by freelance translators. My personal rule has tended to be only to take on work that I thought was unlikely to be translated if I didn’t do it. This has meant, for the most part, non-commissioned projects that I needed to research and then pitch to publishers. And that has meant probably not genre fiction (though I suspect I would enjoy translating some pf those genres), also not popular or well-known authors, and mostly works on the experimental side, unusual somehow, highly literary, sometimes quirky or idiosyncratic. Luckily, I also enjoy such works.
There are big advantages to this way of translating from a scheduling standpoint. For one thing, generally no one is waiting for you to finish besides your own internal critic. And that means that you can spend a lot of time and energy on the project at hand without worrying about the dreaded deadline. You can also only work on projects you find attractive and worthwhile from an aesthetic standpoint or a political or theoretical one. You can also stop working on something if it begins to ring hollow somehow, or if your views about it or about life change. These are enormous freedoms, and I don’t think I ever took them lightly.
My current project has not been like this, of course. It was commissioned. It could have been translated by someone else. It has a deadline (had a deadline, then another, now it has what I hope will be the final one—next month) from a publisher with a strong list and an eye for high quality works. The exception has both proven the rule and reinforced it. I plan to go back to the rule after this, with a clearer sense of the privileges and freedoms I enjoy in approaching translation the way I generally have approached it, without rushing too much, thinking about the work carefully, selecting on the basis of quality and what I suspect I can do well, if not to say what I will have done well afterward.
Let this serve as a new year’s resolution then, and a sincere wish for anyone else who might see the work, the vocation, the calling to translate as the privilege that I do.
My local vet once referred to her dog, which was about to have a litter, as a bitch, and I thought nothing of it. Or rather, what I thought was that she, the vet, was using the word correctly and also perhaps somewhat provocatively. She, the vet, is also a somewhat unusual person, uses crystals and homeopathic remedies in her practice, and this too seemed to corroborate my dim feeling that someone else in the same circumstances might not have used that particular word. The context was clear, so it wasn’t that terribly provocative, and there was no chance that anyone would have confused her use with regard to a female dog about to have a litter of pups with using the word to refer to a female person. The provocation in this case, if I’m right in hearing it in her usage, was about using the right word for the circumstances and refusing to change her word choice just because some people today might not use the word under any circumstances for fear of being thought misogynistic. Enter translation, where the specific term for a female dog in another language might not be so loaded as the English term “bitch.” It might be loaded, in fact probably is loaded, but is also very likely not loaded in the same way.
Translationese would tend to soften and explain, and so “female” would likely rise to the surface as the best option. And of course as an isolated case, in the midst of, say, a long prose work, using the word female would not likely be seen by anyone but the most self-righteous language police enforcer as problematic at all. It would be akin, I think, to finding the right idiom for something conveyed in a very specific way in the source language, for instance, “to stand someone up” for the French poser un lapin à quelqu’un. The French phrase uses the words “put” and “rabbit” in a very distinctive way, but as long as the “putting” and the “rabbit” are not thematically relevant (an interpretation the translator would need to decide on), it would not be a terrible loss to substitute “standing” and “up.” On the contrary, this move would create other interpretive avenues to English language readers, enriching the text rather than impoverishing it. This is an aspect of the “remainder” that several translation theorists have commented on. And if the text were older, something from the nineteenth century, for instance, again there would not be much of a problem. Readers would tend to read with a principle of charity, understanding that many of the contemporary associations we might have with words would not apply to a book from a hundred years ago or more. If the story in question is both about rabbits and contemporary, however, then all bets are off.
And so in a story about dogs that take on human characteristics, a story like the very last chapter of the 2013 novel Kin, which is entitled “Sarajevo Dogs,” what is the right way to consider the use of the quite specific word “bitch”? In an earlier section of the same book, my author uses bees as the human surrogates, and bees too have their own very specific lexicon, with drones and workers and queens. Now “queen” might begin to take on some of the complicated social and political implications that “bitch” immediately conjures, but the context is clearer somehow, and this kind of slippage seems less likely. Is it because bees are not mammals? A female dog (bitch) has nipples, after all, but a queen bee is an abstraction, almost a metaphor.
At this point I am leaning towards “female” because “bitch” seems more of a distraction and because the uses of the term kuja or, even more, the diminutive kujica (little bitch?) do not appear to be laden in this text with the associations of the English term. This is my interpretation, of course. I am also aware, however, of my own reactions in reading the work, which become much harsher towards it if I allow for the possibility that such bitchy associations might be intended by the author. I don’t think they are there, but I also recognize that I do not want them to be there. And given the choice, I prefer not to have them in the English version. I am of course thinking of audience here, so this strategy can be understood within a rhetoric of translation, which I have written and published about elsewhere, most recently here.
I am getting close to the end of this translation and feeling a bit light headed.
I don’t think I wrote much about the trip I took in September to Zagreb, to speak with my author, and then to Sarajevo to walk through the areas he writes so much about. It feels like a long time ago now, but I keep seeing the places as I translate lines that refer to them. It has helped a lot, since I had never been to Sarajevo before, and while I could translate the words, I really did not have a feel for the spatial dimensions and so much more that is simply implied.
The backache is nearly constant now, as the distinctive feature of translating prose works makes itself felt. So this is what it feels like to have translated over eight hundred pages of a single book with a little under two hundred to go. I wonder if the ache isn’t at least partly from the anticipated remainder, a little like one feels tired sometimes because of the list of things to do rather than because of the things one has just done. In fact, isn’t there more often a feeling of elation rather than fatigue at the end, after one has finished with something long and taxing? I suspect that will happen here too.
Based on what my author says about Sarajevo, I picked the right month to travel there. He has long passages of fog, mist, smog, snow, and ice, all of it rather grimy and dark, for the rest of the year. The trip also helped me to feel the pressure of the hills he often refers to, the central spaces, the Miljacka River, the street and general area where he spent a number of years as a youngster, especially its relative remoteness and insularity despite being a short, even if rather steep, walk to the center of town.
I was surprised to find it referred to as Šepetarevac (with the first letter as a š instead of as it ought to be, a plain s) in the first book by Jergović that appeared in English, Sarajevo Marlboro (Archipelago Books, 2004), especially as the name is emphasized so much. It has to be a mistake. I suspect mine will inevitably have some, too.