From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Laurens Van Houtven <_@lvh.io>
Cc: Bastien <bzg@gnu.org>, Nick Dokos <ndokos@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: Quotes for LaTeX export
Date: Wed, 05 Feb 2014 14:37:09 +0100 [thread overview]
Message-ID: <87k3d93cl6.fsf@gmail.com> (raw)
In-Reply-To: <CAE_Hg6a+1B5bC_8q9A4rXOUkDqcaoY1fB7uOmydZ_ghk1jTsng@mail.gmail.com> (Laurens Van Houtven's message of "Wed, 5 Feb 2014 12:30:58 +0100")
Hello,
Laurens Van Houtven <_@lvh.io> writes:
> On Wed, Feb 5, 2014 at 8:46 AM, Bastien <bzg@gnu.org> wrote:
>
>> Nick Dokos <ndokos@gmail.com> writes:
>>
>> > IIRC, there was support for csquotes in the old exporter[fn:1] but I
>> guess
>> > it went away when the new exporter came along.
>>
>> Yes, it'd be good to make it possible again to use
>> \usepackage{csquotes} and \enquote{something}.
>
>
> I guess it's obvious, but yes; I agree :)
I'm still not convinced about the need to support this package out of
the box.
We already have a working solution for many languages, and more general
that this LaTeX-centered command. It has limitations, but "csquotes"
support would inherit them anyway since it would be built on top of
smart quotes mechanism.
If you want to csquotes, I suggest to:
1. Disable smart quotes.
2. Define a macro like:
#+MACRO: q \enquote{$1}
3. Call the macro when you need it:
{{{q(something)}}}
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-02-05 13:37 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 [this message]
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=87k3d93cl6.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=_@lvh.io \
--cc=bzg@gnu.org \
--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).