Re: [gentoo-user] Re: X bitmap fonts and UTF-8
So, nobody knows what can this be? I even tried to recompile dmenu with Xutf8* functions instead of Xmb*, and this didn't help.
[gentoo-user] X bitmap fonts and UTF-8
Hi. I have some strange problem with X fonts (not freetype). I installed xmonad, dzen2 and dmenu and configured the last two to use font -xos4-terminus-medium-*-*-*-12-*-*-*-*-*-iso10646-1 (but I have this problem in other fonts too) because I need the unicode for correct display of russian letters (i have ru_RU.UTF-8 locale, so koi8-r is not my option). But russian text looks very strange. The text from xmonad (for example, window captions) contains one symbol per one russian letter, but it is not correct - something like 0?8A0BL ?8AL . In the text in dmenu (or in dzen2 when I pipe output from echo to it on the console) the letters are not displayed as hieroglyphs or strange symbols; each letter consists of an ' (apostrophe sign) and one symbol from ASCII table from Q up to q (33 chars totally). I have found no correspondence between UTF-8 bytes and these pairs (but the first byte in russian letters is also the same). The same configuration of xmonad and dzen2 on my other machine (ubuntu) works perfectly, and the text in xterm and emacs also looks very well. What can this be? Sorry for my bad language if it is such :)
Re: [gentoo-user] Re: X bitmap fonts and UTF-8
Yes, of course. There are unicode and utf8 in make.conf and UNICODE=yes in rc.conf. 2009/10/14 walt w41...@gmail.com: On 10/14/2009 07:00 AM, DPX-Infinity wrote: Hi. I have some strange problem with X fonts (not freetype). I installed xmonad, dzen2 and dmenu and configured the last two to use font -xos4-terminus-medium-*-*-*-12-*-*-*-*-*-iso10646-1 (but I have this problem in other fonts too) because I need the unicode... Do you have the 'unicode' USE flag set? I think it may be on by default, but I'm not sure.
Re: [gentoo-user] Re: X bitmap fonts and UTF-8
No, they are entirely same. 2009/10/14 walt w41...@gmail.com: On 10/14/2009 12:17 PM, DPX-Infinity wrote: Here are mine: Installed versions: 4.28(23:40:35 09.10.2009)(X pcf psf ru-dv ru-g ru-i -a-like-o -bolddiag -quote -raw-font-data -ru-k -width) But I think USE-flags aren't connected with this strange behaviour. I already said, that russian letters are not displayed in every font, including misc-fixed, for example. I also tried original (from official site) fonts, but the result was the same. Definitely fonts are not the reason. I've attached a screencap of what I see using misc-fixed. Do you see something different? attachment: xfontsel.png
Re: [gentoo-user] Problem emerging alsa-utils-1.0.20-r4
2009/8/15 Mick michaelkintz...@gmail.com I seem to have the same problem like this bug report: http://bugs.gentoo.org/show_bug.cgi?id=281434 which I am not sure why it has been marked as resolved/invalid. This is what happens: Emerging (1 of 1) media-sound/alsa-utils-1.0.20-r4 * alsa-utils-1.0.20.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ...[ ok ] * checking miscfile checksums ;-) ... [ ok ] * Obsolete config /etc/modules.d/alsa found. * * ERROR: media-sound/alsa-utils-1.0.20-r4 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * alsa-utils-1.0.20-r4.ebuild, line 34: Called die * The specific snippet of code: * die Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * The die message: * Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/media-sound:alsa-utils-1.0.20-r4:20090814-200133.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/alsa-utils-1.0.20-r4/temp/die.env'. Have you had such a problem? What's the fix? I have both files mentioned: # ls -la /etc/modules.d/alsa -rw-r--r-- 1 root root 202 Jan 5 2009 /etc/modules.d/alsa # ls -la /etc/modprobe.d/alsa.conf -rw-r--r-- 1 root root 1028 Jul 4 09:27 /etc/modprobe.d/alsa.conf -- Regards, Mick Obviously, the existence of /etc/modules.d/alsa does not allow emerge to continue. I think you must merge alsa file to alsa.conf and then delete alsa.
Re: [gentoo-user] Problem emerging alsa-utils-1.0.20-r4
2009/8/15 Mick michaelkintz...@gmail.com On Friday 14 August 2009, DPX-Infinity wrote: 2009/8/15 Mick michaelkintz...@gmail.com I seem to have the same problem like this bug report: http://bugs.gentoo.org/show_bug.cgi?id=281434 which I am not sure why it has been marked as resolved/invalid. This is what happens: Emerging (1 of 1) media-sound/alsa-utils-1.0.20-r4 * alsa-utils-1.0.20.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * Obsolete config /etc/modules.d/alsa found. * * ERROR: media-sound/alsa-utils-1.0.20-r4 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * alsa-utils-1.0.20-r4.ebuild, line 34: Called die * The specific snippet of code: * die Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * The die message: * Move /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/media-sound:alsa-utils-1.0.20-r4:20090814-200133.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/alsa-utils-1.0.20-r4/temp/die.env'. Have you had such a problem? What's the fix? I have both files mentioned: # ls -la /etc/modules.d/alsa -rw-r--r-- 1 root root 202 Jan 5 2009 /etc/modules.d/alsa # ls -la /etc/modprobe.d/alsa.conf -rw-r--r-- 1 root root 1028 Jul 4 09:27 /etc/modprobe.d/alsa.conf -- Regards, Mick Obviously, the existence of /etc/modules.d/alsa does not allow emerge to continue. I think you must merge alsa file to alsa.conf and then delete alsa. Perhaps I'm too tired to understand the message ... is it telling to move file /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf by hand? -- Regards, Mick Yes. As I can see, these files are identical in sytax. Just add information from alsa to alsa.conf if any and them rm alsa.
