<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Wilding Translation</title>
	<atom:link href="http://wilding-translation.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://wilding-translation.com</link>
	<description>Translations from German to English</description>
	<lastBuildDate>Tue, 24 Jan 2012 17:21:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>No, I am not happy to charge by the &#8220;source word&#8221; for unseen texts</title>
		<link>http://wilding-translation.com/2012/01/24/no-i-am-not-happy-to-charge-by-the-source-word-for-unseen-texts/</link>
		<comments>http://wilding-translation.com/2012/01/24/no-i-am-not-happy-to-charge-by-the-source-word-for-unseen-texts/#comments</comments>
		<pubDate>Tue, 24 Jan 2012 17:21:49 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=587</guid>
		<description><![CDATA[<p>I have recently again been asked by an agency for my rate, which they require expressed &#8220;per source word&#8221;. Before I go further, I would refer those of you who can read German to a good discussion of this matter at http://www.intra-eg.de/wort_gegen_zeile.pdf.</p>
<p>Let me say that I do understand that agencies need to know, in advance, what [...]]]></description>
			<content:encoded><![CDATA[<p>I have recently again been asked by an agency for my rate, which they require expressed &#8220;per source word&#8221;. Before I go further, I would refer those of you who can read German to a good discussion of this matter at <a href="http://www.intra-eg.de/wort_gegen_zeile.pdf">http://www.intra-eg.de/wort_gegen_zeile.pdf</a>.</p>
<p>Let me say that I do understand that agencies need to know, in advance, what a freelancer is likely to charge for a given translation. We freelancers are, I think, sensible if we reserve the right to modify this on site of the actual text, just as we really must reserve the right to decline any job when we have actually had an opportunity to see the relevant files. But it is a commercial reality that agencies need to be able to estimate what a particular translator is almost certain to charge for a given job.</p>
<p>There was a time when the publishing world thought of the &#8220;word length&#8221; of, let&#8217;s say, a newspaper article as a purely nominal estimate, based on a double-spaced typed page, with an average of 10 (English) words per line, 30 lines per page. The typewriter wrote at 10 characters per inch, and that was that. Because the actual, precise word count is constantly available from your word processor, people have adopted the idea of using this as a measure of the &#8220;size&#8221; of a given text. But, as any agency with any experience of German should know, this is a very bad idea when it comes to measuring German. The problems are easy to see.</p>
<p>Firstly, I leave aside the issue of quoting for work simply on the basis of the quantity of text, ignoring questions of complexity, subtlety or style. There are things to be considered there, but for this article I will assume that we are dealing entirely with run-of-the-mill texts, typical for what a particular translator or particular agency handles.</p>
<p>The most obvious point is that German is positively famous for its long collocations, written without spaces to form a single word. People who don&#8217;t know the language sometimes think that it is a particular difficulty of German: &#8220;oh, all those long, long words.&#8221; In fact, of course, it is just something you quickly get used to. Let&#8217;s take a couple of examples.</p>
<p>We begin with something very simple: the source text says &#8220;Ich bin Alex&#8221;, and our translator summons their skill to convert this to English: &#8220;I am Alex&#8221;. Three words, in each case, and no obvious problem.</p>
<p>Next, we are translating a patent, written in German, for a new and inventive hairbrush. As is typically the case with patents, the document will probably not call it a &#8220;hairbrush&#8221;, to exclude the possibility that a competitor will come along with something very similar and say: &#8220;oh, but ours isn&#8217;t a hairbrush, it&#8217;s a multi-row comb, so your patent doesn&#8217;t cover it.&#8221; For this reason they will be likely to have an expression such as, &#8220;a hair alignment device, such as a hairbrush or comb&#8221;. It sounds comical, but there are good reasons for it. So our German text refers to a &#8220;Haarenausrichtungsgerät&#8221;. As I say, not as strange as it might look, because &#8220;Haaren&#8221; refers to our hair &#8220;Ausrichtung&#8221; is alignment, and a &#8220;Gerät&#8221; is a device. (This is, by the way, a joke &#8211; as far as I know &#8220;Haarenausrichtungsgerät&#8221; is not a real German word. But it could be!)</p>
<p>Now if we measure these texts by the &#8220;target word&#8221;, things are bad enough. If we do that, we are saying that the amount of work, skill, and so on involved in translating &#8220;hair alignment device&#8221; is exactly the same as that involved in translating &#8220;I am Alex&#8221;. Clearly not true. If, however, we base our charging on the number of characters, we have 21 characters as against 9 characters, and we would be saying that the translation of the long phrase is worth a bit more than twice as much as the short phrase. You might argue that the factories too high, you might argue that it is too low, but at least it is a factor, and it recognises the fact that the first phrase is longer and more complex than the second.</p>
<p>If, however, you want to measure by the &#8220;source word&#8221;, things are even worse. For the reasons described above, agencies will naturally want to work on the basis of the source text, because they want to know in advance what you are likely to charge. Commercial reality again – in its way, it&#8217;s fair enough. But what happens here is that we end up saying that &#8220;Haarenausrichtungsgerät&#8221; is only one word, and therefore that the translation of &#8220;I am Alex&#8221; is three times as difficult, and justifies a payment three times higher than the translation of &#8220;hair alignment device&#8221;. This is no longer merely &#8220;bad enough&#8221; – it is downright ludicrous.</p>
<p>The solution is simple. With one click of the mouse I can see the number of characters in my text. When working in Word it&#8217;s at the bottom left-hand corner of the window. &#8220;Characters (with spaces)&#8221; is what it says. You can use this directly, but the numbers tend to be large. More conveniently, and conventionally, you can divide it by 55 and get the number of &#8220;standard lines&#8221;. Asking for advanced pricing based on counts of the number of German words is highly unsatisfactory. To my mind it suggests that an agency who wants to do this may be lacking in experience.</p>
<p>Taking about 1 million recently translated words from my database, I see that on average I write almost exactly five English words for every four German words, but the length in characters tends to be usually within 1% or so of the source. In fact my translation is more often marginally shorter than the original than marginally longer. The problem, of course, is not that the average German word is longer than the average English word, but that the spread of lengths is much higher, and that the really long words tend to occur in texts that are, in any case, more complex and difficult to understand and require a more specialised vocabulary to express in English.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2012/01/24/no-i-am-not-happy-to-charge-by-the-source-word-for-unseen-texts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why you should use a proper translator</title>
		<link>http://wilding-translation.com/2012/01/09/why-you-should-use-a-proper-translator/</link>
		<comments>http://wilding-translation.com/2012/01/09/why-you-should-use-a-proper-translator/#comments</comments>
		<pubDate>Mon, 09 Jan 2012 16:23:04 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=580</guid>
		<description><![CDATA[<p>A perfect example from &#8220;My Switzerland&#8221; and the German version.</p>
<p>Read the first, and you may think that the Swiss are being refreshingly honest when they introduce &#8221;The city of Zug, well-known for its steep taxes&#8230;&#8221;, although you&#8217;d think they would at least quietly ignore that flaw. Read the second, and you will hear of &#8220;Die Stadt Zug, bekannt [...]]]></description>
			<content:encoded><![CDATA[<p>A perfect example from &#8220;<a href="http://www.myswitzerland.com/en/zug-1.html">My Switzerland</a>&#8221; and the <a href="http://www.myswitzerland.com/de/zug-1.html">German version</a>.</p>
<p>Read the first, and you may think that the Swiss are being refreshingly honest when they introduce &#8221;The city of Zug, well-known for its steep taxes&#8230;&#8221;, although you&#8217;d think they would at least quietly ignore that flaw. Read the second, and you will hear of &#8220;Die Stadt Zug, bekannt durch die tiefen Steuern&#8221;. Ahh, &#8220;low&#8221; taxes, not steep ones!</p>
<p>Machine translation? Or just poor quality? Perhaps the taxes are so very low, they had no money to pay for a proper translator!</p>
<p>I am asking them for comment, and will report.</p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2012/01/09/why-you-should-use-a-proper-translator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Just humour&#8230;</title>
		<link>http://wilding-translation.com/2011/05/05/just-humour/</link>
		<comments>http://wilding-translation.com/2011/05/05/just-humour/#comments</comments>
		<pubDate>Thu, 05 May 2011 08:17:24 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=561</guid>
		<description><![CDATA[<p>This has been around for a while, but it is amusing &#8211; How *Not* to Discuss Rates with a Translator</p>
<p>I should stress that this is not at all like my [...]]]></description>
			<content:encoded><![CDATA[<p>This has been around for a while, but it is amusing &#8211; <a href="http://www.youtube.com/watch?v=LeF7ykpRRc4">How *Not* to Discuss Rates with a Translator</a></p>
<p>I should stress that this is <strong><em>not</em></strong> at all like my regular clients!</p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2011/05/05/just-humour/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TAUS, &#8220;data-driven translation&#8221; and the future</title>
		<link>http://wilding-translation.com/2010/12/28/taus-data-driven-translation-and-the-future/</link>
		<comments>http://wilding-translation.com/2010/12/28/taus-data-driven-translation-and-the-future/#comments</comments>
		<pubDate>Tue, 28 Dec 2010 12:30:22 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=550</guid>
		<description><![CDATA[<p>A few weeks ago my attention was drawn to an article at http://www.translationautomation.com/perspectives/translation-leaks.html. In the associated discussion, I said that &#8220;it would be easy to pick holes in his largely spurious arguments if I had time&#8221;. Someone commented that, &#8220;suggesting that you have the capability but not the time to pick apart somebody else&#8217;s cogent arguments [...]]]></description>
			<content:encoded><![CDATA[<p>A few weeks ago my attention was drawn to an article at <a href="http://www.translationautomation.com/perspectives/translation-leaks.html">http://www.translationautomation.com/perspectives/translation-leaks.html</a>. In the associated discussion, I said that &#8220;it would be easy to pick holes in his largely spurious arguments if I had time&#8221;. Someone commented that, &#8220;suggesting that you have the capability but not the time to pick apart somebody else&#8217;s cogent arguments is a bit like those people who sometimes offer to black one&#8217;s eye over the Internet,&#8221; so now I have a little time, here are my thoughts. I reproduce the article in full, so that my comments, which are in red, have the full context.</p>
<p>Tuesday, 07 December 2010 15:00 Jaap van der Meer</p>
<p>You trusted your bank. You trusted your currency. You trusted your government. You trusted your translations.</p>
<p>So what happens now? Your certainties are being unraveled one after another. The system you trusted is leaking. It is unsettling. And even scary… But then you realize: trust is good, and knowing the facts is always the best policy.</p>
<p>You trusted your translations, your carefully chosen terminology, and your translation memories built up with great care, and well protected against unauthorized use. And now, you realize that your translations are as good or as bad as any others, that your customers rarely read your translations and often rely on machine-translated texts &#8211; machine translations that, annoyingly, are sometimes surprisingly good. <span style="color: #993300;">(Certainly some, and probably most of my clients do read my texts, in some cases quite carefully. If they don&#8217;t read yours, you must be a different branch of the industry.) </span>You realize that others are sharing translation memories, perhaps even <em>your</em> translation memories that you have nurtured as your own assets. You realize now that your secure world of translation is leaking. You are losing control. The model isn’t working anymore. It is upsetting, but it is better to face this new reality. Let go of the illusion of control.<span style="color: #993300;"> (I never did have an illusion of control, thank you. I maintain my translation memories as carefully as I can, but I have <em>sold</em> my translations – it is open, as it always was, to my clients to do with them whatever they want.</span><span style="color: #993300;">)</span></p>
<p><strong>New reality</strong></p>
<p>The world is changing and the translation industry is lagging behind. The industry still operates with a 20th century, western world mindset: the developed world exporting its goods and spreading its civilization to customers rich enough to pay. <span style="color: #993300;">(That&#8217;s what I call business.)</span> Translation is largely one-directional – from English into the major languages – and one translation per language fits all customers. <span style="color: #993300;">(I don&#8217;t have the figures to challenge this, but it strikes me as a surprisingly narrow and extraordinarily Anglo-centric view to be held by somebody who works in the translation field. English may, indeed, be at present one of the world&#8217;s most important technical and commercial languages, but surely<strong><em>, by that very token,</em></strong> a huge slice of the translation business involves translating texts <strong><em>into</em></strong> English, and I am quite sure that another huge slice is between languages where <strong><em>neither</em></strong> is English.)</span> Translation is priced by the word<span style="color: #993300;"> (in many cases)</span> and managed in projects <span style="color: #993300;">(that&#8217;s the way business is done)</span>. A project is traditionally product documentation, or instructions for use, or the user interface. Each project in principle is meant to increase sales in new markets and is measured by ROI. Efficiencies come from an overly simplistic <span style="color: #993300;">(I take it that &#8220;overly simplistic&#8221; is an overblown way – should I say &#8220;overlyblown&#8221; – of saying &#8220;very simple&#8221;)</span> technology called translation memory that was invented in the 80’s of the last century and has hardly advanced since then.<span style="color: #993300;"> (I am at a total loss trying to understand why the author regards software of this sort as in some way excessively simple. If he believes that it has not advanced over the last 20 years, I suspect he has not been using it. It has advanced hugely, as any user must surely know.)</span></p>
<p>Translation in the 21<sup>st</sup> century requires a very different vision.<span style="color: #993300;"> (I believe we are getting to his main commercial pitch.)</span> Western hegemony is over. Products and services are developed, manufactured and marketed everywhere and anywhere. Customers are more self-confident and don’t read manuals anymore. They read blogs and peer reviews and pull information from customer support sites when they need it. In fact new generation users don’t need user instructions at all and if new products are well designed, they’re completely intuitive and let the users ‘plug and play’. But new generation customers are also more discerning when they buy a product.</p>
<p>In this new regime, translation is multidirectional, from any language into any language.<span style="color: #993300;"> (I think it always was – see above.)</span> Quality requirements are different for different users and different usages. Machine translation is good enough for the largest volumes of dynamic web content <span style="color: #993300;">(I wonder which language is he has tried this out on. Recently I have had occasion to make considerable use of Google translate for Italian, as I now live in Italy without speaking the language. Italian may be less important than English, but it is scarcely an obscure language. The plain fact is that in most cases the reader is lucky if the sense rises above gibberish. Worse still than being incomprehensible, it is not uncommon for it to be entirely wrong, failing for instance to see negatives or inserting negatives where they do not exist.)</span>, whereas pre-sales texts require a step-up in quality from the current one-translation-fits-all policy. <span style="color: #993300;">(Who uses this policy? I suspect most of my clients have always had a higher standard.) </span>Tuning in to the style and sub-culture of niche customer groups makes all the difference in an increasingly global marketplace. Word-based pricing and ROI measurement do not make much sense in this new economic reality. Translation memory software still serves its goals in the shrinking business of manual translations <span style="color: #993300;">(Is there any evidence that the market is actually shrinking? I somehow doubt it)</span>, but it is totally inadequate for the growing volumes of dynamic content.</p>
<p><strong>A Lesson for Translation in the 21<sup>st</sup> Century</strong></p>
<p>If you can see even half way through this new reality, your concerns over translation leaks will begin to give way to a growing sense of excitement. Translation is coming out of the dusty libraries. <span style="color: #993300;">(I think that happened some while ago!)</span> Translation is gaining in relevance and significance as a worldwide service industry with billions of customers. Translation as a feature on every web site and every mobile device is the key to a vital global economy.</p>
<p>It is still unsettling of course when you realize that 90% of the translated words will be generated by machine translation engines, probably at no charge to the end-user. But considering there is a non-stop stream of multimedia information, the translation market will certainly innovate and assert its value in different ways. Naturally there is no need for every business to change and everyone to automate. In fact there will be a growing need for high-quality, tailored translations. But if you are tempted to join the innovation wave, I am sure you will figure out a way to prosper in this rapidly changing environment.</p>
<p>One aspect of the future of translation, however, is easily overlooked: the importance of ‘data’. ‘Data’ replaces the role of ‘translation memories’ as the key to efficiency. A jet engine with a thousand times the power of those 1980s propellers. Data drive  translation engines. Data will control the quality and the efficiency of translation in the future. <span style="color: #993300;">(This is a highly contentious point, and there is no substantial evidence yet that data-driven translation engines can do an even adequate job, let alone a good one, of anything but the most restricted, narrow types of text with highly concrete references. Perhaps the directions for how to get from Wimbledon to Andover might be translated this way, although I would want to be sure that the source didn&#8217;t contain anything &#8220;challenging&#8221; like &#8220;don&#8217;t turn left here, even though the sign tells you to&#8221;. I concede that data may indeed control the quality of this kind of translation – it is likely to keep it at a low level.)</span> Whoever has access to the data controls the future of translation. Privileged or monopolized access to data will jeopardize the blossoming of a 21st century translation industry. <span style="color: #993300;">(Jeopardize the author&#8217;s project?)</span> Ownership of translation memories – translation data – is therefore an important and sensitive topic of debate. The legal argument will not help us much longer in this age of translation leaks. <span style="color: #993300;">(I take it that he is trying to preemptively prepare the ground in the hope of deflecting the criticism that much of what TAUS plans may well be in breach of copyright.)</span> Data are mined, scraped, masked, shared and used by everyone from individual translators to large global corporations. Attempting to make a legal case against the unauthorized use of translation data will probably not work. The practical argument is all that counts <span style="color: #993300;">(he hopes)</span>, and once translations are published, there is no way to control the leaks <span style="color: #993300;">(he hopes)</span>. And to be honest, wouldn’t you rather turn the whole argument round? If your translations are not confidential, why not simply share these data with everyone who can use them to improve the efficiency and quality of translation as a whole. What stops you from doing this? <span style="color: #993300;">(What stops me? Professional discretion, for a start, even if I haven&#8217;t signed a nondisclosure agreement (NDA). I don&#8217;t know quite how typical my position is, but I do know that it is not unusual. As a freelance translator, I have <strong><em>sold</em></strong> my translations. I feel that I have the right to recall my past translations, and to use technology to assist me in that task, and in that way to improve my future translations. But it seems to me quite clear that, at least in the vast majority of cases, copyright was assigned to the client. Suppose that a German nut manufacturer wrote some brilliant advertising copy, and imagine that, after my attentions, the English version was still brilliant. Let&#8217;s imagine that the two were published side by side on the client&#8217;s website. Now let&#8217;s suppose that a German bolt manufacturer sees this and thinks <em>&#8220;Wunderbar, ve kann kopy zis text, und verr ze nut makers haff written &#8220;nut&#8221;, ve kann write &#8220;bolt&#8221;, und ve haff ze über-brilliant advertising kopy for ten cents only und ve kann sell our bolts to ze British and ze Amerikans!&#8221;</em>. Clearly there would be a problem, and it seems to me obvious that it would be the nut-makers who would have a case against the bolt makers for breach of copyright. My translation was sold, and it was up to them to do whatever they like with it. Now over the years I have worked for over 50 clients, and since many of those have been agencies, there must have been several hundred end-clients. If I were to share my translation memories with TAUS I would therefore need to get written permission from hundreds of owners, many of whom, for obvious commercial reasons, are unknown to me. And that is true even for those where I have not signed any sort of NDA. I wonder to what extent TAUS is simply hoping that nobody will ever notice how much copyright material is present in the database they are assembling.</span></p>
<p><span style="color: #993300;">Oh, yes, there is another reason that stops me from doing this. Believe it or not, rather than paying me a substantial sum for joining them and sharing my translation memories, they want <strong><em>me</em></strong> to pay <strong><em>them</em></strong>. Work that one out!)</span></p>
<p><strong>Wishing you Wisdom <span style="color: #993300;">(I think he means &#8220;Wishing you will come over to my point of view&#8221;)</span></strong></p>
<p>Here we are, at the start of the second decade of a new millennium, facing some real dilemmas. I know it’s hard to take such a radical step from one world into another. But be aware that while you are puzzling over which direction to go, your translations are leaking.</p>
<p>We wish you wisdom and success in 2011 and the decade ahead. We at TAUS are here to help as the industry think tank <span style="color: #993300;">(or so they want us to believe)</span>, your innovation partner and a safe harbor for sharing your translation memories.</p>
<hr size="1" />REGISTER FOR WEBINAR: TRANSLATION IN THE 21st CENTURY</p>
<p><strong>8am PDT / 5pm CET<br />
Wednesday 15 December<br />
45-minutes in duration</strong></p>
<p>We share insights on the future of the translation industry. Content is based on a number of market and collective intelligence exercises undertaken by TAUS during 2010. This includes continuous review of the market, ideation sessions with major translation decision makers, and discussion with leading scientists, amongst others</p>
<p><span style="color: #993300;">(I included this advert from the bottom of the webpage, as an example of the language used by these language professionals. &#8220;Ideation sessions.&#8221; Good grief.)</span></p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2010/12/28/taus-data-driven-translation-and-the-future/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Catherine Tate Interpreter</title>
		<link>http://wilding-translation.com/2010/11/02/catherine-tate-interpreter/</link>
		<comments>http://wilding-translation.com/2010/11/02/catherine-tate-interpreter/#comments</comments>
		<pubDate>Tue, 02 Nov 2010 07:40:21 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=538</guid>
		<description><![CDATA[Catherine Tate Interpreter  [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;">You have to laugh:<br />
<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="480" height="385" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/QNKn5ykP9PU?fs=1&amp;hl=en_GB" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="480" height="385" src="http://www.youtube.com/v/QNKn5ykP9PU?fs=1&amp;hl=en_GB" allowfullscreen="true" allowscriptaccess="always"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2010/11/02/catherine-tate-interpreter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pharmerging &#8211; ghastly word of the year?</title>
		<link>http://wilding-translation.com/2010/10/20/pharmerging-ghastly-word-of-the-year/</link>
		<comments>http://wilding-translation.com/2010/10/20/pharmerging-ghastly-word-of-the-year/#comments</comments>
		<pubDate>Wed, 20 Oct 2010 08:11:34 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Reflection]]></category>
		<category><![CDATA[Translation]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=536</guid>
		<description><![CDATA[My vote in 2010 goes to "pharmerging" as the ugliest word of the year. [...]]]></description>
			<content:encoded><![CDATA[<p>This word, which had turned up in a client&#8217;s document – written in German it should be said – is my submission for ghastly word of the year. The &#8220;pharmerging&#8221; markets are those developing countries where the consumption of pharmaceuticals is rocketing. The USA and Europe are the biggest markets, but they are not far from saturation. The big pharmaceutical companies are looking for countries where they can expect to sell hundred tablets in a few years&#8217; time for every one sold today.</p>
<p>My client had the decency to put &#8220;pharmerging&#8221; in inverted commas and to speak about &#8220;so-called&#8221; pharmerging. A little research on Google soon tells me that the word is known, and is precisely relevant to my client&#8217;s field, so I am not blaming them. I almost don&#8217;t blame the twisted brain that thought up the idea. But I do blame the people who have had the bad taste to adopt it as a buzzword, presumably in the belief that it makes them look as if they have esoteric marketing knowledge.</p>
<p>I&#8217;m not actually sure when it first came into circulation, so it may not really be this year&#8217;s word, but this is the first time I have come across it. I&#8217;m willing to bet that I won&#8217;t come across anything else with such low linguistic sensitivity this year, so there you have it: my vote in 2010 goes to &#8220;pharmerging&#8221; as the ugliest word of the year.</p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2010/10/20/pharmerging-ghastly-word-of-the-year/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What do people think about translators?</title>
		<link>http://wilding-translation.com/2010/10/08/what-do-people-think-about-translators/</link>
		<comments>http://wilding-translation.com/2010/10/08/what-do-people-think-about-translators/#comments</comments>
		<pubDate>Thu, 07 Oct 2010 13:45:48 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=534</guid>
		<description><![CDATA[<p>A (very good) agency for whom I work has sent me a job from a client I shall, of course, not name. It consists of 60 or 70 picture captions for a magazine. The end-client does not seem to think it worth giving the translators access to the actual pictures. After all, all we do in [...]]]></description>
			<content:encoded><![CDATA[<p>A (very good) agency for whom I work has sent me a job from a client I shall, of course, not name. It consists of 60 or 70 picture captions for a magazine. The end-client does not seem to think it worth giving the translators access to the actual pictures. After all, all we do in this business is retype what is there, but we just do it in a different language, don&#8217;t we?</p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2010/10/08/what-do-people-think-about-translators/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Seven million words</title>
		<link>http://wilding-translation.com/2010/07/15/seven-million-words/</link>
		<comments>http://wilding-translation.com/2010/07/15/seven-million-words/#comments</comments>
		<pubDate>Thu, 15 Jul 2010 12:48:02 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=521</guid>
		<description><![CDATA[More than seven million words translated so far [...]]]></description>
			<content:encoded><![CDATA[<p>I just noticed that I recently passed a landmark &#8211; 7,000,000 words logged in my translating career so far. Will I make it to 10 million?<br />
I do remember going out to celebrate 1 million words, which seemed like a lot at the time, but that was years ago, of course.<br />
Oh, in case you are wondering, the millionth word was &#8220;but&#8221;. The seven-millionth was &#8220;monthly&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2010/07/15/seven-million-words/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Machine translation and human clangers</title>
		<link>http://wilding-translation.com/2010/03/10/machine-translation-and-human-clangers/</link>
		<comments>http://wilding-translation.com/2010/03/10/machine-translation-and-human-clangers/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 02:13:51 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=414</guid>
		<description><![CDATA[<p>The New York Times has recently run a comparison of Web translation tools.  Over the last few weeks I have had reason to look at some Italian sites, and the existence of these tools has made me realise that there cannot be much money left in the business of &#8220;gist&#8221; translations. What has reassured me, however, [...]]]></description>
			<content:encoded><![CDATA[<p>The New York Times has recently <a href="http://www.nytimes.com/interactive/2010/03/09/technology/20100309-translate.html" target="_blank">run a comparison of Web translation tools</a>.  Over the last few weeks I have had reason to look at some Italian sites, and the existence of these tools has made me realise that there cannot be much money left in the business of &#8220;gist&#8221; translations. What has reassured me, however, as someone who makes a living from translation, is that even now these tools often fail even to give a &#8220;gist&#8221;.  Of course, we can expect the results to improve, and possibly to do so quite fast, but in many cases, especially if the source is at all complex, the result is near gibberish.  Consider, for instance, the word &#8220;provanti&#8221;, which does indeed seem to be some kind of Italian word.  But what does it mean?  Attempts to use the Google translator on phrases containing this word yield gibberish: “Casa Provanti”, for instance, is yielded as &#8220;home hard to deal with&#8221;, and other trials show that at the moment the translation engine believes that &#8220;provanti&#8221; means &#8220;hard to deal with&#8221;. No, no, no, no, no.  It is a participle associated with a verb for attempting or trying, as in &#8220;I am trying to please my guests&#8221;.  The engine seems to have fallen for what I recall as a schoolboy joke:</p>
<p>&#8220;Can&#8217;t you do that with a bit more effort?&#8221;<br />
&#8220;Sorry, I&#8217;m trying.&#8221;<br />
&#8220;Yes you are, very!&#8221;<br />
(Boom, boom!)</p>
<p>But humans make mistakes too. Consider, for instance, a site to which I was recently referred, in the &#8220;languagering&#8221;, offering &#8221; Training in writting&#8221;, and telling us that &#8220;writing can be a tedious tasks&#8221;.  It would appear that for that writer, checking spelling and proofreading were just too tedious by far!</p>
<p>And here is another, although the author of this one can be perhaps forgiven, as the text was submitted for proofreading and correction.  I will not name the source, as it is a client who pays me. It illustrates the mistake that can be made by some Germans (and no doubt those with other native tongues) who plan to save money by doing the &#8220;translation&#8221; themselves, then paying a native of the target for the proofreading only.  The problem is, of course, that the difficulties created by this process mean that the &#8220;proofreading and correction&#8221; may demand more time and money than simply translating in the first place.  The source text was &#8220;Bei Werkstattmontage gebohrt&#8221;. For those who don&#8217;t know German, &#8220;bei&#8221; is related to the English &#8220;by&#8221;, and carries meanings like &#8220;in association with&#8221; or &#8220;at the same time as&#8221;, as well as &#8220;next to&#8221; and so on.  It is not used, however, to convey agency in the same way as in &#8220;I was knocked down by a car&#8221;. &#8220;Werkstattmontage&#8221; is a simple example of a German compound noun, and can uncontroversially be translated as &#8220;workshop assembly&#8221;. “Bohren” is to make a hole, as into &#8220;bore into a piece of leather&#8221;; in engineering contexts it is most often translatable as to &#8220;drill&#8221;, and a &#8220;Bohrung&#8221; is a drilled hole.  So our phrase is a comment on a hole, and tells us that it is &#8220;<em>Drilled during workshop assembly</em>&#8220;. Our German &#8220;translator&#8221;, however, had rendered it as (wait for it&#8230;): &#8220;<em>Bored by workshop assembly</em>&#8220;.  They probably were!</p>
<p>Disclaimer: having criticised the spelling and command of language of others it is a cosmic law (WIP &#8211; Wilding&#8217;s Inevitability Principle) that I have made at least one silly mistake in this article.  Don&#8217;t blame me!</p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2010/03/10/machine-translation-and-human-clangers/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Co-operation and un-co-operation</title>
		<link>http://wilding-translation.com/2009/12/01/co-operation-and-unco-operation/</link>
		<comments>http://wilding-translation.com/2009/12/01/co-operation-and-unco-operation/#comments</comments>
		<pubDate>Tue, 01 Dec 2009 04:59:08 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://wilding-translation.com/?p=337</guid>
		<description><![CDATA[Translation can do with input from the author [...]]]></description>
			<content:encoded><![CDATA[<p>I have been doing some work, through an agency, for a very big and well-known German industrial company &#8211; let&#8217;s call them GIC. This has not always been easy, as the company has very specific ideas about the vocabulary it wants to use, and is very particular about sticking to their terminology. This is, of course, a good thing &#8211; only too many people give no thought at all to the possibility that their texts might one day need to be translated. &#8220;Authoring for translation&#8221; is one of those ideas that often escapes writers altogether, or else is seen as an idealistic waste of time &#8211; after all, one might think, why do we pay translators if not to solve the problems of translation? It can take a lot of experience before people realise that &#8220;authoring for translation&#8221; can save a great deal of time, trouble and money in the long run, and can bring a far superior result. I hardly need to point out that a superior translation may well convert into superior sales figures.</p>
<p>On the other hand, I have known companies who have at least invested the necessary effort in the preparation of preferred vocabulary lists, and who are keen to provide translators with access to these lists and to ensure that they are used to bring more consistent results. I should stress that this is only a tiny part of &#8220;authoring for translation&#8221;, but it is certainly a positive step even if it is only a small one.</p>
<p>After some repeated difficulty with GIC, I pointed out to them that if they have a preferred vocabulary list, and if they want me to use it, perhaps they could give me, their translator, access to it. You can perhaps imagine my disappointment when, instead of the large Excel file that I expected, I was told where I can buy their dictionary. Hmmm.</p>
]]></content:encoded>
			<wfw:commentRss>http://wilding-translation.com/2009/12/01/co-operation-and-unco-operation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

