emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Quotes for LaTeX export
Date: Tue, 04 Feb 2014 22:42:16 +0100	[thread overview]
Message-ID: <87eh3iftc7.fsf@gmx.us> (raw)
In-Reply-To: CAE_Hg6YxrksOG0eQ_b17q6cx7g583YyyZnuiLr6xH_WKG=fEjA@mail.gmail.com

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.


> 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.

> 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.

> 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.

Hope it helps.

—Rasmus

-- 
Er du tosset for noge' lårt!

  reply	other threads:[~2014-02-04 21:38 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 [this message]
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
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=87eh3iftc7.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).