From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Exporting to groff, now in org-export.el ... Date: Sat, 30 Jun 2012 08:42:36 +0200 Message-ID: <87k3yp1esj.fsf@gmail.com> References: <22257.1340710426@alphaville> <87fw9i15sq.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:39784) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SkrRP-0007l8-H8 for emacs-orgmode@gnu.org; Sat, 30 Jun 2012 02:46:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SkrRN-0003bj-Os for emacs-orgmode@gnu.org; Sat, 30 Jun 2012 02:45:59 -0400 Received: from mail-wg0-f49.google.com ([74.125.82.49]:44753) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SkrRN-0003bP-Fq for emacs-orgmode@gnu.org; Sat, 30 Jun 2012 02:45:57 -0400 Received: by wgbds1 with SMTP id ds1so2640256wgb.30 for ; Fri, 29 Jun 2012 23:45:54 -0700 (PDT) In-Reply-To: (Luis Anaya's message of "Fri, 29 Jun 2012 23:58:16 +0000") 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: Luis Anaya Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org Hello, Luis Anaya writes: > First release (?!) of the org-e-groff.el is available. I still need to > do more testing but it manages to export from org. Thanks for that new back-end. > The code is in the same github location, > http://github.com/papoanaya/emacs_utils. 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, it adds a lot of useless code (for example footnote handling is very specific and, as such, probably wrong on your back-end) and I'm not sure it will be a win in the long run. For future back-ends, I suggest to use an incremental approach, starting from scratch and adding features and transcoders step by step. Complexity can wait. Also, the way e-latex handles attributes isn't an example to follow: it uses "key=3Dvalue" instead of ":key value". If you use the latter, you can benefit from `org-export-read-attribute' function. Speaking of attributes, 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 dates.= =20 > The code to export and add the appropriate markup is completed, but=20 > that code is not running. By default, planning info are not exported. See `org-export-with-planning' variable. > I am aware that there is a flag at org-export.el to control the > output,=C2=A0 but they are all "t".=C2=A0 Before I go all crazy on this, = I need > to ask if this is a feature to control its output or am I missing > something that I should take a look. 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? Regards, --=20 Nicolas Goaziou