Hi, have a look at the file /etc/horde/horde3/nls.php and set the 
parameter $nls['defaults']['language'] to your preferred language. 
When this parameter was empty, I think my horde+imp installation 
behaved as you described.



/* The language to fall back on if we cannot determine one any other

    way (user choice or preferences). If empty, we will try to negotiate

    with the browser using HTTP_ACCEPT_LANGUAGE. */

$nls['defaults']['language'] = 'sk_SK';

Stalled until someone is able to reproduce this or track it further down.

On the IMP login page (where the language drop down is as noted in an 
earlier comment), the input fields are hidden, their values being 
populated from HTTP-AUTH interaction. That is the only code change 
I've located to date.



As for other systems, I've received reports of similar occurrences, 
but I've yet the time to substantiate, or replicate, them. The reports 
cover mainly RedHat and Fedora derived systems.

Thanks for the detailed steps and screenshots. It probably doesn't 
help much further though, since I have never seen such a thing before.

Regarding the "gibberish", these are translations displayed in the 
wrong charset, i.e. Russian being displayed in iso-8859-1 in the first 
case, and Persian being displayed in windows-1251 (Russian charset) in 
the second case.

The second case should not happen in any way, because the user's 
language is always used, if he has set one in his preferences, 
regardless of the language he has chosen in the login screen.

I have to admit, I have no idea what's happening there and noone ever 
reported something similar. Did you change anything in the code? Does 
this happen on all systems?

Hopefully the following helps with clarity.



For this test I created a new user for the email system, one that has 
never logged into Horde before. This gives a relatively clean working 
environment. The Horde install is 3.1.3, the IMP install is 4.1.3; PHP 
version 4.4.2. If needed I can provide a listing of locale -a output 
and other details. For clarity a number of screen shots are provided, 
numbered in the order of reference. Please see the attached file for 
the screen shots. The browser used for this test is FireFox 1.5.0.7 on 
Mac OS X. Now to the test.



Screen Shot: step one

Depicted is the Horde/IMP Login screen. Here one can select a language 
and log in. No language is actually selected at this point.



Screen shot: step two

Depicted is the same screen as shown in step one, after the user 
selects Russian from the language drop down. Notice the page is 
localized, the character set is correct. On this page, no matter the 
language selected, the page is always localized and the proper 
character set is used.



Screen shot: step three

Depicted is the resulting IMP Interface after selecting Russian (as 
shown in step two) and logging on the system. Notice the amalgam of 
English and I'm not certain what else. This is the "gibberish" I 
referenced in the original report.



Screen shot: step four

In the same login session as step three, the Global Options page 
displays in English. No matter the language selected at the login page 
(steps one and two), this page, and its sub-pages, always displays in 
English, unless the user sets a language/charset preference in the 
Global Options -> Locale and Time



Screen shot: step five

This follows after the user:

   1. Enters the Global Options -> Locale and Time page

   2. Selects a preferred language, in this case Russian

The page refreshes after saving the option. Notice the interface is 
now nearly 100% localized (the display of the word "Information" in 
English appears to be a deficiency of the Russian translation as other 
Languages correctly show the word localized).



Screen shot: step six

After performing the actions in step five, the session is ended. At 
the Login Page (depicted in step one) the language corresponding to 
the language saved in the Global Options -> Locale and Time in step 
five is selected and the user logs in. The interface is properly 
localized. No problems as experienced in step three.



Screen shot: step seven

The prior sessions are ended. At the login screen (depicted in step 
one) a different language is selected from the drop down, in this case 
Persian. Please note that this is the same user as all previous steps, 
who has Russian selected in Global Options -> Locale and Time. After 
login, with Persian selected, the resulting interface is again 
"gibberish", some words appearing in Cyrillic (Global Options, Help, 
Logout and others) while others making *might* be Persian, but if so 
are not displaying properly (Persian usually doesn't use the @ 
character, among other symbols, in regular words).

Sorry, I can't follow what you are talking about and I can't reproduce 
anything strange with language selection either. Also, what exactly do 
you consider "gibberish"?

I filed this against the incorrect queue, could someone please move it 
to Horde Base, thank you.

Below behavior tested with Horde 3.1.3/IMP4.1.3 using FireFox 1.5.0.7, 
Konqueror 3.5.3 and Opera 9.1



When selecting a language from the language drop down on the Horde 
login page, the application of such is meaningless:



1. The login page is translated just fine, no matter the language selected.



2. Once logged in, the Application is not translated according to what 
was selected at login. In part this is because the charset is not 
changed in the Web Server headers. The resulting web page is 
gibberish. No language was set in the users Global Locale preferences 
nor in the Horde/config/nls.php file.



3. If user has a default language selected in the Global Loacle 
options, the same language must be selected from the dropdown at 
login, otherwise one experiences the same gibberish.