Dear Locopon,
I am very grateful for the tools you provide for free. I am building a web site for a third-world university in two languages and have no budget for anything commercial. That is one of the reasons why I ended up choosing for DNN. For content localization, DSLocalizator was the only extension that filled my need.
I have complemented the installation with magic content although I later realized I could have achieved the same effect by displaying/hiding modules. But Magic Content adds to the realization that each module is supposed to appear in both languages and needs to be translated.
I have the DS extension running on a live site. I know that this is a beta, but it is the only thing I could find and the web site is conceptually not finished anyway, it is more of a learning site. Have a look at cup (dot) edu (dot) kh
The localization works fine, even the locale selector works perfect when applied as a module. But it is with skins that I encounter the problems. And that is not due to DSLocalizator, it is due to a misfit between the new skinning procedures and the documentation available to me. All explains the production of so-called legacy skins.
There is no how-to-proceed for 5.x skinning. I had hoped that I might procede from your test skin to produce my own, however I need to make it work properly before I can go to the next step. I am sure, it must be something I fail to understand: the test skin works for others, doesn't it?
My hope is that if you or anyone browsing through this forum has a look at the problem in khmersupport (dot) com click on nature tours to see the offending skin - and has an idea what I do wrong, you or he might give me a grasp on what now still remains a deep mystery.
It can't be all that difficult? I know it's something simple.