From: Stefan Kangas <stefankangas@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Mauro Aranda <maurooaranda@gmail.com>,
Eli Zaretskii <eliz@gnu.org>,
"stephen.berman@gmx.net" <stephen.berman@gmx.net>,
"ola.x.nilsson@axis.com" <ola.x.nilsson@axis.com>,
"64046@debbugs.gnu.org" <64046@debbugs.gnu.org>
Subject: bug#64046: 30.0.50; Quoting in customize choice tags
Date: Fri, 1 Sep 2023 00:59:58 +0200 [thread overview]
Message-ID: <CADwFkmn=pN=VzodFwBWVu6WxcOmt_8xbM+3hOEpyBqdyaN-9LQ@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB54881B198234986F6624D2D8F3E5A@SJ0PR10MB5488.namprd10.prod.outlook.com>
Drew Adams <drew.adams@oracle.com> writes:
> > Do you have an example of where it's not? I can't think of one, so
> > you'll have to help me here.
>
> Don't need one. The TITLE can be _any_ text.
> Who knows how ` and ' might be used? You don't,
> any more than I do. Or if you do, please let us
> know your assumptions about this: what gives you
> the idea that they should always be translated
> to curly quotes?
I was convinced by Stephen Berman's arguments upthread. He spoke
about the specifics of this function, how it might typically be used,
and used examples to show why using curly quotes is a good idea here.
The reality is that we have decided to use curly quotes in Emacs, in
places where it is typographically correct. That decision was made
before I was very active in the project, BTW. So either we reverse
that decision, or we try to be consistent about it. My position is
that the latter is preferable.
next prev parent reply other threads:[~2023-08-31 22:59 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:02 bug#64046: 30.0.50; Quoting in customize choice tags Stephen Berman
2023-06-13 15:56 ` Eli Zaretskii
2023-06-14 19:51 ` Mauro Aranda
2023-06-14 20:05 ` Mauro Aranda
2023-06-15 11:39 ` Stephen Berman
2023-06-22 20:07 ` Stephen Berman
2023-06-22 22:59 ` Mauro Aranda
2023-06-23 22:18 ` Stephen Berman
2023-06-24 6:37 ` Eli Zaretskii
2023-06-24 8:50 ` Stephen Berman
2023-07-15 13:20 ` Mauro Aranda
2023-07-20 15:48 ` Stephen Berman
2023-07-20 19:11 ` Mauro Aranda
2023-07-20 19:53 ` Stephen Berman
2023-08-21 12:04 ` Ola x Nilsson
2023-08-21 14:51 ` Mauro Aranda
2023-08-24 12:51 ` Stephen Berman
2023-08-24 13:19 ` Stephen Berman
2023-08-24 20:14 ` Mauro Aranda
2023-08-24 20:54 ` Stephen Berman
2023-08-24 21:58 ` Mauro Aranda
2023-08-25 8:02 ` Ola x Nilsson
2023-08-25 21:50 ` Stephen Berman
2023-08-28 9:33 ` Ola x Nilsson
2023-08-28 13:50 ` Stephen Berman
2023-08-30 15:29 ` Mauro Aranda
2023-08-30 16:29 ` Stephen Berman
2023-08-30 22:33 ` Mauro Aranda
2023-08-30 22:51 ` Stephen Berman
2023-08-30 22:58 ` Mauro Aranda
2023-08-31 5:41 ` Eli Zaretskii
2023-08-31 6:43 ` Stefan Kangas
2023-08-31 15:43 ` Drew Adams
2023-08-31 20:52 ` Stefan Kangas
2023-08-31 22:10 ` Drew Adams
2023-08-31 22:59 ` Stefan Kangas [this message]
2023-09-01 1:08 ` Drew Adams
2023-09-01 6:34 ` Eli Zaretskii
2023-09-01 16:17 ` Drew Adams
2023-09-01 23:29 ` Stephen Berman
2023-09-01 23:38 ` Stefan Kangas
2023-09-02 9:49 ` Stephen Berman
2023-09-02 18:59 ` Stefan Kangas
2023-09-02 21:25 ` Stephen Berman
2023-09-02 2:12 ` Drew Adams
2023-09-01 6:16 ` Eli Zaretskii
2023-09-01 16:32 ` Drew Adams
2023-08-24 20:53 ` Stefan Kangas
2023-08-24 21:10 ` Stephen Berman
2023-08-24 21:14 ` Stefan Kangas
2023-08-24 21:41 ` Stephen Berman
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='CADwFkmn=pN=VzodFwBWVu6WxcOmt_8xbM+3hOEpyBqdyaN-9LQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=64046@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=maurooaranda@gmail.com \
--cc=ola.x.nilsson@axis.com \
--cc=stephen.berman@gmx.net \
/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.