unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Torsten Bronger <bronger@physik.rwth-aachen.de>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; wrong glyph widths of some Unicode codepoints
Date: Fri, 23 May 2008 15:46:52 +0900	[thread overview]
Message-ID: <E1JzR3E-00016T-TT@etlken.m17n.org> (raw)
In-Reply-To: <8763t6r1tp.fsf@physik.rwth-aachen.de> (message from Torsten Bronger on Thu, 22 May 2008 13:54:42 +0200)

In article <8763t6r1tp.fsf@physik.rwth-aachen.de>, Torsten Bronger <bronger@physik.rwth-aachen.de> writes:

> The sub/superscripts (e.g. ⁴ or ₃) are narrower than the ordinary
> characters if using a monospace font (monospace-13 in my case), with
> the exceptions of ¹²³.  The same is true at least for the prime
> character ′.  The right arrow → and the cubic root ∛ used to have a
> "correct" width, but with the recent Emacs, it is too wide (the
> cubic root even too tall, too).

Please type C-u C-x = on normal ascii characters and those
problematic characters and check which fonts are used.

By the way, are you sure that your monospace-13 font has
glyphs for all of them.  In my environtment, monospace font
is actually mapped to "bitstream vera sans mono" and that
font doesn't have glyphs for those characters.  In such a
situation, it's difficult to expect to see them with the
same metrics as others.

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




  reply	other threads:[~2008-05-23  6:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 11:54 23.0.60; wrong glyph widths of some Unicode codepoints Torsten Bronger
2008-05-23  6:46 ` Kenichi Handa [this message]
2008-05-23  7:00   ` Torsten Bronger
2008-05-23  7:55     ` Kenichi Handa
2008-05-23  8:57       ` David Hansen
2008-05-23 12:25         ` Kenichi Handa
2008-05-23 12:51           ` Jason Rumney
2008-05-23 16:47       ` David De La Harpe Golden

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=E1JzR3E-00016T-TT@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=bronger@physik.rwth-aachen.de \
    --cc=emacs-pretest-bug@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 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).