Kepub format questions

[forster01]

and i don't have any of the kepub patches installed...

[davidfor]

Generally, I agree.

Originally Posted by maximus83

2. Converting to .kepub gives you at least these features:
- Faster, more responsive page turns.

I've never really thought the difference was important, except maybe in very long chapters. And in recent firmware, the difference has dropped.

- Reading statistics

The in-book stats are the main reason I consider kepubs. I don't have enough books with images or

3. To convert in Calibre, just install the KoboTouchExtended plugin (developed by @davidfor),

No, not me. KoboTouchExtendedDriver is developed by @jgoguen. He also did the kepub output plugins. I do the main KoboTouch driver and the Kobo Utilities plugin. The kepub input and metadata reader and writer plugins are a bit confusing. They have my name on them, but, are in jgoguen's codebase. I don't remember how that happened.

[davidfor]

Originally Posted by geek1011

According to some emails I have recieved (I haven't checked this myself), it has helped with certain ebooks which don't show their styles otherwise. As for me, I find it a useful debugging option in certain cases.

For testing various style changes, I can see it would be handy. But, I haven't seen any other bugs. I'd be interested in what you have been told.

Most optional changes are for firmware bugs or customization, most unusual mandatory changes are to fix issues reported to me about differences in the kepub and epub renderer. The nbsp replacement is one of these (they don't show otherwise).

Not in any of my tests. The calibre editor tends to use the unicode character for everything instead of entities. I have lots of non-breaking spaces scattered through the books and they all show OK. And I remember discussing how different spaces work in the past. At the time I added various types of spaces as unicode, named HTML entities and numeric HTML entities to a test book. They all display OK.

The smart punctuation is my opinion (it isn't as heavy handed as others though),

My issue isn't that you do it, but that it isn't documented as being done and can't be turn off. But, unless I missed something, it only seems to be doing double and triple dashes (and then fixing comments). But, it is forcing a space around them. That is something that gets argued about. But, from memory, it also tends to be national. US tends to not use the space, UK tends to use them, but prefers an en-dash.

and the others are just code cleanups which make no difference otherwise (like the ms tags and the indentation of the opf). I'll work on documenting them all as I work on v3.

Not doing the nbsp replacement causes side effects in itself.

You said above they don't display, which isn't the case here. But, side effects sounds like something else. What are they?

[koboy]

Originally Posted by geek1011

I've mentioned it in bits and pieces scattered around many places. I'll be consolidating it for kepubify v3.


https://www.mobileread.com/forums/sh....php?p=3769235


Most are in the command documentation, some I've removed after the need was gone. You can find the most up-to-date information in: https://github.com/geek1011/kepubify...kepub/kepub.go


Custom CSS is currently added before the body tag end after all other CSS tweaks. Inlining adds the stylesheet as a style tag in the same place the link tag was (to preserve precedence).


That's partly the intention. You aren't supposed to notice the fixes unless they are necessary. But, I agree they need to be documented properly. That will be resolved in kepubify v3.

speaking as someone who is not the most technically minded slight understatement since i became aware of kepubify i use it all the time to convert from epub to kepub i find it's easy to use and very very fast to batch convert/excellent all rolled into one.

thank you. long may kepubify continue i'm looking forward to v3.

best wishes koboy

[kyrilson]

Originally Posted by koboy

speaking as someone who is not the most technically minded slight understatement since i became aware of kepubify i use it all the time to convert from epub to kepub i find it's easy to use and very very fast to batch convert/excellent all rolled into one.

thank you. long may kepubify continue i'm looking forward to v3.

best wishes koboy

I tried kepubify last week but Calibre wouldn't import the updated kepub. So in order to load it to my Kobo, as far as I could figure out, I'd have to create a folder for the author on the Kobo itself and copy it over to match up with my other kepubs already on the ereader. This is a bit cumbersome. Is there an easier way?

Sent from my SM-G950U1 using Tapatalk

[geek1011]

Originally Posted by kyrilson

I tried kepubify last week but Calibre wouldn't import the updated kepub. So in order to load it to my Kobo, as far as I could figure out, I'd have to create a folder for the author on the Kobo itself and copy it over to match up with my other kepubs already on the ereader. This is a bit cumbersome. Is there an easier way?

Sent from my SM-G950U1 using Tapatalk

You can either (depending on your needs):
- Drag a folder of books on to kepubify to preserve the structure
- Convert your whole library (https://www.mobileread.com/forums/sh...d.php?t=313137)
- Rename the books from .kepub.epub to .kepub so Calibre will recognize them

[kyrilson]

Originally Posted by geek1011

You can either (depending on your needs):

- Drag a folder of books on to kepubify to preserve the structure

- Convert your whole library (https://www.mobileread.com/forums/sh...d.php?t=313137)

- Rename the books from .kepub.epub to .kepub so Calibre will recognize them

Hmm. I didn’t know about that first trick. That might work best since I have a lot of ePubs already in calibre. I’ll try it later today. Thanks!

[GERGE]

kepub is nice and all but there is no ligatures there =(

[ebok]

I sideload some kepubs on my moded KA1 but the moment I click on the book it tells me something about adobe DRM and now I can't find them on the GUI. What is going on and how can I fix this? Cheers!

Originally Posted by davidfor

Generally, I agree.

I've never really thought the difference was important, except maybe in very long chapters. And in recent firmware, the difference has dropped.

With the books I was testing, about 25 total (mostly lengthier books with a lot of footnotes), the effect of converting to .kepub was dramatic. It was the difference between wanting to keep my Forma vs not keeping it. The page-turning, footnote popups, and better image handling were just huge, for me.

Originally Posted by davidfor

No, not me. KoboTouchExtendedDriver is developed by @jgoguen. He also did the kepub output plugins. I do the main KoboTouch driver and the Kobo Utilities plugin. The kepub input and metadata reader and writer plugins are a bit confusing. They have my name on them, but, are in jgoguen's codebase. I don't remember how that happened.

Oops, sorry for the confusion. Now fixed in the earlier post.

[ps67]

Originally Posted by ebok

I sideload some kepubs on my moded KA1 but the moment I click on the book it tells me something about adobe DRM and now I can't find them on the GUI. What is going on and how can I fix this? Cheers!

Do You use calibre? If yes what happens when You connect the Kobo to calibre? If there are some strange messages read them (corrupted database for example).

And what happens if You eliminate the books and sideload them again? You could also create them again before sideloading. This is to be sure that the issue is not with the books themselves.

I had a similar problem and the cause was a corrupted database (calibre told me it), so I had to do a logout from My Kobo id and sign in again. This generates a new database and all books from Kobo are downloaded again. Then You will sideload the others books (or not? may be they will remain on the Kobo, I don't remember). I hope Your problem will not need a logout but do not worry about it: it is boring but not painful.

And if You have a copy of the database You can install it again avoiding a log out (I never did it so it is better if somebody else help You in this case).

[ZodWallop]

Originally Posted by GERGE

kepub is nice and all but there is no ligatures there =(

Why is that, anyway? Is there a reason kepub doesn't support ligatures?

[jackie_w]

Originally Posted by ZodWallop

Why is that, anyway? Is there a reason kepub doesn't support ligatures?

Kepubs do support both ligatures and kerning if you add the right line of CSS - body {text-rendering: optimizeLegibility;} - either by hand, via calibre driver or via patch. Ligatures/kerning will only be as good as the font you're using.

The drawback is that if you read your books full-justified then occasionally word- and letter-spacing can be weirdly uneven. I've convinced myself that this unevenness arises (at least partly) from the KoboTouchExtended (KTE) algorithm which adds the koboSpan tags necessary for turning an epub into a kepub. KTE tries to replicate exactly the algorithm used in Kobo-bought kepubs so I don't suppose it's likely to change.

FWIW I did hack my own version of KTE to change the koboSpan algorithm. I've been happy with the results for my own reading purposes, with the caveat that I can't be 100% sure that I haven't degraded the bookmarking/notes/highlighting features in some way because I rarely use them.

Also I've never compared side-by-side a full-justified epub with an equivalent 'hacked' kepub. All I know is that, for over 2 years, my hacked kepubs have been good enough for me and they have both ligatures and kerning.

[NiLuJe]

@jackie_w: For curiosity's sake, what did you tweak?

[jackie_w]

Originally Posted by NiLuJe

@jackie_w: For curiosity's sake, what did you tweak?

For most of the past 2 years I tweaked in 2 ways:

• Create only one koboSpan per node rather than trying to create one koboSpan per sentence.
• For text content within any single koboSpan, if it contains leading and/or trailing spaces, move the spaces outside the koboSpan tags.

Until very recently I was convinced (based on no evidence ) that the former was more important. Now I think it might be the latter, but I haven't yet read enough books tweaked only with the latter option to draw any firm conclusions.