From: Kenichi Handa <handa@m17n.org>
To: Sascha Wilde <wilde@sha-bang.de>
Cc: emacs-devel@gnu.org
Subject: Re: Display problems with non-ascii characters
Date: Wed, 08 Oct 2008 20:43:48 +0900 [thread overview]
Message-ID: <E1KnXSG-0002Sd-In@etlken.m17n.org> (raw)
In-Reply-To: <m24p3n34xc.fsf@kenny.sha-bang.de> (message from Sascha Wilde on Wed, 08 Oct 2008 09:46:23 +0200)
In article <m24p3n34xc.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.
> 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
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-10-08 11:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 13:12 Display problems with non-ascii characters Sascha Wilde
2008-10-07 12:13 ` Kenichi Handa
2008-10-07 17:20 ` Sascha Wilde
2008-10-08 1:21 ` Kenichi Handa
2008-10-08 7:46 ` Sascha Wilde
2008-10-08 11:43 ` Kenichi Handa [this message]
2008-10-08 15:19 ` Sascha Wilde
2008-10-09 16:19 ` Sascha Wilde
2008-10-10 1:21 ` Kenichi Handa
2008-10-10 7:45 ` Sascha Wilde
2008-10-14 9:14 ` Sascha Wilde
2008-10-14 11:49 ` Kenichi Handa
2008-10-14 12:29 ` Sascha Wilde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1KnXSG-0002Sd-In@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=wilde@sha-bang.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).