From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Elston Subject: Re: Re: IMPORTANT: (possibly) incompatible Change Date: Thu, 01 Apr 2010 18:17:08 -0700 Message-ID: <4BB54594.5070803@comcast.net> References: <86sk7gooh2.fsf@portan.ibr.cs.tu-bs.de> <3E3E058D-6BBD-4D9B-845D-3E13235EF0DC@gmail.com> <4BB3973D.3090305@comcast.net> <9667B267-935B-4DFB-800B-FC76DBCCBF28@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NxVVv-0001we-0b for emacs-orgmode@gnu.org; Thu, 01 Apr 2010 21:17:35 -0400 Received: from [140.186.70.92] (port=38826 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NxVVt-0001uJ-PF for emacs-orgmode@gnu.org; Thu, 01 Apr 2010 21:17:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NxVVs-0007Nl-BY for emacs-orgmode@gnu.org; Thu, 01 Apr 2010 21:17:33 -0400 Received: from qmta11.emeryville.ca.mail.comcast.net ([76.96.27.211]:51616) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NxVVr-0007NN-RX for emacs-orgmode@gnu.org; Thu, 01 Apr 2010 21:17:32 -0400 In-Reply-To: <9667B267-935B-4DFB-800B-FC76DBCCBF28@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Carsten, Thanks for this clarification. This makes the transition much simpler than I originally thought. I can certainly remove the common package names. The existing org-export-latex-classes also contains the documentclass line. That won't change, will it? I am assuming from what you have written that the generated LaTeX code will be something like: Is this correct? Mark On 3/31/2010 11:59 PM, Carsten Dominik wrote: > Hi Mark, > > OK, it seems that I have really overstated this change. You are of > course right that your header for a document type can be very long, > that that defining it in org-export-latex-classes is a viable option > (other being to put this stuff into a separate file). > > So let me restate what I am trying to say in this thread. > > ------------------------------------------------------------------------------ > > Org-mode contains now a new variable > `org-export-latex-default-packages-alist' > which contains all the LaTeX packages it needs to use for basic Org-mode > functionality. The corresponding \usepackage statements used to be part > of the header definitions in org-export-latex-classes, and they had to > be repeated for each document class. This is wasteful, error prone, and > hard to maintain. > Therefore, these packages are now collected in the new variable, > and they will be spliced into the header. > > If you have customized the variable org-export-latex-classes, you need to > remove the following lines from each class definition: > > \usepackage[AUTO]{inputenc} > \usepackage[T1]{fontenc} > \usepackage{graphicx} > \usepackage{longtable} > \usepackage{float} > \usepackage{wrapfig} > \usepackage{soul} > \usepackage{latexsym} > \usepackage{amssymb} > \usepackage{hyperref} > > If you have other packages you always want to use in all > classes, you can add them to another variable, > `org-export-latex-packages-alist'. > ------------------------------------------------------------------------------ > > > > I think this makes more sense, thank you for making me clarify this. > > - Carsten > > >