mb_str_replace()... is slow. any alternatives?

php multibyte
onassar picture onassar · Aug 16, 2010 · Viewed 30.5k times · Source

I want to make sure some string replacement's I'm running are multi byte safe. I've found a few mb_str_replace functions around the net but they're slow. I'm talking 20% increase after passing maybe 500-900 bytes through it.

Any recommendations? I'm thinking about using preg_replace as it's native and compiled in so it might be faster. Any thoughts would be appreciated.

Answer

Áxel Costas Pena picture Áxel Costas Pena · Jan 14, 2013

As said there, str_replace is safe to use in utf-8 contexts, as long as all parameters are utf-8 valid, because it won't be any ambiguous match between both multibyte encoded strings. If you check the validity of your input, then you have no need to look for a different function.

Related questions

Issue with utf-8 encoding using PHP + MySQL

I moved data from MySQL 4 (they were originally set to latin2 encoding) to MySQL 5 and set encoding to utf-8. It looks good in phpMyAdmin, and utf-8 is okay. However there are question marks instead of some characters on website! The …

Read More
str_replace() on multibyte strings dangerous?

Given certain multibyte character sets, am I correct in assuming that the following doesn't do what it was intended to do? $string = str_replace('"', '\\"', $string); In particular, if the input was in a character set that …

Read More
Multibyte trim in PHP?

Apparently there's no mb_trim in the mb_* family, so I'm trying to implement one for my own. I recently found this regex in a comment in php.net: /(^\s+)|(\s+$)/u So, I'd implement it in the following way: …

Read More