Standard EBooks Adds (kepub imports as epub)

[bdub]

When I add a kepub from Standard Ebooks, it shows up as an epub instead of as a kepub.

Also, when I add the advanced epub from Standard Ebooks, no cover comes through.

Any ideas?

Here's an example to try out:

https://standardebooks.org/ebooks/h-...es-dexter-ward

I'm using 8.12.

[JSWolf]

Originally Posted by bdub

When I add a kepub from Standard Ebooks, it shows up as an epub instead of as a kepub.

Also, when I add the advanced epub from Standard Ebooks, no cover comes through.

Any ideas?

Here's an example to try out:

https://standardebooks.org/ebooks/h-...es-dexter-ward

I'm using 8.12.

StandardEBooks code is atrocious. Try here to see if the same eBooks are available.

[bdub]

Originally Posted by JSWolf

StandardEBooks code is atrocious. Try here to see if the same eBooks are available.

I usually get my public domain books from either Project Gutenberg or the library. However, I do like how they will compile short stories by authors into Short Fiction books. And there are some books they have that I can't find either at Project Gutenberg or the library.

What code is atrocious?

[jackie_w]

Originally Posted by bdub

When I add a kepub from Standard Ebooks, it shows up as an epub instead of as a kepub.

Using the book you linked...

The downloaded kepub is has filename & extension

h-p-lovecraft_the-case-of-charles-dexter-ward.kepub.epub

If you import that file into your calibre library as-is, calibre will see it as an epub because calibre only sees the .epub file extension. If you want calibre to recognise it as a kepub then rename the file to the following before importing

h-p-lovecraft_the-case-of-charles-dexter-ward.kepub

[bdub]

I have some follow-up questions.

On my Kobo, if I look at the file extension, it shows as kepub.epub. When I look at my Calibre library, I see only kepub.

Since it appears that Calibre will treat the kepub.epub file extension as epub, what happens when I convert that kepub to an epub or kepub? I'm looking at the results in the viewer, and they still look okay. But I'm expecting something to not work right.

Is the best practice now if I download a file with a kepub.epub extension to rename it?

What would have to change in Calibre to treat the extension kepub.epub as a kepub?

[JSWolf]

Originally Posted by bdub

I usually get my public domain books from either Project Gutenberg or the library. However, I do like how they will compile short stories by authors into Short Fiction books. And there are some books they have that I can't find either at Project Gutenberg or the library.

What code is atrocious?

The code used for the eBooks from StandardEBooks is atrocious. It's why there are problems with it. It's why it won't work as an ePub with a Kobo. I don't know why they insist on using code that they don't need to use. It's awful.

[PeterT]

The device driver handles the rename from .kepub to .kepub.epub when the book is transferred to the Kobo.

The use of a single extension to identify ebook type is just how it is and I really doubt kovid would ever consider a change

Sent from my TB350FU using Tapatalk

[theducks]

Calibre can view either. KEPB just has additional markup that Calibre ignores.

[JSWolf]

Originally Posted by theducks

Calibre can view either. KEPB just has additional markup that Calibre ignores.

But if you plan to edit any of the eBooks, then you want ePub. But even then it's a mess because the code is a mess.

Best to try to find the eBooks you want in the library right here at MR.

[DNSB]

Originally Posted by JSWolf

But if you plan to edit any of the eBooks, then you want ePub. But even then it's a mess because the code is a mess.

Best to try to find the eBooks you want in the library right here at MR.

Jon, isn't about time that you stopped whinging about eBook coding choices that you don't agree with?

1. calibre will strip the extra spans that are 99% of the added code for kepubs. Or you can use the ModifyePub plugin which will do the same.
2. Standard Ebooks like Vellum uses consistent code which, for me, means that using Sigil's saved searches especially with the new conditional run option or calibre's Editor Chains plugin makes it very easy to clean up the code.
3. Standard Ebooks uses semantic markup. Very good for accessibility which is something I personally support.
4. At this time, ePub3 has been the current ePub standard for over a decade. Isn't time that you gave up whinging that some ebooks just do not display well using ADE 2?

Yes, very few apps and ereaders will display Standard eBook's Advanced coding well. Oddly the ePub3 renderer on Kobo ereaders does render them well. Ditto for Thorium and Sigil. Perhaps you might want to re-read the warning? The one that reads: "Advanced epub—An advanced format that uses the latest technology not yet fully supported by most ereaders".

[JSWolf]

Originally Posted by DNSB

Jon, isn't about time that you stopped whinging about eBook coding choices that you don't agree with?

1. calibre will strip the extra spans that are 99% of the added code for kepubs. Or you can use the ModifyePub plugin which will do the same.
2. Standard Ebooks like Vellum uses consistent code which, for me, means that using Sigil's saved searches especially with the new conditional run option or calibre's Editor Chains plugin makes it very easy to clean up the code.
3. Standard Ebooks uses semantic markup. Very good for accessibility which is something I personally support.
4. At this time, ePub3 has been the current ePub standard for over a decade. Isn't time that you gave up whinging that some ebooks just do not display well using ADE 2?

Yes, very few apps and ereaders will display Standard eBook's Advanced coding well. Oddly the ePub3 renderer on Kobo ereaders does render them well. Ditto for Thorium and Sigil. Perhaps you might want to re-read the warning? The one that reads: "Advanced epub—An advanced format that uses the latest technology not yet fully supported by most ereaders".

There's no reason the eBooks cannot properly display with RMSDK on a Kobo. It's stupid code that they don't need that's causing the problem. The code could be very simple and still be ePub3 with accessibility. But they choose to use really bad code that a lot of software won't understand.

[DNSB]

Jon, haven't you been slapped down enough times over your claims that an ePub MUST display properly with old versions of RMSDK? For me, RMSDK is there simply for the times I send library books using ADEPT DRM, otherwise, I use the ePub3 renderer.

And I would appreciate that when you claim an ePub can properly display only using ePub2 supported by old RMSDK versions, that you would post the code needed. As in discussions where you have claimed that displaying a specialized item can be done in RMSDK supported ePub2 without any willingness to port your code despite being asked for that code.

[thiago.eec]

Originally Posted by DNSB

[*]At this time, ePub3 has been the current ePub standard for over a decade. Isn't time that you gave up whinging that some ebooks just do not display well using ADE 2?[/list]

I don't get it either. EPUB3 is the EPUB standard. It is backward compatible and works fine in recent apps/devices. It's like complaining IE doesn't work well with HTML5.

---
Edit:

The linked book, for example, passes EPUBCheck. It does use the obsolete "epub:type='ordinal'", but that doesn't make it fail. It also uses CSS namespaces, but I don't think this is a problem for recent renderers. The rest is just pretty standard: no Math, no JS, just standard and custom epub:type's.

[JSWolf]

Originally Posted by DNSB

Jon, haven't you been slapped down enough times over your claims that an ePub MUST display properly with old versions of RMSDK? For me, RMSDK is there simply for the times I send library books using ADEPT DRM, otherwise, I use the ePub3 renderer.

And I would appreciate that when you claim an ePub can properly display only using ePub2 supported by old RMSDK versions, that you would post the code needed. As in discussions where you have claimed that displaying a specialized item can be done in RMSDK supported ePub2 without any willingness to port your code despite being asked for that code.

The thing is, it could display with RMSDK, be ePub3, and have all of the needed accessibility. There is nothing in these eBooks that needs complicated code. Most of the code that's needed would work with ePub2 and ePub3. There is no need to use the latest code where most programs used to display ePub won't be fully compatible.

[JSWolf]

Originally Posted by thiago.eec

I don't get it either. EPUB3 is the EPUB standard. It is backward compatible and works fine in recent apps/devices. It's like complaining IE doesn't work well with HTML5.

---
Edit:

The linked book, for example, passes EPUBCheck. It does use the obsolete "epub:type='ordinal'", but that doesn't make it fail. It also uses CSS namespaces, but I don't think this is a problem for recent renderers. The rest is just pretty standard: no Math, no JS, just standard and custom epub:type's.

Look at the CSS and tell me that it needs to be that complicated when it could be that simple. The way to do eBooks is KISS. StandardEBooks way to do it is Keep it as complicated as possible.