unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: sand@blarg.net
Cc: sand@blarg.net, emacs-devel@gnu.org,
	613@emacsbugs.donarmstrong.com, bronger@physik.rwth-aachen.de
Subject: Re: bug#613: 23.0.60; Unicode display problems
Date: Thu, 21 Aug 2008 09:51:21 +0900	[thread overview]
Message-ID: <E1KVyOX-0002nz-6S@etlken.m17n.org> (raw)
In-Reply-To: <18604.9770.893099.425147@priss.frightenedpiglet.com> (sand@blarg.net)

In article <18604.9770.893099.425147@priss.frightenedpiglet.com>, sand@blarg.net writes:

> Kenichi Handa writes:
[...]
> > Now I see what is wrong.  Dejavu Sans Mono lacks some of
> > charaters (#x201C #x2200 #x2500) to be used as `symbol'
> > font, so the other arbitrary font that contains all of those
> > characters are selected.  This setting was added by the
> > request in the attached mail, but it seems that the
> > restriction is too strong for symbol fonts.  So, I deleted
> > that restriction.  Please try again with the latest CVS code.

> Removing the symbol restrictions will allow Emacs to pick (incorrect)
> ISO8859-1 fonts for these characters again.  Have you changed
> something in the C code to prevent that?

Now the entry for symbols is this:

     (symbol ,(font-spec :registry "iso10646-1"))

So, at least, Emacs tries to select an iso10646-1 font that
is closest (in family, style, size) to the default font.

> Looking at the DejaVu Sans Mono glyphs in "gucharmap", it appears that
> #x2200 is the problem.  The #x201C, #x2200, #x2500 combination was an
> attempt to find "representative" symbol codepoints, but that
> combination isn't all-or-nothing.  Can you first try leaving just
> #x201C in `script-representative-chars'?  That's LEFT DOUBLE QUOTATION
> MARK, so it should have wide coverage.

I think the typical usage of symbol characters is to use a
few of them in a normal text.  In that case, the most
suitable font for those symbols is the default font
(provided that it supports those symbols) rather than a font
that covers wider range of symbols.  So, I think there's no
merit in restricting fonts in the above way.

As a result, when a sequence of many symbols is displayed,
Emacs will not use the same font for them, but, I think it's
not a big problem.

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




  reply	other threads:[~2008-08-21  0:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87myjv2tc8.fsf@stupidchicken.com>
     [not found] ` <E1KQGun-0001xF-Ms@etlken.m17n.org>
     [not found]   ` <87zlnrx33y.fsf@physik.rwth-aachen.de>
     [not found]     ` <E1KQbdw-0005G7-Jw@etlken.m17n.org>
     [not found]       ` <87ej52vg8r.fsf@physik.rwth-aachen.de>
2008-08-13 10:46         ` bug#613: 23.0.60; Unicode display problems Kenichi Handa
2008-08-18 12:15           ` Kenichi Handa
2008-08-18 12:49             ` Torsten Bronger
2008-08-18 12:59               ` Kenichi Handa
2008-08-18 13:52                 ` Torsten Bronger
2008-08-20  1:38                   ` Kenichi Handa
2008-08-20 14:11                     ` sand
2008-08-21  0:51                       ` Kenichi Handa [this message]
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-03  2:34                                 ` sand
2008-08-20 16:01                     ` Torsten Bronger
2008-08-21  1:01                       ` Kenichi Handa
2008-08-21  1:18                         ` Juanma Barranquero

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=E1KVyOX-0002nz-6S@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=613@emacsbugs.donarmstrong.com \
    --cc=bronger@physik.rwth-aachen.de \
    --cc=emacs-devel@gnu.org \
    --cc=sand@blarg.net \
    /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).