Erik van Ballegoij wrote:
To me it seems rather silly to force a portal to open into a certain language, if you offer multiple languages. If i visit a french portal that also offers english, i very much like the portal to open up in english instead of french upon my first visit. IMHO, multilingual portals also need some level of understanding with the client, and the consultant advising the client....
Hi Erik - sorry for bringing this old issue up again, but I have a different perspective for it.
I would like to set a default language based on the domain name, because domain names can contain a language specific part (i.e. www.dotnetnuke.com / www.dotnetnuke.co.uk / www.dotnetnuke.fr / www.dotnetnuke.dk / etc.). While dotnetnuke has the power to let all these domains point to the same domain and still have the option to change language based on the dotnetnuke preference (www.dotnetnuke.com/da-dk /) it would seem rather wierd to me that a site with the domain of .dk would open up in english based on the browser i use (since many danish users are using an english browser). I would expect the site www.dotnetnuke.dk to open up in danish, even if I'm in sweden visiting a friend, and not open up in english, swedish or any other language based on browser settings.
Wouldn't it make sense to be able to let domain take priority to the browser language? The automatic language setting is genius when only one domain is used (like .com or .info), but with the domain language extensions it can become a source of confusion. (why am I viewing www.dotnetnuke.dk/da-dk/? - it has 2 parameters for language now). The alternative would be to create a new portal for each langauge, but that really defeats the functionality of the dotnetnuke multilanguage support.
If you (or anyone else) have a solution to this perspective, I'm all ears :)
Kind Regards
Rune