<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Making Global Translator 0.6 and FireStats Play Nice</title>
	<atom:link href="http://www.j2fi.net/2007/04/06/making-global-translator-06-and-firestats-play-nice/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.j2fi.net/2007/04/06/making-global-translator-06-and-firestats-play-nice/</link>
	<description>Yet Another Gaijin In Japan</description>
	<pubDate>Wed, 19 Nov 2008 23:51:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Jason</title>
		<link>http://www.j2fi.net/2007/04/06/making-global-translator-06-and-firestats-play-nice/#comment-70</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Sun, 08 Apr 2007 01:47:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.j2fi.net/2007/04/06/making-global-translator-06-and-firestats-play-nice/#comment-70</guid>
		<description>Hi Davide, I've tested your update and found that the FireStats link still wants to be sent to either Google or BabelFish.  Luckily, only two lines in the translate function need to be changed:

$url_to_translate = BLOG_HOME . str_replace('//', '/', '/' . preg_replace('(/it/&#124;/ko/&#124;/zh-CN/&#124;/pt/&#124;/en/&#124;/de/&#124;/fr/&#124;/es/&#124;/ja/&#124;/ar/&#124;/ru/&#124;/el/&#124;/nl/&#124;/zh/&#124;/zt/)', '/', $_SERVER['REQUEST_URI']));
$resource = build_translation_url(BASE_LANG, $lang, $url_to_translate);

Once this is done, it'll work just great with FireStats.  I've tested this on WordPress 2.0.4, 2.0.5, 2.0.7, 2.0.10, 2.1 and 2.11 with FireStats 1.1.5 as well as WordPress 2.1 with FireStats 1.1.8.

Aside from these two small changes, your code works flawlessly.  Great work :)</description>
		<content:encoded><![CDATA[<p>Hi Davide, I&#8217;ve tested your update and found that the FireStats link still wants to be sent to either Google or BabelFish.  Luckily, only two lines in the translate function need to be changed:</p>
<p>$url_to_translate = BLOG_HOME . str_replace(&#8217;//&#8217;, &#8216;/&#8217;, &#8216;/&#8217; . preg_replace(&#8217;(/it/|/ko/|/zh-CN/|/pt/|/en/|/de/|/fr/|/es/|/ja/|/ar/|/ru/|/el/|/nl/|/zh/|/zt/)&#8217;, &#8216;/&#8217;, $_SERVER['REQUEST_URI']));<br />
$resource = build_translation_url(BASE_LANG, $lang, $url_to_translate);</p>
<p>Once this is done, it&#8217;ll work just great with FireStats.  I&#8217;ve tested this on WordPress 2.0.4, 2.0.5, 2.0.7, 2.0.10, 2.1 and 2.11 with FireStats 1.1.5 as well as WordPress 2.1 with FireStats 1.1.8.</p>
<p>Aside from these two small changes, your code works flawlessly.  Great work <img src='http://www.j2fi.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davide</title>
		<link>http://www.j2fi.net/2007/04/06/making-global-translator-06-and-firestats-play-nice/#comment-69</link>
		<dc:creator>Davide</dc:creator>
		<pubDate>Sat, 07 Apr 2007 17:10:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.j2fi.net/2007/04/06/making-global-translator-06-and-firestats-play-nice/#comment-69</guid>
		<description>Hi Jason
I appreciate you contribution! I don't use Firestats so at now I'm unable to test it with my plugin.
Last night I've released the 0.6.beta2 version which should fix some issues I've discovered in the link replacement code you're talking about on this post. Could you test it and tell me if it works better also with Firestats ? Thanks!</description>
		<content:encoded><![CDATA[<p>Hi Jason<br />
I appreciate you contribution! I don&#8217;t use Firestats so at now I&#8217;m unable to test it with my plugin.<br />
Last night I&#8217;ve released the 0.6.beta2 version which should fix some issues I&#8217;ve discovered in the link replacement code you&#8217;re talking about on this post. Could you test it and tell me if it works better also with Firestats ? Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason&#8217;s Random Thoughts &#187; Blog Archive &#187; WordPress Global Translator and FireStats</title>
		<link>http://www.j2fi.net/2007/04/06/making-global-translator-06-and-firestats-play-nice/#comment-68</link>
		<dc:creator>Jason&#8217;s Random Thoughts &#187; Blog Archive &#187; WordPress Global Translator and FireStats</dc:creator>
		<pubDate>Sat, 07 Apr 2007 03:05:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.j2fi.net/2007/04/06/making-global-translator-06-and-firestats-play-nice/#comment-68</guid>
		<description>[...]  Update:  For those of you interested in getting Global Translator 0.6 to work with FireStats, go here. [...]</description>
		<content:encoded><![CDATA[<p>[...]  Update:  For those of you interested in getting Global Translator 0.6 to work with FireStats, go here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
