Calibre v8.0 kepub features?

[kovidgoyal]

Turn on hyphenation.

[hengyu]

Originally Posted by kovidgoyal

Turn on hyphenation.

Not sure if you're replying to me, but hyphenation is already on and can be seen in my image?

[kovidgoyal]

Then that's the best you are going to get, there is no difference in the markup generated, between the builtin and KTE drivers that can possibly affect how the kobo firmware does justification.

[hengyu]

Originally Posted by kovidgoyal

Then that's the best you are going to get, there is no difference in the markup generated, between the builtin and KTE drivers that can possibly affect how the kobo firmware does justification.

I downgraded Calibre to 7.26 and used the old way to send the exact same book to my device. Here's the outcome, and a comparison image.

[kovidgoyal]

The only difference I can see is there is no space after the period. If converting to KEPUB is removing the sapce in this book, then open a bug report and attach the original book.

[hengyu]

Thanks, I will open a bug report as suggested and upload both the original EPUB and the v8 converted KEPUB and the v7 + extended driver converted KEPUB.

The space is still there when I open the .kepub.epub file using Calibre's reader via the Device menu, and it doesn't seem like that's the problem here.

I also got another comparison photo of the two versions.

Update:

Output is confirmed different, but the broken justified text is a consequence of trying to make sure there're no gaps in highlighting, and this won't be fixed

https://bugs.launchpad.net/calibre/+bug/2107778

[Terisa de morgan]

Originally Posted by hengyu

Thanks, I will open a bug report as suggested and upload both the original EPUB and the v8 converted KEPUB and the v7 + extended driver converted KEPUB.

The space is still there when I open the .kepub.epub file using Calibre's reader via the Device menu, and it doesn't seem like that's the problem here.

I also got another comparison photo of the two versions.

Checking those pictures, it looks like there is no added space before the dot in v8. Non-break space instead of normal space?

[JSWolf]

Originally Posted by hengyu

Thanks, I will open a bug report as suggested and upload both the original EPUB and the v8 converted KEPUB and the v7 + extended driver converted KEPUB.

The space is still there when I open the .kepub.epub file using Calibre's reader via the Device menu, and it doesn't seem like that's the problem here.

I also got another comparison photo of the two versions.

Update:

Output is confirmed different, but the broken justified text is a consequence of trying to make sure there're no gaps in highlighting, and this won't be fixed

https://bugs.launchpad.net/calibre/+bug/2107778

Try the version of calibre 8 prior to the highlighting fix and see if it fixes the problem you are having. If it does fix the problem, report it.

[Sirtel]

This is a dealbreaker for me too. I don't highlight, but I read only justified text. This means I've got to stay on 7.26 from now on.

[Terisa de morgan]

Originally Posted by Sirtel

This is a dealbreaker for me too. I don't highlight, but I read only justified text. This means I've got to stay on 7.26 from now on.

Try first, I read only justified text and I hadn't felt it till somebody has said something... and still don't note it when I'm reading.

[Sirtel]

Originally Posted by Terisa de morgan

Try first, I read only justified text and I hadn't felt it till somebody has said something... and still don't note it when I'm reading.

I noticed it, but because I use a smallish font and the space-reducing patch, my instances were far fewer than those of the OP. So I just thought it was something in the book I was reading. The problem was definitely there, though.

[PeterT]

I realise it's a long shot, and it's not a feature that was previously in either the base KoboTouch or KoboTouch Extended driver but would it be possible to display a warning if the any of the columns in the Custom Collections field are not present in the database? It's fairly common for folks to forget the leading # symbol on field names.

[kovidgoyal]

Originally Posted by PeterT

I realise it's a long shot, and it's not a feature that was previously in either the base KoboTouch or KoboTouch Extended driver but would it be possible to display a warning if the any of the columns in the Custom Collections field are not present in the database? It's fairly common for folks to forget the leading # symbol on field names.

You mean while configuring the driver?

[DNSB]

Originally Posted by kovidgoyal

You mean while configuring the driver?

I think that is what is being asked for. If you enter an invalid column name such as adding a # to tags ( #tags instead of tags ) or failing to add a # to a custom column ( finished instead of #finished ) or simply enter a mistyped column name ( tgas instead of tags ).

Of course, this is probably much easier to suggest than to code.

[chaley]

Originally Posted by kovidgoyal

You mean while configuring the driver?

Originally Posted by DNSB

I think that is what is being asked for. If you enter an invalid column name such as adding a # to tags ( #tags instead of tags ) or failing to add a # to a custom column ( finished instead of #finished ) or simply enter a mistyped column name ( tgas instead of tags ).

Of course, this is probably much easier to suggest than to code.

@Kovid, I'll submit a PR.