From: David Kastrup <dak@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: How to opt out of curly-quote spamming altogether?
Date: Tue, 25 Aug 2015 06:25:29 +0200 [thread overview]
Message-ID: <87k2skq9ja.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <c58dc562-7658-4425-94ec-4666ec07f851@default> (Drew Adams's message of "Mon, 24 Aug 2015 14:44:19 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
>> The proper representation in Unicode is the use of the English
>> ‘quote marks’: those are the proper characters for the glyphs TeX
>> and Texinfo use for text fonts in the slots for ` and '.
>> Consequently, it is quite correct that those are the output for
>> the preformatted Info pages.
>
> See above. It's not about translating ` and '. Imagine that those
> are not used in the input to start with, i.e., that we used other
> markup to distinguish inline code, URLs etc.
>
> That curly quotes are "proper representations in Unicode" of ` and '
> is irrelevant. We should not be asking how to represent ` and ',
> but how to demark things like inline code fragments in a structural
> layer and how to present them in a presentation layer.
>
> Besides which, the "proper representation" of ` and ' in Unicode
> is ` and '. They are first-class Unicode citizens.
What about “those are the proper characters for the glyphs TeX and
Texinfo use for text fonts in the slots for ` and '” did you not
understand?
--
David Kastrup
next prev parent reply other threads:[~2015-08-25 4:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<c1f42565-e538-49e6-b246-07e43dab673a@default>
[not found] ` <<834mjoha4r.fsf@gnu.org>
2015-08-24 17:57 ` How to opt out of curly-quote spamming altogether? Drew Adams
2015-08-24 18:05 ` Eli Zaretskii
2015-08-24 18:36 ` David Kastrup
2015-08-24 21:44 ` Drew Adams
2015-08-25 4:25 ` David Kastrup [this message]
[not found] <<a4c77735-a9de-400e-88f2-243c66e24836@default>
[not found] ` <<83fv38hfsx.fsf@gnu.org>
2015-08-24 16:34 ` Drew Adams
2015-08-24 16:45 ` Eli Zaretskii
2015-08-24 17:09 ` Paul Eggert
2015-08-24 17:29 ` Drew Adams
2015-08-24 18:44 ` Paul Eggert
[not found] ` <<c8408881-dddb-4661-9e7f-6ec42d9bf5fa@default>
[not found] ` <<837fokhby1.fsf@gnu.org>
2015-08-24 17:06 ` Drew Adams
2015-08-24 17:25 ` Eli Zaretskii
2015-08-24 4:16 Drew Adams
2015-08-24 15:22 ` Eli Zaretskii
2015-08-24 15:26 ` Paul Eggert
2015-08-24 17:06 ` Drew Adams
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=87k2skq9ja.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).