From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: LaTex export: How to use `csquotes' and `\enquote{}' Date: Thu, 07 Jul 2011 11:10:25 -0400 Message-ID: <17965.1310051425@alphaville.dokosmarshall.org> References: <6663.1309983647@alphaville.americas.hpqcorp.net> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([140.186.70.92]:48192) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QeqDq-00068m-1D for emacs-orgmode@gnu.org; Thu, 07 Jul 2011 11:10:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QeqDl-00044p-Dd for emacs-orgmode@gnu.org; Thu, 07 Jul 2011 11:10:33 -0400 Received: from vms173007pub.verizon.net ([206.46.173.7]:64610) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QeqDk-00044c-VC for emacs-orgmode@gnu.org; Thu, 07 Jul 2011 11:10:29 -0400 Received: from alphaville.dokosmarshall.org ([unknown] [173.76.32.106]) by vms173007.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LNY0005RY5DQG40@vms173007.mailsrvcs.net> for emacs-orgmode@gnu.org; Thu, 07 Jul 2011 10:10:27 -0500 (CDT) In-reply-to: Message from Stefan Nobis of "Thu, 07 Jul 2011 10:02:09 +0200." 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: Stefan Nobis Cc: Frederik , nicholas.dokos@hp.com, emacs-orgmode@gnu.org Stefan Nobis wrote: > Nick Dokos writes: > > > Here are some points to keep in mind while working on a patch: > > > o csquotes.sty is part of the texlive-latex-extra package on Ubuntu > > (and probably something similar on other Linux distros and > > possibly MacOS X - hunoz about Windoz?) > > On MacOS the MacTeX distribution is quite common and in this case a > complete TeXLive (including csquotes) is installed. > > On Windows MikTeX is probably the defacto standard and IIRC it > supports installing packages on demand (I'm not sure wether csquotes > is included in the basic installation, but on the other hand I would > assume that a complete installation is not uncommen). > OK, that's good. > But another suggestion: > > Always use \enquote for quotations in the exported text. In the > preambel of the document either include csquotes or provide a simple > macro enquote like the very simple > > \newcommand{\enquote}[1]{``#1''} > > Maybe a bit more hackery might be needed for some special cases, but > with this approach it would be quite easy to change quotations styles > later on. > Not too thrilled about this: the current handling for the bare-bones default case works OK and it could be easily extended to handle the csquotes case. I'd worry a bit about adding the newcommand in the preamble during org processing: what would happen if I tried to use csquotes then? Would I get a conflict? Would I have unpredictable situations where sometimes I'd get the bare-bones definition and sometimes the csquotes one? All of these can be answered of course, but the point is that you can't leave it to accident. > BTW: IMHO babel and csquotes should be considered standard packages > for all non-US texts (and even for US texts they have some > advantages). > Agreed. Nick