Quote:
Originally Posted by pdurrant
I've never tried uploading through Mobipocket. I can only guess that they are insisting on people using their DRM (urgh). IMO DRM only troubles the people who are actually willing to pay for your books. Whether there's a way to publish through Mobipocket without using DRM I don't know.
The no text encoding sounds easy - your source files haven't specified what text encoding they use, and you have specified explicitly in the appropriate field in the Mobipocket Creator program either. Do one or the other (i.e. specify whether the text source is in Windows Latin-1, Mac Roman or UTF-8)
The table of contents error sounds like you're specified your own table of contents, but that one of the links in it is broken in some way.
For Mobipocket, I've found the best way to do a table of contents is to get my source text into basic HTML, with the sections/chapters marked up with header (H1,H2,...etc) and then get Mobipocket Creator to create the TOC for me. I can always then tweka the html in the new table of contents file, but I can be sure the links are all correct.
|
Hi! Apparently Mobi won't take a file from a publisher unless it has the DRM. This was handled by using the mobigen.exe tool and specifying -s2 in the command prompt. The file then opens in the Mobi Creator and formats with the encryption.
Thanks for the tip on the encoding. My error was not specifying in the Mobi Creator--> Book setting the correct encoding. It defaulted to Western and the files were International UTF8, so by changing this in the setting, it handled the error.
On the TOC, this took some trial and error, but I finally hit on a simple handling as I wanted to use the TOC already formatted and linked in the epub file. The epub file uses an .ncx file for the navigational map and to create the TOC. Mobi doesn't recognize .ncx, so by changing the toc.ncx to toc.xhtml to match the other files, it handled the bug and built the files.
Lucy