Bug 1117680

Summary: same keyboard input indicator for Latin input mode and Direct Input mode in libkkc
Product: [Fedora] Fedora Reporter: anish <apatil>
Component: ibus-kkcAssignee: Daiki Ueno <dueno>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 22CC: anish.developer, dueno, i18n-bugs, petersen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 20:06:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description anish 2014-07-09 08:09:56 UTC
Description of problem:
same keyboard input indicator is been used for  Latin input mode and Direct Input mode in libkkc
Better to have separate keyboard indicators.

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

How reproducible:

Steps to Reproduce:
1. Choose libkkc as input method 
2. Switch to Latin input mode or Direct input mode 

Actual results:
You see same input method indicator 

Expected results:

Additional info:

Comment 1 Daiki Ueno 2014-07-10 07:26:36 UTC
What label would you suggest for the direct input mode?

Comment 2 Jaroslav Reznik 2015-03-03 16:07:09 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:

Comment 4 Fedora End Of Life 2016-07-19 20:06:01 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.