<?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: How to Internationalize Your PHP Site</title>
	<atom:link href="http://waynepan.com/2007/12/17/how-to-internationalize-your-php-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://waynepan.com/2007/12/17/how-to-internationalize-your-php-site/</link>
	<description>tech &#124; js &#124; ui &#124; ajax &#124; life &#124; mobile</description>
	<pubDate>Sat, 22 Nov 2008 21:38:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Wayne</title>
		<link>http://waynepan.com/2007/12/17/how-to-internationalize-your-php-site/#comment-206</link>
		<dc:creator>Wayne</dc:creator>
		<pubDate>Fri, 13 Jun 2008 18:59:34 +0000</pubDate>
		<guid isPermaLink="false">http://waynepan.com/2007/12/17/how-to-internationalize-your-php-site/#comment-206</guid>
		<description>@Nicolas, you can use -x option for xgettext to exclude strings in existing po files. Also I find the msguniq command very useful for removing duplicates from an existing po file.

The following command will find and run xgettext on all php files in &lt;source_dir&gt; excluding strings in &lt;existing_po_file&gt;

find &lt;source_dir&gt;/. -iname "*.php" -exec echo {} \; -exec xgettext --no-wrap -j -x &lt;existing_po_file&gt; -L PHP {} \;&lt;/existing_po_file&gt;&lt;/source_dir&gt;&lt;/existing_po_file&gt;&lt;/source_dir&gt;</description>
		<content:encoded><![CDATA[<p>@Nicolas, you can use -x option for xgettext to exclude strings in existing po files. Also I find the msguniq command very useful for removing duplicates from an existing po file.</p>
<p>The following command will find and run xgettext on all php files in <source_dir> excluding strings in <existing_po_file></p>
<p>find <source_dir>/. -iname &#8220;*.php&#8221; -exec echo {} \; -exec xgettext &#8211;no-wrap -j -x <existing_po_file> -L PHP {} \;</existing_po_file></source_dir></existing_po_file></source_dir></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas</title>
		<link>http://waynepan.com/2007/12/17/how-to-internationalize-your-php-site/#comment-205</link>
		<dc:creator>Nicolas</dc:creator>
		<pubDate>Fri, 13 Jun 2008 13:46:25 +0000</pubDate>
		<guid isPermaLink="false">http://waynepan.com/2007/12/17/how-to-internationalize-your-php-site/#comment-205</guid>
		<description>Hello Wayne,

I just find your blog and this post, while looking for best practices and advices about the usage of gettext to manage string translations.

I'm working on a website that's supposed to be available in several languages, and I'm thinking about using gettext. But so far the .po files management seems to be annoying. Especially after the first xgettext use, I mean when you already have a .po file full of translations, and just want to detect the new ones (that appeared since the last xgettext use). Well perhaps it's just that I don't get it &#62;&#60;

I was wondering if you have any advice on this topic ? 

Thanks by advance :)

Nicolas</description>
		<content:encoded><![CDATA[<p>Hello Wayne,</p>
<p>I just find your blog and this post, while looking for best practices and advices about the usage of gettext to manage string translations.</p>
<p>I&#8217;m working on a website that&#8217;s supposed to be available in several languages, and I&#8217;m thinking about using gettext. But so far the .po files management seems to be annoying. Especially after the first xgettext use, I mean when you already have a .po file full of translations, and just want to detect the new ones (that appeared since the last xgettext use). Well perhaps it&#8217;s just that I don&#8217;t get it &gt;&lt;</p>
<p>I was wondering if you have any advice on this topic ? </p>
<p>Thanks by advance <img src='http://waynepan.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Nicolas</p>
]]></content:encoded>
	</item>
</channel>
</rss>
