Other tricks in the Bible Code

Referencing

http://www.straightdope.com/mailbag/mbiblecode.html

Drosnin also used the trick that most people don’t know
Hebrew, to his advantage, in other ways.

When a grid of Hebrew is sitting in front of you, it’s not
so obvious that the horizontal rows were still just the
Torah, reading as normally as ever. So he could pick out
the ancient Hebrew word for chief/tribe leader, and claim
it was the ancient word for ‘president’, found ‘magically,’
and that it crossed “Kennedy.” Actually “Kennedy” was just
three Hebrew letters - transliterated KND.

He found some ancient cities that way, too - they’re just
sitting there, horizontally.

And he could accept the ancient word for something (like
‘chief’ for ‘president’), or the transliterated modern word.

And he never pointed out that looking at a grid of say,
a 17-letter wide Torah, and then picking out skews that went
at a ‘rise to run’ of two or three, was just taking every
19th letter or 20th letter, like so:

OAAAAAAAAAAAAAAAA
AAAOAAAAAAAAAAAAA
AAAAAAOAAAAAAAAAA
AAAAAAAAAOAAAAAAA
AAAAAAAAAAAAOAAAA

so he could find some significant word taking every 17th
letter, find another taking every 20th letter, and “force”
a grid to make it look significant.

Yes, thanks, bup, for pointing out that words like “chief” or “murder” appear all by themselves in the Bible text, and so will also appear in any word-find matrix. Plus, most proper names (people or places) have meanings also; thus the name “Adam” contains the Hebrew “D-M” meaning “blood”, so it wouldn’t be hard to find a fair number of occurrences of the word “blood” in the first chapters of Genesis.

IIRC, Hebrew doesn’t have vowels, so the job of finding “hidden” words is relly easy. There is an excellent essay on this subject in Simon Singh’s “The Code Book”

C. W., Y. R. C.

From the Staff Report: