I run one portal, purely in Khmer with in the same DNN instance 2 other portals ML.

DSLocalizator is installed. In the one-language Khmer portal, I have a strange occurance: When I enter Tab names solely in Khmer unicode characters, the navigation system cannot handle it and returns for any click in the navigation menu to the same page (1). A work-around is possible since DSLocalizator is already installed. If I add a unique number for the tab level in the tab name, and then remove that number in thwe Khmer localization in DSLocalizator's page localizator, I get the required effect. I wonder how that will survive mutation to core CL

I suspect the collation settings in SQL 2008 R2 to have something to do with it. But there is a problem. SQL 2008 R2 supports Khmer collation (Khmer_100_), but only on column or expression level data, not as server or database collations (together with a few other Indian and more exotic collations).

Then again, if one is to change collation, it would be on portal or on language level, wouldn't it? How does that work?

(1) Last time I tried was in DNN 5.2 or 5.3

---

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

Are there any DNN portals out there that use non-latin script and have (or don't have) similar problems?

If the problem only occurs with the few exotic languages, then the solution may be to hold my breath, wait for SQL 2008 R3 or SQL 201x and hope that Khmer gets to stand on equal footing as all the other languages in future editions of the SQL server.

If the problem occurs with all non-latin script portals, then this may be something the DNN team will have to find an answer for, sooner or later, when Asian sites start to use DNN Professional edition.

---

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

the menu need to be able to create urls from page names, even if non-ASCII characters are used - this doesn't sound to be database related, because collation is only used for comparison of texts. you may turn off human friendly urls in your web.config and exclude pagenames, this should result in urls like /tabid/13/default.aspx and not be affected by page names.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN