Bug 1032442 - [ibus-typing-booster][F20] - Support for the surrounding text needs to be implemented [RFE]
Summary: [ibus-typing-booster][F20] - Support for the surrounding text needs to be imp...
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-typing-booster
Version: 20
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Mike FABIAN
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-11-20 08:34 UTC by Satyabrata Maitra
Modified: 2014-01-29 03:09 UTC (History)
8 users (show)

Fixed In Version: ibus-typing-booster-1.2.9-1.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-01-29 03:04:24 UTC

Attachments (Terms of Use)

Description Satyabrata Maitra 2013-11-20 08:34:17 UTC
Description of problem:
In F20 TC6 as tested, the support for the   surrounding text needs to be implemented.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Add hunspell or typing-booster input source for any locale from Region & 
   Language settings.
   (Here I consider typing-booster:bn-IN or hunspell:bn-IN for example and 
   taken itrans as keymaps)
2. Select the keymaps mentioned in step 1.
3. For example type "baag" and press "SPACE" key
4. Observe the candidate window with predictive words disappears as soon as 
   user press the "SPACE"
5. Now press "LEFT ARROW KEY" once
6. Observe the text.

Actual results:
After step 6, the text does not get selected again to let the same previous candidate window with same predictive word list appeared.

Expected results:
The text should get selected again as before (when user typed "baag") and the same candidate window with the same predictive word list should appear.

Additional info: Even if you press "BACKSPACE" instead of navigation key (LEFT ARROW KEY) the result remains the same.

Comment 1 Pravin Satpute 2013-11-20 08:38:55 UTC
This issue was observed by Krishnababu in testing event we had yesterday. 

So it often happen we do not get exact word suggestions from candidate list and user commit the part of word and try to again edit it.

But during edit itb start showing new suggestion based on last part of word. So having surrounding text will help users to get appropriate suggestion and also appropriate words will get added in user db.

Comment 2 Mike FABIAN 2013-11-20 09:20:22 UTC
Yes, I thought about such a feature as well a while ago.
Would be nice. I’ll try to implement it.

Comment 3 Pravin Satpute 2013-11-21 16:27:04 UTC
Thats nice. I saw the same feature on default predictive IME on Android as well.

Comment 4 Fedora Update System 2014-01-17 16:25:48 UTC
ibus-typing-booster-1.2.9-1.fc20 has been submitted as an update for Fedora 20.

Comment 5 Fedora Update System 2014-01-17 16:27:17 UTC
ibus-typing-booster-1.2.9-1.fc19 has been submitted as an update for Fedora 19.

Comment 6 Fedora Update System 2014-01-18 04:25:10 UTC
Package ibus-typing-booster-1.2.9-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ibus-typing-booster-1.2.9-1.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 7 Mike FABIAN 2014-01-20 07:12:07 UTC
The above change implements the reopening of the preedit only
for backspace, not for the arrow keys. Doing it for the arrow
keys is more difficult, I am still trying to figure out how
to do it. But I wanted to release the fix for backspace because this
works already.

Comment 8 Fedora Update System 2014-01-29 03:04:24 UTC
ibus-typing-booster-1.2.9-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-01-29 03:09:01 UTC
ibus-typing-booster-1.2.9-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.