Bug 29136 – Japanese messages in the logout confirmation dialog get scrambled

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 29136 - Japanese messages in the logout confirmation dialog get scrambled

Summary:	Japanese messages in the logout confirmation dialog get scrambled

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kdebase (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:	Aaron Brown
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-02-23 16:03 EST by Satoru SATOH
Modified:	2007-04-18 12:31 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-03-05 00:17:28 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Satoru SATOH 2001-02-23 16:03:31 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.1-0.1.9 i686; ja-JP; 0.7)
Gecko/20010220


When I try to logout the KDE desktop, the dialog window that confirm me
whether logout or not is appeared. Although other Japanese messages in KDE
menu and dialogs are displayed correctly, the Japanese messages of that
dialog window get scrambled.

Reproducible: Always
Steps to Reproduce:
1.set LANG to ja_JP.eucJP
2.login the KDE desktop
3.logout the desktop

	

Actual Results:  The confirmation dialog window appeared and the messages
of that get scrambled.

Expected Results:  The Japanese messages displayed correctly :)

Comment 1 Glen Foster 2001-02-23 16:56:04 EST

We (Red Hat) should really try to resolve this before next release.

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