From: Nick Dokos <nicholas.dokos@hp.com>
To: Luis Anaya <papoanaya@hotmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting to groff...
Date: Tue, 26 Jun 2012 07:33:46 -0400 [thread overview]
Message-ID: <22257.1340710426@alphaville> (raw)
In-Reply-To: Message from Luis Anaya <papoanaya@hotmail.com> of "Mon, 25 Jun 2012 23:36:56 EDT." <BLU0-SMTP34026A4F0A2F8A46C4F1014B7E00@phx.gbl>
Luis Anaya <papoanaya@hotmail.com> wrote:
> Hi:
>
> Being that groff is not available in org mode (at least by default, I
> decided to give it a try and write a driver to export Org files into
> groff with the use of the -mm macros.
>
> Being that I'm not familiar with many of the facilities in Org mode,
> I am modifying the org-latex.el to write groff markups.
>
> In its current incarnation it exports the titles, content and basic
> support for tables
>
> You can see the resultant output at: http://ppl.ug/1_8pA3lpXWA/
>
> Really messy code currently in http://github.com/papoanaya/emacs_utils
>
If you are going to continue working on this and take it further, it
would be a good idea to change your starting point: org-latex.el is on
its way to extinction, to be replaced by Nicolas Goaziou's "new"
exporter. The code for that is in contrib/lisp/org-export.el, and the
latex/html/ascii backends are implemented in
contrib/lisp/org-e-{latex,html,ascii}.el. They are all based on a "real"
org parser in contrib/lisp/org-elements.el, as opposed to the ad-hoc
collection that the current backends use.
Nick
next prev parent reply other threads:[~2012-06-26 11:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 3:36 Exporting to groff Luis Anaya
2012-06-26 11:33 ` Nick Dokos [this message]
2012-06-26 14:09 ` Luis Anaya
2012-06-26 14:55 ` Nicolas Goaziou
2012-06-29 23:58 ` Exporting to groff, now in org-export.el Luis Anaya
2012-06-30 6:42 ` Nicolas Goaziou
2012-06-30 11:56 ` Nicolas Goaziou
2012-07-03 1:18 ` Luis Anaya
2012-07-03 9:51 ` Nicolas Goaziou
2012-07-05 22:46 ` Luis Anaya
2012-07-06 7:14 ` Nicolas Goaziou
2012-07-07 14:25 ` #+CAPTION: Not being protected when they are used with #+begin_src Luis Anaya
2012-07-07 17:15 ` Eric Schulte
2012-07-07 19:00 ` Luis Anaya
2012-07-07 19:01 ` Nicolas Goaziou
2012-07-07 19:33 ` Luis Anaya
2012-07-07 20:28 ` Exporting to groff, now in org-export.el Luis Anaya
2012-07-07 20:31 ` Luis Anaya
2012-07-07 22:59 ` suvayu ali
2012-07-08 1:49 ` Luis Anaya
2012-07-08 1:56 ` suvayu ali
2012-07-08 13:14 ` Luis Anaya
2012-07-08 14:07 ` Suvayu Ali
2012-07-09 0:29 ` Luis Anaya
2012-07-09 20:32 ` Luis Anaya
2012-07-09 21:23 ` suvayu ali
2012-07-09 21:55 ` Luis Anaya
2012-07-09 22:01 ` suvayu ali
2012-07-10 0:00 ` Luis Anaya
2012-07-10 0:21 ` suvayu ali
2012-07-10 1:09 ` Luis Anaya
2012-07-10 1:20 ` suvayu ali
2012-07-10 13:30 ` Luis Anaya
2012-06-30 22:36 ` Luis Anaya
2012-07-13 18:51 ` Luis Anaya
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=22257.1340710426@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=papoanaya@hotmail.com \
/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).