View Single Post
Old 09-15-2019, 10:08 AM   #5
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,619
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I was going to say that you could also use the \x{0000} syntax in the F&R fields for finding unicode codepoints. The one for the non-breaking space would be \x{00a0} or (\x00a0 or just \xa0), but it appears we've introduced some sort of bug into F&R where \xa0 only matches non-breaking space characters in multiples of two??? It used to work fine, so I'll have to look into it. Inserting an nbsp character into the F&R fields with a Clip's keyboard shortcut works just fine in the meantime, though.
DiapDealer is offline   Reply With Quote