Hi all,

Since the beginning of dotnetnuke, one of the biggest difficulties I ever found is the multi-language portal creation and administration.

Version after version, things changed and it is always a new challenge to get my skin working properly with all languages.

Now, many skin are coming using custom menu that sometime does not support multi-language.

I am not an expert ... so my question today is :

What is the best practice to make multi-language available and easy for my portal using standard module, store and so ...?

Thanks for your help and recommendation.

Stephane

thanks, apologies for the (relative) lack of documentation - we're be shortly deploying an updated version of the wiki that integrates with the dotnetnuke filemanager (so we can upload images that work in our webfarm) and this will be the first area I'll be writing up (it requires a lot of screen shots). There are some useful pieces of information already on localization in the wiki (predominantly static localization i.e. the labels/text you see on screen - http://www.dotnetnuke.com/Resources/W... ) but in recent versions we also introduced portal localization (http://www.dotnetnuke.com/Community/B...) and content localization (you can view a few slightly out of videos at http://www.dotnetnuke.com/Resources/V...)

Finally in the interests of balance don't forget that there are great 3rd party options such as http://ealo.codeplex.com/ , http://www.adequation-dotnetnuke.com/... and http://www.apollo-software.nl/ that often are better suited (dependening on your sites needs)

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US