Quote:
Originally Posted by DiapDealer
But it doesn't directly edit the markup in an azw3. Sure, it's not doing full-blown conversion, but the raw markup in a binary azw3 file is not standard (x)HTML. There are no filenames, for instance, and the links are offsets, and there's proprietary elements/attributes. Those file names you see in the editor are invented by calibre when it extracts the raw markup and massages the proprietary portions into something that can be easily edited by the user. Then it compiles that back into the kindlebook's proprietary binary database format. You are very much editing an intermediate format.
|
Y'know...
When I think about this--and I really don't want to make this about Calibre--I feel as though using a simple ePUB for this purpose is less of an "intermediate" method than using Calibre, for the reasons amply elaborated upon by Diap. What's "intermediate" about an ePUB, all in all? If I make a mobi, and then crack it open, by using an ePUB-->KP or KG, at least what I see when I crank that sucker open is recognizable by me. No weird flattened CSS, (
per se) etc. It's the book as I made it--with some "help" from Amazon, of course.
Just sayin'.
Hitch