From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scot Becker Subject: Re: [BUG] Nested lists in LaTeX export Date: Sat, 13 Jun 2009 14:53:45 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0290857043==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MFTg9-0005Hl-10 for emacs-orgmode@gnu.org; Sat, 13 Jun 2009 09:53:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MFTg4-0005Dc-6s for emacs-orgmode@gnu.org; Sat, 13 Jun 2009 09:53:52 -0400 Received: from [199.232.76.173] (port=46158 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFTg3-0005DH-NS for emacs-orgmode@gnu.org; Sat, 13 Jun 2009 09:53:47 -0400 Received: from mail-fx0-f217.google.com ([209.85.220.217]:49971) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MFTg2-0000FI-0w for emacs-orgmode@gnu.org; Sat, 13 Jun 2009 09:53:47 -0400 Received: by mail-fx0-f217.google.com with SMTP id 17so4164523fxm.42 for ; Sat, 13 Jun 2009 06:53:45 -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: Carsten Dominik Cc: Christian Egli , emacs-orgmode@gnu.org --===============0290857043== Content-Type: multipart/alternative; boundary=001485f85ef64ff18f046c3b2721 --001485f85ef64ff18f046c3b2721 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable This may not do what you want, but check out the 'easylist' package on CTAN. It allows deeply nested lists. It's quite flexible (though I don't think it lets you specify *different* kinds of list bullets/numbers within the same list). There is no org export path to easylist, but by default it uses a format very like org's plain text list and outline structure (nestin= g shown by increasing numbers of asterisks), so one would be fairly simple to write. Easylist PDF doc here. My previous post on easyliston this list Like I said, as far as I can tell, it wouldn't work with your sample document without some modification, but it does have some possibility for some kinds of nested lists. Scot On Sat, Jun 13, 2009 at 7:07 AM, Carsten Dominik wrote: > 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 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 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 y= ou >> have access to it when you ever need to roll back to an older 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 install. >> =95 Setup some configuration files according to the READM= E or >> the 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 READM= E or >> the INSTALL file in Puppet. >> =95 Deploy. >> =95 If the deployment fails or the application doesn't come up, t= he >> installation is rolled back, i.e. the package is removed with the uninst= all >> script, and the old version is reinstalled. The faulty package is sent b= ack >> to Development. >> =95 If the installation was successful the package is integrated = in >> 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 >> > > > > _______________________________________________ > 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 > --001485f85ef64ff18f046c3b2721 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable This may not do what you want, but check out the 'easylist' package= on CTAN.=A0 It allows deeply nested lists.=A0 It's quite flexible (tho= ugh I don't think it lets you specify *different* kinds of list bullets= /numbers within the same list).=A0 There is no org export path to easylist,= but by default it uses a format very like org's plain text list and ou= tline structure (nesting shown by increasing numbers of asterisks), so one = would be fairly simple to write.=A0

Easylist PDF doc here. <= br>My previo= us post on easylist on this list

Like I said, as far as I can tell, it wouldn't work with your sampl= e document without some modification, but it does have some possibility for= some kinds of nested lists.

Scot


On Sat, Jun 13, 2009 at 7:07 AM, Carsten Dominik <carsten.dominik@= gmail.com> wrote:
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 sentence
"If you use Puppet...steps instead:" is missing and the second su= blist
is inserted in the parent list.

All is done with latest org from git.

Thanks
Christian

## =A0-*- mode: org; -*-
#+TITLE: =A0 =A0 Software Deployment Process
#+LANGUAGE: =A0en

** Production

1. Keep the delivered and accepted package in a save place, so you
=A0have access to it when you ever need to roll back to an older
=A0version or if you need to redeploy the package.
2. Install the package.
=A01. Unpack the ~tar.gz~ on the production server.
=A02. Install with the provided installation script such as ~make
=A0 =A0 install~.
=A03. Setup some configuration files according to the ~README~ or the
=A0 =A0 ~INSTALL~ file contained in the ~tar.gz~.
=A0If you use [[http://reductivelabs.com/trac/puppet][Puppet]] for= deployment then do the following steps instead:
=A01. Integrate the installation in Puppet.
=A02. Integrate the configuration as described in the ~README~ or the
=A0 =A0 ~INSTALL~ file in Puppet.
=A03. Deploy.
3. If the deployment fails or the application doesn't come up, the
=A0installation is rolled back, i.e. the package is removed with the
=A0uninstall script, and the old version is reinstalled. The faulty
=A0package is sent back to Development.
4. If the installation was successful the package is integrated in the
=A0error monitoring system.


Software Deployment Process
Table of Contents
=A0 =A0 =A0 =A0=95 1 Production
1 Production
=A0 =A0 =A0 =A0=95 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 vers= ion or if you need to redeploy the package.
=A0 =A0 =A0 =A0=95 Install the package.
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=95 Unpack the tar.gz on the production ser= ver.
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=95 Install with the provided installation = script such as make install.
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=95 Setup some configuration files accordin= g to the README or the INSTALL file contained in the tar.gz.
If you use Puppet for deployment then do the following steps instead:

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=95 Integrate the installation in Puppet. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=95 Integrate the configuration as describe= d in the README or the INSTALL file in Puppet.
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=95 Deploy.
=A0 =A0 =A0 =A0=95 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 packag= e is sent back to Development.
=A0 =A0 =A0 =A0=95 If the installation was successful the package is integ= rated in the error monitoring system.
Date: 2009-06-12 11:40:23 CEST

HTML generated by org-mode 6.27trans in emacs 23

<test.pdf>
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gn= u.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode



_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gn= u.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

--001485f85ef64ff18f046c3b2721-- --===============0290857043== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============0290857043==--