From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurens Van Houtven <_@lvh.io> Subject: Re: Quotes for LaTeX export Date: Wed, 5 Feb 2014 14:31:25 +0100 Message-ID: References: <87eh3iftc7.fsf@gmx.us> <87ppn1zrkc.fsf@gmx.us> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e013a08a2301f1504f1a8c75f Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36690) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <_@lvh.cc>) id 1WB2a0-00070d-Gc for emacs-orgmode@gnu.org; Wed, 05 Feb 2014 08:31:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <_@lvh.cc>) id 1WB2Zu-0005bD-BK for emacs-orgmode@gnu.org; Wed, 05 Feb 2014 08:31:52 -0500 Received: from mail-yk0-f174.google.com ([209.85.160.174]:37293) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <_@lvh.cc>) id 1WB2Zu-0005b5-5q for emacs-orgmode@gnu.org; Wed, 05 Feb 2014 08:31:46 -0500 Received: by mail-yk0-f174.google.com with SMTP id 10so942764ykt.5 for ; Wed, 05 Feb 2014 05:31:45 -0800 (PST) In-Reply-To: <87ppn1zrkc.fsf@gmx.us> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rasmus Cc: emacs-orgmode@gnu.org --089e013a08a2301f1504f1a8c75f Content-Type: text/plain; charset=ISO-8859-1 On Wed, Feb 5, 2014 at 1:12 PM, Rasmus wrote: > This is exactly the reasons why I don't want to use csquotes: > > \enquote{something}. > I'm not sure I understand. Are you suggesting the syntax is bad? 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. > Okay, that's a fair argument. It would require consistent configuration in more than one place, unless (I think?) Org's LaTeX export automagically use/configure Babel. > > > 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 "'". > Right: I'm talking about TeX and not org-mode there. The semantic way to say "this is quoted" is csquotes and \enquote. Are those code points U+0022 QUOTATION MARK and U+0027 APOSTROPHE? (I am not an org-mode expert. I'm assuming org-mode does operate on code points, not bytes?) \documentclass{article} > \usepackage{fontspec} > \addfontfeatures{Mapping=} > \addfontfeatures{Ligatures=} > \begin{document} > ``test'' > \end{document} > > Could you share a snip that reproduces your problem? > That appears to compile correctly on my machine as well. Perhaps there is a discrepancy between how I'm building the tex file and how org is building the intermediary tex file. I will investigate :) thanks again lvh --089e013a08a2301f1504f1a8c75f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On W= ed, Feb 5, 2014 at 1:12 PM, Rasmus <rasmus@gmx.us> wrote:
This is exactly the reasons why I don't want to use csquotes:

=A0 =A0 =A0\enquote{something}.

I'm= not sure I understand. Are you suggesting the syntax is bad?

=
But check for instance org-latex-tables-booktabs, which makes optional
support for booktabs. =A0That kind of support for csquote is of course
OK. =A0One reason I'd not use this is that the quotes exported to HTML<= br> and LaTeX are no longer in sync. =A0Which is why I'd rather see
customization through a user smart quote alist.
=

Okay, that's a fair argument. It would= require consistent configuration in more than one place, unless (I think?)= Org's LaTeX export automagically use/configure Babel.
=A0
> =A0> I think it would make sense to support this for org, and perha= ps
>> eventually
>> > make it default behavior. FWIW: I had no idea about this unti= l it bit me
>> > when my LaTeX document suddenly had bogus quotes in it.
>>
>> This has never happened to me, despite extensive usage of LaTeX fo= r
>> 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 '"' an= d "'".

Right: I'm tal= king about TeX and not org-mode there. The semantic way to say "this i= s quoted" is csquotes and \enquote.

Are those code points U+0022 QUOTATION MARK and U+0027 APOSTROPHE? (I a= m not an org-mode expert. I'm assuming org-mode does operate on code po= ints, not bytes?)

=A0=A0 \documentclass{article}
=A0 =A0\usepackage{fontspec}
=A0 =A0\addfontfeatures{Mapping=3D}
=A0 =A0\addfontfeatures{Ligatures=3D}
=A0 =A0\begin{document}
=A0 =A0``test''
=A0 =A0\end{document}

Could you share a snip that reproduces your problem?

That a= ppears to compile correctly on my machine as well. Perhaps there is a discr= epancy between how I'm building the tex file and how org is building th= e intermediary tex file. I will investigate :)

thanks again
lvh
--089e013a08a2301f1504f1a8c75f--