Re: Display problems with non-ascii characters

[Kenichi Handa <handa@m17n.org>]

In article <m2myhg2ug9.fsf@kenny.sha-bang.de>, Sascha Wilde <wilde@sha-bang.de> writes:

>>> 3. ; evaluate:
>>> (set-face-font 'default "terminus 12")
>>> ; everything looks fine, but the umlauts disappeared and when you
>>> ; move the text cursor above them even the cursor disappears.
> >
> > This bug doesn't happen for me. 

> Stange enough: for me too (nightly cvs builds, so this is no more the
> same CVS head), but in normal use the problem is still there...

Which font is used in that "normal use"?  C-u C-x = tells
the font name.

> Indeed this is a very annoying heisen-bug: I see the same symptoms under
> varying conditions all the time, but its hard to get a reproduction
> receipt.  A co-worker of mine has the same problems with a different
> font -- both fonts have in common, that they are x11 bitmap fonts.

> Maybe the used toolkit is a factor two?  This is with lucid (haven't
> tested gtk2)...

I don't think so because the display routine doesn't use
toolkit's renderer.

> > The font used for those German letters is:
> >     x:-xos4-terminus-medium-r-normal--16-160-72-72-c-80-iso10646-1 (#xC4)

>>> 4. ; evaluate:
>>> (set-face-font 'default "terminus 11")
>>> ; the umlauts reappear.
> >
> > This doesn't change the font for me.  Which font is used in
> > your case in 3 and 4?

> For 3 (Terminus 12):
>   x:-xos4-terminus-medium-r-normal--16-160-72-72-c-80-iso10646-1 
> and for 4 (Terminus 11):
>   x:-xos4-terminus-medium-r-normal--14-140-72-72-c-80-iso10646-1

It seems that your display has the different resolution than
mine (100dpi).  What resolution is yours (xdpyinfo command
tells it)?

---
Kenichi Handa
handa@ni.aist.go.jp