Bug 79109 – chart keys do not print properly non-ASCII characters

Bug 79109 - chart keys do not print properly non-ASCII characters

Summary:	chart keys do not print properly non-ASCII characters

Status:	CLOSED WONTFIX

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-12-05 14:54 EST by David Monniaux
Modified:	2014-03-16 22:32 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-01-28 17:18:36 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 David Monniaux 2002-12-05 14:54:27 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
When used in an UTF-8 environment (unsure about other locales): the pie etc..
charts do not display accented characters in account names. Those characters are
just ignored.

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


How reproducible:
Always

Steps to Reproduce:
1.Launch GnuCash over a non-empty set of accounts with expense account names
containing UTF-8 characters
2.Reports -> Profit and loss -> Expense piechart
3.
	

Actual Results:  Captions just skip accented characters

Expected Results:  They should display them properly

Additional info:

This is probably a bug in Guppi.

Comment 1 Bill Nottingham 2005-01-28 17:18:36 EST

This is almost certianly due to the use of GTK+1, which isn't really
utf-8 safe.

Hopefully it will be fixed in the upcoming GNOME 2 port.

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