<?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>Emmer Inc &#187; localization</title>
	<atom:link href="http://blog.emmerinc.be/index.php/tag/localization/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.emmerinc.be</link>
	<description>Tales from a .NET developer who's making the jump to the iPhone &#38; App Store wonderland.</description>
	<lastBuildDate>Mon, 06 Sep 2010 19:43:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Localizing Localizable.strings woes</title>
		<link>http://blog.emmerinc.be/index.php/2009/04/22/localizing-localizablestrings-woes/</link>
		<comments>http://blog.emmerinc.be/index.php/2009/04/22/localizing-localizablestrings-woes/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 20:18:59 +0000</pubDate>
		<dc:creator>Yannick Compernol</dc:creator>
				<category><![CDATA[Xcode]]></category>
		<category><![CDATA[localization]]></category>

		<guid isPermaLink="false">http://blog.emmerinc.be/?p=434</guid>
		<description><![CDATA[While localizing the Localizable.strings file of Be Tv I encountered a rather curious (mis)behaviour. I used the NSLocalizedString macro wherever I needed to get my localized text and used the genstring command to generate the Localizable.strings file. I made a dutch and french localization of this file and everything was working in the iPhone simulator. [...]]]></description>
			<content:encoded><![CDATA[<p>While localizing the Localizable.strings file of <a href="http://blog.emmerinc.be/index.php/tag/be-tv/">Be Tv</a> I encountered a rather curious (mis)behaviour. I used the NSLocalizedString macro wherever I needed to get my localized text and used the genstring command to generate the Localizable.strings file. I made a dutch and french localization of this file and everything was working in the iPhone simulator. Nonetheless when deployed to my test device, the localization was not working. Localized nib files were though.</p>
<p>After fiddling with some Xcode settings, I gave up and resorted to Googling. Luckily I found <a href="http://cagan327.blogspot.com/2008/12/localizablestrings-problem-in-iphone.html">this blog post</a>, describing the exact same problem, giving an explanation why &#038; providing a solution. Turns out the localized Localizable.strings file has the wrong encoding, UTF-8 instead of UTF-16. Change the encoding, do a clean rebuild and your localization is up &#038; running.</p>
<blockquote><p> To change the file&#8217;s encoding to UTF-16 from UTF-8, use &#8216;View&#8217; &#8211;> &#8216;Text&#8217; &#8211;> &#8216;File Encoding&#8217; in XCode menu.</p></blockquote>
<p>Credits go to <a href="http://cagan327.blogspot.com/">Cagan Senturk</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.emmerinc.be/index.php/2009/04/22/localizing-localizablestrings-woes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
