emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

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 15:31:37 +0100	[thread overview]
Message-ID: <877g993a2e.fsf@gmail.com> (raw)
In-Reply-To: <CAE_Hg6bB3u7898H86dnTudkXuLEGnraBxGsZrYEYE0vRGKiGuA@mail.gmail.com> (Laurens Van Houtven's message of "Wed, 5 Feb 2014 15:05:33 +0100")

Laurens Van Houtven <_@lvh.io> writes:

> On Wed, Feb 5, 2014 at 2:37 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>
>> 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.
>>
>
> This is only for LaTeX-export, so I don't see how LaTeX-centered is
> relevant. I really don't see how it affects other export langs;

The current quote mechanism is built at the export framework level so
that each export back-end doesn't need to bring up its own recipe. I'd
rather not add back-end specific code unless it is an improvement.

So far, I don't see the improvement. Do you have an example of an Org
document that produces a wrong tex file, which would be correct if it
used "csquotes"?

> plus, it was in the old LaTeX exporter anyway!

True. And?

I gave you a solution to use "csquotes" feature in your documents.

> The reason is that the exporter occasionally produces TeX code that renders
> poorly on some setups (we're still figuring out which those are exactly).
> csquotes never does this.

I assume it will render poorly in setups that do not use that package.

I'm surprised that "csquotes" is compulsory in some setups. Of course,
it would be good to know about them so we can find a workaround.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2014-02-05 14: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 [this message]
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=877g993a2e.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

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