Quote:
Originally Posted by enuddleyarbl
I'm not sure if this is the method to embed a monospace font your talking about, but according to this page:
https://www.wezm.net/v2/posts/2022/m...-kobo-ereader/
it doesn't work any more. Unfortunately, the page doesn't give details on why it doesn't work and I haven't found anything else about it.
EDIT: I've not tried any of that. I just ran across the page while I was researching this and am passing it on. |
What Wesley Moore omitted is that the method he documented only ever worked for standard epubs not kepubs.
In addition Kobo's font handling changed a lot in fw 4.32.19501 (April 2022). Since then the rules have changed:
EPUB:
The 4 monospace font files you sideload to the Kobo
/fonts directory must now be named simply and precisely
Courier both internally and externally.
Renaming the external filenames is trivial (e.g. Courier-Regular, etc) but *internal* renaming requires using some kind of font editor (e.g. FontForge or ttfedit). In other words you can no longer get away with sideloading a monospace font whose name begins with
Courier but whose full name is longer, e.g.
Courier PragmataPro Mono to quote his example.
KEPUB:
As far as I can tell, embedding the monospace font is now the *only* method which works.
Prior to fw 4.32 all that was necessary was to include the full name of any sideloaded monospace font in the kepub CSS, e.g.
Code:
.mono {font-family: "Courier PragmataPro Mono", monospace;}
or even just
Code:
.mono {font-family: "Courier PragmataPro Mono";}
ETA: It looks like JSWolf beat me to it
