<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for MarComments</title>
	<atom:link href="http://blog.marcomments.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.marcomments.com</link>
	<description></description>
	<lastBuildDate>Tue, 22 Dec 2009 10:59:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Type casting: tips to make your typography more readable. by Fred</title>
		<link>http://blog.marcomments.com/2009/12/21/type-casting/#comment-36</link>
		<dc:creator><![CDATA[Fred]]></dc:creator>
		<pubDate>Tue, 22 Dec 2009 10:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.marcomments.com/?p=157#comment-36</guid>
		<description><![CDATA[Thank you Chuck for recalling us these basics rules! Here in Grenoble, France, we love type! And the classic rules are a starting point. Respecting these conventions gives us a guarantee to be understandable and legible but of course these rules are evolving with the uses. Here In Europe there are a lot of languages with many different accents, that gives us the joy to discuss hours about having to use the caps with accent or not? That is the question. I say yes! Because the current technology makes that possible and the caps without accent can change dramatically the sens of the sentence. Example: UN PÈRE INDIGNÉ...  devient : UN PERE INDIGNE. (A SHOCKED FATHER… becomes: AN UNWORTHY FATHER). Don’t you feel bored with the accent less English?
One of my favorite fonts designers: http://www.emigre.com/index.php]]></description>
		<content:encoded><![CDATA[<p>Thank you Chuck for recalling us these basics rules! Here in Grenoble, France, we love type! And the classic rules are a starting point. Respecting these conventions gives us a guarantee to be understandable and legible but of course these rules are evolving with the uses. Here In Europe there are a lot of languages with many different accents, that gives us the joy to discuss hours about having to use the caps with accent or not? That is the question. I say yes! Because the current technology makes that possible and the caps without accent can change dramatically the sens of the sentence. Example: UN PÈRE INDIGNÉ&#8230;  devient : UN PERE INDIGNE. (A SHOCKED FATHER… becomes: AN UNWORTHY FATHER). Don’t you feel bored with the accent less English?<br />
One of my favorite fonts designers: <a href="http://www.emigre.com/index.php" rel="nofollow">http://www.emigre.com/index.php</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Translating corporate-speak into American English by Jolene Dobbin</title>
		<link>http://blog.marcomments.com/2009/11/23/corporate-speak/#comment-32</link>
		<dc:creator><![CDATA[Jolene Dobbin]]></dc:creator>
		<pubDate>Mon, 30 Nov 2009 20:28:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.marcomments.com/?p=125#comment-32</guid>
		<description><![CDATA[Great example. I can see where that term would be confusing outside of its appropriate context. It&#039;s vague enough within its appropriate context.]]></description>
		<content:encoded><![CDATA[<p>Great example. I can see where that term would be confusing outside of its appropriate context. It&#8217;s vague enough within its appropriate context.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Translating corporate-speak into American English by Sara</title>
		<link>http://blog.marcomments.com/2009/11/23/corporate-speak/#comment-27</link>
		<dc:creator><![CDATA[Sara]]></dc:creator>
		<pubDate>Wed, 25 Nov 2009 12:54:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.marcomments.com/?p=125#comment-27</guid>
		<description><![CDATA[&quot;Competitive innovation&quot; is one I&#039;ve seen three or four times recently. It basically means &quot;we don&#039;t innovate just for innovation&#039;s sake; the products of our innovation must also be marketable.&quot; Might be OK in a research article about innovation or risk management, but not in a corporate mission statement or annual report!]]></description>
		<content:encoded><![CDATA[<p>&#8220;Competitive innovation&#8221; is one I&#8217;ve seen three or four times recently. It basically means &#8220;we don&#8217;t innovate just for innovation&#8217;s sake; the products of our innovation must also be marketable.&#8221; Might be OK in a research article about innovation or risk management, but not in a corporate mission statement or annual report!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Your mission? Writing a mission statement. by More on writing corporate mission statements — SFM Traduction: Blogging about the business of language and the language of business</title>
		<link>http://blog.marcomments.com/2009/11/09/mission-statement/#comment-14</link>
		<dc:creator><![CDATA[More on writing corporate mission statements — SFM Traduction: Blogging about the business of language and the language of business]]></dc:creator>
		<pubDate>Tue, 10 Nov 2009 11:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.marcomments.com/?p=111#comment-14</guid>
		<description><![CDATA[[...] mission statements here. Over at Marcomments, the discussion continues with some tips about how to write a good mission statement in the first place.  Corporate mission statements would be easier to translate into other [...]]]></description>
		<content:encoded><![CDATA[<p>[...] mission statements here. Over at Marcomments, the discussion continues with some tips about how to write a good mission statement in the first place.  Corporate mission statements would be easier to translate into other [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Features and benefits in marcom copy by Harding Marketing</title>
		<link>http://blog.marcomments.com/2009/10/26/marcom-copy/#comment-11</link>
		<dc:creator><![CDATA[Harding Marketing]]></dc:creator>
		<pubDate>Fri, 30 Oct 2009 02:31:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.marcomments.com/?p=106#comment-11</guid>
		<description><![CDATA[Thank you for taking the time to read our article. Harding welcomes your comments.]]></description>
		<content:encoded><![CDATA[<p>Thank you for taking the time to read our article. Harding welcomes your comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Features and benefits in marcom copy by Sara</title>
		<link>http://blog.marcomments.com/2009/10/26/marcom-copy/#comment-9</link>
		<dc:creator><![CDATA[Sara]]></dc:creator>
		<pubDate>Tue, 27 Oct 2009 12:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.marcomments.com/?p=106#comment-9</guid>
		<description><![CDATA[Transforming features into benefits (or, even better, benefits of benefits, as you so aptly point out) is an issue that comes up again and again in my translation, copywriting, and training business. Whether it is translating marketing copy for clients, writing it for them from scratch, or helping them do it in house through training, I often use the &quot;so what&quot; test to facilitate the shift in mindset (writing from your customers&#039; viewpoint rather than your own) that is so necessary if we are to move from product specs to user benefits. Just keep asking &quot;so what&quot; until you can&#039;t go any further...for instance &quot;product X is made of a revolutionary bio-sourced new-age polymer made from genetically modified post-consumer hemp scraps&quot; (so what?) &gt;&gt;&gt; &quot;It is lightweight, durable, recycled and recyclable&quot; (so what?) &gt;&gt;&gt; &quot;You don&#039;t have to replace it as often, it costs less to ship, and the company will take it back and recycle it for you&quot; (so what?) &gt;&gt;&gt; &quot;You save money on shipping, on replacement costs, and get to communicate to YOUR customers on your environmental commitment to using only green products&quot;...etc.]]></description>
		<content:encoded><![CDATA[<p>Transforming features into benefits (or, even better, benefits of benefits, as you so aptly point out) is an issue that comes up again and again in my translation, copywriting, and training business. Whether it is translating marketing copy for clients, writing it for them from scratch, or helping them do it in house through training, I often use the &#8220;so what&#8221; test to facilitate the shift in mindset (writing from your customers&#8217; viewpoint rather than your own) that is so necessary if we are to move from product specs to user benefits. Just keep asking &#8220;so what&#8221; until you can&#8217;t go any further&#8230;for instance &#8220;product X is made of a revolutionary bio-sourced new-age polymer made from genetically modified post-consumer hemp scraps&#8221; (so what?) &gt;&gt;&gt; &#8220;It is lightweight, durable, recycled and recyclable&#8221; (so what?) &gt;&gt;&gt; &#8220;You don&#8217;t have to replace it as often, it costs less to ship, and the company will take it back and recycle it for you&#8221; (so what?) &gt;&gt;&gt; &#8220;You save money on shipping, on replacement costs, and get to communicate to YOUR customers on your environmental commitment to using only green products&#8221;&#8230;etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Translating marcom copy: How to avoid a world of trouble. by Sara</title>
		<link>http://blog.marcomments.com/2009/10/05/translating-marcom-copy-how-to-avoid-a-world-of-trouble/#comment-8</link>
		<dc:creator><![CDATA[Sara]]></dc:creator>
		<pubDate>Wed, 07 Oct 2009 10:36:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.marcomments.com/?p=65#comment-8</guid>
		<description><![CDATA[I couldn&#039;t agree more, but then again I&#039;m a translator. 

A key resource for anyone thinking about taking their communication international for the first time is the American Translators Association client-education brochure &quot;Translation, Getting it Right,&quot; available here: https://www.atanet.org/docs/Getting_it_right.pdf

Translation-friendly writing is crucial. However, a professional translator should ask questions and work with the writer to clarify any of the above points should they happen to sneak into a piece of writing, which they inevitably do. 

If your translator doesn&#039;t ask questions, consider it a warning sign!]]></description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more, but then again I&#8217;m a translator. </p>
<p>A key resource for anyone thinking about taking their communication international for the first time is the American Translators Association client-education brochure &#8220;Translation, Getting it Right,&#8221; available here: <a href="https://www.atanet.org/docs/Getting_it_right.pdf" rel="nofollow">https://www.atanet.org/docs/Getting_it_right.pdf</a></p>
<p>Translation-friendly writing is crucial. However, a professional translator should ask questions and work with the writer to clarify any of the above points should they happen to sneak into a piece of writing, which they inevitably do. </p>
<p>If your translator doesn&#8217;t ask questions, consider it a warning sign!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Translating marcom copy: How to avoid a world of trouble. by Give your brochure its own passport — SFM Traduction: Blogging about the business of language and the language of business</title>
		<link>http://blog.marcomments.com/2009/10/05/translating-marcom-copy-how-to-avoid-a-world-of-trouble/#comment-7</link>
		<dc:creator><![CDATA[Give your brochure its own passport — SFM Traduction: Blogging about the business of language and the language of business]]></dc:creator>
		<pubDate>Wed, 07 Oct 2009 10:28:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.marcomments.com/?p=65#comment-7</guid>
		<description><![CDATA[[...] at MarComments, the Harding Marketing marketing communication blog, this post about avoiding a world of trouble when translating brochures and other marketing materials, with which I couldn&#8217;t agree [...]]]></description>
		<content:encoded><![CDATA[<p>[...] at MarComments, the Harding Marketing marketing communication blog, this post about avoiding a world of trouble when translating brochures and other marketing materials, with which I couldn&#8217;t agree [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

