<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Localizability: Unnecessary dynamic behaviour</title><link>http://blogs.msdn.com/jesperh/archive/2006/07/25/678001.aspx</link><description>The evidence is overwhelming: if your localizers do not have enough context when they localize, odds are that they will not get it right. Lack of context leads to unnecessary bugs and lower quality overall, both of which can be very costly. One way for</description><dc:language>sv-SE</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Localizability: Unnecessary dynamic behaviour</title><link>http://blogs.msdn.com/jesperh/archive/2006/07/25/678001.aspx#684137</link><pubDate>Mon, 31 Jul 2006 17:44:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:684137</guid><dc:creator>Serge Wautier</dc:creator><description>Swedish localizer Jeppe gives a real-world example of why setting dialog contents at run-time is a nightmare for localizers.&lt;br&gt;&lt;br&gt;I believe he's damn right!</description></item><item><title>Localization Quality</title><link>http://blogs.msdn.com/jesperh/archive/2006/07/25/678001.aspx#9482475</link><pubDate>Tue, 17 Mar 2009 08:12:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9482475</guid><dc:creator>Jesper snackar dynga då och då. Här är beviset.</dc:creator><description>&lt;p&gt;Localization bugs are often classified into these symptom buckets: Build/BVT (1) breaks This kind of&lt;/p&gt;
</description></item></channel></rss>