Tuesday, June 17, 2003

This weekend I searched unsuccessfully for a Movable Type plug-in that would create a PDF version of Contact Sheet. We know full well that The Web Is Not Print, and even more that Print Is Not the Web (thanks to Dave S. for the reminder). With that in mind, I hacked together my own PHP script bringing you the short history of Contact Sheet in PDF.

The links are gone, the graphics are gone, every bit of formatting is gone making it one bland robotic document. I’m not in the business of creating an HTML to PDF converter, so I threw the CSS out with the bathwater. This is pure text and line breaks, baby.

So does this have any useful purpose? It’s good for saving a simple copy of your weblog, or packaging your blog into one portable file. It’s great for printing out your blog in one fell swoop to save for the year when harddrives are obsolete. I’ve come across great sites wishing there was one PDF that I could grab, saving me the pain of motion-sickness reading that much text on screen.

(Interestingly, two proponents of web standards that I’ve read recently each relate their standardization concerns to current technology becoming obsolete.

In the above Owen Brigg’s design rant:

Just like much of NASA’s 1976 Viking data. NASA can no longer read the format those tapes are in. Researchers are having to review that Mars data by digging through paper print-outs that older scientist hadn’t thrown away.

Jeffrey Zeldman says:

My studio was built around an Akai 12-track, an excellent machine, but with a proprietary format… A year into it, Akai changed their tape format. My master tapes became museum pieces. Then the machine broke down and I couldn’t easily arrange repairs or get parts. This experience would later make me highly receptive to the advantages of common technological standards, as in Web standards.

…but what we really need are less standards and more paper printouts!)

Formatting aside, the main stink is that links don’t work (at least in the printed version, of course), severely limiting the context of many blogs.

I used the R&OS PDF classes, but there are a lot more free PHP-PDF tools available, some with XML capabilities that might be a better way to retain more of the styles and formatting. For this example, I created a new MT template, stripped out all the HTML, and fed it to the PHP script which was an altered version of the sample that came with the package.

If others are interested I’ll make it available, once I peel away the duct tape and rubber bands holding it together. But I said it before and I’ll say it again: it ain’t pretty.


Comments


by spencer » Jun 17, 2003 11:35 PM

What about styling for print? A couple rules would make the main content printable and as beautiful as you want it to be. That's the simplest method I can think of. All the user has to do is File>Print and they can rest their eyes just like you said. It also seems to fulfill all the other benefits of print you spoke about. Besides, styling for print is such an eloquent solution. I hate PDF.

http://www.alistapart.com/stories/goingtoprint/

Comments


by ss » Jun 18, 2003 10:53 AM

Good points.

I don't like PDF in that it's proprietary, sluggish and more bloated than need be. However, there is no other format that will preserve the precise layout of a full page design in a single file with such efficiency in file size (and with such a widely distributed viewer).

I also like the idea of formatting a single page of an entire blog, but browsers have memory restrictions that would limit blogs with 1000+ entries.

Comments


by spencer » Jun 18, 2003 7:36 PM

There is no format period that will preserve the precise layout. Browser inconsistancy is the same in print and web, so you could recreate the same layout in print equally as well as it is created on the web.

Comments


by Leendert Van Gemeren III » Oct 8, 2003 12:33 AM

There's another purpose to pdf on the fly or from html and that's an on line invoice when purchasing on the web. Customers will have an instant invoice with a link to it in the confirmation E-mail. I am working to modify fpdf and even (text or graphical) hyperlinks may work in the document. It is also safer because for regular shoppers it is not an easily altered format so the information on the invoice cannot be changed. A combination with an encrypting class would be even safer. Anyway, it's a work in progress and information is welcome.

Search

Syndication

RSS: .91 / 1.0 / 2.0