Bug 2307 - Key binding representation shown in uim-pref should be proper
Summary: Key binding representation shown in uim-pref should be proper
Status: RESOLVED FIXED
Alias: None
Product: UIM
Classification: Unclassified
Component: libuim (show other bugs)
Version: unspecified
Hardware: All All
: high major
Assignee: uim-bugs
QA Contact:
URL: http://lists.freedesktop.org/archives...
Whiteboard:
Keywords:
Depends on:
Blocks: 2304 2311
  Show dependency treegraph
 
Reported: 2005-01-18 02:01 UTC by YamaKen
Modified: 2005-02-10 15:59 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description YamaKen 2005-01-18 02:01:34 UTC
Key binding representation shown in uim-pref is having following problems.

- " " should be shown as "space"
- "<Control>g" and "<Control>G" should be unified
- "," as key should be distinguishable from separator character

These problems should be resolved in relation with uim-custom and libuim
implementation.
The translation prefix <IgnoreCase> and <IgnoreShift> will help the solution.
I'll suggest particular plan later.
Comment 1 YamaKen 2005-01-27 19:13:37 UTC
"space" problem has been fixed by r371.
Comment 2 YamaKen 2005-01-30 17:03:27 UTC
r390 had resolved following problem.

- "<Control>g" and "<Control>G" should be unified

Last one problem is remaining. It's a uim-pref layer problem. Hiroyuki, Takuro
or Kazuki, can this problem be fixed easily? If no, close this bug.

- "," as key should be distinguishable from separator character
Comment 3 YamaKen 2005-02-03 00:30:53 UTC
Can "," be colorized?
Comment 4 Takuro Ashie 2005-02-03 12:18:04 UTC
From commit log of r506:

* helper/pref-gtk.c:
  - (olist_pref_entry_set_value): Quote each item of list and put space
    after separator(comma) to make easy to recognize. Although I don't         
     
    think that it is the best way, I think it is better than before.
  - (key_pref_entry_set_value): Same with above.
Comment 5 Takuro Ashie 2005-02-11 10:59:21 UTC
Further fix mey be difficult at this time.
I close this bug.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.