<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Fucking Stationary and Flagrant Mistranslations</title>
	<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/</link>
	<description>machine translation, semantic analysis and life in China</description>
	<pubDate>Sat, 22 Nov 2008 08:01:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: trevelyan</title>
		<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-23</link>
		<dc:creator>trevelyan</dc:creator>
		<pubDate>Thu, 14 Feb 2008 18:15:02 +0000</pubDate>
		<guid>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-23</guid>
		<description>dried fruit guys, you win. :)</description>
		<content:encoded><![CDATA[<p>dried fruit guys, you win. <img src='http://adsotrans.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-22</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Thu, 14 Feb 2008 12:26:22 +0000</pubDate>
		<guid>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-22</guid>
		<description>Micah: yeah, it was quite a good *translation*, just not an accurate *gloss*.</description>
		<content:encoded><![CDATA[<p>Micah: yeah, it was quite a good *translation*, just not an accurate *gloss*.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micah</title>
		<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-19</link>
		<dc:creator>Micah</dc:creator>
		<pubDate>Wed, 13 Feb 2008 07:41:16 +0000</pubDate>
		<guid>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-19</guid>
		<description>I think "I want to do Fan Bingbing" is a pretty good translation.  Also, "I want to do what Fan Bingbing does" is correct as well, no?

I was amused that the translation of 干果 you used is "nuts".  Seems apt.</description>
		<content:encoded><![CDATA[<p>I think &#8220;I want to do Fan Bingbing&#8221; is a pretty good translation.  Also, &#8220;I want to do what Fan Bingbing does&#8221; is correct as well, no?</p>
<p>I was amused that the translation of <span class="adso">干果</span> you used is &#8220;nuts&#8221;.  Seems apt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: trevelyan</title>
		<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-16</link>
		<dc:creator>trevelyan</dc:creator>
		<pubDate>Wed, 13 Feb 2008 02:10:13 +0000</pubDate>
		<guid>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-16</guid>
		<description>@Todd,

Hypothetically, the simplest solution is adding a rule to the definition "to fuck" associated with 干 (or 想干) using the advanced editing page. This adds weight to the gloss whenever it's found before a person's name.

&#60;NEXT me 1&#62;Person&#60;/NEXT&#62;

Non-hypothetically, this is a good suggestion so I've just done it. Opens up problems with sentences like 我想干范冰冰干的那个活, but who can say what that means for sure anyway.</description>
		<content:encoded><![CDATA[<p>@Todd,</p>
<p>Hypothetically, the simplest solution is adding a rule to the definition &#8220;to fuck&#8221; associated with <span class="adso">干</span> (or <span class="adso">想干</span>) using the advanced editing page. This adds weight to the gloss whenever it&#8217;s found before a person&#8217;s name.</p>
<p>&lt;NEXT me 1&gt;Person&lt;/NEXT&gt;</p>
<p>Non-hypothetically, this is a good suggestion so I&#8217;ve just done it. Opens up problems with sentences like <span class="adso">我想干范冰冰干的那个活</span>, but who can say what that means for sure anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-15</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Wed, 13 Feb 2008 01:36:08 +0000</pubDate>
		<guid>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-15</guid>
		<description>Is it evil and wrong of me that I just want to know how to make Adso annotate 干 as "to fuck"? I tried "我想干范冰冰" (merely an invented example, I assure you), but only got "to want to do" as an annotation. Come on David, give us a clue!</description>
		<content:encoded><![CDATA[<p>Is it evil and wrong of me that I just want to know how to make Adso annotate <span class="adso">干</span> as &#8220;to fuck&#8221;? I tried &#8220;<span class="adso">我想干范冰冰</span>&#8221; (merely an invented example, I assure you), but only got &#8220;to want to do&#8221; as an annotation. Come on David, give us a clue!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: trevelyan</title>
		<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-7</link>
		<dc:creator>trevelyan</dc:creator>
		<pubDate>Tue, 12 Feb 2008 15:40:25 +0000</pubDate>
		<guid>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-7</guid>
		<description>Actually had to add 干果 when writing the post too - really surprised it wasn't there before. Turned out the editing-api wasn't updating the pinyin field. Is fixed, along with the pinyin.</description>
		<content:encoded><![CDATA[<p>Actually had to add <span class="adso">干果</span> when writing the post too - really surprised it wasn&#8217;t there before. Turned out the editing-api wasn&#8217;t updating the pinyin field. Is fixed, along with the pinyin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan</title>
		<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-6</link>
		<dc:creator>Brendan</dc:creator>
		<pubDate>Tue, 12 Feb 2008 14:56:47 +0000</pubDate>
		<guid>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-6</guid>
		<description>Cool -- will keep my eyes open. One sweet little irony: In the text "我喜欢干果" above, your Adso popup is giving the, forgive me, wrong fucking Pinyin -- "gàn guǒ" rather than "gānguǒ." (Another pain-in-the-ass nitpick:spaces between the syllables? There are <em>rules</em>, you know!)</description>
		<content:encoded><![CDATA[<p>Cool &#8212; will keep my eyes open. One sweet little irony: In the text &#8220;<span class="adso">我喜欢干果</span>&#8221; above, your Adso popup is giving the, forgive me, wrong fucking Pinyin &#8212; &#8220;g<span class="adso">à</span>n gu<span class="adso">ǒ</span>&#8221; rather than &#8220;g<span class="adso">ā</span>ngu<span class="adso">ǒ</span>.&#8221; (Another pain-in-the-ass nitpick:spaces between the syllables? There are <em>rules</em>, you know!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-5</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 12 Feb 2008 13:51:23 +0000</pubDate>
		<guid>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-5</guid>
		<description>Most of the basic code is similar, although proper noun recognition is not as good as in the previous version yet and the software does some new things like try to build up phrases in ways that can lead to mistakes that weren't there before. Most of the time this is a sign that something is mistagged in the database.

Major improvement with 将 this weekend, and am spending time on  ongoing basis improving problems as I stumble into them. This week was dates, numbers and the unification of some geographic place names. Prepositional phrases are a problem area now, but that will change soon. If you run into obvious problems that you know the old version got right email me the text and I'll do what I can.</description>
		<content:encoded><![CDATA[<p>Most of the basic code is similar, although proper noun recognition is not as good as in the previous version yet and the software does some new things like try to build up phrases in ways that can lead to mistakes that weren&#8217;t there before. Most of the time this is a sign that something is mistagged in the database.</p>
<p>Major improvement with <span class="adso">将</span> this weekend, and am spending time on  ongoing basis improving problems as I stumble into them. This week was dates, numbers and the unification of some geographic place names. Prepositional phrases are a problem area now, but that will change soon. If you run into obvious problems that you know the old version got right email me the text and I&#8217;ll do what I can.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan</title>
		<link>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-4</link>
		<dc:creator>Brendan</dc:creator>
		<pubDate>Tue, 12 Feb 2008 13:04:17 +0000</pubDate>
		<guid>http://adsotrans.com/blog/fucking-stationary-and-flagrant-mistranslations/#comment-4</guid>
		<description>The new Adso is plenty nice, but I've caught it making weird parsing mistakes it didn't used to. How much overlap is there between the new rules and the old ones? Also, the new popups are indisputably Teh Hawt, but what's with the pin1yin1?</description>
		<content:encoded><![CDATA[<p>The new Adso is plenty nice, but I&#8217;ve caught it making weird parsing mistakes it didn&#8217;t used to. How much overlap is there between the new rules and the old ones? Also, the new popups are indisputably Teh Hawt, but what&#8217;s with the pin1yin1?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
