U4-118 - True support for 1:1 multi-lingual setup

Created by Morten Christensen 12 Jul 2012, 13:08:48 Updated by Shannon Deminick 26 Jun 2017, 05:39:41

Add true 1:1 support for adding culture variants of documents and have build-in routing support for fetching the right versions.

Comments

Stephan 26 Oct 2012, 08:47:38

Some notes & questions...

  • Do we want culture variants at document level (on copy per culture) or at property level (some properties have one value per culture, some have a shared value)?
  • How could we support that in the UI? Indicate that a property has 2 or more values?
  • How could we support that in the front-end (umbraco:item control, XSLT, Razor) - what would be the syntax to retrieve the property's value, for the default culture or for a specific culture?
  • We need to support different urls per culture -- so NiceUrl(...) would accept a culture parameter too?
  • Do we want to fully abstract/manage this, or to tell people to hand-make properties such as titleEN and titleDE as they do today?


Greg Fyans 15 May 2014, 14:08:47

I'd love to see this implemented. Get true 1:1 multi-lingual support and you'd blow every other CMS out of the water. My tuppence worth...

Do we want culture variants at document level (on copy per culture) or at property level (some properties have one value per culture, some have a shared value)?

At document level. Property level would be too awkward for everyone - developers and content editors alike.

How could we support that in the UI? Indicate that a property has 2 or more values?

Exactly why it should be at document level.

How could we support that in the front-end (umbraco:item control, XSLT, Razor) - what would be the syntax to retrieve the property's value, for the default culture or for a specific culture?

Using existing syntax culture is inferred from ASP.NET, so if a site implements multi-languages and they use ASP.NET to do this (i.e. they don't roll their own implementation) then no changes to code is required.

If they want to specifically target a language then the various methods that return content will need to accept a culture parameter.

<umbraco:Item field="nodeTypeAlias" culture="es-ES" runat="server"/>

We need to support different urls per culture – so NiceUrl(...) would accept a culture parameter too?

Yep.

Do we want to fully abstract/manage this, or to tell people to hand-make properties such as titleEN and titleDE as they do today?

Full abstraction. It's the only way it'll be successful.


Shannon Deminick 26 Jun 2017, 05:39:42

Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/


Priority: Normal

Type: Feature (planned)

State: Closed

Assignee:

Difficulty: Normal

Category: Architecture

Backwards Compatible: False

Fix Submitted:

Affected versions:

Due in version:

Sprint:

Story Points:

Cycle: