Bug 62110

Summary:	wrong character set for gnome menu items in kde
Product:	[Retired] Red Hat Linux	Reporter:	Leonid Kanter <leon>
Component:	kdebase	Assignee:	wdovlrrw <brosenkr>
Status:	CLOSED DUPLICATE	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	hp
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-04-06 17:43:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	61590

Description Leonid Kanter 2002-03-27 16:18:51 UTC

Description of Problem:

Looks like bug 51643 is re-implemented in kde3 from beta3, but in new kind: it
currently use iso8859-1 font for non-utf8 menu items (gnome and
/etc/X11/applnk), while must use font in `locale charmap` encoding (KOI8-R in my
case).

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

kdebase-3.0.0-0.cvs20020314.4

How Reproducible:

always

Steps to Reproduce:
1. set LANG=ru_RU.koi8r
2. start kde
3. select Russia, Russian language

Actual Results:

All gnome menu items will be displayed by iso-8859-1 characters.

Expected Results:

For gnome menu must be used the same font which is used for native kde menu
items (cyrillic characters in this case)

Comment 1 Bernhard Rosenkraenzer 2002-03-28 12:58:00 UTC

This is because GNOME doesn't honor the desktop files standard, which clearly 
states desktop files must use UTF-8 encoding.

Comment 2 Havoc Pennington 2002-03-28 13:47:24 UTC

No it doesn't state that. It states that .desktop files may use either UTF-8 or
Legacy-Mixed encoding. Read the spec.

Comment 3 Leonid Kanter 2002-04-06 17:43:33 UTC

I'm unable to reproduce the bug in beta4 (kdebase-3.0.0-3). Everything is OK
with GNOME menu.

Comment 4 Bernhard Rosenkraenzer 2002-04-10 16:35:25 UTC


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