all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 295@emacsbugs.donarmstrong.com
Subject: bug#295: 23.0.60; wrong glyph widths of some Unicode codepoints
Date: Wed, 06 Aug 2008 08:58:03 +0200	[thread overview]
Message-ID: <87abfqvddw.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: <871w136o8l.fsf@physik.rwth-aachen.de>

Hallöchen!

Torsten Bronger writes:

> Chong Yidong writes:
>
>>>> The sub/superscripts are narrower than the ordinary characters
>>>> if using a monospace font (monospace-13 in my case)
>>>
>>> IIUC your problem is that not all thsoe characters use the same
>>> font.  This may be due to your font not having those chars, or
>>> to Emacs doing something wrong.
>>>
>>> Can you check again with the latest code (where some font
>>> problems have been fixed)?  Use C-u C-x = to find the font used
>>> for the char at point.
>>
>> Do you still see this problem?
>
> Yes.  Take for example left and right German double quotes (which
> are alternative interpretations of x201e and x201c):
>
> [...]

I mixed up the bugs, so my reply was only partly true.  For the sub-
superscript numbers, everything is alright now.  The other glyphs
indeed still look sub-optimal, though.

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus
                   Jabber ID: torsten.bronger@jabber.rwth-aachen.de






  reply	other threads:[~2008-08-06  6:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 22:50 bug#295: 23.0.60; wrong glyph widths of some Unicode codepoints Chong Yidong
2008-08-05 23:22 ` Torsten Bronger
2008-08-06  6:58   ` Torsten Bronger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-22 11:54 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=87abfqvddw.fsf@physik.rwth-aachen.de \
    --to=bronger@physik.rwth-aachen.de \
    --cc=295@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    /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.