Random thoughts about publishing

Site Feed

Labels

Palimpsest has moved. Please visit our blog in its new location for the most recent posts from Scriptorium.

Palimpsest

 

In defense of English majors: we can understand business issues, too

Monday, July 27, 2009 — posted by Alan Pringle

In his latest blog entry, Neil Perlin explains how important it is for technical writers to have an understanding of business issues. With such knowledge, they can contribute to cost justifications for decisions that affect them directly. I couldn't agree more with that. It is absolutely in writers' best interests (and a matter of self-preservation) to understand processes and costs.

I strongly disagree, however, with the following assertion:

Writers from fine arts or English backgrounds can rarely discuss cost-justification in finance terms, so they have little input on buying decisions.

I am an English major, and I freely admit I am more of a "words" person than a "numbers" person. That being said, I am no slouch in the finance department. (Calculus is another matter, though.) I know many people with degrees in English and the liberal arts who are quite adept at understanding The Big Picture and developing business cases. Lumping all of us into a "can rarely discuss cost-justification" group is unfair.

Now I need to remind myself not to group software developers into a "can rarely write a coherent procedure" category. (It's easy to make generalizations when you're not the target of them.)

Labels: business, cranky, technical writing

10:34 AM Permalink | |

 

Death to Recipes!

Tuesday, May 19, 2009 — posted by Sarah O'Keefe

I love food. I enjoy cooking and I especially enjoy eating. One of my favorite web sites is epicurious.com, and the kitchen shelf devoted to cookbooks sags alarmingly. Many Saturday mornings, you will find me here.

But I am not happy about how recipes have insinuated themselves into my work life. For some reason, the recipe is the default example of structured content. Look at what happens when you search Google for xml recipe example. Recipes are everywhere, not unlike high fructose corn syrup. Unfortunately, I am not immune to the XML recipe infiltration myself.

I understand the appeal. Recipes are:

• highly structured content
• well understood

But I think the example is getting a little tired and wilted. Let's try working with something new. Try out a new kind of lettuce, er, example. This week, I'm trying to write a very basic introduction to structured authoring, and I'm paralyzed by my inability to think of any non-recipe examples.

I'm considering using a glossary as an example. After all, it's a highly structure piece of content whose organization is well understood. Maybe I'll use food items as my glossary entries. Baby steps...

PS It's totally unrelated, but this article about two chefs eating their way through Durham ("nine restaurants in one night, at least five hours of eating and drinking") is quite fun.

Labels: cranky, recipes, xml

11:17 AM Permalink | |

 

I am not a Pod Person

Friday, February 27, 2009 — posted by Sarah O'Keefe

Confession time: I don't like podcasts.

And I think I know why.

I am a voracious reader. And by voracious, I mean that I often cook with a stirring spoon in one hand and a book in the other. I go through at least a dozen books a months (booksfree is my friend).

So why don't I like podcasts?

1. They're inconvenient. I don't have a lot of interrupted listening time, other than at the gym. And frankly, there's a bizarre cognitive dissonance listening to Tom Johnson interview Bogo Vatovec while I'm lifting weights. I tried listening to a crafting podcast, but that was worse -- my brain can't handle auditory input describing crocheting techniques while simultaneously operating an elliptical machine. So I went back to Dr. Phil on the gym TV. It may rot my brain, but at least it doesn't hurt.
   
2. They're inefficient. I can listen to a 30-minute podcast, or I can skim the equivalent text in 90 seconds.

I've been thinking about what would make a podcast more appealing to me, and realized that it's not really the medium I object to, it's my inability to control the delivery.

I'll become a podcasting proponent when I perceive these properties:

1. Better navigation. Podcasts, like other content, need to be divided into logical chunks. These chunks should be accessible via a table of contents and an index.
2. Ability to skim. Podcasts need to provide the audio equivalent of flipping pages in a book or scrolling through a document while only reading the headings.

Depending on the software you use to consume podcasts, you may already have some of the features. For instance, a colleague told me that he listened to my recent DITA webinar at five times the normal speed:

I wanted to let you know about something in particular. I listened to it at 5x fast fwd in Windows Media Player while drinking a coke. My heart is still racing. You should try it. :o)

Do you enjoy podcasts? Do you have any special techniques for managing them efficiently?

Labels: cranky, podcasts

2:38 PM Permalink | |

 

Can this relationship be saved?

Tuesday, July 22, 2008 — posted by Terry Smith

For 15 years, I was a lovesick FrameMaker groupie. Ask anybody. As a founding member of the North Carolina FrameMaker Users Network (NC-FUN), I went to meetings regularly for ten years to talk about everything FrameMaker: plug-ins, database connectivity, scripting, single-sourcing, structure, obscure features, you name it. I couldn't get enough. FrameMaker was the great desktop publishing love of my life. When I joined Scriptorium Publishing earlier this year, I was given the task of updating Publishing Essentials: Unstructured FrameMaker 8. Yes! FrameMaker and I were inseparable.

But then FrameMaker 8 absolutely refused to produce an acceptable PDF file.

Whatever anybody might say about FrameMaker, one thing was always true: FrameMaker produced top-of-the-line PDF files. If you needed good PDF files, you included FrameMaker in your workflow. Now, PDF files produced from FrameMaker were a mess. Sure, some PDF problems had cropped up with earlier versions (and what relationship doesn't have a few PDF problems?), but it was worse now. Much worse. Undeterred, I tried a lot of things. I found some workarounds, but the problem was never really fixed. I could get text and high-quality pictures or I could have hypertext links, but not both. I felt angry and betrayed.

Pfft. Why not dump FrameMaker completely and just move my content to a dedicated XML editor? After all, XSL-FO could also give me a lot of trouble followed by lousy PDF output. I was this close to telling FrameMaker to hit the bricks.

Then Microsoft released a hotfix that patches the problems with Windows that are apparently the root of FrameMaker's PDF problems. So it's not all FrameMaker's fault after all. I applied the hotfix and FrameMaker is back in the house...

...but sleeping on the couch. I'm still miffed about the new conditional expressions. That's a post for another day.

You have to request the hotfix to get it: http://support.microsoft.com/?id=952909.

Labels: cranky, FrameMaker, humor

2:34 PM Permalink | |

 

Garlic Delight

Monday, June 23, 2008 — posted by Sheila Loring

Today, a few traveling coworkers missed out on Georgina's fragrant garlic rolls. Simon and Sarah, here's a photo for your viewing pleasure:

On our last visit, a few of us were a bit cranky when our waitress didn't serve the rolls. And in the lunch rush, we had no time to demand the greasy little delights. This time, thank you very much, the basket was delivered shortly after we ordered.

It's the little things...

Labels: cranky, garlic, georgina's

5:41 PM Permalink | |

© 2009, Scriptorium Publishing Services. Legal Stuff