View Single Post
Old 09-23-2012, 01:06 PM   #6
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: 8,774
Karma: 39540023
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Until Amazon fixes this I don't believe it is possible to find a reliable solution which works with all devices.
You mean using anchors, right?

As long as the href for the "text (or start)/toc" reference items in the OPF's guide section points directly to an (x)html file (with no url fragments involved), all my ebooks' Start Points behave exactly the same in the Kindle Previewer as they do on a KF8-capable Kindle Keyboard device.

I can, however, reproduce your exact issue (on the Kindle Keyboard) by introducing anchors and url fragments into the mix. So it seems to me that the "fix" is a bit obvious. But perhaps I'm not fully understanding.
DiapDealer is online now   Reply With Quote