Comment 3 for bug 700619

The problem is language-selector and ubiquity set the subtag of locale in different way, like if you choose en_US druring your installation, then LANG and LANGUAGE will be set as en_US.UTF-8, but after you made any changes with language-selector, like change the language, the subtag will be set as xx_XX.utf8, and this is obviously a problem.
In my case, my remote machine is using en_US.UTF-8, but after I made a change with my local machine, the locale will be set as zh_CN.utf8, then, all Chinese characters on remote machine can't be displayed correctly from within the screen sessions. In addition, I think most distros are still using the tag scheme like xx_XX.UTF-8, instead of xx_XX.utf8.
So I'm very curious about why shall we use xx_XX.utf8? In addition, we have a lot of place to set locale variants, it make user feel frustrated, especially from GDM, too complicated. Why don't we just put all those languages relevant variant into /etc/environment or /etc/default/locale for system-wide settings, and into ~/.profile for users setting? then GDM/KDM/XDM/ just read it from them, it will more easy and straightforwad not only for end users, but also for developers.