<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.1-alpha-2539" -->
<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>WordPress.com Forums &#187; Topic: &quot;Likes&quot; are very i18n unfriendly</title>
		<link>http://en.forums.wordpress.com/topic/likes-are-very-i18n-unfriendly</link>
		<description>WordPress.com Forums &#187; Topic: &quot;Likes&quot; are very i18n unfriendly</description>
		<language>en</language>
		<pubDate>Sat, 25 May 2013 01:46:43 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1-alpha-2539</generator>
				<atom:link href="http://en.forums.wordpress.com/rss/topic/likes-are-very-i18n-unfriendly" rel="self" type="application/rss+xml" />

		<item>
			<title>miladin on "&quot;Likes&quot; are very i18n unfriendly"</title>
			<link>http://en.forums.wordpress.com/topic/likes-are-very-i18n-unfriendly#post-545757</link>
			<pubDate>Thu, 13 Jan 2011 18:17:30 +0000</pubDate>
			<dc:creator>miladin</dc:creator>
			<guid isPermaLink="false">545757@http://en.forums.wordpress.com/</guid>
			<description><![CDATA[<p>Following <a href="http://en.forums.wordpress.com/topic/spelling-mistake-in-french-blog-subscription-widget?replies=6">good experience</a> of other reporter, I'll try reporting issues that are more deeper in wpcom. If problem is solved successfully, expect flood of related reports from me.</p>
<p>There are two main issues with "Likes": they don't use plural forms and their placeholder usage for post types is very unfriendly. For both cases, here is an example.</p>
<p>String:<br />
<em>You and %s other bloggers like this %s.</em></p>
<p>In use:<br />
<em>You and 2 other bloggers like this post.</em></p>
<p>Problem is that post (type) is shown in original, English form. We need to have: 1) all separate cases for each post type 3) placeholder while post type would have context so that we know that its used in this exact string.</p>
<p>Other issues:</p>
<ul>
<li>if there are two or more placeholders, there should be argument swapping like %1$s, %2$s, etc, because of different order</li>
<li>sentences shouldn't be splitted without meaning (eg: <em>other bloggers like this %s.</em>)</li>
<li>tab on homepage showing likes doesn't have all strings in gettext</li>
<li>strings in top bar (already <a href="http://en.forums.wordpress.com/topic/subscribe-menu-untranslatable?replies=12">discussed</a>)</li>
</ul>
<p>Most of this issues are common for whole wpcom code and developers should follow some standards in i18n, most of them are covered <a href="http://codex.wordpress.org/I18n_for_WordPress_Developers">on the Codex</a>.</p>
<p>Now lets see results, in the past mostly we didn't see them.
</p>
]]></description>
					</item>

	</channel>
</rss>
