From: Laurens Van Houtven <_@lvh.io>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Quotes for LaTeX export
Date: Wed, 5 Feb 2014 12:30:35 +0100 [thread overview]
Message-ID: <CAE_Hg6ZKSjwQQCr9GYMsr78SibaQ-Yrrc+Lf6C7JrHYqbR4dxg@mail.gmail.com> (raw)
In-Reply-To: <87eh3iftc7.fsf@gmx.us>
[-- Attachment #1: Type: text/plain, Size: 2780 bytes --]
Hi Rasmus,
On Tue, Feb 4, 2014 at 10:42 PM, Rasmus <rasmus@gmx.us> wrote:
> Hi Laurens,
>
> Laurens Van Houtven <_@lvh.io> writes:
>
> > I'm writing a book using org-mode. On export, org-mode turns double
> quotes
> > like "hello" into ``hello''. Some modern LaTeXes no longer support that
> > form, instead preferring semantic markup. (The reasoning being that the
> > markup implies a particular quote style, whereas quotation style is
> > language-dependent.)
>
> This is not true. Quotes depend on your LANGUAGE-cookie. See
> org-export-smart-quotes-alist.
>
To more accurately: *my* org-mode is turning double quotes into
``something'' when I export to LaTeX. I do not have an explicit language
cookie set. That is the part you objected to, not the LaTeX part, right?
> > As a result, I get
> >
> > The preferred way to do that these days is, in the preamble:
> >
> > \usepackage{csquotes}
> >
> > ... and then later:
> >
> > \enquote{something}
>
> But this would require us to load an extra package. Org is quite
> capable of handling this on the lisp side (and Org ≠ LaTeX). Clearly,
> we could have a org-export-user-smart-quote-alist taking priority over
> the predefined one.
>
A package that, IIUC, is quite commonly available. Plus, the consequence is
that on a bunch of new setups, you get busted quotes, whereas the csquote +
enquote approach AFAIK works on pretty much any reasonable LaTeX
installation.
That said, if org does it, that's fine by me too.
> I think it would make sense to support this for org, and perhaps
> eventually
> > make it default behavior. FWIW: I had no idea about this until it bit me
> > when my LaTeX document suddenly had bogus quotes in it.
>
> This has never happened to me, despite extensive usage of LaTeX for
> almost ten years.
>
This is a fairly new occurrence, and it is not true for all LaTeXes
currently available. The motivation is the one that I have given above:
quotations are language-specific and semantic markup is preferable. I don't
have an exact list of which, but e.g. in ConTeXt MkIV it is now the
default, and it is also the default for me on the current TeX Live when
using lualatex or xelatex. This leads me to believe that perhaps it is not
a *common* issue, but it
Here is an example:
https://f.cloud.github.com/assets/97816/2078835/cac687b6-8dc2-11e3-8b6a-00c1a8175c94.png
> If there is no interest to add this to org, how do I hack org so that this
> > is what it does?
>
> The cleanest way would be a filter, probably
> org-export-filter-quote-block-functions and filter-plain-text.
>
> The easiest way would be a macro or simply redefining
> org-export-smart-quotes-alist to suit your needs.
>
thanks!
lvh
[-- Attachment #2: Type: text/html, Size: 4108 bytes --]
next prev parent reply other threads:[~2014-02-05 11:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 20:44 Quotes for LaTeX export Laurens Van Houtven
2014-02-04 21:42 ` Rasmus
2014-02-04 22:05 ` Nick Dokos
2014-02-05 7:46 ` Bastien
2014-02-05 11:30 ` Laurens Van Houtven
2014-02-05 13:37 ` Nicolas Goaziou
2014-02-05 14:05 ` Laurens Van Houtven
2014-02-05 14:31 ` Nicolas Goaziou
2014-02-05 11:30 ` Laurens Van Houtven [this message]
2014-02-05 12:12 ` Rasmus
2014-02-05 13:31 ` Laurens Van Houtven
2014-02-05 13:44 ` Rasmus
2014-02-05 14:06 ` Laurens Van Houtven
[not found] ` <871tzh1qwf.fsf@strey.biz>
2014-02-06 11:31 ` Michael Strey
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=CAE_Hg6ZKSjwQQCr9GYMsr78SibaQ-Yrrc+Lf6C7JrHYqbR4dxg@mail.gmail.com \
--to=_@lvh.io \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).