At times, I decide to shed the silken cloak of Mac OS X/Darwin/Aqua/userinterfaceland, and take a walk on the wild side. Actually, calling it a wild side is a bit of a stretch. It’s really more the case that the silken cloak is shed, and I reveal (my) crustyness of being a long-time UNIX user. Specifically? I’m willing to go to no end(s) to prove to UNIX — once and for all, of course — that I’m the master and he’s but a wee Lee Van Cleef, ninja ordinaire.
Screw you, UNIX!
Right. So, I started working on a new book project recently. If I’ve learned one thing over the past 7 years of authorship, it’s simple: use the right tool for writing, so you — and nobody else — will suffer later. This group of would-be sufferers includes the author (who has to add changes during the edit/copyedit phases), the production staff of the book company (who have to DO the copyedit and little things like indexing), the content editor, the production tools staff who’ll do any conversions so that the book can easily be transitioned into a printed form, and the reader who knows good typeset from bad. If one of the people/phases above goes bad? The book is shit; it cannot be said in any other way. And when a book goes to shit, I’m afraid that 9/10’s of the time, it’s the fault of the author.
As usual, digressions and I are compatible. I’ll proceed.
Since I’m dealing with a new publisher this time around, this makes the “lay of the land” different. In the past, I had the dumb luck of dealing with a publisher who’d employed an excellent and skilled production staff; this production staff would (with minimal bawking — might I add) take the crappiest of all manuscripts/formats and beautify them. It was truly remarkable. With this new publisher, we’re expected to submit a manuscript that’s basically complete in terms of content and format. And, making matters more interesting, we had only 3 choices as to which tools we’d be able to use to prepare the book. The first choice was to use Frame(Maker); Frame is great, and complete, and I’ve used it extensively when I’ve written books in the past. Unfortunately, Frame is not cheap, and it’s not currently available as an OS X native. Next! (No, not NeXT, either!). The second choice was to use MS-Word, which is available as an OS X native application. Unfortunately, MS-Word has its own set of problems, and — given my experience with bookstuff — I’d hesitate to write a technical book with it. I won’t expound, as I could go on forever about where Word is inadequate, and why I won’t use it for a project of this size/scope. Aside of where it’s inadequate, Word is also pretty expensive. Next! The third choice was to use TeX/LaTeX. TeX/LaTeX have been around forever, and in some ways, I think that TeX/LaTeX personifies the, uhh, flavor of All That is UNIX; it’s a motherfucker, but when you think about it, you realize that TeX/LaTeX is our motherfucker. And, TeX/LaTeX also intellectually superior to all other text processors, right down to its obfuscation by design.
Yeah, fuck you, TeX! And fuck you too, UNIX!
Now, given my druthers, I’d be apt to pop the whole book into HTML or something equally as stupid, ‘tar’ everything up, and send things along when I was done. But I decided that I’m up for the challenge of building a book from scratch; and I’m taking my pal cms along with me for the ride.
Of course, just using TeX/LaTeX isn’t the fun part. Given the length of time that TeX/LaTeX have been around, the distributions have grown, splintered, whithered, moved, and splintered from withering. The first dog ‘n’ pony show? Finding a TeX/LaTeX distribution and building it on my system.
Question: Where do I find TeX/LaTeX?
TeX FAQ: Fuck you!
Question: Are you saying that there isn’t one?
TeX FAQ: You should already know.
Question: If I already knew, I wouldn’t be asking.
TeX FAQ: Fine, check out Knuth’s TeX, GNU/th TeX (for you Stallman fans out there), genericTeX, TexLive, teTex, thisTex, thatTex, and TexMeX. And as always? Fuck you.
Why, thank you, TeX FAQ!
In ye olde days, when men were men, and operating systems were installed from magnetic tape, hacking software to get it to build was par for the course. Yes, somewhere along the way, Charles Ingles was cast off, and was replaced with Charles Nelson Reilly. Men became less tolerance of vi, and abominations of automation — like Red Hat Llinux — were born.
Okay, that’s not exactly true. TeX/LaTeX, like the cockroach, survived extinction, or at least in part. While it’s alleged to have evoled, the rank-and-file cockroach still can’t fly, but my, it’s more than a bit of a pest. 3 UNIX platforms and 3 weeks later, I finally have TeX/LaTeX and all of its (necessary) extensions built. And still, the Tex/LaTeX software build instructions read to me like an infamous line from the movie “Better Off Dead”:
(To install TeX/LaTeX…)
“Go that way really fast. And if anything gets in your way? Turn!”
And all of this, so we can merely write in another format, convert to TeX/LaTeX and write PDF. It’s worth it. The 20 new hairs on my chest prove it. I keep telling myself that.
“Install TeX/LaTeX, dude. Make a gnarly run like that? And girls will go sterile just LOOKING at you!”
Well, girls? Got sterility?