Several users of the MTCurly plugin have written in or commented about the module catching em dashes written in as two hyphens. In the PHP function I have parsing the text on this site, I actually have this rule running. Well, it’s a pretty trivial task to do this, but when I was thinking about it the issue of en dashes bothered me and I decided to reread one of my favorite ALA articles, A List Apart: The Trouble With EM ‘n EN.

While the majority of people will just want to use the em dash, I think the possibility of having en dashes generated automatically as well would be very convenient and encourage more widespread adoption of them. But how do you notate an en dash using only the characters on the keyboard? I thought about this and came to the conclusion that there should be two optional addons to the code, one for changing two hyphens into an em dash, and one that changes two hyphens into an en dash and three into an em dash. Get the updated code. I’m curious to hear some thoughts on this.

For those who aren’t familiar with the proper usage of em and en dashes, here’s a quote from the ALA article, which I think is the best summary of the matter on the net, by Peter K. Sheerin.

The em dash (—) is used to indicate a sudden break in thought (“I was thinking about writing a—what time did you say the movie started?”), a parenthetical statement that deserves more attention than parentheses indicate, or instead of a colon or semicolon to link clauses. It is also used to indicate an open range, such as from a given date with no end yet (as in “Peter Sheerin [1969—] authored this document.”), or vague dates (as a stand-in for the last two digits of a four-digit year).

Two adjacent em dashes (a 2-em dash) are used to indicate missing letters in a word (“I just don’t f——ing care about 3.0 browsers”).

Three adjacent em dashes (a 3-em dash) are used to substitute for the author’s name when a repeated series of works are presented in a bibliography, as well as to indicate an entire missing word in the text.

The en dash (–) is used to indicate a range of just about anything with numbers, including dates, numbers, game scores, and pages in any sort of document.

It is also used instead of the word “to” or a hyphen to indicate a connection between things, including geographic references (like the Mason–Dixon Line) and routes (such as the New York–Boston commuter train).

It is used to hyphenate compounds of compounds, where at least one pair is already hyphenated (as in “Netscape 6.1 is an Open-Source–based browser.”). The Chicago Manual of style also states that it should be used “Where one of the components of a compound adjective contains more than one word,” instead of a hyphen (as in “Netscape 6.1 is an Open Source–based browser”). Both of these rules are for clarity in indicating exactly what is being modified by the compound.

Other sources also specify the use of an en dash when referring to joint authors, as in the “Bose–Einstein” paper. Some also prefer it to a hyphen when text is set in all capital letters.

While quoting the above article, I noticed what may be an error in the source where it looks like in the paragraph about en dashes em dashes are actually used. I’ve corrected it in the quote above. Typos happen, I’ll drop Zeldman an email. (Time to break out the spel chequer.)

I’m also considering adding a few other things to the next version of the plugin, so if you have anything you’d like to see in there let me know.

Gallery, in my opinion, is the best photo management software out there for web right now; it really does everything you could want such a package to do. However, it’s relatively old, as far as web projects go, and development decisions made long ago are starting to really limit it. With version two of Gallery Bharat, the main developer, is fixing everything he wishes he had done right the first time. I’ve been following the new code on the CVS pretty closely and from what I’ve seen so far it’s really quite nice.

Bharat (page has sound) is doing things right the second time around, but the project isn’t moving terribly fast. One of the biggest hassles in trying to deal with Gallery as it stands now is interfacing with the serialized data files. It’s almost impossible to hack unless you get really knee deep in the code. Also, due to the flat-file nature of the data files, things get slower the bigger they get. I had to disable the random picture on the menu just because it was adding about a second or more to the time taken to generate every page! With the data accessible through SQL, I could write a random photo block in five lines of code that takes almost no time to run, not to mention all the other fun things you could do with the data in a proper relational database. Check out the Zeitgeist for an example of some fun things you can do with SQL and PHP when you’re bored.

Anyway, it looks like a temporary solution may be available soon. I’ve contacted the developer and I’m looking into implementing this her as soon as possible. Cross your fingers :).

I am happy to announce that the “curlyquotes” module for Movable Type has passed out of beta into the release stage. Many thanks to Todd of Dominey Design for testing and providing valuable feedback. Here are the updated instructions. For full details, please see this script’s info page, which lets you receive updates by email, leave comments, report bugs, ask for features, and ask questions, et cetera. Here are the updated installation directions:

1. Install the MTRegex plugin. (Directions from readme.txt file)
   1. Get file.
   2. Place the ‘regex.pl’ file in your Movable Type “plugins” directory
   3. Place ‘regex.pm’ and ‘postproc.pm’ in a ‘bradchoate’ subdirectory underneath your Movable Type “extlib” directory.
   4. You should end up with something like this:
      • (mt home)/plugins/regex.pl
      • (mt home)/extlib/bradchoate/regex.pm
      • (mt home)/extlib/bradchoate/postproc.pm
2. Create a new template module called curlyquotes with the code from here.
3. Add <$MTInclude module="curlyquotes"$> to the top of all your templates.
4. Replace all occurences of <$MTEntryBody$> with <$MTEntryBody
regex="1"$>.

Usage is free, in every sense of the word, but if you could throw a link back this way I would appreciate it. Also if you improve on the code in some way, submit your changes so everyone can benefit.

What this module does: It takes straight quotes/prime mark, and makes them proper typographer’s quotes, sometimes called “curly” or “smart” quotes. So basically it takes "this" and makes it “this” using the proper HTML entities. It also works with single quotes, apostrophes, and multi-paragraph double quotes. It slices and dices!

Why? Because there is no button for a curly quote or apostrophe on the keyboard. No really, see the old post for more.

Todd Dominey has reported a small bug in the curly quotes regex where a quote in links, like this “photolog“, displays wrong. I’ve also rewritten the guide for installing the code on Movable Type thanks to Todd and Michael, and I’ll be posting it soon.

Google News has ‘officially’ launched, insofar that it is now a tab on the now-crowded Google toolbar (not toolbar, I guess tab-bar). Although it’s still labeled as beta, those of you who remember what it used to look like know that it’s come quite a way. It seems to have some sort of algorithm running, so check it out. If you’re interested in seeing what else is cooking at Google, check out Google Labs, which currently has such goodies as a keyboard navigable interface, a glossary, something fancy with sets, and an interface that will return results based on your voice commands.

Try it out!

I’m in the process of compiling ht://Dig 3.2.0b4 to add full-featured search to this site. If you don’t have experience with it already, I would highly recommend checking out ht://Dig next time you consider making a search feature. I considered using a FULLTEXT MySQL search but that would ignore one of the largest sections of the site, the Photolog, which is not MySQL-driven (yet).