Glo Calibre Plugin KoboExtended: Shut off Header and Footer?

[jgoguen]

I wonder if this is another difference between ACCESS and the Adobe RM engines? You're seeing success with global KePub styling but ibu is failing with per-ePub CSS. Or maybe it would be the same if you applied the CSS directly to a KePub instead of globally.

[ibu]

Originally Posted by DNSB

That value represents the line spacing slider position.

What does that mean exactly please?
Where does the scala begins and where does it end? (1 to 4?)
Is it equal to the CSS value of line-height?

Originally Posted by DNSB

What I am seeing here is that after I added a custom .css for .kepubs, the slider position no longer seems to have an effect.

Hhmm. That different here as my few experiments showed me.

May be we can prove that together with a reference valid epub document without any embedded css?
Does anyone know a source of such an epub?

[DNSB]

Originally Posted by jgoguen

I wonder if this is another difference between ACCESS and the Adobe RM engines? You're seeing success with global KePub styling but ibu is failing with per-ePub CSS. Or maybe it would be the same if you applied the CSS directly to a KePub instead of globally.

On my Aura, when I apply line-heights in the css stylesheet in an .epub file, the line spacing slider no longer seems to have an effect.

Regards,
David

[PeterT]

Originally Posted by ibu

May be we can prove that together with a reference valid epub document without any embedded css?
Does anyone know a source of such an epub?

Would this do?

[DNSB]

Originally Posted by ibu

What does that mean exactly please?
Where does the scala begins and where does it end? (1 to 4?)
Is it equal to the CSS value of line-height?

The scale starts at 1.3 which is the minimum (recommended seems to be 1.2 or 1.3) and ends at 3. This is looking at the Kobo eReader.conf file with the line spacing slider fully left and fully right.

Originally Posted by ibu

Hhmm. That different here as my few experiments showed me.

May be we can prove that together with a reference valid epub document without any embedded css?
Does anyone know a source of such an epub?

I found that interesting as well. I've attached two screenshots, one with the line spacing slider full right, the other with it full left. Just noticed that the Aa control panel does not show in the screen shot as I took two others to show the slider position. So now I have 4 identical screen shots.

The kepub-book.css file I used for this test had the following contents:

body {
   -webkit-hyphens: auto !important;
   line-height: 1.0 !important;
   widows:  0 !important;
   orphans:  0 !important;
   margin: 0 !important;
   padding: 0 !important;
   }
div {
   font-size: 1em !important;
   line-height: 1.0; !important;
   margin-bottom: 0.2em !important;
   padding: 0 !important;
   }
p {
   font-size: 1em !important;
   line-height: 1.0; !important;
   margin-bottom: 0.2em !important;
   padding: 0 !important;
   }

Regards,
David

[DNSB]

Originally Posted by DNSB

I found that interesting as well. I've attached two screenshots, one with the line spacing slider full right, the other with it full left. Just noticed that the Aa control panel does not show in the screen shot as I took two others to show the slider position. So now I have 4 identical screen shots.

I've found the cause for the size slider now having any effect. Opening the kepub files with 7Zip, there is a folder called css with a kobo-android.css file. This file is filled with various css directives, most with !important.

Removing that file allowed the font size slider to work. Unfortunately, it also ended each page on a paragraph which gave an imposing amount of blank space.

Regards,
David

[davidfor]

Originally Posted by ibu

What does that mean exactly please?
Where does the scala begins and where does it end? (1 to 4?)
Is it equal to the CSS value of line-height?

The line spacings the slider can set are: 1.3, 1.35, 1.4, 1.6, 1.775, 1.9, 2, 2.2, 3. As far as I can tell, this is the same as having "line-height=x" in the CSS.

And for completeness...

The font size are: 12, 14, 16, 17, 18, 19, 20, 21, 22, 24, 25, 26, 28, 32, 36, 40, 44, 46, 48, 50, 52, 54, 56, 58

The margins run from 0 to 16 in steps of 2.

These values are stored in the configuration file. They are also stored in the database for each book when you change the settings. If you remove the settings from the configuration file, the defaults will be used for the next book.

If you edit the configuration file, you can use any value in the above ranges. So you can set a font size of 23. Values above the range seem to work. Below the range there seems to be limits. My testing showed that the minimum line spacing is 1.225.

[ibu]

Originally Posted by PeterT

Would this do?

Yes, it would. Thanks

May be you like to add a TOC, metadata and a cover.jpg (not a cover.xhtml) into that document and reupload it. It is nice to have complete reference document for testings in the forum.
If you have an EPUB3 editor, you can may be clone the document as a valid EPUP3.

Another very helpful reference document would be a Kepub file with and a second without kobo-android.css file"

"speaking names" could be:

valid-minimalistic-epub2-no-styles.epub
valid-minimalistic-epub3-no-styles.epub
valid-minimalistic-kepub-with-kobo-android-css.kepub.epub
valid-minimalistic-kepub-without-kobo-android-css.kepub.epub


Of course: just a suggestion

@davidfor
Thanks for these complete listings!

[ibu]

Originally Posted by DNSB

I've found the cause for the size slider now having any effect. Opening the kepub files with 7Zip, there is a folder called css with a kobo-android.css file. This file is filled with various css directives, most with !important.

Removing that file allowed the font size slider to work. Unfortunately, it also ended each page on a paragraph which gave an imposing amount of blank space.

Very interesting, thanks!

That leads into the wish:

We need a hack, that allows a global style file for epubs, and not for just for kepubs.

Kepubs add to much stuff, which is a new area out of our control.

Until we have such a hack, may Joel can spent us an option, which cleans kepubs of the kobo-android.css automatically.

Internetbrowser use a so called browser style sheet. It contains rules for every element of the html specification. rules without !important of course.
It is the "first level" in the CSS cascade.

May be we can get access to Kobos "ereader style sheet" somewhere in the depth of the file system?

[ibu]

Originally Posted by jgoguen

Well, there we have it. Although like I said, the reader values actually must override the CSS for it to work in the way people expect. You could get around it by removing the reading settings and then never make any settings changes on the device

Never make changes to the font-size is - sadly - not realistic.
Because you have bad designed epubs where you have help yourself with manually changing the font-size.

Kobo lacks a simple "reset button".

"Disable all Kobo reading settings for the open book"

"Disable all Kobo reading settings for all books"

Unfortunately there's no value "inherit" for "Kobo ereader.conf" fields.

But may we find ways for a better and more complete control of the reading design of kepubs by disabling kobo-android.css file automatically.

Please see my other post, too.

[jgoguen]

Originally Posted by ibu

Until we have such a hack, may Joel can spent us an option, which cleans kepubs of the kobo-android.css automatically.

I'm not sure I like the idea of removing the CSS file entirely, that may remove all book styling. I may consider a "Replace Kobo Styles" option though. Submit a feature request so I don't forget, life is soon going to be quite hectic and I have a memory like a sieve

[DNSB]

Originally Posted by ibu

Until we have such a hack, may Joel can spent us an option, which cleans kepubs of the kobo-android.css automatically.

Originally Posted by jgoguen

I'm not sure I like the idea of removing the CSS file entirely, that may remove all book styling. I may consider a "Replace Kobo Styles" option though. Submit a feature request so I don't forget, life is soon going to be quite hectic and I have a memory like a sieve

I'd suspect the only place we are going to find the kobo-android.css stylesheet is in ebooks downloaded from Kobo's site in their kepub format. So far my experiments in removing/modifying the file have had some very odd results and caused me to spend quite a bit of time perusing the differences between epub3 and epub2 courtesy of the idpf.org website (http://www.idpf.org/epub/30/spec/epub30-changes.html documentation.

So far all 9 of the kobo-android.css stylesheets I've run into have not been encrypted. I don't know is this is a limitation of Kobo's DRM scheme or a decision on their part to allow modifying css stylesheets without having to decrypt and re-encrypt the files. The expletive deleted Adobe page-template.xpgt files are encrypted though removing them seems to have had minimal noticeable effects.

Regards,
David

[ibu]

Originally Posted by jgoguen

I'm not sure I like the idea of removing the CSS file entirely, that may remove all book styling. I may consider a "Replace Kobo Styles" option though. Submit a feature request so I don't forget, life is soon going to be quite hectic and I have a memory like a sieve

Thanks for thinking about my suggestion.
I will submit a feature request as soon I finished further test around the complex topic "getting full control over all involved css in the chain".

[ibu]

Originally Posted by DNSB

I'd suspect the only place we are going to find the kobo-android.css stylesheet is in ebooks downloaded from Kobo's site in their kepub format.

I've never bought a book from the Kobo shop. And indeed, no one of my epubs I exported with the Plugin KoboExtended as a Kepub, contains a "kobo-android.css".

[jgoguen]

That's because I don't create that file. I add "kobo.js" only if you have a reference.kepub.epub, which probably (but not definitely) does have kobo-android.css. And non-Kobo books would likely not have Kobo files unless they go through my plugin.