This bug is from bug 80230. It seems that only Windows platform does not work -UILocale and -contentLocale switching for the 1st time. The operation needs twice to make this work. Here is the report from Maruyama-san (from bug 80230). --- Sorry, I have fixed panels.rdf for JP Region, http://www.ash.ne.jp/~mal/mozilla/091jp-panels.rdf and regjp.xpi. http://www.ash.ne.jp/~mal/mozilla/moz0.9.2plus-regjp-070504.xpi I also tried to change Japanese menu and content used -UILocale and -contentLocale option on win2k. 1. Install langjajp.xpi and regjp.xpi 2. Mozilla start up and exit 3. delete <user profile>/chrome/user-locales.rdf 4. "mozilla -UILocale ja-JP" command-line start up 5. Mozilla apply Japanese menu -contentLocale JP also success. When <user profile>/chrome/user-locales.rdf is *not* deleted, not success to change UI and content Language. --- This problem happens on Windows. We're not seeing this on UNIX. Can anyone know the differences between Windows and UNIX around rdf and profile loading??

Reassign to tao, cc to jbetak.

Switching qa contact to jonrubin.

Changing Platform and OS to all, because it is necessary to start twice in MacOS9.1 also for the changes to take effect. Note that on both Win and Mac, the Profile Manager UI changes immediately with the -UILocale switch (tested on 07-23-03-branch).

Changing summary to reflect problem on Mac as well.

Katakai-san, Do you mind if I make a slight change to the summary? I have found that the -UILocale and -contentLocale options are needed only once to switch locale; however, the browser needs to be launched twice for the locale changes to fully take effect. I propose the following new summary: "Win and Mac only: Need to launch browser twice to switch locale after initial use of -UILocale and -contentLocale options". I have made the following observations: 1) If I use -UILocale and -contentLocale the first time I launch, I can immediately see the UI changes in Profile Manager. However, the browser UI and content do not completely change with this first launch. If I launch a second time without the -UILocale and -contentLocale options, the browser UI and content will still change correctly according to the options I used in the first launch. 2) If I use -UILocale ja-JP (en-US profile), the browser still has English UI after the first launch. However, all of the menu keyboard shortcuts appear as they would for ja-JP UI. For example, in en-US menu, the "F" in "File" is underlined; after the first launch using ja-JP option, "File" still appears in English, but there is an underlined "(F)" that appears after the word "File", just as it appears after the Japanese katakana "fairu" after the second launch (the "F" in "File" itself is not underlined).

This bug might not get resolved until moz 1.0.

mass change, switching qa contact from jonrubin to ruixu.

reassign to new owner ->dbragg

Hi, Joe: Would you please verify if this problem still exists?

Can still repro with NS6.2 RTM build.

Mass changing QA contact to jimmyu@netscape.com

Mass changing QA contact to jimmyu@netscape.com

new owner ->tao

FUTURE. => ftang

assign future

what a hack. I have not touch mozilla code for 2 years. I didn't read these bugs for 2 years. And they are still there. Just close them as won't fix to clean up.

Mass Re-open of Frank Tangs Won't fix debacle. Spam is his responsibility not my own

Mass Re-assinging Frank Tangs old bugs that he closed won't fix and had to be re-open. Spam is his fault not my own

Filter on "Nobody_NScomTLD_20080620"