all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: James H.Cloos Jr. <cloos@jhcloos.com>
Cc: Gerd Moellmann <gerd.moellmann@t-online.de>,
	wl@gnu.org, emacs-devel@gnu.org, Richard Stallman <rms@gnu.org>,
	Miles Bader <miles@gnu.org>
Subject: Re: [wl@gnu.org: changing line heights]
Date: Fri, 26 Sep 2003 10:03:12 -0400	[thread overview]
Message-ID: <m37k3vtzof.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <3F7394BC.1070103@jclark.com> (James Clark's message of "Fri, 26 Sep 2003 08:22:04 +0700")

>>>>> "James" == James Clark <jjc@jclark.com> writes:

James> It seems to me that the right solution is by default to
James> map 0x60/0x27 to the Unicode quotation marks only in
James> buffers displaying documentation (help and info);

GNU documentation is not the only user of `' for ‘’ and
``'' for “”, that is also the way TeX specifies quotes.
And apostrophes.

Not to mention their use in source code.

James> users should also be able to enable this mapping
James> on a per-buffer basis and globally.

As Miles wrote, some fonts make the glyphs hard to distinguish.
A few years ago I used to use 75dpi/lutRS08.bdf for xterms and
emacs.  (Really. :)  There is no where there to tell apart the
open and close glyphs.  OTOH, I now use misc/9x18.bdf and that
makes the glyphs easy to distinguish.  It is important to give
the users a single defcustom that the default behavior depends
on, as well as per mode and per buffer controls.

-JimC

  parent reply	other threads:[~2003-09-26 14:03 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
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. [this message]
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=m37k3vtzof.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@t-online.de \
    --cc=miles@gnu.org \
    --cc=rms@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.