View Single Post
Old 07-23-2011, 09:02 AM   #1
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,583
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
EXTH 116 when converting to MOBI

Perhaps I've missed it—or not done enough experimenting—but, how exactly (if at all), is the EXTH record type 116 being created when converting documents to MOBI? And is it configurable by providing certain criteria in the source document?

I'm thinking specifically of ePub->MOBI. Kindlegen uses certain reference items (if they exist) from the guide section of the OPF file to create that "startreading" EXTH 116 record. The href in that reference item is converted to the position (4-byte offset) in the resulting mobi at which to open when first opened. The "text" ePub semantic (assignable in Sigil) is used by Kindlegen for this purpose. I believe it will use a "start" reference type as well.
Code:
<reference type="text" title="Text" href="Text/EditorsPreface.xhtml#startanchor"/>
So far, nothing I can do to the source document will make calibre create (or populate) that EXTH 116 record. Is there any way to make this happen currently, that I've missed? Or can there be a way in the future?
DiapDealer is online now   Reply With Quote