* [BUG] Nested lists in LaTeX export
@ 2009-06-12 9:44 Christian Egli
2009-06-13 6:07 ` Carsten Dominik
0 siblings, 1 reply; 3+ messages in thread
From: Christian Egli @ 2009-06-12 9:44 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
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
[-- Attachment #2: Org test file --]
[-- Type: text/plain, Size: 1177 bytes --]
## -*- 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.
[-- Attachment #3: HTML export --]
[-- Type: text/html, Size: 4130 bytes --]
[-- Attachment #4: LaTeX export --]
[-- Type: application/pdf, Size: 99667 bytes --]
[-- Attachment #5: Type: text/plain, Size: 204 bytes --]
_______________________________________________
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [BUG] Nested lists in LaTeX export 2009-06-12 9:44 [BUG] Nested lists in LaTeX export Christian Egli @ 2009-06-13 6:07 ` Carsten Dominik 2009-06-13 13:53 ` Scot Becker 0 siblings, 1 reply; 3+ messages in thread From: Carsten Dominik @ 2009-06-13 6:07 UTC (permalink / raw) To: Christian Egli; +Cc: emacs-orgmode 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 > • 1 Production > 1 Production > • 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. > • Install the package. > • Unpack the tar.gz on the production server. > • Install with the provided installation script such as make > install. > • Setup some configuration files according to the README or the > INSTALL file contained in the tar.gz. > If you use Puppet for deployment then do the following steps instead: > > • Integrate the installation in Puppet. > • Integrate the configuration as described in the README or the > INSTALL file in Puppet. > • Deploy. > • 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. > • 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 > > <test.pdf> > _______________________________________________ > 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [BUG] Nested lists in LaTeX export 2009-06-13 6:07 ` Carsten Dominik @ 2009-06-13 13:53 ` Scot Becker 0 siblings, 0 replies; 3+ messages in thread From: Scot Becker @ 2009-06-13 13:53 UTC (permalink / raw) To: Carsten Dominik; +Cc: Christian Egli, emacs-orgmode [-- Attachment #1.1: Type: text/plain, Size: 4845 bytes --] 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 (nesting shown by increasing numbers of asterisks), so one would be fairly simple to write. Easylist PDF doc here. <http://www.tug.org/texlive/devsrc/Master/texmf-dist/doc/latex/easylist/easylist-doc.pdf> My previous post on easylist<http://article.gmane.org/gmane.emacs.orgmode/13896>on 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 <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 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<http://reductivelabs.com/trac/puppet%5D%5BPuppet>]] >> 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 >> • 1 Production >> 1 Production >> • 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. >> • Install the package. >> • Unpack the tar.gz on the production server. >> • Install with the provided installation script such as >> make install. >> • Setup some configuration files according to the README or >> the INSTALL file contained in the tar.gz. >> If you use Puppet for deployment then do the following steps instead: >> >> • Integrate the installation in Puppet. >> • Integrate the configuration as described in the README or >> the INSTALL file in Puppet. >> • Deploy. >> • 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. >> • 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 >> >> <test.pdf> >> _______________________________________________ >> 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 > [-- Attachment #1.2: Type: text/html, Size: 5867 bytes --] [-- Attachment #2: Type: text/plain, Size: 204 bytes --] _______________________________________________ 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-06-13 13:53 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-06-12 9:44 [BUG] Nested lists in LaTeX export Christian Egli 2009-06-13 6:07 ` Carsten Dominik 2009-06-13 13:53 ` Scot Becker
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).