Google Books Goofed

Anything worth doing is worth doing right. —Hunter S. Thompson

I’ve recently been researching Old English measures, and found that the ability of Google’s search engine to do a plain-text search on everything they’ve scanned into Google Books / the Google Library Project has been a phenomenal aid in ferreting out lost knowledge that shouldn’t be so obscure that until today, every Wikipedia entry on the pound Sterling said its weight had always been different from the Tower Pound.

Awesome that Google let me discover that!

However, when I wanted to read the rest of the story, so that I could accurately update Wikipedia, Google failed me completely. The low resolution at which they scanned A View of the Silver Coin and Coinage of England is so pitifully low that you cannot decipher many of the composed fractions. For this book, published in 1762, copyright hasn’t been an issue for many years. A few, such as ½ and ¼ vary from somewhat decipherable (though not in all instances, and usually because I already knew the value from another source, as on page 4), to not quite decipherable (several of those on page 13; is that 5 5⁄8 grains or 5 5⁄8 grains or 5 3⁄9 grains?), but once you get to the fractions on page 14 and 15, there’s no chance of deciphering those without access to the original document. And heaven help you if the composed fractions (which are by definition substantially smaller than the surrounding characters) are in a footnote, whose text size is already smaller than the standard text.

Stealth Trade Shows

Whateverwhenever. (This was going to be the title for this post, but then I realized that topic deserves its own story. Maybe later this weekend…) How much do you care about your customers’ or prospective […]

Proving Your Identity—Smart Cards and the Sad State of the Art

I am in the process of updating my vCard to the new 4.0 standard, and decided it was time to once again obtain a digital certificate that I could use to sign and/or encrypt e-mail messages with. And since I have a laptop with a Smart Card reader, I figure it would be great to leverage it for more secure logins, file encryption, and a few other things. The only digital certificate that can do all those things is the ITU’s x.509 public key infrastructure (PKI) standard, which dates from 1988.

There are many reasons why the average person, not just this geek’s geek, would want to do this:

Save Me From The Evil Back Button

This experience is one of many reasons why I have a love/hate relationship with web-based software. I had just finished composing a message on a Yahoo group, and went to hit the post button. But […]

Celebrating Blogger’s Anniversary by Switching to WordPress

OK, the dust has settled, and I have ported all of my content from the old static version of the site to the new WordPress-driven one. My hard-core standards compliance pages remain at a variation […]

Pardon the Dust—Switching from Blogger to WordPress

My long-term hate-hate relationship with Blogger is over. I never really fully bought into the concept anyway; I had simply found its ability to publish to a plain-text file that I then wove into my […]

W3C mobileOK hurts interoperability

I guess this is what happens when I stop involving myself in the development of Web standards. Am I the only one on the planet that understands content negotiation and how important it is to […]

Laird Destroys Cushcraft

I’m trying to save Fridays for writing about Fabulous things, instead of Frustrating things, but an experience I just had necessitates postponing my daily themes a bit. At the Burlingame Red Cross office I’ve been […]

Interoperability of Phones and PDAs with the Web

I’ts Christmas day, and I’m launching a new Website designed as a catalyst to improve how cellphones, PDAs, and desktop computers work on the Web and with each other. PDAcritic.com is not only a place […]

Content Negotiation for WAP Browsers

After trying several times over the past several years to have one URL work for both desktop browsers and mobile phone browsers—using the HTTP content negotiation first defined in 1992 and again in 1997 and […]