Translation of this answer
7-bit ASCII?
If you suddenly turned out to be in 1963, and just want to use 7-bit ASCII printable characters, then all you need to do is delete all the characters in the range of codes 0-31 and 127-255:
$string = preg_replace('/[\x00-\x1F\x7F-\xFF]/', '', $string);
8-bit extended ASCII?
In 1963, you didn’t like it and moved to the eighties and encountered 8-bit ASCII, in which the characters 128-255 are normal, displayed, characters. Then you just need to slightly adjust the replacement string and delete the characters 0-31 and 127:
$string = preg_replace('/[\x00-\x1F\x7F]/', '', $string);
UTF-8?
Welcome to the 21st Century! If your string is a UTF-8 string, then you will have to use the \u modifier :
$string = preg_replace('/[\x00-\x1F\x7F]/u', '', $string);
You simply delete the characters 0-31 and 127. This construction will work for both UTF-8 and 8-bit ASCII, since the second is a subset of the first and they both have the same ranges of control characters . Frankly, such a construction will work without /u , but it will make your life easier if you need to delete any other characters ...
If you are dealing in Unicode, then there are a lot of non-printable characters in it , but let's consider one most frequently used one: NO-BREAK SPACE (U + 00A0)
In the UTF-8 string, it can be represented as 0xC2A0 . Accordingly, you will need to search and delete this sequence of characters, but if you used the /u modifier, you can simply specify \xA0 :
$string = preg_replace('/[\x00-\x1F\x7F\xA0]/u', '', $string);
Bonus: what if str_replace?
preg_replace is extremely efficient, but if you need to process a large amount of text, it will be more efficient to use str_replace with an indication of the character array:
//задаем массив, который будем использовать во всех своих операциях замены $badchar=array( // Управляющие символы chr(0), chr(1), chr(2), chr(3), chr(4), chr(5), chr(6), chr(7), chr(8), chr(9), chr(10), chr(11), chr(12), chr(13), chr(14), chr(15), chr(16), chr(17), chr(18), chr(19), chr(20), chr(21), chr(22), chr(23), chr(24), chr(25), chr(26), chr(27), chr(28), chr(29), chr(30), chr(31), // Непечатные символы chr(127) ); //Удаляем нежелательные символы $str2 = str_replace($badchar, '', $str);
Intuitively, it seems that this approach will work much faster, but let's do the tests. Let's create a set of test strings of various lengths and contents and check the speed of work (PHP 7.0.12 was used):
2 chars str_replace 5.3439ms preg_replace 2.9919ms preg_replace is 44.01% faster 4 chars str_replace 6.0701ms preg_replace 1.4119ms preg_replace is 76.74% faster 8 chars str_replace 5.8119ms preg_replace 2.0721ms preg_replace is 64.35% faster 16 chars str_replace 6.0401ms preg_replace 2.1980ms preg_replace is 63.61% faster 32 chars str_replace 6.0320ms preg_replace 2.6770ms preg_replace is 55.62% faster 64 chars str_replace 7.4198ms preg_replace 4.4160ms preg_replace is 40.48% faster 128 chars str_replace 12.7239ms preg_replace 7.5412ms preg_replace is 40.73% faster 256 chars str_replace 19.8820ms preg_replace 17.1330ms preg_replace is 13.83% faster 512 chars str_replace 34.3399ms preg_replace 34.0221ms preg_replace is 0.93% faster 1024 chars str_replace 57.1141ms preg_replace 67.0300ms str_replace is 14.79% faster 2048 chars str_replace 94.7111ms preg_replace 123.3189ms str_replace is 23.20% faster 4096 chars str_replace 227.7029ms preg_replace 258.3771ms str_replace is 11.87% faster 8192 chars str_replace 506.3410ms preg_replace 555.6269ms str_replace is 8.87% faster 16384 chars str_replace 1116.8811ms preg_replace 1098.0589ms preg_replace is 1.69% faster 32768 chars str_replace 2299.3128ms preg_replace 2222.8632ms preg_replace is 3.32% faster
Measurements were made for 10,000 iterations. It is very interesting to look at the relative differences. For lines up to 512 characters, preg_replace wins by a wide margin. In the range of 1-8kb the difference is leveled.
An interesting result, isn't it? But in any case, you should not entirely rely on my tests, since everything can be exactly the opposite on your specific data.