From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: [BUG] Nested lists in LaTeX export Date: Sat, 13 Jun 2009 08:07:43 +0200 Message-ID: References: Mime-Version: 1.0 (Apple Message framework v935.3) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MFMPB-0006R0-Ji for emacs-orgmode@gnu.org; Sat, 13 Jun 2009 02:07:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MFMP6-0006Px-0s for emacs-orgmode@gnu.org; Sat, 13 Jun 2009 02:07:52 -0400 Received: from [199.232.76.173] (port=51811 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFMP5-0006Pu-SG for emacs-orgmode@gnu.org; Sat, 13 Jun 2009 02:07:47 -0400 Received: from mail-ew0-f225.google.com ([209.85.219.225]:64087) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MFMP4-0001Bq-WE for emacs-orgmode@gnu.org; Sat, 13 Jun 2009 02:07:47 -0400 Received: by ewy25 with SMTP id 25so2074631ewy.42 for ; Fri, 12 Jun 2009 23:07:46 -0700 (PDT) In-Reply-To: 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: Christian Egli Cc: emacs-orgmode@gnu.org Hi Christian, this is indeed a shortcoming of the list parser used only in LaTeX export, but not in the other exporters. Unfortunately I do not have an easy fix. - Carsten On Jun 12, 2009, at 11:44 AM, Christian Egli wrote: > Hi > > I have the following org snippet which exports properly using the HTML > and the docbook exporter. Open the attached file and export it to HTML > to see how item #2 of the parent list contains two numbered sublists. > > If you however export this to pdf using the latex exporter the =20 > sentence > "If you use Puppet...steps instead:" is missing and the second sublist > is inserted in the parent list. > > All is done with latest org from git. > > Thanks > Christian > > ## -*- mode: org; -*- > #+TITLE: Software Deployment Process > #+LANGUAGE: en > > ** Production > > 1. Keep the delivered and accepted package in a save place, so you > have access to it when you ever need to roll back to an older > version or if you need to redeploy the package. > 2. Install the package. > 1. Unpack the ~tar.gz~ on the production server. > 2. Install with the provided installation script such as ~make > install~. > 3. Setup some configuration files according to the ~README~ or the > ~INSTALL~ file contained in the ~tar.gz~. > If you use [[http://reductivelabs.com/trac/puppet][Puppet]] for =20 > deployment then do the following steps instead: > 1. Integrate the installation in Puppet. > 2. Integrate the configuration as described in the ~README~ or the > ~INSTALL~ file in Puppet. > 3. Deploy. > 3. If the deployment fails or the application doesn't come up, the > installation is rolled back, i.e. the package is removed with the > uninstall script, and the old version is reinstalled. The faulty > package is sent back to Development. > 4. If the installation was successful the package is integrated in the > error monitoring system. > > > Software Deployment Process > Table of Contents > =95 1 Production > 1 Production > =95 Keep the delivered and accepted package in a save place, so = you =20 > have access to it when you ever need to roll back to an older =20 > version or if you need to redeploy the package. > =95 Install the package. > =95 Unpack the tar.gz on the production server. > =95 Install with the provided installation script such = as make =20 > install. > =95 Setup some configuration files according to the = README or the =20 > INSTALL file contained in the tar.gz. > If you use Puppet for deployment then do the following steps instead: > > =95 Integrate the installation in Puppet. > =95 Integrate the configuration as described in the = README or the =20 > INSTALL file in Puppet. > =95 Deploy. > =95 If the deployment fails or the application doesn't come up, = the =20 > installation is rolled back, i.e. the package is removed with the =20 > uninstall script, and the old version is reinstalled. The faulty =20 > package is sent back to Development. > =95 If the installation was successful the package is integrated = in =20 > the error monitoring system. > Date: 2009-06-12 11:40:23 CEST > > HTML generated by org-mode 6.27trans in emacs 23 > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode