Changing "Chapter Name" font

Question

When making an ePub I can't create a new "Chapter Name" with a different font and still have it behave like a Chapter Name style i.e. inserting a page break. I don't want change the original style because it'll affect all Chapter Names. I wouldn't mind this if I could insert a page break but the Chapter Name is the only to do this. Any ideas?
Les

Answer 1

When I put my book in iBooks there is a white boarder around the cover.
Not sure if you are referring to a an "cover art image" problem or a "device display" problem here.
In the latter case, all hardware devices I own, as well as all of the ones I've looked at in stores, have had one common problem --that of dedicating some portion of the display area for the display of info, margins, and/or the "framing" of text and images. For this reason, it is not really possible "not" to have some sort of "border" around an image embedded on a "page" of an ePUB file when viewing the content on most such devices currently available on the market.
In the former case where a "cover art" image is used, a "white" border could be the result of image dropped/imported into iTunes. For instance, most Amazon cover art images are overlaid on a white 500x500 pixel background. Thus, when they are used are dropped/imported to iTunes as cover art, display with a "white" border on the black default background used by most Apple apps/devices such as iTunes, TV, iPad, etc. Borderless cover art images, of course, do not have this problem.
I can "Get Info", load in my cover in the cover art section and it will work fine there but I won't be able to do that when I put my book up for sale. Any ideas?
It is my understanding that dropping/importing a cover art image to iTunes merely "associates" the external image with the content within the iTunes database which then, in turn, passes the cover art images to other devices in an appropriate manner for display on the specifically supported device(s).
Basically, there are two methods of embedding "cover" images within the ePUB file. The first is to include the image on a "page" (usually the first) within your project. This method has the advantage of making/allowing the "cover" to be viewed as the first page of your book. In addition, most applications/devices automatically use this first image/page as a thumbnail icon for readers employing a graphic user interface. The major disadvantage, as you have noted, is that such "cover" art is invariably displayed with some sort of a border.
The second method is to embed an actual "cover" image within the ePUB file in the "Image Folder." The advantage here is that the image is usually of a reduced size requiring less space than a "full page" image. Again, most eReaders will recognize this "cover" file and use it for cover display and/or the graphic interface. The disadvantage, of course, is that this image cannot be viewed as a page of your ePUB book in the reader.
Different applications seem to use different approaches here. Pages, for instance, will, if you use the option during export, take the first page of your project--be it a "full cover page" in-line image in a marginless document, a "full cover page" floating object placed over a margined page, a text "Title" page, or a combination of images and text--remove it from your document, take a snapshot of the page, and place this "cover-image.png" in the ePUB package "OPS > images" folder. Thereafter, this image will be used in the same manner as cover art manually dropped/import to iTunes--i.e., it will display as a icon in the graphic interface and be used as the "cover" for the book in Books as the book opens on the iPad but is store within the ePUB package. On the other hand, since the the associated XHTML file content was deleted during ePUB compilation, it is no longer available for viewing as a regular page.
Legend Maker, on the other hand, goes in the opposite direction. Since you include a source "cover.png" image in your project to begin with, it creates a "cover.html" page in the ePUB package which displays (with the normal limitations) as the first page of your ePUB book and also places the original "cover.png" file in "OEBPS > images" folder which is available for "cover art" icon/graphic use in apps/devices that use them.
So basically, yes, there is a way for Pages to automatically embed the "cover art" functionality formerly manually applied by you in iTunes if this is what you want. Just remember that your "cover art" must entirely cover the Pages document page since this is what is used as the "canvas" for the automatically generated image. If it does not do so, then the image will include a "white" border for any background area(s) left exposed. This may require distorting or cropping the original art as desired/needed.