<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Benchmarking PHP Localization - Is gettext fast enough?</title>
	<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/</link>
	<description></description>
	<pubDate>Sat, 17 May 2008 15:16:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Kruxik</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-7168</link>
		<dc:creator>Kruxik</dc:creator>
		<pubDate>Fri, 10 Aug 2007 14:01:12 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-7168</guid>
		<description>If you use mod_php (not CGI) and have problem with cached dictionary after its update there is one solution which doesn't need webserver restart. You can create the domain name dynamicly and change it whenever you change the dictionary.
Example: standard name (domain) of the dictionary is messages.mo - means domain is "messages". You can rename the file to "messages1.mo", and tell PHP to change domain from "messages" to "messages1".

This solution is 100% functional (we use it for our CMS gettext editor).</description>
		<content:encoded><![CDATA[<p>If you use mod_php (not CGI) and have problem with cached dictionary after its update there is one solution which doesn&#8217;t need webserver restart. You can create the domain name dynamicly and change it whenever you change the dictionary.<br />
Example: standard name (domain) of the dictionary is messages.mo - means domain is &#8220;messages&#8221;. You can rename the file to &#8220;messages1.mo&#8221;, and tell PHP to change domain from &#8220;messages&#8221; to &#8220;messages1&#8243;.</p>
<p>This solution is 100% functional (we use it for our CMS gettext editor).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quellen zu Internationalisierung und Lokalisierung &#187; contactsheet.de</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-3292</link>
		<dc:creator>Quellen zu Internationalisierung und Lokalisierung &#187; contactsheet.de</dc:creator>
		<pubDate>Thu, 03 May 2007 07:52:43 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-3292</guid>
		<description>[...] Benchmarking PHP Localization - Is gettext fast enough? in einem inzwischen etwas älteren Artikel nimmt Pablo Hoch drei verschiedene Techniken unter die Lupe: native PHP-Arrays, PHP-gettext sowie die Kombination aus PHP-gettext-Extension und locale. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Benchmarking PHP Localization - Is gettext fast enough? in einem inzwischen etwas älteren Artikel nimmt Pablo Hoch drei verschiedene Techniken unter die Lupe: native PHP-Arrays, PHP-gettext sowie die Kombination aus PHP-gettext-Extension und locale. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for Jun 19-26 at 59ideas</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-337</link>
		<dc:creator>links for Jun 19-26 at 59ideas</dc:creator>
		<pubDate>Tue, 27 Jun 2006 18:00:51 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-337</guid>
		<description>[...] Benchmarking PHP Localization - Is gettext fast enough? » Pablo’s Development Blog (tags: php i18n) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Benchmarking PHP Localization - Is gettext fast enough? » Pablo’s Development Blog (tags: php i18n) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2006-06-26 at 59ideas</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-329</link>
		<dc:creator>links for 2006-06-26 at 59ideas</dc:creator>
		<pubDate>Mon, 26 Jun 2006 16:19:41 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-329</guid>
		<description>[...] Benchmarking PHP Localization - Is gettext fast enough? » Pablo’s Development Blog (tags: php i18n) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Benchmarking PHP Localization - Is gettext fast enough? » Pablo’s Development Blog (tags: php i18n) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Schneider</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-159</link>
		<dc:creator>Jan Schneider</dc:creator>
		<pubDate>Mon, 08 May 2006 23:09:26 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-159</guid>
		<description>On most shared hosts a web server restart is not required because they often use either CGI PHP SAPIs. These don't cache the locale (because it's actually the web server process, not PHP that is doing the caching), so locale updates work instantly.</description>
		<content:encoded><![CDATA[<p>On most shared hosts a web server restart is not required because they often use either CGI PHP SAPIs. These don&#8217;t cache the locale (because it&#8217;s actually the web server process, not PHP that is doing the caching), so locale updates work instantly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hm-ohj2006 : blogi &#187; Blog Archive &#187; PALAUTUS: Gettextillä Railsia lokalisoimaan.</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-147</link>
		<dc:creator>Hm-ohj2006 : blogi &#187; Blog Archive &#187; PALAUTUS: Gettextillä Railsia lokalisoimaan.</dc:creator>
		<pubDate>Fri, 28 Apr 2006 14:36:49 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-147</guid>
		<description>[...] Gettext-tuki löytyy myös PHPstä, mutta Railsissa sen eteen on jo tehty valmiiksi töitä. Näin käyttöönotto on suoraviivaisempaa ja muutamalla lisäyksellä (mm. Rakefilen lisätehtävätä) todella vaivatonta. Lisäksi tehokkuusmielessä on Gettextin oikeanlainen käyttö varsin nopeaa. PHP:lle sitä onkin testattu ainakin yhden tapauksen verran ( [1] ). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Gettext-tuki löytyy myös PHPstä, mutta Railsissa sen eteen on jo tehty valmiiksi töitä. Näin käyttöönotto on suoraviivaisempaa ja muutamalla lisäyksellä (mm. Rakefilen lisätehtävätä) todella vaivatonta. Lisäksi tehokkuusmielessä on Gettextin oikeanlainen käyttö varsin nopeaa. PHP:lle sitä onkin testattu ainakin yhden tapauksen verran ( [1] ). [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zhitao Ma</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-95</link>
		<dc:creator>Zhitao Ma</dc:creator>
		<pubDate>Tue, 18 Apr 2006 01:12:53 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-95</guid>
		<description>My test results are in the following,

                  Requests per Second
gettext-ext           395.63
gettext-php          221.12
stringids               568.66

I tested them on a Windows XP SP2 computer with the Apache 2.0.55 and PHP 5.1.3-dev. It seems that the results are quite different on Windows and Debian.</description>
		<content:encoded><![CDATA[<p>My test results are in the following,</p>
<p>                  Requests per Second<br />
gettext-ext           395.63<br />
gettext-php          221.12<br />
stringids               568.66</p>
<p>I tested them on a Windows XP SP2 computer with the Apache 2.0.55 and PHP 5.1.3-dev. It seems that the results are quite different on Windows and Debian.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-91</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 17 Apr 2006 05:53:16 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-91</guid>
		<description>We have used both methods and find gettext not only easier in the long run for updates, but faster also.</description>
		<content:encoded><![CDATA[<p>We have used both methods and find gettext not only easier in the long run for updates, but faster also.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Thomas</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-90</link>
		<dc:creator>Richard Thomas</dc:creator>
		<pubDate>Sun, 16 Apr 2006 02:04:59 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-90</guid>
		<description>I am also working with gettext and have managed to combined it with savant temlate system.

Using a savant plugin I can translate on the fly, or with a script pretranslate all the templates so gettext doesnt need to be used on the live site

http://www.cyberlot.net/Savantgettext</description>
		<content:encoded><![CDATA[<p>I am also working with gettext and have managed to combined it with savant temlate system.</p>
<p>Using a savant plugin I can translate on the fly, or with a script pretranslate all the templates so gettext doesnt need to be used on the live site</p>
<p><a href="http://www.cyberlot.net/Savantgettext" rel="nofollow">http://www.cyberlot.net/Savantgettext</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Plush</title>
		<link>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-86</link>
		<dc:creator>Jim Plush</dc:creator>
		<pubDate>Thu, 13 Apr 2006 22:54:33 +0000</pubDate>
		<guid>http://mel.melaxis.com/devblog/2006/04/10/benchmarking-php-localization-is-gettext-fast-enough/#comment-86</guid>
		<description>I also did some benchmark tests when my last company needed an i18n ready site. might be worth a read

http://www.litfuel.net/plush/?postid=84</description>
		<content:encoded><![CDATA[<p>I also did some benchmark tests when my last company needed an i18n ready site. might be worth a read</p>
<p><a href="http://www.litfuel.net/plush/?postid=84" rel="nofollow">http://www.litfuel.net/plush/?postid=84</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
