View Single Post
Old 12-12-2019, 01:02 PM   #33
dmapr
Evangelist
dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.dmapr ought to be getting tired of karma fortunes by now.
 
Posts: 469
Karma: 600816
Join Date: Sep 2009
Device: Kobo Aura HD, Kobo Aura One
Quote:
Originally Posted by jackie_w View Post
Yes, if you don't want to use Courier you should be able to use the new Find: strings from fw 4.19 and your old working custom Replace: strings from 4.18. e.g.
Code:
  - FindReplaceString: {Find: "/normal/Courier", Replace: "/normal/Dark"}
  - FindReplaceString: {Find: "/bold/Courier", Replace: "/bold/Dark"}
  - FindReplaceString: {Find: "/italic/Courier", Replace: "/italic/Dark"}
  - FindReplaceString: {Find: "/bolditalic/Courier", Replace: "/bolditalic/Dark"}
If there are a lot of people voicing concern about the removal of the monospace patch then we can consider putting it back in.
Thanks, jackie_w. And it's the same as the old one in the sense that it's doing prefix matching, right? So if my monospace font name is longer than 7 characters I just put the first 7 into the replace string and it'll get picked up?
dmapr is offline   Reply With Quote