Bug 89446
Summary: | Default font not loaded in non-unicode locale | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Carlos Rodrigues <cefrodrigues> | ||||
Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 9 | CC: | rvokal | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | athlon | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-09-29 20:37:54 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: | |||||||
Attachments: |
|
Description
Carlos Rodrigues
2003-04-22 22:54:38 UTC
Created attachment 93182 [details]
loads console font even when the locale is not unicode
I changed the lang.sh and lang.csh scripts a bit to load the default console
font even when the locale is not unicode.
This shouldn't be necessary; what problem are you seeing without this? Fonts don't really need to be called for each console; setting it once should suffice (the reason unicode_start is called is because there are other issues that it takes care of.) I'm defining the font lat9w-16 for the console because it has accented characters (like á for instance). But (without my changes to lang.sh) it is only defined for the first vt, so, if I press "´ + a" in the first vt I see "á", but if I do the same in the other vt's I see "a". I made a little mistake in my previous comment. Actually "á" (á) displays ok but some characters which have a tilde - like "ã" (ã) and "õ" (õ) do not. Besides this small detail (maybe next time I will reproduce the problem again instead of trusting my memory of it) my point remains the same. *** Bug 75564 has been marked as a duplicate of this bug. *** Closing bugs on older, no longer supported, releases. Apologies for any lack of response. I suspect this was due to a kernel bug, which we worked around in previous releases. The kernel bug was fixed in 2.6.13 and later. |