This seems to be the right place to publish some thoughts about content localization.

• from the current product stage, there are at least three areas to be covered:
1. static elements of the framework, that are stored in the database, as module friendly names and description, user role names, all entries in the lists module.
   This is needed for fully localized  single language portals.
   
2. Page name, title, description and keywords
   as well as
   module name, header and footer text
   and
   a (multi-)assignment of languages for pages and modules, so they can be displayed for specific languages only.
   This offers the ability to build portals for multiple languages without language distinguishing modules.
   
3. Modules, that allow different texts depending of the available (installed) languages. This will also require an extension of the search interface.
   
4. For portals with huge content in multiple languages it would be desirable to have translation support, so a translater (or an admin for export to translating services) can easily find text, that has not been translated yet or has been updated since the last translation. Herefore the original text, that has been translated before will be needed (per language), so altered text portions can be highlighted.

Just my 2 cent. 

This is good news Geert, dank je. Just one question: why did we deviate from the standard vocabulary? I think I've seen some document somewhere that explained that language, locale and culture are different things. In any case, I'm happy I can set it now. Does the new core get the skin object with it (this is now a trivial element)?

Peter

Just as a sidenote:

it looks like as if the language cookie in eriks core mod is not set in register.ascx - so if someone updates theit language settings from the profile page that change is not being reflected...