<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Multiple langage sites in Farcry</title>
	<atom:link href="http://www.reynacho.com/2006/11/multiple-langage-sites-in-farcry/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.reynacho.com/2006/11/multiple-langage-sites-in-farcry/</link>
	<description>... on Flex, ColdFusion, FarCry, and much more ...</description>
	<lastBuildDate>Tue, 09 Feb 2010 18:36:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Christopher Wigginton</title>
		<link>http://www.reynacho.com/2006/11/multiple-langage-sites-in-farcry/comment-page-1/#comment-378</link>
		<dc:creator>Christopher Wigginton</dc:creator>
		<pubDate>Fri, 09 May 2008 14:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://jakewp.cfwebtools.com/2008/02/29/multiple-langage-sites-in-farcry/#comment-378</guid>
		<description>Since this is an older post, have you stuck with this method for I18n of content?  I&#039;ve been tasked with the same thing recently.  I was thinking having one root might be the better way and then under that have your language tree
root-&gt;en and root-&gt;fr, etc.. then on tree building select the sub node based on label in the tags.

What I&#039;d really like to build is one tree where each content object had associated language objects, but that&#039;s a big change to the core and could get really messy with version tracking.</description>
		<content:encoded><![CDATA[<p>Since this is an older post, have you stuck with this method for I18n of content?  I&#8217;ve been tasked with the same thing recently.  I was thinking having one root might be the better way and then under that have your language tree<br />
root-&gt;en and root-&gt;fr, etc.. then on tree building select the sub node based on label in the tags.</p>
<p>What I&#8217;d really like to build is one tree where each content object had associated language objects, but that&#8217;s a big change to the core and could get really messy with version tracking.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

