Bug 135363 - [KDE][xcin] display only partial status window
Summary: [KDE][xcin] display only partial status window
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: iiimf-le-xcin
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Leon Ho
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: IIIMF
TreeView+ depends on / blocked
 
Reported: 2004-10-12 08:18 UTC by Lawrence Lim
Modified: 2014-03-26 00:51 UTC (History)
2 users (show)

Fixed In Version: iiimf-le-xcin-0.1.7-8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-19 07:08:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
take notice of the status window of xcin (187.76 KB, image/png)
2004-10-12 08:19 UTC, Lawrence Lim
no flags Details

Description Lawrence Lim 2004-10-12 08:18:43 UTC
Description of problem: 
In the KDE environment, xcin can only display the status window 
partially. In fact, only the first character is displayed in the 
status window. 
 
Version-Release number of selected component (if applicable): 
- iiimf-le-xcin-0.1.7-6 
- kdebase-3.3.0-7 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1.in gdm, login as normal user with traditional chinese / kde session 
2.after run kde, press alt-f2 to run dialog 
3.ctrl-space to activiate LE 
   
Actual results: 
xcin only display the status window partially (only the first 
character can be displayed) 
 
Expected results: 
xcin display the whole status window 
 
Additional info: 
Tested with chinput LE and all four characters can be displayed 
properly

Comment 1 Lawrence Lim 2004-10-12 08:19:38 UTC
Created attachment 105052 [details]
take notice of the status window of xcin

Comment 2 Leon Ho 2004-10-15 06:55:20 UTC
Thanks for the report Lawrence. Please confirm in rawhide.

Comment 3 Lawrence Lim 2004-10-19 07:08:01 UTC
Confirmed fixed. Tested with iiimf-le-xcin-0.1.7-8. All the characters
are now displayed properly in the status window, some of which has 4
charcaters.


Thanks.


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