Firmware 4.16.13337

[davidfor]

Originally Posted by Calenorn

Hmmm. So is the day coming when side-loaded books will have to be kepub to play nicely with Kobos? I have a lot of old epubs. A LOT. Sure don't want to have to convert them all!

As long a Kobo supports books with Adobe DRM, then it will support sideloading ePubs. And I think if they did drop that support, they would change the kepub renderer to handle epubs without the kepub modifications.

[JSWolf]

Originally Posted by davidfor

As long a Kobo supports books with Adobe DRM, then it will support sideloading ePubs. And I think if they did drop that support, they would change the kepub renderer to handle epubs without the kepub modifications.

If Kobo dropped Adobe DRM support, there would be hell to pay as that would mean no more library eBooks. That's not going to happen since Rakuten owns Overdrive.

[MGlitch]

Originally Posted by JSWolf

If Kobo dropped Adobe DRM support, there would be hell to pay as that would mean no more library eBooks. That's not going to happen since Rakuten owns Overdrive.

Except there are other ways to handle this that don’t involve Adobe DRM and presumably Kobo would have developed their own way if they did ever drop Adobe DRM.

[JSWolf]

Originally Posted by MGlitch

Except there are other ways to handle this that don’t involve Adobe DRM and presumably Kobo would have developed their own way if they did ever drop Adobe DRM.

How are there other ways as Adobe owns the DRM and time litmied DRM for ePub could very well be copyrighted by Adobe.

[MGlitch]

Originally Posted by JSWolf

How are there other ways as Adobe owns the DRM and time litmied DRM for ePub could very well be copyrighted by Adobe.

I’d like to introduce you to a small company you might have heard of called Amazon. And before you whine that you can’t get amazon books from the library directly to a kindle I’ll remind you they don’t own overdrive.

Of course since this is all over your hyperbolic response to David giving an example of what would be a sign Kobo was giving up ePub support (and even then he had a caveat) it’s pretty much moot.

[John F]

Originally Posted by JSWolf

How are there other ways as Adobe owns the DRM and time litmied DRM for ePub could very well be copyrighted by Adobe.

I was under the impression that when you borrowed from a library using the Kobo device, that it downloaded a time limited DRMed kepub?

[davidfor]

Originally Posted by geek1011

I usually edit my books to be one file per chapter and a TOC entry per file, and to remove overly specific font styling, but one thing I noticed the most is page numbering jumping between chapters, and stats bring messed up.

Is this in 4.16.13337? Or before? The firmware I have seem to be fine.

P.S. One pet peeve of mine is the books with a whole file just for the title of the chapter, and with the content in another file, not in the TOC, but referenced using the spine.

For a book chapter, I would generally agree. I've seen a couple of books where I agreed with it. But, I'd probably add a ToC entry for the actual text.

I partly disagree with this, but only with regards to fiction. I believe publishers get too much freedom with EPUB, and tend to abuse it (especially for fiction). The font overriding wars is an example of this, and using divs for everything and using CSS to make it online, increase the font size, look like a paragraph, and so on.

The body font I agree with. It would be nice to be able control that separately to fonts used elsewhere. My problem with Jon's campaign is that I see no reason to cram everything together. A few extra page turns per book doesn't hurt. And I like a little style in the books.

[geek1011]

Originally Posted by davidfor

Is this in 4.16.13337? Or before? The firmware I have seem to be fine.

It's the previous versions.

For a book chapter, I would generally agree. I've seen a couple of books where I agreed with it. But, I'd probably add a ToC entry for the actual text.

You wouldn't want to merge them?

The body font I agree with. It would be nice to be able control that separately to fonts used elsewhere. My problem with Jon's campaign is that I see no reason to cram everything together. A few extra page turns per book doesn't hurt. And I like a little style in the books.

Yes, that makes sense. Maybe Jon would rather read fb2 ebooks ? If you convert them to epub, you get the most consistent and boring look I've ever seen (but the best compatibility).

[Terisa de morgan]

Originally Posted by geek1011

As for the patches which will be deprecated or rewritten (so far), see src/version/4.16.13337/patches.md on GitHub.

I have a couple of comments about this file:

• Could you rewrite "Custom font to collection and author titles" and specially "Increase the view details container size".
• Which is the persistent clock that appears in the status bar and that makes unnecessary "Clock display duration"? Standard from Kobo or the miniclock?

Thanks a lot for all your work.

[geek1011]

Originally Posted by MGlitch

Pardon my ignorance how does one go about snagging the patches that have been updated from github? And is it just grabbing the nickel, Adobe, rmsdk, and libnickle files or would I have to compile anything?

You have multiple options:
- Manually copy them from the files in src/versions/4.16.13337.
- If you use Linux, run ./scripts/build.sh in the repo.
- If you don't, you can use the almost-finished build script written in Go to build the patches (go run ./scripts/build.go 4.16.13337).
- If you don't want to do anything, the patches will probably be out before next Tuesday, either for this version, or the next one when it is released.

[geek1011]

Originally Posted by Terisa de morgan

I have a couple of comments about this file:

• Could you rewrite "Custom font to collection and author titles" and specially "Increase the view details container size".
• Which is the persistent clock that appears in the status bar and that makes unnecessary "Clock display duration"? Standard from Kobo or the miniclock?

Thanks a lot for all your work.

I'll rewrite those if I have time, but that's next week at the earliest. Also, jackie_w and oren64 have more experience with those parts of the CSS then I do.

The clock now shows in the top-right of the status bar, and doesn't disappear after a certain amount of time. Depending on how you interpret it, persistent may not be the right word.

[Terisa de morgan]

Originally Posted by geek1011

I'll rewrite those if I have time, but that's next week at the earliest. Also, jackie_w and oren64 have more experience with those parts of the CSS then I do.

For me, that's to do it in a hurry, no problem with that, and it cannot be done... well... a lot of wasted space in that page, not a matter of live of death...

Originally Posted by geek1011

The clock now shows in the top-right of the status bar, and doesn't disappear after a certain amount of time. Depending on how you interpret it, persistent may not be the right word.

Ok, it appears when all the menus appear, thank you. So, I'll stick to miniclock

[MGlitch]

Originally Posted by geek1011

You have multiple options:
- Manually copy them from the files in src/versions/4.16.13337.
- If you use Linux, run ./scripts/build.sh in the repo.
- If you don't, you can use the almost-finished build script written in Go to build the patches (go run ./scripts/build.go 4.16.13337).
- If you don't want to do anything, the patches will probably be out before next Tuesday, either for this version, or the next one when it is released.

Thank you, I’ll probably hold off unless the features in 4.16 start calling me too strongly, I really do like the new reader UI.

[geek1011]

Originally Posted by MGlitch

Thank you, I’ll probably hold off unless the features in 4.16 start calling me too strongly, I really do like the new reader UI.

Yes, that's probably a good idea. 4.16.13337 is still a bit buggy, and most of the good patches aren't updated yet.

[ZodWallop]

Originally Posted by Calenorn

Hmmm. So is the day coming when side-loaded books will have to be kepub to play nicely with Kobos?

Probably not. But I would suggest using kepubs on a Kobo anyway.

I have a lot of old epubs. A LOT. Sure don't want to have to convert them all!

Originally Posted by Sirtel

Why not? It's a bulk job in Calibre. It's not like you have to convert them one by one.

Even better, using the extended driver, the books will be converted to kepub automatically when sending them to the device. You won't have the kepubs littering your library.

This exactly. I have 3,350 kepubs on my Kobo and none in my Calibre library. The extended driver just converts the books as it sends them to the device. Easy peasy.