I think this error might br related to the permissions. Make sure the permissions on your web folder are inherited by the child objects. (Right-click your web folder and go to the Security tab. Of course, first check if your permissions are still correct or reset if necessary. Then click the Advanced button, and thereafter click the "Change permissions..." button. Put a mark next to "Replace all child object permissions with...(etc)" and click OK until you are out). I mean the folder your iis points to.

If I am to help you through the setup, it is necessary you make this work. With the manifest file of the current version, the skin tokens do not setup correctly and cannot be parsed from the html file into the ascx file. You can still make it work, but it is so much more work and so much more explaining to do.

First of all, if you want to test how you can change skin in DSL, I suggest you try to have a few different skins, so that you can see clearly the effects. What you do now makes no sense: DNN will show you the same skin anyway because you point to the same skin. Have for instance a look here: http://dnnskins.codeplex.com/ and google around a little - remember when you look for skins, you look for the ones having HTML4 doctype (unless you aim for more advanced visitors than the ones still using IE6) - this is a trade-off we all have to make.

Next, DNN 5.6.0 has issues, you better download 5.6.1 or wait a little more for DNN 5.6.2. DSL 3.0.6 will also solve issues, but not the one you mention (because that is not a DSL issue). I would be thrilled if you could point me to another bug, because  having a good functionning localization system is important for me too.

When you have an issue in one browser but not in another one, the next step would be to validate the HTML and CSS code at w3.org . I would not spend too much time on this issue if I were you, it is irelevant unless your purpose is to research differences between HTML and XHTML.

Have you tried different skins? I can hardly imagine you plan to use the minimal entropy skin on your final web portal. This skin is a demo skin in XHTML. If you plan to create a web portal in Arab, you will want some skins that are adapted to the right to left writing style, I suppose.

Try 3 different skins, clearly identifiable (for instance by different colors). Make one the default skin in the portal settings and the 2 other skins the default skin in each of the languages in the portal localization control. Before you go check your localized pages, clear the DSL cache (in the host section of the DSLocalizator module) if you told DSLocalizator to use cache (on the same place).

Then let me know what happens.

While you are at it, try to add a DSLocaleSelector module to one of your pages. Then click on the Locale Selector options in the module's action menu and try to configure it to your taste. Later on, I will explain how this module helps you to build a language selector in your skin.

Creating skins requires some knowledge of HTML and CSS. If you have this, creating a skin is much easier than it would seem at first. Tiendaboliviana is not the site to learn skinning, but if you do an effort to grasp some of the skinning techniques, I will show you how to use the LocaleSelector skin object in your skin.

By the way, the language selector in your minimal entropy skin is not DSLocaleSelector but the core Language skin object. It however functions just as well as DSLocaleSelector in a DSL environment. In former versions of DNN, the language skin object had very little options for configuration, whereas DSL was fully configurable with templates. But the latest versions of DNN have added new parameters to the language object. The only difference is now that DSL delivers smaller flags than DNN (which is one of the reasons that I continue to use it)