Closed Bug 55804 Opened 25 years ago Closed 25 years ago

unable to type Japanese (on non Japanese localized System)

Categories

(Core :: Internationalization, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: tracy, Assigned: nhottanscp)

Details

(Keywords: regression, smoketest)

windows build 2000-10-09-06-M18 bring up japanese fonts from from windows toolbar. attempt type text in composer, mail or AIM....nothing happens. note: did normal install, then retried with custom install, neither work.
Keywords: smoketest
Summary: unable to use Japanese fonts → unable to use Japanese fonts
Is this a problem of Japanese input or font? Can you view Japanese pages (e.g. http://home.netscape.com)? How about other platforms?
Status: NEW → ASSIGNED
browsing japanese pages is fine.... inputing text doesn't work. linux build 2000-10-09-06-M18 worked fine. no mac commercial build yet.
I tried 2000100909-M18 build on Win95-J. Japanese IME works fine both on Composer and Mail.
I tried 2000100909-M18 build on WinNT-J. Japanese IME works fine both on Composer and Mail.
Teruko is using Naoki's account. I looked at Tracy's setup. He is using Grobal IME with Windows US. When he start using Japanese IME, the error "Microsoft Grobal IME 5.0 for Japanese was unable to load the Japanese language pack." He cannot type any Japanese at all in Composer and Mail. However, Xianglan uses Japanese Windows. Japanese IME works fine. I think this is the problem on Grobal IME. Need to investigate.
I think the tree should not be closed for this one.
It also happens on branch build, so it's more serious. Put regression keyword. Also changed the title.
Keywords: regression
Summary: unable to use Japanese fonts → unable to type Japanese (on non Japanese localized System)
this turned out to be an isolated glitch on my machine. marking invalid
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
verified as invalid.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.