<?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: Translation for texts by other plugins and themes</title>
	<atom:link href="http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpml.org</link>
	<description>Using WordPress to build full multilingual websites</description>
	<lastBuildDate>Sun, 14 Mar 2010 01:12:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: amir</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-4442</link>
		<dc:creator>amir</dc:creator>
		<pubDate>Fri, 15 Jan 2010 13:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-4442</guid>
		<description>icl_register_string is used for dynamic strings that users enter, not for the PHP code itself.

WPML 1.6.0, coming out very soon, will be able to scan the PHP code and automatically extract all the gettext code for plugins, like it&#039;s doing for the theme now.</description>
		<content:encoded><![CDATA[<p>icl_register_string is used for dynamic strings that users enter, not for the PHP code itself.</p>
<p>WPML 1.6.0, coming out very soon, will be able to scan the PHP code and automatically extract all the gettext code for plugins, like it&#8217;s doing for the theme now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tarik</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-4441</link>
		<dc:creator>Tarik</dc:creator>
		<pubDate>Fri, 15 Jan 2010 13:03:51 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-4441</guid>
		<description>Excellent plugin !
I would like to know where I should add icl_register_string($context, $name, $value)  in order to get the plugin&#039;s source code crawled by wpml.

thank you!</description>
		<content:encoded><![CDATA[<p>Excellent plugin !<br />
I would like to know where I should add icl_register_string($context, $name, $value)  in order to get the plugin&#8217;s source code crawled by wpml.</p>
<p>thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-3213</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sat, 07 Nov 2009 11:25:54 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-3213</guid>
		<description>Hi,
You posted following example above:

icl_register_string($context, $name, $value)
icl_register_string(&#039;Contact Form 7&#039;, &#039;Input field label&#039;, &#039;Profession&#039;)

2nd parameter is used both for distinguishing different strings internally, and for displaying. Therefore we usually have to provide English descriptions for strings. This is not good, because translator may not know English, but know two other languages very well. I suggest to add new parameter to pass description string, which can be translated using standard po/mo files. Could you implement this feature? With this, we will be able do such call:

icl_register_string(&#039;Contact Form 7&#039;, &#039;Input field label&#039;, &#039;Profession&#039;, __(&#039;Input field label&#039;, &#039;my-plugin&#039;))</description>
		<content:encoded><![CDATA[<p>Hi,<br />
You posted following example above:</p>
<p>icl_register_string($context, $name, $value)<br />
icl_register_string(&#8216;Contact Form 7&#8242;, &#8216;Input field label&#8217;, &#8216;Profession&#8217;)</p>
<p>2nd parameter is used both for distinguishing different strings internally, and for displaying. Therefore we usually have to provide English descriptions for strings. This is not good, because translator may not know English, but know two other languages very well. I suggest to add new parameter to pass description string, which can be translated using standard po/mo files. Could you implement this feature? With this, we will be able do such call:</p>
<p>icl_register_string(&#8216;Contact Form 7&#8242;, &#8216;Input field label&#8217;, &#8216;Profession&#8217;, __(&#8216;Input field label&#8217;, &#8216;my-plugin&#8217;))</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-3005</link>
		<dc:creator>Alexander</dc:creator>
		<pubDate>Sun, 25 Oct 2009 15:23:06 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-3005</guid>
		<description>Where should  icl_register_string($context, $name, $value) be added?
Thanks,</description>
		<content:encoded><![CDATA[<p>Where should  icl_register_string($context, $name, $value) be added?<br />
Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WPML &#187; 整合的主题本地化</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-2269</link>
		<dc:creator>WPML &#187; 整合的主题本地化</dc:creator>
		<pubDate>Sun, 30 Aug 2009 01:46:52 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-2269</guid>
		<description>[...] WPML 的字符串翻译屏幕来翻译字符串 [...]</description>
		<content:encoded><![CDATA[<p>[...] WPML 的字符串翻译屏幕来翻译字符串 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amir</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-2264</link>
		<dc:creator>amir</dc:creator>
		<pubDate>Sat, 29 Aug 2009 13:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-2264</guid>
		<description>Support for translating user inputs need to be built into the plugin. You can ask the author of Tiny Contact Form to include it and we&#039;ll be very happy to help.

In the mean while, there is an excellent contact form plugin which you can use that already includes full multilingual support. It&#039;s Contact Form 7:
http://wordpress.org/extend/plugins/contact-form-7/

You can find instructions for translating the field names here:
http://ideasilo.wordpress.com/2009/07/22/contact-form-7-2-0/</description>
		<content:encoded><![CDATA[<p>Support for translating user inputs need to be built into the plugin. You can ask the author of Tiny Contact Form to include it and we&#8217;ll be very happy to help.</p>
<p>In the mean while, there is an excellent contact form plugin which you can use that already includes full multilingual support. It&#8217;s Contact Form 7:<br />
<a href="http://wordpress.org/extend/plugins/contact-form-7/" rel="nofollow">http://wordpress.org/extend/plugins/contact-form-7/</a></p>
<p>You can find instructions for translating the field names here:<br />
<a href="http://ideasilo.wordpress.com/2009/07/22/contact-form-7-2-0/" rel="nofollow">http://ideasilo.wordpress.com/2009/07/22/contact-form-7-2-0/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amy</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-2263</link>
		<dc:creator>Amy</dc:creator>
		<pubDate>Sat, 29 Aug 2009 12:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-2263</guid>
		<description>I am using Tiny Contact Form wordpress plugin
I do not understand how i can translate input fields
they are hard coded into the plugin
if i use .mo file (wp-content/languages) it do not change field translations if i choose between the languages

any advice? 
thanks,

Amy</description>
		<content:encoded><![CDATA[<p>I am using Tiny Contact Form wordpress plugin<br />
I do not understand how i can translate input fields<br />
they are hard coded into the plugin<br />
if i use .mo file (wp-content/languages) it do not change field translations if i choose between the languages</p>
<p>any advice?<br />
thanks,</p>
<p>Amy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaume</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-1969</link>
		<dc:creator>jaume</dc:creator>
		<pubDate>Tue, 11 Aug 2009 20:46:32 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-1969</guid>
		<description>Thanks a lot Amir,
I found a solution
I activated :
Activate expert mode (only if you really know what you are doing)
And then s easy coz I can put the category ID
It works erfect

It was just a bit confused coz of the &quot;(only if you really know what you are doing)&quot;

maybe something like &quot;(using IDs and numbers)&quot; will clarify more

Anyway, thanks a lot for your work, congratulations</description>
		<content:encoded><![CDATA[<p>Thanks a lot Amir,<br />
I found a solution<br />
I activated :<br />
Activate expert mode (only if you really know what you are doing)<br />
And then s easy coz I can put the category ID<br />
It works erfect</p>
<p>It was just a bit confused coz of the &#8220;(only if you really know what you are doing)&#8221;</p>
<p>maybe something like &#8220;(using IDs and numbers)&#8221; will clarify more</p>
<p>Anyway, thanks a lot for your work, congratulations</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-1968</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 11 Aug 2009 20:29:43 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-1968</guid>
		<description>It appear that PostLists isn&#039;t using the normal WordPress API to access the database, but is querying the database directly. It&#039;s surprising that it even works without WPML after all the WP updates.

You can try to contact PostLists author and get them to update their plugin. It&#039;s a simple update that doesn&#039;t have anything to do with WPML. We can still help with technical advice.

Amir</description>
		<content:encoded><![CDATA[<p>It appear that PostLists isn&#8217;t using the normal WordPress API to access the database, but is querying the database directly. It&#8217;s surprising that it even works without WPML after all the WP updates.</p>
<p>You can try to contact PostLists author and get them to update their plugin. It&#8217;s a simple update that doesn&#8217;t have anything to do with WPML. We can still help with technical advice.</p>
<p>Amir</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaume</title>
		<link>http://wpml.org/documentation/support/translation-for-texts-by-other-plugins-and-themes/comment-page-1/#comment-1967</link>
		<dc:creator>jaume</dc:creator>
		<pubDate>Tue, 11 Aug 2009 19:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://wpml.org/?page_id=1915#comment-1967</guid>
		<description>Hello,
I&#039;m usin the plugin PostLists 
http://wordpress.org/extend/plugins/postlists/

Im getting a list of posts in my default language. But when I change the language, I get the same list, no way to get the list of posts in the second language.

I tried to create a second category as a translation&#039;s category, but PostLists cannot see this new category.

Any idea?

Thanks</description>
		<content:encoded><![CDATA[<p>Hello,<br />
I&#8217;m usin the plugin PostLists<br />
<a href="http://wordpress.org/extend/plugins/postlists/" rel="nofollow">http://wordpress.org/extend/plugins/postlists/</a></p>
<p>Im getting a list of posts in my default language. But when I change the language, I get the same list, no way to get the list of posts in the second language.</p>
<p>I tried to create a second category as a translation&#8217;s category, but PostLists cannot see this new category.</p>
<p>Any idea?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>
