View Single Post
Old 12-12-2019, 01:18 PM   #35
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 dmapr View Post
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?
Yes, to the best of my knowledge, that should do the trick.

It can be <=7 chars, but it needs to be enough so that the device can't get confused if you have fontnames with similar prefixes.
jackie_w is offline   Reply With Quote