From: Luis Anaya <papoanaya@hotmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting to groff, now in org-export.el ...
Date: Fri, 13 Jul 2012 14:51:27 -0400 [thread overview]
Message-ID: <BLU0-SMTP371FEEB7AD2734A52DBFC4DB7D70@phx.gbl> (raw)
In-Reply-To: <87k3yp1esj.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 30 Jun 2012 08:42:36 +0200")
Hi:
I'm still working on this exporter, however being that my boss wants me to do
some actual productive work, I need to split the time between work and
hacking in emacs lisp.
However, during the week I performed the following coding changes to the
groff exporter:
1. Cleaned up some issues related to nested lists and special blocks.
2. Added formatting control on tables. Now the use of <l> <w> and <c>
will propagate in the exported table.
3. Added a new option for title line on tables (:title-line). It overrides the first
line to cb (centralized bold).
4. Added support to propagate column width. It will convert 5 characters
to one centimeter. It works sort of ok, but it's groff's doing, not
org-mode. Needs more testing, but what I want to export, it's being
exported fine.
5. Removed irrelevant code, more needs to be removed. This will be ongoing.
Some of these have been discovered while eating my own dog food. I have
an org file in which I store all the meeting notes. I started to export
those to PDF using the groff exporter. Things that have been found that
have resulted in bugs are being fixed and propagated. I'll do that to
make sure that the exporter is stable for daily use by... using it
daily. :)
--
Luis Anaya
papoanaya aroba hot mail punto com
"Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
prev parent reply other threads:[~2012-07-13 18:43 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
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 [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=BLU0-SMTP371FEEB7AD2734A52DBFC4DB7D70@phx.gbl \
--to=papoanaya@hotmail.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).