From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Luis Anaya <papoanaya@hotmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Exporting to groff, now in org-export.el ...
Date: Sat, 30 Jun 2012 08:42:36 +0200 [thread overview]
Message-ID: <87k3yp1esj.fsf@gmail.com> (raw)
In-Reply-To: <BAY171-W476BAE1AEA79E05B6C4098B7E50@phx.gbl> (Luis Anaya's message of "Fri, 29 Jun 2012 23:58:16 +0000")
Hello,
Luis Anaya <papoanaya@hotmail.com> 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=value" 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.
> The code to export and add the appropriate markup is completed, but
> 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, but they are all "t". 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,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-06-30 6:46 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
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 [this message]
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=87k3yp1esj.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
--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).