TYPO3 Core

The labels can be set in the installer with the configuration item BE[loginLabels].

Thats nice, that it is possible to change the labels in the install tool, but it is not a overall solution.

It would be better if it runs over the regular translation engine so that not everyone has to reinvent the wheel.

It would be also great if the error messages are translated.

And it would be even better, if the user could change the language and if there would be some language detection.

Imagine a huge typo3 with users from several nations, like UK, Germany and even China.

The install tool way has also a special chars problem öäü don't work.

I also noticed this problem (broken umlauts in the login-screen) quite a while ago - and it is related to the Install Tool, so I think it will be fixed in v2, which is currently in early development, but will hopefully be ready for 4.2.

Sonja, the problem with localizing the labels is that at this point we don't know the language of the editor. We could of course try to guess it from the browser-settings, which would be the best possibility for multi-langual installations. Setting it in the backend would require a new config-option and again, we would lock out all users with a different language than the one set as default by the admin.
So, if I find the time in the next days, I will try to fix this and give a patch here.

What is missing is a HTTP language negotiation accompanied with a language drop down box.

The attached diff-file should fix the problem. It introduces three new functions, two in t3lib_BEfunc and one in t3lib_div. The one in t3lib_div is only a helper for a change in EXT:lang/lang.php.

The default behaviour is changed in the following way: In typo3/template.php at the end there's the initialization routine for the $LANG-object. If a BE-user is detected, it behaves the same as bevor - $LANG is initialized with the users selected language. If not, it checks for the GP-var lang. If this is set, it is used, if not, the browser's accept languages are evaluated.
For evaluating these languages, a new function t3lib_BEfunc::getBrowserAcceptLanguages has been written. It returns an array with all languages, optionally also with variants like de-DE, in the order in which they appeared. This array is then checked in lang::init() for a language available in the BE. The first which is found is used, if none is found, the default is used.
The advantage of modifying $LANG is that now we also could translate the error messages ("no pages are found on the rootlevel", "Yeah, that's a classic..." etc.) [though I would say that "Yeah, that's a classic" should stay the way it is as it is really part of TYPO3's soul ;)]

Additionally, it displays a language-selector-box right above the form-fields on the login-screen.

Please check this patch. If you need them, I also have l10n-files for de ready.

Michael Stucki asked me to divide the patch into two ones, one for the language-selector and one for the labels. These patches are not applicable, at least I have not tested them, and at least 6228_labels.diff will throw errors. They are only provided for easier understanding, so if you want to apply the patch, use 6228.diff.

Since 4.3 the BE login gets the preferred language from the user's browser settings and uses locallang files.