Sorry, I overread this.

Peter,

you stated in your first post, that you need a solution soon. So did other developers a couple of month ago and enhanced the core with the features they needed. Imho this is one of the basic principles of open source - to add functions and present the solutions. I am glad, ErikVB did this as I use his solution for our community service site DeutschNetNuke = DotNetNuke auf Deutsch, which would have been much more difficult without ML modules. I agree with you, that it would be preferable to have a core solution for content localization, this would have avoided the current situation with 3 framework localization solutions (from ErikVB, Locopon and Germans) and at least four approaches for ML modules (from same 3 and Bo)*. Fortunately the solutions of ErikVB, Locopon and Bo do not interfere, I use them in the same portal without problems, did not try Germans' yet. 

I am not happy with this situation though, as I would have preferred an earlier solution by the core team - or at least a concept for this as I demanded from the core team shortly after the first beta of DNN 3.0 came out in 2004. But now we have to shut the stable door, after the horse has bolted. We should take the time, to find the best solution for content localization, there are promising starting points, that have to be collected and formed into a concept, so we hopefully get fully ML done, soon after the move towards ASP 2.0 has been made. And I also expect, that the authors of the current ML solutions will jump on the train or at least provide an upgrade solution for their modules.

Sebastian

* Edit: forgot to mention Nokiko's ML solution for skin objects.

Sebastian,

Thanks for you contribution to this discussion. My frustration mostly concerns the attention it gets from the (mainly American) core team. When I met Shaun earlier this year I talked to him about this and hoped he would return to Canada knowing how important this issue is to us 'rest-of-the-world-citizens'. What we see are multiple solutions living side-by-side and that makes life more difficult. It is true that under the time pressure we have to make a move and implement whatever we have. I will add another solution to the growing stack of ML solutions and I'll publish it so anyone can comment on it/try it.

Peter

PS I notice that all localization packs are offered using the country code as well. This means that there are no 'generic language' packs. Shouldn't there be any? I mean, if a Flemish user (nl-BE) uses DNN, we only have 'nl-NL' to offer where probably it would have been nice to have 'nl' as well.