Quote:
Originally Posted by dhdurgee
K3W = Kindle 3 Keyboard - WiFi model - S/N: B008 xxxx
KT2 = Kindle Touch 2(Basic - 7th generation) - S/N: 90C6 06xx
Dave
|
Just say K3 and stop confusing people.
Quote:
Originally Posted by notimp
edit2: As for the larger azw3 files. Amazon promoted .azw3 as a container for both .mobi and .kf8 for its entire format life. When you think of .azw3 the way current Kindles see them, you are actually thinking of .kf8 in the .azw3 wrapper. .azw3 mostly becomes that much "bigger", because there are both the .mobi and the .kf8 version of a book embedded in one .azw3 file.
Amazon used it as a transition technology (to get away from .mobi and .prc which had a legacy of being "rather open").
Calibre has an option to only package the .kf8 file in there (actually it is its default .azw3 setting for some time now), which almost halfs its filesize.
|
Um, not really?
Amazon always delivers split *.azw (MOBI) or *.azw3 (AZW3).
kindlegen generates dual-MOBI (has both) and names it *.mobi
So, no.
*.azw3 has never ever been a container for mobi7.
And they have never used *.kf8 as a file extension.
AZW3 is legitimately somewhat bigger than MOBI on average.
It makes up for it by properly supporting CSS, by supporting separate files internally, by supporting properly defined covers... Just try cracking one open in calibre's Editor.
I like being able to update the cover without doing a MOBI-to-MOBI conversion.
ToC support is also better.
Basically, AZW3 is more polished than MOBI. It is feature-comparable to EPUB.
MOBI predated EPUB altogether, and in many ways is just an ancient, lousy format.
I will agree that KFX has not brought anything new to the table.
Quote:
Originally Posted by notimp
Name the features you are talking about that get lost in your opinion. .azw3 (.kf8) has brought less new stuff to the "playing field" than you might expect.
And as .css formating conventions go - it was mostly hit and miss anyhow. You can argue, that once people accepted azw3 as the new default, they optimized their .css sheets for it - but thats all minor stuff in comparison (think floating text around objects, marginally better alignment options for some objects, stuff like that).
But lets not draw this out beyond its purpose here... Look at both, decide for yourself. The usage with JBPatch is a fringe case anyhow. (And in the end you almost always want hyphenation - so...)
For me its more about the story behind it (azw3 (kf8) by no means was that much better "featurewise" - it mostly served another purpose... ).
If the ePub 3.0 featureset became more widely used, the story might have been different. |
Yes, that enhanced CSS support is put to good use, as mentioned above. Just because you don't think CSSis useful, doesn't mean everyone else agrees.
MOBI was dramatically behind EPUB on that front, and AZW3 caught up.