<?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: Let&#8217;s drop the formalities</title>
	<atom:link href="http://ginstrom.com/scribbles/2009/05/04/lets-drop-the-formalities/feed/" rel="self" type="application/rss+xml" />
	<link>http://ginstrom.com/scribbles/2009/05/04/lets-drop-the-formalities/</link>
	<description>Random scribbling about programming, translation, and Japan</description>
	<lastBuildDate>Fri, 03 Feb 2012 09:05:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tom Ellett</title>
		<link>http://ginstrom.com/scribbles/2009/05/04/lets-drop-the-formalities/comment-page-1/#comment-5038</link>
		<dc:creator>Tom Ellett</dc:creator>
		<pubDate>Sat, 06 Jun 2009 04:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=1022#comment-5038</guid>
		<description>I had a similar reaction recently from a Swedish client for whom I had translated a how-to guide intended to get new volunteers involved in political campaigning. The original text was written in very simple, conversational Swedish, so I adopted a similarly chatty tone in English, using lots of contractions. I half expected to have to justify this to a client who had probably been taught overly formal English (by today&#039;s standards) in high school. Sure enough, I had to deal with a reaction along the lines of &quot;But I thought you only used &#039;don&#039;t&#039; and &#039;it&#039;s&#039; in speech, not in serious writing.&quot;</description>
		<content:encoded><![CDATA[<p>I had a similar reaction recently from a Swedish client for whom I had translated a how-to guide intended to get new volunteers involved in political campaigning. The original text was written in very simple, conversational Swedish, so I adopted a similarly chatty tone in English, using lots of contractions. I half expected to have to justify this to a client who had probably been taught overly formal English (by today&#8217;s standards) in high school. Sure enough, I had to deal with a reaction along the lines of &#8220;But I thought you only used &#8216;don&#8217;t&#8217; and &#8216;it&#8217;s&#8217; in speech, not in serious writing.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Ginstrom</title>
		<link>http://ginstrom.com/scribbles/2009/05/04/lets-drop-the-formalities/comment-page-1/#comment-2737</link>
		<dc:creator>Ryan Ginstrom</dc:creator>
		<pubDate>Mon, 11 May 2009 07:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=1022#comment-2737</guid>
		<description>@Judy

Choosing not to capitalize &quot;internet&quot; is certainly a valid decision, and in my non-translation writing I tend not to. If your clients are happy with &quot;internet,&quot; great! You&#039;re lucky to have a client who both cares about getting it right and is able to make intelligent decisions about it. :)

Working with Japanese clients can be very rewarding, because I feel that I&#039;m giving them a service that they really need, but it can be frustrating as well. In general, though, I prefer working for Japanese clients over American ones. At least Japanese clients never send me Chinese documents and ask me to translate them, or send me a fax with the last two characters of each line cut off (because they couldn&#039;t tell the difference).</description>
		<content:encoded><![CDATA[<p>@Judy</p>
<p>Choosing not to capitalize &#8220;internet&#8221; is certainly a valid decision, and in my non-translation writing I tend not to. If your clients are happy with &#8220;internet,&#8221; great! You&#8217;re lucky to have a client who both cares about getting it right and is able to make intelligent decisions about it. <img src='http://ginstrom.com/scribbles/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Working with Japanese clients can be very rewarding, because I feel that I&#8217;m giving them a service that they really need, but it can be frustrating as well. In general, though, I prefer working for Japanese clients over American ones. At least Japanese clients never send me Chinese documents and ask me to translate them, or send me a fax with the last two characters of each line cut off (because they couldn&#8217;t tell the difference).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Judy Jenner</title>
		<link>http://ginstrom.com/scribbles/2009/05/04/lets-drop-the-formalities/comment-page-1/#comment-2339</link>
		<dc:creator>Judy Jenner</dc:creator>
		<pubDate>Wed, 06 May 2009 17:05:11 +0000</pubDate>
		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=1022#comment-2339</guid>
		<description>Interesting point. A lot of companies go to greath lenghts to provide language-accessible documents in &quot;plain&quot; English, but I certainly understand that for your Japanese customers, it&#039;s a huge paradigm shift. If the friendly, less-formal language makes it into their textbooks (in, hm, 10 years) perhaps they will be more receptive. Until then, you are the pioneer! :) I completely agree that formal can be/has to be friendly and understandable. There&#039;s no reason to be stiff and writing from the ivory tower. BTW, at my old employer (a dot-com) we argued about Internet vs internet for a long time (and considered all the important guides), but finally did settle on internet (analogous to other forms of communication with lower-case: telephone,  mail, etc.), but both work.</description>
		<content:encoded><![CDATA[<p>Interesting point. A lot of companies go to greath lenghts to provide language-accessible documents in &#8220;plain&#8221; English, but I certainly understand that for your Japanese customers, it&#8217;s a huge paradigm shift. If the friendly, less-formal language makes it into their textbooks (in, hm, 10 years) perhaps they will be more receptive. Until then, you are the pioneer! <img src='http://ginstrom.com/scribbles/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  I completely agree that formal can be/has to be friendly and understandable. There&#8217;s no reason to be stiff and writing from the ivory tower. BTW, at my old employer (a dot-com) we argued about Internet vs internet for a long time (and considered all the important guides), but finally did settle on internet (analogous to other forms of communication with lower-case: telephone,  mail, etc.), but both work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

