We get asked by clients all the time how they can have multiple-languages for their site. We tell them the standard approach is to simply clone the content tree and use the host-names/culture/dictionary system.
Often this seems too heavy handed for the client who wants really to just to be able to edit the content for different languages.
I think it would be quite cool if Umbraco supported multi-language by letting users simply switch between languages when editing the content view - or maybe even create some virtual 'language' nodes underneath each node for the languages your site supports.
This may be quite limiting compared to the cloned-tree approach but for simple site translations I think it would be a valid alternative method.
The alternative would be to create tabs based on the languages you need to support.
So you could have "English", "German" etc. where you have the properties for the content, which has then been suffixed with _uk and _de for instance. But the problem is that it does not scale very well if you're creating a rather large site, which requires many tabs etc.
But for smaller sites with not that much content this approach could probably work well.
But doing multilanguage sites is always a bit of a challenge and it's an interesting topic to discuss.
Multi-Language - Single Tree
Hi everyone,
We get asked by clients all the time how they can have multiple-languages for their site. We tell them the standard approach is to simply clone the content tree and use the host-names/culture/dictionary system.
Often this seems too heavy handed for the client who wants really to just to be able to edit the content for different languages.
I think it would be quite cool if Umbraco supported multi-language by letting users simply switch between languages when editing the content view - or maybe even create some virtual 'language' nodes underneath each node for the languages your site supports.
This may be quite limiting compared to the cloned-tree approach but for simple site translations I think it would be a valid alternative method.
Thoughts?
Robert
Hi Robert
The alternative would be to create tabs based on the languages you need to support.
So you could have "English", "German" etc. where you have the properties for the content, which has then been suffixed with _uk and _de for instance. But the problem is that it does not scale very well if you're creating a rather large site, which requires many tabs etc.
But for smaller sites with not that much content this approach could probably work well.
But doing multilanguage sites is always a bit of a challenge and it's an interesting topic to discuss.
/Jan
is working on a reply...