Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 24342

Summary:	Non-ASCII characters in translated messages aren't shown correctly
Product:	[Retired] Red Hat Linux	Reporter:	Göran Uddeborg <goeran>
Component:	gnupg	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED DUPLICATE	QA Contact:	Aaron Brown <abrown>
Severity:	low	Docs Contact:
Priority:	medium
Version:	7.0
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:	2001-01-20 23:45:50 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:

Description Göran Uddeborg 2001-01-19 09:17:34 UTC

Recent versions of gnupg, like 1.0.4-9, includes translated messages. 
Recent versions of gettext, like that from glibc 2.2, translates fetched
messages to the used character set.  If no character set has been choosen
with setlocale(LC_CTYPE, ...), a plain US-ASCII is assumed.  Any characters
not in this set is replaced with question marks.  This happens to the
Swedish messages for gpg.

The 1.0.4-9 SRPM includes a patch for this, gnupg-1.0.2-locale.patch (patch
#0).  But for some reason this patch isn't applied.  Why not?

Comment 1 Nalin Dahyabhai 2001-01-20 23:45:46 UTC

GnuPG depends on collation data for the C locale, so the patch would cause
things to break.  We kept it in the package for future reference.

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