<?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: Moving a locale out of beta</title>
	<atom:link href="http://blog.mozilla.com/seth/2008/12/15/moving-a-locale-out-of-beta/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/seth/2008/12/15/moving-a-locale-out-of-beta/</link>
	<description>localization and community at mozilla</description>
	<lastBuildDate>Fri, 20 Nov 2009 20:49:29 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dwayne Bailey</title>
		<link>http://blog.mozilla.com/seth/2008/12/15/moving-a-locale-out-of-beta/comment-page-1/#comment-136851</link>
		<dc:creator>Dwayne Bailey</dc:creator>
		<pubDate>Tue, 03 Feb 2009 10:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/seth/?p=297#comment-136851</guid>
		<description>A direct link to pofilter itself:
http://translate.sourceforge.net/wiki/toolkit/pofilter</description>
		<content:encoded><![CDATA[<p>A direct link to pofilter itself:<br />
<a href="http://translate.sourceforge.net/wiki/toolkit/pofilter" rel="nofollow">http://translate.sourceforge.net/wiki/toolkit/pofilter</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dwayne Bailey</title>
		<link>http://blog.mozilla.com/seth/2008/12/15/moving-a-locale-out-of-beta/comment-page-1/#comment-136850</link>
		<dc:creator>Dwayne Bailey</dc:creator>
		<pubDate>Tue, 03 Feb 2009 10:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/seth/?p=297#comment-136850</guid>
		<description>I would also recommend that anyone using PO files to localise Firefox also run the Translate Toolkits QA tests as follows:

pofilter --mozilla po-files/ po-files-check/
#Review all PO files in po-files-check and fix errors
pomerge -t po-files po-files-check po-files

These steps are best done against files stored in a version control repository.

We maintain a list of the QA checks here:
http://translate.sourceforge.net/wiki/toolkit/pofilter_tests

Ones that are most interesting are:
* XML checks - makes sure you don&#039;t destroy any XML, in many cases human QA won&#039;t find these they&#039;ll only appear after you move out of beta when you get a flood of users.
* Variables - ensures you haven&#039;t inadvertantly translated or mistyped a variable.
* Cosmetic - extract unchanged messages so that you can review them, spellcheck, overly long, emails, filepaths, etc, etc

Many of these are impossible to find as a human since we quickly fuzz out when looking at text and can stare at errors without even realising it.

Give it a whirl. When we first started checking translations we found errors in official languages.  So you definately won&#039;t regret the effort.

If you&#039;re in beta it might even win you some points with Seth on his activity scale to get you out of beta.</description>
		<content:encoded><![CDATA[<p>I would also recommend that anyone using PO files to localise Firefox also run the Translate Toolkits QA tests as follows:</p>
<p>pofilter &#8211;mozilla po-files/ po-files-check/<br />
#Review all PO files in po-files-check and fix errors<br />
pomerge -t po-files po-files-check po-files</p>
<p>These steps are best done against files stored in a version control repository.</p>
<p>We maintain a list of the QA checks here:<br />
<a href="http://translate.sourceforge.net/wiki/toolkit/pofilter_tests" rel="nofollow">http://translate.sourceforge.net/wiki/toolkit/pofilter_tests</a></p>
<p>Ones that are most interesting are:<br />
* XML checks &#8211; makes sure you don&#8217;t destroy any XML, in many cases human QA won&#8217;t find these they&#8217;ll only appear after you move out of beta when you get a flood of users.<br />
* Variables &#8211; ensures you haven&#8217;t inadvertantly translated or mistyped a variable.<br />
* Cosmetic &#8211; extract unchanged messages so that you can review them, spellcheck, overly long, emails, filepaths, etc, etc</p>
<p>Many of these are impossible to find as a human since we quickly fuzz out when looking at text and can stare at errors without even realising it.</p>
<p>Give it a whirl. When we first started checking translations we found errors in official languages.  So you definately won&#8217;t regret the effort.</p>
<p>If you&#8217;re in beta it might even win you some points with Seth on his activity scale to get you out of beta.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
