emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Nested smart quotes
Date: Thu, 05 Oct 2017 15:13:21 -0400	[thread overview]
Message-ID: <87wp49tnla.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: CABUJmkDmvMN7vXH7gvL+9WUVeT0K7XuSa2krRhf6tPbRnHktPg@mail.gmail.com

Martin Alsinet <martin@alsinet.com.ar> writes:

> ...
> I have found that the smart-quotes option of org-mode does not export properly the quotes when they are nested (single quotes inside double quotes), but only when they coincide at the
> start or the end of the quote.
>
> Maybe the problem will be clearer with an example:
>
> #+TITLE: Smart quotes example
> #+OPTIONS: toc:nil ':t
> #+LANGUAGE: en
> #+LATEX_CLASS: book
> She said to me: "Rick screamed, 'let's go together'" 
>

This example has the additional problem of the apostrophe in "let's", which
basically causes more mayhem. Let's simplify the example a bit by considering

    She said to me: "Rick screamed, 'let us go together'"

which when export to TeX becomes:

    She said to me: ``Rick screamed, `let us go together'''

and TeX misinterprets the three closing single quotes as (closing
double quote, closing single quote) instead of (closing single quote,
closing double quote).

Modifying the TeX output to this:

    She said to me: ``Rick screamed, `let us go together'\,''

makes TeX interpret things correctly and it is also visually pleasant
(IMO of course).

> This gets exported to TeX as:
>
> She said to me: ``Rick screamed, `let's go together'''
>
> Which gets rendered as PDF as:
>
> The orde
>
> The order of the closing quotes gets reversed, it first closes the outside double quotes and then the nested single quote.
>
> I have tried leaving a space between them, but that is arguably worse
>
> Org:
>
> She said to me: "Rick screamed, 'let's go together' " 
>
> TeX:
>
> She said to me: ``Rick screamed, `let's go together' "

I do not get this with the space. I get this in the TeX output:

   She said to me: ``Rick screamed, `let us go together' ''

which has a larger space between the single and the double quote at the end
than with \, but is otherwise OK.


>
> Internal
>
> In this case, the internal single quotes are rendered correctly, but the closing quote is not converted into its "smart" version.
>
> If the nested quotes are in such a way that there are other characters between the quotes, that is they are not together at the start or the end of the quote, they get rendered correctly.

I'm not sure whether smart quotes can be made smarter, perhaps by
detecting the problem and inserting the small space \, to resolve the
ambiguity; but the manual space solution should have worked: what
version of org are you using?

FWIW, mine is latest master: Org mode version 9.1.2
(release_9.1.2-84-geeaf9a @ /home/nick/src/emacs/org/org-mode/lisp/)

Going back to the original string with the apostrophe, I don't see any
way that org or TeX can deal with it except by really understanding
what is being said: having the apostrophe be denoted by the same
symbol as the closing quote is bound to introduce ambiguities. In
these days of Unicode, I think the only solution is to use xelatex or
another Unicode-cognizant TeX system and to use a proper apostrophe.

-- 
Nick

  parent reply	other threads:[~2017-10-05 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 16:27 Nested smart quotes Martin Alsinet
2017-10-05 17:22 ` Colin Baxter
2017-10-05 17:39   ` Martin Alsinet
2017-10-05 18:46 ` Nicolas Goaziou
2017-10-05 19:13 ` Nick Dokos [this message]
2017-10-05 19:41   ` Colin Baxter
2017-10-05 19:41   ` Martin Alsinet
2017-10-05 21:36     ` Nested smart quotes [fixed] Martin Alsinet
2017-10-05 21:56 ` Nested smart quotes Adonay Felipe Nogueira
2017-10-05 22:21   ` Martin Alsinet

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=87wp49tnla.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@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/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).