Bug 62364 – konsolekalendar prints dates as "???" when non-ASCII locale is used

Bug 62364 - konsolekalendar prints dates as "???" when non-ASCII locale is used

Summary:	konsolekalendar prints dates as "???" when non-ASCII locale is used

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	wdovlrrw
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	61901
	Show dependency tree / graph

Reported:	2002-03-30 04:25 EST by Aleksey Nogin
Modified:	2007-04-18 12:41 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-04-10 12:53:06 EDT
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 appropriate .local8Bit() (824 bytes, patch) 2002-03-30 04:26 EST, Aleksey Nogin	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Aleksey Nogin 2002-03-30 04:25:42 EST

konsolekalendar forgets to do .local8Bit() on some of the strings it prints
resulting in dates being printed as "???" when I use it under LANG=ru_RU.KOI8-R.
I'll attach a patch in a minute.

P.S. Should I attempt to report these things to bugs.kde.org (I wish they'd use
Bugzilla!) instead of (or in addition to) doing it here?

Comment 1 Aleksey Nogin 2002-03-30 04:26:46 EST

Created attachment 51444 [details]
add appropriate .local8Bit()

Comment 2 Aleksey Nogin 2002-04-01 17:05:00 EST

A patch for this was checked in to CVS today, but that was post-3.0 if I
understand correctly.

Comment 3 Bernhard Rosenkraenzer 2002-04-10 12:53:01 EDT

Right. I've just applied it to KDE_3_0_BRANCH in CVS.

Comment 4 Bernhard Rosenkraenzer 2002-04-10 13:09:46 EDT

Added in the 3.0.0-2 package.

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