From mboxrd@z Thu Jan 1 00:00:00 1970 From: Coleman Gariety 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: Sat, 5 Jan 2019 19:51:20 -0800 Message-ID: References: <87imz8z8h9.fsf@nicolasgoaziou.fr> <87lg42ugu4.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000001c1380057ec207d6" Return-path: Received: from eggsout.gnu.org ([209.51.188.92]:57737 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gfzTM-00046M-IJ for emacs-orgmode@gnu.org; Sat, 05 Jan 2019 22:51:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gfzTL-0003mQ-BG for emacs-orgmode@gnu.org; Sat, 05 Jan 2019 22:51:36 -0500 Received: from mail-yb1-xb29.google.com ([2607:f8b0:4864:20::b29]:39389) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gfzTL-0003g9-2z for emacs-orgmode@gnu.org; Sat, 05 Jan 2019 22:51:35 -0500 Received: by mail-yb1-xb29.google.com with SMTP id n187so12627588yba.6 for ; Sat, 05 Jan 2019 19:51:32 -0800 (PST) In-Reply-To: <87lg42ugu4.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Coleman Gariety , emacs-orgmode@gnu.org --0000000000001c1380057ec207d6 Content-Type: text/plain; charset="UTF-8" Nicolas, Thank you for your response. > When you need that level of precision, smart quotes are not for you. I agree. However, in specialized fields (linguistics and philosophy, for example), single quotation marks are commonly used to refer to technical terms or specialized uses of words : "Single quotes are easier on the eyes when reading material that uses quotes frequently, which is why academic publishers adopted this format for works in these areas." > You can use entities directly to obtain the desired result, e.g. \rsquo, \lsquo... I think that this is rather tedious. Do you agree? If so, it seems reasonable to me that there should be some option to export text such as... 'foo' ...in the form of... ‘foo’ It occurs to me that an academic who works in the field of linguistics or philosophy should be able to properly export his or her writing without using cryptic glyphs ("...") or commenting out line `5545` of `ox.el`. Do you agree? Thank you for your time and your consideration. Coleman On Thu, Jan 3, 2019 at 3:21 AM Nicolas Goaziou wrote: > Hello, > > Coleman Gariety 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 > --0000000000001c1380057ec207d6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Nicolas,

<= div>Thank you for your response.

> When you need = that level of precision, smart quotes are not for you.

=
I agree. However, in specialized fields (linguistics and philosophy, f= or example), single quotation marks are commonly used to refer to technical terms or specialized uses of words:= =C2=A0"Single quotes are easier on the eyes when reading material that= uses quotes frequently, which is why academic publishers adopted this form= at for works in these areas."

> You = can use entities directly to obtain the desired result, e.g. \rsquo, \lsquo= ...

I think that this is rather tedious. Do you ag= ree? If so, it seems reasonable to me that there should be some option to e= xport text such as...

'foo'

...in the fo= rm of...

=C2=A0&lsquo;foo&rsquo;

It occu= rs to me that an academic who works in the field of linguistics or philosop= hy should be able to properly export his or her writing without using crypt= ic glyphs ("...") or commenting out line `5545` of `ox.el`. Do yo= u agree?

Thank you for your time and your consider= ation.
Coleman

On Thu, Jan 3, 2019 at 3:21 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
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!&q= uot; 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 pri= mary
> 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
--0000000000001c1380057ec207d6--