<?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: Protecting text strings from theme upgrades</title>
	<atom:link href="http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades/feed" rel="self" type="application/rss+xml" />
	<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades</link>
	<description>Life, Blogging, and WordPress</description>
	<lastBuildDate>Fri, 10 Feb 2012 12:19:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: </title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-18546</link>
		<dc:creator></dc:creator>
		<pubDate>Tue, 15 Jul 2008 09:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-18546</guid>
		<description>An interesting thing here, is that it opens doors for guys like me, that writes about life in the kitchen and my &quot;well-known&quot; recipes, with a twist of daily stories.

I have tried out every single multilanguage plugin there is, but i cant seem to get any of them to work properly! YET.

With a localized theme it might just be posible and maybe i dont have to post recipes in english elsewhere, but on the &quot;english&quot; site of my blog!-</description>
		<content:encoded><![CDATA[<p>An interesting thing here, is that it opens doors for guys like me, that writes about life in the kitchen and my &#8220;well-known&#8221; recipes, with a twist of daily stories.</p>
<p>I have tried out every single multilanguage plugin there is, but i cant seem to get any of them to work properly! YET.</p>
<p>With a localized theme it might just be posible and maybe i dont have to post recipes in english elsewhere, but on the &#8220;english&#8221; site of my blog!-</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Tadlock</title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-18236</link>
		<dc:creator>Justin Tadlock</dc:creator>
		<pubDate>Sun, 13 Jul 2008 01:20:38 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-18236</guid>
		<description>&lt;strong&gt;J Mehmett&lt;/strong&gt;
Here&#039;s a little something I just found out.  The Default WordPress theme isn&#039;t even localized!  I haven&#039;t looked at that for a while, but I just happened to open it the other day and noticed it.

&lt;strong&gt;gofree&lt;/strong&gt;
The good thing is that you can&#039;t possibly mess up your theme using this method.  If something goes wrong, you only have to worry about one file.  In the long run, it might be worth it to learn PoEdit.

&lt;strong&gt;Ptah Dunbar&lt;/strong&gt;
Now, I&#039;m interested.  That could be a neat way to do it.

Maybe if you could set up a theme options page with all the text strings, it could work.  What would be even neater would be if you could have the options page auto-generate the .mo and .po files.  That way, you wouldn&#039;t have to hack up your theme files getting theme options for every string.</description>
		<content:encoded><![CDATA[<p><strong>J Mehmett</strong><br />
Here&#8217;s a little something I just found out.  The Default WordPress theme isn&#8217;t even localized!  I haven&#8217;t looked at that for a while, but I just happened to open it the other day and noticed it.</p>
<p><strong>gofree</strong><br />
The good thing is that you can&#8217;t possibly mess up your theme using this method.  If something goes wrong, you only have to worry about one file.  In the long run, it might be worth it to learn PoEdit.</p>
<p><strong>Ptah Dunbar</strong><br />
Now, I&#8217;m interested.  That could be a neat way to do it.</p>
<p>Maybe if you could set up a theme options page with all the text strings, it could work.  What would be even neater would be if you could have the options page auto-generate the .mo and .po files.  That way, you wouldn&#8217;t have to hack up your theme files getting theme options for every string.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ptah Dunbar</title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-14798</link>
		<dc:creator>Ptah Dunbar</dc:creator>
		<pubDate>Mon, 23 Jun 2008 02:52:09 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-14798</guid>
		<description>This is a pretty cool idea. But the perfectionist in me makes me want to take out the middle man &quot;poedit&quot; and create an interface via PHP for this. hmm...</description>
		<content:encoded><![CDATA[<p>This is a pretty cool idea. But the perfectionist in me makes me want to take out the middle man &#8220;poedit&#8221; and create an interface via PHP for this. hmm&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress Weekend Resources - June 20, 2008 &#124; Theme Lab</title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-14469</link>
		<dc:creator>WordPress Weekend Resources - June 20, 2008 &#124; Theme Lab</dc:creator>
		<pubDate>Fri, 20 Jun 2008 12:33:07 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-14469</guid>
		<description>[...] Protecting text strings from theme upgrades - This post by Justin Tadlock goes over how to make your themes translatable. I&#8217;ll admit, this is something I do not do with the themes on Theme Lab, but I may start after reading this. [...]</description>
		<content:encoded><![CDATA[<p>[...] Protecting text strings from theme upgrades &#8211; This post by Justin Tadlock goes over how to make your themes translatable. I&#8217;ll admit, this is something I do not do with the themes on Theme Lab, but I may start after reading this. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cool coding tips from around your WordPress community - part 1 &#8212; WP Project</title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-14174</link>
		<dc:creator>Cool coding tips from around your WordPress community - part 1 &#8212; WP Project</dc:creator>
		<pubDate>Thu, 19 Jun 2008 06:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-14174</guid>
		<description>[...] Tadlock talks about theme localization, and reveals how to protect your text strings from theme upgrades. Have you ever wanted to change some text that reads “Continue reading” or “Post written [...]</description>
		<content:encoded><![CDATA[<p>[...] Tadlock talks about theme localization, and reveals how to protect your text strings from theme upgrades. Have you ever wanted to change some text that reads “Continue reading” or “Post written [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gofree</title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-14026</link>
		<dc:creator>gofree</dc:creator>
		<pubDate>Wed, 18 Jun 2008 15:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-14026</guid>
		<description>Edit : I do want to add that it would be more complicated for first-time users of Poedit though.

This is what i am going to back off! I have always wonder how to not destroy my already customized theme, but now it seems a bit more work for a noob like me :(</description>
		<content:encoded><![CDATA[<p>Edit : I do want to add that it would be more complicated for first-time users of Poedit though.</p>
<p>This is what i am going to back off! I have always wonder how to not destroy my already customized theme, but now it seems a bit more work for a noob like me <img src='http://justintadlock.com/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J Mehmett</title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-14024</link>
		<dc:creator>J Mehmett</dc:creator>
		<pubDate>Wed, 18 Jun 2008 14:56:24 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-14024</guid>
		<description>&lt;blockquote&gt;I’m not sure why WordPress accepts non-standard localization file names. But, here’s a question. What if WP only accepted standard names and someone wanted to create a site purely based on an  Elvish language (Lord of the Rings)?&lt;/blockquote&gt;

Of course that&#039;s why WordPress is independent. 

&lt;blockquote&gt;I do agree though that plugin and theme authors could really help out the community by adding a few extra lines of code to their themes. The average theme wouldn’t have too many strings to change anyway.&lt;/blockquote&gt;

WordPress was designed to help all, and to produce better open source world. Localization is part of better WordPress.</description>
		<content:encoded><![CDATA[<blockquote><p>I’m not sure why WordPress accepts non-standard localization file names. But, here’s a question. What if WP only accepted standard names and someone wanted to create a site purely based on an  Elvish language (Lord of the Rings)?</p></blockquote>
<p>Of course that&#8217;s why WordPress is independent. </p>
<blockquote><p>I do agree though that plugin and theme authors could really help out the community by adding a few extra lines of code to their themes. The average theme wouldn’t have too many strings to change anyway.</p></blockquote>
<p>WordPress was designed to help all, and to produce better open source world. Localization is part of better WordPress.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Tadlock</title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-14008</link>
		<dc:creator>Justin Tadlock</dc:creator>
		<pubDate>Wed, 18 Jun 2008 13:24:25 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-14008</guid>
		<description>&lt;strong&gt;J Mehmett&lt;/strong&gt;
I&#039;m not sure why WordPress accepts non-standard localization file names.  But, here&#039;s a question.  What if WP only accepted standard names and someone wanted to create a site purely based on an &lt;a href=&quot;http://lotr.wikia.com/wiki/Elvish_language&quot; title=&quot;Elvish Language&quot; rel=&quot;nofollow&quot;&gt; Elvish language&lt;/a&gt; (Lord of the Rings)?  

&lt;em&gt;Hey, it could happen.&lt;/em&gt;

I do agree though that plugin and theme authors could really help out the community by adding a few extra lines of code to their themes.  The average theme wouldn&#039;t have too many strings to change anyway.</description>
		<content:encoded><![CDATA[<p><strong>J Mehmett</strong><br />
I&#8217;m not sure why WordPress accepts non-standard localization file names.  But, here&#8217;s a question.  What if WP only accepted standard names and someone wanted to create a site purely based on an <a href="http://lotr.wikia.com/wiki/Elvish_language" title="Elvish Language" rel="nofollow"> Elvish language</a> (Lord of the Rings)?  </p>
<p><em>Hey, it could happen.</em></p>
<p>I do agree though that plugin and theme authors could really help out the community by adding a few extra lines of code to their themes.  The average theme wouldn&#8217;t have too many strings to change anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J Mehmett</title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-13967</link>
		<dc:creator>J Mehmett</dc:creator>
		<pubDate>Wed, 18 Jun 2008 06:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-13967</guid>
		<description>Truely man WP plugin and theme authors ignore the idea of localization  which affects the end-users.

By the way I wonder why WordPress accepts non-standard localization filenames like &lt;code&gt;mycrazylanguage.po&lt;/code&gt; as &lt;code&gt;define (&#039;WPLANG&#039;, &#039;mycrazylanguage&#039;);&lt;/code&gt; instead of accepting only gettext standards such as &lt;code&gt;en_US.po/en_US.mo&lt;/code&gt; or &lt;code&gt;en_EN.po/en_EN.mo&lt;/code&gt; defined in WP as &lt;code&gt;define (&#039;WPLANG&#039;, &#039;en_EN&#039;);&lt;/code&gt;

Nice tip, JT.</description>
		<content:encoded><![CDATA[<p>Truely man WP plugin and theme authors ignore the idea of localization  which affects the end-users.</p>
<p>By the way I wonder why WordPress accepts non-standard localization filenames like <code>mycrazylanguage.po</code> as <code>define ('WPLANG', 'mycrazylanguage');</code> instead of accepting only gettext standards such as <code>en_US.po/en_US.mo</code> or <code>en_EN.po/en_EN.mo</code> defined in WP as <code>define ('WPLANG', 'en_EN');</code></p>
<p>Nice tip, JT.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Tadlock</title>
		<link>http://justintadlock.com/archives/2008/06/17/protecting-text-strings-from-theme-upgrades#comment-13959</link>
		<dc:creator>Justin Tadlock</dc:creator>
		<pubDate>Wed, 18 Jun 2008 04:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://justintadlock.com/?p=943#comment-13959</guid>
		<description>&lt;strong&gt;Richard H&lt;/strong&gt;
Localizing themes can open up a theme author to an entirely new audience.  I believe since I started doing this, I&#039;ve gotten a lot more international users willing to use the themes.

&lt;strong&gt;David&lt;/strong&gt;
For protection against theme upgrades &#8212; no, it won&#039;t be used much.  It was just a neat idea I thought about doing and figured I&#039;d post it as kind of a twist on how localization works.

It&#039;s actually not hard to implement.  If the English .po file is available, all a user has to do is load the file in Poedit and translate whatever strings they want.  It could literally take less than 5 minutes.

&lt;em&gt;Edit&lt;/em&gt; : I do want to add that it would be more complicated for first-time users of Poedit though.</description>
		<content:encoded><![CDATA[<p><strong>Richard H</strong><br />
Localizing themes can open up a theme author to an entirely new audience.  I believe since I started doing this, I&#8217;ve gotten a lot more international users willing to use the themes.</p>
<p><strong>David</strong><br />
For protection against theme upgrades &mdash; no, it won&#8217;t be used much.  It was just a neat idea I thought about doing and figured I&#8217;d post it as kind of a twist on how localization works.</p>
<p>It&#8217;s actually not hard to implement.  If the English .po file is available, all a user has to do is load the file in Poedit and translate whatever strings they want.  It could literally take less than 5 minutes.</p>
<p><em>Edit</em> : I do want to add that it would be more complicated for first-time users of Poedit though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

