I read in the issue tracker that dnn core CL does not provide localized skins by design. The comments are closed, but I'd like to add my own two cents worth.

For uniquely western ML sites, this may be acceptable, but for sites with non-western font systems, that may make life more difficult.

I speak from my experience with Khmer, but I figure this is not unique. I need to have different containers and skins or at least different css files. Some of the reasons:

• some languages need a different line spacing for fonts with the same font size.
• some languages need specific fonts for h1, h2, h3 etc markups etc

DSLocalizator has this option. :-) This seems like one more reason to keep the effort going. :-) :-) :-)

---

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

That's why my style helper skin object allows you to load a css filtered on language or text direction:
http://40f.nl/emtDEL

You can use the current culture for that.
You would have to add the skin object once for every language you want to support

---

Actually, what you need is already part of the CSS specification (didn't think of that before).
You can address languages via the lang attribute of the HTML element:
http://www.w3.org/International/quest...

AFAIK, you should be able set all language specific styles like that.

---