From: Werner LEMBERG <wl@gnu.org>
Cc: miles@gnu.org, gerd.moellmann@t-online.de, emacs-devel@gnu.org,
jjc@jclark.com
Subject: Re: [wl@gnu.org: changing line heights]
Date: Sat, 27 Sep 2003 07:56:30 +0200 (CEST) [thread overview]
Message-ID: <20030927.075630.55493946.wl@gnu.org> (raw)
In-Reply-To: <E1A34rq-00054t-Ms@fencepost.gnu.org>
> 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?
Not really. It depends on the used fonts. `Classical' fonts like the
ETL bitmap fonts which provide only glyphs for ISO 8859 characters
normally don't have U+2018/U+2019 at all -- the exception is
greek-iso8859-7, but this is broken currently (see my other mail).
For such fonts, the ` and ' characters are almost exclusively used for
left and right quotes -- there is hardly a need to have a stand-alone
version of the grave accent. [I know this is hard to avoid on
e.g. German keyboards which use dead-keys to create accented
characters.]
In case someone wants to use U+2018 and U+2019 instead of 0x27 and
0x60, there must be a possibility to select the font. In my case, I
would select the ETL iso-8859-7 fonts for *some* modes, not for all.
> 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
^^^^^^^^^^^^^^
[Can't resist: Either something is correct, or it isn't -- what does
`more correctly' then mean? :-)]
> substantial amount of work just to enter and maintain data about
> lots of fonts.
I think this is unavoidable. IMHO you shouldn't combine glyphs from
different fonts without asking the user. Perhaps some standard fonts
can be covered in a table, but in general this won't work.
A suggestion: If the user types `C-u C-x =' while being on a left or
right quote, a string like
This glyph is probably taken from another font and thus looks ugly!
Please use `M-x configure-quotation-glyphs' to set up replacement
glyphs for the left and right quotation characters.
could appear in the pop-up window.
Werner
next prev parent reply other threads:[~2003-09-27 5:56 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 [this message]
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=20030927.075630.55493946.wl@gnu.org \
--to=wl@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@t-online.de \
--cc=jjc@jclark.com \
--cc=miles@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).