I've got a test site on 5.5 build 336 going.  I've added and enabled the nl-NL lanuage pack, and created a duplicate set of pages.  So far so good, I now have Home (nl-NL) and 'Test Page (nl-NL)' created in the site. 

The problem is that when I click on the nl-NL pages (via the flag) none of the strings change localization. I'm talking about login/logout etc- the string values that used to show the localized versions whenever you qualified the Url with /language/xx-YY

This happens both for logged-in users and for anonymous users. 

I've tried manually specifying the language in the Url and have checked all sorts of settings but I don't seem to be able to get it to work.

Am I missing something here?  Is the old content localization via resource strings supposed to work in the way it used to, or is something else afoot?

I would have thought that as long as the language was specified in the querystring, then the localized strings would all show that language, regardless of what content was actually on the page. 

On another point, the 'localized.gif' image seems to be missing from my the /images folder in my instll package.  This shows up in the Admin-Languages page as a broken link.

I've also tried to mark a page as translated, but it doesn't update when you click the 'mark translated' link.  YOu have to go out of the page and then come back in again later.  Not sure if this is just a refresh or caching issue.

FInally, I can't work out how to add a localized version of a page once it has been added after the initial creation of the localization package (which duplicates the tabs).  I was expectign to see a listing of the page in the translation status page, or perhaps a button in the 'localization' section of the page settings, but can't find anything anywhere.

Bruce, this is by design - the querystring value change was effectively double-loaded i.e. a change would affect both static text and the content of any localized module - now with 5.5 it would have affected page selection also (meaning that if you wanted to work with different languages you had to accept seeing the text in that language also -which is not typically the use case i.e. i want the static text to remain in english, but i may want to add a french page or cut-and-paste a french translation i have).. Instead this is now driven by the browsers language value and the users profile property allowing static text to remain fixed but page/module selection to vary. Note: there is some discussion about the thread culture and setting it - im not sure what the current state of this is.

---

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