From: "Tim O'Callaghan" <tim.ocallaghan@gmail.com>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: About latex export
Date: Tue, 9 Sep 2008 19:00:23 +0200 [thread overview]
Message-ID: <3d6808890809091000h7f59d2cbr66701addd13cea06@mail.gmail.com> (raw)
In-Reply-To: <4C0C70B0-53BC-482D-9FC7-A0CEC5E73E52@uva.nl>
For the Latex users, I feel i should also point out this tool called
Plans Unfolding.
http://www.myreckonings.com/PlansUnfolding
I've not had a chance to play with it properly, but it uses latex
templates for all of its reports, so might be a handy resource/tool
Tim.
2008/9/8 Carsten Dominik <dominik@science.uva.nl>:
> Hi Nick,
>
> please see
>
> http://article.gmane.org/gmane.emacs.orgmode/7684/
>
> On Sep 8, 2008, at 8:08 PM, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> While fiddling with latex export, I wondered if there was a variable to
>> specify some more packages that should be added the code produced — i.e.
>> I'd like to add \usepackage[frenchb]{babel} everytime.
>>
>> I could somehow manage to write a function adding it after exporting the
>> code — maybe with the help of a hook — but I can't help thinking it
>> would be messier.
>>
>> On another topic, it looks like the latex export process doesn't play
>> well with the "description" environment. In fact,
>>
>> - a :: first
>> - b :: second
>>
>> is rendered as
>>
>> \begin{itemize}
>> \item a :: first
>> \item b :: second
>> \end{itemize}
>>
>> Odd, isn't it ?
>
> Not odd, description lists have not yet been implemented in the LaTeX
> exporter.
>
> - Carsten
>
>
>
> _______________________________________________
> 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
>
prev parent reply other threads:[~2008-09-09 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 18:08 About latex export Nicolas Goaziou
2008-09-08 20:20 ` Carsten Dominik
2008-09-09 16:46 ` Nicolas Goaziou
2008-09-09 17:00 ` Tim O'Callaghan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d6808890809091000h7f59d2cbr66701addd13cea06@mail.gmail.com \
--to=tim.ocallaghan@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).