Quote:
Originally Posted by eschwartz
They don't expect people to look at <gasp> files and other weird things.
Usually they are right.  |
my final try at a sum up- as this could turn into one of those "how many angels fit on a pin" debates.
OP, or whoever, begins with epub. converts to mobi(both) - so in the output file there's a quasi azw format code with all his mark up intact , and an old mobi code with some features stripped out.
sends the file to amazon who ignore the new improved azw code and accept only the old downgraded mobo code
amazon then either label that as azw and send it OR ( this is the only unclear bit? ) convert that old code to "new style" azw code. & then send it. ( but that's like trying to convert a lo-fi mp3 back to wav, you can't replace what you don't know is missing )
so what gets sent to device has less markup etc, then would be there if file had been sent as azw or as mobi new by usb.
e.g. if the epub had left & right margins, embedded fonts and an indent of 1.5 em, what arrives on device with have indent rounded up, or down, and less margins.
converting to azw & sending via other routes: USB, dropbox, calibre server, is less lossy.