| Summary: | dialog screen is distorted with unicode | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | André Terpstra <andre> |
| Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | minor | CC: | jakub, tools-portage, truedfx |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Root .profile file
Simple dialog test script UFED screen shot Consolefont config file UFED console screen shot with latw9-16 |
||
|
Description
André Terpstra
2005-04-12 02:30:33 UTC
This is probably caused by having unicode enabled in your config files. If you did that, you also need to set LANG to (for example) en_US.UTF-8 so that the dialog tool knows how to display the checklist. Also, in case you run ufed using sudo, make sure that it doesn't unset that. Even if that isn't it, though, ufed doesn't display the menu itself - it simply calls dialog - so it can't really be caused by ufed. You should see the same behaviour by running dialog --yesno '' 0 0 directly. However, if that does work, but ufed still doesn't, there must indeed be a bug in ufed, and in that case, please re-open. Thanks for the quick reply! An example to other bug reports IMHO. Anyway, you were right that it is a dialog problem, so I've changed the bug title and reopened it. Right now I'm trying your other suggestions. Well there's been some improvement, after create a .profile file. I'm doing this following the Gentoo UTF-8 guide http://www.gentoo.org/doc/en/utf-8.xml but am logged in as root, although this is not recommended. The display is more readable but the characters "[]()" aren't displayed correctly. This points to a character set problem I think. Maybe someone has some good advice otherwise this bug may be closed again. Okay, that's not really my thing. Can you provide more detailed information on what you did, so that I may be able to reassign this bug to whoever handles what specifically is causing your problem? Just an idea - does running unicode_start fix this? Created attachment 56155 [details]
Root .profile file
Created attachment 56156 [details]
Simple dialog test script
Jakub: thanks for your help but no that didn't change anything. Perhaps some more info. I've created a profile file (attachment #1 [details]) and a simple dialog test script (attachment #2 [details]). Without the .profile file both the dialog box edges and some of the text inside do not appear correctly, some of it is displayed twice. When I create the .profile file and logout and login again, the text inside is displayed OK, but the edges are shown as strange characters. Some screen output would probably be helpful but I have no idea how to create that from within a command prompt. Ah, if that's the problem, you may be using a font that simply doesn't include these characters, or you didn't set CONSOLETRANSLATION correctly. If you're using a font other than the default, try changing it back to the default (default8x16, CONSOLETRANSLATION not necessary), run /etc/init.d/consolefont restart, and see if it works then. Since this now very much seems like a configuration problem rather than an actual bug, I'll close it again, but if it still doesn't work after that, please reopen, provide your /etc/rc.conf and/or /etc/conf.d/consolefont (whichever is appropriate), as well as a screenshot (using media-gfx/fbgrab). Created attachment 56185 [details]
UFED screen shot
Created attachment 56186 [details]
Consolefont config file
So I've been experimenting along your suggested line of thought. As I still have no problems from within KDE it must de be some font problem. I've added a CONSOLETRANS statement (attachment #56186 [details]) but that doesn't change much (attachment #56185 [details]). I'll keep experimenting, but I wish the Unicode guide was more complete... To me, it seems that if it doesn't get characters right with the default font, yet you've made sure you enabled unicode and set the environment correctly, that's a problem with either kbd (the fonts) or ncurses, so I'm reassigning this to base-system. Please take a look. default font isnt supposed to cover unicode if the guide is incomplete, see the other bugs on bugzilla to get it updated ive never used unicode, but it seems to me that if you enable unicode support and dont change fonts / keymaps to support unicode, that's partly your fault and partly the guide's fault for not covering it You're partly wrong. I originally had enabled a Unicode-aware font (lat9w-16) as suggested by the UTF-8 guide (strange, that particular lines seems to have disappeared now). That's where the problems started and I went experimenting. Anyway here's a screen shot that font. Created attachment 56339 [details]
UFED console screen shot with latw9-16
so whats the issue here ? you tried to use a font that's supposed to support unicode (lat9w-16) and it didnt seem to work ? do any console fonts work ? did you emerge ncurses with USE=unicode ? did you set UNICODE=yes in /etc/rc.conf ? rather than setting up stuff in ~/.profile, try exporting the vars yourself and see if dialog still draws weird on the console ... No user response here. |
