Entries for November, 2005

Continuing on …. “PDF vs EXE”

Friday, November 4th, 2005

These are the two main types of files used for ebooks right now.

PDF
PDF stands for Portable Document Format, originally created by Adobe, and is currently used by anyone from corporate big boys to the smallest self-publisher.

PDF has a couple of things going for it that the other ebook formats can’t touch. For one thing, PDF is a universal format. A PDF ebook can be viewed on any computer running any operating system - doesn’t matter if it’s Windows, Mac, Linux, Unix, BeOS, Sun, or anything else. The ebook can be read, and will show up looking the same on all the operating systems. This is a huge advantage over .EXE ebooks, which can *only* be read on a computer running Windows.

Other advantages are the graphics, fonts, colors, etc that can be used in PDF files. Fonts are embedded into the PDF, so you are not restricted as you are in .EXE ebooks, colors are exact, graphics are a snap. In my opinion, you can create a much more professional ebook when you have the capapability of having the ebook look exactly the same on everyone’s computer. Also, although many people don’t realize it, you can also embed any other type of file into a PDF, use page transitions, add JavaScript, and pretty much do anything you want with the file. Some of the smaller ebooks I create are done in a type of Powerpoint format - full screen, dark background - like a slideshow, yet it’s still all PDF.

EXE (HTML)
Let’s face the facts here. The “.exe” ebooks are really nothing more than HTML pages compiled together. An HTML ebook is a glorified web page. Being a web page, it’s subject to all the problems web designers have to put up with.

First, there is the problem of fonts. HTML (which is dependent on the Internet Explorer engine) can only use the fonts that are on the *reader’s* machine. Yep. Forget about using those great fonts you picked up on the net. You are stuck with the reader’s fonts, and if his (or her) computer doesn’t have the fonts you specify, the Internet Explorer engine will actually substitute the fonts the reader *does* have. God only knows what your ebook will end up looking like! Your designs are restricted to the lowest common denominator.

Next we have the problem of screen resolution. Some of your readers will be using an 800 by 600 screen, some 640 by 480, some 1600 by 1200 - there’s no telling, and certainly no controlling it. If you are designing on a computer with 1024 by 768, you have to take into account that there will be a whole range of screen resolutions out there. You cannot specifiy a font size - you have to relative sizes to make it look somewhat the same on all computers.

Design is next. If you’ve ever designed a webpage, you know how difficult it is just to place a line where you want to using HTML, much less do a whole ebook design! You’re just asking for a huge headache. There are templates out there, though, that can ease this pain a bit. Still, it’s a nightmare. Add in the limitations of color, and your designing with your hands in handcuffs and a blindfold over your eyes.

The final, crushing blow - the one that puts the nails into the HTML coffin - is that HTML ebooks (yes, all the ones that have the “.exe” extension) can only be viewed by people running Windows. Why on earth would anyone want to restrict their market to a group that is becoming smaller by the day?? The trend is that as people grow out of the “newbie” stage with computers, they start looking for operating systems that are more stable, less prone to attack, and a whole lot less retsrictive to use. Windows may always be the “beginner’s” operating system, but the savvy user is looking for more… just keep that in mind.

There should be no question in your mind which format I prefer. As a matter of fact, I’ve even restricted my ebook designing to pdf format, and now refuse to design HTML ebooks anymore.

There are a few things, though, that HTML ebooks can do better than pdf, and they all have to do with security. HTML can use the powers of Windows to create some pretty strong security measures to protect your ebook from piracy, etc. If you are adamant about no one ever being able to read your ebook who hasn’t paid for it, then stick with HTML. Your paranoia will be eased, but remember - like birth control, nothing is 100% (except abstinence.) But, security is the topic of another chapter - and you may be surprised to learn that there are some things that can be done to protect pdf’s these days….