all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: sand@blarg.net
To: Kenichi Handa <handa@m17n.org>
Cc: sand@blarg.net, emacs-devel@gnu.org,
	613@emacsbugs.donarmstrong.com,
	Torsten Bronger <bronger@physik.rwth-aachen.de>
Subject: bug#613: 23.0.60; Unicode display problems
Date: Wed, 20 Aug 2008 07:11:54 -0700	[thread overview]
Message-ID: <18604.9770.893099.425147@priss.frightenedpiglet.com> (raw)
In-Reply-To: <E1KVcf0-0004FY-Gl@etlken.m17n.org>

Kenichi Handa writes:
> In article <87od3qqvlg.fsf@physik.rwth-aachen.de>, Torsten Bronger <bronger@physik.rwth-aachen.de> writes:
> 
> > finding a font for: (8220)
> > ftfont-list: -unknown-DejaVu Sans Mono-*-iso10646-1:script=symbol
> > list: -unknown-DejaVu Sans Mono-*-iso10646-1:script=symbol
> [...]
> 
> 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?

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.

Derek






  reply	other threads:[~2008-08-20 14:11 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-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 12:59               ` Kenichi Handa
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 [this message]
2008-08-21  0:51                       ` Kenichi Handa
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-09-01  2:53                               ` Kenichi Handa
2008-08-27 14:07                         ` 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:18                         ` Juanma Barranquero
2008-08-21  1:18                         ` Juanma Barranquero
2008-08-21  1:01                       ` Kenichi Handa
2008-08-18 13:52                 ` Torsten Bronger
2008-08-18 12:15           ` Kenichi Handa
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=18604.9770.893099.425147@priss.frightenedpiglet.com \
    --to=sand@blarg.net \
    --cc=613@emacsbugs.donarmstrong.com \
    --cc=bronger@physik.rwth-aachen.de \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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.