Bug 75589 - redhat-config-xfree86 uses wrong decimal character
Summary: redhat-config-xfree86 uses wrong decimal character
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-xfree86 (Show other bugs)
(Show other bugs)
Version: 8.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On: 75621
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-10 00:21 UTC by Christian Rose
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-10 00:22:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screenshot showing use of wrong decimal characters (34.33 KB, image/png)
2002-10-10 00:22 UTC, Christian Rose
no flags Details

Description Christian Rose 2002-10-10 00:21:52 UTC
Tested with RHL 8.0 and using sv_SE.UTF-8.

redhat-config-xfree86 uses the wrong decimal character (point instead of comma)
in the monitor frequencies section, both in input and display (see screenshot).
This locale's decimal character is comma.

Comment 1 Christian Rose 2002-10-10 00:22:46 UTC
Created attachment 79720 [details]
Screenshot showing use of wrong decimal characters

Comment 2 Alexander Larsson 2002-10-10 09:14:50 UTC
This is an unfortunate problem with python. The python environment fails if you
change the numeric locale, so pygtk2 automatically sets it to C.


Comment 3 Christian Rose 2002-10-10 09:46:25 UTC
Should I file a bug report against python?

Comment 4 Alexander Larsson 2002-10-10 09:59:28 UTC
pygtk does:

    /* set the LC_NUMERIC locale back to "C", as Python requires that
     * it be set that way. */
    setlocale(LC_NUMERIC, "C");

I'm not sure this can be fixed, but maybe it can.


Comment 5 Alexander Larsson 2002-10-10 10:00:38 UTC
Easiest would be to just ask jamesh if this is fixable.


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