Monday, February 12, 2007

Friday, February 09, 2007

The Tent of Meeting

After my last post, I got to thinking about the diagram I had put up, of the Tabernacle. My problem is the “Tent of Meeting;” I’ve done the diagram as if the entire structure, including the Outer Court, and the Holy Place and Most Holy Place, are all part of something called the “Tabernacle,” whereas the little structure inside, holding the Holy Place and the Most Holy Place, is called the “Tent of Meeting.”

Thursday, February 08, 2007

Friday, February 02, 2007

Verse of the Day

I’ve added a “Verse of the Day” item to the sidebar, from Bible Gateway. Unfortunately, I don’t have a lot of control over it—it’s got a fixed width, and a black background.

If they ever come up with a more customizable one, that I can fit into the sidebar better, or if I find one somewhere else, I’ll replace it.

Leviticus 15

Leviticus 15: Rules for discharges causing uncleanness

Thursday, February 01, 2007

Leviticus 14

Leviticus 14: Rules for cleansing from infectious skin diseases and mildew

Wednesday, January 31, 2007

Punctuation

This has nothing to do with the Bible; it’s just related to the way I write this blog.

On my personal blog—and in email, on chat, and in other contexts—I’ve gotten into the habit of writing quotations marks in the hacker writing style, instead of following American English standards for quotation marks.

Hackers tend to use quotes as balanced delimiters like parentheses, much to the dismay of American editors. Thus, if “Jim is going” is a phrase, and so are “Bill runs” and “Spock groks”, then hackers generally prefer to write: “Jim is going”, “Bill runs”, and “Spock groks”. This is incorrect according to standard American usage (which would put the continuation commas and the final period inside the string quotes); however, it is counter-intuitive to hackers to mutilate literal strings with characters that don’t belong in them. Given the sorts of examples that can come up in discussions of programming, American-style quoting can even be grossly misleading. When communicating command lines or small pieces of code, extra characters can be a real pain in the neck.

The article quoted goes on to mention that the hacker style of writing quotes is now preferred practice in Great Britain—however, in Britain, single quotes and double quotes are used in reverse to how they are used in America. e.g. in America you would write

Said John, “He said ‘I’m going to the mall,’ but I didn’t believe him.”

Whereas in Britain you would write

Said John, ‘He said “I’m going to the mall”, but I didn’t believe him.’

Canadians, who are neither British nor American—but almost both—tend to use American-style quotations. I, on the other hand, have picked up a mish-mash of both; I use double and single quotes where Americans would, but punctuate around the quotes like the hacker style above.

I have decided, however, to try and write this blog, from now on, using American-style punctuation around my quotation marks. I say “try” because the hacker style of writing has become very ingrained; I often find myself, in my professional writing career, having to go back and “correct” my punctuation using the American style.

My reason for doing so here is that I’m afraid some Biblical scholar will find my blog via Google some day, pop in, and start harassing me about my punctuation not being grammatical. Priests and Reverends and Pastors (and whatever other titles you can think of) love education, and it’s exactly the type of thing that I can see them being overly worried about.

Leviticus 13

Leviticus 13: Rules for infectious skin diseases, and mildew

Tuesday, January 30, 2007

Leviticus 12

Leviticus 12: Rules for “purification” after childbirth

Monday, January 29, 2007

Leviticus 11

Leviticus 11: Rules for clean and unclean food