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

部首のバグ修正と改善 #1169

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

faketanaka
Copy link

@faketanaka faketanaka commented Jan 31, 2025

Description

Issue IDs

#653

Copy link

google-cla bot commented Jan 31, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@faketanaka
Copy link
Author

CLAについてですが,当方Googleアカウントを保有していません.なにかできることはございますか.

@hiroyuki-komatsu
Copy link
Collaborator

Thank you for sending the PR.

CLA is a required process to accept PRs due to the repository policy.
I'm not sure if you can sign CLA without Google account.

Thank you for your cooperation.

@faketanaka
Copy link
Author

わかりました。Googleアカウントを作成しますのでお待ちいただければ幸いです。


所属組織のGitHubアカウントで返信してしまったため再投稿です。

@faketanaka
Copy link
Author

Googleアカウントにログインし、CLAに同意いたしましたのでご報告いたします。

@hiroyuki-komatsu
Copy link
Collaborator

Hi faketanaka,
Thank you for your PR.

I agree that there is a room to improve radical related conversions as discussed in #653. On the other hand, a number of radical characters look quite similar to normal characters. For example, ⾚ (U+2F9A) as a Kangxi radical (康煕部首) looks identical to 赤 (U+8D64) as a normal kanji.

Therefore, we would like to avoid confusing users from two similar characters, even though the radical one has some descriptions. Some environments may not show those descriptions.

So we would like to avoid too generic readings for radical characters (e.g. あか for ⾚ [U+2F9A]). Please remove those readings from radical characters and keep readings that the users can intentionally type radical characters.

@faketanaka
Copy link
Author

So we would like to avoid too generic readings for radical characters (e.g. あか for ⾚ [U+2F9A]). Please remove those readings from radical characters and keep readings that the users can intentionally type radical characters.

これは変換候補の右側に表示されるコメントのことではなく、「あか」と入力して部首のあかが表示されるのは混乱を招くため、候補を出すためのキーワードを改善する必要がある、ということでしょうか。

私はこの問題に対する対応は #1165 で十分であると考えておりました。具体的にどのような入力で表示されるのがいいか、なにか案はないでしょうか。例えば「ぶしゅのあか」で候補に出すといったことが考えられますが、「ぶしゅのあか」というキーワードが適切かどうかは私一人では判断できかねます。

@hiroyuki-komatsu
Copy link
Collaborator

"ぶしゅのあか" sounds good to me too. Please be informed that I possibly ask you other ways again during the internal review process.

私はこの問題に対する対応は #1165 で十分であると考えておりました。

Indeed, I should have noticed this confusion beforehand while reviewing in #1165.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants