Jeff Duntemann's Contrapositive Diary Rotating Header Image

publishing

The Pulps Reconsidered, Part 4

BasketballStoriesCover350Wide.jpgThe essential difference between literary (as we define it today) and non-literary fiction didn’t crystallize for me until first-person shooters happened. I’m not one for games in general, but an hour or two playing early shooter games like Doom and Quake back in the 90s was an epiphany: This is a species of fiction. The following years proved me right. Most ambitious action games have at least a backstory of some kind, and some modern MMORPG systems have whole paperback novels distilled from them. (See Tony Gonzales’ EVE: The Empyrean Age, based on EVE Online.)

Of course it’s not literature. Did anybody say it was?

What it is is something else, something important: immersive. You get into a good game, and you’re there. I can do the same thing with a decent SF novel, but the phenomenon is in no way limited to SF. I’m guessing that Farmville or almost any reasonably detailed simulation works the same way.

Immersivity is the continental divide between literary fiction and pulp fiction. Like anything else in the human sphere it’s a spectrum, placing World of Warcraft on one end and Finnegan’s Wake on the other, with everything else falling somewhere in the middle. The term measures the degree to which you can lose yourself in a work, where “lose yourself” means “forget that you’re reading/playing and enter into experiential flow.”

Don’t apply a value scale to immersivity. It’s only one dimension of many to be found in fiction, and my point here isn’t to dump on Finnegan’s Wake. Literature is intended to evoke a response in the reader, but that response is not necessarily immersion. (It can be, particularly with classics like Huckleberry Finn that are new enough to be culturally familiar to us–dare you to read Chaucer without footnotes!–and yet not so new as to be afraid of Virginia Woolf.)

Pulling the reader in and carrying him/her along requires a smooth, linear narrative style, a vivid setting, and enough going on to maintain the reader’s interest after a long day working a crappy job. Pulp characters are often types, but that’s not necessarily due to a lack of skill on the writer’s part. A carefully chosen and well-written type allows room for a reader to imagine being that character, which is important in immersive fiction. As much as I enjoyed Gene Wolfe’s massive Book of the New Sun (and I’ve read it three times since its publication) I had a very hard time imagining myself as Severian. I empathize with him and certainly enjoyed watching him against the dazzling surreality of Urth (though I had to read numerous sections several times to be sure I knew what was going on) but being him? No chance. Keith Laumer’s Retief, on the other hand, no problem. Louis Wu? Same deal.

And for the umptieth time: (I can hear the knives being sharpened) This is not to denigrate literary fiction, of which I’ve read a lot and still do. My point is that immersive fiction is a valid entertainment medium, requiring different mechanisms and different skills than literary fiction. Let’s not dump on things for simply being easy to read. Easy is good if easy is what you want–and (on the author side) if easy is what people are willing to pay for.

Which should not suggest that easy to read is necessarily easy to do. The immersive magic of the pulps is obscured by the fact that a lot of it was just badly done, and could not have been otherwise, given that some pulp titles paid a quarter cent a word and published eighty thousand words twice a month. We can do much better these days, at least on the quality side. A brilliant potboiler is eminently possible–if we as readers give authors some sense that it’s ok to take up the challenge, and that they’ll be paid for their efforts when they succeed.

More in this series as time allows.

The Pulps Reconsidered, Part 3

SDMCover.jpg

Bet you thought I forgot about this series, huh? Not so: I needed a little time to take a broader look at the field. (Click here for Part 1 and Part 2.) Someone told me that a lot of 1930s/40s/50s pulps were being scanned and posted on Usenet at alt.binaries.pictures.vintage.magazines, so I went up there and pulled down a representative sample. And I’m not talking SF anymore; what I grabbed were things like Air Wonder Stories, Mammoth Western, Strange Detective Mysteries, Adventure, and Spicy Stories.

It’s been wonderful fun. In fact, it’s a lot like watching campy old b/w TV shows, only better, because I can decide how everybody and everything looks. I don’t have to be appalled (or giggle) at the cheap crappy special effects. I just willingly enter a world in which nobody rolls their eyes at a homicidal supermarket butcher about to strangle a square-jawed hero armed with a pistol in one hand and a hacksaw in the other. (See above. No, I didn’t read that story. I still wonder what the hacksaw was about.)

I’m not the first to suggest that the pulps vanished largely because TV took over their niche. The pulps were Saturday-morning movie serials that you could enjoy any time you wanted, and once TV started showing Commando Cody, Bomba the Jungle Boy, Flash Gordon, and made-for-TV adventures like The Texas Rangers, Sky King and Highway Patrol, much of the money went out of pulp publishing. The financial pressure was eventually fatal, but over the short term, as the pulps dwindled, their quality went up. And it wasn’t just that we knew more about science and technology and hence could write better SF. The SF of the Thirties was awful because the readership didn’t care. The pulps had a monopoly on cheap entertainment and people bought it because it was all there was, and reading it was better than staring at the wall.

Print entertainment evolved out of the pulps and into other print markets, particularly glossy mags. The railroad pulps died, but glossy, ad-supported magazines like Trains and Railroad picked up the readership, which after WWII had more money to spend on locomotive picture books and model railroading. Tacky text-porn mags like Spicy Stories (which had racy drawings and a handful of “artful” b/w nude photos) gave way to Playboy and its cheaper imitators as social strictures against visual porn weakened in the 50s. In the late 50s, pulp SF improved hugely, and bootstrapped itself into the new world of mass-market paperbacks by selling reprint anthologies of the best work to come out of the pulp era. (We can be fooled into thinking 30s and 40s pulp SF was better than it was because what we read of it was hand-picked for quality decades after its publication. Read a couple of original SF pulps circa 1935 and you’ll see what I mean.) Crime pulps went both up and down, to comics on the low end (much of “crime” fiction from the Depression was actually horror) and to book-length mysteries on the high end. The romance pulps like My Romance split similarly into gossip mags and mass-market romance novels.

Fewer people may be reading these days, but those who gave it up probably never liked reading that much to begin with. Again, reading was better than staring at the wall, but TV, when it arrived, was easier, especially for people with marginal education. The audience that remained was pickier, and many had been formally exposed at the college level to classic literature, which became the standard by which all fiction was measured.

And that may be a mistake. (I’ll come back to this point in a future entry.)

Leaving the quality of the writing itself as a separate issue, after a good long look around I’d say that the lessons of the pulps are these:

  • The pulps were about specific cultures. They were tightly linked to a time and a place and a generally understood cultural subtext. This was even true of early pulp SF, much of which might be characterized as “Depression-era Chicago on Mars.”
  • Characters were intended as costumes to be worn by readers, not fully realized individuals to be admired on their own merits as independent men and women. A lot of people don’t understand this, and many still won’t admit it. Make characters too vividly fluky and original, and readers will have a hard time identifying with them.
  • As a corollary to the above: Concepts, settings, and action were as important as characters, and much more vivid. Again, it’s the difference between imagining yourself driving a fast car and imagining someone else driving it.
  • The pulps were fun. They understood and accepted their role as immersive entertainment. They were not equipped to be literature and didn’t try to be literature.

With all that in mind, the big questions become: Is there unmet demand today for good-quality immersive (non-literary) fiction? How much of this legacy can we retrieve in 2010 and do well?

More next time.

Coding vs. Compiling EPubs

It’s always unsettling to admit that the other side has a point, but it’s good practice and often absolutely necessary. I am the VDM guy, after all, and I’ve never been one for hand-coding what can be generated automatically. As I’ve mentioned here earlier, an awful lot of people take their text and hand-code an EPub framework around it to create an ebook, which I found borderline ridiculous…until this morning. Now I think I know why they do it.

It’s simple: Our EPub compilers have a very long way to go.

The process of creating EPub-formatted ebooks can be done two ways: Write your own XML/XHTML by hand, or let a utility of some sort generate it for you. I’ve done both in recent days, and I was bowled over by the conceptual similarities between that and the gulf between writing a program entirely in assembly and writing it in an HLL like C. I’ve done a fair bit of tracing through assembly code as compiled by GCC, and I’ve been very impressed by the cleanness and comprehensibility of the assembly files it produces. GCC is one helluva compiler, as is the Delphi compiler. (And that’s where my low-level code tracing experience begins and ends, mostly.)

Well, I’ve been spoiled. Compared to GCC (or even Delphi, which is now 15 years old, egad) the EPub format is a babe in diapers: poorly understood, still growing furiously, and, as often as not, smelly as hell. All of that will pass. (I remember my nephew Brian in his diapered era; he is now 27 and an investment banker.) But in the meantime, well, the immaturity of the EPub technology must be dealt with.

I did another, larger test case EPub yesterday. I took a 15,000-word article from an old theology journal, extracted the text via ABBYY PDF Transformer, cleaned up the text (which was in fact pretty damned clean to begin with; ABBYY does a superb job here) and loaded the text into the Atlantis word processor. Without a great deal of additional editing, I exported it to an EPub file. That file may be downloaded here. (40K EPub.) There are no images, and all the text exists in a single XHTML section. It’s about as simple structurally as an EPub can get, and what you see is just as it came out of Atlantis. I did not tweak it at all post-Atlantis, neither manually nor in Sigil. (Note well that Atlantis can export EPub, but it cannot import EPub files, nor display/edit EPub XML/XHTML.) I then took that file and loaded it into Sigil, added a cover image, and split the text into two sections. You can find that file here. (1 MB EPub.) Both of these files pass EPubCheck without errors.

The Atlantis EPub renders (reasonably) well in all the local readers I have here, as well as the online Ibis Reader. It’s small (only 40K) and if you can do without a cover it’s a perfectly reasonable ebook. The Sigil copy does not do nearly as well. The online Ibis Reader refuses to render any of the images at all, including the cover image, the copyright glyph, and the generated images of the two grapevine glyphs that I inserted into the title page as decorations just to see what would happen. The copyright glyph issue is disturbing for legal reasons, but worse, it’s a standard character with a standard HTML encoding, and should be renderable irrespective of font. Ditto Azardi, which renders the Atlantis EPub well but not the Sigil copy. Over and above Azardi’s leaving out all the images (including the copyright glyph) the Sigil copy of the EPub loses what little formatting it had in the Atlantis EPub. None of the centered text remains centered, for example.

There are some additional weirdnesses in the readers themselves: FBReader renders both files well, but (weirdly) the Go Forward button moves the reading window toward the beginning of the file, and the Go Back button moves the window toward the end of the file, perfectly bass-ackwards. Ibis displays the title three times, which is overkill. FBReader handles the images just fine, but renders the copyright notice for both versions in Greek letters, sheesh.

These rendering issues are probably reader failures, since the files themselves are EPub-compliant. However, the autogenerated XML/XHTML code is often obscure, and in one case, at least, dead wrong: The title tag includes only the first line of the title. I understand that the title text is split into two lines, but I was never asked to define the text within the title tag and can only assume that Atlantis picked the first Heading 1 style it found and plugged its text into title. (The metadata for the title was stored correctly, and all readers displayed the full title text. I don’t think that the title tag is used by the readers. An empty title tag is perfectly acceptable to EPubCheck.) The gnarliest part of the compiled EPub (in both versions) is the CSS. Atlantis took the page format settings and translated them into generically named CSS classes, which are accurate representations of the word processor settings, but not easily identifiable and in no wise good quality CSS.

This isn’t insurmountable, and most of the problems I’ve had so far can be blamed on incomplete and buggy reader apps, but it shows how young a business this is. The hand coders still have the edge, and I’d be better off on the readability side creating the ebook text in a WYSIWYG HTML editor like Kompozer or Dreamweaver and hand-coding the CSS myself. That is, however, precisely what I’m trying to avoid. Sooner or later, Atlantis or something like it will offer pre-written CSS style sheets designed specifically for text intended for EPub export. That will help a great deal. In the meantime, some manual futzing is unavoidable, and my opinion of Sigil has been greatly tarnished. I may have to try something else on the EPub editor side; suggestions always welcome.

And the readers, yeech. Don’t get me started. I may have to buy an iPad just to see what my own damned books look like!

Atlantis and the EPub Toolchain

You’ve heard me say this before, and I suspect you’ll hear it again and again: Creating ebook files is much harder than it needs to be, and creating ebooks in the EPub format is particularly–and inexplicably–hard. In my June 9, 2010 entry, I spoke about the EPub format itself, and how it’s not a great deal different from a word processor file format. In fact, Eric Bowersox pointed out that OpenOffice’s ODF files are also based on XML and organized in a similar way.

Bogglingly, most people appear to be hand-coding EPub XML. In recent days I’ve been looking for better ways to create EPub ebooks. Many places online cite Sigil as the only WYSIWYG EPub editor in existence right now, and I grabbed it immediately. It’s a very nice item, but appears to be an undergraduate’s Google Code project, and I certainly hope he will hand it off to others if he ever gets tired of hammering on it. Version 0.2.1 has just been released, and it fixes a number of bugs that I stumbled over in the last couple of weeks that I’ve been using it.

Then, yesterday, without any need for ancient maps or Edgar Cayce, I found Atlantis.

The Atlantis word processor is a $35 shareware item created by a very small company in France. It’s portable software, meaning it can live on a thumb drive and does not have to be installed in the usual fashion. It’s tiny; nay, microscopic (the executable is 1.1 MB!!) and lightning fast. It doesn’t have all the fancy eye candy of modern software, but it’s amazingly capable, and highly focused on the core mission of getting documents down and formatted. It has a spellchecker and other interesting features like an “over-used words” detector. It reads and writes .doc, .docx, and .odt (ODF) files, and here’s the wild part: It exports to EPub.

Furthermore, it does a mighty good job of it. I loaded a .doc of my story “Whale Meat” into Atlantis and then exported it to EPub. The generated EPub file passed the very fussy EPubCheck validator immediately with flying colors. Now, this was pure text, without any images or embedded fonts or other fanciness, but that’s ok. You have to start somewhere, and I would prefer to start with a genuine word processor.

I then loaded the EPub file that Atlantis had generated into Sigil, which I used to divide the story into chapters and add a cover image. Sigil isn’t really a word processor in the same sense that Atlantis or Word are, but it allows split-screen editing of WYSIWYG text on one side and XML/XHTML code on the other. Sigil 0.2.0 had a bug that generated an incomplete and thus illegal IMG tag (XHTML requires the ALT attribute) but I see that the new 0.2.1 release fixes that. Adding the ALT attribute manually in Sigil 0.2.0 allowed the EPub file to pass EPubcheck without further errors.

I have not yet generated a TOC in Sigil, nor have I attempted to create an EPub of any significant size. (“Whale Meat” is only 8,700 words long.) When I’m through playing around, I’m going to load the entire .doc image of Cold Hands and Other Stories into Atlantis, export it to EPub, semanticize it in Sigil, and see what I have. At some point along the way I may be forced to hand-code (or at least hand-correct) the XML or XHTML, and you’ll hear me bellyache about it when I do. But I will admit that I’m pleased with what I have so far. Yes, Atlantis and Sigil ought to be one product, or at least two closely-knit utilities in the same product family. Still, given the primitive state of the EPub reader business (I have yet to find a Windows or Linux-based EPub reader that I’m willing to use) I’m satisfied with the way that Atlantis and Sigil cooperate. Now that Apple has anointed the EPub format for iBooks, I’m guessing that EPub-related improvements will be arriving thick and fast in coming months.

Cold Hands and Other Stories

CHCoverPrototype.png

I’m sure I’d be a lot more famous if I weren’t so slow, but better late than never: I’m pleased to announce that Cold Hands and Other Stories is now available from Lulu.com in print form, with cover art by the estimable Richard Bartrop. Trade paperback, 230 pp. $11.99.

The body of my short fiction divides pretty much in halves: Stories focused on AI, and stories focused on everything else. I published all of my AI shorts in Souls in Silicon back in 2008. Cold Hands and Other Stories contains everything else, albeit with a new excerpt from my nanotech AI novel, The Cunning Blood. And “everything else” covers a lot of ground: spaceflight, aliens, religion, calculus, witchcraft, and steam locomotives, or at least steam locomotives hacked together from alien parts that probably weren’t intended to go into steam locomotives.

Most of the stories have appeared in print before, and one, “Cold Hands,” was on the final Hugo ballot in 1981. There are a few new ones, including one as new as late last week. Here’s the lineup:

  • “Cold Hands” (from IASFM, June 1980)
  • “Our Lady of the Endless Sky” (from Nova 4, 1974)
  • “Inevitability Sphere” (from IASFM, Sept./Oct. 1978)
  • “Whale Meat” (from Starwind Magazine, August 1977)
  • “Born Again, With Water” appears for the first time.
  • “Drumlin Boiler” (from IASFM, April 2002)
  • “Drumlin Wheel” appears for the first time.
  • “Roddie” appears for the first time.

Rounding it out is another excerpt from The Cunning Blood, different from the one I published in Souls in Silicon, and not available anywhere else but in the novel itself.

A big chunk of the book involves the Drumlins world, which I introduced in 2002 and intend to do a lot more with. Calling it steampunk isn’t quite fair, as it doesn’t take place in Victorian times and corsets are mentioned exactly once. Someone described “Drumlin Boiler” to me as “hillbilly steampunk” (steambilly?) and while that’s a surreal notion, it may be as close as you’ll come.

Yes, an ebook edition is planned, though given the sad, fragmented state of the ebook world right now, it’s going to take some time to kick the file down the tool chain into all the requisite formats. Fortunately, Lulu is a certified aggregator for iBooks, so once I have an EPub that passes the gnarly epubcheck test for standards compliance, I’m going to give it an ISBN and let Lulu list it on iBooks.

As always, blog mentions and reviews are much appreciated!

Odd Lots

mysteryimage500wide.jpg

  • Pete Albrecht sent the above image, and challenged me to characterize it. What would you call it? (Answer at the end of this entry.)
  • The people who created the indie WWII film The Downfall have had enough, and persuaded YouTube to pull hundreds of parodies of the well-known scene in which Hitler freaks out when he learns that the Soviets are closing in on Berlin and the war is lost. The film is in German, with English subtitles. People were swapping in their own subtitles, and whereas the first one (or maybe two) were funny in a painful way, after I watched three or four I had had enough myself. On the flipside, it was a fortune in free publicity for a film I’d never even heard of before people started sending me links to various parodies.
  • Another Web site (following the example of Ars Technica) started banning people for even mentioning AdBlock on their forums. They retreated, defending their position all the way. The problem here is that ads can be malware injectors, and unless Web sites can guarantee clean ads (which isn’t easy, given how current ad systems work) I’m with the blockers here.
  • Assuming that this is legit, it may be our best hope yet for fighting cancer after metastasis.
  • Ditto a new broad-spectrum mechanism for knocking out viruses. (Thanks to Frank Glover for the link.)
  • For people who hadn’t read my earlier entries about it, Fat Dogs (see the photo of their sign in my April 19th entry) is a small chain of gas stations/convenience stores in western Nebraska. They’re so small they don’t have a Web site. That doesn’t mean they don’t have a great sign and motto. (“You Are Nowhere.”)
  • Book publisher Penguin Australia published a pasta cookbook, one recipe of which calls for “finely ground black people” instead of “finely ground black pepper.” Although Penguin hasn’t copped to it yet, this reeks of an instance in which a mispelled form of “pepper” generated the suggestion “people” in the spell checker, and some underpaid knucklehead editorial staffer clicked on “accept all.” I gave that lecture to a couple of my staffers ten years ago. You’d think the publishing world at large would have internalized the danger by now.
  • NASA’s Solar Dynamics Observatory satellite goes live today, promising the best solar images we’ve ever obtained.
  • Give up? (See first item in this entry.) It’s a…bichon frieze.

CBZ Files as Image Archives

Last fall, I gathered a stack of Alma-Tadema‘s paintings from my pre-1923 images folder, wrapped them up into a ZIP file, and sent them to a friend who was looking for a copyright-free color cover for a novel. Some weeks ago, I learned that the CBZ (Comic Book Zip) file format is nothing more than a ZIP file with a different extension. I downloaded and installed a free CBZ reader called Comical. After changing the extension on the Alma-Tadema archive to .cbz, I double-clicked on it, and boom! There it was, beautifully presented and trivially easy to click through. And if you change the extension back to .zip, you can de-archive the images in the usual fashion using any ZIP-capable archiver. It’s all in the extension; no changes to the binary archive need to be made.

Not being a comics guy, I’d never heard of the CBZ format, though it’s been around since 2004. It’s basically an ebook reader protocol (since it is, after all, simply an ordinary ZIP archive) that opens a .zip file and displays the files in alpha order by filename. If the files are displayable as images, the reader displays them. If the files are not displayable as images, a well-behaved reader will ignore them. (Comical, one of the simplest free readers, sometimes crashes when it encounters a non-image binary.) If you need an indicia page, some readers will display text if it’s in an .nfo file. The .nfo will appear in a separate text window on opening the file, rather than in the page display area.

I’ve tested four free CBZ readers: ComicRack and Comical under Windows, and QComicBook and Comix under Linux. All but ComicRack are open-source. ComicRack is overkill in a lot of ways, though it works very well. (It requires the .NET framework, if that’s significant to you.) Comical is much simpler, and my only gripes are that it doesn’t display .nfo files, and it crashes when it finds certain kinds of non-displayable files in a .cbz archive. QComicBook is a Qt4/KDE app, and the one I find myself using under Linux. Comix (a Python app) works well but is not as capable as QComicBook. (Feature-wise, it’s on a par with Comical.) Others exist. Okular will open CBZ files without complaint, but it simply scrolls vertically through the images without attempting to show one per click.

Most of the comic book readers also read CBR and CBT files, which are RAR and TAR archives, respectively, and work almost exactly the same way. (I haven’t tested those formats.)

The CBZ system works best when all the images in the archive are the same dimensions and aspect ratios. I’m putting together some photo albums for showing the folks back home that are collections of digital photographs in one (big) .cbz file. The bigness is mostly unavoidable, since JPG files don’t compress very well. Still, it makes file management simpler

Here are some sample CBZ archives that I put together for testing: Alma-Tadema (14 MB). Hi-Flier Kite Catalog 1977 (6 MB). The “Elf” Space-Charge Receiver (1.7 MB).

Odd Lots

The Pulps Reconsidered, Part 2

bakehead.jpg

Back in my Febrary 23, 2010 entry, I began a series about the pulp fiction mags of the first half of the 20th Century. Because most people would assume I’ll be talking about SF, I deliberately went elsewhere, to a category most of my readers have probably never even heard of: railroad fiction. I bought and have been reading some 1930s issues of Railroad Stories magazine, published by the Frank A. Munsey Company, which in 1882 basically invented pulp fiction mags as we know them.

I can give you a good flavor for the genre with a single 300-word excerpt, from a story called “Bakehead Hennessey,” by Ed Samples, in the August 1935 issue:

Barney softly coupled his two engines into the head car. An “air” man connected the hose. The compressors on the head engine cut in, racing, clicking, thumping, forcing the train line pressure up to ninety pounds. Barney glanced at his gage, then out toward the yard office, where Conduc­tor Gardner was running to the plat­form with two sheaves of green and white tissue in his hands. Behind him waddled stout Superintendent Moran. A second later Old Tom Ryan was climbing down upon the brick plat­form to meet Gardner.

Barney watched him, glanced once more at his air gage, then toward the rear. An inspector’s light was saying: “Set the air.” He opened the valve, watched the needle swing back, then closed it; and wiping his hand on a piece of cotton waste, went striding toward the men who were comparing watches and reading train orders.

The conductor handed him his set of flimsies in silence. There were only three: two slow orders and the running order. He glanced at the latter.

“Running us as Second Seven?” he asked, looking at Gardner.

Gardner nodded. Barney read the order through. He knew that never in the history of the road had such a task been laid out for an engineer: to clip sixty minutes off the time of No. 7, the fastest train through the Rockies on any line.

Air pumps were racing. The pop valve on the 3775 opened and white steam climbed skyward. A dozen lights darted hither and yonder about the steel mail cars. Superintendent Moran came panting up to the group.

“We want action on this run tonight,” he began.

“What the hell’s the use uh puttin’ out a fast schedule for that sizzlin’ bakehead?” snarled Old Tom. “He’s got you fellers all buffaloed into thinkin’ he’s a hoghead. Hoghead! Bakehead! Bakehead Hennessey!”

‘Nuff train talk for ya? I’m the son of a passionate railfan and have researched railroads more than most people, but I still had to look some of this stuff up. A “bakehead” is a locomotive fireman, who stokes the engine manually or maintains the stoking machinery. A “hoghead” is the engineer of a freight train. “Flimsies” are train orders, often printed on something just a hair better than tissue paper. Nonetheless, if you know the jargon, this scene will be utterly clear to you, and back in 1935, this was not nostalgia but the way the railroad industry actually worked.

Nor is this unusual within the genre. In the two issues I’ve read so far, all the writing is precisely like this, in that what matters are the trains. The people are types, which isn’t to say they didn’t exist in the real world or are somehow badly drawn in the tale itself. (Not everyone is an American Original.) But descriptions of their internal conflicts and personal growth were not what the reader was paying for. In a way very much like the Tom Swift books I read in the early 60s, the railroad pulp stories (and I’m guessing all pulp stories) were created to help people imagine themselves in certain roles and in certain situations. The people (thinly) depicted in the stories were like halloween costumes, in a way, to be put on by people who wanted to imagine themselves as railroad engineers and brakemen, or perhaps remember being railroad engineers and brakemen years ago.

This should be obvious, and it may be obvious to you, but I’m amazed at how some people just don’t understand why pulp fiction was ever popular. A lot of people would consider the railroad pulps bad fiction because they focus on technology (railroad tech, such that it was in 1935) rather than inner conflict and growth. Swap in “spaceflight” for “railroads” and you’ll have pulp SF of the same era. The railroad pulps had their share of adventure and fistfights and gunplay, but I was amazed at how close the action stayed to the tracks. And just as superb writers like Robert A. Heinlein stepped aside from the action to teach lessons on orbital dynamics, the railroad pulp authors sometimes taught lessons about their beloved technology. Read this excerpt from “When Destiny Calls” by E. S. Dellinger, the cover story in the August 1935 issue. It’s dense, but if you love trains you’ll understand the frightening energy contained in a boiler full of steam (enough to lift a 100-ton locomotive two and a half miles into the air) as well as how the devastating boiler explosions common during the steam era actually happened. I’ve ridden behind a couple of steam locos on tourist lines. That excerpt gave me chills.

Which, of course, was part of the package. The firms that published pulp fiction knew exactly what their customers wanted: a sense of being somewhere else, somewhere vivid and colorful, somewhere better and more exciting than a boarding house during the Great Depression, after a twelve-hour day at a mindless job in a sweltering factory that paid a quarter an hour.

The pulps were hugely successful for quite awhile. The writing wasn’t great, but it was nowhere near as bad as people make it out to be. Much of its “badness” was the focus on action, setting, ideas, and a certain sort of culture. The words could be carelessly arranged, but words can be fixed, and there is a particular skill in creating vivid settings and action scenes that few people understand until they realize that they don’t have it. The concept of pulp fiction deserves better than it’s gotten in recent decades. It didn’t even completely disappear, though the psychology is a little different these days. More in Part 3.

Odd Lots

  • Never fear; I’ll return to the pulps discussion shortly. I’m way behind on a lot of projects right now.
  • One of the few things I remember about the old 40s Flash Gordon serials (which played incessantly on Saturday morning TV in Chicago circa 1960) are the Rock Men, who could blend into the rocks to escape giant lizards with poison breath. They talked weirdly, and eventually we figured out that they were talking backwards, but none of us had a tape recorder in 1960 to reverse it and see what they were actually saying. Finally, somebody has done it.
  • Popular Science has posted the entire 137-year run of its back-issue archives on the Web via Google Books, and you can read it all for free. The whole mags have been posted, including the advertisements. Maybe this time I can find one of those weird ads for the Rosicrucians.
  • Gizmodo is beginning a series on Microsoft’s Courier project, which is starting to look more like the ebook reader I’ve always wanted.
  • A link on the Make Blog concerning the Vacuum Tube Radio Hat (which I’ve seen before, on Wikipedia, with schematic) led me to Retro Thing, which has just eaten a goodly portion of my morning. Be warned.
  • BTW, the model in the Radio Hat cover story above is Hope Lange at age 15.
  • I had plum fergot about Boeing’s X-37 spaceplane (and this is probably just what the Air Force wanted) but it will apparently be launched on April 19. Don’t get too excited; it’s a robot and won’t carry humans. (Of course it won’t. It can’t. Impossible. They said so. The subject is closed. How ’bout those Blackhawks?)
  • I’ve seen this time and again among the Pack here, but I never knew it had a name: The Nose of Peace. (Thanks to Bruce Baker for the link.)
  • Be careful how you talk in front of very small children, even (or especially) girls. (Thanks to Mary Lynn Jonson for the link.)
  • I have no idea what to think about this: A site that creates techno music from…Web sites. Read the algorithm description under “About.”