Now Serving number 8,911,336

Got my first hits from Technorati this weekend. Followed them back just to see what I look like from there. It is strange to see one’s words next to a flashing CapitalOne credit card ad, but such is life. Technorati also tells you where you rank in terms of popularity of the blogs it lists. Me? I have rocketed from nowhere to um, 8,911,336th place. Hey, everybody’s got to start somewhere. At least I cracked 9 million. I don’t think I could handle being over 9 millionth in line. I get antsy if there’s more than 2 people in front of me at Target.

Then I think, there’s somebody out there with the least popular blog in the world. What number is that? And what the hell are they writing about?

Anyway, I promise not to put (many) funny pictures of my cats “has cheezburger” to inflate my numbers.

And watch out Mr./Ms. 8,911,335, I’m gunning for you.

In terms of actual publishing stuff, I got an invitation today to an interesting conference that I probably won’t be able to attend, but I’ll read up on it anyway. It’s T.H.E. Journal’s Congress on the Future of Content. The goal is to “bring together leaders from all aspects of the educational publishing industry” and address 2 questions:

  1. What is your vision for content and how content should be delivered within the next five years?
  2. What are the barriers to implementing that vision?

Since educational publishing still pays my mortgage, and my kids are consumers of this stuff for 180 days a year (alongside vast amounts of Pepperidge Farm Goldfish), I will keep an eye on this one. I have my own answers to those two key questions, and I’d love to compare them to what the people at this conference are saying. Hopefully, they’ll post some public papers.

Apple is going to be there, but interestingly, no Adobe. C’mon people, there’s an opportunity here. Flash RIAs in the classroom, study hall, teachers’ lounge, on the bus (where my son does most of his homework)? Bring it on.

Boston Web Design Class Experience?

Hey pubLISHers, I have a question for you. I got a request today for a recommendation on a Web design class in the Boston area. I’ve never taken one outside of a conference, so I had no advice to give. Do any of you have any experiences, good, bad, or otherwise to share?

Book Group: The Big Switch

Welcome to the first meeting of the Publicious Book Group. Take a seat anywhere. Coffee’s over there. Our first book is The Big Switch: Rewiring The World, From Edison to Google by Nicholas Carr. I saw it in with the new books at the library, and despite it’s aggressively undesigned cover, checked it out.

plish006-bigswitch.jpg

I’ll read it over the next couple weeks, and post my thoughts back here. If anyone wants to join in and read along, or if you’ve already read The Big Switch, please comment and make this a conversation.

The Book

The book is about about the impending death of desktop computing, and the takeover of web apps. Seems quite relevant to publishing industry and the tools I talk about here. Just look at Photoshop Express, moving a big complicated app and the files it processes from a desktop machine to a hosted “data cloud.” Sure Px is to Photoshop CS3 as Fruity Pebbles is to the Honeymooners. (Stay with me, there.)

If Carr is right, some day in the not too distant future there won’t be a desktop version of Photoshop. We’ll have to subscribe to some level of Adobe Creative Suite Service to use it. I can see it now. “You have 500 Nationwide Photoshop Minutes Remaining on your account. To add minutes or brushes to your palette, press 1. To speak with a Prepress Expert, press 2…”

On the plus side, I imagine the History palette will include every keystroke I ever made. On the downside, I’ll probably only be able to afford the Cheap Bastard tier of services, and the “Blade Runner Enhance” filter will be grayed out.

The Big Switch also seems relevant to me personally, since at work I’ve just witnessed a transition where many skilled people and the machines they used left the building. That move would not have been possible before a Web-based workflow. And I get the sense that more and more of the apps I use at work will soon float off into the cloud. Maybe I will too.

The Author

I am arriving late to the Nicholas Carr party, just as I was late to the blogging party, but I think there’s still some Doritos left in the bowl. The man that Wired describes as “high tech’s Captain Buzzkill” set off a literary bomb in tech circles 4 years ago with the publication of Does IT Matter? Information Technology and the Corrosion of Competitive Advantage. Google Books has about 30 pages that you can peruse.

Guess he felt like the original title, IT Doesn’t Matter gave away the ending.
The basic premise was that IT’s importance is dwindling, since 1) everyone has it, and 2) it’s become so standardized, it’s a commodity, like water or electricity. You need IT to do business, but spending more won’t give you an edge over your competitors. And the best strategy is to be on the trailing, not leading edge of innovation.

With Chapter titles like “Vanishing Advantage”, and “Managing the Money Pit”, he wasn’t exactly cheering on the geeks. Needless to say, this ruffled the feathers of some rather large birds. The book managed to piss off Microsoft, HP, IBM, Intel, and every guy who ever plugged in an Ethernet cable at work. Entire conferences were devoted to de-bunking the book. So I guess the catering industry likes Carr.

Further Reading

Nick Carr’s blog

His regular old-fashioned website complete with drop-shadowed torn paper banner

And the inevitable, Does Nick Carr Matter?

Sometime when you’re you’re feeling especially meta, check out the Wikipedia article on Carr, which attempts to describe Carr’s description of itself and the rest of Web 2.0. Holy circularity Batman! I’m blogging about a Wikipedia entry about an author writing about blogging. It’s starting to feel like the scene in Being John Malkovitch, where Malokvitch takes a ride into his own head and everyone’s a Malkovitch Malkovitch Malkovitch.

Malkovitch!

The High Cost of Purple Hamburgers

The plan for this evening was to get the kids to bed, pour myself a tasty beverage and check out Photoshop Express. I intended to sign up, upload some pics and report back what I found out.

I am a tad cyncial about some of the “free” stuff companies offer online. So far, I love WordPress, but it isn’t free to me. I paid to map my domain, and in the future, I’ll pay for more disk space, CSS, etc. I was an Economics major for about 15 minutes, and the only thing that I clearly remember was the prof writing “There’s No Such Thing As A Free Lunch” on the chalkboard the first day. I wrote that down in my notebook, and I think it applies here tonight.

I went to the Photoshop Express sign up page and poked around, feeling a bit out of place. The marketing is geared for Millennials and not my vintage GenX sensibilities. The people destined to become “Px Drivers” were born about the same time as my Mac 512k. Or later. It was like I wandered into the Hot Topic in the mall and asked if they had any Max Headroom posters.

Still, I’ve been using Photoshop for 1/3 of my life. I wouldn’t want to miss out on what’s next. So I went for a second opinion. Checked several reviews of the program, read my first freetard vs. paytard flamewar, basically came away feeling like my hesitation was warranted. Still, I went back and did the Test Drive. Here’s what I thought.

1. This isn’t really Photoshop. Or Photoshop Lite. It isn’t even iPhoto. There are 18 tools in all, and they’re made for play, not work.

plish005-burger1.jpg

Drag slider, click thumbnail, and get on with your day. Fine, I get it, but please don’t call it Photoshop. Photoshop is a $650 badass program. Those two things go hand in hand. Maybe I’m weird, but I actually like having a program so deep and rich that I struggled to master it (and keep up with it). And deep down I know this is just my issue. Adobe’s smart use of their brand is about to result in an army of new people who call themselves Photoshop users.

Also, as an RIA, Px performs really well. It’s as slick and smooth as can be. Everything is intuitive and handy. And those kids at Hot Topic will probably love it.

2. The Terms of Service, which those same kids will never read. As of now, the way it’s written should give them pause. Particularly Section 8.

“Adobe does not claim ownership of Your Content. However, with respect to Your Content that you submit or make available for inclusion on publicly accessible areas of the Services, you grant Adobe a worldwide, royalty-free, nonexclusive, perpetual, irrevocable, and fully sublicensable license to use, distribute, derive revenue or other remuneration from, reproduce, modify, adapt, publish, translate, publicly perform and publicly display such Content (in whole or in part) and to incorporate such Content into other Materials or works in any format or medium now known or later developed.”

Now I’m no lawyer, but that sure sounds like you just gave away your pics. For free. Forever. For what ever Adobe or anyone they sell your pics to feels like doing with them. They say they don’t own your pictures, but for all intents and purposes, they do. For giving you the ability to show your friends that purple hamburger. Free feels really expensive. I need to ask some of my friends who make a living with photo permissions what they think of this and report back here.

When I decided to start a blog, ownership of the content was one of the first things I wondered about and researched. It’s one of the reasons why I went with WordPress. I love the fact that I can easily get an XML dump of the entire blog. I bought a domain to keep the content at the same address should I ever decide to part ways with WP.

The WP Terms of Service offer quite a contrast to Photoshop Express. Hopefully I haven’t missed a Draconian clause buried somewhere that says they own my kids, my car, and the contents of my fridge.

I was glad to read that Adobe has responded to people’s concerns, and is re-writing the Terms of Service.

Family Cookbook 2.0 continued

When we left off with our project, we had transmogrified the cookbook Quark file into InDesign, and a made few observations about the potential work needed to make it the apple of our cross-media eyes.

plish004-fritter.gif

Remember, what we (I) have to work with is Quark Xpress 4.11, InDesign CS3, Acrobat, and no scripting knowledge, Xtensions, Xcetera. At the finish we want to serve up our cookbook content in an nice HTML/CSS website, plus a new InDesign doc for print.

Before we start working in InDesign, just so you’ll never think I’m lazy (crazy, sure; lazy, no) here’s a list of alternate methods I explored for getting the content out of that old XPress file, and why I didn’t choose them.

The Roads Not Taken

1. Quark to ASCII: yields nice clean text, but no hooks to attach the XML tags to, and the text from the recipe cards gets left out since it’s not part of the main story.

2. Quark to XPress Tags: a little more interesting. Any time we hear the word “tags” our ears should prick up. It also gave me a reason to dust off David Blatner’s venerable Quark XPress 4 Book, and read the section on XPress Tags. His enthusiasm about them makes me feel like I missed out on something cool, well geek cool, since I never really used them before. Guess I’ll never know.

Quark’s tagging syntax is quite different from XML. It’s based on presentation and uses only opening tags. So we’d need to be clever about crafting a Find-and-Replace scheme. Before I read A Designer’s Guide to InDesign and XML, I would have just given up and moved on, but that book gave me the confidence to try just about anything with Find and Replace. I’ll spare you the gory details, but in 3 steps, I went from the XPress Tags and whitespace surrounding the ingredients to real live opening and closing XML tags.

plish004-xtagstoxml.jpg

So this method does work. But it kind of hurts my brain. And anyway, there’s that same deal killer of the recipe card content getting left out. Ahh, if only I could go back in time and warn myself not to put that stuff in inline text boxes…

3. Quark to Word: I can save to either Word 6 or Word 8. Both versions crash InDesign when I try to place them. No thanks.

4. Quark to PDF to Word: practically every paragraph is in it’s own text frame and somehow my 6 paragraph styles have ballooned into 44 styles named CM1-CM44. Pass.

5. Quark to PDF to RTF: I had high hopes for this one, since I thought it would reuinte those inline boxes with the rest of the text and have a style attached to everything. But I’ve tried several times to import it into ID and it crashes it every time. Sucks to be me.

6. Quark to PDF to HTML: no cards, plus everything’s chopped to bits in tiny <p> and <span> elements that don’t really correspond to meaningful elements. I think I need a beer.

7. Quark to PDF to XML: This is also kind of interesting, but not in a good way. More like Marshmallow-Peeps-in-a-microwave interesting. Almost everything is wrapped in <P> tags, which alone would be a deal breaker. But I really screwed things up by carelessly making the PDF from Quark with missing fonts, and as a result some of the recipe cards have overset text. Of course, the PDF doesn’t include any of that overset text, so it’s just gone. I also think the missing fonts resulted in some of the ingredients ending up in table tags. Very loose lines of justified text also got put into tables. “Clean-up in aisle 7!”

plish004-justifed.jpg

plish004-tablexml.jpg

8. Quark to PDF to Mars to SVG to XML: OK, I need to stop. You get the point. Besides if I do the work in InDesign, I can make use of what’s already there for the print side of things.

If you just can’t get enough of this text-out-of-Quark topic, by all means check out the InDesign Secrets thread on it. It just makes me jealous that I don’t have access to things like TeXTractor (or a comp vendor in India).

Here’s how you know you’ve drunk the Adobe kool aid: I can’t type the word “India” without capitalizing the “d,” so it’s always InDia the first time. I am no longer capable of InDependent thought. InDeed, it’s InDefensible.

InDesign clean-up

Ahhh, it feels so good to be back in InDesign after all that Quark-Word silliness (told ya I drank the Kool-Aid). Let’s do this quick. I want that text creamed and buffed with a fine chamois, and I want it now. Chop chop. The first thing is to clean up the paragraph styles so they match the element names I want to use in my XML. I have the luxury of not having to conform to a DTD or Schema, so I can call ’em anything I want. For now I’ll stay with simple semantic names. Then I’ll create tags with matching names that match the styles, and I change the default Root to cookbook. I’ll tag the story frame as recipies.

plish004-tagsnstyles.jpg
Now to clean up those two-column ingredients. A quick trip to the Find/Change dialog will suffice. First we replace all tabs in the ingredient style with paragraph returns. I also had some soft returns in there to put comments under ingredients, so let’s replace those with regular spaces. And last let’s use 3 of InDesign’s built-in GREP searches to tidy up any extra returns, spaces, or tabs.

plish004-grep.jpg

Now comes the moment of truth. Mapping Styles to Tags. If I’ve done things right to this point, everything will fall into place. And…I think it worked. The XML is pretty flat but I like what we’ve got here. In a project with more than one destination for this code, I’d want some nesting so that each recipe was a enclosed in a set of tags, and maybe even the ingredients and groups as well. But this is a one-off kind of thing.

plish004-cleantagstruct.jpg

The next step is straight out of A Designer’s Guide… Chapter 9 to be precise. Since there’s no other re-use of this content besides a page on a Web server, then there is no need to get all huffy about keeping the semantic nature of our tags. I already have things grouped consistently, so I can change XML tags to HTML tags, add a few things and I’m good to go. First I’ll change cookbook to HTML, then add a tag called head, and drag it waaaaaaaaaay up in the structure pane, just under HTML. I’ll change the recipes tag to div, and map the card tag to it. The code is starting to look Webbish.

plish004-finalxml.jpg

Let’s export it.

InDesign gives me a little agita on the way out:

plish004-cannotbeencoded.jpg

I tried in vain to find these shady characters. How dare they refused to be encoded! I want to speak to their parent elements!

I thought the warning might have something to do with the Structure Pane Gremlin I’ve seen from time to time. Here he is.

plish004-gremlin.jpg

Has anyone else seen this thing and know what it is? Looks like an Asian character of some sort. He is darn difficult to get rid of. I’ve had to untag and delete all the surrounding content to get rid of him. I thought maybe the Department of Homeland Security had bugged my InDesign file to see if I was a terrorist. Or maybe it’s just a glitch in the Matrix. Nothing to worry about. The Gremlin appeared 3 times in the cookbook code. Unfortuantely, even after removing all 3, I still get the warning message, so I have two unsolved mysteries. But the good news is the code looks fine when I eyeball it in Firefox.

That’s all for now. When we pick this up again, we’ll try to achieve Find and Replace nirvana in oXygen and test my ability to use CSS without making a MESS.

Photoshop Rastafarian

A little news bite for you. During my lunchtime RSS and e-mail grazing, I came across two interesting bits:

1. Mark Logic is hosting a “Webinar” (I hate that Frankenword) on April 8 at 11AM Eastern called “Achieving Agile Publishing — How XML is Changing the Face of Dynamic Content Delivery.”

The basic pitch:

“Attend this event and learn how you can leverage an XML architecture to build out a publishing model that is agile enough for today’s changing market.”

I’ll be checking it out since I came away from the XML Conference last December with a feeling (not actually knowledge, mind you) that the Mark Logic people really “got it” regarding XML workflows, content, and publishers moreso than anyone else.

If you are an XML geek, pubtech geek, or especially if you’re both, here’s the registration form.

Afterwards, let’s all grab a Webrewski and Webscuss the Webifcations of this Webciting Webology.

2. Adobe introduces a new member of the Photoshop family, Photoshop Express. It looks like a flash-based rich internet app version of Photoshop, and it comes with 2 GB of online storage and a hook to Facebook. Looks like I’ll be getting a Facebook account tonight. Hmmm, Flash, Photoshop, RIA, Web 2.0…Everything I’m interested in seems to be merging into one massive thing. Or as I recall Bob Marley once said on a mixtape of mine, “Instead of I and I and I and I, there’s just one I. RAS-ta-far-I.” Man, I miss Bob.

I’ll post the next installment of our XML cookbook project tonight.

And now, back to lunch.

The Themes Are A-Changin’

Just a quick note to say, I changed the theme tonight. The old one was bugging me for a few reasons so it had to go. It wouldn’t let me add an RSS link to the sidebar, the calendar entries were too subtle, and let’s face it, it was kind of boring. Not nearly ‘licious enough. Hopefully this is a step in the right direction. I’ll add a nice picture to the header soon, and maybe tweak the CSS if time permits (and I decide it’s worth the paid upgrade). I’m not crazy about the padding and borders around the images. If anyone has a strong opinion either way on the new theme, speak up.