[jackie_w]

Originally Posted by JSWolf

If that's not the correct code, what it is?

My earlier post #15 shows the easiest method for standard epubs because you don't need to add any extra @font-faces to each epub to get CSS styles containing font-family:monospace to display in your sideloaded Courier font. The only disadvantage is that you need to go through the one-time font-renaming process if your favourite sideloaded mono font is not already named Courier (internally and externally).

If you want to avoid font-renaming (internal) then you need to add something like the following CSS to every epub that needs it:

@font-face {
  font-family: monospace;
  font-weight: normal;
  font-style: normal;
  src: url("res:///fonts/normal/Dark Courier");
}
@font-face {
  font-family: monospace;
  font-weight: bold;
  font-style: normal;
  src: url("res:///fonts/bold/Dark Courier");
}
@font-face {
  font-family: monospace;
  font-weight: normal;
  font-style: italic;
  src: url("res:///fonts/italic/Dark Courier");
}
@font-face {
  font-family: monospace;
  font-weight: bold;
  font-style: italic;
  src: url("res:///fonts/bolditalic/Dark Courier");
}

replacing the bold red bits with the actual internal font name of your sideloaded monospace font.

There's also the monospace patch in librmsdk.so.1.0.0.yaml. However, this is less useful than it used to be because when customising it you can only change the default value of Courier to a different font name of <= 7-chars. If you're going to have to do internal font-renaming anyway then you may as well just use the method in post #15.