From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis Anaya Subject: Re: Exporting to groff, now in org-export.el ... Date: Sat, 30 Jun 2012 22:36:40 +0000 Message-ID: References: , <22257.1340710426@alphaville>, , <87fw9i15sq.fsf@gmail.com>, , <87k3yp1esj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:40307) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sl6HV-00039I-03 for emacs-orgmode@gnu.org; Sat, 30 Jun 2012 18:36:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sl6HT-0000Sy-AK for emacs-orgmode@gnu.org; Sat, 30 Jun 2012 18:36:44 -0400 Received: from bay0-omc3-s17.bay0.hotmail.com ([65.54.190.155]:41109) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sl6HT-0000Sh-43 for emacs-orgmode@gnu.org; Sat, 30 Jun 2012 18:36:43 -0400 In-Reply-To: <87k3yp1esj.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: n.goaziou@gmail.com Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org Hi: > I see this is based on org-e-latex.el. While this is a fast way to have > a back-end running in the short term=2C it adds a lot of useless code (fo= r > example footnote handling is very specific and=2C as such=2C probably wro= ng > on your back-end) and I'm not sure it will be a win in the long run. True. I wanted to get something going to get the feel of the routine.=A0 I = know that there is a lot of latex specific code=2C and I will clean it up as tes= ting goes on.=20 In terms of foot notes. I did adjust to the way GROFF uses them=2C but when= I tested them nothing came out. The way it works is to insert a .FS/.FE pair on the text to be footnoted. GROFF will place the text in the footnote and automatically add the marker in the location that the .FS/.FE marks where placed.=20 Well=2C it is not working... so needs to be fixed :) [chomp... good suggestions!] > Speaking of attributes=2C org-e-groff.el has to add "ATTR_GROFF" to both > `org-element-affiliated-keywords' and `org-element-multiple-keywords'. > > > One thing I have not managed to export are the deadlines/scheduled date= s. > > The code to export and add the appropriate markup is completed=2C but > > that code is not running. > > By default=2C planning info are not exported. See > `org-export-with-planning' variable. I suspected that there was a variable that controlled it=3B but I was not s= ure=2C=20 thanks for clarifying. > > Are you talking about org-export-with-* variables? Some of them have > a nil value (planning is an example). What do you want to know about > them? I thought that these were used to control the export of the planning=20 information. But you already answered my question. Luis =