[Device Plugin] Kobo Touch Extended Driver

[PeterT]

Originally Posted by davidfor

That's OK. I frequently turn it off when testing things so that connecting doesn't take as long. And I never remember to turn it on until I notice a missing series.

Maybe time for an optional feature (turned on by default) that will warn if Metadata Management is manual?

[arspr]

Originally Posted by PeterT

Maybe time for an optional feature (turned on by default) that will warn if Metadata Management is manual?

I was just going to suggest the very same thing.

It's not obvious that this setting rely on other. I think it would be a great UI improvement if you get a warning about Metadata Management "wrong" setting just below the setting itself in KT (and therefore KTE).

It's a really tricky setting. You think you have just enabled it, but it isn't because of other dependencies, and you don't actually have any feedback...

[davidfor]

Originally Posted by arspr

I was just going to suggest the very same thing.

It's not obvious that this setting rely on other. I think it would be a great UI improvement if you get a warning about Metadata Management "wrong" setting just below the setting itself in KT (and therefore KTE).

It's a really tricky setting. You think you have just enabled it, but it isn't because of other dependencies, and you don't actually have any feedback...

The problem with this is that the driver configuration dialog is almost completely out of my control. I can set the text of the option, the tooltip and the type. Everything else is done by base calibre. What I haven't looked at is if I can put in a warning when the dialog closes. There already is one if you select a format that isn't in the default list, so there might be something I can look at.

The alternative is writing a new configuration dialog. Some time ago I had a look at doing a tabbed dialog so that the common driver options are on one tab, the KoboTouch options on one or more and any subclassed drivers such as KTE could override or add tabs as needed. I might revisit it as I'm a lot more comfortable with calibre code outside of the driver now.

[fdant]

I've notice that the actual version (2.3.3) adds a extra left margin to the text, causing a problem to the dictionary (when I try to get the definition from the last word of each line) and sometimes cropping the text at the right side of the screen.

[jgoguen]

Is this across all books, or only on a specific book?

[NiLuJe]

That vaguely looks like what happens with a body element with a margin and/or padding set, which is just broken with Kobo's kepub renderer (everything shifts to the right, and stuff ends up offscreen). (EDIT: In FullScreen mode).

[fdant]

I'm sorry, but now I've found out that the source of the problem is the fullscreen mode. Removing "FullScreenReading=true" from the .config file solved the problem.

I've though the plugin triggers the problem because it disappear when the box "activate advanced kobo functions" (or something similar, I'm using the portuguese translation) was unchecked.

[PeterT]

There was a time I am used the full screen option but I found too many weird behaviors with it and turned it off and left it off.

[GeoffR]

There seem to be two seperate problems that affect kepubs in full-screen mode: one triggered by margin/padding on the body element; the other by a lack of padding on div/p elements. Both problems have workarounds for sideloaded kepubs though, which is what the recent changes to the driver were about. I've posted here with details.

[jgoguen]

Is full-screen supported by Kobo yet?

[PeterT]

Nope
(added to make the message long enough to post)

[anacreon]

I have many poetry books, which I would like converted to kepubs while keeping as close to the author's choices as possible, and I have problems.

It seems the plugin applies my conversion parameters, so I unchecked all save minimal line height, default font size, and a few CSS
body { orphans: 1; widows: 1; }
div, p , blockquote {line-height: 1.2},
page { margin-bottom: 5pt; margin-top: 5pt;}


Mostly, when I then reconverted my epubs, it looked good, but I have two problems

1. all the beautiful centred separations (stars, small pictures and such) become left justified
2. in the books where there are negative indents, which remain readable as epubs, I loose the first characters of every line.

I tried unchecking "modify CSS" from the plugin parameters, but it made no difference.

Anybody know how I can solve that? I hate the way epubs look on my kobos, and make note calling next to impossible.

[jackie_w]

Originally Posted by anacreon

1. all the beautiful centred separations (stars, small pictures and such) become left justified

If your poetry book already contains all the correct css values for text-align, whilst the book is open, open the font menu option and try changing the 'Justification' setting to 'Off' for that book. I think that should stop your device stomping all over the book's internal css alignments.

[anacreon]

Originally Posted by jackie_w

If your poetry book already contains all the correct css values for text-align, whilst the book is open, open the font menu option and try changing the 'Justification' setting to 'Off' for that book. I think that should stop your device stomping all over the book's internal css alignments.

Thanks for the answer. Unfortunately, those books obviously do NOT contain the correct css values - never mind that I paid for the paper and the epub versions...

The alignment is incorrect both on kobo reader with justification off and calibre viewer.

[jgoguen]

@anacreon: Do you have Dropbox or Copy or some similar service where you could put the original ePub and the converted KePub up for me to download? These are obviously copyrighted works, so please don't post the links publicly, PM them to me, and I'll let you know when I download them. I'd like to take a look at the files and see if I can sort out what may be different enough to throw off the alignment.