Related Articles

1 user responded in this post

Subscribe to this post comment rss or trackback url
User Gravatar
Christopher Wigginton said in May 9th, 2008 at 8:13 am

Since this is an older post, have you stuck with this method for I18n of content? I’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->en and root->fr, etc.. then on tree building select the sub node based on label in the tags.

What I’d really like to build is one tree where each content object had associated language objects, but that’s a big change to the core and could get really messy with version tracking.

Leave A Reply

 Username (Required)

 Email Address (Remains Private)

 Website (Optional)