Quote:
Originally Posted by tomsem
I didn't know there was a workaround, but presumably that is gone now. It was only ever intended as a side load format, which is all the more reason it's kind of insulting for SB to provide these instead of making sure their ePubs convert without issues (which is a straightforward task). People that want to side load can do their own conversion with calibre (either to AZW3 or KFX).
Instead they say 'complain to Amazon'.
|
Does Standard Ebooks run the Send to Kindle service? Should they be responsible for any of the glitches that Send to Kindle can and has caused?
And could you please translate your "
It was only ever intended as a side load format, which is all the more reason it's kind of insulting for SB to provide these instead of
making sure their ePubs convert without issues" into something humanly understandable? Standard Ebooks offers .azw3 to sideload to your Kindle which you specifically state is that format's only intended purpose and then complain that Standard Ebooks should be responsible for making sure their ePubs (also downloaded for sideloading) are not going to be munged by Send to Kindle. Pull one of the other ones, bucko! It's got bells!
Perhaps you should look at the CSS generated by Vellum in it's attempt to cover all the multitudinous variations of mobi and KF8/azw3 that Amazon Desktop Publishing can spit out? A CSS stylesheet with 800+ lines of media queries which is close to double the number of lines in the main stylesheet trying to compensate for the limitations of Amazon's ebook formats.