View Single Post
Old 09-03-2022, 11:30 AM   #40
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by Tex2002ans View Post
Any reason why Kobo still hasn't included a monospace font? Hasn't this bug/complaint been known about for years and years?
I don't know but some thoughts.

Short answer:
Cost to license one? Not enough demand to include one? Not enough complaints about its absence? Take your pick

Longer answer:
Kobo probably think they've already 'fixed it' for those who care enough, i.e. use epub with a sideloaded Courier font. All they needed to do was to fix one of the pre-existing settings in the Adobe-supplied epub reading app. Effort required minimal - nevertheless appreciated by some of us.

Fixing it for kepub is another matter entirely. If the user was willing to leave their Kobo selected font permanently at 'Publisher default' then there would be a chance that font-family:monospace; could be directed to use a default mono font, if it existed, in the same way that they currently direct font-family:serif; and font-family:sans-serif; to Georgia and 'Avenir Next' respectively.

However, as soon as the user selects a custom font to display main body text in their kepubs then the sledgehammer kepub override CSS for font-family comes into play, namely
* { font-family: %1 !important;}
Every one of the kepub's CSS styles containing the font-family property will be overridden, i.e. the whole book will be displayed in the single user-selected font, which may, or may not, be what the user really wanted.

Kobo *could* make the kepub font-family override CSS less aggressive (there are kobopatches which can do this). It would almost certainly lead to more complaints for their Help Desk when the less aggressive font-family override failed to override in the way the user expected because of the badly-designed CSS found in so many retail books.

In summary, for people who care enough and are prepared to put in the effort there are workarounds and Kobo probably know that. For everyone else they have their fallback response as explicitly stated in their Kobo EPUB Guidelines
Quote:
Content creators are advised against referencing fonts in the CSS that are not embedded in the ePub.
jackie_w is offline   Reply With Quote