I've read the documentation and forums and I've seen two ways of doing multilingual websites (on a single domain name):
1:1 with as many trees as languages supported and a xslt content/children selector
nodes properties with as many tabs as languages supported
I'll try to explain our website's peculiarity:
This is no 1:1 content, some pages won't have other languages equivalent.
Language tabs mean you have to add a new tab to every document type when adding a language.
There are usercontrols which are translated using umbraco framework and dictionary depending on thread's current culture. Doesn't need 1:1 trees or tabs.
Language selection is done with a dropdown usercontrol which changes thread's current culture.
Why is it that there is no simple multilingual answer for umbraco websites?
Any advices on how to implement localization in this case?
1. Create the first version of the website 2. Copy the homepage node under content, you now have duplicated the entire website. I rename the homepage nodes to be the language 2-letter ISO code 3. Assign hostnames to the two homepage nodes, choosing the relevent url (e.g. yoursite.com/en) and language 4. Replace hard coded text in your templates/macros with dictionary items
- En - page - page - page
- Es - page - page - page
Now you have a 1:1 website but there is no reason why it must remain as such. The sites can be as different as necessary, and in my case 1:1 sites are never appropriate in the first place. Using tabs for language text is also a path to madness as it just doesnt scale very well.
Does this explain further? You can see an example of this approach at www.pindar.com
I'm guessing that the challenge is that all sites will have the same navigation, but some sites will be a mix of english and translated content. And that particular scenario will need some sort of customized development in order to get it working nicely.
Not sure if pindar.com is live or development but the french version pindar.fr was not found. Don't know if you recently registered it or not. Just FYI.
Thank you for your help dandrayne, sadly, 1:1 structure doesn't seem to fit our website's needs.
We'll probably try out a single tree structure with translated pages under the same parent node. which would look like
- Home - page_en - page_fr - page_ru - Buy - Sell - etc.
Now, following on the dropdown change usercontrol system, do you think it could be feasible to create properties in a doctype for redirections. i.e. when thread's current culture changes, the uc accesses the page property and redirects to the relevant localized clone.
Using that method, you are not tied to a 1:1 structure at all. Copying and pasting a site structure gives you a starting point but no requirement to keep the structure the same. You could start afresh with the new site just by creating a new homepage under the root node and not copying and pasting - same result.
Using the method such as
-Home - page_en - page_fr - page_ru
Would end up being a pain, as
* you'll need to set hostnames every time you create a new page * You won't be able to restrict user access to "only french pages" * The tree will become fairly messy pretty quickly * Creating navigation based on chosen language could become laborious
No easy way to do multilingual
I've read the documentation and forums and I've seen two ways of doing multilingual websites (on a single domain name):
I'll try to explain our website's peculiarity:
Why is it that there is no simple multilingual answer for umbraco websites?
Any advices on how to implement localization in this case?
Do you want different url's for the languages?
Hi Lauris
Starting with a structure such as this...
1. Create the first version of the website
2. Copy the homepage node under content, you now have duplicated the entire website. I rename the homepage nodes to be the language 2-letter ISO code
3. Assign hostnames to the two homepage nodes, choosing the relevent url (e.g. yoursite.com/en) and language
4. Replace hard coded text in your templates/macros with dictionary items
Now you have a 1:1 website but there is no reason why it must remain as such. The sites can be as different as necessary, and in my case 1:1 sites are never appropriate in the first place. Using tabs for language text is also a path to madness as it just doesnt scale very well.
Does this explain further? You can see an example of this approach at www.pindar.com
I'm guessing that the challenge is that all sites will have the same navigation, but some sites will be a mix of english and translated content. And that particular scenario will need some sort of customized development in order to get it working nicely.
Dan,
Not sure if pindar.com is live or development but the french version pindar.fr was not found. Don't know if you recently registered it or not. Just FYI.
-Chris
eurgh, looks like the client forgot to renew their domain. thanks!
Morten Bock > we'd rather go with a single url.
Thank you for your help dandrayne, sadly, 1:1 structure doesn't seem to fit our website's needs.
We'll probably try out a single tree structure with translated pages under the same parent node. which would look like
Now, following on the dropdown change usercontrol system, do you think it could be feasible to create properties in a doctype for redirections. i.e. when thread's current culture changes, the uc accesses the page property and redirects to the relevant localized clone.
Hi Lauris
Using that method, you are not tied to a 1:1 structure at all. Copying and pasting a site structure gives you a starting point but no requirement to keep the structure the same. You could start afresh with the new site just by creating a new homepage under the root node and not copying and pasting - same result.
Using the method such as
Would end up being a pain, as
* you'll need to set hostnames every time you create a new page
* You won't be able to restrict user access to "only french pages"
* The tree will become fairly messy pretty quickly
* Creating navigation based on chosen language could become laborious
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.