From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Quotes for LaTeX export
Date: Wed, 05 Feb 2014 13:12:35 +0100 [thread overview]
Message-ID: <87ppn1zrkc.fsf@gmx.us> (raw)
In-Reply-To: CAE_Hg6ZKSjwQQCr9GYMsr78SibaQ-Yrrc+Lf6C7JrHYqbR4dxg@mail.gmail.com
Hi Laurens,
Laurens Van Houtven <_@lvh.io> writes:
> 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?
The language is org-export-default-language if no LANGUAGE is set.
>> > 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
d>> 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.
This is exactly the reasons why I don't want to use csquotes:
\enquote{something}.
But check for instance org-latex-tables-booktabs, which makes optional
support for booktabs. That kind of support for csquote is of course
OK. One reason I'd not use this is that the quotes exported to HTML
and LaTeX are no longer in sync. Which is why I'd rather see
customization through a user smart quote alist.
> > 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:
See below.
> quotations are language-specific and semantic markup is preferable.
Org already has semantic quote characters, namely '"' and "'".
Compare the output of
#+LANGUAGE: fr
#+OPTIONS: ':t
"test"
and
#+LANGUAGE: en
#+OPTIONS: ':t
"test"
> 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
I'm unable to reproduce with TeXLive up-to-date 2013 with both XeLaTeX
and LuaLaTeX. I don't have context installed. Here's my code where I
tried to disable fancy features of fontspec:
\documentclass{article}
\usepackage{fontspec}
\addfontfeatures{Mapping=}
\addfontfeatures{Ligatures=}
\begin{document}
``test''
\end{document}
Could you share a snip that reproduces your problem?
–Rasmus
--
I hear there's rumors on the, uh, Internets. . .
next prev parent reply other threads:[~2014-02-05 12:11 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
2014-02-05 12:12 ` Rasmus [this message]
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=87ppn1zrkc.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).