<?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: My authors are getting better, or I am</title>
	<atom:link href="http://ginstrom.com/scribbles/2009/10/05/my-authors-are-getting-better-or-i-am/feed/" rel="self" type="application/rss+xml" />
	<link>http://ginstrom.com/scribbles/2009/10/05/my-authors-are-getting-better-or-i-am/</link>
	<description>Random scribbling about programming, translation, and Japan</description>
	<lastBuildDate>Thu, 10 May 2012 05:41:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Ryan Ginstrom</title>
		<link>http://ginstrom.com/scribbles/2009/10/05/my-authors-are-getting-better-or-i-am/comment-page-1/#comment-11561</link>
		<dc:creator>Ryan Ginstrom</dc:creator>
		<pubDate>Mon, 26 Oct 2009 07:32:40 +0000</pubDate>
		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=1299#comment-11561</guid>
		<description>@Kevin

Notice I said &quot;better than average,&quot; not perfect. :)

When read with a copy editor&#039;s eye, even such august publications as the New York Times and the Economist are rife with errors.

Fellow translator Bill Lise used to say that the first and last time a document is fully understood is when it&#039;s translated. We tend to notice all the errors and logical inconsistencies, because we&#039;ve actually got to understand exactly what the author meant in order to translate the document.

Nevertheless, my point is that native readers of the source document generally navigate these problems in the source document with aplomb, and thus we should, too. The kinds of complaints you usually hear from beginning translators is that the source document is illogical, or that the exposition is poor, when often this is simply because the translator isn&#039;t familiar with the conventions of the source language.</description>
		<content:encoded><![CDATA[<p>@Kevin</p>
<p>Notice I said &#8220;better than average,&#8221; not perfect. <img src='http://ginstrom.com/scribbles/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>When read with a copy editor&#8217;s eye, even such august publications as the New York Times and the Economist are rife with errors.</p>
<p>Fellow translator Bill Lise used to say that the first and last time a document is fully understood is when it&#8217;s translated. We tend to notice all the errors and logical inconsistencies, because we&#8217;ve actually got to understand exactly what the author meant in order to translate the document.</p>
<p>Nevertheless, my point is that native readers of the source document generally navigate these problems in the source document with aplomb, and thus we should, too. The kinds of complaints you usually hear from beginning translators is that the source document is illogical, or that the exposition is poor, when often this is simply because the translator isn&#8217;t familiar with the conventions of the source language.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Lossner</title>
		<link>http://ginstrom.com/scribbles/2009/10/05/my-authors-are-getting-better-or-i-am/comment-page-1/#comment-11547</link>
		<dc:creator>Kevin Lossner</dc:creator>
		<pubDate>Sun, 25 Oct 2009 12:38:16 +0000</pubDate>
		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=1299#comment-11547</guid>
		<description>This is a complain I utter with some frequency, but it has nothing to do with an understanding of the source text. There is the occasional sentence which I&#039;ve looked at wrong and need to revisit, but the &quot;poor quality source material&quot; that I refer to typically means mislabeled diagrams (showing incorrect part assignments), a dozen typographical errors and spelling mistakes on each page, many obvious and not an impediment, but some truly baffling, missing words, sections copied without necessary changes being made, etc. Or dialect being used instead of the standard language. Sometimes the term in the local dialect is an antonym of the word in the standard language. (The German word &quot;verbauen&quot; is a typical case.) These are issues that may affect safety or legal validity in some cases. 

However important these documents may be to the client, they are too often not executed with due care. I see it as part of my job to address these issues where possible, though in the case of a notary&#039;s document for which I am preparing a certified translation, there isn&#039;t much I can do about the fact that he spells his client&#039;s name five different ways in four pages.

Simply receiving a source document which has been spellchecked is a highlight of some days. It does not happen often. Clients who perform even the most basic competent QA on documents before sending them to me are held in the highest esteem.</description>
		<content:encoded><![CDATA[<p>This is a complain I utter with some frequency, but it has nothing to do with an understanding of the source text. There is the occasional sentence which I&#8217;ve looked at wrong and need to revisit, but the &#8220;poor quality source material&#8221; that I refer to typically means mislabeled diagrams (showing incorrect part assignments), a dozen typographical errors and spelling mistakes on each page, many obvious and not an impediment, but some truly baffling, missing words, sections copied without necessary changes being made, etc. Or dialect being used instead of the standard language. Sometimes the term in the local dialect is an antonym of the word in the standard language. (The German word &#8220;verbauen&#8221; is a typical case.) These are issues that may affect safety or legal validity in some cases. </p>
<p>However important these documents may be to the client, they are too often not executed with due care. I see it as part of my job to address these issues where possible, though in the case of a notary&#8217;s document for which I am preparing a certified translation, there isn&#8217;t much I can do about the fact that he spells his client&#8217;s name five different ways in four pages.</p>
<p>Simply receiving a source document which has been spellchecked is a highlight of some days. It does not happen often. Clients who perform even the most basic competent QA on documents before sending them to me are held in the highest esteem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kate L</title>
		<link>http://ginstrom.com/scribbles/2009/10/05/my-authors-are-getting-better-or-i-am/comment-page-1/#comment-11106</link>
		<dc:creator>Kate L</dc:creator>
		<pubDate>Mon, 05 Oct 2009 13:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=1299#comment-11106</guid>
		<description>The first draft of any of my translations tends to be mediochre, and it is only through careful editing that I am able to submit high-quality translations to my client. I&#039;ve come to realise that this is not a reflection of poorly written original texts, but that I need to go through a two-step process in order to produce a good translation. 

My first draft is a literal translation of the text. I translate the meaning of the words and sentences into English, but the style still mirrors that of the original text. It is only during stage two of the translation process - careful editing - that I eliminate typically French sentence constructions and turn my translation into a more reader-friendly text in English. 

I agree with you that the &quot;poorly written source text&quot; argument most likely boils down to the fact that the translator has not fully understood the source language text. The skill in translation comes from working out what the author has (often intelligbly) written, and producing a stylish, flowing translation in the target language. 

If your translation sounds stilted, it is probably that you have completed step one of the translation process, but not step two. Re-read your work, try and work out exactly what the author is trying to say, and re-write it in your own words. Chances are that by doing this, you will inject clarity and style into your translations.</description>
		<content:encoded><![CDATA[<p>The first draft of any of my translations tends to be mediochre, and it is only through careful editing that I am able to submit high-quality translations to my client. I&#8217;ve come to realise that this is not a reflection of poorly written original texts, but that I need to go through a two-step process in order to produce a good translation. </p>
<p>My first draft is a literal translation of the text. I translate the meaning of the words and sentences into English, but the style still mirrors that of the original text. It is only during stage two of the translation process &#8211; careful editing &#8211; that I eliminate typically French sentence constructions and turn my translation into a more reader-friendly text in English. </p>
<p>I agree with you that the &#8220;poorly written source text&#8221; argument most likely boils down to the fact that the translator has not fully understood the source language text. The skill in translation comes from working out what the author has (often intelligbly) written, and producing a stylish, flowing translation in the target language. </p>
<p>If your translation sounds stilted, it is probably that you have completed step one of the translation process, but not step two. Re-read your work, try and work out exactly what the author is trying to say, and re-write it in your own words. Chances are that by doing this, you will inject clarity and style into your translations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

