Description of problem: The user interface of Fedora Core 5 seems to ignore /etc/sysconfig/i18n. When booting up, the system reads and understands the file, but the desktop environment acts as if it didn't exist and UTF-8 was all the world. When setting the encoding in /etc/sysconfig/i18n to ISO-8859-1, I end up with a mixed system where some programs (wget, svn) think I'm using ISO-88591, and everything else thinks I'm still using UTF-8. Version-Release number of selected component (if applicable): Not applicable. How reproducible: Always. Steps to Reproduce: 1. Edit /etc/sysconfig/i18n by replacing UTF-8 with ISO-8859-1. 2. Reboot. Actual results: The Fedora Core 5 graphic user interface still thinks I'm using UTF-8. All programs with their own graphic user interface do so too. Some programs that are not part of the Fedora Core 5 environment (wget, svn) think I'm using ISO-8859-1. This creates a system incompatible with itself. Expected results: The whole system should have switched to ISO-8859-1. Additional info: I realise everyone and his dog is telling me to switch to UTF-8 for good. However, this is not my decision to make. Our company still uses ISO-8859-1 in both source code and documentation. Because of this, I am unable to do any development work at home.
Can't you mark your source files are being in ISO-8859-1, or force your editor/IDE to use that? FC5 is no longer supported, is this still a problem?
Does this problem occur if you switch to runlevel 3, and use "startx"? If so, see bug #372151
I think Mike is right sounds like bug 372151 for gdm.
Hi, We no longer support Fedora Core 5 and I am currently trying to get my open bug count down to a more manageable state. I'm going to close this bug as WONTFIX. If this issue is still a concern for you, would you mind trying to reproduce on a supported version of Fedora and reopening? (this is a mass message)
The problem I reported in bug #352151 has allegedly been resolved (although I haven't confirmed it yet personally), so you might want to try Fedora 9 or newer which allegedly has the fix. Hope this helps.