How Sherlock Translation Channels Worked in Mac OS 9

In Apple’s Mac OS 9, Sherlock 2 transformed from a simple local file search utility into a customizable, internet-connected information hub powered by a tabbed feature known as "channels." Among these specialized channels was the Reference channel, which allowed users to perform direct dictionary lookups and language translations without opening a standalone web browser. By dispatching background web requests and parsing the results directly within its native interface, Sherlock provided one of the earliest desktop-integrated web services experiences.

The Role of Channels and the Reference Tab

Sherlock 2 organized different search domains into visual icons at the top of its interface, called channels. The standard Reference channel, typically represented by a stack of books or a dictionary icon, was pre-configured to query linguistic and encyclopedic databases. Rather than indexing the entire World Wide Web via traditional search engines, this channel routed queries specifically to reference service providers like Dictionary.com, Britannica, and early machine-translation engines like AltaVista’s Babel Fish and SYSTRAN.

The Mechanism Behind Search Plugins (.src Files)

Sherlock’s translation and dictionary capabilities relied entirely on Apple's Search Plugin format, designated by the .src file extension. Stored in the "Internet Search Sites" folder inside the System Folder, these plain-text files defined how Sherlock interfaced with remote websites:

  1. Request Mapping: The plugin defined the target server URL, the method (HTTP GET or POST), and the query arguments. For a dictionary, it mapped the input text to the service's lookup path. For translation, it sent the text along with specific parameters indicating source and target language pairs (such as English to French or Spanish to English).
  2. Result Parsing: Plugins contained parsing delimiters that instructed Sherlock where the useful content began and ended within the returned HTML. By stripping away extraneous page layouts, navigation bars, and banner ads, Sherlock extracted only the definition, pronunciation, or translated text.

The User Workflow and Data Retrieval

When a user typed a word or phrase into the Reference channel and initiated a search, Sherlock executed the underlying plugin scripts:

  • Query Execution: Sherlock transmitted the query to the designated third-party translation or dictionary server in the background.
  • Inline Display: Instead of launching a browser like Netscape Communicator or Internet Explorer, Sherlock utilized a native, embedded HTML display pane at the bottom of its window.
  • Viewing Results: For definitions, the top half of the window listed matching terms, and selecting an entry populated the bottom pane with the definition. For translations, the generated translation was rendered directly in the preview pane, allowing users to copy the localized text directly into local applications like SimpleText or AppleWorks.