<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: How to set MXMLC (FCSH) to English (on Windows)</title>
	<link>http://www.tyz.nl/2010/03/25/how-to-set-mxmlc-fcsh-to-english-on-windows/</link>
	<description>Flash Developer</description>
	<pubDate>Mon, 06 Feb 2012 07:49:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Bart</title>
		<link>http://www.tyz.nl/2010/03/25/how-to-set-mxmlc-fcsh-to-english-on-windows/#comment-9353</link>
		<author>Bart</author>
		<pubDate>Wed, 03 Nov 2010 13:13:08 +0000</pubDate>
		<guid>http://www.tyz.nl/2010/03/25/how-to-set-mxmlc-fcsh-to-english-on-windows/#comment-9353</guid>
		<description>Another way to enforce this is to browse to your local FLEX SDK installation, then go to /flex/lib and remove the mxmlc.jar's with the unwanted locale.

Removing just the mxmlc_nl.jar seems to do the trick, but there's some other stuff (I see batik and xerces in my Flex 4.0) that you might want to check out: I'm not sure if Flex does a global 'revert to global locale' switch, or if it checks on a per-resource basis. 

Also note there's localized stuff in the /flex/framework that might show up and interfere lateron.</description>
		<content:encoded><![CDATA[<p>Another way to enforce this is to browse to your local FLEX SDK installation, then go to /flex/lib and remove the mxmlc.jar&#8217;s with the unwanted locale.</p>
<p>Removing just the mxmlc_nl.jar seems to do the trick, but there&#8217;s some other stuff (I see batik and xerces in my Flex 4.0) that you might want to check out: I&#8217;m not sure if Flex does a global &#8216;revert to global locale&#8217; switch, or if it checks on a per-resource basis. </p>
<p>Also note there&#8217;s localized stuff in the /flex/framework that might show up and interfere lateron.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: erik</title>
		<link>http://www.tyz.nl/2010/03/25/how-to-set-mxmlc-fcsh-to-english-on-windows/#comment-7866</link>
		<author>erik</author>
		<pubDate>Tue, 10 Aug 2010 21:37:57 +0000</pubDate>
		<guid>http://www.tyz.nl/2010/03/25/how-to-set-mxmlc-fcsh-to-english-on-windows/#comment-7866</guid>
		<description>Hahahahha, dit probleem had ik vandaag dus en nu lees ik 't toevallig 5 uur later hier ook. Ben nu met een multitouch game bezig in flash, dus moet opeens op windows 7 developen....... argh..... dat is echt rocketscience voor een mac adept.</description>
		<content:encoded><![CDATA[<p>Hahahahha, dit probleem had ik vandaag dus en nu lees ik &#8216;t toevallig 5 uur later hier ook. Ben nu met een multitouch game bezig in flash, dus moet opeens op windows 7 developen&#8230;&#8230;. argh&#8230;.. dat is echt rocketscience voor een mac adept.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thijs</title>
		<link>http://www.tyz.nl/2010/03/25/how-to-set-mxmlc-fcsh-to-english-on-windows/#comment-6379</link>
		<author>Thijs</author>
		<pubDate>Thu, 25 Mar 2010 14:44:57 +0000</pubDate>
		<guid>http://www.tyz.nl/2010/03/25/how-to-set-mxmlc-fcsh-to-english-on-windows/#comment-6379</guid>
		<description>Unfortunately this trick doesn't  work for Extension Manager bug. The Extension Manager still installs all extension in to the 'nl' folder instead of the 'en' folder.</description>
		<content:encoded><![CDATA[<p>Unfortunately this trick doesn&#8217;t  work for Extension Manager bug. The Extension Manager still installs all extension in to the &#8216;nl&#8217; folder instead of the &#8216;en&#8217; folder.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

