I have used DNN for a while and I find it to be very good built but there is one thing I don't get. Why don't we have localization capabilities for every module. The static localization for each module is taken care of and thats good. But the problem occurs when you for example have a blog, link or html module. These modules have text that we today can't localize.

Lets say I have a HTML module with some text in English. When the user change to lets say German, Norwegian or French the English text is shown. What we want is to be able to store one version of the HTML for every language. Since this HTML is stored in the database and connected to a specific module all we need to do is to add one column containing culture code. When you have chosen English (en-US) and you save the html i should be saved with the en-US as culture code. If I change to German (de-DE) the html module should be empty (since it now gets the html with culture code de-DE). Now I can write my text in German and save it (now with culture code de-DE). This solution can be used for all modules and would be extremely easy to implement. All you need is one new column holding the culture code. This way we can always save the content of a module with the selected culture code. When the module is shown it will always look for the content with the selected culture code.

This is very good news. When this is implemented I feel DNN is really become a rock solid web portal that can fight with the "big guys".

Keep up the good work. Thanks to all the people that drives this product forward.

 And as I start using your free extension now, will I get in trouble in the future when ML is build in DNN itself?

Kind regards,

Kriz