Does this happen for all searches?
** Changed in: ubuntu-keyboard (Ubuntu)
Importance: Low = High
** Also affects: ubuntu-keyboard
Importance: Undecided
Status: New
** Changed in: ubuntu-keyboard
Importance: Undecided = High
** Changed in: ubuntu-keyboard
Assignee:
** Changed in: ubuntu-keyboard
Status: New = Fix Released
** Changed in: ubuntu-keyboard (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282433
Thanks for reporting this, a fix for this has been released in recent
images. Requests by text fields to disable predictive text are now
ignored by the Pinyin keyboard, since this is required for Pinyin input
under any circumstances.
--
You received this bug notification because you are a member
** Package changed: ubuntu-system-settings (Ubuntu) = ubuntu-keyboard
(Ubuntu)
** Changed in: ubuntu-keyboard (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does Pinyin use preedit?
System Settings search field set inputMethodHints: Qt.ImhNoPredictiveText.
This means that OSK disable WordPrediction and disalbe preedit too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
yes, my issue is that keyboard doesn't offer to input chinese characters
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282433
Title:
System setting is not able to search by Chinese
To manage
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New = Incomplete
** Changed in: ubuntu-system-settings (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Do you mean that the keyboard doesn't offer you chinese characters to
input? Or that it does and the application doesn't filter by the entered
Chinese correctly?
The former is probably a bug in the OSK, if that's what you mean. That's
the behaviour I get if I try to reproduce this locally.
--
