View Single Post
Old 03-07-2017, 09:57 AM   #25
Doitsu
Grand Sorcerer
Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.Doitsu ought to be getting tired of karma fortunes by now.
 
Doitsu's Avatar
 
Posts: 5,731
Karma: 24031401
Join Date: Dec 2010
Device: Kindle PW2
Quote:
Originally Posted by ibu View Post
Then I zipped everything with the app: it validates with http://www.pagina-online.de/software/epub-checker/
BTW, this software use the same validator as the epubcheck plugin.

Quote:
Originally Posted by ibu View Post
But when I open the EPUB in Sigil, it automatically adds a NCX. Is there any way to prevent that in Sigil?
No. You'll have to use Calibre Editor for final edits. Make sure to install the Calibre epubcheck plugin and run it before and after your edits. However, Calibre might add its own set of custom metadata entries, unless you disable the following option:

Edit > Preferences > Integration with Calibre > Update metadata ...

Quote:
Originally Posted by ibu View Post
Ditto for the entry about the Sigil version in the meta element.
You can't suppress this metadata entry, which is useful when tracking down version specific bugs.

Quote:
Originally Posted by ibu View Post
I hope there will be a solution for Sigil to keep it prevent that automatically generated NCX.
KevinH has indicated that future versions might have an option to suppress the automatic generation of NCX files, however, you might want to keep the NCX file for backwards compatibility with epub2 apps.

Quote:
Originally Posted by ibu View Post
Are there strong reasons against the idea to place the complete content into one single file (title, content, about, imprint)? Will that cause problems in a Kobo? I think of inserting automatical page breaks in front of specific headings via CSS. Than there's no need at all for separated files for the content.
If you use separate files, they'll usually load faster. Also some older epub apps have problems with files larger than 300-400KB.
As for Kobo-specific questions, you'll have to ask them in the Kobo forum.
Doitsu is offline   Reply With Quote