The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex
As Ranhiru said, here and here you can see how PDFs are parsed.
ReplyDeleteFor .mobi, however, there is no library, so you'll have to parse the format yourself. A full specification of the format can be read on the mobileread wiki.
With .azw files, it's different: if the Kindle ebook is DRM-free, then its format coincides with the .mobi one, i.e. they are absolutely interchangeable. Otherwise, it's very difficult to do, since you'll also have to generate a Kindle PID and perform the de-DRM-ing of the .azw file. There's a guide on how to do that on the desktop here. However, it is strongly not recommended, since it breaks the whole point of DRM and is illegal pretty much everywhere.