Bug 149849 - YaST don't handle Japanese letters correctly
Summary: YaST don't handle Japanese letters correctly
Status: RESOLVED DUPLICATE of bug 53173
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Stanislav Visnovsky
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-10 05:14 UTC by Shinkichi Yamazaki
Modified: 2006-02-22 06:43 UTC (History)
0 users

See Also:
Found By: i18n Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
YaST screen shot. (61.40 KB, image/png)
2006-02-10 05:19 UTC, Shinkichi Yamazaki 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shinkichi Yamazaki 2006-02-10 05:14:26 UTC 
Japanese messages in YaST is partly broken.
Comment 1 Shinkichi Yamazaki 2006-02-10 05:19:15 UTC 
Created attachment 67484 [details]
YaST screen shot.

This image open with 10.1 on terminal, start YaST and select
Software -> Software Management.
Comment 2 Michael Gross 2006-02-13 14:22:12 UTC 
Does this work with the graphical interface? Are these broken letters all over YaST or only in the software management module?
Comment 3 Shinkichi Yamazaki 2006-02-14 01:11:58 UTC 
This works with YaST2 graphical interface. 
The chracter break occurs with YaST and all over YaST module.
Comment 4 Michael Gross 2006-02-14 11:30:25 UTC 
Ok then this appears to be a ncurses-specific problem. Please attach the logfiles (/var/log/YaST2/*).
Comment 5 Shinkichi Yamazaki 2006-02-14 12:04:14 UTC 
Created attachment 68310 [details]
log file in /var/log/YaST2/

Ok, uploaded YaST2 log files. All files in YaST2 is huge so I uploaded the latest YaST2 log file.
Comment 6 Michael Gross 2006-02-14 14:34:30 UTC 
I suppose the private state of the last comment was not intended ;)
Stanislav: Please look into this.
Comment 7 Stanislav Visnovsky 2006-02-22 06:43:27 UTC 

*** This bug has been marked as a duplicate of 53173 ***