Kindle Paperwhite 2-Voyage Software Update 5.6.5

[Rizla]

Originally Posted by eschwartz

It is rather early to be pontificating about the redundancy of KFX, when for all we know it may do more than enable new typography.
And as already mentioned, processing the rendering information ahead of time on Amazon's servers in order to ease the load on the devices themselves, cannot be a bad thing, although one might debate how much value it actually brings.

It's not "pontificating," it's discussion and speculation.

It is unreasonable to compare the upgrade from MOBI to AZW3 to the upgrade from AZW3 to KFX. MOBI was an old and very limited format, whereas AZW3 can support all the features of EPUB, which can support the "new" typographical features introduced in this software update.

As such, one can only assume that Amazon's intention in introducing the new format must include other plans. It will be interesting to see what Amazon intends for its new file format. We already know that it includes encoding.

[HarryT]

Originally Posted by Rizla

As such, one can only assume that Amazon's intention in introducing the new format must include other plans. It will be interesting to see what Amazon intends for its new file format. We already know that it includes encoding.

It also provides the capability of delivering device-specific image resolutions, which the KF8 format does not. That is, I suspect, the main reason for its introduction: so that images can be optimised for the specific device that the book is being sent to.

[tomsem]

Originally Posted by HarryT

This is true, but there are an awful lot of ePub devices out there - almost certainly the majority of them, in fact - that have older versions of the RMSDK that don't support RTL.

That's unfortunate, but not a problem if one is reading on a smartphone or tablet. Reading apps are a lot easier to update than dedicated devices, which by design have limited performance and hardware resources.

[HarryT]

Originally Posted by tomsem

That's unfortunate, but not a problem if one is reading on a smartphone or tablet. Reading apps are a lot easier to update than dedicated devices, which by design have limited performance and hardware resources.

Very true. It is, however, a problem for those selling books.

[cvkemp]

Originally Posted by tomsem

That's unfortunate, but not a problem if one is reading on a smartphone or tablet. Reading apps are a lot easier to update than dedicated devices, which by design have limited performance and hardware resources.

I can no longer read on a tablet smartphone or even a computer screen for any time at all. My eyes just will not allow me to do so. But I can read on e-ink for hours as long as a take a short break every hour.

[HarryT]

Originally Posted by cvkemp

I can no longer read on a tablet smartphone or even a computer screen for any time at all. My eyes just will not allow me to do so. But I can read on e-ink for hours as long as a take a short break every hour.

You can of course run generic reading apps on devices with eInk screens, should that be your preference. There are a number of general-purpose Android tablets with eInk screens on the market.

[cvkemp]

I love my voyage and I know how to convert the formats as needed so I can read on my voyage.

[eschwartz]

Originally Posted by Rizla

It's not "pontificating," it's discussion and speculation.

You were and still are declaring, not speculating. There is a rather large difference.

[Rizla]

Originally Posted by eschwartz

You were and still are declaring, not speculating. There is a rather large difference.

No I'm not.

[Rizla]

Originally Posted by HarryT

It also provides the capability of delivering device-specific image resolutions, which the KF8 format does not. That is, I suspect, the main reason for its introduction: so that images can be optimised for the specific device that the book is being sent to.

It sounds like a reason, but it's a jump to think its the "main" reason.

[DuckieTigger]

Originally Posted by Rizla

It sounds like a reason, but it's a jump to think its the "main" reason.

It is a pretty good main reason right now. There has been problems with small maps and such when the Voyage was new due to resolution, if I remember right. So until Amazon comes out with some new feature it doesn't have to reveal exactly what all the kfx format is capable of. So instead of frankensteining an old format to add device specific images, they simply made a new format that is doing it naturally.

There probably is more to the advanced typesetting engine as well once publishers have access to a tool to create the books themselves. Right now the advanced typesetting is added by Amazon to some books and not others without opting in or out from the publishers side. At least that is true for indies, especially in one case where I talked to the author/publisher (self-pubed) where the first 3 books in a series didn't get the advanced typesetting, but the 4th one did.

[cerem0ny]

I hope the Android app gets updated soon. I love reading on my Galaxy Tab now but I do miss the... erm... 'quietness' of my Voyage. No eye strain whatsoever - no idea what any of you guys are talking about... maybe you've got the brightness set too high? I've grown up staring at screens for hours so maybe I'm just well adjusted....

[cvkemp]

Now that I have my voyage I do not read on anything else. I love that I can read on the voyage for hours and not be bothered by email, and facebook or anything else. I also enjoy the e-ink screen. After about 10 mins of reading on a computer, or tablet my eyes are killing me. And I do set the background light as low as possible.

[eschwartz]

Originally Posted by Rizla

No I'm not.

Originally Posted by Rizla

It sounds like a reason, but it's a jump to think its the "main" reason.

It is ALSO a jump to think it is not the "main" reason.

You know what, just imagine I have transcluded my previous posts in this sub-conversation.

I'm not going to go in circles with you any more.

[ATimson]

Originally Posted by tomsem

You can also use Report Content Error feature on the Kindle itself. It's probably good to do both, as they probably get different people looking at the reports. RCE is recorded at your kindle.amazon.com page and you can track status there.

That's what it says when you report stuff but I've never been able to find that info online. Can you give me directions on where I can find the RCE info?