Implement multilingual content


After the initial release we should focus on enabling multilingual content. From a View perspective this could be as simple as creating an overload, like:
<% Html.RenderHtmlContent("myContentId", "nl-NL"); %>
The major issue at the moment seems to be how to make this consistent between different ContentProviders. CultureInfo, or some sort of enumeration structure, could perhaps help on this.
It would be ideal if there was a "default" language which will always be used if an optional additional language field is left empty.


wrote Aug 11, 2010 at 12:52 PM

Associated with changeset 64549.

wrote Aug 11, 2010 at 12:53 PM

wrote Aug 11, 2010 at 2:41 PM

Associated with changeset 64555.

wrote Nov 9, 2010 at 2:03 PM

wrote Nov 9, 2010 at 2:04 PM

wrote Nov 27, 2010 at 11:08 PM

wrote Feb 13, 2013 at 3:04 AM