all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: miles@gnu.org, gerd.moellmann@t-online.de, wl@gnu.org,
	emacs-devel@gnu.org
Subject: Re: [wl@gnu.org: changing line heights]
Date: Fri, 26 Sep 2003 22:31:30 -0400	[thread overview]
Message-ID: <E1A34rq-00054t-Ms@fencepost.gnu.org> (raw)
In-Reply-To: <3F73D92F.5050508@jclark.com> (message from James Clark on Fri, 26 Sep 2003 13:14:07 +0700)

    I wonder whether we should divide the problem into two parts:

    - One part is whether in a particular buffer 0x60/0x27 should be 
    displayed so that they look like grave/vertical quote or like open/close 
    quote.  This is determined by mode and individual user preference; this 
    problem is specific to quotes.

This seems like a clean approach, assuming we need to offer more than one
way to do it.  But it would be better to find one way that satisfies
all the problems.

It looks like the problem is that the appearances for 0x27 and 0x60
don't look right for open and close quote, but the others that look
right for open/close quote are at the same time too similar to each
other.  Is that correct?

If so, is there a way that avoids both problems?

What about displaying 0x60 as accent grave, and 0x27 as close quote?
They would not "match" in style, but they would be better as
open quote and close quote than the standard font images for
0x60 and 0x27.  Meanwhile, they would not look similar either.

    - One part is whether the glyphs at index 0x60/0x27 in a particular font 
    display as grave/vertical quote or like open/close quote.  This has 
    nothing to do with user preference or mode. Emacs could be configured so 
    that it knows about common free fonts. This part seems like it would be 
    best tackled in a general way by allowing per-font control over 
    character to glyph index mapping (or is there some way to do this in 
    Emacs do this already?).

If we need to offer multiple options, this is a good way to make them
default more correctly.  At the same time, it might be a substantial
amount of work just to enter and maintain data about lots of fonts.

  reply	other threads:[~2003-09-27  2:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86isni5yyh.fsf@gerd.free-bsd.org>
     [not found] ` <20030924.144951.177659448.wl@gnu.org>
     [not found]   ` <86brta5noi.fsf@gerd.free-bsd.org>
2003-09-25  8:47     ` [wl@gnu.org: changing line heights] Werner LEMBERG
2003-09-25  9:23       ` Jason Rumney
2003-09-25 23:21         ` Richard Stallman
2003-09-25 23:30           ` Jason Rumney
2003-09-26 14:54             ` Richard Stallman
2003-09-25  9:56       ` Gerd Moellmann
2003-09-25 12:58         ` Werner LEMBERG
2003-09-25 23:21         ` Richard Stallman
2003-09-26  0:37           ` Miles Bader
2003-09-26  1:22             ` James Clark
2003-09-26  1:40               ` Miles Bader
2003-09-27  2:31                 ` Richard Stallman
2003-09-26  5:32               ` Werner LEMBERG
2003-09-26  6:14                 ` James Clark
2003-09-27  2:31                   ` Richard Stallman [this message]
2003-09-27  5:56                     ` Werner LEMBERG
2003-09-28 15:33                       ` Richard Stallman
2003-09-27 20:20                   ` Kai Grossjohann
2003-09-26  7:23               ` Jason Rumney
2003-09-26 14:03               ` James H.Cloos Jr.
2003-09-27  2:15         ` Kenichi Handa
2003-09-29  1:41           ` Kenichi Handa
2003-09-25 23:21       ` Richard Stallman
2003-09-25 23:47         ` Jason Rumney

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=E1A34rq-00054t-Ms@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@t-online.de \
    --cc=miles@gnu.org \
    --cc=wl@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.