From: Martin Alsinet <martin@alsinet.com.ar>
To: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Nested smart quotes
Date: Thu, 05 Oct 2017 19:41:14 +0000 [thread overview]
Message-ID: <CABUJmkDLncC36n+g+EcWLswb=1TxR0B12gVjZyGHzUPT=hFAYw@mail.gmail.com> (raw)
In-Reply-To: <87wp49tnla.fsf@alphaville.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]
Hello Nick. First, thank you so much for your detailed answer.
On Thu, Oct 5, 2017 at 2:16 PM Nick Dokos <ndokos@gmail.com> wrote:
>
> 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).
>
>
I was beginning to suspect that, I didn't see it at first, but after
writing and explaining the problem, it dawned on me that it could be LaTeX
that cannot correctly parse the three consecutive single quotes.
> >
> > 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/)
>
I am using Org mode version 8.2.10, I will update my version and try again.
Martin
[-- Attachment #2: Type: text/html, Size: 2293 bytes --]
next prev parent reply other threads:[~2017-10-05 19:41 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
2017-10-05 19:41 ` Colin Baxter
2017-10-05 19:41 ` Martin Alsinet [this message]
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='CABUJmkDLncC36n+g+EcWLswb=1TxR0B12gVjZyGHzUPT=hFAYw@mail.gmail.com' \
--to=martin@alsinet.com.ar \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
/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).