<?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>Intentional Design Inc. &#187; Localization</title>
	<atom:link href="http://intentionaldesign.ca/category/localization/feed/" rel="self" type="application/rss+xml" />
	<link>http://intentionaldesign.ca</link>
	<description>Content strategies for business impact</description>
	<lastBuildDate>Thu, 15 Jul 2010 20:51:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<image>
  <link>http://intentionaldesign.ca</link>
  <url>http://intentionaldesign.ca/www/pmh3472/public_html/wp-content/uploads/2009/09/IDI-favicon.ico</url>
  <title>Intentional Design Inc.</title>
</image>
		<item>
		<title>The impact of content convergence on localization</title>
		<link>http://intentionaldesign.ca/2009/01/11/the-impact-of-content-convergence-on-localization/</link>
		<comments>http://intentionaldesign.ca/2009/01/11/the-impact-of-content-convergence-on-localization/#comments</comments>
		<pubDate>Sun, 11 Jan 2009 23:14:25 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Development]]></category>
		<category><![CDATA[Localization]]></category>
		<category><![CDATA[content convergence]]></category>
		<category><![CDATA[translation]]></category>

		<guid isPermaLink="false">http://wpsandbox.com/?p=400</guid>
		<description><![CDATA[I’ve been talking about content convergence for a while now, and have been watching the impact of this change on the adjunct processes connected to the design, production, and execution of content. I use the word execution rather than “publish” deliberately, as sometimes the push of content wouldn’t be classified as “publishing” at all, despite [...]]]></description>
			<content:encoded><![CDATA[<p>I’ve been talking about content convergence for a while now, and have been watching the impact of this change on the adjunct processes connected to the design, production, and execution of content. I use the word execution rather than “publish” deliberately, as sometimes the push of content wouldn’t be classified as “publishing” at all, despite the content being created and/or transformed from its incoming format into something consumable by a reader. Sometimes the reader is human; sometimes it’s another software application, where the content is passed through, absorbed, and then spit out for consumption somewhere down the line.</p>
<p>Other times, the mid-stream transformation is done by humans, and ingested back into the system for further transformation. Localized content fits in this area, and the implications can be far-reaching. The drive to package content into neat little bundles, so that they can be re-used in multiple contexts, is difficult enough to carry out for a single language or homogeneous market. Writing to satisfy the complexities of multiple languages or localized markets creates exponential challenges. Further complicating the situation is the fact that the people charged with transforming your content are usually outsiders, and probably haven’t been included in the sessions that taught the concepts and developed the architecture for the new content order within your organization. Not only do your translators have to figure out how your content convergence strategy is intended to work for you, they have to figure out how to retain the accuracy and flavor of your intent across languages and cultures. It’s a tall order, and an aspect of content convergence often overlooked.</p>
<p>There’s an article, <a title="Anticipating the Impact of Content Convergence" href="http://www.multilingual.com/articleDetail.php?id=1525">Anticipating the Impact of Content Convergence</a>, in the January/February 2009 issue of <a title="Multilingual Computing" href="http://www.multilingual.com/">Multilingual Computing</a> that elaborates on some of the things translation professionals, and their clients, need to consider as the nature of content undergoes a profound change.</p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=400&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2009/01/11/the-impact-of-content-convergence-on-localization/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Global Communication</title>
		<link>http://intentionaldesign.ca/2008/10/18/global-communication/</link>
		<comments>http://intentionaldesign.ca/2008/10/18/global-communication/#comments</comments>
		<pubDate>Sat, 18 Oct 2008 23:21:15 +0000</pubDate>
		<dc:creator>rahelab</dc:creator>
				<category><![CDATA[Content Development]]></category>
		<category><![CDATA[Localization]]></category>
		<category><![CDATA[instructional design]]></category>
		<category><![CDATA[plain language]]></category>
		<category><![CDATA[structured content]]></category>
		<category><![CDATA[translation]]></category>

		<guid isPermaLink="false">http://wpsandbox.com/?p=414</guid>
		<description><![CDATA[Some instructional materials created as part of my long involvement with localization and internationalization of technical content.]]></description>
			<content:encoded><![CDATA[<p>Some recent work I’ve been doing has reminded me of some of the instructional materials I created as part of my long involvement with localization and internationalization of technical content. The periodic resurgence of localization as a hot topic is interesting to see; the processing technology is the same, but the theory really hasn’t changed.</p>
<p>Creating translation-ready content is useful, whether the translation happens or not, because there are sure to be plenty of ESL readers who will need to decipher the English version. Localized content draws on guidelines from the Plain Language movement, from Controlled Language (or Controlled English or Controlled Technical English), and from the field of translation. There are visual elements to consider, as well as design elements. No matter how small the localization or internationalization initiative, there are sure to be unexpected considerations. Here are some resources that make that point:</p>
<p><a title="You Talking to Me?: Usability for Global Audiences on a Shoestring Budget" href="http://www.intentionaldesign.ca/images/uploads/YouTalkingToMe.pdf">You Talking to Me?: Usability for Global Audiences on a Shoestring Budget</a></p>
<p><a title="Reaching Global Audiences: Doing More with Less" href="http://www.stc.org/intercom/PDFs/2002/200206_17-21.pdf">Reaching Global Audiences: Doing More with Less</a></p>
<p><a title="Following the Road Untraveled: From Source Language to Translation to Localization" href="http://www.intentionaldesign.ca/images/uploads/Following_the_Road_Untraveled.pdf">Following the Road Untraveled: From Source Language to Translation to Localization</a></p>
<p><a title="Yours Truly International" href="http://www.intentionaldesign.ca/images/uploads/Yours_Truly_International.pdf">Yours Truly International</a></p>
<p><a title="High-Quality Content that Communicates Across Language Barriers" href="http://www.slideshare.net/abelsp/creating-high-quality-content-that-communicates-across-language-barriers-reducing-localization-costs-by-focusing-on-information-quality">High-Quality Content that Communicates Across Language Barriers</a></p>
<p><a title="Case studies in Controlled Authoring" href="http://www.tedopres.com/en/case-studies/">Case studies in Controlled Authoring</a></p>
<img src="http://intentionaldesign.ca/?ak_action=api_record_view&id=414&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://intentionaldesign.ca/2008/10/18/global-communication/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
