search

ogata0916 / mozc

Automatically exported from code.google.com/p/mozc
0 stars 0 forks source link

Feature request: limit variants #229

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
// Mozc-1.15.1815.102

Type "omosiroi" and space.
You will see these candidates:
> 面白い
> おもしろい
> オモシロイ
> omosiroi
> OMOSIROI
> Omosiroi
> ｏｍｏｓｉｒｏｉ
> ＯＭＯＳＩＲＯＩ
> Ｏｍｏｓｉｒｏｉ
> ｵﾓｼﾛｲ

I think it's too much.

We can limit variants on MS-IME.
http://support.microsoft.com/library/images/support/kbgraphics/public/ja/kblight
/t008/7/10d.gif
http://support.microsoft.com/kb/883192/ja
See "候補一覧に追加で表示する文字種".

Microsoft says:
http://office.microsoft.com/ja-jp/products/HA101818289.aspx
"候補一覧に表示される候補が減るため、目的の候補を選び�
��すくなります。"
I think it's very reasonable.

I know we can limit some variants on Mozc,
but it is not enough.
I unchecked all variants, but Mozc shows 10 candidates for "omosiroi". :-/

Original issue reported on code.google.com by heathros...@gmail.com on 3 Jul 2014 at 8:22

GoogleCodeExporter commented 9 years ago 
I don't think the issue you reported is specific to OSS Mozc.  Can you ask in 
the Google Japanese Input User forum rather than here?  Since OSS Mozc is one 
of downstream projects of Google Japanese Input, I don't think it is reasonable 
to change behavior only in OSS Mozc apart from its upstream project.
Here is the Google Japanese Input User forum:
https://productforums.google.com/forum/#!forum/ime-ja

Note that I guess we have already gotten some similar requests.
https://productforums.google.com/d/msg/ime-ja/ZWMDLEYTFok/kl7YfB5H-8sJ
https://productforums.google.com/d/msg/ime-ja/ujkUHCREcYM/_jmT5dQBLD0J

Also note that there are some historical reasons why we haven't yet addressed 
this issue.  It's actually related to our internal implementation of 
transliteration such as F9 key and F10 key.  For example:
1. Type "omoshiroi"
2. Hit F9 key twice to convert it to "ＯＭＯＳＩＲＯＩ"
Surprisingly, this is internally implemented by pointing the 8th candidate in 
the list you mentioned.  As a result, changing something related to 
transliteration easily breaks existing behavior which makes people really 
upset.  Perhaps it could be an easy task at an early stage of this project but 
now it is supposed to require relatively complicated code change unfortunately. 
 Sorry about that.

Original comment by yukawa@google.com on 3 Jul 2014 at 9:37