From Pages to epub format

On June 2, in a post entitled Pages to ePub, I evoked the challenge of transforming a novel, written in Pages, into epub format for the iPad device. Over the last week, I've succeeded in carrying out this task completely, in an essentially manual way.

Harrison Ainsworth's excellent tutorial on building epubs, which is perfectly sufficient for the basic stuff, can be found at

http://www.hxa.name/articles/content/epub-guidehxa72412007.html

The first operation consisted of exporting all my Pages files as pure text. Then I used BBEdit (on my iMac) to insert countless pairs of XHTML tags: basically "p" tags. The steepest learning curve for me (as an enthusiastic Flash developer who hasn't touched HTML for years) was getting the knack of how to write a perfect XHTML-oriented Cascading Style Sheets (CSS) file.

Curiously, I was hung up by a trivial obstacle for several days: the necessity of zipping together all my files, to create the final .epub document. Here again, Harrison Ainsworth kindly solved this problem by pointing me to a magic tool (in fact a tiny AppleScript device) that can be found on a MobileRead forum at

http://www.mobileread.com/forums/showthread.php?t=55681

While waiting to buy an iPad, I'm using the Adobe Digital Editions tool on my iMac to display my novel. Finally, the most convenient way of validating the end result consists of using the website at

http://www.threepress.org/document/epub-validate

So, my 318-page novel is now ready (well, almost ready) to be published. I'm awaiting an ISBN number from the French authorities. And maybe I should get a professional graphics artist to produce a first-class cover illustration. For the moment, I haven't looked into the question of whether Apple will be prepared to accept my novel for their iBooks distribution (since I live in France).

I'm now faced by the following tough question: Should I carry on using Pages as a creative-writing tool, or would I be better off using an ebook-oriented environment right from the start? For the moment, there are two or three significant advantages in using Pages for creative writing: (1) There's no technical barrier between the author and his/her output. (2) I can distribute my stuff conveniently to friends and colleagues in the form of PDF files. (3) I can print out pages on A4 paper, for checking.

As much as I'm really fond of Pages, I'm not sure that these advantages justify the messy operations involved in moving to epub format. Consequently, I fear that I might soon be putting Pages in mothballs… alongside Textures, PageMaker and InDesign.

iMac, Mac OS X (10.5.8)

Posted on Jun 11, 2010 4:34 AM

Reply
17 replies

Jun 11, 2010 5:21 AM in response to Gamone

Gamone wrote:

I'm now faced by the following tough question: Should I carry on using Pages as a creative-writing tool, or would I be better off using an ebook-oriented environment right from the start? For the moment, there are two or three significant advantages in using Pages for creative writing:
(1) There's no technical barrier between the author and his/her output.


Not sure I understand what you are saying here, as Pages throws plenty of technical barriers at writers and there are many simpler word processors or text editors which provide output closer to what is required for ePubs.

(2) I can distribute my stuff conveniently to friends and colleagues in the form of PDF files.


You can print to pdf from any OSX app.

(3) I can print out pages on A4 paper, for checking.


ditto

As much as I'm really fond of Pages, I'm not sure that these advantages justify the messy operations involved in moving to epub format. Consequently, I fear that I might soon be putting Pages in mothballs… alongside Textures, PageMaker and InDesign.


I am sure that there will be a large number of apps leaping into the vacuum left by Apple.

btw Indesign CS4 and CS5 both output to ePub without any of the Pages' hassles.

Peter

Jun 11, 2010 6:12 AM in response to Gamone

One caveat for you: while Mr. Ainsworth's tutorial is very good for general epub creation, it is dated 2007. I would suggest reading through the links collected at Liz Castro's blog, Pigs, Gourds, and Wikis for information about the peculiarities of epub creation for ibooks, if you haven't already done so. (A valid epub that passes the Apple validator does not necessarily truly meet the requirements. and there are a number of quirks in ibooks, like the need to include Palatino someplace in your document, or lose all font formatting.)

EDIT Peter, InDesign has its own set of quirks for epub creation, although I agree it's probably one of the best choices right now. (See Gabriel Powell's videos for more about those.)

Jun 11, 2010 11:04 AM in response to Gamone

Thanks for your reactions. I have the impression that self-publishing on the iPad is a burgeoning preoccupation (the device itself only appeared in France a short time ago), and I would imagine that forums (as distinct from self-interested blogs) will soon come into existence. For the moment, I discover that:

(1) It's so easy to create an epub document that looks great on the Adobe emulator.

(2) Nobody seems to advocate Pages as a good starting-point for iPad self-publication.

(3) Apple doesn't appear to be proposing much help to prospective self-publishing enthusiasts (such as me). I even saw an amazing mention of the fact that prospective authors need to have a US tax number!

Once upon a time, I was a white Protestant...

Jun 12, 2010 1:05 AM in response to Gamone

Since this is a forum about Pages, I insist upon pointing out that this Apple tool is by far the most comfortable and elegant word-processing environment I've ever known. And I've known a lot of word-processing environments over the years. I can nevertheless understand what an erudite expert such as Peter means when he says that Pages +"throws plenty of technical barriers at writers"+. As a former adept of a marvelous Macintosh tool named PageMaker, I never stop complaining about the fact that Pages is often relatively dumb. If I decide to insert a trivial press cutting near the start of a chapter in a genealogical monography, for example, Pages obliges me to renumber manually all the figure captions, which is a truly mindless operation. And let's not rub salt into the painful absence of indexes. In any case, I've more or less got over these shortcomings. I manage to live with them. And I persist in thinking of Pages as a great device for playing around with written words. To put it bluntly, using a metaphorical allusion of which I'm not exactly proud, +*Pages on my iMac has become my Word.*+ (Literally, I've trashed every remnant of the latter ugly gas factory.)

Personally, it doesn't seem so long ago (although it was) that I used a pen and paper to map out rough ideas of what I wanted to say, and only resorted to my word processor when the cake needed sugar coating. For years, this has no longer been the case. Pages is truly a "Think Tank" (name of an ancient Macintosh software tool) that makes it an easy and pleasant task to assemble ideas, expressions and images.

The real reasons behind my present ranting (Why isn't there at least a magic button in Pages that churns out some kind of roughly-tagged pure-text XHTML version of the document?) are expressed in my blog post entitled Self-publishing:

http://skyvington.blogspot.com/2010/06/self-publishing.html

Once again, thanks to Barbara and Peter for your helpful reactions. Now, let me get back to my experimenting...

Jun 13, 2010 5:25 AM in response to Gamone

You will find that you can't create a valid epub for sale that way (not without spending many hours fixing formatting issues and putting in the various required code elements), and pdf is the very worst format to try to convert, although you can use calibre to convert a pdf in a way that may be okay for home use.

It's an okay solution for wresting the text from a pdf if that's all you have, but it's not a workflow to choose voluntarily. PDF should always be an end format, not a middle one, if at all possible, in making ebooks.

You didn't mention genealogy before. Are we talking genealogical tables here? If you plan to have graphics in an ebook, everything is more difficult by a order of magnitude, unless you have the skills such that you would be comfortable writing the book in CSS/XHTML.

Believe me, if making a salable ebook only involved: 1. make pdf, 2. open calibre, the publishing world wouldn't be in nearly such a swivet as it is right now.

Jun 13, 2010 8:53 AM in response to PeterBreis0807

Honestly, at the moment if you are writing fiction, the easiest answer is to use Word or one of the Open Office variants and then use an aggregator and let them hassle with the coding parts (although I must point out that there are some difficulties for the future in terms of the publisher code and the ISBN ownership). Or else get really good at writing CSS/XHTML for yourself, or hire someone to do it for you. There are places where you can get a manuscript formatted for all the major outlets.

For any kind of heavily formatted book, I think the solution is to hunker down and wait a bit. People in the industry are still figuring out how to enforce a lot of formatting (there are some magnificent cookbooks in ibooks right now, for instance, but section headers and captions may not appear in the right place if you tinker with the settings), and it remains to be seen exactly what Steve Jobs meant by including PDFs in ibooks. He didn't say "sell PDFs through the ibookstore", and for material where there's any kind of fixed formatting, PDF is still the best way.

There are some serious bugs in InDesign CS5 for epub creation, although the chapter splitting feature is very tempting. But I think a lot of production shops are waiting to see if Adobe will release a point update before moving to CS5, for all the hassles in CS4.

The other big consideration is the platform wars. If you want maximum readership, you will need separate formatting for Nook, Kindle, ibooks, and now there is a new ereader that is going to be sold in all kinds of general purpose stores like CVS, for example. Formatting for that isn't known yet.

Eventually this will all shake out. They are working on a new standard for epub that should help with a lot of the current problems, but that's probably 18 months away or more.

Another option is to publish your book as an app. I did see a press release last week from someone who is selling a kit to turn a book into an app, but I haven't heard any feedback about whether it's any good or not. Or you can do what the Take Control series has been doing: sell a PDF and recommend GoodReader.

I was pretty excited about that blog post last fall where someone claimed to have found ebook creation embedded in the Pages package, but in reality right now it's a highly complex process, no matter where you start, so it's not surprising this hasn't come to pass. My own ideal would be to be able to lay out a book in Pages and use that as the basis for a PDF or just send a perfect epub straight to the ibookstore, but I'm not sanguine that this will ever be possible.

Jun 14, 2010 12:37 AM in response to Gamone

Thanks, Peter and Barbara, for your latest thoughts.

To my mind, a manual approach (using BBEdit on the Mac) is quite satisfactory for converting a novel from Pages to epub. And, once the novel is in epub, there seems to be no reason why the author should carry on maintaining (editing) the original Pages version. I'm perfectly satisfied with the look and feel of the epub version of *All the Earth is Mine* (for which I'm awaiting an original cover illustration and an ISBN number).

In the domain of genealogical monographs, I wasn't so sure that things would turn out as simply as for a novel. I decided that the only way of reaching a firm conclusion would consist of carrying out a hands-on test. So, I took the chapter 7 of my Pages document entitled *They Sought the Last of Lands* and produced an epub version. This chapter contains 67 graphic items, whose dimensions often had to be readjusted. I also had to use Illustrator to export all my .eps genealogical charts (created in Freehand) into .png format. I started work on this conversion at the start of the evening (instead of watching the catastrophic Australian soccer match) and the epub document was running by midnight. So, here's the website that lets you obtain the results:

http://nutopia.free.fr/paternal

You can download both the conventional .pdf version of my chapter 7 and an experimental epub book containing only this chapter 7. On the surface, the contents of the two documents appear to be very similar, but the epub version necessitated lots of small but tedious changes.

My motivations for this experiment were based upon the idea that it might be "nicer" to offer people an epub version (which they could upload onto an iPad) rather than expecting them to consult .pdf files.

Is the conversion task justified? As a genealogical researcher, can I seriously envisage the maintenance of both the original Pages version and an epub version? Or could I maybe adopt an epub-only approach?

My personal conclusion, for the moment, is that I should forget about epub in the genealogical domain, and continue my conventional approach using Pages. An epub content file is simply far too complicated to manipulate.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

From Pages to epub format

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.