Thread: i Loathe ePub...
View Single Post
Old 09-27-2017, 08:54 AM   #56
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by jackie_w View Post
I think the kobostylehacks CSS contained in the <head> section of each (Kobo bought) kepub HTML file has an effect on the look and feel in a standard epub rendering app, particularly the red bit:
Code:
<style xmlns="http://www.w3.org/1999/xhtml" type="text/css" id="kobostylehacks">
  div#book-inner p, div#book-inner div {
      font-size: 1em;
  }
  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>
As already stated Modify Epub can remove this to restore the main CSS file's "style intent".
Of course it does. And that was my point. It is just normal code and removing it will mean the renderer will do something different. Which is exactly what I would expect. But, it isn't "kepub code", just code Kobo wants as standard. And plenty of publishers put their own standard code in to achieve some common affect. And a DIV wrapping the text in a chapter is pretty common.
davidfor is offline   Reply With Quote