On 2009-01-03 07:38 +0100, Osamu Aoki wrote: > On Fri, Jan 02, 2009 at 08:01:40PM +0100, Sven Joachim wrote: >> package emacs21 >> merge 352811 405952 >> thanks >> Hi, >> >> I'm triaging bugs in the emacs21 package. This one is particularly >> nasty. > > Thanks for the efforts. > >> On 2007-01-07 16:36 +0100, Osamu Aoki wrote: >> >> > Package: emacs21 >> > Version: 21.4a+1-3 >> > Severity: important >> > >> > I started emacs from shell and menu. Alas, I get many boxes. This kind >> > of funny application behavior is the typical situation when correct font >> > is not available. Is this intended thing under en_US.UTF-8 locale? I >> > thought etch was UTF-8 as default. >> >> It is, and for most people (including me) emacs21 works fine, yet some >> people see only hollow boxes instead of characters. The reasons are >> still unknown, although the problem has been discussed in great length >> in bug #352811. >> >> > Since gvim start without problem here, I think default behavior of emacs >> > deserves a bit better support. (I think issue is default font selection.) >> >> Two years have passed since. Do you still see the problem with the >> emacs[12] packages in Lenny? > > I do not experience this problem with the emacs21 package nor with the > emacs22 package in Lenny. (I am not extensive user of emacs)
Good to hear. > As you know: > We have new X server/client situation where fontconfig is used > (i.e., client side font management: the new Xft 2 font system is used) > So .Xdefaults may not be the only one chosing fonts. > > http://people.debian.org/~osamu/pub/getwiki/html/ch08.en.html#fontsinthexwindow None of this applies to Emacs 22 and earlier. Only Emacs 23 will have fontconfig/Xft support. > Also emacs might have changed default behavior ... Certainly not the emacs21 package, and emacs22 isn't much different in that respect. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
