<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Vigilance 1.45 Released</title>
	<atom:link href="http://thethemefoundry.com/blog/vigilance-145-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://thethemefoundry.com/blog/vigilance-145-released/</link>
	<description>Handcrafted WordPress themes &#38; professional support</description>
	<lastBuildDate>Mon, 06 Feb 2012 15:51:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Drew Strojny</title>
		<link>http://thethemefoundry.com/blog/vigilance-145-released/#comment-559</link>
		<dc:creator>Drew Strojny</dc:creator>
		<pubDate>Thu, 14 Jan 2010 22:18:55 +0000</pubDate>
		<guid isPermaLink="false">http://themes.jestro.com/blog/?p=1207#comment-559</guid>
		<description>OK,

I installed the localization plugin and everything worked well for me. After creating the /languages folder in either the parent or child theme I was able to test translating the .po files and I saw no errors. Here is where I think the problems are according to both your comments:

1. The theme may be missing text that hasn&#039;t been marked for translation.

2. Some of the strings use an improper textdomain.

3. Some of the strings may need to be more complete.

It would be great if you  could email me specific instances where these three problems exist, along with fixes for anything that falls into the third category.  If I am missing something else please let me know. Either way, let&#039;s carry this on over email. I can get you guys setup on our bug tracking software so you can report specific problems.

Thanks!</description>
		<content:encoded><![CDATA[<p>OK,</p>
<p>I installed the localization plugin and everything worked well for me. After creating the /languages folder in either the parent or child theme I was able to test translating the .po files and I saw no errors. Here is where I think the problems are according to both your comments:</p>
<p>1. The theme may be missing text that hasn&#8217;t been marked for translation.</p>
<p>2. Some of the strings use an improper textdomain.</p>
<p>3. Some of the strings may need to be more complete.</p>
<p>It would be great if you  could email me specific instances where these three problems exist, along with fixes for anything that falls into the third category.  If I am missing something else please let me know. Either way, let&#8217;s carry this on over email. I can get you guys setup on our bug tracking software so you can report specific problems.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drew Strojny</title>
		<link>http://thethemefoundry.com/blog/vigilance-145-released/#comment-517</link>
		<dc:creator>Drew Strojny</dc:creator>
		<pubDate>Tue, 29 Dec 2009 15:03:18 +0000</pubDate>
		<guid isPermaLink="false">http://themes.jestro.com/blog/?p=1207#comment-517</guid>
		<description>Thanks Leonardo, I appreciate the feedback.

I am planning on looking at this soon with the localization plugin nv1962 mentioned. If there are any specific cases you know of please send me an email (themes {at} jestro.com) detailing what needs to be changed/fixed.</description>
		<content:encoded><![CDATA[<p>Thanks Leonardo, I appreciate the feedback.</p>
<p>I am planning on looking at this soon with the localization plugin nv1962 mentioned. If there are any specific cases you know of please send me an email (themes {at} jestro.com) detailing what needs to be changed/fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leonardo Fontenelle</title>
		<link>http://thethemefoundry.com/blog/vigilance-145-released/#comment-514</link>
		<dc:creator>Leonardo Fontenelle</dc:creator>
		<pubDate>Mon, 28 Dec 2009 22:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://themes.jestro.com/blog/?p=1207#comment-514</guid>
		<description>I&#039;m still waiting for the internationalization improvements to start translatoring Vigilance and maybe other themes... As nv1962 points out, the messages that gettext extracts from the themes need to be more complete (not sentence fragments) for the translators to do a decent job.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still waiting for the internationalization improvements to start translatoring Vigilance and maybe other themes&#8230; As nv1962 points out, the messages that gettext extracts from the themes need to be more complete (not sentence fragments) for the translators to do a decent job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drew Strojny</title>
		<link>http://thethemefoundry.com/blog/vigilance-145-released/#comment-472</link>
		<dc:creator>Drew Strojny</dc:creator>
		<pubDate>Mon, 21 Dec 2009 06:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://themes.jestro.com/blog/?p=1207#comment-472</guid>
		<description>Thanks for pointing this out! I will take a look ASAP and see if I can fix it up.</description>
		<content:encoded><![CDATA[<p>Thanks for pointing this out! I will take a look ASAP and see if I can fix it up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nv1962</title>
		<link>http://thethemefoundry.com/blog/vigilance-145-released/#comment-471</link>
		<dc:creator>nv1962</dc:creator>
		<pubDate>Mon, 21 Dec 2009 00:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://themes.jestro.com/blog/?p=1207#comment-471</guid>
		<description>I suggest installing on a test server with Vigilance the &lt;a href=&quot;http://www.code-styling.de/english/development/wordpress-plugin-codestyling-localization-en&quot; rel=&quot;nofollow&quot;&gt;Codestyling Localization&lt;/a&gt; plugin, to find localization issues due to improper formatting / wrapping of localized strings. As I&#039;ve also &lt;a href=&quot;http://wordpress.org/support/topic/340947&quot; rel=&quot;nofollow&quot;&gt;mentioned here&lt;/a&gt;, there are several strings that cause problems either using or creating localization files (the .po and .mo files) and using that plugin will track that type of problems down for you. Not to mention that it&#039;s a fantastic tool to create localizations, but that&#039;s past the scope of the Vigilance development proper.</description>
		<content:encoded><![CDATA[<p>I suggest installing on a test server with Vigilance the <a href="http://www.code-styling.de/english/development/wordpress-plugin-codestyling-localization-en" rel="nofollow">Codestyling Localization</a> plugin, to find localization issues due to improper formatting / wrapping of localized strings. As I&#8217;ve also <a href="http://wordpress.org/support/topic/340947" rel="nofollow">mentioned here</a>, there are several strings that cause problems either using or creating localization files (the .po and .mo files) and using that plugin will track that type of problems down for you. Not to mention that it&#8217;s a fantastic tool to create localizations, but that&#8217;s past the scope of the Vigilance development proper.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

