What are my options for internationalization on an Umbraco-managed site? The only way I have done it before is using subdomains, having a copy of the site for each language with related nodes, and then referencing dictionary items in templates instead of field values. This does seem like the best way; however, I am curious if there are any other ways besides using additional page fields for each language, which is obviously clumsy and nonscalable?
Also, a more specific question: can Umbraco work with www.mysite.de instead of de.mysite.com? Some way of using de.mysite.com within Umbraco but then somehow configuring the webserver to serve that as www.mysite.de? We want to have an entirely different domain for each language. Anyone done this, or know how to?
Looking for all manner of I18n best practices here.
We have not run into any problems with the "manage hostnames" feature of v4.7.2 using completely different domains. I don't think it cares whether you give it subdomain.example.com, or www.example.de, or whatever. You just need to set these up in DNS and your IIS site bindings accordingly, of course.
As far as how to structure your site, this is a bigger topic I've seen discussed in these forums a few times. For our purposes, we tend to just build separate sites as their own nodes, all under a single "site container" root node, and mimic the structure between the various sites manually as best we can. Sometimes this works to our advantage, since you may not yet have a translation for a new page you just added to one site, so it gives you time to add in the other site pages later. Or perhaps you don't want a certain page to exist in a different language, perhaps for cultural or regionally-specific reasons.
Multilanguage Site / I18n: Subdomains vs. Domains
Hi,
What are my options for internationalization on an Umbraco-managed site? The only way I have done it before is using subdomains, having a copy of the site for each language with related nodes, and then referencing dictionary items in templates instead of field values. This does seem like the best way; however, I am curious if there are any other ways besides using additional page fields for each language, which is obviously clumsy and nonscalable?
Also, a more specific question: can Umbraco work with www.mysite.de instead of de.mysite.com? Some way of using de.mysite.com within Umbraco but then somehow configuring the webserver to serve that as www.mysite.de? We want to have an entirely different domain for each language. Anyone done this, or know how to?
Looking for all manner of I18n best practices here.
Thanks in advance,
Garrett
We have not run into any problems with the "manage hostnames" feature of v4.7.2 using completely different domains. I don't think it cares whether you give it subdomain.example.com, or www.example.de, or whatever. You just need to set these up in DNS and your IIS site bindings accordingly, of course.
As far as how to structure your site, this is a bigger topic I've seen discussed in these forums a few times. For our purposes, we tend to just build separate sites as their own nodes, all under a single "site container" root node, and mimic the structure between the various sites manually as best we can. Sometimes this works to our advantage, since you may not yet have a translation for a new page you just added to one site, so it gives you time to add in the other site pages later. Or perhaps you don't want a certain page to exist in a different language, perhaps for cultural or regionally-specific reasons.
Good luck!
is working on a reply...