Quote:
Originally Posted by volwrath
Yea they all sync up fine. The point was that the older firmware showed locations of 1214-1216. Newer K3 format appears to have abandoned the location range for a single value , and if you hold your head right newer k3s MAY show pages as well as location.
|
Ah, gotcha. Yeah, I'm not happy with the fact that I have to press the menu button to see the location info, but that's a software issue rather than a spec issue. The only thing that shows full-time is the percentage bar. I'd prefer a configurable display option, and I hope that will someday come to fruition.
Quote:
Originally Posted by volwrath
Mobipocket created the format in 2000 and the format has aged relatively well but I think its time for amazon to embrace xml and make publishing mobi content easier. I think the title of the thread was harsher than I intended though.
|
I agree that advances/improvements can be made (although "improvement" can be subjective, as the page count issue illustrates beautifully). I find it hard to believe that they don't have people currently working on updating the spec, but I would be happier if they worked on making it easier for the current spec to be properly implemented by others. When mobi files processed with Amazon's OWN SOFTWARE come out looking like crap, there's more of a problem than just an XML deficiency.
Haha, my pet peeves are showing.
I just know, in my heart of hearts, that even if Amazon made mobi the most amazing format on earth, many publishers and indie self-pubs would still do a crappy job of making their ebooks. I look at the amazing files that MR users upload to the library here, proving that with time and care, amazing ebooks can come out of the mobi format.
Amazon can start by helping Smashwords fix their Meatgrinder. There have been times I've downloaded nearly every available format for a book, trying to find the one that's the least mangled.
I don't know if I added anything to this discussion, but I sure do feel better now that I got that out of my system.