From: David Kastrup <dak@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Alan Mackenzie <acm@muc.de>, Emacs Development <Emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/internationa
Date: Fri, 04 Sep 2015 20:53:39 +0200 [thread overview]
Message-ID: <8737yut3rg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <55E9E45E.7090206@cs.ucla.edu> (Paul Eggert's message of "Fri, 4 Sep 2015 11:35:10 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 09/04/2015 11:07 AM, David Kastrup wrote:
>> whether the
>> display/font/whatever warrants specific marking for third-party texts
>
> This is not strictly a third-party issue. For example, the Emacs
> manual is not a third-party text, and it uses curved quotes.
Its use of curved quotes is outside of the interactive Emacs' control,
so for the purpose of display-related options, it is a third-party text.
Some people might want to have an Info-specific setting of such a
display option, but an Emacs-specific setting does not make any sense.
> True, we could develop a more-complicated mechanism, presumably with
> more variables to control the added complexity -- for example, we
> could implement three separate variables to control quotes in
> diagnostics vs quotes in help buffers vs quotes in info files -- but
> there are advantages to keeping things simple when user need for the
> extra complexity has not been demonstrated.
Conversion of Emacs' _output_ and _display_ manipulations are entirely
separate operations. It does not make sense to conflate them by
stipulating a set of permissible motives for either desire.
--
David Kastrup
next prev parent reply other threads:[~2015-09-04 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 14:51 [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/internationa Paul Eggert
2015-09-04 16:23 ` Alan Mackenzie
2015-09-04 17:49 ` Paul Eggert
2015-09-04 18:07 ` David Kastrup
2015-09-04 18:35 ` Paul Eggert
2015-09-04 18:53 ` David Kastrup [this message]
2015-09-04 18:53 ` Alan Mackenzie
2015-09-05 18:40 ` Paul Eggert
2015-09-09 9:38 ` Paul Eggert
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=8737yut3rg.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=acm@muc.de \
--cc=eggert@cs.ucla.edu \
/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.