For the content localization I had chosen for Locopon's Localizator. I also frequently use the Magic Content module that has more great features besides those for localization. But Magic Content can only be a replacement for HTML modules, so I do use Locopon's module localizations also occasionally.

The problem is that I did not succede with the installation of his locale selector within a skin. Locopon's package has 2 locale selectors, one as a skin object and one as a module. I have been using the module version, until I could solve the skinning problem.

With time, I have grown a little more at ease with skinning and I spent a big chunk of this weekend researching how to build the locale selector in my skin. I have come to the conclusion that his skin object simply does not work. Anyone has been able to run his locale selector run within a skin under DNN 5.x.x?

Luckily, Locopon's hack works fine with the language object from the DNN core. I've built me a skin using the language object instead and it works perfectly. This how I wanted it from the beginning.  Well, almost...

The country flag displayed by dslocaleselector is smaller. Is there some option in the core version that akllows me to display the smaller flags?
And - In dslocalizator I can hide the selected link so that on the Khmer page I show only the American flag and on the English page I show only the Khmer flag? Or do I only have two options?

---

____________________________________
The one-eyed in the land of the blind.

Have I read somewhere that the next step in localization in DNN 5.5 would be "a one-to-one relationship". I do not remember reading what it meant, though it's a subject that interests me very much. I try to keep the university website strictly one-to-one at least for the public part. English to impress foreigners and Khmer to provide (most) online services for students.

With the above tools, I've been able to maintain that relationship - well allmost. But besides the above shortcoming of the skin element, I'm meeting some other problems. dslocalizator allows you to define different default skins for each language. So, that's what I've done for a few simple skins. I've made a Khmer version and an English version and edited skin.css and container.css and edited the font families. I don't seem to get it to work properly, but it's still too soon to point an accusing finger to anyone. It still might be me and I need another weekend testing. But I do see my changes turn up where I do not expect it.

Yet, when I set the Khmer skin to the default skin of the site, I can see all the settings that I defined in the css files. Strange.

DNN 5.4 did (ahum, does) not allow to identify different default skins for different locales. When I select in my site settings the Khmer properties, change the site skin there and then update the settings, I have also changed the default skin in the en-US page.

So, I'm very curious about the future of dnn. The ability to define default skins and page skins per language and the same for containers. Khmer scripture does not have capital letters, but it has something as a blockletter font. It requires a larger font size, and it is used for titles as well as shop signs.

Furthermore, Khmer needs a slightly higer line spacing in regard to western fonts of the same size. Whatever design a designer will cume up with, it will need to have two versions

Need beta testers? I've been hosting the site on my computer till the end of the contract with the current webhost. By the end of July it moves to its destination on a windows 2008 server and my current computer can become development computer. I'd be glad to comment on the new settings, I hope to fing all the functionality that dslocalizator promised to give (an probably once gave under 4.x) Anyway, I'd be happy if dslocalizator's functionality could be implemented from the core. Basically it means that I can change language on most any page. And it goes a long way if one can hide or display modules based on language selection.

Magic modules have a nice option of alternative content based on roles. I haven't tried it out yet, because I'm not sure its concept will survive future content localization strategies of the dnn development team. Yet, for current content localization, I like using them.

---

____________________________________
The one-eyed in the land of the blind.

there are no changes for multiple skins, 5.5 works as pervious versions. Note: I disagree that the 5.5 interferes with existing ML solutions - we still inject the language querystring that ML solutions rely on. I appreciate that we do not recognise existing ML solutions so you need to manually mark them as translated to keep your counts correct, but that's something we're planning on looking at at a future release.

---

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