It is highly likely that this character is associated with UTF-8 encoding problems. Joel article Absolute minimum Every software developer Absolutely, should know positively about Unicode and character sets (no excuses!) , Of course, it is recommended to read in this case.
Filtering these characters before sending them to the database is, of course, the wrong thing.
In the case you mention, you are probably dealing with the character U + 00A0, which is the Unicode character for non-distribution. Bit chart for this symbol:
1010 0000
After UTF-8 encoding, where the encoded bytes look like
110x xxxx 10xx xxxx
where 'x' represents the bit of the Unicode character value, so U + 00A0 is encoded as:
1100 0010 1010 0000
which is equal to 0xC2 0xA0. Coincidentally, the second character is the same byte value as the original character you encoded (U + 00A0), while the first character is the view you see.
source share