Frustration with Pages to ePub page breaks

Hi. I am losing my mind and hoping someone can help...
I am creating a non-traditional book (a catalog) in Pages, for use in both PDF and ePub formats (for iBooks on iPad). I CANNOT get the page breaks in Pages retained when exported to ePub and viewing on the iPad. I used the "ePub best practices" document as my starting template, then changed it by modifying the layout (margins, etc.), and modifying the styles to the font, color and style I want for look of the PDF version. At one point I had 80% or so of the page breaks in ePub, then after making some edits in the document and exporting again, many of the page breaks disappeared. I've also had headlines and such literally disappear in the ePub version.
The best thing would be to have a method of manually entering a page break in Pages that I KNOW would represent a page break in ePub. Is this possible?
Please help!

After an insane amount of testing, here are the unwritten rules that I have uncovered (so far) regarding how Pages exports to ePub.
- The items checked to be used in your TOC (whether you actually have one in your document or not) are what dictate the page/section breaks. This is hugely important because it effects EVERYTHING else, including formatting.
- Using the option to "Use first page as book cover image" will do so, but will effectively suck it out of the actual book when it displays so that your book will "open" to whatever page is next. This sort of stinks if you would like your book to open to the actual Title Page. One solution to this is to turn this option OFF when exporting, and BE SURE to set the title of your book to one of the Paragraph Styles that you included in your TOC list (see above). This will put your title in the auto-generated TOC *created by your reader* (we'll call this the "Reader TOC"), but it will allow your first page to remain your Title Page and should prevent problems with your formatting.
- It would seem that ANY time you start a new section in an ePub (Title, Preface, Chapter, etc… and not to be confused with a Section Break in the Pages document itself) it MUST start with a TOC marked style. If you don't you will start to find your formatting will change semi-randomly (I noticed it in left justified headlines becoming centered). You CAN manually modify the format of the text once you have set the correct style (if you want to change the justification or something).
- Use of the Insert Page/Section Break menu options will have little or no effect in the ePub itself. You can keep them in your Pages document if you like, but *it is the TOC marked styles that completely dictate the section/page breaks in the ePub export.*
- The auto-generated Table of Contents that Pages can create will be dropped in your ePub. The Reader TOC (the actual one used by the readers) will be recreated by the TOC marked sections as mentioned above. So, you might as well leave it out of a Pages document if you are only exporting to ePub. However, most Reader TOC's are not actually present in the text of the book, which is a little weird. To include a TOC in the book itself, you will need to manually create one (without page numbers since ePub's are reflowable), and then manually link it to "bookmarks" within your book. Be sure to use a TOC marked style for the header ("Table of Contents") so it starts on it's own page. Then go through your book, bookmarking sections that you want as TOC entries. The Link Inspector in the inspector pane is where you will find the bookmarking options. If, like me, you want to add, say, chapter titles as entries in your TOC, then find that title in your text, select it, then hit the "+" to add it as a bookmark. Once you have bookmarked all your sections, then go back to the text in your TOC, select an entry, and hyperlink it to one of your bookmarks. Repeat. The manual TOC will be visible in your book, and clickable to your chapters/sections.
- Some formatting works, some doesn't. You might have to experiment here. I would stay away from anything too "non-standard", such as rules and borders. Margin padding seems to be okay, as does BOLD and ITALIC. Text size will also apply, but some readers reset this, so don't count on it.
- If you can set a font beyond sans-serif or serif, I haven't found a way to do it. Readers are probably going to reset this anyway. Think "web-fonts" available in standard HTML at best.
- You CAN include graphics, but they MUST be "inline" and NOT "floating". This is nice if you want to include some simple graphic ligatures to mark the end of a chapter or something.
Hope it helps… Good luck!

Similar Messages

  • HT4168 I have created an 100 page booklet in Pages, with many photographs, can I export it to ePub, and make an electronic book, because it says that "Note: The Pages document must have been created using a word processing template"?

    I have created an 100 page booklet in Pages, with many photographs, and much written word, can I export it to ePub, and make an electronic book, because it says that "Note: The Pages document must have been created using a word processing template"?....
    Basically what I want to do is publish the document into both an eDocument, and a hard copy document. What is the best way to do this?

    No Peter, this statement came right off the Apple ePub statement when outlining how to use ePub. the full context is:
    Creating ePub files with Pages
    Summary
    Learn how to create ePub files with Pages.
    Products Affected
    Pages '09
    ePub is an open ebook standard produced by the International Digital Publishing Forum. Pages ’09 lets you export your documents in ePub format for reading with iBooks on iPhone, iPad, or iPod touch.
    iBooks supports both ePub and PDF file formats, and you can export both from Pages.
    When to use ePub or PDF
    Use ePub when text is the most important part of your document, for example when you create a book, a report, a paper, a thesis, or classroom reading material.
    More details on using ePubUse PDF when layout is the most important part of your document, for example when you create a brochure, a flyer, or a manual with multiple illustrations.
    More details on using PDF
    Creating an ePub Document to Read in iBooks
    You can export any Pages word processing document to the ePub file format for reading in an ePub reader, such as the iBooks application on the iPad, iPhone, or iPod touch. Documents created in page layout templates can’t be exported to the ePub format.
    Documents exported to ePub format will look different than their Pages counterparts. If you want to get the best document fidelity between the Pages and ePub formats, style your Pages document with paragraph styles and other formatting attributes allowed in an ePub file. A sample document is provided on the Apple Support site that features styles and guidelines to help you create a Pages document that’s optimized for export to the ePub file format, which you can use as a template or a guide. To learn more about using paragraph styles in Pages, see the topics under the heading “Working with Styles” in the Pages built-in help.
    To read your ePub document in iBooks on your mobile device, you must transfer the ePub file that you create onto your device.
    To use the “ePub Best Practices” sample documentTo learn more about using the ePub format and get a better feel for how a Pages document might appear as a book in iBooks, it’s a good idea to download the “ePub Best Practices” sample document. After reading the guidelines and instructions within the document, you can use it as a template to create your own document. You can also import the styles from the sample document into a new document you create.
    Download the “ePub Best Practices” sample document at the following web address:
    http://images.apple.com/support/pages/docs/ePub_Best_Practices_EN.zip
    Do either of the following:Use the sample document as a template.Import the paragraph styles from the sample document into a new or existing Pages document.
    Export the document you create to ePub format to see how it looks in iBooks.
    Preparing an existing Pages document for export to ePub format
    Documents exported to the ePub format automatically appear with page breaks before every chapter. A table of contents is automatically generated, which allows readers to jump quickly to any chapter title, heading, or subheading in the book. In order to create a meaningful table of contents, it’s important to apply appropriate styles within your document. The ePub reader uses the paragraph styles to determine which items should appear in the table of contents for your book.
    Note: The Pages document must have been created using a word processing template.

  • Really having problems with organising documents in pages. For example, deleting pages deletes the whole section and I cannot insert a section break as its greyed out & sending an object to background deletes several pages - what the **** is going on???

    Really having problems with organising documents in pages. For example, deleting pages deletes the whole section and I cannot insert a section break as its greyed out & sending an object to background deletes several pages and trying to insert a text box autmatically creates new pages- what the **** is going on??? Is this programme really this badly thought out? I thought everything apple was supposed to be intuitive!?!?!? Help.

    You can not insert a section break into a textbox.
    You appear to have a lot of objects with wrap set, that once you take them out of the flow of text (by sending them to the background) causes the text to reflow and contract into fewer pages. Pages is almost unique in the way it forms up pages in Word Processing mode only so long as there is text on them.
    I suspect you probably have hammered away at returns, spaces and tabs as well to position things, which only works to add to the mess.
    Download the Pages09_UserGuide.pdf available under the Help menu and swot up a bit on how it works.
    You may find this a usueful resource as well:
    http://www.freeforum101.com/iworktipsntrick/
    Peter
    PS There is quite a lot of programming in OSX that is far from "intuitive". Pages is easy at one level, when using the templates, otherwise it can be quite frustrating.

  • When ever link any link on a web page many popups are opening. I don't get popups or adds when I use chrome or IE. Really frustrated with Firefox.

    Fire fox current version very frustrating and allows losts of ads and popups. When ever I click on any link from a web page ( any web page) i get a pop ups from ads like jabong, etc. I use the url of the same web page in chrome or IE I do not get such popups. It also crashes often.
    The only way to get rid of this is to get use to Chrome or some other browser.

    vksh89, What Extensions do you have installed as there are a few that can insert ad links on pages for example.
    Also if Firefox is your default browser something on computer may be targeting it.

  • 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!

  • Pages to epub...pfft...over!

    Working with Pages on iMac. Tried ePub--exported file to iTunes Books. Connected iPad. Everything OK, save Chapters. They are all connected, i.e., no breaks despite having cleanly placed Section Breaks at end of each Ch. How does one command each Ch to neatly begin on its own page? Tried Page Breaks, Section Breaks, multiple versions of each, but error continues. Even tried jumping up and down, climbing an apple tree and invoking an Ancient Swedish deity and zip! Anyone know? Thanks!

    I am having similar problems. I designed my ebook using the apple epub template and although 90% there I do have a variety of unsolved formatting issues.... I think, in answer to your question we have to remember that an ebook does not technically have pages... the way to streamline things is seemingly to ensure you follow the best practise template as best you can and used chapter headings to create new sections....(sort of)... I have evolved at least 20 versions and still not there... so I presume it is a matter of patience and playing around until the magic works.... my current issue is how to place picture captions 'alongside' or above or below some diagrams I have... I simply cannot get it to work. So may have to redesign and add the text to the diagram jpgs. I hope this might help.... 

  • Pages and formatting keeps breaking

    I continue to be frustrated with Pages because I spend a lot of my time managing the layout of my pages and sections as things continually break.
    I move a page within a document, and it breaks the formatting of other nearby pages. I insert a page break and it deletes a section below. I insert a page break and it ***** content to the next section. I try to break out a page into a new section and it inserts a blank page below that can not be removed.
    I am sure there may be reasons for some of this, but I have never had to sped so much time fixing and figuring out. Any recommends?

    Tracy,
    If you had Pages ’09 v4.3 before the Pages v5 upgrade downgrade, then it was moved into /Applications/iWork '09. If you want to return to productivity, you should export any Pages v5 documents back to Pages ’09 format, and then resume using the older application. It simply has 100+ features that were not implemented in Pages v5.
    LibreOffice is powerful, and with that power comes a new learning curve. They do have rather good documentation, too. Try Pages ’09 v4.3 if you have it, and I would recommend exporting each document to a MS Word .doc file, with consistent backups — as Apple future-proofing.

  • How do I "Print Booklet" with just odd pages and even pages for duplexing . . options disabled

    I have InDesign CS5.5 on a Windows 7 64-bit machine hooked to a Xerox 7750 printer.  I have created a 8.5x11 portrait document and trying to create a booklet on 12x18 sheets.
    I need to print duplex manually and so I need to print just the odd spreads and then the even spreads.
    I have printed to Adobe PDF and printed from my created PDF file and have it working, but I want to know why InDesign won't let me do it.  When I click "File > Print Booklet > Print Settings" then it shows the Print Dialog box with the Pages section, which includes the Sequence that normally would allow me to do Odd Pages or Even Pages, but it is disabled.  Why?  I can define Print Presets and I can choose Odd Pages, but when I choose that in the Preset box it does not show anything, everything is still disabled.
    Anybody have any idea of why it is disabled?  Is it my printer driver?

    I too was very frustrated after upgrading to indesign cs5.5 and the latest LION OS on my new MAC.  I missed the odd/even page selection in the print dialog box within Indesign.  I tried about everything and found little of value in various forums.  But I did find a workable solution that makes since in terms of Apple's OS.
    My objective is to "impose" my document and also end up with a file that I can just print again and again without "ripping" in the InDesign Print Booklet Dialog.
    Here is the quick version of what to do.  I am not including every little step with pictures. =)  (I can if there is interest.)
    1. create your document
    2. Print Booklet
    3. At the first dialog box, just ignore the printer in print preset (you will come back to this) and go to the 2-up perfect bound option and select 16 page signatures.  This will impose 2-up on 4 physical pieces of paper printed both sides.  So 16 of your document pages printed duplex on 4 physical sheets of paper.  It would be nice to then just select the printer and scaling, etc. and the option to print even pages, flip over and then print odd pages but that ain't an option.  If you have different needs, do the math and input the correct numbers before proceeding
    4. Click on Print Settings  to pull up a second dialog box.
    5. Select for Printer PostScript File (not your printer)  Also select for PPD your printer or Adobe PDF 9 if you have that installed.  Don't obsess on this just pick your Printer for the PPD.
    6. Select 1 copy and All Pages while in the General Tab
    7. Select the Setup Tab Here is where you put in the actual physical paper size that you are going to print your document on. Don't scale to fit.  You must do this.  If you feel the need, check out all the tabs and options but for now, you are just trying to get an output file.  You probably do want to select CENTER for page position in this same setup tab.
    8. Hit OK whcih will return you to the original dialog.  Check when you return to be sure that at the top Printer is populated with PostScript File.  Click on Print and give the thing a name and a location to save at the resulting dialog.
    Breathe as you are almost home.  You have sucessfully created a file that can be called up again and again without opening InDesign. (albeit, a postscript file but not a problem)
    Now,
    1. Double click on this new file (it will have a .ps extention) or just open it in your PREVIEW (apple supplied utility)   Preview is where you accomplish the even and odd page objective.
    2. Preview will show you a short progress dialog while it rips this postscript file into a PDF.
    3. Click on PRINT
    4. Select your printer,page range, select the Paper Size (again not document size  but  the size sheet that you are printing the 2-up , imposed (booklet) document on. If not in the selection dialog, then use the custom option to create it (custom paper size) and give it a name.
    5. Click on SCALE and insert 100% in place of the weird number that it will insert for you.  You will then see your document correctly displayed in the sidebar preview window.
    6.  OK, now what you have been waiting for. Click on the box that says Preview (the active window) and select Paper Handling from the drop-down and select from Pages to Print the coveted odd or even page selection.  You can also do other things that should have been back at the InDesign print dialog but are now gone.  Explore. Enjoy.
    7.  You will have to work out your own work flow about reverse or no reverse order and how to flip, etc. But you will be working with something predictable at this point.
    8.  Since this has been ripped into a PDF , you might as well Click on the PDF button and click on save as a PDF at this point to save that postscript to PDF rip.   Also print using PREVIEW for the newly created PDF file next time as you will not have to learn a bunch of new dialogs and be frustrated all over again.
    I am now back in business printing the book blocks for my handbound journals.

  • How can I have a Pages document that is shared with me under my Pages section and not open it with the link?

    How can I have a Pages document that is shared with me under my Pages section and not open it with the link?

    Try this.
    Open the document and select and copy a few pages, say ten pages.
    Open a new blank document and paste the pages you copied into that.
    Save it with a new name.
    Work on those new pages to see if the problem has disappeared.
    If this helps, continue breaking up the large file in to smaller chunks and working on them
    You can of course later reverse the process and merge the files into one new one.
    This suggestion is based on my experiences with large Word files. Breaking it up in to smaller chunks does two things. First, if there is any corruption in the old file, the new copies might escape that. Second, the Mac is faster handling the smaller chunks.

  • How do I adjust the page orientation in Pages?  I want to keep the pages above the section break as portrait, and the ones below I want to change into landscape.  Is this possible?  I can only get it to be one or the other but not both.

    I want to keep the pages above the section break as portrait, and the ones below I want to change into landscape.  Is this possible?  I can only get it to be one or the other but not both.

    The work around is to do two documents, one in portrait format and one in landscape format. When finished export to Pdf. open in Preview by select both files and use Cmd + O or doubleclick. You can now in Previews thumbnail column the pages from one document into the other and then save.
    If you have created only one with i.e. all pages in portrait format but with the content for the landscape pages rotated on the pages, you can rotate the pages in Preview. Two ways to get the same result.

  • 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.

  • 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!

  • Fixed layout ePub page turn not working in portrait mode

    Hello all,
    First time poster here. I created a childrens book, full color ePub from the Apple 3.1 ePub template. Everything sems to work great in general.  But I wanted the book to be in portrait mode only to get the most out of the graphics. I have the package.opf file set for portrait mode, which shows just one page (correctly), but when turning pages the cool page turn animation does not work when testing on my iPhone5 and an iPad2.  Pages just slide left or right.  But when I change the opf to allow landscape mode, when testing on iDevices, it shows two pages at a time in any mode and the page turn effect works perfectly.  Any way to get the page turn animation to work on just a single page in Portrait mode? To add to it I have an ePub example book from a non-Apple publisher that defaults to single page portrait, and is mostly text (so I'm not sure if its fixed layout or not), and the single page portrait mode allows the page turn animation to work perfectly.
    Thanks all!
    EDL

    The small caps are wrong in Source Sans Regular. This are not correct small caps . This seams to be missing in the font.
    But in italic style you will find correct small caps. They only work in InDesign not in ePub.
    And if you look in my images (first from InDesign, second from Radium - iBooks looks the same) you can see many difference between InDesign and ePub.
    Note the word "pfiffig", the I at the beginning of "Igor" in second paragraph and the "a" in the italic paragraph.
    This is very frustrating! 

  • Has anyone else had issues with hidden images in Pages?

    I wrote a 380-page book using Pages. The book has beautiful illustrations. My goal was to publish it on iBooks to take advantage of the clean interface. However, when I created the ePub version, got the book transferred to my iPad for testing (inside the iBooks software), all images were replaced with a white box. If I clicked twice on the box, the images did pop-up with an X on the left corner as the closing option.
    I did research and found out that the image files had to be of a certain size, and the dimensions also had limitations. So I deleted and replaced every image according to the recommended specifications. My Pages file doubled or tripled in size, and when I transferred to the iPad again, now the images were too small.
    I then thought to publish the book on Amazon first, maybe the image problem would be solved. Amazon took files directly from Microsoft Word, so I converted my Pages file to Word and on the Finder's preview would see these weird images. I knew something was wrong, but the Word file looked clean. When I submitted it to Amazon and opened in the Kindle Preview, there were all the images I had deleted!
    After much research, I found out that if you switch your Word file to Publishing Layout, the crazy duplicated images become visible. You can delete them from there and then switch back to the Print layout.
    Word is still not the perfect solution because it leaves weird borders on the images. That I have not figured out yet how to remove. Argh!
    My next step now is to open the Word document in Pages, now that the images are removed, to convert the Pages file into an eBook file, and publish it on iBooks.
    One should not have to go through so much trouble just to create an ePub file from Pages, right? Apple, if you are reading, can you please fix this bug soon?

    Tell Apple this http://www.apple.com/feedback/pages.html
    In the forum we are only end users like you.
    You also have a feed back option ín your Pages Pages menu.

  • 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.

Maybe you are looking for

  • BO/BW Report Level Calculation and Prompts

    Hi, There is an infoprovider in BI , delta enabled.Start Date and End Date are two fields in Infoprovider. The requirement is to have an Use Indicator Prompt having values Y or N. if the prompt input is Y , then display only those records where the c

  • What is the field and table name to describe -Employee Hourly Rate or Emplo

    Hi, Can any one please tell me what is the field and table name to describe  Employee Hourly Rate or Employee Rate. Thanks for ur time. Murali.

  • Error code -50 or system hand when copying

    Hi all I'm hoping someone can give me some extra info about an error code -50 / system hang that I keep experiencing. I've already done some research so I think I know where the problems might lie but not exactly how to solve them. OK, my iBook hard

  • Boot Camp Assistant: Can't Partition Drive

    I've been trying to partition my hard drive using the Boot Camp Assistant so I can install Windows XP. However, whenever I try to partition the drive, I get an error message saying that my hard drive needs to be a single Mac OS Extended (Journaled) v

  • Warning: language 'class' does not have locator

    Hi, While deploying an application on WLS8.1 SP2 we get the following error/warning - Warning: language 'class' does not have locator <Jan 20, 2004 12:52:00 PM GMT+05:30> <Warning> <WLW> <000000> <Warning: language 'class' does not have locator> Can