unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Werner LEMBERG <wl@gnu.org>
Cc: gerd.moellmann@t-online.de, emacs-devel@gnu.org, rms@gnu.org,
	miles@gnu.org
Subject: Re: [wl@gnu.org: changing line heights]
Date: Fri, 26 Sep 2003 07:32:23 +0200 (CEST)	[thread overview]
Message-ID: <20030926.073223.258112866.wl@gnu.org> (raw)
In-Reply-To: <3F7394BC.1070103@jclark.com>

> > The default ' and ` characters in the XFree86 4.x fonts I looked
> > at*, by contrast, _are_ fairly easy to distinguish in my font --

Since I use the ETL fonts at a 24x12 resolution, this is true for me
also -- the ` and ' glyphs are *designed* to be used as left and right
quotes.

> Unicode says that the characters 0x60 and 0x27 are a grave accent
> and a vertical quote, not an open and close quotation mark.  The
> XFree86 fonts are doing the right thing.

The ETL fonts aren't XFree86 fonts...

> However, GNU documentation (info and doc strings) use them as open
> and close quotation marks.  It seems to me that the right solution
> is by default to map 0x60/0x27 to the Unicode quotation marks only
> in buffers displaying documentation (help and info); users should
> also be able to enable this mapping on a per-buffer basis and
> globally.

I agree.  Whatever solution is found, there should be an indication
for `C-u C-x =' that those characters (probably) come from a different
font.  Additionally, it should be possible to exactly specify which
font is used for those two characters.


    Werner

  parent reply	other threads:[~2003-09-26  5:32 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 [this message]
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.
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

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