Summary: | mc-4.6.1 and 4.6.1-r2 don't display graphical lines on terminal anymore | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Hyman <pete4abw> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Hyman
2006-09-09 13:39:13 UTC
They display just fine when your consolefont/consoletranslation and locales are set correctly. You didn't post any kind of this information, so really hard to guess what's wrong on your side. Also please note that bugzilla is not a support forum. so then, why did it work before 2006.1? I changed no /etc files. # /etc/rc.conf: Global startup script configuration settings # UNICODE specifies whether you want to have UNICODE support in the console. # If you set to yes, please make sure to set a UNICODE aware CONSOLEFONT and # KEYMAP in the /etc/conf.d/consolefont and /etc/conf.d/keymaps config files. UNICODE="yes" # /etc/conf.d/consolefont # CONSOLEFONT specifies the default font that you'd like Linux to use on the # console. You can find a good selection of fonts in /usr/share/consolefonts; # you shouldn't specify the trailing ".psf.gz", just the font name below. # To use the default console font, comment out the CONSOLEFONT setting below. # This setting is used by the /etc/init.d/consolefont script (NOTE: if you do # not want to use it, run "rc-update del consolefont" as root). CONSOLEFONT="default8x16" # CONSOLETRANSLATION is the charset map file to use. Leave commented to use # the default one. Have a look in /usr/share/consoletrans for a selection of # map files you can use. #CONSOLETRANSLATION="8859-1_to_uni" # This file names the list of locales to be built when glibc is installed. # The format is <locale>/<charmap>, where <locale> is a locale from the # /usr/share/i18n/locales directory, and <charmap> is name of one of the files # in /usr/share/i18n/charmaps/. All blank lines and lines starting with # are # ignored. Here is an example: # en_US/ISO-8859-1 en_US/ISO-8859-1 en_US.UTF-8/UTF-8 ja_JP.EUC-JP/EUC-JP ja_JP.UTF-8/UTF-8 ja_JP/EUC-JP en_HK/ISO-8859-1 en_PH/ISO-8859-1 de_DE/ISO-8859-1 de_DE@euro/ISO-8859-15 es_MX/ISO-8859-1 fa_IR/UTF-8 fr_FR/ISO-8859-1 fr_FR@euro/ISO-8859-15 it_IT/ISO-8859-1 Sigh, post the output of locale command, not what you have built in glibc. http://permalink.gmane.org/gmane.linux.gentoo.user/169818. This thread adds some color. For some reason, my locale is blank. Why would that be? When I recompiled glibc, it went through a lot of languages. 151 of them. peter@mars ~ $ locale LANG= LC_CTYPE="POSIX" LC_NUMERIC="POSIX" LC_TIME="POSIX" LC_COLLATE="POSIX" LC_MONETARY="POSIX" LC_MESSAGES="POSIX" LC_PAPER="POSIX" LC_NAME="POSIX" LC_ADDRESS="POSIX" LC_TELEPHONE="POSIX" LC_MEASUREMENT="POSIX" LC_IDENTIFICATION="POSIX" LC_ALL= Wonderful. So why are you setting UNICODE="yes" if your locale is POSIX??? http://www.gentoo.org/doc/en/utf-8.xml Hi Jakub, I can add a "me too" here. Manually adding /etc/env.d/02locale with the lines suggested in the gentoo doc is pretty much what I had to do to fix things up for MC. Running env-update and source /etc/profile finished it up. The thing that I don't understand is, why did it work correctly before my move to 2006.1? the 02locale file should have been created by... especially if localization is going to be the norm. By the way, setting UNICODE to "no" had no effect on the way mc was being effected. (In reply to comment #6) > the 02locale file should have been created by... By what? And how? Using some random guess? Sorry, setting up locales correctly is users' job. (In reply to comment #7) > (In reply to comment #6) > > the 02locale file should have been created by... > > By what? And how? Using some random guess? Sorry, setting up locales correctly > is users' job. > Yes, it is. Unfortunately, for over two years, I was happily running without incident. So, by updating to the 2006.1 profile, this problem occured. So, on the one hand, I was ignorant, but on the other hand, it was working fine without any user intervention. So, at the least, there should be some information for users to set LANG and LC_? so that programs will function as expected at the console. JM2C. |