<?xml version="1.0"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Forum posts to 'Engineering'</title>
		<link>http://rhonix.translate.com/engineering/rss</link>
		<atom:link href="http://rhonix.translate.com/engineering/rss" rel="self" type="application/rss+xml" />
		<description></description>

		
		<item>
			<title>The importance of planning for Medical Device UI localization</title>
			<link>http://rhonix.translate.com/engineering/show/101#post101</link>
			<description>&lt;p&gt;Medical devices tend to be notorious for limited space in their displays. At the same time, it is vital that there is no truncated text, that abbreviations are non-ambiguous, easily understood, and that they are consistent. This has its own challenges within the software itself, but when you add Online help and User manuals to the mix, it quickly can become a disaster of inconsistencies, misunderstandings, delays in project schedules and of course additional costs. &lt;/p&gt;&lt;p&gt;The only true way of dealing with this is PLANNING: &lt;br /&gt;1.&amp;nbsp;&amp;nbsp;&amp;nbsp;create a rigorous glossary of terms and have translations approved by all subject matter experts involved&lt;br /&gt;2.&amp;nbsp;&amp;nbsp;&amp;nbsp;review English screens for potential string limitations prior to translation&lt;br /&gt;3.&amp;nbsp;&amp;nbsp;&amp;nbsp;provide screen captures of strings in context&lt;br /&gt;4.&amp;nbsp;&amp;nbsp;&amp;nbsp;during translation, identify translated words that may need to be abbreviated in several screens&lt;br /&gt;5.&amp;nbsp;&amp;nbsp;&amp;nbsp;during translation, decide on whether to find a shorter term, or whether there is an acceptable abbreviation that will work across several screens &lt;br /&gt;6.&amp;nbsp;&amp;nbsp;&amp;nbsp;add approved abbreviations to the  glossary&lt;br /&gt;7.&amp;nbsp;&amp;nbsp;&amp;nbsp;test and regress software fully&lt;br /&gt;8.&amp;nbsp;&amp;nbsp;&amp;nbsp;update glossary with any additional/changed abbreviations&lt;br /&gt;9.&amp;nbsp;&amp;nbsp;&amp;nbsp;take any required screen captures used in help and documentation&lt;br /&gt;10.&amp;nbsp;&amp;nbsp;&amp;nbsp;only now, start help and documentation translations, allowing for potential customizations of localized text to explain abbreviations used. &lt;br /&gt;If your schedule allows for all the above, you have little to worry about. However, reality rarely allows for this generous of a timeline. &lt;/p&gt;&lt;p&gt;This does not mean you should not think through each and every step of the ideal process. By taking a couple of days to brainstorm and truly think through the challenges involved with your particular device, you can come up with smart compromises that will save you money, improve quality, and reduce stress on everyone involved. Also remember that for each target locale you add, the costs and delays caused by lack of planning multiplies exponentially.&lt;/p&gt;&lt;br&gt;&lt;br&gt;Posted to: The importance of planning for Medical Device UI localization &lt;a href=&quot;http://rhonix.translate.com/engineering/show/101#post101&quot;&gt;Show Thread&lt;/a&gt; | &lt;a href=&quot;http://rhonix.translate.com/engineering/show/101#post101&quot;&gt;Post Reply&lt;/a&gt;</description>
			<pubDate>Wed, 09 Dec 2009 19:11:14 -0700</pubDate>
			<dc:creator>Åsa</dc:creator>
			<guid>http://rhonix.translate.com/engineering/show/101#post101</guid>
		</item>
		

	</channel>
</rss>
