Pages to ePub

This was the subject of my query of 2 June 2010. At that time, it sounded like a most fuzzy subject. Today, ePub has become an export option for Pages authors.
Meanwhile, I discovered that it's a trivial task to convert a Pages document manually into an ePub version, using an editing tool such as BBEdit. But I then had no way (since I live in France) of proposing my novel "All the Earth is Mine" to iBooks in the USA. So, I finally decided to submit my novel to the Smashwords aggregator, which meant that I had to abandon Pages and give them an impeccable version of my novel in Word. Funnily enough, Smashwords is shipping my novel to iBooks today (on the same day that the ePub export option becomes available in Pages), and it should appear in their catalog in about a week.

I've put an ePub version of Apple's tiny Pages-to-ePub guide at
http://www.skyvington.com/export.epub
To read it, download the Adobe Digital Editions reader.
If you drop this export.epub file (in fact, it's a zipped container) onto Stuffit Expander, you'll obtain a folder containing all the component files generated by the export-to-ePub option of Pages. An inspection of these files will give you a good feeling for the structure of an ePub document.

Similar Messages

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.

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.

Video Formats in Pages to Epub Conversion

I have included (.m4v) videos in my Pages document and then converted to EPUB. These show up fine when I load the epub directly to the iPad.
However when I try and upload to the Apple iBookstore I am told the videos are in .mov format which the iBookstore doesn't want.
Sure enough when I look at the epub files (in Sigil) the videos are all described as .mov. Even editing the files in Sigil then has no effect.
Anyone know why Pages to Epub conversion puts the videos back into ".mov" format rather than leave them as ".m4v"? The videos were created in iMovie and exported as iphone .m4v files.

This is what Pages User Guides says:
Pages accepts any QuickTime or iTunes file type, including the following:
MOV
MP3
MPEG-4
AIFF
AAC
Maybe you should convert the m4v to something else? You could try to change the file extension to .mp4

Export from Pages to ePub??

Help! I need to export from Pages to epub. I've read the tutorial a hundred times and it says that when you click on "export" one of the options should be epub. However, my only options are pdf, word, or rtf. What am I doing wrong?

If your admin bought the iWork package as a DVD, Pages '09 version 4.0.3 is really the late version available on this media.
As fruhulda wrote, you must get and apply an updater (maybe you must ask the admin to do that, I know that some of them are a bit picky).
PS, since last wednesday, the best Apple tool to create ePub is the free iBooks Author.
Yvan KOENIG (VALLAURIS, France) dimanche 22 janvier 2012
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
My Box account is : http://www.box.com/s/00qnssoyeq2xvc22ra4k

Export pages to epub in ipad

Please tell about size limitations of images and videos while exporting pages to epub.

Follow Peter's advice. Pages ’09 v4.n can export to RTF.
In Pages v5+, you can press command+A to select all of your body text. Then from the Pages menu, Choose Services > New TextEdit Window Containing Selection.
This exploits the fact that Pages v5+ copies content to the Clipboard as RTF text, and its return to TextEdit is preserved.

Pages to ePub: TOC and Title Page

Hello everyone... please help! I'm pulling my hair out.
When exporting from Pages to ePub, I'm having two issues:
1- The Title Page (which is page 1 and has been selected as the cover of the book) does not appear or appears blank. What do I have to do to make it appear?
2- I hear in all forums the need to build a TOC in addition to the one ePub already creates and that appears on the left hand side when the file is opened using an ebook reader. Can anyone please tell me why I have to do this and most importantly HOW to do it?
Thank you very much!!

Thank you for sharing such an informative post! I'd like to offer one small correction.
My company publishes children's picture storybooks in print. These are edge to edge full color pages for those who may not be familiar with this format. Our early ePub's were always disappointing in that we could not duplicate the print format without showing considerable white margins on an e-reader. We have since solved that problem in order to achieve the maximum image size. There will always be some amount of white margin in ePub format, but our image output now nearly fills the screen of any e-reader.
The 600X860 resolution is correct in order to achieve a wall to wall ePub image. The image must be created at that resolution for insertion into the document, and the page setup must also be set at the same dimension, which in inches is 8.333X11.944. You cannot, for example, use a smaller size image and drag it with constrained proportions to fill the viewport at the 600X860 resolution. The exported ePub file recognizes the portion of the image that is beyond the margins of the viewport and it will show up in an e-reader with a large white bottom margin.
Dragging a smaller image than the 600X860 resolution to fill the viewport with unconstrained proportions will work, but of course distorts the image. So, create your images at 600X860, insert them into your doc, export to ePub and you will be happy, happy, happy!

Image export from Pages to epub

Hope this is the right forum.
Question about exporting images from Pages to ePub: What does the following comment mean?
Images beyond the 11MB of un-encoded image data allocation per chapter.
1. Does "images" mean total number in chapter? Or is the 11MB per image?
2. What is "un-encoded image data" please?
Thanks.

I asked the above question because I am writing a book with many pictures, and the exported ePub files for one particular chapter stop including pictures after a certain point.
However, that point is much beyond 11MB. The pics average 600KB, and it includes 45 of them (about 27MB) before stopping.
Thanks for the help.

When creating documents in pages for ePub what dimensions will fit ipad?

when creating documents in pages for ePub what dimensions will fit ipad?

Here you are in a forum dedicated to Pages for OS X.
Most of us don't use Pages for iOS.
Yvan KOENIG (VALLAURIS, France) mercredi 18 janvier 2012
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
My Box account is : http://www.box.com/s/00qnssoyeq2xvc22ra4k
My iDisk is : http://public.me.com/koenigyvan
For iWork's applications dedicated to iOS, go to :
https://discussions.apple.com/community/app_store/iwork_for_ios

How do I change the way the title/author appear and is there any way to remove pages on EPUBs?

Hi all--
I am having a really hard time--I am trying to transfer EPUBs from my Win 7 comp to my Nook Tablet. I bought a lot of books from several non-BN sites because they were lots cheaper and were also sold in bundles--but the site was messed up and sent the books in PDF form rather than EPUB. PDF files won't read like a regular book on my Nook Tablet, so my friend offered to convert them to EPUB for me.
Most of the books turned out fine, but some of them now have a few extra pages at the beginning before the cover image and the correct title and author are not displaying--it seems to instead show the filepath where the file was saved on m friend's computer (C:\My Computer/Documents and Settings...etc.)
So, what I would like to do is be able to edit the EPUB files so I can delete the extra pages at the beginning so the correct cover image will be displayed and to be able to change the file's data sp it will show (and be searchable by) the correct title and author.
I am new to all this, so I appreciate any help you can offer. Thank you SO much for your help!!
--Jamie
P.S. Having the title and author show up correctly so they are searchable and appear in the correct place on my Nook Tablet is the top priority--correct cover pages would be nice aesthitically, but it is not that important.
****ALSO--does anyone know of an app or anything for the Nook Tablet that would allow PDF files to be read just like an EPUB/B&N=purchased book? Currently when I open a PDF, it shows the page in TINY print--you can use pinching to zoom in, but then the file enlarges so it is bigger than the screen, making it very hard to read. I can't figure out any way to enlarge the text but still fits the page like an EPUB does, so I'm wondering if there's an app that would do that--it's hard because you can't try apps before you buy them and I can't teel if they will work from the descriptions.

For sideloaded content the nook pulls the metadata from ePub file itself. I would suggest looking at a program like Sigil or Calibre that will let you edit the metadata in the book to make it appear like you want.
For the PDF vs ePub - No, that's the way PDFs work (think of them as graphics, not text), wheres ePubs are Web Pages - so no you can't them to behave exactly alike without converting the files.

Pages to ePub observations and hints

I've been experimenting with exporting ePubs. Here are some things I have have found that may help others.
These observations are based on Pages v4.1 and iBooks v2.0.1
These truths might be invalidated when new versions of Pages and/or iBooks appear.
There may be subtle distinctions and/or situations where these observations don't work as described. Or maybe for some of them, I have gotten close to the truth but not fully realized it completely yet. Experiment with them at your will.
1. Pages does not and will not insert any "page breaks" (or css causing that effect) in an ePub file per se. When exporting to ePub, Pages ignores any and all page breaks or section breaks you insert into a Pages document. Instead, it splits what it considers to be chapters each into separate xhtml files within the created ePub container. It seems that iBooks is hardcoded to automatically display each xhtml file beginning on a new "page."
2. According to Apple's "ePub Best Practices" document, Pages considers chapters to be delimited by instances of text of the style "Chapter Name". I have found that changing the name of that style does not effect the resulting ePub. Therefore, it is not the style's name that informs pages to use it as the chapter delimiter. Instead, I have found that Pages will look at all the styles you have marked as to be included in the TOC (hereafter called "TOC-included-styles"). Whichever one of these happens to be used first in the document, will be the style that Pages will use to parse chapters, unless the first TOC-included-style used is named "Chapter Number". In this case, that instance of "Chapter Number" is skipped over when considering the style to use as chapter delimiter, and the next TOC-included-style found will be used.
3. Unlike "Chapter Name", the style named "Chapter Number" is required be to named "Chapter Number". This style further affects the splitting of the xhtml files, and therefore, iBook's rendering of "page breaks". An exported ePub will normally be split into xhtml files at the first character of all instances of "Chapter Name". A document that also includes any "Chapter Number" instances will be split at the first character of those instances. The rule, in plain english, would be: split into xhtml files at instances of 'Chapter Name', but if any particular 'Chapter Name' instance has a 'Chapter Number' instance before it, back up and make the split immediately before that 'Chapter Number'. If a "Chapter Name" instance has more than one instance of "Chapter Number" before it, the split will happen at the earliest instance of "Chapter Number" until a previous "Chapter Name" is found. If the last "Chapter Name" instance in a document has any "Chapter Number" instances after it, there will be no split at those "Chapter Number" instances. Any other styles in between any of these instances are preserved, so you could have a new page in iBooks with a chapter number, followed by some text, then the chapter's name. If you rename the "Chapter Number" style to something else, it is then considered like any other style and has no affect on resulting ePub structure.
4. If you insert a TOC into your Pages document, it is ignored for ePub export. The TOC created in an ePub will include whatever styles are checked in the Document->TOC inspector. The ePub TOCs as generated by Pages seem to have only two levels of indentation. The high level is the chapter level, as described above, whatever TOC-included-style appears first in the document will be the chapter delimiter and be the least indented level of the TOC. All other TOC-included-styles, no matter what they are named or how they are configured in Pages, will be placed at indent level two in the resulting ePub's TOC. So, a style does not need to be named "Heading" to be included in the ePub TOC, it just needs to be a TOC-included-style.
5. You can add however many images you want to a chapter, but if the combined file size of the images in that chapter add to more than 1Mb, then the resulting ePub will not display any of the images which cause the size of that chapter to surpass 1Mb.
6. There is talk that a "magic" resolution for images is 600x860 in order to have them occupy a full "page" in the resulting ePub. I have found that any image whose pixel resolution fills the iBooks page viewport will do that, if the image is also set to cause wrap-with-clear-space on the left and/or right. The iBooks viewport seems to be 368x569 pixels when the iPad is held in landscape orientation. So in other words, no matter how large your image is, when viewing on the iPad in landscape mode, it will be at the most 368x569 physical iPad pixels. Therefore it seems to me, if you only wanted to view a book in landscape mode, you could make all your images exactly 368x569, and not larger, making the resultant ePub file as small as possible. But you'd probably want to design the book for portrait mode as well. In portrait mode, the viewport seems to be 547x???. Where I have not taken the time to deduce the exact vertical viewport dimension, but I know it is close to 780px, either way, the image can be smaller than 600x860. iBooks will shrink any image larger than the viewport at hand (portrait or landscape) to fit the viewport. If the aspect ratio of the image differs greatly from the viewport, the image will appear "letterboxed" because the aspect ratio of the image is maintained as it is shrunk to fit the page's viewport.
7. The margins of your Pages document, whether they be document-wide margins, or margins within a section, don't seem to affect the resulting ePub. The document-wide-margins and the layout-margins (in a section) can be set to zero. The on-the-ruler margins can be at the edges of the "paper." Extranious tabs on the rulers can affect things. I find it is best to drag all tab stops off the rulers.
8. Tables are problematic. They are not good constructs to put in ePubs. Pages will dimension tables/columns width based on percentages. So if the overall width of your table drawn in Pages happens to be 50% the width of the "paper", then in iBooks on the iPad, the table will be 50% of the width of iPad's page viewport. An 8.5x11 "sheet" of paper shown in Pages is typically defined as 612 pixels wide* (change your Pages ruler units preferences to Points to verify, the Document inspector will show the page size in pixels). So if you draw your table half the width of that sheet, you get a table 306px wide in Pages. That's pretty good, you can fit a bit of text in a table that wide. But now you export to ePub, and since the iPad's (landscape) viewport is only 368 pixels wide, your resulting table is 50% of that, or 184px wide. Since the size of the text hasn't changed much, now everything is wrapping and going crazy. Column widths are also generated as percentages of the table's width, so a column that fits its content nicely in Pages is now too narrow in the ePub. Confusion ensues. Incidentally, the above assumes your document left and right margins are set to zero, if not, the percentage of width is calculated between the margins, not the edges of the page. What you can do is make the table 100% of the width of the page, in that case the resulting table in the ePub will always be 100% of the width of the page viewport on the iPad. For a bit of left and right margin, you can throw in an empty column to the left and an empty column to the right of your table's content, then shut off the border lines for those side columns so they aren't seen. This won't solve your problems, but might take some of the pain away. If a user cranks the font size up as high as it will go on the iPad, no table remains standing.
* if you do any measuring with on-screen rulers, make sure you set Page's zoom to 100% first, as it defaults to 125%!
9. If you want to get a clue as to how your book will flow on the iPad (in landscape mode for example), you can temporarily set your document's Page Size to be 368x569 pixels (will all margins set to zero). You set Page Size and Margins in pixels (in inspector) by first changing the ruler units to Points in Page's settings. Be careful though, it's an approximate result, not exact WYSIWYG, the words won't end up exactly where you see them.
10. If you have read thus far, you probably already know that the first (on-screen) page of a Pages document can be used to automatically create the ePub's cover image upon export. As mentioned elsewhere on the 'net, floating images can be used on this first page (if they are used elsewhere they are ignored). I have found that shapes, specifically floating shapes can be used on the first page as well. You can even use background shapes! This unlocks the door to creating some truly nice covers with a minimum of work. I have here attached an image of a cover I created in just a couple of minutes without using Photoshop or any other image editor, just Pages. I will describe below how it is done
All the objects on the first page (shown above) is set to floating or background, therefore, you need to move the inline text to the next page. You can do this by inserting a section break. You can see it in the upper left corner. That forces all the text to be shuttled off to next page, out of the way.
First I created the swirly pattern background. To do so, create a box shape on the page and immediately set its Placement properties to "in background". Keep "background objects selectable" and resize it to cover the entire page. Remove any border or shadow from it. Then set its Fill to any seamless pattern you like. Keep the pattern pixel dimensions small so as not to create a large ePub. This particular swirly pattern I created very quickly for free at patterncooler dot com. Set the fill properties to "Tile" so that your pattern is tiled throughout the whole box shape. Now you can uncheck "background objects selectable" so that you can work on top of it without disturbing it.
The size of the pattern repeat itself is important to consider. The book cover will be seen in two places: on iBook's bookshelf (small), and opposite the table of contents in the book itself if the iPad is held in landscape mode. If the size of the repeat is too small, then you cant really make out the pattern in the bookshelf icon because the whole cover has been shrunk down, if the repeat is too large, it might look nice on the bookshelf but funny opposite the TOC. You'll have to experiment, but the repeat used in this example is a good compromise.
Next the brown spine down the left hand side is another box shape. This one's placement is set to "floating". Stretch it to the edges of the page. I filled this one with a subtle gradient to give it a slightly 3 dimensional look. Remember that iBooks will overlay shade an indentation along the left edge to appear as a crease. So dont make it too dark. Remove any border from this box, but give it a shadow on the right, just enought to make it appear affixed on the book. I used shadow settings of Offset 1pt, Blur 6pt, Opacity 75% at an angle of 323. Too much offset or blur ruins the effect. You want it to appear as a very thin layer adhesed to the "book". As for colors, use the eyedropper on the color inspector to pick colors from the background pattern, this will make it "work together" if you are color challenged.
The stitching on the right edge of the spine shape is a simple line shape 2 pts wide. Properties are: dotted, with a very slight shadow (2,4,85%,315). You can use the "bring forward" or "send backward" commands if the stack order gets mixed up.
Next add the Title and Author boxes. They are simple floating box shapes with color fill, and simple black border of 3px. Page's pop-up alignment guides will help you center them in the page. There is no shadow for these boxes as they (here) are supposed to mimic a printed and not a physical adhesion. Instead of a line border, you can also apply Page's "picture frame borders. I went crazy with those, but ultimately came back to the simple line border.
If you want to make these "adhesions" there are lots of nice paper textures on the 'net you can use as fill.
Finally you see there is a slight highlight on the top edge of the book and slight shadow along the right and bottom edge. These make the cover seem to have rounded edges, they give it a 3D appearance. To create the right hand "round over" draw a line-shape the height of the page. Make it 5px wide, and give it shadow properties of 5,4,50%,142. Next you have to move it so that it is slightly off the paper and thus not seen, but close enough that it's shadow is still seen. To move it, you can use a combination of the mouse, the arrow buttons on the keyboard, and/or the position inspector pane. In my example, the page is 600px wide, and the line sits at the 601px location. Be careful about moving shapes off the page, as you can "lose" them. Oddly enough, there is no way to see and/or find shapes that are "off page" (that I know of anyway). If you lose a shape off the page, you have to draw selection boxes blindly, until you stumble upon the shape again. It seems a way to hide content if one so desired.
For the bottom edge of the book, do the same thing with a horizontal line. Shadow angle in my example is the same 142 degrees.
For the top edge, do the same except make the shadow color white. (5,5,50%,270). This shape is hard to select once you have it offscreen. If you want to select it, you might have to move the background and right edge shadow out of the way first. Then draw a small box at the top right corner of the page until you hit it.
And one last detail, you might notice my page size is 600x860px (8.333in x 11.944in). This is because I think this aspect ratio is shaped more like a novel than than 8.5x11in (612x792px). The latter is squarer, and more the shape of a text book.
I hope this stuff has been useful to you.
Dave

Thank you for sharing such an informative post! I'd like to offer one small correction.
My company publishes children's picture storybooks in print. These are edge to edge full color pages for those who may not be familiar with this format. Our early ePub's were always disappointing in that we could not duplicate the print format without showing considerable white margins on an e-reader. We have since solved that problem in order to achieve the maximum image size. There will always be some amount of white margin in ePub format, but our image output now nearly fills the screen of any e-reader.
The 600X860 resolution is correct in order to achieve a wall to wall ePub image. The image must be created at that resolution for insertion into the document, and the page setup must also be set at the same dimension, which in inches is 8.333X11.944. You cannot, for example, use a smaller size image and drag it with constrained proportions to fill the viewport at the 600X860 resolution. The exported ePub file recognizes the portion of the image that is beyond the margins of the viewport and it will show up in an e-reader with a large white bottom margin.
Dragging a smaller image than the 600X860 resolution to fill the viewport with unconstrained proportions will work, but of course distorts the image. So, create your images at 600X860, insert them into your doc, export to ePub and you will be happy, happy, happy!

Cannot find how to export from Pages to ePub

I have Pages '09, and looked on Apple's tutorials for how to export as an ePub file... It says just click share, export, ePub, but I do not have an ePub option. My only options are PDF, Word, RTF, and Plain Text. Am I missing something very obvious?

It's interesting that 'they' have decided to NOT let folks on 10.4 produce an ePub (from Pages). I understand that I cannot 'do' the whole ePub consumer side on this machine but I was hoping to get a bit of a headstart while on the road. (The mini at home base is running 10.6 and is my ePub production environment. That version of iWork9 does have the later Pages, which is why I was surprised when I could not find the same UI on my 'travel' machine.)
As to why I don't upgrade the G4? I need one machine that can run Classic. So it will live at 10.4.11 for the rest of its life.
I have my fingers crossed that today's announcement will include a suitable Macbook Air update ... one that is not too wide and/or too high. (The 13" 'books have been too large a footprint to replace my trusty 12" so I've been holding out...)

HT4168 Pages only exports first ten pages to epub

Hi, community! Here's my problem: I'm trying to export a comic, pasted into Pages, as an epub file but no matter what I do I only get the first ten pages to export. The weird part is that I have another file - where I did exactly same thing - and it exported fine ... all the way up to 60 some pages
I heard somewhere that it might have to do with the Pages file size but the file I'm trying to convert is only 7.8mb.
Help!

It could be something on the eleventh page that is corrupt. Try creating a document page 11 and on and see if it that works. Delete the 11th page if not and try again asf.
The size restriction is 11 Mb per chapter. Read more here
http://support.apple.com/kb/HT4168

Cannot transfer .mov audio from pages to epub

I am a total newbie at making epubs...
I have dragged a .mov audio file made in quicktime into my pages document. It is inline. The audio file works when I click on it (speaker icon) in the pages document.
After converting to epub, the speaker icon disappears and I have no audio available.
Can anyone help?
Thanks!
I have pages version 4.1

It's interesting that 'they' have decided to NOT let folks on 10.4 produce an ePub (from Pages). I understand that I cannot 'do' the whole ePub consumer side on this machine but I was hoping to get a bit of a headstart while on the road. (The mini at home base is running 10.6 and is my ePub production environment. That version of iWork9 does have the later Pages, which is why I was surprised when I could not find the same UI on my 'travel' machine.)
As to why I don't upgrade the G4? I need one machine that can run Classic. So it will live at 10.4.11 for the rest of its life.
I have my fingers crossed that today's announcement will include a suitable Macbook Air update ... one that is not too wide and/or too high. (The 13" 'books have been too large a footprint to replace my trusty 12" so I've been holding out...)

Tabs not moving from Pages to ePub

My Pages doc moved to ePub, and then my iPad great... except there's no tabs. Every new paragraph starts flush left.
What went wrong?

Ahhh that's what you are after.
Yes you will need tabs, or have you tried en or em spaces? I think Pages' ePub "solution" is going to kill either as they really need hand encoding.
I can only suggest you search for explicitly ePub software:
http://www.macupdate.com
This is starting to look much like Apple's previous html feature in Pages. Basically useless until users cottoned on, then it was removed.
Peter

Coverproblem doing Pages to ePub

I have this novelmanuscript. Only text. Right now we'll forget about the page-break-problems :-)
Ok, when I export the Pages (4,3) document to ePub, it works in the validator ePub Checker. Everything is ok.
But when I add a picture as a coverpage as page 1, the validator sees an error:
"ERROR: /OPS/cover.xhtml(5,452): element div not allowed her, expected the element end-tag, text or element "a", "abbr", "acronym", "applet", "b", "bdo", "big", "br", "cite", "code", "del", "dfn" …" and several others
And the only thing I have done, is to insert the coverpic as page 1 in .jpg (have also tried TIFF with same negative result)
Though the validator notes an error, my epub-reader "calibre" reads the cover fine. But the error-report makes it impossible or difficult to place my eBook in certain eBook stores.
Anyone who understands that error message? Or even better: can tell me what to do?

The image IS inline. (I guess what you mean is the choice you get when clicking on the image in the Pages document; you can choose between - in Danish - "integreret" og "flydende", guess that equals "inline" and "floating" ...)
I have tried importing styles from the document mentioned, I have tried the two methods mentioned in that document, I have tried creating a new document from a template and pasting my document in.
No matter what I do, "ePub Checker" gives me the above mentioned error message.
But maybe "ePub Checker" checks something else than the end product in "iBooks" ...
Cause actually the file HAS been made available (free) in iBooks store a month ago with no problems.
But then I decided to sell it for money in the Danish eBooks-stores, and it has got to "pass" the 'exam' made by this "ePub Checker".

Pages to ePub

Similar Messages

Maybe you are looking for