This is already on the roadmap as a different suggestion here: http://roadmap.cintanotes.com/topic/15284-saved-predefined-searches/

Thanks for the report!
This happens because of the U+FEFF character occurring in the middle of that string. Here is an exerpt from the Unicode FAQ:

Q: What should I do with U+FEFF in the middle of a file?

A: In the absence of a protocol supporting its use as a BOM and when not at the beginning of a text stream, U+FEFF should normally not occur. For backwards compatibility it should be treated as ZERO WIDTH NON-BREAKING SPACE (ZWNBSP), and is then part of the content of the file or string. The use of U+2060 WORD JOINER is strongly preferred over ZWNBSP for expressing word joining semantics since it cannot be confused with a BOM. When designing a markup language or data protocol, the use of U+FEFF can be restricted to that of Byte Order Mark. In that case, any U+FEFF occurring in the middle of a file can be treated as an unsupported character. [AF]

As you see, this is really a rare and exceptional case and thus I consider fixing unnecessary at the moment. Just delete the offending character, and the font becomes normal.

Closing this because the bug was not reproduced and there hasn't been second upvote in 3 months