Re: Display problems with non-ascii characters

[Kenichi Handa]

In article <address@hidden>, Sascha Wilde <address@hidden> 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.

> x:-xos4-terminus-medium-r-normal--16-160-72-72-c-80-iso8859-1

You at first wrote that in the case of "terminus 12", the
font used was:

x:-xos4-terminus-medium-r-normal--16-160-72-72-c-80-iso10646-1

It's different from the above only in CHARSET_REGISTRY
field, but it had the problem.  Now you wrote that the case
of "terminus 12" doesn't show a problem but "normal use"
shows the problem.  Does it mean that the font used for
"terminus 12" is different now?

>>> 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)?

> resolution:    96x96 dots per inch

Ah, that's why the 14 dots font is selected for terminus 11
point in your case.

Your 96 DPI case:
(* 96 (/ 11 72.27)) => 14.6  ==> 14-dot font matches best
(* 96 (/ 12 72.27)) => 15.9  ==> 16-dot font matches best

My 100 DPI case
(* 100 (/ 11 72.27)) => 15.2 ==> 16-dot font matches best
(* 100 (/ 12 72.27)) => 16.6 ==> 16-dot font matches best

---
Kenichi Handa
address@hidden