Copying books to Kindle

[jackm8]

Different tastes, I guess. I couldn't stand AZW3 simply because of its horrible paragraph spacing. The thing is, bad paragraph spacing in AZW3 can't be fixed. Line spacing, on other hand, can be in both formats. We got new spacing settings in latest patch, and it can be fixed by using modified fonts.

[cellaris]

Originally Posted by Sirtel

In short, KFX being superior or inferior is pretty subjective and depends on your preferences. For me it was inferior, YMMV.

I agree. Personally, I have no problem with either format. I had always used AZW3 until Amazon switched to KFX for converting books sent via Send to Kindle. For a while, I sent the same book as both AZW3 and KFX. Eventually, I realised that I always read the one in KFX format. I like wide line spacing, and I find the distance between words and hyphenation perfect without needing to tweak anything, as well as the font recognition. In the end, I found KFX much more comfortable to use than AZW3. But it's a matter of personal preference. I could also use AZW3 without any major problems, but personally it doesn't offer me anything special and, moreover, it makes it impossible for me to synchronise between devices. In any case, the important thing is that everyone uses the format they feel most comfortable reading with.

[DNSB]

Originally Posted by jackm8

You're constantly changing the topic. At first you were talking how KFX forces styles on you, now you're defending Kobo comparisons that have nothing to do with the topic discussed.

I am not changing the topic. I am saying that most of what Amazon claims to be "enhanced typesetting" has been available on other devices for decades. It's like reading a claim that a new TV has enhanced audio since it now support a TOS optical connection.

Originally Posted by jackm8

On Kindle, we've the choice between AZW3 and KFX, and KFX in most cases works the best, even compared to EPUB, if it's running in KoReader. That's a plain fact, as far as I'm concerned. I see nothing that would disprove it. Maybe KFX is worse than other formats on other readers, I'm not judging that. But if you think that it is, I'd really like to see some proofs of that, not just pointless talk.

Simple items such as forcing a minimum 1.2 line height. On my ePub readers, I don't set a line height allowing the user to set the line height using the ereader controls if they don't like the default. Other such as the kerning, ligatures, etc.? Again available elsewhere for decades. With the download speeds currently available using either WiFi or cellular connections, the ability to start reading before the full book has downloaded is not all that useful (again all IMNSHO).

As for KOReader? For the most part, it's a pretty decent renderer but does not handle many ePub3 options such as initial letter. Since I edit most ebooks before reading them—most new ePubs have decent enough formatting making editing a pretty trivial task—I no longer find KOReader of much use.

If you are happy with KFX, I have no issues with that. Just please try to realize that Amazon's Enhanced Typesetting does not seem to offer any typesetting features that have not been available elsewhere for years if not decades.

[Sirtel]

Originally Posted by jackm8

Different tastes, I guess. I couldn't stand AZW3 simply because of its horrible paragraph spacing. The thing is, bad paragraph spacing in AZW3 can't be fixed. Line spacing, on other hand, can be in both formats. We got new spacing settings in latest patch, and it can be fixed by using modified fonts.

What horrible paragraph spacing? The only possible paragraph spacing for me personally is no paragraph spacing, that is, no spaces between paragraphs. I fix all my ebooks to not have them. YMMV, as always.

[jackm8]

Originally Posted by Sirtel

What horrible paragraph spacing? The only possible paragraph spacing for me personally is no paragraph spacing, that is, no spaces between paragraphs. I fix all my ebooks to not have them. YMMV, as always.

I meant word spacing. AZW3 doesn't support hyphenation, so there's really no solution for justified text.

Originally Posted by DNSB

I am not changing the topic. I am saying that most of what Amazon claims to be "enhanced typesetting" has been available on other devices for decades. It's like reading a claim that a new TV has enhanced audio since it now support a TOS optical connection.



Simple items such as forcing a minimum 1.2 line height. On my ePub readers, I don't set a line height allowing the user to set the line height using the ereader controls if they don't like the default. Other such as the kerning, ligatures, etc.? Again available elsewhere for decades. With the download speeds currently available using either WiFi or cellular connections, the ability to start reading before the full book has downloaded is not all that useful (again all IMNSHO).

As for KOReader? For the most part, it's a pretty decent renderer but does not handle many ePub3 options such as initial letter. Since I edit most ebooks before reading them—most new ePubs have decent enough formatting making editing a pretty trivial task—I no longer find KOReader of much use.

If you are happy with KFX, I have no issues with that. Just please try to realize that Amazon's Enhanced Typesetting does not seem to offer any typesetting features that have not been available elsewhere for years if not decades.

You're again not providing anything that would substantiate your words. You're saying that it's all available elsewhere, but it's apparently not available in KOReader, it's certainly not available in AZW3. Where and on which devices is it? For myself, I can also confirm that KFX is more advanced compared to EPUB3 on Pocketbook. So where can I see what you're saying in action? It really shouldn't be that hard to take a screenshot from your devices, right? I've provided you with epub. Fonts that I used are open source. Just put the epub on your device, and take a screenshot on the same pages that I did.

And, yes you are changing your words, you went from KFX forcing the look of the books, which I'm glad to say, has been overruled, to KFX providing nothing new. In a few more posts, you'll start admitting that it offers features not present elsewhere.

ps.
Here's same epub on my Pocketbook InkPad in its native reader. That should be one of the devices that fits "Amazon's Enhanced Typesetting does not seem to offer any typesetting features that have not been available elsewhere for years if not decades."
Ligatures work. But it again does nothing to image sizes. So they're too small in this case as well. And I can't enlarge them, either. I also didn't get the justification to work. It may be possible, but it would require tinkering with the file. Still, with KFX it all works out of the box without any fuss at all. And I think that's the biggest benefit of it. In combination with native Kindle reader, it provides simple experience that works really well in most cases. I've pretty much moved completely to epub and KOReader on my Kindle, but denying KFX's benefits, or downplaying them, is a bit silly. It's a good format.

[DNSB]

Originally Posted by jackm8

You're again not providing anything that would substantiate your words. You're saying that it's all available elsewhere, but it's apparently not available in KOReader, it's certainly not available in AZW3. Where and on which devices is it? For myself, I can also confirm that KFX is more advanced compared to EPUB3 on Pocketbook. So where can I see what you're saying in action? It really shouldn't be that hard to take a screenshot from your devices, right? I've provided you with epub. Fonts that I used are open source. Just put the epub on your device, and take a screenshot on the same pages that I did.

And as I pointed out, KOReader is not all that great for it's ePub3 support. As for using your piece of crap epub? Perhaps you should have looked at the copy of Three Men in a Boat in MobileRead's library. I used that as the basis for my version.

Originally Posted by jackm8

And, yes you are changing your words, you went from KFX forcing the look of the books, which I'm glad to say, has been overruled, to KFX providing nothing new. In a few more posts, you'll start admitting that it offers features not present elsewhere.

Sorry but I have not changed my words. I keep pointing out features that Amazon claims for KFX that have been available elsewhere for over a decade. As for forcing the look of books? KFX forces a minimum line height of 1.2. KFX still forces Amazon's overly wide left/right margins. KFX does strange things with treating a non-breaking space as if it was breakable. And if you have never had the joy of having a two column justified landscape mode suddenly drop to a ragged right single column, you are a lucky soul.

Originally Posted by jackm8

Here's same epub on my Pocketbook InkPad in its native reader. That should be one of the devices that fits "Amazon's Enhanced Typesetting does not seem to offer any typesetting features that have not been available elsewhere for years if not decades."
Ligatures work. But it again does nothing to image sizes. So they're too small in this case as well. And I can't enlarge them, either. I also didn't get the justification to work. It may be possible, but it would require tinkering with the file. Still, with KFX it all works out of the box without any fuss at all. And I think that's the biggest benefit of it. In combination with native Kindle reader, it provides simple experience that works really well in most cases. I've pretty much moved completely to epub and KOReader on my Kindle, but denying KFX's benefits, or downplaying them, is a bit silly. It's a good format.

I already have a copy of Three Men in a Boat on several of my ereaders using my edit of @zelda pinwheel's 2010 edit. I've attached screenshots from several pages. I admit that the images in this version are all inline and it lacks the idiocy of having the images split out as if they are footnotes.

[salamanderjuice]

Originally Posted by jackm8

I meant word spacing. AZW3 doesn't support hyphenation, so there's really no solution for justified text.




You're again not providing anything that would substantiate your words. You're saying that it's all available elsewhere, but it's apparently not available in KOReader, it's certainly not available in AZW3. Where and on which devices is it? For myself, I can also confirm that KFX is more advanced compared to EPUB3 on Pocketbook. So where can I see what you're saying in action? It really shouldn't be that hard to take a screenshot from your devices, right? I've provided you with epub. Fonts that I used are open source. Just put the epub on your device, and take a screenshot on the same pages that I did.

And, yes you are changing your words, you went from KFX forcing the look of the books, which I'm glad to say, has been overruled, to KFX providing nothing new. In a few more posts, you'll start admitting that it offers features not present elsewhere.

ps.
Here's same epub on my Pocketbook InkPad in its native reader. That should be one of the devices that fits "Amazon's Enhanced Typesetting does not seem to offer any typesetting features that have not been available elsewhere for years if not decades."
Ligatures work. But it again does nothing to image sizes. So they're too small in this case as well. And I can't enlarge them, either. I also didn't get the justification to work. It may be possible, but it would require tinkering with the file. Still, with KFX it all works out of the box without any fuss at all. And I think that's the biggest benefit of it. In combination with native Kindle reader, it provides simple experience that works really well in most cases. I've pretty much moved completely to epub and KOReader on my Kindle, but denying KFX's benefits, or downplaying them, is a bit silly. It's a good format.

These aren't really format differences though. They are renderer differences. Kobo's KEPUB renderer will handle images like the KFX/AZW3 examples you have. I don't think it does ligatures however (though I think the Kobo ePub one will?).

I do wish we had better renderers in general. I don't think there's any that tick all the boxes simultaneously even on PC. Something is always left out.

[Sirtel]

Originally Posted by salamanderjuice

These aren't really format differences though. They are renderer differences. Kobo's KEPUB renderer will handle images like the KFX/AZW3 examples you have. I don't think it does ligatures however (though I think the Kobo ePub one will?)

You can enable kerning and ligatures in kepubs by editing the configuration file.