View Single Post
Old 12-23-2014, 01:37 PM   #5
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,926
Karma: 146918083
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by jackie_w View Post
As long as you've also taken steps (as per icallaci's link re: kobo_extra.css) to point the Kobo at a sideloaded monospace font the answer should be 'yes'. Similarly, this 2nd option should also work:
Code:
<p class="para-wlf"><span class="monospace">This is the paragraph.</span></p>
The root of the problem with the mono class being defined on the <p> tag is that the fw internal css override (userStyle.css) for the Adobe renderer contains this css code
Code:
body, p {font-family: -ua-default !important;}
where you can see that the <p> tag is being forcibly overridden. Consequently, a 3rd option is to use the Patcher to change it to
Code:
body    {font-family: -ua-default !important;}
For me, this is much less effort than changing the html in every epub, but whether it's a good solution for you will depend on how/where you allow font-family code in your epub css. For many people it may make things worse, but I'm happy to post the extra Patch for fw 3.12 if you think it will help.
Please yes, post the patch. I would like to give it a try. Thank you for this.
JSWolf is offline   Reply With Quote