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

Change "nn" behavior please #16

Closed
GoogleCodeExporter opened this issue Apr 22, 2015 · 5 comments
Closed

Change "nn" behavior please #16

GoogleCodeExporter opened this issue Apr 22, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

Maybe this is not a bug,
but I don't think it's good for most users.

Type "nihonnouen" and press space => "日本応援"
Type "nihonnouen", press space, press shift + space => "日本のうえん"
(nihon'no|uen, 日本の|うえん)

I think it should be "日本応援" or "日本おうえん".

Original issue reported on code.google.com by heathros...@gmail.com on 19 Jun 2010 at 8:50

@GoogleCodeExporter
Copy link
Author

> Type "nihonnouen", press space, press shift + space => "日本のうえん"

ah,
press space, press shift + "right" => "日本のうえん".

Original comment by heathros...@gmail.com on 26 Jun 2010 at 9:40

@GoogleCodeExporter
Copy link
Author

Thank you for the report. Reproduced on GoogleJapaneseInput-0.11.383.100

Original comment by t...@google.com on 29 Jun 2010 at 4:54

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

We are going to disable Romaji spelling correction feature when user changes 
the word boundary. This change will fix the original issue. However, there 
might be another side effect.

1. User input みんあで
2. Spelling correction feature is invoked and rewrite it to みんなで
3. Shrink the right boundary with shift+left

In this case, the output will become みんあ|で, not みんな|で.
I don't think it is a critical issue and won't fix this side effect. The 
problem here was that user was not able to restore the original input even 
after changing the word boundary. Actually, MS-IME has a similar 
romaji-spelling feature and has the same side effect.

Thanks.

Original comment by t...@google.com on 30 Jun 2010 at 1:32

@GoogleCodeExporter
Copy link
Author

fixed on r32. Please let me know if you have any problems

Original comment by t...@google.com on 1 Jul 2010 at 4:09

  • Changed state: Fixed

shitamo pushed a commit to shitamo/mozc that referenced this issue Jun 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant