View Single Post
Old 02-18-2013, 04:31 PM   #6
Kolenka
<Insert Wit Here>
Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.Kolenka ought to be getting tired of karma fortunes by now.
 
Kolenka's Avatar
 
Posts: 1,017
Karma: 1275899
Join Date: Jan 2008
Location: Puget Sound
Device: Kindle Oasis, Kobo Forma
Quote:
Originally Posted by Popup View Post
Yes, that seems to be the case. Although I don't think that it's a KF8 book. File claims that the .azw3 file is 'mobipocket'.

I've left 1-star reviews and hope that the issue will be fixed. Hopefully this will be rectified in a future update.
All Kindle formats use Mobipocket files as the container. AZW3 is KF8 + MOBI in the same file (although one or the other can be stripped out if desired). KF8 is built using ePub as the base, but by using the Mobipocket file container, it makes backwards compatibility possible.

However, with ePub (and thus KF8), the spec pretty much allows poor publishing like what you ran up against, because of how much CSS is supported. An eBook author can set the font used in the CSS or HTML and it will usually wind up overriding whatever the device tries to set as the font and size.

This is definitely a problem with HTML content spat out by a generator, like say, Microsoft Word's HTML output. HTML generators in word processors tend to do stupid things with CSS that results in files like this.
Kolenka is offline   Reply With Quote