From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Coleman Gariety <garietyc@reed.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Secondary smart quotes are exported as apostrophes. [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/coleman/.emacs.d/elpa/org-9.1.14/)]
Date: Thu, 03 Jan 2019 12:21:39 +0100 [thread overview]
Message-ID: <87lg42ugu4.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJdAXQzEBNp_dP0+6PyEU2TdT9aVT2OAQrwrZUZHtzQ8+adhxw@mail.gmail.com> (Coleman Gariety's message of "Wed, 2 Jan 2019 13:51:12 -0800")
Hello,
Coleman Gariety <garietyc@reed.edu> writes:
> Also, it occurs to me that one can make use of single quotation marks as
> primary quotes when mentioning a word without using it. Moreover, when
> italics and double quotation marks are also present, the use of single
> quotations as primary is necessary.
>
> For example:
>
> 'GNU' is an acronym for the phrase "GNU's Not Unix!" but GNU is an
> operating system and *not* an acronym.
When you need that level of precision, smart quotes are not for you.
"Smart" quotes are a dumb way to automate some basic typographic rules.
Clearly, this is not what you are after.
You can use entities directly to obtain the desired result, e.g. \rsquo,
\lsquo...
> Is it feasible to add an option to treat single quotation marks as primary
> pairs on export?
I think you are mixing up the level of quotation and the glyph used. You
can export "..." as single quotes by setting
`org-export-smart-quotes-alist' accordingly.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-01-03 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 18:41 Bug: Secondary smart quotes are exported as apostrophes. [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/coleman/.emacs.d/elpa/org-9.1.14/)] Coleman Gariety
2019-01-01 15:46 ` Nicolas Goaziou
2019-01-02 21:51 ` Coleman Gariety
2019-01-03 11:21 ` Nicolas Goaziou [this message]
2019-01-06 3:51 ` Coleman Gariety
2019-01-08 10:13 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lg42ugu4.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=garietyc@reed.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).