Hatam Soferet

La vie soferet – proofreading with accomplices

2010-08-03T03:30:20Z

Well, that was fun. An afternoon at Hadar working with one of my ~~accomplices~~ apprentices on Elementary Proofreading.

No, I don’t really have apprentices. Just the occasional afternoon teaching here and there; the sort of thing that I would do more of if I had apprentices. Anyway, we were doing some sheets of a sefer that needed proofreading. It was the soferet’s first Torah work, I think, and the client, for doubtless good and valid reasons, had decided not to have a computer check.

The computer check, you remember, is the one that super-reliably checks that you’ve got all the letters in place – no missing vavs or extra yuds or homophones or accidental switches. Lacking that, apprentice and self have to do that job, which means checking each letter, several times, against the tikkun.

Me, I have my lovely scribomatic program to help me with that, but Apprentice hasn’t bought a copy of it (yet), so I was taking her through the old-fashioned method, reading each letter off the tikkun and checking it that way. First I read and she checked; then we swapped places and I checked while she read. We marked in pencil everything that seemed to need attention, and compared notes afterwards.

It’s very easy, when proofreading someone else’s work, to get into one of those superior “dear me, my daughter-in-law has dust on top of her bookshelves!” mindsets. Proofreading is an inherently critical process – it’s your job to look for mistakes – and accordingly I’m trying to get into the habit of, if I’m criticising, to turn it into a lesson – not “this is bad” but “here is how to improve this.” “This is pasul,” sometimes, but not “therefore you suck,” rather “here is how to make it kosher.” I didn’t have anyone to do that for me, so if I do it for other people, the world is a better place, right? So I was trying to model that for Apprentice, and I’ll also be sending an email version (with photographs) to the Soferet.

Apprentice is taking some sheets home with her to work on, and we’ll meet again and look them over in a few weeks’ time. The first thing she needs to do is do the Thing with the Tikkun; this is relatively easy. The more subtle details – is this kosher, is that kosher, what about this detail – she’ll have a go at, and we’ll meet again in a few weeks and see how she got on. If she was a full-time apprentice she’d do that with me checking in pretty often; as is, we’ll have to save all the checkups until we next meet.

Anyway, after several hours, I needed to leave the Apprentice and go buy shoes – my sandals are falling to bits on my feet, not good – but the Apprentice didn’t want to start driving to Boston in rush hour. So – we were at Yeshivat Hadar – I cast about the beit midrash, and propositioned a likely-looking person – one of those people whom you rather suspect would get a kick out of being asked to help – and left the pair of them sitting and doing the Thing with the Tikkun.

This pleased me rather. There’s me, with a fair bit of experience, leaving Apprentice, who has a little bit of experience, working with Yeshiva Girl, who has no experience fixing Torahs but can perfectly well read letters from a tikkun. And she’ll ask questions of Apprentice, who asks questions of me, and everyone moves up a step.

Except me because I didn’t find any sandals, but hey, can’t have everything.

Mirrored from hasoferet.com.

comments

Proofreading, part 30

2010-01-15T03:59:17Z

The very observant will note that this series has talked a lot about letters, but really not about layout at all. The reason for this is that while letter forms are relatively inflexible and easy to get wrong, layout is relatively very flexible and (these days) pretty hard to screw up, so it’s not part of the proofreading process.

If you were making a chair, you wouldn’t need to check that it had four legs; you’d know darn well if it didn’t have four legs. These days, layout errors for scribes like me are of that order of magnitude.

It was not always so. More about that in a week or two.

In the meantime, I will just note that I generally proofread a little faster than I correct, so the proofreading gets ahead of the correcting, and thus it was a couple of weeks ago that I was learning leyning in Bereshit, correcting in Shemot, proofreading in Vayikra, and writing in Bemidbar. Heh.

Mirrored from hasoferet.com.

comments

Proofreading, part 29

2010-01-14T03:41:21Z

I summarised my attitude towards women writing Torahs by saying that the full citizen, the adult male in good standing, may participate in the transmission of the community’s symbolic centre, and the adjunct classes of women, children, and slaves, may not; today, it is a matter of principle that women not be an adjunct class and therefore may participate on the same basis as men.

This is not how the language of halakha expresses itself, naturally. Halakhically, the issue is framed in terms of the mitzvah of tefillin – those who are Biblically-commanded and socially-accepted as tefillin-wearers may write the sacred scrolls; others may not. Women are not Biblically commanded to wear tefillin, therefore they may not write the scrolls.

It seems simplistic to say that in communities where halakhic validity and gender equality are equally indispensable, women do wear tefillin, and that said wearing is held by said communities to be equivalent to men’s. Simplistic, but when an immutable principle meets an overwhelming imperative, on some level the answer is simple. The community says in its actions “this is what we do, this is what we expect of people, this is how it’s going to stay” – and once that sentiment is in the heart of a community, we don’t wrench it out, so the halakha must perforce adjust to accept it.

You can’t run a religion like that, changing the rules of the society every time you sniff hurt feelings. This is a halakhic sledgehammer, and swinging it too freely will destroy the halakhic structure. But societies where gender equality is well-grounded and gaining demonstrate that gender equality does not render a society inherently unstable (on a century of evidence; give it another five centuries and we’ll be better placed to tell), and thus one may say with a fair amount of certainty that applying the halakhic sledgehammer to the principle of gender equality will not render the halakhic structure inherently unstable either.

We’ve got off the topic of proofreading rather, but there again, proofreading is the process that ensures the stability of the Torah text, which itself is symbolically the stability of the Jewish people, so it’s vaguely associated. Anyway, that’s about all I’ve got to say concerning proofreading at the moment.

Mirrored from hasoferet.com.

comments

Proofreading, part 28

2010-01-13T05:11:28Z

Most readers here, I imagine, live in countries where rights and responsibilities in the social plane are officially not apportioned with reference to gender. Broadly, this is because it is a matter of principle that women and men function as equal members of society. How well this actually plays out in practice is another matter, but in principle, that’s how it is.

It is then implausible to expect the religious plane to stand orthogonal to the social plane. To function as a full citizen in one plane and an adjunct citizen in another plane requires either a superhuman suspension of disbelief or an impaired existence in one or both planes.

This isn’t good for religion’s chances – if you’re used to functioning fully in a social plane, you’re not going to take kindly to being told you have lesser status in a religious plane. But further, it encourages the idea that the religious and social planes are and must be distinct. As someone who sees religion as an enhancement to, not a removal from, the social plane, this doesn’t work for me.

Like it or not, social climate filters into Jewish life, and in social climates which foster egalitarianism, there will exist egalitarian Jewish life, in which the idea of women as an adjunct class is in principle both redundant and repugnant. Given such a change in the makeup of society, it is not implausible for its women to write Torahs. Naturally there are communities in which women are, and are content with being, adjuncts, and certainly these communities shouldn’t have women writing their Torahs, but these are not communities I choose to live in.

The halakhic aspect to follow.

Mirrored from hasoferet.com.

comments

Proofreading, part 27

2010-01-12T04:16:31Z

Of course, people say “um, no actually” to me, being female. It wasn’t the handless guy’s fault he had no hands, it’s not my fault I’m female. He just didn’t have the physical makeup to write a valid Torah and that was too bad; I don’t have the physical makeup to write a valid Torah and that’s too bad also.

Really, I do know a lot of decent people who have to say “um, no actually” to me, and they do act like yesterday’s posited rabbi – feeling really sorry that he’s got to say “um, no actually” to this person who’s put in so much effort and so badly wants to be part of the community and it isn’t their fault they can’t participate through this activity.

So why’s it different? why am I expecting the handless guy and the Braille-writer to suck it up, while I go right ahead and write Torahs?

You could say I’m just a hypocrite, a case of “one rule for us, one rule for them.” Some people do say that. I see where they’re coming from.

Way I see it, women doing men’s things isn’t exactly a physical makeup thing, it’s about how gender affects one’s communal status. Women are barred from Torah writing in the context of societal strata; some classes of people may participate, some may not. In particular, the full citizen, the adult male in good standing, may participate in the transmission of the community’s symbolic centre, and the adjunct classes of women, children, and slaves, may not.

This is perfectly sensible as far as it goes, except that in our days it is a matter of principle that women not be an adjunct class.

Such a statement requires some unpacking. More on that tomorrow.

Mirrored from hasoferet.com.

comments

Proofreading, part 26

2010-01-11T03:42:55Z

Backtracking a bit to the experience of writing.

I talked about producing letters as not necessarily being writing. Specifically, embossing (the process of creating a shape by pressing up from the other side) isn’t really writing.

We might say: ah, but Braille is created by embossing, and today there are lots of people for whom writing in Braille is experientially the same as writing. So why couldn’t you emboss letters and make a Torah for the blind? At any rate, a Braille Torah?

Leaving the technical difficulties aside (rolling an embossed document into a scroll is asking for trouble), it’s an interesting proposal.

There’s a case recorded – I forget the reference, I’ll look it up if anyone cares deeply – where a guy with no hands wrote a Torah with the pen held in his teeth, and the Torah was ruled invalid, because holding the pen in one’s teeth is not what most people perceive experientially as writing.

The guy had written a whole Torah, remember. That’s a hell of a lot of work – I mean, it takes me a whole year, and I’ve got two perfectly good hands. He’s written a whole Torah with the pen in his teeth, and he’s got no hands – I would speculate that the rabbi who ruled his Torah invalid felt like a real heel. You couldn’t be any kind of decent person and feel really sorry that you’ve got to say “um, no actually” to this person who’s put in so much effort and so badly wants to be part of the community and it isn’t their fault they can’t participate through this activity.

But you’ve got to, and I think that’s also the case for Braille Torahs. Holding the pen in one’s teeth, or writing Braille, is definitely some people’s experience of writing, but that doesn’t mean it’s the cultural experience of writing, and it seems that that’s what matters here.

Ramifications of this attitude tomorrow.

Mirrored from hasoferet.com.

comments

Proofreading, part 25

2010-01-10T03:41:34Z

I also have to deal with a certain amount of, let’s say, cognitive dissonance. In my travels, I’ve given scrolls (usually megillot) I’ve written to various traditional-Orthodox types, and the response is, quite often, “Goodness me, this is very nice, very nice indeed…” until they discover that I wrote it. Then their opinion abruptly changes; suddenly it is not aesthetically pleasing, the writing is not nice, and so forth. This is a) obvious and b) tiresome.

A story by way of example. One of my proofreading go-betweens also sells Torahs, and once I collected a scroll from him – it’d been written in Israel and I was to take it to its new home after sewing on some rollers and other details.

Well, some colleagues and I opened up that scroll and we were horrified. The writing was appalling. By no stretch of the imagination could it have been described as kosher.

So back it went to Mr Go-Between, who insisted that it was completely fine. No problems at all, he said. 100% kosher, he said. He sent it back to us. We sent it back to him. Repeat a couple of times; he was adamant that this scroll was absolutely kosher with no problems at all.

Eventually he was persuaded to examine it in daylight, and he conceded that there were more than one hundred critical errors per column. Completely fine, hm? 100% kosher? No problems at all? Right.

Subsequent investigation revealed that the sofer had taken the commission despite his failing sight. He had written the scroll practically blind, and while that’s quite an achievement, it doesn’t make for a kosher scroll.

But we digress. This was Mr Go-Between insisting that a really dreadful Torah was totally fine. Later, I took him my scroll for scanning, and he insisted that the writing was deeply deeply problematic in assorted ways.

Clearly I’m not unbiased, but at least mine didn’t have a hundred critical errors per column.

I certainly have scope for improvement, but that seemed like some pretty intense cognitive dissonance to me. I just have to bite down and count myself lucky that he’ll deal with me at all. Oh, and watch out for my own biases making me behave similarly in other areas of my life – nasty experience, good lesson, anyway.

Mirrored from hasoferet.com.

comments

Proofreading, part 24

2010-01-09T03:30:05Z

Talking of inaccessible. This part of the proofreading process is hard for me to access. I don’t own the fancy software, not many people do since it’s so expensive (multiple thousands of dollars, I understand). Most people send their scrolls away to have someone else do the scanning part.

Well, that’s hard for me, because the people who have the software are all people who don’t hold with women writing Torahs. If I take my Torah to one of them and ask them to scan it, they refuse, saying they can’t have anything to do with it, it’s bad for their reputations, etc. Which I understand, but it doesn’t exactly make me leap for joy. So I send my work to someone who sends it to someone who sends it to someone and eventually it’s anonymised enough that it can go to the scanner without anyone directly violating anyone else’s principles or reputation.

Sigh; not the way I’d choose to work, given the choice, but until there are enough liberal scribes to make buying the software a sensible investment, it’s going to stay as it is.

Mirrored from hasoferet.com.

comments

Proofreading, part 23

2010-01-08T04:29:02Z

The misplaced expectation that a computer can infallibly check a Torah also touches on a deeper concept, that of the experience of writing.

What does it mean to write? is a question that has always been part of the Torah-writing rules. Could you, for instance, embroider the Torah? Is that writing? What about carving letters into plaster-covered monoliths? Embossing them onto metal headbands? What about printing? Jewish communal narrative recognises these processes as producing letters, more or less, but also recognises that this is not how people normally write: you wouldn’t embroider your account book, and if you were embroidering accounts you wouldn’t say you were writing. Experientially, producing letters is not necessarily the same as writing.

By axiom, the Written Torah has to be written, and if it’s going to be a proper written document, it needs to be properly written. It’s got to be produced by someone having the experience of writing, not someone simply having the experience of doing embroidery or whatever.

But for your average North American Jew,* the experience of writing involves a keyboard. It makes absolute intuitive sense that computers would feature in any act of writing, not excluding that of writing a Torah. Computers are how we write things. Handwritten material is positively extraordinary; the skill of penmanship is practically unknown. No-one would expect to see an embroidered book; similarly, people frequently assume Torah scrolls are printed – no-one expects to see a handwritten book. Intuitively, it makes a twisted sort of sense that the Torah should be typed.

Fortunately, we don’t take it that far; even though typing is the more common writing experience these days, pen-and-ink is still, culturally, the more authentic writing experience. Pen-and-ink is associated with real writing in a way that typing is not.**

Indeed, way way back in the days of the first Torahs when literacy was limited to an elite few, a Torah scroll – a written document – probably had an air of mystique about it simply because so few people could write, so few people could conceive of producing one. Nowadays also, a Torah has mystique by virtue of being written, because again so few people can write in this way.

An interesting example of history coming full circle, there. Writing the Torah starts as a skill limited to a small group of people; as literacy spreads but before printing is invented, writing sifrei Torah becomes less remote, such that some authorities even equate sifrei Torah with printed books containing Torah material. Then, once printing is ubiquitous, writing again becomes a rare skill and Torahs are elevated back into the inaccessible.

* By way of example, not by way of exclusion

** Which is one reason I’m not keen on silk-screening Torahs. Halakhically it’s justifiable – ink in the forms of letters is, technically, laid down onto the klaf by hand – but intuitively it isn’t right, because any fool knows that silk-screening isn’t really writing.

Mirrored from hasoferet.com.

comments

Proofreading, part 22

2010-01-07T04:25:12Z

Proofreading a Torah is a tremendous task, requiring much memory and data processing and demanding infallible accuracy. Computers, of course, have much memory and data processing ability, and are notoriously accurate. Having established that computer checking can be part of proofreading, one frequently hears the question “Why can’t the computer do it all?”

I think we’ve mostly answered that, under the heads of human error and technological limitations, but I find the question itself interesting. Why would anyone think the computer could do it all?

A child of my generation, it came as something of a surprise to me to realise that some people genuinely do think of computers as infinitely clever, infinitely powerful (Which kind of makes sense – when “the system” is down, utter helplessness ensues, so one might unconsciously infer that non-helpless states are only possible when the system is up). And if you see a computer as a magical mystery box that can do all sorts of things you couldn’t possibly do, I suppose it makes sense that you would think a computer could do a much better job of checking a Torah than you could, just like it can do a spellcheck better than you can.

Except that of course the computer’s spellchecking ability only goes so far, and you yourself still have to check for anomalies the spellcheck isn’t clever enough to spot – and computer checking of Torahs is just the same.

The computer is a good tool which gets most things right most of the time; it makes life a lot easier, can’t live life for you, and that applies just as much to checking Torahs as it does to anything else we do.

Mirrored from hasoferet.com.

comments

Proofreading, part 21

2010-01-06T04:23:21Z

Even this process, though, isn’t completely foolproof. Humans run the software, and as soon as humans come on the scene, there’s potential for human error.

If the various software operations aren’t applied properly – like forgetting to run the spellcheck on a document – the software won’t flag up problems because it won’t have looked for them. Perhaps the “is it there?” process on each letter of a column was run but the “is it kosher?” process accidentally wasn’t.

The computer needs human help to learn the writing, and perhaps the human isn’t paying attention. Perhaps the computer says “hey, human, what’s this?” and the human is half-asleep and says “vav” when he means “yud,” and a spelling mistake consequently goes unspotted.

Sometimes the software just can’t pick up on things. Very fine lines – the scanner might not pick them up; sometimes the presence or absence of a very fine line can be the difference between kosher and pasul. But we can’t (at present) scan to so high a resolution as to pick up on all these; the processing time would be prohibitive.

Finally, the letters are very slightly three-dimensional; a human, with stereo vision, can tell the difference between ink and shadow, and a scanner can’t always. Sometimes it’ll interpret a shadow as a crucial fine line, and report a letter kosher when it really isn’t.

So a scan is an excellent tool – I think it’s one of the finer syntheses of technological development and ancient ritual – but it does not replace all the other proofreading tools we use, and it is not a substitute for hard work and knowing your stuff. Few things are, really.

Mirrored from hasoferet.com.

comments

Proofreading, part 20

2010-01-05T03:13:54Z

The other form of computer checking involves much more sophisticated software, and further reduces the chance of human error. In the process we’ve just been talking about, the letters were fed to me automatically, but I still had to use my brain to identify them and see that they were kosher. In this process, there’s barely any brain involved at all.

In this process, the operator uses a hand-held scanner to get the columns of text into the computer. Then it is run through OCR software – very clever software, which not only recognises letter glyphs but can also be taught to handle variations in glyphs caused by its being hand-written. Because it is a computer, it can also be taught some of the laws of whether a letter is kosher or not, so it can apply those mechanically to each glyph and flag up any doubtful cases.

Finally, the OCR output is compared to a Torah text, and any discrepancies are flagged up along with the doubtfully-kosher ones. A report with all problems is generated and given back with the scroll to the sofer, who then goes through the list and fixes everything on it.

Scan report

Like this. Column 003, says the first entry on this report, which starts “Vayomer Adonai Elohim” – one comment. Line 21 (Bereshit 3:5), problem, thus: extra letter vav in the word “mimenu,” where it should say “…yodea Elohim ki b’yom akhalkhem mimenu v’nifkedu eineikhem…” and then in the picture you can see it’s got “v’mimenu,” for some reason or other.

I think I probably started writing the mem, got distracted mid-stroke, forgot I’d already started it, and started it over, but I don’t remember now.

Mirrored from hasoferet.com.

comments

Proofreading, part 19

2010-01-04T04:15:32Z

Erm, hem, Part 19 seems to have been exactly the same as Part 18, bit of overenthusiastic copying & pasting there. Normal service will resume tomorrow.

Mirrored from hasoferet.com.

comments

Proofreading, part 18

2010-01-03T04:06:50Z

Another rather pleasing thing about this sort of aural proofreading has to do with the shapes the letters make.

When writing, some letters make very pleasing shapes on the page – the taggin, or how they fit in with the other letters around them, that sort of thing:

It’s just nice.

And sometimes pleasing three-dimensional shapes as well, although I usually tone those down a bit for the sake of good artisanship:

Checking letters by listening, you aren’t so much aware of the letters’ aesthetic value relative to surrounding letters, only their kashrut status, but you do become aware of the shapes they make in sound relative to surrounding letters. I had never thought of the phrase ויבא אביו as having a pleasing shape, for instance, but when the scribomatic read it to me, vav-yud-bet-aleph-beep-aleph-bet-yud-vav, the symmetry there made me very happy. (The scribomatic beeps at spaces.)

Or: alef-tav-beep, hey-alef-tav-tav. Rhythm!

Or יוכבד דדתו לו לאשה – dalet-beep-dalet-dalet, nice, and then vav-beep-lamed, vav-beep-lamed.

Torah writing frequently surprises me with experiences I would never have thought to anticipate, and this was another of them.

Yes, I was proofreading Shemot when I was writing this post.

Not simultaneously, silly.

Mirrored from hasoferet.com.

comments

Proofreading, part 17

2010-01-02T04:17:52Z

A funny thing about checking the letters like this is that you completely lose track of where you are in the Torah.

When you’re writing, you say the words out loud as you’re going along. You’re going very slowly, so you might forget what was happening a few paragraphs before, but you know what’s happening in the part you’re writing.

When you hear the letters coming at you, one after the other, and you’re focusing on them as individual letters and not as words, as a string and not as a text, you don’t have that awareness. At least, I don’t. Try it with a friend and a lump of English sometime, see what you make of it. It’s very interesting, I think – yet another perspective on the Torah text that I wouldn’t have suspected was there.

Mirrored from hasoferet.com.

comments

Proofreading, part 16

2009-12-31T05:47:44Z

There’s still chance for human error though – misspeaking, mishearing, losing the place, saying “hang on a minute” when marking an error and needing to re-establish the place afterwards, going too fast and missing bits, going too slow and wasting time. Plus, it still takes a long time, and paying someone to sit there and read letters is expensive.

This is why I had a friend write me a program which plays the part of the Reader. He called it the scribomatic, which I find vastly pleasing. I have the Torah text in my computer; I copy and paste in the portion of text I want to check, and the scribomatic reads the letters one by one.

Now all I have to do is pick the letter out of the air, not find it in the tikkun, I’m only using a little bit of brain on “Is it there?” and I have lots of brain left over for “Is it kosher?” which means I can assess that more efficiently. When I want the next letter, I press space and the scribomatic reads me the next letter. Pressing space is much quicker than saying “Okay” to the reader and waiting for them to register that and read the next letter.

So the scribomatic uses a computer to do some of the reading and communicating previously done by a human, which reduces the chance of human error. Interacting with the scribomatic is easier and faster than interacting with a human, which makes the process faster. I don’t have to fit into its schedule, and I don’t have to pay it for its time.

Mirrored from hasoferet.com.

comments

Proofreading, part 15

2009-12-30T05:45:04Z

Broadening our scope back into the general activity of proofreading, we left off with me saying that one person checking the Torah by reference to a tikkun isn’t terribly efficient, for several reasons. This is why tradition developed an alternative process, in which a Reader has the tikkun and a Sofer has the klaf. The Reader reads the letters from the tikkun one by one, and the Sofer checks them off.

This greatly reduces the chance of errors caused by misremembering. It also greatly reduces the amount of time spent moving one’s gaze between the klaf and the tikkun, finding and refinding the place, stretching your neck up and down – considered over the length of the entire Torah, this is a considerable saving.

Further, the chance of erring by anticipating – seeing what you think should be there rather than what is there – is reduced, since the text is now being handled as a string of individual letters, rather than as words. To reduce it even further, some people read the text backwards, so it really does become just a string of letters, with no room for anticipation at all.

Mirrored from hasoferet.com.

comments

Proofreading, part 14

2009-12-29T03:39:40Z

Proofreading also picks up on things which are technically kosher and wouldn’t make the reader confused, but just aren’t very pretty.

This stage is a tricky one, because there’s always, always going to be stuff you could have done better, and if you’re not careful you’ll drive yourself into a frenzy of ever more microscopic tweaking, far beyond the point where it could possibly make a difference. Balancing artistic integrity and realism is a skill that has application beyond Torah proofreading, though, so it’s a good skill to learn regardless.

Here’s an example. That mem could be prettier.

This is a level of detail I think you can only apply to yourself or your student. Applying it to someone else’s writing is just wrong on so many levels – pragmatically idiotic and technically unrealistic, as well as being an exercise in fantastic subjectivity, hyper-criticism, and wishful thinking.

For instance, if you have a Torah that’s getting on in years, some of its letters are not going to be as pretty as they once were. Fact of life. You could spend months going over it and restoring each letter to perfection, but like any invasive cosmetic procedure, there’s only so much that’s going to help; at some point it’s better to accept it as is.

But this is a new Torah and I wrote it, so if I want to make that mem prettier, I will.

Mirrored from hasoferet.com.

comments

Proofreading, part 13

2009-12-28T05:42:45Z

The astute will have worked out by now that this Torah has advanced into the proofreading stage, writing and proofreading happening simultaneously. I just thought I’d mention that.

Mirrored from hasoferet.com.

comments

Proofreading, part 11

2009-12-26T05:38:16Z

Pasul letter mem

Proofreading has to pick up on letters which have real problems in their form. Maybe the scribe’s hand slipped, maybe the letter got smudged by accident, maybe the ink spread after being put on – letters can go wrong, and we don’t always notice while we’re writing. So proofreading has to be alert for that kind of thing.

Again, you need knowledge of letter forms. You need to know why the above is a problem.

The problem is this little join. Such a little thing, but so important.

I like thinking of it as being similar to electricity. Electricity doesn’t care if it’s only a little tiny wire making the short-circuit; that little tiny wire short-circuits your thing and boom, it isn’t working any more. Same with letters. This mem is short-circuited, and it doesn’t work any more.

And like the more annoying kind of short-circuit, you can’t just take out the offending part and have everything work, no, you have to take the thing apart and rebuild it.

(Super-geekies can read chapter 8, paragraph 6 of the Keset ha-Sofer for info on how to fix a short-circuited mem, but the non-super-geeky may prefer to give it a miss.)

Couple more examples, for your delectation. One’s a shin with a short-circuit, the other is supposed to be a yud followed by a nun, but the short-circuit there has turned it into a mysterious tzaddi-ayin hybrid. Internet cookies for anyone who explains how to fix them.

Mirrored from hasoferet.com.

comments

Proofreading, part 10

2009-12-25T07:26:23Z

We saw an example of one sort of thing which proofreading turns up – where the text is Just Wrong:

Text should read שמנה מאת שנה.

That was a case where the extra letter vav completely changed the meaning – “eight hundred” became “one hundred and eight.” But in some cases, an extra or missing yud or vav doesn’t actually change the meaning, thanks to the accommodating nature of Hebrew vowels. These are known as haser (deficient) or malei (overblown) spellings. Like this:

This is a word spelled haser – lacking a vav – where it should be spelled with a vav, ויולד.

If you’re reading in the Torah and you find the first kind of Wrong, it’s a problem, and you have to stop and switch Torahs. But if you find the second sort, you don’t have to switch Torahs. The mistake ought to be fixed soon, because thinking “oh, it doesn’t matter” is the first step on the road to propagating mistakes which jolly well do matter, but you don’t have to stop reading.

This has to do with the extent to which we think the text of the Torah is incorruptible. I simplified a bit earlier – the integrity of the text is a theological principle except for these kinds of spellings. These ones we’re not exactly certain of, and haven’t been since Talmudic times.

So we weigh values. Stopping and switching out Torahs is not good, for various reasons; reading from a Torah with wrong spelling is not good either. With very egregious misspellings, the badness of the mistake outweighs the badness of switching Torahs. But haser and malei misspellings, since we’re not absolutely certain they’re actually wrong, there’s a chance our spelling could be the right one, and on the strength of that chance we swing the balance the other way. Interesting, huh?

Mirrored from hasoferet.com.

comments

Proofreading, part 9

2009-12-25T02:51:04Z

All this place-finding and looking up and down takes time. Only a couple of seconds each time, but that adds up fast, as you can probably imagine.

Holding a string of letters in your mind isn’t efficient either, partly just because one can forget things, and partly because of anticipation; when you’re reading the text as words, you’re much too liable to remember what you think ought to be there rather than what actually is there. That’s how most of these mistakes get in there in the first place.

You’re also liable to confuse phononyms, liable to skip silent letters, liable to attempt to remember too much and thus forget parts unawares.

And all this is only answering “Is the letter there?”. The question of “Is it kosher?” requires more mental processing, as we saw earlier – is it touching another letter, does it have all the parts it needs, does it have the right decoration. The above list doesn’t leave much brain left over for processing these questions.

More about how we deal with that later. First, we’ll see some other cases where such mental processing is required.

Mirrored from hasoferet.com.

comments

Proofreading, part 8

2009-12-25T02:49:34Z

When I’m proofreading my writing for the first time, there are two questions I’m asking regarding each of the 304,805 letters: is the letter there, and is the letter kosher?

The process goes like this.

With a sheet of freshly-written Torah in front of you, you find your place in the tikkun and look at it to see what letters ought to be written.

Carrying those letters in your mind, you look down and find your place on the klaf, and compare the letter string in your mind to the letter string on the klaf.

If they don’t match, fix it.

For instance, this is just wrong, but I didn’t realise it at the time. It ought to read שמנה מאת שנה.

Then look back up and find your place in the tikkun, and repeat.

Mirrored from hasoferet.com.

comments

Proofreading, part 7

2009-12-25T02:46:50Z

Getting back to proofreading proper.

As we’ve heard, in order to encourage integrity of the text, we have a rule that even one wrong letter invalidates the entire Torah.

When you’re writing 304,805 letters, you’re bound to slip up on some of them. So, when you write a Torah, you proofread it extremely carefully, more than once, before you release it into the wild, as it were, and read from it.

Here’s a place where I was merrily writing along, wrote the wrong letter, and realised it at once. The ink was still wet, so I blotted off as much as I could with kitchen paper, that’s why it looks grey and shadowy. Makes the erasing easier.

To fix this sort of thing, you need to let it dry and then scrape off the excess. But letting it dry takes a good fifteen minutes (if you try fixing it sooner you just rub it in and make it worse) and it’s inefficient to sit about watching ink dry for a quarter of an hour. If you’re writing tefillin or mezuzot, you’ve got no choice, you’ve got to fix it before continuing, but when you’re writing Torah you can skip over the mistake and come back to fix it later.

Now we’re in the proofreading stage, it’s “later,” and time to fix.

These pale-grey blotted ones are obvious – when you made the mistake, you realised it at the time, you blotted it, perhaps you made a note in pencil in the margin – these aren’t difficult to see. The really taxing part comes next.

Mirrored from Hatam Soferet.

comments

Proofreading, part 2

2009-12-17T04:29:04Z

A scribe today has an exhaustive list of rules for how each letter ought to look – here's an example for letter shin, from the Mishnah Berurah:

Shin has three heads. The first head, with the leg which is drawn out of it, is like a vav, and its face is tilted slightly upwards. The second head is like yud; its head is tilted slightly upwards, and ideally it has a little prickle on it. The third head must be made like zayin, and it has three taggin on it. The left heads of all the letters שעטנז גץ are like zayin. One must take care that the heads do not touch each other. The leg of this left head should lekhathilah be particularly vertical...

and it goes on, I won't give you all of it here.

Specifically, it's interesting that the later authorities - i.e. the ahronim, post-Shulhan-Arukh, more or less - devote a lot of space to defining how the letters should look, but the rishonim and earlier (including the Shulhan Arukh) don't seem too interested in that - they know how the letters ought to look, and they content themselves with reminding you particular ways in which you ought not to stray, like not making alefs ayins and suchlike.

Alef-bets differ with region and period. We've already seen some of the ways Ashkenazic and Sephardic alef-bets differ, when we were discussing influence of writing implement on letter style. We didn't discuss there how those styles relate to the laid-down rules for letter forms.

Letter shin is a case in point. Literally.

Sephardi shin

Ashkenazi shin

More about that later.

comments