[Device Plugin] Kobo Touch Extended Driver

[davidfor]

I've done some experiments, and I agree with jgoguen. It sounds like it is how the book was created.

Attached is a sample book with pictures and chapters in various layouts:

• First chapter has full screen picture in the middle of the chapter
• Then another chapter followed by picture in a separate file and another set of text in separate file.
• Then a chapter that starts with the picture and has text afterwards.

In all cases, the picture is wrapped in SVG to display it full screen. And they work as I expected. The first has page numbering across the full chapter including the picture. The second restarts the page numbering for each file. The picture and later text file don't have a chapter name displayed. The last one starts the page numbering with the picture and keeps going from there. It doesn't display chapter name.

My guess would be snowstone's book does the second one. But, it might be the last one. Splitting the picture into a separate file should make it easier to guarantee it is displayed on a separate page by itself. But, it does mess up the page numbering used for kepubs.

[molier]

Since the latest firmware 3.8.0 the look and feel of the kepub misses the upper and lower toolbars with title of book end pages per chapter. I have read this plugin is no longer being developed. Is there an alternative?

[PeterT]

That will not be an issue with the driver,rather its a difference with the A device itself and how it handles kepub formats.

Unfortunately I'm traveling so can't experiment right now. Hopefully someone else can provide feedback.

Also while its not under active development it does not mean no development...

[davidfor]

Originally Posted by molier

Since the latest firmware 3.8.0 the look and feel of the kepub misses the upper and lower toolbars with title of book end pages per chapter.

That most likely means you have added the option to allow full screen reading into the config file. Then went into the reading settings and changed a setting. Go into the reading settings and look for an option something like "Show header and footer." Change the setting and see if the title and footer are shown again.

I have read this plugin is no longer being developed. Is there an alternative?

Yes, the original developer has moved on from the plugin. But, nothing has changed to make the plugin not work. There are several people here capable of making any changes needed. If there are changes needed, something will be done.

[fernando2112]

Hi, I just bought a Kobo Glo, and I am using this extension.

When trying to use my own epubs file, the top title bar is not visible, so I installed the plugin, and now it is visible and it's fine.
But, I usually edit my epubs with embedded fonts for headings (h1,h2, etc), and after the plugin, they do not work anymore.
So without the plugin, I got no title bar, which sucks, but have embedded fonts working properly, with the plugin, the fonts no longer work.

Is there any way to use the plugin, and have embedded fonts to work at the same time?

Thanks

[jgoguen]

No, but that's a known bug with the Kobo reader firmware. What I would recommend you do instead is send your fonts to the reader (there's directions in the Kobo forum for doing that) and use custom CSS rules to reference those fonts instead of embedding them. It's not as nice of a solution, it really ties you to this particular setup, but until Kobo fixes that bug it's probably the best you can do.

[fernando2112]

Oh I see.

Well, I will give it a try… but I agree with you, it is not the ideal solution.
Don't know for how long Kobo have this bug, but I hope they fix it soon.

Thank you very much for the quick reply, it really helped

[jgoguen]

They've had that bug for a while...

[fernando2112]

Oh, that sucks…

What about the "Modify Epub" plugin?
https://www.mobileread.com/forums/sho...d.php?t=154371

They say it removes some code from the kepub (css and js referencing) that is responsible to force kobo css rules, some kobo hacking style stuff, I don't know much about.

This would be the code kobo applies that mess up with the css:

<?xml version='1.0' encoding='utf-8'?>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Wild Cards I</title>
<link rel="stylesheet" type="text/css" href="../styles/stylesheet.css"/>
<style id="kobostylehacks" type="text/css">div#book-inner p, div#book-inner div { font-size: 1.0em; } a { color: black; } a:link, a:visited, a:hover, a:active { color: blue; } div#book-inner * { margin-top: 0 !important; margin-bottom: 0 !important;}
</style><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
</head>

I tried the plugin, but I don't understand much of its functionality yet, so it didn't worked for me.

Do you guys tried this method?

[jgoguen]

No change, if you use a KePub with embedded fonts, you're going to have a bad time. Normal ePub is fine, KePub is not.

[fernando2112]

Oh ok, thanks for the info!

Guess it's just sit and wait for a fix then

[muadfr]

hello,
which firmware do I need to install on my aura HD to get the stats on side-loaded kepub ??
I have 3.3 and I'm using this plugin but I don't have the stats.

[snowstone]

Originally Posted by muadfr

hello,
which firmware do I need to install on my aura HD to get the stats on side-loaded kepub ??
I have 3.3 and I'm using this plugin but I don't have the stats.

Kobo removed stats from firmware 2.9.0 and up. So it doesn't matter if you use the plugin.

[JSWolf]

Originally Posted by jgoguen

No change, if you use a KePub with embedded fonts, you're going to have a bad time. Normal ePub is fine, KePub is not.

What is wrong with kepub and embedded fonts?

Can a kepub with embedded fonts be easily converted back to the ePub like kepub without embedded fonts can?

[muadfr]

Originally Posted by snowstone

Kobo removed stats from firmware 2.9.0 and up. So it doesn't matter if you use the plugin.

Thanks for the reply.
So if I downgrade my aura hd I'll be able to get the stats.