all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Torsten Bronger <bronger@physik.rwth-aachen.de>
Cc: 613@emacsbugs.donarmstrong.com, emacs-devel@gnu.org
Subject: bug#613: 23.0.60; Unicode display problems
Date: Wed, 13 Aug 2008 19:46:51 +0900	[thread overview]
Message-ID: <E1KTDsR-0007MI-4Y__46291.3909731016$1218625723$gmane$org@etlken.m17n.org> (raw)
In-Reply-To: <87ej52vg8r.fsf@physik.rwth-aachen.de> (message from Torsten Bronger on Wed, 06 Aug 2008 07:56:20 +0200)

Sorry for the late responce.

> Kenichi Handa writes:
> > Thank you.  But, unfortunately, the list was too long and
> > font-show-log truncated such long lists.  Please show me the
> > value of font-log itself instead:
> >
> > (1) Start Emacs as "% emacs -Q".
> > (2) ESC : (setq font-log nil)
> > (3) ESC : (insert #x201c)
> > (4) C-h v font-log RET

Thank you for the data.  I found very strange thing.  The
log has this entry.

>  (list "-unknown-DejaVu Sans Mono-*-iso10646-1"
>        [])

So, Emacs couldn't find a font matching with:
  -unknown-DejaVu Sans Mono-*-iso10646-1
But, the log also has this entry.

>  (list "-unknown-DejaVu Sans Mono-*-normal-normal-*-m-0-iso10646-1"
>        ["-unknown-DejaVu Sans Mono-bold-normal-normal-*-m-0-iso10646-1" "-unknown-DejaVu Sans Mono-normal-normal-normal-*-m-0-iso10646-1"])

So, Emacs found:
  -unknown-DejaVu Sans Mono-bold-normal-normal-*-m-0-iso10646-1
even if it should match with the former font pattern.

I tried various settings but I couldn't reproduce such a
thing.  Aren't there anyone else who has the same problem.

To find out what's going on in your environment, I need more
detailed logging info.  So I'm going to improve the font-log
facility.

By the way, what is the result of:

% fc-list 'Dejavu Sans Mono' file

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






  parent reply	other threads:[~2008-08-13 10:46 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 17:57 bug#613: 23.0.60; Unicode display problems Chong Yidong
2008-08-05  7:25 ` Kenichi Handa
2008-08-05  8:44   ` Torsten Bronger
2008-08-06  5:33     ` Kenichi Handa
2008-08-06  5:56       ` Torsten Bronger
2008-08-13 10:46         ` Kenichi Handa
2008-08-18 12:15           ` Kenichi Handa
2008-08-18 12:49             ` Torsten Bronger
2008-08-18 12:49             ` Torsten Bronger
2008-08-18 12:59               ` Kenichi Handa
2008-08-18 13:52                 ` Torsten Bronger
2008-08-18 13:52                 ` Torsten Bronger
2008-08-20  1:38                   ` Kenichi Handa
2008-08-20  1:38                   ` Kenichi Handa
2008-08-20 14:11                     ` sand
2008-08-21  0:51                       ` Kenichi Handa
2008-08-27 14:07                         ` sand
2008-08-27 14:07                         ` sand
2008-08-28  6:51                           ` Kenichi Handa
2008-08-28 15:16                             ` sand
2008-09-01  2:53                               ` Kenichi Handa
2008-09-01  2:53                               ` Kenichi Handa
2008-09-03  2:34                                 ` sand
2008-08-21  0:51                       ` Kenichi Handa
2008-08-20 16:01                     ` Torsten Bronger
2008-08-20 16:01                     ` Torsten Bronger
2008-08-21  1:01                       ` Kenichi Handa
2008-08-21  1:01                       ` Kenichi Handa
2008-08-21  1:18                         ` Juanma Barranquero
2008-08-21  1:18                         ` Juanma Barranquero
2008-08-18 12:59               ` Kenichi Handa
2008-08-18 12:15           ` Kenichi Handa
2008-08-13 10:46         ` Kenichi Handa [this message]
2008-08-06  6:59       ` Torsten Bronger
2008-08-05 14:14   ` Chong Yidong
  -- strict thread matches above, loose matches on Subject: below --
2008-09-02 16:35 Chong Yidong
2008-09-02 19:59 ` Torsten Bronger
2008-09-02 20:06   ` Torsten Bronger
2008-07-26 17:32 Torsten Bronger

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='E1KTDsR-0007MI-4Y__46291.3909731016$1218625723$gmane$org@etlken.m17n.org' \
    --to=handa@m17n.org \
    --cc=613@emacsbugs.donarmstrong.com \
    --cc=bronger@physik.rwth-aachen.de \
    --cc=emacs-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.