Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All IME's don't work (Chinese/Japanese/Korean input, Emoji Picker, etc.) #2213

Closed
ZedG2 opened this issue Aug 3, 2019 · 51 comments · Fixed by #1919
Closed

All IME's don't work (Chinese/Japanese/Korean input, Emoji Picker, etc.) #2213

ZedG2 opened this issue Aug 3, 2019 · 51 comments · Fixed by #1919
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.
Milestone

Comments

@ZedG2
Copy link

ZedG2 commented Aug 3, 2019

Environment

Microsoft Windows [版本 10.0.18362.267] 
Windows Terminal version (if applicable):0.3.2142.0

Steps to reproduce

  1. Open the terminal.
  2. Switching CJK input methods.(doesn't work)
  3. Typing.

Expected behavior

Show phrase candidate boxes.

Actual behavior

Directly entered English.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Aug 3, 2019
@klesh
Copy link

klesh commented Aug 4, 2019

Microsoft Windows [Version 10.0.18362.239]
Version: 0.3.2142.0

I'm having the same problem here.

@yuchenyang1994
Copy link

Microsoft Windows [Version 10.0.18950.1000]
Version: 0.3.2142.0

i'm having the same problem here.

@etern
Copy link

etern commented Aug 5, 2019

Same here, as I remember, it works fine in Preview-0.2

@Z-H-Sun
Copy link

Z-H-Sun commented Aug 6, 2019

Likewise. IME selection was supported in version 0.2

@techloghub
Copy link

techloghub commented Aug 8, 2019

Microsoft Windows [Version 10.0.18362.267]
Version: 0.3.2171.0

I'm having the same problem here, I can't input Chinese in it.

@zadjii-msft
Copy link
Member

I'd think that @philnach might have some thoughts in this area. I believe #1919 might improve this dramatically. I'd be curious to find out what caused this to regress since 0.2. Maybe something from @carlos-zamora's accessibility work slightly regressed this as an unexpected side-effect?

(also related #459)

@zadjii-msft zadjii-msft added Area-Input Related to input processing (key presses, mouse, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. labels Aug 8, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 8, 2019
@zadjii-msft zadjii-msft added this to the Terminal v1.0 milestone Aug 8, 2019
@spindensity
Copy link

Microsoft Windows [Version 10.0.18362.267]
Windows Terminal version: v0.3.2171.0 installed from Microsoft Store.

Same problem here.

@wrvsrx
Copy link

wrvsrx commented Aug 12, 2019

Microsoft Windows [Version 10.0.18956.1000]
Windows Terminal version: v0.3.2171.0 installed from Microsoft Store.

Can't input Chinese character in windows terminal.

@etern
Copy link

etern commented Aug 12, 2019

Hi developers, I notice that this issue is added to milestone Terminal v1.0, which is Due by April 30, 2020.
Would you consider fix this a little earlier? I think IME is of great use in non-english countries.

@zadjii-msft
Copy link
Member

@etern Yea this is certainly a higher priority task for us than that milestone lets on. Unfortunately we only really have milestones for "things we're getting done in the current month", "things we need by 1.0", and "things that can wait till after 1.0". I don't think we're going to be able to fix this by the end of the month, hence why it's parked on the 1.0 milestone currently.

@DHowett-MSFT DHowett-MSFT removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Aug 12, 2019
@strega-nil
Copy link
Contributor

This also affects the emoji picker afaict.

@zhoupro
Copy link

zhoupro commented Sep 2, 2019

Uninstall v0.4, download v0.2 from assets.

@Yang-ZG
Copy link

Yang-ZG commented Nov 19, 2019

os: 19013
terminal version: 0.6.2951.0

Same problem

@leadscloud
Copy link

同样的问题,这bug这两天还有人一直提问题,我记得这软件出来好久了
os: win10 1909 18363.476
terminal version: 0.6.2951.0

@namewalt
Copy link

无法使用任何输入法,更不能输入中文

@dbwodlf3
Copy link

why closed? it is still a problem!

@hez2010
Copy link

hez2010 commented Nov 23, 2019

why closed? it is still a problem!

It has been fixed but the newer build hasn't shipped to Windows Store yet.

@sidian123
Copy link

same question, why closed ? i encounter the same problem, cannot input chinese character

@hez2010
Copy link

hez2010 commented Nov 23, 2019 via email

@dbwodlf3
Copy link

dbwodlf3 commented Nov 23, 2019

It has been fixed, but the build was not shipped to Windows Store yet.

aha.. okay. thanks reply.

@Green1ee
Copy link

When can i get the newer from Windows Store.

@DHowett-MSFT
Copy link
Contributor

You can get the newer version when it is released.

@Green1ee
Copy link

You can get the newer version when it is released.

ha,so when?

@ghost ghost added the Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. label Nov 26, 2019
@JushBJJ
Copy link

JushBJJ commented Nov 26, 2019

@Green1ee 30th of November. Only a few days left!

@ghost
Copy link

ghost commented Nov 26, 2019

🎉This issue was addressed in #1919, which has now been successfully released as Windows Terminal Preview v0.7.3291.0.:tada:

Handy links:

@DHowett-MSFT DHowett-MSFT unpinned this issue Nov 26, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Nov 26, 2019
@luochen1990
Copy link

I updated and it works well, hooray!

@seonk
Copy link

seonk commented Nov 27, 2019

Upgraded, Chinese input method can be used, but the continuous input of several sentences is 100% crashed. Is it a bug or a problem with my computer settings? (using Google Translate)

@seonk
Copy link

seonk commented Nov 27, 2019

Reset the app and the problem persists. The Chinese input method has been changed to Microsoft Pinyin, and it has not crashed so far. However, to input punctuation marks, you need to double-click consecutively to input correctly. No symbol is displayed when you click it. (Still using Google Translate)

@zhoupro
Copy link

zhoupro commented Nov 28, 2019

I update it, It crash 100%.

@foriequal0
Copy link

Korean input also doesn't work for https://github.com/microsoft/terminal/releases/tag/v0.8.10261.0
For example, If I type "한글이 안돼" (It messes up Korean doesn't work), with 2-beolsik Microsoft IME,
It normally shown as these sequences in the screen (A character with _ means it is in the composition, v means space bar)

ㅎ_
하_
한_
한ㄱ_
한그_
한글_
한글ㅇ_
한글이_
한글이v
한글이 ㅁ_
한글이 마_
한글이 망_
한글이 망ㄱ_
한글이 망가_
한글이 망갖_ # Notorious 2-beolsik phantom character phenomenon. Koreans are used to this. This is not a problem.
한글이 망가져_
한글이 망가져v
한글이 망가져 ㅇ_
한글이 망가져 아_
한글이 망가져 안_
한글이 망가져 안ㄷ_
한글이 망가져 안도_ # Some middle vowel characters are also composed themselves, not only consonants and vowels(가), and vowels(않).
한글이 망가져 안돼_
한글이 망가져 안돼v

However, in Terminal,

ㅎ_
하_
한_ # works well for the first character after the ascii charcter
한ㄱ_
한그ㄱ # Weird things starts. compositioning cursor disappears
한그ㄱ글_ # reappear cursor
한그ㄱ글ㅇ_
한그ㄱ글이ㅇ
한그ㄱ글이ㅇ이_
한그ㄱ글이ㅇ이v
한그ㄱ글이ㅇ이 ㅁ_
한그ㄱ글이ㅇ이 마_
한그ㄱ글이ㅇ이 망_
한그ㄱ글이ㅇ이 망ㄱ_ 
한그ㄱ글이ㅇ이 망가ㄱ # again
한그ㄱ글이ㅇ이 망가ㄱ갖_ # reappear
한그ㄱ글이ㅇ이 망가ㄱ가져_ # sometimes 가 and 져 is overlayed in the same place.
한그ㄱ글이ㅇ이 망가ㄱ가져져v # sometimes 가 and 져 is overlayed in the same place.
한그ㄱ글이ㅇ이 망가ㄱ가져져 ㅇ_
한그ㄱ글이ㅇ이 망가ㄱ가져져 아_
한그ㄱ글이ㅇ이 망가ㄱ가져져 안_
한그ㄱ글이ㅇ이 망가ㄱ가져져 안ㄷ_
한그ㄱ글이ㅇ이 망가ㄱ가져져 안도 # again
한그ㄱ글이ㅇ이 망가ㄱ가져져 안도ㄷ_ # reappear
한그ㄱ글이ㅇ이 망가ㄱ가져져 안도ㄷ돼_
한그ㄱ글이ㅇ이 망가ㄱ가져져 안도ㄷ돼v

@simnalamburt
Copy link

@foriequal0 That issue is currently being tracked in #4226

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.