Closed Bug 98376 Opened 23 years ago Closed 16 years ago

Unable to input Latin-1 chars using US keyboard with input locale set to CJK

Categories

(Core :: Internationalization, defect, P4)

Product:
Core
Component:
Internationalization
Platform:
x86
Windows 2000
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Milestone:
Future

People

(Reporter: ji, Assigned: smontagu)

Details

(Keywords: intl) 

Build: 090505 win32
OS: Win XP RC1 Ja

On Japanese Win XP, I can't input latin-1 accented characters using US keyboard. 
I don't see this problem on IE 6.0 which comes with the system.

Steps to reproduce:
1. Launch browser.
2. Set focus to the URL bar or any other editable field, change keyboard to US.
   Turn on NumLock, press Alt + 0235. it doesn't give me ë char.
Keywords: intl
QA Contact: andreasb → ruixu
Similar to bug 95139?
I don't think so. Bug 95139 is about input latin-1 chars on CJK keyboard, which 
is a common problem on all the windows platforms. This one is about input 
latin-1 on US keyboard, which I think it's XP Ja specific. Marina, do you see 
this problem on English XP?
no, i do not have problem with inputting non-ascii on WinXp en ( would be a
major hassle!), neither do i have this problem on JA NT4.
Yuying and I tested more at this. It's also reproducible on W2K when US 
keyboard/layout is set for Japanese input locale. This type of setting is 
available on W2K and XP. It could be related to bug 95139. I think the fix for 
bug 95139 should include the fix for this possible setting on W2K and XP. 
I'd like to keep this bug open, so we can verify the fix thoroughly.
Summary: Unable to input Latin-1 chars using US keyboard on XP Ja → Unable to input Latin-1 chars using US keyboard with input locale set to JP
this problem ( when keyboard is set to JA locale) was always there ( i never was
able to input accented chars in this case..), don't we have an old bug on this??
Now we have two bugs on it:
bug 95139: JP input locale with Ja keyboard layout.
this bug: JP inputlocale but with US keyboard layout.
Is this related to bug 98134? The problem there sounds like the flipside of the
one described here.
sounds like a major problem.  accepting
Status: NEW → ASSIGNED
Keywords: nsbranch
How many users (need to input non-ASCII latin1 in CJK input locale) do we expect
to be affected?
Are there any workarounds?

Can we reproduce this in the final US XP release with the input locale set to
Japanese?  Could this be an RC2 bug?

Does this work with IE or other apps?

If we switch to the US-International keyboard layout, can enter latin-1 using
the dead-key method?

Is it easy to change to a different input locale on W2K and XP?  (I know you can
easily switch keyboards, but is the only way to change input locales is to use
to the Regional Setting control panel?)
>How many users (need to input non-ASCII latin1 in CJK input locale) do >we
expect to be affected?
Not sure about this, but I would assume there are some Ja users who knows
European languages.
>Are there any workarounds?
The user can input non-ASCII latin1 in EN input locale.

>Can we reproduce this in the final US XP release with the input locale >set to
Japanese?  Could this be an RC2 bug?
Anybody with US XP?

>Does this work with IE or other apps?
Yes. it works fine on IE.

>If we switch to the US-International keyboard layout, can enter >latin-1 using
the dead-key method?
No, it doesn't work either with US-International keyboard.

>Is it easy to change to a different input locale on W2K and XP?  (I >know you
can easily switch keyboards, but is the only way to change >input locales is to
use to the Regional Setting control panel?)
After you add a input locale or keyboard layout from Region Setting control
panel, it's very easy to switch since they show up on the language bar.


First of it is not a WinXP specific problem, it an Nscp6 problem with input
non-ascii chars under JA system or with JA locale. It is reproducable on WinNT
JA, ( i believe with Win98) and i can reproduce it with WinXP US with JA
regional settings.
>Can we reproduce this in the final US XP release with the input locale >set to
Japanese?  Could this be an RC2 bug?
Anybody with US XP?

Input locale set to JA: doesn't work, can't type in 8bit characters
Input locale set to EN: works fine 
Input locale set to DE: works fine

IE 6.0 works fine in all of the above scenarios.
That's all true, though it is not an XP problem, this is mozilla input problem
under JA locale ( reproducable on other systems : JA WinNT for example)
Xianglan (ji) or marina, can you regress this against the commercial 6.0 and 6.1
builds?  I assume it shows the same problem, can you confirm?  Thanks.
I am confirming this problem with 6.01 and 6.1 rtm builds, this goes way back
and is present on all platforms with JA locale
I had a similiar problem when using a Simplified Chinese input locale.
On an iso-8859-1 page, pressing ALT + 0235 gives me a question mark.
i think it is expected from the behavior with JA locale, all double-byte systems
(locale)will have problem inputting accented chars in mozilla, we have to change
the summary of this bug
To summary the problems we have had:
bug 95139: unable to enter latin-1 accented characters on in CJK input locale
with CJK keyboard layout, this is across all the windows platforms including 9x,
ME, W2K and XP.
bug 98376 (this bug): unable to enter latin-1 accented characters in CJK input
locale but with US or US International keyboard laylout. This type of input
locale and keyboard layout setting are available on W2K and XP.

And all these happen on 6.0 and 6.1 as well.

Bug 98736 could be a duplicate of bug 95139 depending on how the fix is implemented.
Summary: Unable to input Latin-1 chars using US keyboard with input locale set to JP → Unable to input Latin-1 chars using US keyboard with input locale set to CJK
Marking nsbranch- as it was decided in the August bug triage that we wouldn't
have enough time in eMojo to fix this.  Let's revisit for MachV.
Keywords: nsbranch-
Oops, this is a new bug.  We should reconsider whether or not it gets a -
Keywords: nsbranch-
marking nsbranch- since it is not a regression. It should be fixed in future
release, though
Keywords: nsbranch → nsbranch-
setting the milestone and priority.
Priority: -- → P1
Target Milestone: --- → mozilla0.9.5
One observation:  WinXP-ja with IE
Typing <Alt> + 0193 shows a Latin Captial Letter A with Acute,
where as  typing <Alt> + 193 shows a single byte katakana 'chi'
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Priority: P1 → P4
Target Milestone: mozilla0.9.6 → Future
I think this bug is P4 Future. Normal user won't know how to do this. BTW, is 
there any Microsoft Help mention such functionality in IME ?
Blocks: 107067
Keywords: nsbranch-
No longer blocks: 107067
Masayuki-san / Jim, you guys have been doing great work on IME/internationalization, any thoughts on this bug?

Resetting assignees due to no work being done for ~7 years.
Assignee: tetsuroy → smontagu
Status: ASSIGNED → NEW
QA Contact: ruixu → i18n
I cannot reproduce this bug on latest trunk build. Probably, this was fixed already.
(In reply to comment #26)
> I cannot reproduce this bug on latest trunk build. Probably, this was fixed
> already.

Resolving WFM per comment #26.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.