p. Localization is becoming more and more important for web designers and developers. It’s coming to a web site near you soon and you need to know how to do it and do it fast. And it isn’t only about swapping strings that you understand with ones you don’t, it is about doing it quickly and smoothly to give your site a global image.
p. “Pablo Hoch”:http://pablohoch.de/ has done a little research into 3 methods of implementing localization using PHP and their relative speed impacts on your site. He shares his research with us in his blog entry “Benchmarking PHP Localization – Is gettext fast enough?”:http://mel.melaxis.com/devblog/. The obligatory pull-quote says:
bq. I wrote a version using the “gettext PHP extension”:http://us2.php.net/gettext (“gettext Ext.”), one using “PHP-gettext”:http://savannah.nongnu.org/projects/php-gettext/ (“gettext PHP”, a gettext implementation written in pure PHP) and a version that does not use gettext at all, instead it uses an array that contains all the translations (“String ID”).
p. Even though he used “Debian”:http://www.debian.org/ instead of “Gentoo”:http://www.gentoo.org as the testing platform, I believe his results are still valid. Since I don’t want to spoil it for you, I won’t tell you what method is the fastest, you’ll have to click the link to find out.