magnoliafaye
New Member
Posts: 7 
|
Post by magnoliafaye on Apr 22, 2013 16:02:35 GMT -8
I have tried and tried to get this thing straightened out and thought I had it at last. When I download the book as a PUB to Adobe, it works perfectly. It also works on my nook. Latest report from Smashwords follows: The links in your TOC are inoperable (all except, oddly, Chapter 16, which is working perfectly); please fix. See Step 20 in the Style Guide for help. ||| Some of these problems may not appear in your source .doc. Please view your EPUB by downloading a free copy of Adobe Digital Editions from here: www.adobe.com/products/digital-editions.html. When you're finished correcting your book, go to Dashboard: 'upload new version' to upload the new version. Thanks. Anyone have any ideas? Thanks |
|
|
|
Post by David Ellis on Apr 22, 2013 16:56:14 GMT -8
I have not uploaded anything yet. I will soon. I hope to see what has worked for others so I can learn more and help more later. I did read the style guide. Did you do all your writing in Microsoft Word? That sounds like the main potential issue when I read the style guide.
|
|
magnoliafaye
New Member
Posts: 7
|
Post by magnoliafaye on Apr 22, 2013 17:04:56 GMT -8
Yes, everything was done in Word. What I can't understand is why the TOC works for me in Adobe and my actual nook but not for them?
|
|
|
|
Post by David Ellis on Apr 22, 2013 17:10:59 GMT -8
There is an Amazon style guide for Kindle publishing that helped me with the table of contents more than anything else. I would check the settings on your headings. Check the style/format used on Chapter 16 and then make the others match. Format Painter might help.
|
|
|
|
Post by galatea on Apr 23, 2013 5:49:22 GMT -8
Is it just the epub they're complaining about? Did you run it through the epub validator: validator.idpf.org/ ? Did it return any errors? If it gave you an error, it might be handy to post the error here. It it doesn't give you an error and says the epub is ok though Smashwords says it's not, you might want to install Sigil. You can find the programm on code.google.com/p/sigil/ (left menu > featured > downloads). Once installed, open your epub. Then go to tools > check epub with Flightcrew The validate option of Sigil might tell you where the error is where the idpf validator does not (I know this from my own experience). |
|
magnoliafaye
New Member
Posts: 7
|
Post by magnoliafaye on Apr 23, 2013 10:28:18 GMT -8
Before I originally uploaded (successfully) the book to Amazon, I used Sigil. Just went back and checked file with Flightcrew and the other validator--No problems found! In Smashwords correspondence, they only reference epub. It is puzzling.
|
|
|
|
Post by Ted on Apr 23, 2013 17:32:45 GMT -8
Before I originally uploaded (successfully) the book to Amazon, I used Sigil. Just went back and checked file with Flightcrew and the other validator--No problems found! In Smashwords correspondence, they only reference epub. It is puzzling. If everything works fine in Sigil, and you have an epub file that works fine on your Nook, then upload that epub to Smashwords using Smashwords Direct. For more information on uploading epubs check the FAQ's on your Dashboard. If you still get an error message from Smashwords after uploading a verified and working epub file, send a Support ticket and explain the situation. Their epub direct upload is in beta and so you can expect a problem here and there, so just notify them of what you did prior to uploading. |
|
|
|
Post by galatea on Apr 23, 2013 23:10:45 GMT -8
I tend to generate my TOC's in Sigil itself nowadays.
It has an autmatic tool for that. Maybe that might help.
If your book happens to be free: I have an iPad on which I can check your TOC (if you want).
Just put the link to your Smashwords page here. Then I'll take a look.
But sometimes it's just the report in Smashwords that's wrong.
Once I got an error that my cover had white spaces, which wasn't the case. I just sent a ticket to Smashwords and they approved it manually. So I'm guessing not every error is actually an error.
|
|
magnoliafaye
New Member
Posts: 7
|
Post by magnoliafaye on Apr 25, 2013 12:17:15 GMT -8
Uploaded epub file and got the following message back from Smashwords:
"We have run EPUBcheck on your file, and it has passed!"
Sent it for review, came back with same error. Checked it on Adobe download site and it works. Cannot figure it out. I am taking a timeout. Thank all of you for your help.
|
|
|
|
Post by Ted on Apr 25, 2013 14:40:27 GMT -8
Uploaded epub file and got the following message back from Smashwords: "We have run EPUBcheck on your file, and it has passed!" Sent it for review, came back with same error. Checked it on Adobe download site and it works. Cannot figure it out. I am taking a timeout. Thank all of you for your help. AS I mentioned before, submit a Support ticket requesting your work be passed for the reasons you've given. I've had similar problems with Amazon KDP, and found explaining things to a human solved the problem. |
|
magnoliafaye
New Member
Posts: 7
|
Post by magnoliafaye on Apr 26, 2013 11:03:15 GMT -8
Decided to completely redo the toc from scratch as a last ditch effort before I completely gave up. Just got the news that it was approved for premium. I am beyond happy that I kept trying. I bet Smashwords can't believe how many times I uploaded new copies to their site. Thanks once again to all of you who took the time to help me.
|
|
|
|
Post by Ted on Apr 26, 2013 11:50:52 GMT -8
Decided to completely redo the toc from scratch as a last ditch effort before I completely gave up. Just got the news that it was approved for premium. I am beyond happy that I kept trying. I bet Smashwords can't believe how many times I uploaded new copies to their site. Thanks once again to all of you who took the time to help me. Any idea why making your TOC from scratch got rid of the problems? Do you think it might be some weird MS invisible coding causing problems? |
|
magnoliafaye
New Member
Posts: 7
|
Post by magnoliafaye on Apr 26, 2013 12:28:51 GMT -8
I think I had "messed with it" so much that I might have added all kinds of extra coding that caused the problem. I thought it would be a breeze since it passed with Barnes/Noble with no problem. Also am wondering if somehow my computer wasn't changing the original file when I tried to make
corrections for hyperlinks? It is still puzzling to me. But, now I am happy, happy, happy. (Phil--Duck Dynasty)
|
|
|
|
Post by Ted on Apr 26, 2013 18:14:20 GMT -8
I think I had "messed with it" so much that I might have added all kinds of extra coding that caused the problem. I thought it would be a breeze since it passed with Barnes/Noble with no problem. Also am wondering if somehow my computer wasn't changing the original file when I tried to make corrections for hyperlinks? It is still puzzling to me. But, now I am happy, happy, happy. (Phil--Duck Dynasty) Sometimes I will take a troublesome MSWord doc and make a copy of that, then open that copy in LibreOffice (or OpenOffice, whichever you prefer), check for errors, correct any errors, then save the file as a .doc file with a new name to distinguish it from the original. Then I'll upload that LO to .doc version and see if it passes. MSWord has done weird stuff to me in the past. I'm using Scrivener now and will upload an ePub instead of a .doc file from now on. |
|
|
|
Post by David Ellis on Apr 26, 2013 19:41:41 GMT -8
Very nice to hear.
|
|
