"I said, "don't encode the text in your ncx as
Isn't that what I said? Maybe I'm missing something
here, but I said that you said to also use ANSI in
Hitch is referring to the use of UTF-8 characters within the text items for NCX navPoints, rather than the encoding of the NCX file itself. I'm unaware of any up to date Kindle readers that still suffer from this problem, but I'd of course be interested to hear if there are examples where this is not the case.
When this was a problem something like this would break the NCX:
<navPoint id='partI' playOrder='1'><navLabel><text>Part I [b][u]— “[/u][/b]Beginning[b][u]”[/u][/b]</text></navLabel><content src='content.html#part1'/></navPoint>
While this would not:
<navPoint id='partI' playOrder='1'><navLabel><text>Part I [b][u]- "[/u][/b]Beginning[b][u]"[/u][/b]</text></navLabel><content src='content.html#part1'/></navPoint>
man2010, I've been following your instructions using MPC and have successfully produced an ebook which appears, at least in testing phase, to be formatted correctly, has the requisite cover, beginning and TOC. So I thank you for such clear and detailed work. I have an old copy of Word which did not have the correct export format, Web Page, Filtered. So using my limited HTML skills, I formatted the manuscript in HTML, then used MPC to add the Kindle specific functions. However, MPC is placing my TOC right after my cover, and I'd prefer it to follow the title page, copyright page, etc. Does MPC automatically place it there, and is there a way to change that position?
I apologize if this has been covered earlier in this thread. If it has, I missed it -- it's a long thread.
Mike, MobiPocket's TOC Wizard always places the table of contents at the very beginning of an ebook, right after the cover. You can code the TOC manually and place it where you want it inside your ebook.
You have two options:
1) Create the custom TOC in MobiPocket Creator
2) Create the new TOC manually by editing the OPF file, as described in the next post (I recommend this option, you have the necessary expertise). This is a modification of a protocol that I posted previously in this thread.
The MobiPocket option: Write the code of your TOC and place it after the title page and copyright section. Place a named anchor "toc" before this table of contents section. While your book project is open in MPC, delete the mbp_toc.html file from your book project and delete all code from the Table of Contents Wizard. Click "Update" and save your book project. After that you need to create a guide item for the new table of contents, as described below:
Click the "Guide" option on the lefthand panel. Create a new guide item with the title "Table of Contents" (without quotes), type should be "toc" (without quotes), and Filename text box should contain the name of the HTML file of your book plus "#toc" (without quotes) right after the file name, like this: book_file.html#toc
(you can click the "browse" button, select your book file and then type #toc at the end). Leave the "onclick" field empty. Click "Update". Now you can build your ebook in MPC or your can build it in KindleGen using your updated OPF file.
[i]1) “Building Your Book for Kindle” states that the outlined procedure will create a professional digital file. This is an exaggeration. There will be many formatting problems, some small, others big, if you use that manual. Granted it is possible to achieve tolerable formatting using only Microsoft Word, as described below. If you do not want to learn HTML and accept the possibility that your ebook will have some minor formatting problems, then read on. (On the other hand, quality formatting requires knowledge and editing of HTML code; see the first post in this thread.)[/i]
Ha! Boy, I just wrote basically the same thing in a prior post. Even good HTML WYSIWYG editors will output improper code here and there. Word processors, HTML editors, and desktop publishing software are all nice tools that make the job faster and easier, but you have to be able to spot the bad code they're bound to create now and then and fix it or you'll never have HTML or Epub files that will validate properly. They may work on some devices but will ultimately look bad on others.
The one that contains the phrase "couldn't delete this post". I posted new attachments there at first, but when a post is at the bottom of a long webpage, linking to that post is problematic. So i tried to delete it.
What's up with this link? I download, open the zip, and find a book about getting smarter by someone named Sevchuk. I know I have to get smarter, but I want to get smarter about the missing toc.ncx file.
Maybe someone can help Here's my problem: I upload my file to Kindle. I upload the converted file to my Kindle for PC. I can navigate to the cover and the beginning. The ToC is functional. So far, so good. Then the heartache begins.
I upload this same file to Kindle Enhanced Previewer, try to open the NCX view and get the error message that I don't have an NCX file. I should think if I didn't I couldn't navigate around the file, but I can.
I've attached a JPEG of the error message that come up.