ePub Store: Kobo or Google Play?

[salamanderjuice]

Originally Posted by HarryT

Won't doing that give you kepub rather than ePub books? You'd still need to do a conversion, in that case.

I can import them fine into ADE, Edge can read them. I've tried them with a few other mobile epub readers and they seem to work. I think most readers ignore Kobo's extra tags. Maybe it's a problem with other eInk readers, IDK.

If need be Kobo's extra tags can be removed and IMO that's still better than conversion.

[llcj]

Different strokes for different folks I guess. I find when importing into Calibre from K4PC that I am presented with a line of gibberish rather than a title more irritating than dealing with ADE. However, I understand your point.

[HarryT]

Sounds good! The OP has a number of options to choose from; I was simply saying what my preferred solution is, which may of course be different to that of other people .

[JSWolf]

Originally Posted by HarryT

There's a very easy way to disable KFX in current versions of K4PC/K4Mac, as explained in the first post of this thread:

https://www.mobileread.com/forums/sh...d.php?t=283371

I agree with you that ADE is a lot harder to use.

But if you did not have MR handy to find out what can be done to fix the current K4PC, then you'd be stuck with KFX.

ADE is not harder to use than K4PC. All you need do with ADE is register for an account at Adobe and use that UN/PW to register ADE. K4PC also requires being registered. Neither is more difficult than the other to get set up.

[HarryT]

Originally Posted by JSWolf

But if you did not have MR handy to find out what can be done to fix the current K4PC, then you'd be stuck with KFX.

But the OP does have MR .

ADE is not harder to use than K4PC.

Um, you're the one who said it was...

Originally Posted by JSWolf

ADE 2.0.1 is a lot harder to use than the current version of K4PC that gets you KFX in most cases.

[JSWolf]

Originally Posted by salamanderjuice

I can import them fine into ADE, Edge can read them. I've tried them with a few other mobile epub readers and they seem to work. I think most readers ignore Kobo's extra tags. Maybe it's a problem with other eInk readers, IDK.

If need be Kobo's extra tags can be removed and IMO that's still better than conversion.

The Modify ePub plugin can remove the kepub tags the kepub becomes ePub once again. However, you can simply download the eBooks as ePub.

[pwalker8]

Originally Posted by HarryT

Sounds good! The OP has a number of options to choose from; I was simply saying what my preferred solution is, which may of course be different to that of other people .

About a year ago, I bought the kindle paper white when my old Kindle 1 was no longer supported as a download device for some ebooks. It has the advantage of giving me a back up ebook device for backpacking trips. It's always good to have options.

[JSWolf]

Originally Posted by HarryT

Um, you're the one who said it was...

You didn't fully quote what I said and if you read it properly, you'll read it as sarcasm.

Now that I' think about it, ADE is actually easier to use than K4PC because when you look at what you've downloaded, you can tell what books are what because ADE shows the filename. The books downloaded with KPC don't have filenames that are of any use.

[HarryT]

Originally Posted by JSWolf

The books downloaded with KPC don't have filenames that are of any use.

True, but of no practical concern if you're just using K4PC as a way of getting books into Calibre. Just sort the "My Kindle Content" folder by date, and drag into Calibre the books whose timestamps correspond with the time you last ran K4PC (i.e. the books at the top of the list).

[DiapDealer]

I'm certainly no Amazon hater, but as an EPUB reader (primarily), I much prefer dealing with ADE-based EPUBs rather than converting Kindlebooks to EPUB. I can never trust 100% that a conversion was truly "lossless." I typically only convert/unpack Kindlebooks when I can't purchase the plain-jane, ADE-based (or DRM-Free) EPUB. And even then, I'll often just read them with the Kindle app on my tablet, rather than converting them to read with my EPUB-reading app on my tablet.

My preference is typically Kobo (if Kepub can be avoided), then Google Play, then Amazon.

[Apache]

I reread lots of books and I have not noticed any of them having any kind of loss from converting to epub.
Apache

[DiapDealer]

Originally Posted by Apache

I reread lots of books and I have not noticed any of them having any kind of loss from converting to epub.
Apache

I have no doubt. I'm only saying a don't have complete faith that something unforseen might not happen, and I wouldn't discover it until in the midst of my read ... away from my computer ... where the tools to fix it all live.

I never said it was a rational fear.

Rationally ... it just makes very little sense to me to convert books when I can easily buy them already in the format I want to read them in (or don't mind reading the occasional book with a different app whenever I--rarely--buy a book in my second-favorite format). Conversion changes things. Regardless if I'm aware of those changes or not.

[JSWolf]

So far, every KF8 I've format shifted, I've never had a problem something unforeseen.

[DiapDealer]

As one who contributes to KindleUnpack's code, I can assure you that bugs are still being discovered and fixed. Books with previously unseen circumstances are how those bugs are discovered and fixed.

So regardless of whether you personally have never run into problems converting; conversion is not entirely risk-free. And I prefer not to take that risk unless there are no other choices. Others are, of course, free to utilize their own risk-to-reward calculations in their personal procedures.

[DNSB]

Originally Posted by HarryT

Won't doing that give you kepub rather than ePub books? You'd still need to do a conversion, in that case.

I haven't found any issues with opening kepubs using non-Kobo hardware or software. The extra spans are pretty much invisible. The only real issue is that quite a few epubs are now epub3 and some authors/publishers are using epub3 features that can cause odd looking rendering when using an epub2 renderer. In that case for my Kobos, either renaming the epub to .kepub.epub or using the KoboTouchExtended driver solves the issue since the ACCESS renderer is pretty good at epub3.