View Single Post
Old 03-09-2012, 11:33 AM   #5
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: 28,691
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
If you were able to open a MOBI with springy and alter the html inside... that was only the original source (x)html you were editing and not the MOBI itself. MOBIs have to be "rebuilt" each time from the modified source. There is no way (currently) to edit a MOBI (like you can edit the contents of an ePub).

I would guess your friend's MOBI (that you could open with Springy) was built with kindlegen. That's why you could access the source. Your MOBI (which you can't open with Springy) was built with the ID plugin and doesn't have the source package included.

When you upload a MOBI that includes the source to Amazon, that source is stripped out before it gets delivered to anyone.

Last edited by DiapDealer; 03-09-2012 at 11:36 AM.
DiapDealer is offline   Reply With Quote