![]() |
#1 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 185
Karma: 1004070
Join Date: Jul 2010
Location: Italy
Device: Kindle for Android, Google Play Books
|
Smashwords formatting issues with headings, TOC and images
To learn about self publishing and Smashwords formatting I have published a free book to Smashwords, which is already available at the site and is pending review by the vetting team. Although the converted ebook doesn't have any AutoVetter errors and is validated by epubcheck without errors or warnings, it still has some formatting issues. Since I don't have any error reports to start from, and this is my first Smashwords book, I'd appreciate any help and suggestions from experienced Smashwords authors on how to fix them.
I formatted the source manuscript with OpenOffice for Linux trying to follow the Smashwords style guide as closely as possible, and saved it to Microsoft Word 97/2000/XP format. I tested the ePub file converted by Meatgrinder with a Cybook Opus ereader, Aldiko Premium for Android, Lucidor and Calibre for Linux. I tested the Mobi format with a Kindle 3 ereader, Kindle for Android, and Calibre. I also checked the book with Smashwords' web viewer. The first major issue is that there is an unexpected page break between chapter "1. Background" and section "About Me". The section title is supposed to immediately follow the chapter title. They are on two separate consecutive paragraphs, formatted with the Heading 2 and Heading 3 styles respectively, and linked from the TOC. There are other similar instances of a chapter title followed by a section title and Meatgrinder converted them as I expected, i.e.: n. Chapter Title Section Title In the above mentioned case the outcome is instead: 1. Background [page break] About Me The issue is exhibited by all the ereaders and reading apps I checked the book with. What's the possible problem? The book includes both the NCX and the linked TOC. When accessing the NCX via the appropriate functionality, the linked TOC in the text is shown by all ereaders and apps except Aldiko, which displays the NCX using a different user interface. Is this the expected behavior? The same readers render the NCX and linked TOC of other books differently. The linked TOC works with all ereaders and apps except Lucidor and the web viewer, where clicking a linked TOC entry always leads to section "About Me" of chapter "1. Background". This may or may not be related to the above mentioned page break issue. On both the Kindle ereader and Kindle for Android app, chapter and section headings appear formatted differently depending on whether they are accessed by browsing the book page by page, or directly going to the headings via the TOC. Headings are formatted with the expected styles (e.g. Heading 2 or 3) if accessed by browsing, and with the Normal style and a slightly different color via the TOC. I attach Kindle for Android screenshots showing section heading "Legibility" when accessed via browsing (title-via-browsing.png) and via the TOC (title-via-toc.png). With OpenOffice I defined a DOC style for image captions based on the Normal style. The caption style uses centered italics text with indented left and right margins. I inserted the book illustrations as per the style guide, and added captions with the appropriate style immediately after the illustrations. The ereaders and apps show a bit too much blank space between images and captions. The OpenOffice screenshot image-and-caption.png shows how this looks like in the manuscript. Is there any way of making them closer? If I remove the centered paragraph separator just below the image, the image disappears. I originally tried to add the cover inside the book so that it also appeared in the PDF version. But Meatgrinder apparently didn't recognize it. The cover appeared twice in the ePub and Mobi versions. Aldiko overlapped text to one of the cover instances and duplicated other images later in the text with similar overlapping. So I was forced to remove the cover from inside the book. I originally tried to do as explained in the Smashwords FAQ (section "Should I add the cover image inside my book?"), but I was unable to find the OpenOffice functionality equivalent to "Layout" -> "In Line With Text" when right-clicking the image and selecting "Format Picture". The book text includes some em dashes I inserted from OpenOffice with "Insert" -> "Special characters...". They are correctly displayed by all ereaders and apps except the Opus, which renders them as question marks. I am aware of the preferred way of inserting dashes in Smashwords ebooks. I'm reasonably sure I inserted the character that way with the appropriate code, i.e. 2015. I can't be completely sure because the OpenOffice special character insertion dialog doesn't provide symbol names as Word does. These are the major formatting issues I found so far. Last edited by amoroso; 05-13-2012 at 12:30 PM. |
![]() |
![]() |
![]() |
#2 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,418
Karma: 35207650
Join Date: Jun 2011
Device: iPad
|
You could try using Open Office to create an RTF of your book, and then use Calbri to convert it to EPUB and see if the results are similar to what you are getting from Smash. IF they are then you can play around with your source file and see what what happens.
I write in MS Word, so do not know the open office interface well enough to make suggestions beyond. that. |
![]() |
![]() |
Advert | |
|
![]() |
#3 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 185
Karma: 1004070
Join Date: Jul 2010
Location: Italy
Device: Kindle for Android, Google Play Books
|
Thanks for the suggestion, I have tried this. The chapter and section headings are correctly kept together, but the linked TOC does not work. The RTF -> ePub conversion doesn't preserve images.
|
![]() |
![]() |
![]() |
#4 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,418
Karma: 35207650
Join Date: Jun 2011
Device: iPad
|
Quote:
MS Word file run through Open Office to make RTF, the RTF loaded in to Calbri to make EPub, etc. So the thought is that if you can get that to flow well then it should make it through their scripts. I know in MS Word I make the TOC work by marking my headings as "Heading 1" and that flows through to the EPUB and MOBI at Smashwords. I do not know what the equiv setting is in Open Office. |
|
![]() |
![]() |
![]() |
#5 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 185
Karma: 1004070
Join Date: Jul 2010
Location: Italy
Device: Kindle for Android, Google Play Books
|
|
![]() |
![]() |
Advert | |
|
![]() |
#6 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 185
Karma: 1004070
Join Date: Jul 2010
Location: Italy
Device: Kindle for Android, Google Play Books
|
I remade the linked TOC from scratch but nothing changed. In particular, the unexpected page break is still there.
Another formatting issue I found is that, regardless of the chosen paragraph separation method, i.e. first line indent or block, Kindle devices and apps always do first line indent. If, like in my case, the book uses the block method, Kindle does both: it separates paragraphs with extra vertical space and indents the first line of each paragraph. Finally, Aldiko shows the book title and subtitle using the Normal text style. I formatted the title and subtitle with custom styles based on Normal, but Aldiko apparently ignores them. |
![]() |
![]() |
![]() |
#7 |
Autism Spectrum Disorder
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,212
Karma: 6244877
Join Date: Sep 2011
Location: Coastal Texas
Device: Android Phone
|
I had an unexpected page break in my first work as well, and it didn't have a TOC. I'm not sure where it came from, only that it was there.
|
![]() |
![]() |
![]() |
#8 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 185
Karma: 1004070
Join Date: Jul 2010
Location: Italy
Device: Kindle for Android, Google Play Books
|
I did a few more tweaks but none of the issues was fixed. I guess my best option is to wait for feedback from the vetting team.
I look forward to the day, hopefully before the end of 2012, when Smashwords will let authors upload ePub and other formats. |
![]() |
![]() |
![]() |
#9 | |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 185
Karma: 1004070
Join Date: Jul 2010
Location: Italy
Device: Kindle for Android, Google Play Books
|
Quote:
Now I don't know whether and how to fix this. Meatgrinder is really frustrating. |
|
![]() |
![]() |
![]() |
#10 |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 185
Karma: 1004070
Join Date: Jul 2010
Location: Italy
Device: Kindle for Android, Google Play Books
|
The book was accepted in the Smashwords premium catalog without requests of changes or other feedback.
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Issue With Chapter Headings and TOC | yoss15 | Kindle Formats | 5 | 02-07-2012 01:54 PM |
Help with Smashwords formatting | Grannygamer | Writers' Corner | 19 | 08-21-2011 02:11 PM |
Managing HTML Link Behavior, From TOC to Chapter Headings | FlooseMan Dave | Calibre | 1 | 03-31-2010 11:55 PM |
Making a TOC for LRFs? Issues with Calibre + LRF TOC editor not working | Magitek | LRF | 0 | 05-06-2009 01:25 PM |