<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Komentarze do wpisu: ExtJS ans simple JavaScirpt Internationalization (i18n)</title>
	<atom:link href="http://blog.adryjanek.eu/2010/01/28/extjs-ans-simple-javascirpt-internationalization-i18n/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.adryjanek.eu/2010/01/28/extjs-ans-simple-javascirpt-internationalization-i18n/</link>
	<description>Kamil Adryjanek - projektowanie aplikacji internetowych</description>
	<pubDate>Sat, 31 Jul 2010 09:48:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Przez: Aaron Conran</title>
		<link>http://blog.adryjanek.eu/2010/01/28/extjs-ans-simple-javascirpt-internationalization-i18n/#comment-13166</link>
		<dc:creator>Aaron Conran</dc:creator>
		<pubDate>Fri, 29 Jan 2010 01:04:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.adryjanek.eu/?p=67#comment-13166</guid>
		<description>Kamil -

This technique will work as long as you have some sort of server-side templating language available when serving/processing your JavaScript. When building a large application, you will want to concatenate and compress your JavaScript for optimal performance. We provide a tool to do this (JSBuilder2 http://www.extjs.com/products/jsbuilder/).

What I would suggest instead would be to place the default language into the prototype of the classes which you are developing. You can then dynamically generate a smaller file which includes your language specific text and overwrites the prototype. This is the same technique that we use to implement i8n in Ext and it works quite well. Check out the example in the SDK.
http://www.extjs.com/deploy/dev/examples/locale/dutch-form.html</description>
		<content:encoded><![CDATA[<p>Kamil -</p>
<p>This technique will work as long as you have some sort of server-side templating language available when serving/processing your JavaScript. When building a large application, you will want to concatenate and compress your JavaScript for optimal performance. We provide a tool to do this (JSBuilder2 <a href="http://www.extjs.com/products/jsbuilder/" onclick="javascript:pageTracker._trackPageview('/outbound/comment/www.extjs.com');" rel="nofollow">http://www.extjs.com/products/jsbuilder/</a>).</p>
<p>What I would suggest instead would be to place the default language into the prototype of the classes which you are developing. You can then dynamically generate a smaller file which includes your language specific text and overwrites the prototype. This is the same technique that we use to implement i8n in Ext and it works quite well. Check out the example in the SDK.<br />
<a href="http://www.extjs.com/deploy/dev/examples/locale/dutch-form.html" onclick="javascript:pageTracker._trackPageview('/outbound/comment/www.extjs.com');" rel="nofollow">http://www.extjs.com/deploy/dev/examples/locale/dutch-form.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
