View Single Post
Old 09-30-2013, 12:26 PM   #2
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 27,478
Karma: 192992430
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Do you mean 'invisible'?

Regardless, you don't put html files in the spine at all. You put 'itemrefs' in the spine... that correspond to the ids of the html 'items' in the manifest.

If you don't want those items to appear in the normal flow (as dictated by the spine) of the ebook, then your only recourse is to add the 'linear="no"' attribute to the itemref in the spine. But support for it is quite spotty in all the most popular readers and apps. It won't work in most ADE-based environments (that I know of).

I'm not sure if "popups" of any kind are going to work on any epub reader that doesn't support at least some of the epub3 spec (like iBooks). Once again, this is going to leave out most of the current crop of ADE-based readers and apps.

Last edited by DiapDealer; 09-30-2013 at 12:31 PM.
DiapDealer is offline   Reply With Quote